Using a 40-track drive

All questions about how to use KryoFlux go here.
Post Reply
rcade
Posts: 119
Joined: Mon Nov 21, 2011 5:21 pm

Using a 40-track drive

Post by rcade » Sat Feb 16, 2019 12:53 am

I recently discovered one of my rescue 5.25" drives is an old 40-track (41, actually). Thinking I could adjust the DTC parameters to write out disks for old 35/40 track media, I tried to do it, but could not end up with readable disks.

Is it possible to write out an 84-track G64 file on a 40-track drive? -k2 should skip odd tracks, shouldn't it?

I tried:
dtc -k2 -ks2 -e41 -w -fD:\devwork\kryoflux\c64\testgames\BruceLee_s0.g64

First, even though I've limited the process to 41 tracks (I thought) DTC will wipe up to track 41, then jump up to track 80 and make a horrible sound, then step down and write the rest. I does *appear* to only step once and write every other track, but the 1541 cannot read this disk afterward.

I don't think it is handling the track spacing properly, or it's writing to the wrong tracks, or some other issue.

If I add -we0 to avoid the wiping, then it ignores the -k2 (even tracks only) command completely and tries to write the halftracks (which fails on a 40-track drive).

The drive can read/write disks fine in an old PC.

Yes, I do understand Apple and Commodore drives are really 80 track steps but with a wider 40-track head. I don't think that is an issue here...

d:\devwork\kryoflux\dtc>dtc -k2 -ks2 -e41 -w -fD:\devwork\kryoflux\c64\testgames\BruceLee_s0.g64
Image name: D:\devwork\kryoflux\c64\testgames\BruceLee_s0.g64
Image type: G64
Image sides: 1
Image tracks: 84
Analysis time: 0.000 s
Side 0: td: 2, cf: off, data: 14, unformatted: 70, nfr: 0
Filter mode: side -wg: 3, crosstalk -wk: 0[3]
Side mode: side -g: 0, td -ks: 2, flip -wy: 0, flippy -y: 0
Write mode: bias -wb: 1, erase -we: 2
00.0 : Wiping
01.0 : Wiping
02.0 : Wiping
03.0 : Wiping
04.0 : Wiping
05.0 : Wiping
06.0 : Wiping
07.0 : Wiping
08.0 : Wiping
09.0 : Wiping
10.0 : Wiping
11.0 : Wiping
12.0 : Wiping
13.0 : Wiping
14.0 : Wiping
15.0 : Wiping
16.0 : Wiping
17.0 : Wiping
18.0 : Wiping
19.0 : Wiping
20.0 : Wiping
21.0 : Wiping
22.0 : Wiping
23.0 : Wiping
24.0 : Wiping
25.0 : Wiping
26.0 : Wiping
27.0 : Wiping
28.0 : Wiping
29.0 : Wiping
30.0 : Wiping
31.0 : Wiping
32.0 : Wiping
33.0 : Wiping
34.0 : Wiping
35.0 : Wiping
36.0 : Wiping
37.0 : Wiping
38.0 : Wiping
39.0 : Wiping
40.0 : Wiping
41.0 : Wiping
80.0 : Wiping
36.0 : Writing G64, trk: 19.0, CBM DOS
36.0 : Control command rejected by the device
36.0 : Writing G64, trk: 19.0, CBM DOS
36.0 : Verify: OK
34.0 : Writing G64, trk: 18.0, CBM DOS with Datasoft, Weak bits
34.0 : Verify: OK
32.0 : Writing G64, trk: 17.0, CBM DOS
32.0 : Verify: OK
30.0 : Writing G64, trk: 16.0, CBM DOS
30.0 : Verify: OK
28.0 : Writing G64, trk: 15.0, CBM DOS
28.0 : Verify: OK
26.0 : Writing G64, trk: 14.0, CBM DOS
26.0 : Verify: OK
24.0 : Writing G64, trk: 13.0, CBM DOS
24.0 : Verify: OK
22.0 : Writing G64, trk: 12.0, CBM DOS
22.0 : Verify: OK
20.0 : Writing G64, trk: 11.0, CBM DOS
20.0 : Verify: OK
18.0 : Writing G64, trk: 10.0, CBM DOS
18.0 : Verify: OK
16.0 : Writing G64, trk: 09.0, CBM DOS
16.0 : Verify: OK
14.0 : Writing G64, trk: 08.0, CBM DOS
14.0 : Verify: OK
12.0 : Writing G64, trk: 07.0, CBM DOS
12.0 : Verify: OK
10.0 : Writing G64, trk: 06.0, CBM DOS
10.0 : Verify: OK
-
Pete Rittwage
C64 Preservation Project
http://c64preservation.com

Post Reply