convert 360ko dump with a 360ko drive
Re: convert 360ko dump with a 360ko drive
It's "by design" because the software was never meant to be used with a 40 track drive.
Re: convert 360ko dump with a 360ko drive
I would also recommend the flux/secor decoding tools that come with the PCE emulator. Totally command line based, and rather complex, but they can be quite powerful when needed.
-
- Posts: 372
- Joined: Fri Nov 08, 2013 10:48 pm
Re: convert 360ko dump with a 360ko drive
Because of another issue I just did study the manual again and found that the -e parameter sets the last track for the reading but -oe sets the last track for the output!
So -oe39 should do the trick....
David
So -oe39 should do the trick....
David
-
- Posts: 15
- Joined: Sun Dec 11, 2011 10:07 pm
Re: convert 360ko dump with a 360ko drive
it doesn't seem to work ;-(
-
- Posts: 123
- Joined: Fri Nov 12, 2010 8:08 pm
Re: convert 360ko dump with a 360ko drive
for me, a 360kb/40 tracks dump is made with a 300RPM drive, a 12xxkb/84 tracks dump is made with a 360RPM.
So what are we really talking about ?
It's impossible to ask to a 360RPM drive to write at 300RPM, the same way you can't write back a dump made at 300 RPM on a 360RPM drive. The drives speed is fixed.
So what are we really talking about ?
It's impossible to ask to a 360RPM drive to write at 300RPM, the same way you can't write back a dump made at 300 RPM on a 360RPM drive. The drives speed is fixed.
Re: convert 360ko dump with a 360ko drive
Actually, there are some 360RPM 5.25" drives that will slow down to 300RPM depending on the density line. Although that is not the way the standard IBM PC does things.
Also, the Kryoflux is good about re-sampling the raw stream when writing to match whatever speed the drive is spinning at.
For example, I can take a stream file made in a 360k 300rpm drive, rename the raw files to track 0, 2, 4, 6, etc, and write the tracks in a 1.2mb 360rpm drive that will read back fine (only in 1.2mb drive unless the disk was degaussed first). Or conversely, I can take an image of a 360k disk made in a 1.2mb 360RPM drive, remove the odd tracks and rename the raw files to track 0, 1, 2, 3, 4, etc, and the Kryoflux will write those fine in a genuine 360k 300RPM drive.
That said, I also normally dump 360k disks using a genuine 360k floppy drive.
Also, the Kryoflux is good about re-sampling the raw stream when writing to match whatever speed the drive is spinning at.
For example, I can take a stream file made in a 360k 300rpm drive, rename the raw files to track 0, 2, 4, 6, etc, and write the tracks in a 1.2mb 360rpm drive that will read back fine (only in 1.2mb drive unless the disk was degaussed first). Or conversely, I can take an image of a 360k disk made in a 1.2mb 360RPM drive, remove the odd tracks and rename the raw files to track 0, 1, 2, 3, 4, etc, and the Kryoflux will write those fine in a genuine 360k 300RPM drive.
That said, I also normally dump 360k disks using a genuine 360k floppy drive.
Re: convert 360ko dump with a 360ko drive
Brighcaster is correct, the output image parameters, such as -oe are there to control the content of the output file if it should be different from the default settings. e.g. it is possible to change track order, or limit the output file to only to specific tracks.
In this case you should use -oe, but keep in mind since you can have multiple output images at the same time -oe39 is an image specific parameter and must be specified alongside the other parameters of the desired output file.
In this case you should use -oe, but keep in mind since you can have multiple output images at the same time -oe39 is an image specific parameter and must be specified alongside the other parameters of the desired output file.