5.25 Drives & Greaseweasel - No Track 0

[huwbaldwin]

Summary

When attempting to read a known good IBM 360k DSDD disk in a 5.25 drive I receive "FluxEngine Error: Greaseweasel Error: No Track 0

Reproduction

I have the following set in the GUI:

Format: IBM PC
Variant: 360kB 5.25" 40‑Track 9‑Sector DSDD

Device properties
Device: Greaseweazle GW1374633B... (The correct GW with the drive is question connected)
High Density: no
Drive type: 40 Track Drive
Drive rotational speed: 300rpm (200ms)
Bus interface: Shugart Bus Interface

I am using a Chinon F-502L II series drive and a GW 4.1 on 1.6 Firmware

Observed behavior

The drives spins and attempts to read and then gives the error in question, adjusting the following flags:
decoder.retries=x
drive.revolutions=x
drive.sync_with_index=true|false

has no effect on the issue.

Note that if I run gw.exe read --device=COM4 --drive=B --format ibm.360 --tracks=c=0-39:h=0,1, the disk images perfectly, I have also tried another
Chinon FZ-506 Series drive with a DSHD disk with the same result, albeit adjusted settings for an 80 track drive and ibm1200 disk type.

This same setup has no issues with 3.5 drives of any type and the appropriate configuration.

[davidgiven]

Hello,

Thanks for the bug report --- I'm actually in the process of rewriting absolutely everything due to a whole slew of difficult-to-fix bugs. What platform are you on, and would you like to try a beta version?

[huwbaldwin]

Thanks David,

Currently on Windows, a Beta version would be fine, happy to do some testing and report back.

[davidgiven]

Try this: https://github.com/davidgiven/fluxengine/actions/runs/32673142194/artifacts/9502121422

Disclaimer --- I haven't tried this before on Windows!

[huwbaldwin]

Thanks David,

Same issue with the Beta, drive spins but No Track 0 - is there a way I can get debug output for you at all?

[davidgiven]

That's interesting --- that suggests it's not a simple code bug.

Question: I see the gw command line has --drive=B in it. Are you using a cable with a twist, or a straight cable?

[huwbaldwin]

this particular cable does have a twist at the end but the the shugart connector is before it - there is only a single drive on the bus.

[davidgiven]

Silly question, but... is drive 1 selected in the FluxEngine GUI? (I ask because the old GUI had a bug where the drive select box didn't actually appear, so you would have had to have added drive.drive=1 to the custom config, and you didn't mention it.) (The new GUI has fixed this.)

[huwbaldwin]

Thanks David,

My apologies, we was running the wrong executable (it has been a long week indeed).
Now running the beta i receive the error when attempting a read:

I have the following settings configured:

[davidgiven]

Whoops, that's a bug at my end (the config field should be usb.greaseweazle.port). Will fix. Cheers.

[huwbaldwin]

Thanks David, let me know when you have a new build ready and will test further.

[davidgiven]

Fixed, I hope. Try this: https://github.com/davidgiven/fluxengine/actions/runs/33212279564/artifacts/9702421866

(BTW, you'll probably need to use COM4 as the serial port on Windows.)

[huwbaldwin]

Thanks David,

I now receive the error:

When using either 4 or COM4 in the serial field

[huwbaldwin]

as a side note, if more than 1 GW is connected we receive:

[davidgiven]

Is the Greaseweazle device not appearing in the dropdown where you can select it without having to manually specify the serial port?

[huwbaldwin]

I have the following appear:

Selecting serial port or n/a makes no difference currently.