Re: I cannot get back into windows xp. Help!!!

Hello. I have a SERIOUS issue that I PRAY AND HOPE someone can HELP ME, PLEASE!!!

I am going to cut to the chase and tell you in detail what is happening now and not what lead up to this issue now. I am not looking for a reason (so I felt out the details on how and what lead up to this issue), I am looking for a way out of this to get my system back up and working again. I would like a reason, but I will consider that a separate thread sometime.

When I boot/start into my Windows XP Media Center Edition 2005 with SP3, I get a message long before the WIndows XP splash screen is visible. At normal startup, I get a message that states,

BOOTMGR is missing
Press Ctrl+Alt+Del to restart


I have installed some time ago Windows Recovery Console as a separate installation of Windows that used to show prior to the Windows XP splash screen appearing. Now, I do not get that option or any options. Actually, I used to get a choice between Windows Recovery Console and Windows XP prior to Windows XP starting. By default, the Windows XP was always highlighted to automatically and normally startup Windows XP. Now, after my BIOS finishes loading I get that message I just stated above since this issue started.

***

I DO have the Windows XP CD-ROM. Now, I set the BIOS to boot from the CD-ROM to run the CD-ROM at boot and I press any key to start Windows XP Setup. After a minute or two of copying the drivers, I get to the options menu in Windows Setup. All I have for options is:

1. To setup Windows XP...
2. To create a partition...
3. To delete a selected partition...

I do not have any Windows Recovery (Console) options here.

Am I missing something on how to get to Windows Recovery Console by chance?

***

I have made copies of MS-DOS Start Disks (6 of them on floppy disks). I set BIOS to start with them and inserted disk number 1. Well, after the BIOS splash screen has stopped loading I get this message:

Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file.

So there you have it. Is there any hopes for me to get back into my Windows XP from where I stand now?

I serious feel I need to get into the Windows Recovery Console to do some system serious repairs with my CD-ROM. Any way I can from where I stand or not?

Any suggestions are HIGHLY asked at this time.

Please provide suggestions, facts, or any advice. Please let me know where I stand from your viewpoint.

Thank you!

 

How To Repair or Replace Boot.ini - hal.dll in Windows XP



The boot.ini file is a hidden file that is used to identify in what folder on which partition and on which hard drive Windows XP is located. Boot.ini can become damaged, corrupted or deleted for a number of reasons and is usually brought to your attention by an error message.

Follow these easy steps to repair the damaged/corrupted boot.ini file or replace it if it has been deleted.
Difficulty: Easy
Time Required: Repairing or replacing the boot.ini file usually takes less than 10 minutes
Here's How:

1. Enter Windows XP Recovery Console. The Recovery Console is an advanced diagnostic mode of Windows XP with special tools that will allow you to restore the boot.ini file.

# Boot From the Windows XP CD
# Allow Windows XP to Begin the Setup Process
# Press R to Enter Recovery Console
# Choose the Windows Installation
# Enter the Administrator Password



2. When you reach the command prompt (detailed above), type the following command and then press Enter.

bootcfg /rebuild

3. The bootcfg utility will scan your hard drives for any Windows XP installations and then display the results. Follow the remaining steps to add your Windows XP installation to the boot.ini file.

4. The first prompt asks Add installation to boot list? (Yes/No/All).

Type Y in response to this question and press Enter.

5. The next prompt asks you to Enter Load Identifier:.

This is the name of the operating system. For example, type Windows XP Professional or Windows XP Home Edition and press Enter.

6. The final prompt asks you to Enter OS Load options:.

Type /Fastdetect here and press Enter.

7. Take out the Windows XP CD, type exit and then press Enter to restart your PC.

Assuming that a missing or corrupt boot.ini file was your only issue, Windows XP should now start normally.

Or at step 2, type

fixboot

And allow that procedure to complete, remove CD, reboot.

Or,



expand d:\i386\hal.dl_ c:\windows\system32\hal.dll

Using the expand command as shown above, d represents the drive letter assigned to the CD drive that your Windows XP CD is currently in. While this is most often d, your system could assign a different letter. Also, c:\windows represents the drive and folder that Windows XP is currently installed on. Again, this is most often the case but your system could be different.


If you're prompted to overwrite the file, press Y.


Take out the Windows XP CD, type exit and then press Enter to restart your PC.

 

Hello. Thanks for the reply.

Unfortunately, "MY" Windows XP CD-ROM does NOT have the Windows Recovery Console option. Hmmm... Reason?

Once I click any key to run the CD-ROM, I get the "Windows Setup" at top of the blue screen, and the drivers start to run immediately. I have done some online checking about the Windows Recovery Console and found it should appear right after tapping a key to start the CD-ROM and it gives you a list of 3 options before the drivers run. I do not have that. I do not know why???

Any other solutions to get to the Windows Recovery Console?
Any other solutions period?

Please reply.

Thanks!

 

Is this the original OEM XP CD? Or a copy burned by someone as backup?

The option to repair should appear after you choose to install XP.

 

Hi

To clarify what cipher said...

You must choose the Setup XP (install) option, and then (I believe) press R for recovery options after the install menu has loaded.

 

Thanks, mate, I could have been a little clearer on that...

 

Hello all.

Time to update you on what I have done and I have done a lot to date.

First that issue I was having by not getting the Windows Recovery Console with my Windows XP CD-ROM. Well, I found that Windows Recovery Console is sort of excluded directly with OEM CD-ROMs versions of Windows XP. What I mean is that normally when you tap any key to run the CD-ROM, you will get that first setup screen called "Windows Setup", and you have 3 options in order to pick from. One of them is the Windows Recovery Console that I think says to press the R key. Now, with OEM versions, they have removed this initial setup screen and it goes directly to copying all those drivers first. Retail versions have this first 3 options screen available that one of them offers the Windows Recovery Console. Therefore, PER MICROSOFT, there is no way to enter the Windows Recovery Console for an OEM XP system. Remember I said 'sort of excluded'. There is a way that MICROSOFT is NOT TELLING YOU! YOU CAN get to it: After you tap a key to get the CD-ROM running, immediately start tapping the F10 key. Yes, you have to do a lot of tapping while the drivers are copying. At the end of the drivers copying, you will go to the Windows Recovery Console. Thank God! Windows XP OEM users can get there!!! Why is Microsoft being that way with OEM Windows XP users? Micorsoft is being rotten here and hiding this option!!! Why? A guess: Have to call your OEM builder for help and take your computer to them to fix your issues you are experiencing. Reason: So OEM builders can make money on you on something that you could possibly fix on your own if you had access to the Windows Recovery Console? Regardless, there IS a way! ..and yet after all of this: I have read that "SOME" Windows XP OEMS are missing this inital Windows Setup screen and others may have it. Hmmm...

Anyways I arrived at the Windows Recovery Console.I performed your steps with the booting issue. I selected my C drive: C:\WINDOWS . I typed: bootcfg /rebuild . Well, after a couple of minutes, I get this error:

Error: Failed to successfully scan disks for Windows installations. This error may be caused by a corrupt file system, which would prevent Bootcfg from successfully scanning. Use chkdsk to detect any disk errors. Note: This operation must complete successfully in order for the /add or/rebuild command to be utilized.

Okay, this makes sense to me. I know there is issues with folders and files and I am sure there is some corruption on this disk or C drive, so I decide to do just that, run chkdsk /r to fix and repair my issue. It took over 2 hours to run. It was very slow between 50 and 55 percent for some time. Finally, I get though that. I get a message at the end of the operating stating, "CHKDSK found and fixed one or more errors on the volume." GOOD I say!

So I go again and do another bootcfg /rebuild command again. Again, after a few minutes, I get the same error message again like above. Now, I am a little worried. What is still wrong with my C drive, what kind of errors this time?

I go ahead and run another chkdsk /r again. After almost 2 hours, I get this message, "CHKDSK has finished checking the volume." Well, it sounds this time I didn't find any issues with the C drive. GOOD!!!

So again I do another bootcfg /rebuild. Again, I get the same error message as above. What is going on?!?!?!? The C drive really has some issues.

So just to see if my system will boot normally, which i doubt, but what the heck, I give it a try anyways.
I get the Windows Startup Options screen that I was not getting before. Hmmm... ...some progress. Windows XP is selected by default and as leaves the Windows Startup Options screen, I get the message:

Windows could not start because the following fole is missing or corrupt
\WINDOWS\SYSTEM32\CONFIG\SYSTEM.

So, I have a choice... ...I can either try further with some guided help and try to overcome this... ...which at this point I feel I am stuck for good and require a clean install. ...or just go to Windows 7 and use that one now... ...let Windows XP be done for good.

How it happened:
When I think about it, I cann't believe it! My system was running fine before I went to bed in the morning hours on Sunday (8/1/10). I started running a long download (319 MB) that was to take about 7 1/2 hours from the ASUS website for a utility update I needed to install. The download was very slow and an absolute crawl. Now I have a broadband fast connection so it should of taken a half hour at tops. I guess their server is downright busy. I figured I would download during the night hours to get a faster download, but I see that didn't matter. But I did it anyways. Also, I was running a system scan with my security solution software. I left the system running while I slept for the download and the scan to complete. I just turned off the power on the monitor to save power. No screensavers running. Now Sunday morning (8/1/10) I woke up to check the system (about 5 hours later). It was then I had issues. I could barely move my mouse as it was jerking across my screen, then it was stuck and finally stopped moving. My system just froze up solid -- the download, the scan, my system clock, etc. stopped. First thought I had is that my hard drive is dead. I had to reboot to see what was going on. Then I could not boot into Windows. The Windows XP splash screen was barely up with the progess meter running, then I was getting the blue screen of death flashing before my eyes and the system rebooting automatically in a vicious circle. Then after a few reboots, As it was rebooting, I was getting less into the system meaning I lost the Windows XP splash screen from showing, then lost the Windows Startup options screen from showing. On another drive, I have installed Windows 7. I ran Windows 7 and before the logon screen loaded, Windows 7 found corruption on the hard drive Windows XP is on and attempted to fix it. The blue screen of death stopped after Windows 7 repair on Windows XP hard drive. Then this is where I pick up here at the start of this thread. My first thoughts, I caught a nasty malware. I do not know, but it sounds like it. I did a deep system scan a few days ago and XP was clean. A last minute infection? Now how can a system go bad that quickly in a few hours???

Any suggestions?

Thanks!

 

Hello. Please read my last post in this thread. This is a continuation...

I just leaned that the latest error message I received:

Windows could not start because the following file is missing or corrupt
\WINDOWS\SYSTEM32\CONFIG\SYSTEM.

...means that my Windows XP has corrupted system registry hives.

Basically, I am done trying now! When you have a corrupted system registry, there is nothing more that can be done.

I just do not know how the this happened so freaking quickly!!!???!!!

Again, thanks for your help!

 

See this article on how to recover corrupted registry files http://support.microsoft.com/kb/307545/

 

Same suggestion here .... slightly different method (and a safer method with an OEM installation of Windows XP) ..... long live Windows XP !

The first thing that you should do is to check that your hard drive is not failing.

Download the diagnostic utility from the hard drive manufacturer's website to create a bootable floppy or CD. Boot the problematic computer with it, and run the short/quick test and then the long/extended test. If the hard drive tests show NO problems what-so-ever with the hard drive, then it is safe to proceed with more work to rectify the problem with the Windows system.

Firstly, you need to find the brand name of your hard drive. You will find this info on the label of the hard drive (most likely you will have to remove the hard drive from the box to read the label). You will also find sufficient info to identify the drive (the model number) by looking in the BIOS Setup Menu.

Hard Drive Diagnostics Tools and Utilities
http://www.tacktech.com/display.cfm?ttid=287
==========================================

An off-line system restore may get you out of trouble.

System Restore from Recovery Console
http://2pure.net/index.php?session=0&action=read&click=open&article=1150238652
(There are a few mistakes in the the instructions text, but simply ignore those.
There is a significant mistake in Step #6 when changing the prompt back one directory level: This is given as cd..
In fact you must enter a space between cd and the two dots, so that it looks like this cd .. )

Please work carefully and deliberately, one step at a time: It is possible that you could be thwarted at any stage.
If you experience any problem with any step of the procedure, please stop, and post a description/question.

***Please be very exact with reading and typing the commands. They MUST be EXACTLY CORRECT, spaces and all.
================================

Does your system start normally now?

 

Thanks for ALL your replies!!!

AustrAlien and pwillener and all others, I got to the bottom of this!

I followed AustrAlien's advice and I did proceed with a diagnostic check first with the hard drive that Windows XP is on. I have a Western Digital Caviar Blue SATA hard drive with 500GB space and a 16 MB Cache.

I used Western Digital Data Lifeguard Diagnostic Tools. I downloaded and installed it on my Windows 7 that is on another hard drive as I have mentioned in another post here. Windows 7's hard drive and Window XP's hard drive are both on separate hard drives on the same computer. I was able to run this program on Windows 7 to check the hard drive that Windows XP is on. This is what I found:

1. Initially I found using some "SMART Status" it stated that it "Passed" with a green checkmark next to it. This is like a quick scan that is performed from the beginning. That is all well in good.

2. Now, I performed a "Extended Test" using this same program. It took under 2 hours to complete. The result stated, "Test found bad sectors that may be repairable." There is a "Repair" button on the window. When I click on "Repair", I get the message, "Error was detected while repairing bad sectors." All I have for options is "OK". I click on "OK", and I get a message stating, "Please contact WD technical support for help". I get back to the main menu of this program and I click on, "View Test Result". Here are the stats it gives:

Test Option: EXTENDED TEST
Model NUmber: WDC WD50000AAKS-00A7B2
Firmware Number: 01.03B01
Capacity: 500.11 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 08 - Error detected while repairing bad sectors.
Test Time: 15:03:3, August 03, 2010

Therefore I can conclude that the WD hard drive is failing.

Any experts on this issue with hard drives? Is this issue completely impossible now to repair with my Windows XP? ...any other possibilities? Verdict?

Please reply?

Thanks!

 

It may be possible to recover your XP installation.

Clone the failing hard drive: That is the first and most important step. There are plenty of cloning tools about, but in your particular case, I suggest that you follow the advice in the following link:

DjLizard's data recovery guide
http://wiki.lunarsoft.net/wiki/Data_Recovery

There is excellent information in this article applicable to your situation. It will give you the best chance to recover as much data from the failing hard drive as is possible.

When you have done that, attempt to boot with the new clone. If you are really lucky .... who knows?

If you still get the

error message, then follow the instructions in my previous post for an off-line system restore.

No guarantees .... best of luck.

 

Hello AustrAlien.

I appreciate your replies and dedication to my extreme issue with Windows XP. Your definately a wonderful technical friend to have!!!

I see the next phase requires me to do some serious work and requires some vested time. I will have to try it and see if it works. I know I am going out on a limb here at this point. I am willing to give it a try soon and see what happens. I have accepted the fact that my Windows XP is probably gone. I have to face facts now! I am keeping this bad drive for a bit before RMA-ing it and try what you have provided. At this point, I have realized it is for fun to see if it works. It is clear that many critical parts of the Windows XP system components are damaged/corrupted, and it may be very hard or impossible to fix. I am now facing the new Windows 7 as my new OS friend. (Let's hope it is good! Window 7's repair utility is much better than Vistas. I used it once not too long ago and it fixed something fast, I cannot recall now what it was. Vista's had a really bad success rate and very limited from what I can recall! XP's offered a lot of options!) At this stage in the game I need to be wise, I think I need to be thinking about the future. I am familiar with Windows and how it works. I stick with it. The learning curve is much bigger for a complete OS change than staying with Windows new OS versions. Learning a whole new OS is a wonderful thing, but there is a thing called available time that most people do not have time for -- a fact of life. Windows has had a lot of problems that Microsoft has shed off onto its users to handle. They are not always pratical and sensible in their approach to issues like Linux and Mac, but there are things and quirks that I respect Microsoft for. I still and always will think fondly of Windows XP. There is under 4 years of life left for Windows XP. I am happy to see that! Vista is done in less than 2! Windows 7 is out there a little further!

I will keep you and everyone here posted on what happens. It will be a little bit before I get back to this thread. Please be patient.

Thank you!

 

Hello all!

I am replying to post my final comment to this thread.

I have tired using the Unix/Linux based program RIPLinuX. My the CD-ROM from the ISO image. After booting, I had some difficulty getting around the program since the steps navigating where not too clear within the program and the instructions. I ultimately needed the component called ddrescue that I searched within the menus to find. I searched high and low, I could not find it. I also have very limited knowledge on Linux commands. The author states that he has his article is aimed at beginners in the beginning, but this is not the case as one reads on and looses me in the dust with little explaining his examples. Linux is much different than Windows. I therefore gave up on that program.

I then tried using a good non filesystem cloning software that I have. I tried copying the bad sector hard drive from the Windows XP partititon to a newly formated partition on another drive. I would used chkdsk /r after a successful clone of the partition to try to repair Windows XP. The whole time the program was copying, I received a bad sectors error along the way. It was about every 5 seconds I received a bad sectors error and I had over 2 hours of cloning to complete. I saw how really bad Windows XP is riddled with damage. After a few minutes, I gave up. I am just wasting time.

At least I can say that it is the hard drive, a physical-based issue and not a software-based issue. Windows XP is not to blame this time! I have had many Windows faillures based on software corruption related or not related to malware. So I am now reformatting my hard drive to get rid of the data on it (the best I can) and I'll be RMA-ing it very soon.

Well, no need to to reply unless you want too.

Again, thanks for all your help!

 

Sorry to hear you had so much trouble with the Linux/ddrescue bit .... I was looking forward to hearing of the result .... optimistic that you would be replying using your newly cloned XP operating system.

Thanks for replying. Glad you have resolved the issue.
Best wishes