April 5th, 2013, 7:22
April 5th, 2013, 7:51
April 5th, 2013, 8:08
April 5th, 2013, 14:09
customukr wrote:Hi,
One of our clients wishes to obtain an old JPG of his sons football team from an old redundant floppy drive.
There are two in total, one with a pzp archive (with the jpg embedded), the other one has the single jpg file.
Both the floppy drives have bad sectors, therefore attempting to copy out of the drive onto desktop will fail with both. The drives and files can be loaded into HxD, but as you scroll down the data stream it will lock up. Of course tools like R-Studio etc can't get around the bad sector issue.
I need to clone the device, but have a lack of available tools (apart from DD). What do you think will be sufficient? I don't want to try DD until I know the best course of action as i'm worried the amount of stress the device will receive will leave it unusable.
I appreciate your time.
Thanks,
Chris

April 6th, 2013, 3:58
Spildit wrote:If you have a very old pc, like a IBM Ps2 you will have better resoults reading damaged floppies at the low speed it uses.
April 6th, 2013, 5:58
April 6th, 2013, 7:58
April 6th, 2013, 9:43
customukr wrote:Hi,
One of our clients wishes to obtain an old JPG of his sons football team from an old redundant floppy drive.
There are two in total, one with a pzp archive (with the jpg embedded), the other one has the single jpg file.
Both the floppy drives have bad sectors, therefore attempting to copy out of the drive onto desktop will fail with both. The drives and files can be loaded into HxD, but as you scroll down the data stream it will lock up. Of course tools like R-Studio etc can't get around the bad sector issue.
I need to clone the device, but have a lack of available tools (apart from DD). What do you think will be sufficient? I don't want to try DD until I know the best course of action as i'm worried the amount of stress the device will receive will leave it unusable.
I appreciate your time.
Thanks,
Chris
April 6th, 2013, 11:02
fzabkar wrote:Your statement made me curious, but I was unable to find any reference to any speed other than 300RPM or 360RPM. In fact, AISI, a reduced rotation rate would result in a lower signal amplitude. That's because the EMF induced in the head coil is proportional to the time rate of change of flux, and that is in turn proportional to the RPM. Therefore ISTM that reducing the RPM would make it more difficult to read a marginal diskette.
April 6th, 2013, 17:30
fzabkar wrote:Spildit wrote:If you have a very old pc, like a IBM Ps2 you will have better resoults reading damaged floppies at the low speed it uses.
Your statement made me curious, but I was unable to find any reference to any speed other than 300RPM or 360RPM. In fact, AISI, a reduced rotation rate would result in a lower signal amplitude. That's because the EMF induced in the head coil is proportional to the time rate of change of flux, and that is in turn proportional to the RPM. Therefore ISTM that reducing the RPM would make it more difficult to read a marginal diskette.
As I mentioned in my post about how to use the FC5025 ( http://www.spellboundblog.com/2011/07/2 ... sks-from... ), I found many of my disks had read errors on some sectors. Is there a chance that the KryoFlux will be able to read sectors that the FC5025 cannot?
Thanks!
Jeanne
Jeanne
Yes, it is possible. The Kryoflux operates at a lower level than FC5025. You can set the KF to attempt to read a sector it cannot reads as many times as you like. In the Manuscripts Division @ NYPL our KF is set to attempt twenty reads on each sector before throwing in the towel. Often the KF will read a sector 10+ times then somewhat magically get a good read.
While I haven't gone back and re-imaged any 5.25 disks done on the fc5025, it's in the plan for the collection of floppies we are currently working on.
Don Mennerich
April 6th, 2013, 18:29
April 6th, 2013, 18:56
fzabkar wrote:@Spildit, I don't for one second question your data recovery experience with floppy diskettes. However, I do take issue with your explanation, and I do that as an electrical engineer. I also have some practical hands-on experience with the PS/2 Model 25 (720KB 3.5" FDD) and the PS1. I did once have the complete set of IBM's technical reference manuals for the Model 25, but I can't recall any specification data for its FDD. However, I do still have the IBM PC/AT Technical Reference Manual.
In fact here are the schematics for the original IBM PC/AT HDD/FDD MFM controller:
http://www.users.on.net/~fzabkar/PC-AT/FDC_HDC/
AISI factors that could explain the PS1's slow FDD copy speed would be track-to-track skew and head skew. In the ideal case the maximum copy time at 300 RPM would be ...
80 tracks per side x 2 sides per diskette x 0.2 seconds per revolution = 32 seconds
The IBM PC/AT standard allows for programmable head load/unload times and stepping rates, among other things. If PC DOS or OS/2 were to opt for more conservative values for each of these parameters than does MS-DOS or Windows, then it could result in the target sector passing by the head before it settles on the next track, which in turn would necessitate an additional revolution. This would significantly increase the copy time.
In fact I once played with a DOS utility that enabled the user to tune these FDD settings, including skew.
http://www.qnx.com/developers/docs/qnx_ ... ormat.html
As for RPM, AFAICT the 720KB and 1.44MB 3.5" drives both spun at 300RPM just like regular PC drives.
See http://retrotechnology.com/herbs_stuff/drive.html
The early 1.2MB 5.25" drives were dual speed (360RPM and 300RPM), but the latest ones were 360RPM single speed drives.
The data separator on the PC/AT FDD controller could be configured for 250kbps, 300kbps, or 500kbps data rates. If you were to slow the drive down, then the data separator's PLL wouldn't have enough range to lock onto the bitrate. That is, unless the PS/2 were to use something different.
In fact the following device appears to be able to accommodate all of IBM's standards, including 2.88MB FDDs, so it does appear that the PS/2 was no different in regard to bitrate.
DP8473 Floppy Disk Controller:
http://www.datasheetcatalog.org/datashe ... 009384.PDF
"This controller is a full featured floppy disk controller that is software compatible with the uPD765A but also includes many additional hardware and software enhancements. These enhancements include additional logic specifically required for an IBM PC PC-XT PC-AT or PS/2 design."
"This controller incorporates a precision analog data separator. ... This provides optimal perform-
ance at the standard PC data rates of 250, 300 kb/s and 500 kb/s. It also enables optimum performance at 1 Mb/s."
So AISI the 720KB 3.5" drives would be operating at a bitrate of 250kbps, and the 1.44MB drives would be running at 500kbps. This would make them no different to ordinary FDDs.
As for why the PS1 drives gave you a better recovery rate, I can only imagine that they may have had better alignment tolerances, or perhaps their heads were more sensitive, or maybe the head coils were slightly wider. Whatever the reason, I can't see how it could be related to copy speed.
April 6th, 2013, 19:09
Spildit wrote:Guess that my IBM PS/1 Controller and drive are as good as the Kryoflux lolololol
April 6th, 2013, 19:10
Spildit wrote:What would you suggest for the OP to do in orther to get a better chance to recover the data from the floppy ?
April 7th, 2013, 0:10
Spildit wrote:What would you suggest for the OP to do in orther to get a better chance to recover the data from the floppy ?
April 7th, 2013, 0:36
Spildit wrote:And by the way, if the floppy that you are trying to read is a low density one (only one window to write-protect and no window on the other side of the floppy) modern USB floppy drives will not even read those !!!! (The majority will only read HD floppy)
April 7th, 2013, 19:02
April 7th, 2013, 19:41
April 9th, 2013, 7:14
April 9th, 2013, 7:37
Powered by phpBB © phpBB Group.