PunnO)))Feb 27

I have two Greaseweazles, one 4.0, one 4.1. I cannot get either to work.

If I run: gw read --format ibm.1440 test.imd

... the activity LED comes on, and I hear the head seek. The motor doesn't spin. Then I get the error "Command Failed: GetFluxStatus: No Index"

Same results with:

GW 4.0 hardware
GW 4.1 hardware
Sony MPF120-02 FDD
Chinon FX-357 FDD
Power from the GW board
Power from an external supply
Two different floppy cables
Two different floppy disks

Any suggestions for what I might be doing wrong?

Show threadPunnO)))Feb 27
Maybe I got unlucky and both FDDs need +12v? But I'm pretty sure the external power supply I used has those.
Show threadarcadeshopperFeb 27
@ieure is your cable straight through or has a twist?
Show threadPunnO)))Feb 27

@arcadeshopper One has a single pin header connector with a twist, the other has pin and edge connectors on the twisted and untwisted sections. I'm connecting the twisted section (drive A) on the latter cable.

Both drives have their activity LEDs light when I use a gw command, which wouldn't happen if the wrong drive was being addressed. Neither has the drive motor spin up.

Show threadarcadeshopperFeb 27
@ieure The twist moves the drive motor lines on a PC. The 3.5" drives are usually hard jumped to d1 or drive 2 .. the twist on a PC moves them to d0 .. I use a straight cable on my gw
Show threadPunnO)))Feb 28
@arcadeshopper Exact same problem with the drive connected to the straight through connector.
Show threadarcadeshopper
@ieure probably needs 12v
Feb 28 at 2:49amTusky
Show threadPunnO)))Mar 3

@arcadeshopper Rustled up an ATX power supply, jumpered the power switch, tested outputs -- have both 5v and 12v.

The Sony is giving a different issue now and seems completely dead. "Can't seek to track 0" or similar to that.

But the motor on the Chinon spins! These are both older drives (Sony has what looks like a 1991 date code), so probably more likely to need +12v.

Unfortunately, I get the exact same "Command Failed: GetFluxStatus: No Index" error. Tried imaging a random disk; writing an Apple .po disk image; and writing a Kryoflux STREAM image I dumped myself. Same result with all three.