Had similar issues with some machines at work--namely, ultra-portable laptops with slow hard drives. When Windows was resumed from standby, the hard drives were taking a while to spin back up--and Windows was trying to access them before they were ready and timing out. After a set number of errors, Windows will set the drives to PIO mode, and no other change I tried could re-enable DMA. I finally found this article that showed me where the in the registry to reset the maximum allowable mode and how to modify the system such that the error counter is reset to 0 after a success. Before, the counter was never decremented or reset...it was always growing.
http://winhlp.com/node/10 Note that you must be running SP2 for the reset-on-success modification to function. I didn't use the VBScript referenced, I manually set the registry values and rebooted the machine. Greg > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:hardware- > [EMAIL PROTECTED] On Behalf Of Bobby Heid > Sent: Tuesday, March 11, 2008 9:26 PM > To: hardware@hardwaregroup.com > Subject: [H] Interrupts issue - Win XP. > > Hey, > > A while back someone gave me an older PC that I set up for my youngest > daughter. It is a PIII 700Mhz machine running XP Pro and 512MB RAM. > > The system started running slowly. I tracked it down to a very high > interrupt processing time (30-90% viewed via process explorer). The > drive > is stuck in one of the PIO modes. I ran the registry mods that I think > I > got from here a long time ago and it did not fix it. I tried various > things > that I found out via Google, but still nothing. I even replaced it > with > another drive thinking that it might be a drive issue. But it is the > same > old thing. > > Anyone know what else I might try? Do you think it might be the EIDE > controller on the MB? I could put a Promise EIDE controller in there, > but > most likely I'd have to format and start over. > > Thanks, > Bobby
