xp pro missing hal.dll

[Guest]

I recently installed a new seagate HD, and loaded xppro. when i get finished
with the booting from the cd where the set up is supposed to take over i get
an error (windowsroot/system32/hal.dll missing). I,ve tried alot of different
ways to get around this even did the boot disket deal, but nothing has
worked. The last thing i tried was from the repair console at C:\WINDOWS
type attrib -H -R -S C:\boot.ini then it tells me parameter is invalid. any
ideas?

 

[Guest]

Are you running a dual boot? Try this link:
http://www.kellys-korner-xp.com/xp_haldll_missing.htm

 

[Guest]

no my HD has been partiioned for 1 full with ntfs only wxp pro installed. How
can i check to make sure that i'm not set up for dual boot?

 

[Guest]

If you have a "dual-boot" setup you will be given the choice of which OS you
want to boot up at startup. There are several hal.dll issues. Google it to
find the correct one. Mike.

 

[Guest]

Hi mike I think you got me on the right track. I rebooted my pc and it
prompted me to select which OS . the problem is i have two winxp pro
configured and the top one doesn't work but the bottom one does boot up to
the windows set up. shortly after this i get a (File asms needed). gotta
clue? Steve.

 

[Guest]

I have my OS cd in, but it is still aking me to type the path where it can be
found.

 

[Guest]

I'm not sure what that file is but try the path c:\windows\system32. Also,
this link should help clear up your dual boot issue:
http://michaelstevenstech.com/xpfaq.html#two

 

[Alex Nichol]

I recently installed a new seagate HD, and loaded xppro. when i get finished
with the booting from the cd where the set up is supposed to take over i get
an error (windowsroot/system32/hal.dll missing). I,ve tried alot of different
ways to get around this even did the boot disket deal, but nothing has
worked. The last thing i tried was from the repair console at C:\WINDOWS
type attrib -H -R -S C:\boot.ini then it tells me parameter is invalid. any
ideas?

If you typed that exactly as stated, including the spaces, it should not
come up with invalid parameter. It may be that the file just is not
there; in which case go on to do the
BootCfg /Rebuild