Bigtime windows install issues: Need help

*whew* Here we go.

Step one: Backup all essentials and stick on secondary 250gb drive
Step Two: Insert WinXP Pro SP2 edition in drive
Step Three: Select fresh install - reboot, enter windows setup
Step Four: Delete C partition and format NTFS
Step Five: Setup installs nessasary install files and restarts
Step Six: ERROR.

Quote:

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.

Well, After many, many hours spent reformatting, trying to install again, reading on various websites, doing expand e:/i386/hal.dl_ c:/windows/system32/hal.dll giving me "error, cannot move file, 0 files have been moved" , deleting boot.ini...

Right now, I'm running a chkdsk /r which is only at 60ish %, after that, im going to
bootcfg /rebuild
fixboot
fixmbr

and if that doesnt work, I'm going to download a hal.dll off a site, stick it on a floppy and load it from there. Keep in mind, I have no more windows on my C drive and I dont want to put it on D cause I'll losemy backup.


SO! GFF techies, I seriously need some help.

Jam it back in, in the dark.

Is the XP disc you're using to install one that you've downloaded from the 'net? Needless to say, all kinds of problems can arise if it is. The chkdsk and fixmbr are really good and important steps to diagnosing/fixing problems.

There's nowhere I can't reach.

its an ISO a friend sent me, which was confirmed to work.

This thing is sticky, and I don't like it. I don't appreciate it.

I could have sworn I already posted in this thread.

Anyhow, if I remember correctly, the hal.dll file is the Hardware Abstraction Layer, which is responsible for hiding various hardware particularities from everything else in the OS, including the kernel itself. This essentially means that it gets loaded before everything else, so it's possible that other files are also corrupted but Windows just doesn't get to loading them. I suppose you could try downloading a copy of the hal.dll file since it probably doesn't change too often, but do make sure to get the right version. At such a low level, it wouldn't be surprising if even the slightest difference, even if it's only a longer string of text, could cause things to break. If it works, then good for you. If it works, only to halt when trying the next file because it's corrupt too, then it's likely that your install media isn't good, or that the data gets corrupted somewhere during the copy to the HD, or on the HD itself.

You could try a bootable linux CD, if it runs then your hardware, with perhaps the exception of the HD, is ok. I'd recommend Ubuntu, since I think there's an option to verify data integrity before actually loading the OS, so that could help you detect trouble with whatever drive you used to burn your CD.

If it doesn't work after getting a new hal.dll file, then try the linux livecd anyway. If anything it'll help you narrow down source of the problem.

EDIT: Yep, just checked with my Ubuntu CD, there's an option to verify its integrity. Also, it possible to make a memory test, so that might be useful, in case there's a defect in a memory location that doesn't get used by the Windows install to store instructions but does get used to store data when it gets copied, so it doesn't affect the install process per se but still corrupts your files.

I am a dolphin, do you want me on your body?

Alright. Yesterdays Log.

Went to a guys house to try all sorts of crap. Took my HD, installed it as a secondary on his PC, formatted using some tool that 0's the drive. stuck it back in mine, tried installing windows, hal.dll error. okay, next. we put in an old 6gb drive, formatted it, tried installing windows on my pc, hal.dll error. we even used another CD-Rom drive, same error. So, we came to the conclusion that its not the CD Drive, the CD, (cause I used 4 diff windows cd's) or the hard drive. Here's some more info then.

Its an HP something or other workstation PC. ya know, the ones that are used in office buildings. After everything I tried, we're guessing its something internaly, mayhaps on the motherboard, some specific file that's not allowing changes to be made. We're also thinking that a virus is doing this, and its somehow stuck in the bios.. With those new facts in mind, new solutions? I'd prefer not to go to Linux or Ubuntu cause if it works, then what? I'd rather do what I can to get windows running.

I'm wondering, can I take the HD out, put it as a secondary on another computer, and install windows through that one? Does it give me an option of which drive to install it? I can try that, install windows, and then put my drive back in, but then will it give me some new error because of hardware changes... *sigh*

If all else fails, bring the stupid thing to FutureShop or Bestbuy and let them deal with it.

I was speaking idiomatically.

Ubuntu is free to order, and if it allows you to test some things - why not? If you know that some part of your computer is broke, then you can fix it. Fix it, get Windows.

What kind of toxic man-thing is happening now?

ordered one then.. In the meantime, any possible other solutions? Firmware of the bios? uh, resetting bios? ideas.. ? =/

FELIPE NO

Resetting the bios. Just pop out the CR2032 for a bit, put it back in. Might as well re-insert your cables and ram and ....etc.

I've had related problems with hardware at fault that was simply fixed by dusting the PC out and re-inserting the hardware.

What, you don't want my bikini-clad body?

Originally Posted by Lukage

Resetting the bios. Just pop out the CR2032 for a bit, put it back in. Might as well re-insert your cables and ram and ....etc.

I've had related problems with hardware at fault that was simply fixed by dusting the PC out and re-inserting the hardware.

Pop out the what?

Jam it back in, in the dark.

The CMOS battery.

Most amazing jew boots

How long do I leave it out for?

This thing is sticky, and I don't like it. I don't appreciate it.

Only a few seconds, then the settings will be reset.

I am a dolphin, do you want me on your body?

So like, what if this doesn't work... am I, just.. screwed?

How ya doing, buddy?

This is somewhat of a longshot, but maybe worth a try if things continue to fail. The problem could also be due to corrupt memory. If you can, try replacing the RAM sticks, at least temporarily. Or you can even run a diagnostic on them, like memtest86. So... yeah, maybe. I just remember a couple years ago, I've seen on a few computers, including this desktop that I'm on right now, have "weird" Windows DLL-related errors that bugged the hell out of me for weeks. Eventually was just upgrading RAM, that involved replacing sticks, and BAM, errors gone. This solutoins worked on some other people's PCs too; maybe it will on yours.

Most amazing jew boots

The ram tester showed no problems, and removing the CMOS battery did nothing either. My last options? Call HP themselves, or go to a tech store with my pc and tell them to fix it.

FELIPE NO

Originally Posted by Turbo

The ram tester showed no problems, and removing the CMOS battery did nothing either. My last options? Call HP themselves, or go to a tech store with my pc and tell them to fix it.

No!! If you do that, they will probably format your drives, and you will lose your backup. My advice to you would be to boot a LiveCD edition of Linux, and use that to copy your files to a diffferent location first. Perhaps if you can get your hands on a second PC, or an external hard drive?

What, you don't want my bikini-clad body?

Oh, I dont care if I lose everything on C. I already backed up everything before trying to format, and I took out the second drive.

After trying all these things, Im still stuck on that hal.dll missing or corrupt. I dunno what to do anymore.

Most amazing jew boots

Originally Posted by Turbo

Oh, I dont care if I lose everything on C. I already backed up everything before trying to format, and I took out the second drive.

Oh it's on a second drive? That's cool then. I thought it was just another partition on the same drive. I apologise, I didn't read your message thoroughly enough.

Quote:

After trying all these things, Im still stuck on that hal.dll missing or corrupt. I dunno what to do anymore.

I'm sorry to say that I haven't a clue. You've ruled out the CD and the CD-ROM drive, and you've also ruled out the hard drive. Your ram is working, and I just don't see what else it can be.

Quote:

We're also thinking that a virus is doing this, and its somehow stuck in the bios...

I've never heard of any form of computer virus that exists independantly of the hard drive. You can almost certainly rule that one out as well. Whatever this error is, I'd be more inclined to put it down to gremlins than to a virus that can infect your BIOS.

The only thing I can imagine it could be is a fault in the IDE controller on your motherboard. It seems that data is being corrupted in the process of being copied to the hard drive, which would imply that the fault is in the hard drive or the controller. Having eliminated the drive, it must be the controller. If it is that, you will need a new motherboard.

There's nowhere I can't reach.

I did talk to the buddy of mine who helped with my windows 95 prob with that uber old computer. He says he wants to know now if the many CDs you used were legal copies.

This thing is sticky, and I don't like it. I don't appreciate it.

legal copies or not, 4 different XP pro CD's shouldnt ALL be giving me the same problem.


I also hope its not the motherboard, cause that's going to be a big time pain to switch out. =/ I'll keep working!

Most amazing jew boots

Well I remember with my windows 95 computer... I kept doing the same stuff over and over (everything you are SUPPOSE to do) and I kept getting my error and finally one day it just worked... go figure. Did you google your prob?

Double Post:
Ok... Jay said something about a boot.ini file... he said try this-

Get into MSDOS by a bootdisk or your CD then type this...

C:
cd\
attrib -r -a -s -h boot.ini
edit boot.ini

He said make sure the operating system is correct and defaut and operating system or the same... like here's mine...



It's correct. the operating system line is right and the defaut line says the same thing.

Then he says see if it has the hal.dll. In MSDOS on C: type dir hal.dll /s If it's missing then go to repair windows (or something equivalent). In MSDOS type D:\i386\hal.dl_ C:\windows\system32\hal.dll (if your cd drive is D and the OS is on C). Tell me if that helps.

I mentioned that I think you were installing and it didn't work... he said if windows isn't on there then this may not help. I'm not sure if he's smart, asked someone, or googled But this is what he said. He put down his books for me ^.^ Nerd... taking summer classes...

Most amazing jew boots

Alright. Problem solved. All I had to do was install a new bios firmware upgrade from the HP site. Thanks for your guys help though

What kind of toxic man-thing is happening now?

Just a FYI, the CMOS battery stores your BIOS settings and such and often the startup settings are corrupt, so popping it out and putting it back in will reset to the defaults, which often can fix those sorts of problems. It's worth a try if you're fiddling with the hardware, anyways.

FELIPE NO

I did the whole battery thing, didnt work. But now at least I know what to do when the problem happens again

What, you don't want my bikini-clad body?