Drives confirmed working with KryoFlux

All questions about how to use KryoFlux go here.
Lizard
Posts: 5
Joined: Sun Nov 07, 2010 9:57 pm

Re: Drives confirmed working with KryoFlux

Post by Lizard »

3,5"
Mitsumi , D359T5 works(maxtrack: 83), however Mitsumi , D359T6 doesn't work here.
User avatar
mr.vince
Posts: 2142
Joined: Tue Oct 05, 2010 5:48 pm

Re: Drives confirmed working with KryoFlux

Post by mr.vince »

Lizard, can you be more precise? Which error? Please turn on full logging with -l15...
Franky
Posts: 5
Joined: Wed Nov 03, 2010 7:39 pm

Re: Drives confirmed working with KryoFlux

Post by Franky »

Here are my drives :

3,5" : Samsung SFD-321B max tracks 83
Tested with Amiga DD and Amiga HD

5 1/4" : Teac FD-55GFR max tracks 83
Tested with Amiga DD and C64

After dumped I loaded the images with an Emulator and check there the content for errors.

Is there any feasible and reliable way of proofing that a dump is a good one (I mean additional to the "Hope & Belief" method :) )?
Lizard
Posts: 5
Joined: Sun Nov 07, 2010 9:57 pm

Re: Drives confirmed working with KryoFlux

Post by Lizard »

mr.vince wrote:Lizard, can you be more precise? Which error? Please turn on full logging with -l15...

Code: Select all

D:\kryoflux_1.0b7r2\dtc>dtc -c2 -l15
0000c8bb: status=0
0000c8cf: status=0
0000c8e3: reset=0
0000cd25: descriptor=C2 DiskSystem/version=1.00/date=Oct 12 2010/time=20:06:17
0000cd39: device=0
0000cd4d: density=0
0000cd61: min_track=0
0000cd75: max_track=83
0000cd89: motor=1
0000d09a: side=1
0000d0ae: track=65535
Control command rejected by the device
CM: maxtrack=0
0000d1fd: motor=0
This is the output I get with the Mitsumi D359T6
User avatar
mr.vince
Posts: 2142
Joined: Tue Oct 05, 2010 5:48 pm

Re: Drives confirmed working with KryoFlux

Post by mr.vince »

Ok, could be this is a problem with the drive's stepping. DTC currently goes strict after specs, so any drive outside specs will trigger this problem. I've seen other people dump successfuly with their drives, although this error was coming up. We will look into timing.

What does the drive do when you try to actually dump a disk?
User avatar
IFW
Posts: 3080
Joined: Mon Nov 08, 2010 2:42 pm

Re: Drives confirmed working with KryoFlux

Post by IFW »

I'd recommend using drives going to 83 (ie supporting 84 tracks; 0-83) for preservation/stream files.
For normal user written disks it does not matter much usually.
User avatar
mr.vince
Posts: 2142
Joined: Tue Oct 05, 2010 5:48 pm

Re: Drives confirmed working with KryoFlux

Post by mr.vince »

Franky wrote:Is there any feasible and reliable way of proofing that a dump is a good one (I mean additional to the "Hope & Belief" method :) )?
Yes, just by make a sector dump, e.g. -i5 AmigaDOS or -i4 for Generic MFM, you are checking the format. Errors will be reported.

Pure STREAM files can't be checked (except by us ATM), but you can additonally decode to some sector format to make sure the RAW data is ok.
User avatar
IFW
Posts: 3080
Joined: Mon Nov 08, 2010 2:42 pm

Re: Drives confirmed working with KryoFlux

Post by IFW »

Don't forget you can dump to as many formats as you like at the same time - the disk will only ever be read once.
You can change the output from the tool and restrict it to format errors only by setting the output level, e.g. -l8 will only ever display format decoding errors - useful for sector dumps when you are normally only interested in those errors anyway.
User avatar
mr.vince
Posts: 2142
Joined: Tue Oct 05, 2010 5:48 pm

Re: Drives confirmed working with KryoFlux

Post by mr.vince »

Lizard wrote:

Code: Select all

0000d0ae: track=65535
Control command rejected by the device
CM: maxtrack=0
0000d1fd: motor=0
This is the output I get with the Mitsumi D359T6
Please try: viewtopic.php?f=3&t=29
Lizard
Posts: 5
Joined: Sun Nov 07, 2010 9:57 pm

Re: Drives confirmed working with KryoFlux

Post by Lizard »

mr.vince wrote:
Lizard wrote:

Code: Select all

0000d0ae: track=65535
Control command rejected by the device
CM: maxtrack=0
0000d1fd: motor=0
This is the output I get with the Mitsumi D359T6
Please try: viewtopic.php?f=3&t=29
With the normal firmware dumping does not work.

When i try the slow firmware I do get the following output:

Code: Select all

D:\kryoflux_1.0b7r2\dtc>dtc -c2 -l5
0001dacf: status=0
0001dae3: reset=0
0001ded2: descriptor=KryoFlux DiskSystem/version=1.00/date=Nov  9 2010/time=20:17:35
0001defa: device=0
0001df0e: density=0
0001df22: min_track=0
0001df36: max_track=83
0001df4a: motor=1
0001e298: side=1
0001e2ac: track=0
0001e2c0: motor=1
0001e2d4: side=1
0001e2e8: track=0
0001e2fc: motor=1
0001e310: side=1
0001e324: track=80
0001e726: motor=1
0001e73a: side=1
0001e74e: track=0
0001eb50: motor=1
0001eb64: side=1
0001eb78: track=0
0001eb8c: motor=1
0001eba0: side=1
0001ebb4: track=81
0001efc2: motor=1
0001efd6: side=1
0001efea: track=0
0001f3f8: motor=1
0001f40c: side=1
0001f420: track=0
0001f434: motor=1
0001f448: side=1
0001f45c: track=82
0001f877: motor=1
0001f88b: side=1
0001f89f: track=0
0001fcba: motor=1
0001fcce: side=1
0001fce2: track=0
0001fcf6: motor=1
0001fd0a: side=1
0001fd1e: track=83
00020145: motor=1
00020159: side=1
0002016d: track=65535
00020588: motor=1
0002059c: side=1
000205b0: track=0
CM: maxtrack=82
0002060d: motor=0
But this only worked once. Now I get the Control command rejected by device again.

Also when I try to dump a disk it's not successful:

Code: Select all

D:\kryoflux_1.0b7r2\dtc>dtc -fimage.adf -i5
KryoFlux DiskTool Console, v1.00 beta 7, uiv.1, Oct 12 2010
(c) 2009-2010 Istvan Fabian, Softpres, www.softpres.org
Licensed for private, non-commercial use only.

00.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.127
00.0    : No flux reversal found
00.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.129
00.0    : No flux reversal found
00.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.111
00.0    : No flux reversal found
00.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.132
00.0    : No flux reversal found
00.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.104
00.0    : No flux reversal found
00.0    : Read operation failed
00.1    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.117
00.1    : No flux reversal found
00.1    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.126
00.1    : No flux reversal found
00.1    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.128
00.1    : No flux reversal found
00.1    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.130
00.1    : No flux reversal found
00.1    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.135
00.1    : No flux reversal found
00.1    : Read operation failed
01.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.117
01.0    : No flux reversal found
01.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.106
01.0    : No flux reversal found
01.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.118
01.0    : No flux reversal found
01.0    : frev: 0, drift: 0.000 us, tfer: 0 B/s, rpm: 300.126
01.0    : No flux reversal found
^C
This happens with the normal and the slow firmware.
Post Reply