NTLDR:FATAL ERROR 57344 READING BOOT.INI

He did it, thanks Daavee.

Groovy!

The current stage is now at only 13% complete with the computer running 24/7.

I have seen check disk take days to complete, but at this point a re-install is the best bet since, as you previously stated, we're not dealing with your primary computer. I am of the opinion we may have had better results if check disk were being performed using Recovery Console. However, the point is now moot in this instance, but may be of use to you if future issues arise. I will add that you need to make sure the disc you have was intended for the computer in question.

If and when I do the reinstall, what are the consequences such as losing everything if there was no backup.

As noted by Liz, a repair install should allow you to retain your personal files. However, while a repair install will replace all Windows system files, is does nothing for the hard drive which very well may be the culprit. That is why I recommended you use KillDisk or Dban to low level format the hard drive prior to re-installing. Low level is simply a more intense formatting process of the drive in which errors in sectors are more likely to be repaired.

As for using the current hard drive to re-install Windows on, I personally wouldn't go as far as to tell you not to use the drive yet. I am of the opinion there is nothing mechanically wrong with the drive other than a few bad sectors which formatting should resolve. In fact, you may want to consider running the program twice.

If it were my computer I would first get my personal files. I would use Ubuntu boot disc to do so. The reason I recommend Ubuntu is that it is capable of recognizing hard drives in situations where a Windows based virtual environment software (Hirens) cannot detect the drive. I really don't believe you would have an issue with the drive being recognized, but if you are going to burn and boot from a disc go ahead and use one that is more apt to do the job the first time. You can follow the instructions on one of my websites HERE.

After my files had been retrieved and backed up I would next test the hard drive to determine whether or not it could be used or need replacing. Should you choose to go this route I will instruct you when the time comes.

You are still a ways from completing this project. However, Liz and I both check the forum regularly for new post to the topics we have engaged in. In other words, the faster you work the faster you will be up and running again. However, you don't want to have to do this again come next month so, let's do it right the first time. :-)

[this post was last edited 0530 GMT, Nov. 25, 2012]

On p. 2 of this thread, Tech-Geek made an excellent point:

> It is unclear from your post whether you booted from the disc or allowed check disk to run as a result of receiving a prompt when trying to load Windows.

I would imagine you did NOT successfully boot off your CD!

Whether you want to run Recovery Console or perform a Clean Install of Windows XP, this is a skill you MUST learn!!!!!

[ Instructions for accessing the Dell's F12 menu have been removed! ]

You need to tell us the make, model, and model number of your PC so we can better assist you with this!

So, please do the following:

Start | Run

Type:

msinfo32

Click OK.

Then when you see the System Information window, click anywhere on the right-hand side. Then press Ctrl+A (selects all). Then Ctrl+C (copies what you just selected to the clipboard). Then when you make your next post to this forum, as you are typing, Ctrl+V (pastes what you copied to the clipboard into your post here). It will look something like this:

OS Name Microsoft Windows XP Home Edition

Version 5.1.2600 Service Pack 3 Build 2600

OS Manufacturer Microsoft Corporation

System Name [ Y O U    CAN     DELETE    THIS    INFO    IF     YOU     WISH!]

System Manufacturer .   <--- this is important to know!

System Model .   <--- this is important to know!

System Type X86-based PC

Processor x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3064 Mhz

BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 1/10/2008

SMBIOS Version 2.5

Windows Directory C:\WINDOWS

System Directory C:\WINDOWS\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"

User Name [ Y O U    CAN     DELETE    THIS    INFO    IF     YOU     WISH!]

Time Zone Eastern Daylight Time

Total Physical Memory 2,048.00 MB

Available Physical Memory 1.32 GB

Total Virtual Memory 2.00 GB

Available Virtual Memory 1.96 GB

Page File Space 3.85 GB

Page File C:\pagefile.sys

Again, once we know what you have, we can better assist you with booting off the CD (it will likely involve entering the BIOS and altering your boot order setting). Once this is done, you should see a screen that looks like this:

http://1.bp.blogspot.com/-zY4M6laSy6k/UFtKTeodwiI/AAAAAAAAABM/DcIMMPgp8rw/s400/xp.jpg

Make sure you press any of your keys! If it doesn't work, that means there is an issue with your keyboard (or BIOS setting for your keyboard).

Is your keyboard wireless or wired? If wired, is it USB or PS/2?

As long as you can boot off your CD, you WILL be able to run Recovery Console, which can be VERY useful. And I'll bet running chkdksk /r FROM YOUR CD'S RECOVERY CONSOLE will be much quicker!!!

I would like to add that Elizabeth23 and Tech-Geek are quite good. Follow their advice, too! :-)

Thanks for the compliment. :-) and your post is very useful information. My primary question at this point is whether the OP's disc or recovery or installation. If they are recovery disc the hard drive very well may contain data on a hidden partition which is needed to perform the recovery. Perhaps the OP can look at the disc and let us know. If they are recovery they will be plainly labeled as such.

On another note, something you may be interested in knowing is that MBAM has released a dedicated rootkit scanner entitled Malwarebytes Anti-Rootkit. Be sure to read the instructions that come within the download. The download contains a file entitled fixdamage.exe which is separate from the scanner file. It will repair certain system services and settings which are frequently broken by certain rootkits such as the firewall, security center and others affected by malware. It is still in beta, but seems very promising.