Page 1 of 1

MFM Copy of CP/M DS/DD Floppy on 40T Drive

Posted: Tue Jul 15, 2014 3:20 am
by ldkraemer
I've got a problem when I try copying an MFM Image (.IMG) file of a Ampro (Z80) Little Board CP/M Computer's DS/DD 40 Track Floppy in
a DS/DD 40 Track Floppy Drive, using the Java GUI. I've selected the end track of 39, with Track Distance of 40, and Head 0. I get 20 Tracks
read in, versus the 40 I should have when a proper read is finished. The HEAD is Double Stepping, versus Single Stepping on a 40 Track
Floppy Drive.
kryo1.png
kryo1.png
kryo2.png
kryo2.png
The same problem exists when I try reading with both Heads of a 40 Track Floppy in a 40 Track DS/DD Floppy Drive.
kryo4.png
kryo4.png
I just received the KryoFlux today, and I'm running Linux - Debian 7.x "Wheezy" 64 Bit.
KryoFlux UI v1.7 beta
DTC v2.20

Will you please verify that I have a proper setup for the 40 Track DS/DD Floppy Drive, and that you can duplicate the issue?

Thanks.

Larry

Re: MFM Copy of CP/M DS/DD Floppy on 40T Drive

Posted: Tue Jul 15, 2014 6:34 am
by Feltzkrone
Track distance should be set to 80 in this case (= single stepping) and not 40 (= double stepping). A track distance of 40 is to be used when using a 96 tpi / 80 track drive to read a 48 tpi / 40 track disk and as a side note, there's generally no need to use a 40 track or DD disk drive to be able to read 40 track DD disks. A standard "1.2 MB" 5.25" HD floppy drive would also do.

Apart from the track distance setting a log excerpt would be really helpful, especially for the first few tracks. Even with wrong track distance selected track 00.0 should have had a good read / decoding. If the log can't be used to clearify things (e.g. all tracks classified as unformatted) the next best thing to do is (if you don't mind) dumping to KryoFlux Stream files and attach the first few .raw files for further investigation.

Re: MFM Copy of CP/M DS/DD Floppy on 40T Drive

Posted: Tue Jul 15, 2014 12:36 pm
by ldkraemer
I'm not exactly sure how to capture a "log excerpt" as I don't see any .log type in any menu setting, but I did capture the commands
that scrolled up in my Linux Terminal, where the Java Software was executed. I've also attached some of the first Tracks of a
Type 0 (RAW KryoFlux Stream File) that read the DS/DD 40T Ampro Floppy, in a DS/DD 40T Floppy Drive.
kryo5.png
kryo5.png
Hopefully it will be enough information for you to determine what is going on.

Another question is:
Would a good copy be possible from the Command Line, versus using the GUI?

I've tried reading one last night from Command Line, but deleted all that information so I'd have a fresh
start today with absolutely no confusion. Since I want to be able to electronically reproduce the Floppy
years in the future, and the KryoFlux only supports four (4) type output WRITES to files, I'm assuming
a "IPL" type file or "RAW" Type 0 or 0a files are best for long term storage to reproduce the Floppy's.
Is this correct?

Thanks.

Larry
Ampro40T.zip
Ampro40T.zip
(954.25 KiB) Downloaded 80 times

Re: MFM Copy of CP/M DS/DD Floppy on 40T Drive

Posted: Tue Jul 15, 2014 1:17 pm
by ldkraemer
It looks like there is also a problem when I try to load a saved KryoFlux Stream from the saved subdirectory.

I read all 40 Tracks into a subdirectory named Ampro40T. It has all the files from both heads for 40 Tracks.
(The second time I try to open the Ampro40T folder, I can't see any files to import, unless I use a different subdir name.???????)
I select Stream files, and select the Subdirectory to read in the files. The software tries to read 80 Tracks,
when ONLY 40 Tracks were saved in the subdirectory. Changing the Stream settings to 40 Tracks doesn't
stop the software from trying to read 80 Tracks.
kryo6.png
kryo6.png
This looks to be a problem when I want to write a new Floppy Image with 40 Tracks. (I realize that the
current RAW data is currently of type UNKNOWN. I was just playing with the Java Software.)

Suggestions, other than using a 1.2M 96 TPI (80 Track) Floppy?

Thanks.

Larry

Re: MFM Copy of CP/M DS/DD Floppy on 40T Drive

Posted: Tue Jul 15, 2014 9:45 pm
by Feltzkrone
Change "Image Type" from "FM sector image" to "MFM sector image" and "Track Distance" to "40 Tracks" or tick "Default". It generally should work then. Additionally (if not already done so) you should go to File -> Settings -> Advanced and set "Max Track, Drive 0" to 39 or 40 for your 48 tpi drive.

With the current software it is not possible to write images made from disks with that format back to disk. Writing to disk is considered a bonus and currently only available for IPF (universal), ADF (Amiga) and G64 (C64) files. Please keep the subdirs containing the "KryoFlux stream files" (type 0) as these contain the raw flux data as present on disk and will allow you to create MFM sector images at any point of time and eventually will allow you to make user created IPFs (suitable for writing to disk) and KF stream files also are supported by some 3rd party products like HxC Floppy Emulator software for example. For long term storage please always keep these files, if you discard them you'll lose the chance to start all over again if something went wrong in a conversion process, e.g. a sector image which holds the wrong number of sectors per track or is missing the second side.