[billy]

Originally Posted by IFW

Edited to reflect that this is the right thread to post these questions

Thanks for all your effort and for moving my question where it needed to go.

I think there may very well be an issue with the jumpers or other configuration of the CHINON drives, but I haven't found the solution yet. When I attempt to calibrate a CHINON on the Kryoflux, the drive is at rest and once I send the command to the drive the motor starts to spin and a few more commands are received, but the entire process fails with a 'Control command rejected by the device'

dtc>dtc -l15 -c2

v1.4 Nov 10 2004 14:49:33

000007da: status=0
000007ee: status=0
00000802: reset=0
00000c44: descriptor=C2 DiskSystem/version=1.00/date=Jan 3 2010/time=20:54:07
00000c58: density=0
00000c6c: min_track=0
00000c80: max_track=83
00000c94: motor=1
00000fa5: side=1
00000fb9: track=65535
Control command rejected by the device
CM: maxtrack=0
000010f4: motor=0

Now on to something more dear to my heart.
I was a C-NET and Image sysop for years back in the 80's and 90's. I still have all my originals but some of them are physically damaged. I know the media is tweaked, see here:

What in your opinion is the best mechanism using KryoFlux to extract and keep whatever is left of the bits on whats left of the media?

In the case of my C-NET 64 DS-2 original, if I read the data twice, it comes back with two different .d64's and the files in the image are truncated at different locations. I don't hold KryoFlux responsible, on the contrary, I just want to know how to preserve the most of what I have for future manual retrieval.

7521f03340a09405474957edf317c143 *C-NET64.BBSvDS-2SerialOriginal1xxx.read2_s0.d64
6f1c66034de33d8040b1b32472645414 *C-NET64.BBSvDS-2SerialOriginal1xxx.read2_s1.d64
d5781a1fc156b4d67640db2e7735485a *C-NET64.BBSvDS-2SerialOriginal1xxx_s0.d64
6a3cbbfc70df57dceeb9387c3a09b31c *C-NET64.BBSvDS-2SerialOriginal1xxx_s1.d64

Thanks again for your work, maybe something good will come from these damaged media tests.