Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!metro!dmssyd.syd.dms.CSIRO.AU!ditsydh.syd.dit.CSIRO.AU!evans
From: evans@syd.dit.CSIRO.AU (Bruce.Evans)
Newsgroups: comp.os.minix
Subject: Re: Floppy drive not working
Keywords: pc, msdos, minix, disk
Message-ID: <1991Jun30.060057.14756@syd.dit.CSIRO.AU>
Date: 30 Jun 91 06:00:57 GMT
References: <9117523.15390@mulga.cs.mu.OZ.AU> <3302@sun13.scri.fsu.edu> <9117614.22163@mulga.cs.mu.OZ.AU>
Organization: CSIRO Division of Info Tech, Sydney, Australia
Lines: 21

In article <9117614.22163@mulga.cs.mu.OZ.AU> djk@cs.mu.OZ.AU (David Keegel) writes:
>nall@sun8.scri.fsu.edu (John Nall) writes:
>]> ... 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?

Other workarounds: don't boot from a floppy (best); pause in shoelace to
give the BIOS time to turn off the motor.

Fix in shoelace: copy the 3 lines in bootblok.s where it says "kill the motor"
to somewhere after shoelace has finished with the floppy.

Fix in driver: add out_byte(DOR, ENABLE_INT); /* motor bits off */ somewhere
in the initialization. Of course this should have been there from the
beginning.
-- 
Bruce Evans		evans@syd.dit.csiro.au