Is there floppy in FDD

[Colonel Kernel]

A policy that fails pitifully the very moment the first time MacOS runs on a hardware that doesn't support this OS-driven eject - dooming Apple to provide expensive Apple-only floppy drives till the end of (floppy) days or break their metaphor.

Is it doom, or an extra source of revenue? ;D

[Pype.Clicker]

but it already fails now with an USB stick,
for example. I can just yank that out whenever I want.

sure! still you're informed of the stick's removal by the USB bus. I don't say "there will never be user-driven hard removal of media", just that "why bother when the hardware is *soo* poor". But i have to admit i never found FDD programming interesting anyway. Dealing with floppies is solely GRUB's concern as far as i'm concerned

[crackers]

Lately I've decided to implement correct behaviour of my OS when there is no floppy and I have new question ;D. Normally reading data looks like:

send read/write command
wait for interrupt
read results

but when there is no floppy everything stops because I'm not getting any interrupt, so I add a counter

Code: Select all

while(interrupt == false)
{
  floppy_delay();
  if (counter == 0)
    return error;
  counter = counter - 1;
}

and it's working ok, but only once. When I try to send any new command I'm getting error - something like "can't execute new command, old command pending". My question is, is there any other way than resetting FDC to remove old command ?

[paulbarker]

I think this has to do with the delay needed for working with a floppy disk. From memory, commands should be at least 50ms apart. If I remember correctly again, this little piece of info is not easily found and is probably mentioned on less than 1% of all websites dealing with floppy disk documents.

I could be completely wrong, I gave up on FD drivers years ago.