missing hal.dll -- recurrence after repair

[JClark]

Hello,

OEM windows XP Pro, SP2
An old Intel PIII computer has been working OK, but quit booting with
the "missing or corrupt \system32\hal.dll" error message. I repaired
the installation with the windows XP CD. It worked for two weeks but
now has the same problem.

Is this likely a "general hardware failure" (one of the causes listed
on the MS support site)? Or should I try again with a repair?

Also, if I replace the MB and processor but leave the same hard drives
in, can I still install the OEM windows XP Pro I bought for the
original machine on the new system? I seem to remember somewhere that
OEM win XP is only good for installation in a single computer. Hope
I'm wrong.

Many thanks.

Jack

 

[Malke]

Hello,

OEM windows XP Pro, SP2
An old Intel PIII computer has been working OK, but quit booting with
the "missing or corrupt \system32\hal.dll" error message. I repaired
the installation with the windows XP CD. It worked for two weeks but
now has the same problem.

Is this likely a "general hardware failure" (one of the causes listed
on the MS support site)? Or should I try again with a repair?

Also, if I replace the MB and processor but leave the same hard drives
in, can I still install the OEM windows XP Pro I bought for the
original machine on the new system? I seem to remember somewhere that
OEM win XP is only good for installation in a single computer. Hope
I'm wrong.

I wouldn't do a repair or a reinstall until I'd tested the hardware
thoroughly. Get your data backed up now if you haven't done so already.

http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

OEM versions of XP are supposed to be tied to the machine on which they
are first installed. If you have a generic OEM, there will be nothing
preventing you from using it on the same rebuilt machine. Legally... I
don't ever answer those questions. Read the EULA and make your own
decision. If this is a branded OEM (Dell, HP, etc.) in all probability
it won't run on an non-Dell or HP motherboard anyway so the point is moot.


Malke

 

[Clark]

Hello,

OEM windows XP Pro, SP2
An old Intel PIII computer has been working OK, but quit booting with
the "missing or corrupt \system32\hal.dll" error message. I repaired
the installation with the windows XP CD. It worked for two weeks but
now has the same problem.

Is this likely a "general hardware failure" (one of the causes listed
on the MS support site)? Or should I try again with a repair?

Also, if I replace the MB and processor but leave the same hard drives
in, can I still install the OEM windows XP Pro I bought for the
original machine on the new system? I seem to remember somewhere that
OEM win XP is only good for installation in a single computer. Hope
I'm wrong.

Many thanks.

Jack

Hi Jack, Hijack that's funney... lol

Replace your hard drive, your drive has gone bad and your files are getting
corrupted. ( I've had many customers with the same problem)
As far as moving your OS, when it comes time to activate and you get
prompted to call MS, just tell them you are a system builder and you are
replacing it (motherboard) under your warranty, if the Feds come knocking at
your door (they won't) please delete this post.


Clark

 

[Nightowl]

An old Intel PIII computer has been working OK, but quit booting with
the "missing or corrupt \system32\hal.dll" error message. I repaired
the installation with the windows XP CD. It worked for two weeks but
now has the same problem.

Is this likely a "general hardware failure" (one of the causes listed
on the MS support site)? Or should I try again with a repair?

Just a thought. . . the hal.dll message can be misleading. It's
sometimes the boot.ini file that is the problem. Might be worth checking
that before you change the motherboard etc.
http://xphelpandsupport.mvps.org/how_do_i_repair_a_missing_or_cor.htm

 

[Lil' Dave]

Hello,

OEM windows XP Pro, SP2
An old Intel PIII computer has been working OK, but quit booting with
the "missing or corrupt \system32\hal.dll" error message. I repaired
the installation with the windows XP CD. It worked for two weeks but
now has the same problem.

Is this likely a "general hardware failure" (one of the causes listed
on the MS support site)? Or should I try again with a repair?

Also, if I replace the MB and processor but leave the same hard drives
in, can I still install the OEM windows XP Pro I bought for the
original machine on the new system? I seem to remember somewhere that
OEM win XP is only good for installation in a single computer. Hope
I'm wrong.

Many thanks.

Jack

Keywords: "OEM windows XP Pro I bought". You have the generic version. As
long as its installed on one machine, no problem.

There's a long list of stuff that's suspect regarding hardware. Its all I/O
associated. RAM, hard drive, the bus system for both on the motherboard and
cpu bus as well. A problematic power supply (borderline) can produce
similar problems.

Dave

 

[JClark]

Keywords: "OEM windows XP Pro I bought". You have the generic version. As
long as its installed on one machine, no problem.

There's a long list of stuff that's suspect regarding hardware. Its all I/O
associated. RAM, hard drive, the bus system for both on the motherboard and
cpu bus as well. A problematic power supply (borderline) can produce
similar problems.

Dave

Many thanks to all who replied. It is not a branded machine. I put it
together from some spare parts and it's done well for several years. I
will try all the suggestions in the replies, but it looks grim for the
old box...

Most of the parts will be the same when I fix it up, including the
case and much of the hardware, so I guess I'm OK with Mr. Gates.

Again, I appreciate the advice..

Jack