Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!control!dixon From: dixon@control.steinmetz (walt dixon) Newsgroups: comp.sys.ibm.pc Subject: Re: comp.sys.ibm.pc Keywords: NEC Multispeed, Microsoft Word 4.0, Microsoft Mouse Message-ID: <11512@steinmetz.ge.com> Date: 13 Jul 88 13:34:45 GMT References: <2041@uhccux.uhcc.hawaii.edu> Sender: news@steinmetz.ge.com Reply-To: dixon@control.steinmetz.ge.com (walt dixon) Organization: General Electric CRD, Schenectady, NY Lines: 11 Typically, BIOS will not turn the disk motors off right away. Once the motors come up to speed, BIOS leaves them running for a couple of seconds. BIOS relies on the timer (int 8h on the pc) to measure this interval. Possibly the mouse driver is messing with the timer interrupt. Look at the current time. Does it change? The BIOS time of day routine runs off the same interrupt (at least on the pc). If you're really fealing adventureous, use debug to check the timer ISR after you load the mouse driver (d 0:20 l 4 ==> segment:offset of timer isr). Does it still point to ROM? If not, try disassembling it. It should be fairly short. Does it do a far jump or call to ROM?