Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!spool.mu.edu!munnari.oz.au!cs.mu.OZ.AU!djk
From: djk@cs.mu.OZ.AU (David Keegel)
Newsgroups: comp.os.minix
Subject: Re: Floppy drive not working
Keywords: pc, msdos, minix, disk
Message-ID: <9117614.22163@mulga.cs.mu.OZ.AU>
Date: 25 Jun 91 04:58:58 GMT
Article-I.D.: mulga.9117614.22163
References: <9117523.15390@mulga.cs.mu.OZ.AU> <3302@sun13.scri.fsu.edu>
Distribution: aus
Organization: Computer Science, The University of Melbourne, Australia
Lines: 26

nall@sun8.scri.fsu.edu (John Nall) writes:
]     Minix eats 1.2 meg floppy drives.  I ruined two different
]     drives with it, before I started using Shoelace.  However,
]     there was also a better version of bootblok.s posted to the
]     net which is another way of solving the problem.  

Is there anything I can do about the drive apart from taking it back
to the manufacturer? And if so, what can I tell them is wrong with it?

I now use shoelace (have been for a few weeks), does this mean it
won't (shouldn't) happen again? It does seem a bit slow reading the
drive right at the start, but apart from that (and fd0 motor running)
I'm quite happy to run shoelace, if it means not trashing my drives.

]> ... floppy motor to stay on until I access fd0 (eg: df /dev/fd0).
]>
]     Yep, a "known problem" (undocumented feature).  You can modify
]     the source of shoelace, or just change your /etc/rc file to do a
]     mount and unmount of /dev/fd0, which is a klutz but easy to do.

Thanks. Anyone volunteering a patch for shoelace?
-- 
+--------------------------------------------------------------------------+
| A heathen is one who hasn't seen The Light.   |        David Keegel      |
| A heretic says it is a torch.                 |       djk@cs.mu.OZ.AU    |
+--------------------------------------------------------------------------+