windows xp pro sp 1
AMD 2600 semperon
g4 5500 video card
80 gig hdd
20 gig hdd
runs @ ABOUT 102 degrees
i got unmountable boot volume
then tried to run the xp repair
got ntldr is missing
replaced the ntldr and ntdetect.exe
then got vgaoem.fon error when trying to load windows and get to the repair center
i dont know what to do now
still getting UNMOUNTABLE BOOT VOLUME when trying to get into windows
1.The file system is damaged and cannot be mounted.
2.You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable.
3.The basic input/output system (BIOS) settings are configured to force the faster UDMA modes.
Back to the top
If it be the connector cable problem then replace the 40-wire cable with an 80-wire UDMA cable.
If it's a BIOS settings problem then load the 'Fail-Safe' default settings, and then reactivate the most frequently used options such as USB Support.
If it's a damaged file system case then:-
1.Insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.
Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted.
2.When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
3.If you have a dual-boot or multiple-boot computer, select the installation that you must access from the Recovery Console.
4.When you are prompted, type the Administrator password. If the administrator password is blank, just press ENTER.
5.At the command prompt, type chkdsk /r , and then press ENTER.
6.At the command prompt, type exit , and then press ENTER to restart your computer.
This takes a bit longer, but the system should boot back into Windows.
Back to the top
"STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME" Error Message When You Restart Your Computer or Upgrade to Windows XPhttp://support.micro...om/?kbid=297185
Description of the Windows XP Recovery Consolehttp://support.micro...b;en-us;Q314058
If the above process fails to restore the system then in the number#5 step use fixboot command instead of the chkdsk /r command.