I had a similar error when my wife's computer took a power surge and
cooked the power supply, half a 512 Mb stick of ram (only half? I still
can't figure that one out....), and the MB. The IDE controller was
onboard, and when I replaced the MB, that's the BSOD I got. It is due to
the new IDE controller on the motherboard having a different chipset
than the old one, and 2k cannot access the drive due to not having the
correct driver loaded for it. The solution per Micro$loth support can be
found in the M$ knowledge base article # 287043. Unfortunately, you seem
to have already tried it...
"To resolve this behavior, restart Windows 2000 Setup and then repair
the Windows 2000 installation. To do so, follow these steps:
1. Start your computer by using the Windows 2000 Setup floppy disks
or from the Windows 2000 CD.
Note The computer must be configured to start from the CD drive or
DVD drive. For more information about how to configure the
computer to start from the CD drive or DVD drive, see the
documentation that came with your personal computer or contact the
manufacturer.
2. At the Welcome to Setup screen, press ENTER.
3. When you are prompted to accept the Windows 2000 licensing
agreement, press F8.
4. Select your current installation of Windows 2000 (if it is not
already selected), and then press R.
5. Follow the on-screen instructions to repair your installation of
Windows 2000."
I did the same thing in my situation, and it did not work either. I have
heard from a number of people who have had the same problem that it
rarely, if ever, is a recoverable error. The only solution in my case
was to format and reload 2K. I did not have a backup at the time for her
system, and the drive was formatted NTFS. To recover her data, I put a 6
Gb drive I had sitting around it in her system, installed 2k on that
drive, and booted from it. That gave me access to the drive.
I hope you have better luck than I did with it, but from what you're
saying, you seem to be in the same boat I was.
Thor Gould
William Coulter wrote:
>I know that this is not a full linux question but I have to ask it. If you would, please respond
>to me personally at wrcoulter30@yahoo.com.
>
>Here is my question or problem. I have rebuild my PC. It was a intel p3-500. It is now a athlon
>xp1600. Now when I put the dvd drive, cd-rw, hard drive, etc, in the new PC, the PC can't find
>the hard drive.
>
>I want you know that I have been doing this for a long time. So, I have done all of the basics,
>checking the cables, power cords, BIOS, etc.
>
>Now when I have done this with win 98 or me, I have had no problems. The system boots up and the
>system says, hey I am in a new pc, what changes have you made to me? But this time I am using a
>win 2000 dual booting with red hat linux 8.0. Here is the kicker. When I put the knoppix cd in
>the PC it runs without any problems. In fact, it finds the win2k along with the rh 8.0
>partitions. What do I have to do to make the PC boot with the hard drive. The error I get is "no
>bootable dirve. boot failure." I have even used the win2k boot disks and use the repair option.
>I know that the new mother board can acccess the hard drive as ata100 and the old mother board was
>ata66 or 33. The only other thing, is that I am using the wrong cable, but I have never seen a
>hard drive ack this way before from that.
>
>William
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! SiteBuilder - Free, easy-to-use web site design software
>http://sitebuilder.yahoo.com
>-----------------------------------------------------------------------
>This list is provided as an unmoderated internet service by Networked
>Knowledge Systems (NKS). Views and opinions expressed in messages
>posted are those of the author and do not necessarily reflect the
>official policy or position of NKS or any of its employees.
>
>
>
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:30:33 EDT