> Great news. What did you change to get it working?
First I had a pin bowed (not broken... puff puff), then the connection was hooked the wrong way, I chonged one part, then the other one, then both, then I came finally with the right system... The pin 0 on both the mb and the floppy drive are difficult to spot. You told me it was where the power lead came, but it was the other way...
If it says it is a 720 kB disk, then it could only read it at the data rate for a 720 kB disk, and it must be formatted that way.
I don't know what AROS does to squash more data onto a floppy. You can sometimes step the head past the 80-cylinder limit and squash more cylinders in that way, but that won't work on all drives and the VIA SB doesn't like it.
Alternatively, you could possibly increase the data rate slightly and/or reduce the sector spacing on each track, but the VIA SB won't allow that either.
Can't remember what happens with the DD/HD hole. IIRC there is no indication from the VIA SB whether the hole is open or covered. I'll have a look at the code again (it's a year since I've been in there).
Please don't tell people to use "Diskchange". It does not tell the driver anything, it only tells the filesystems and they can't tell the driver that a new disk might be there.
To get the driver to check the disk formatting, you must use the FDTool utility, either in immediate mode or auto.
TD_EJECT is not supported by the floppy driver. The internal "identify disk" function determines if a disk is present, then reads it in HD and DD format until it gets an error-free result. It then calls all connected filesystems if there is any change.
The DiskChange command does not issue any requests to the driver, only to the filesystems, so the driver is not told that a disk has been changed.