cptaylor Posted February 20, 2004 Report Share Posted February 20, 2004 Here's the somewhat long story... On my old drive I had MD9.2 and Win98 dual booting using Lilo. I began having frequent crashes in Win98 and scandisk was finding bad sectors occasionally. Finally Linux would hang when trying to boot repeating the error "hda: lost interupt". So I decided to get a new drive, make it the primary master and install WinXP while I was at it. The install went fine but XP does not recognize that there is a second drive. It should be able to see the Win98 partition. I thought the drive may have finally died but I switched my BIOS to boot to the old drive (primary slave). Lilo came up and I was still able to load Win98 (which of course cannot see the NTFS partition). When I run the hardware intallation utility in XP I get a quick message down by the clock that says XP found new hardware but there was a problem. I checked the system event viewer and found the following errors relating to the old drive: The device, \Device\Ide\IdePort0, did not respond within the timeout period. The device 'WDC AC313600D' (IDE\DiskWDC_AC313600D___________________________J7JOA30K\4457572d36543137343035393835203320202020) disappeared from the system without first being prepared for removal. It seems that XP is finding the drive but is having some kind of problem with it. If Win98 can still boot on the drive I would think it is still sound enough that XP should be able to access it. I know XP isn't fond of Linux but having Lilo in the boot sector shouldn't prevent access to the Win98 partition should it? Does any one have any thoughts? In the short term I would like to be able to copy my files from the old drive but I think it would also be useful as extra storage and for transferring files between XP and Linux. Putting on MD10.0 will be my next task. :) It'll likely be ready by the time I finish setting up XP. Thanks, Chris Quote Link to comment Share on other sites More sharing options...
cptaylor Posted February 20, 2004 Author Report Share Posted February 20, 2004 I just found a third error log: The driver detected a controller error on \Device\Ide\IdePort0. -Chris Quote Link to comment Share on other sites More sharing options...
Ixthusdan Posted February 20, 2004 Report Share Posted February 20, 2004 Two things about your drive and windex. One, the drive is apparently going to die soon. The errors are hardware type errors, so save your data if it is important. Two, windex has all sorts of issues cooperating with anything, including old versions of itself! If the drive were good, xp would say something to you about a corrupt drive or a corrupt sector. That's what it thinks of anything other than ms file systems. Don't allow xp to set up your entire drive. Dividing it out in the future will certainly cause xp to "malfunction." Give xp a specific partition, and you will be able to get it to "cooperate" in the future. Quote Link to comment Share on other sites More sharing options...
Pzatch Posted February 21, 2004 Report Share Posted February 21, 2004 Have you tried switching the drives ide ports? Maybe its some type of ide problem and not the drive. Just a shot in the dark. Quote Link to comment Share on other sites More sharing options...
arthurking Posted February 22, 2004 Report Share Posted February 22, 2004 Following on from what pzatch said, You made the old drive pri/slave, but did you remember to switch the jumper to slave. I spent 2 hours with an old drive just recently, about to bin it because of this (my pathetic excuse was "it was getting late") DOH! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.