From: steve marchant on 13 Feb 2007 11:48 Pc frequentlyfails to boot into windows. Just before windows starts in boot sequence, message comes up saying hal.dll file is missing or corrupted, and advises reinstall file. When I try to reinstall this file in Recovery Console, I get "access denied". Sometimes pc boots into windows ok, and I'm able to use system restore to set up previously working date, after which system works fine - for several days before the prob returns. What's the significance of this file, and is there any effective workaround? Some help would be appreciated. BTW it's a system32file.
From: Woody on 13 Feb 2007 15:12 Google is your friend. Do a google search on hal.dll gives lots of information the most common appears to be a corrupt boot.ini file. Also search Microsoft Knowledgebase. "steve marchant" <steve.c.marchant(a)tiscali.co.uk> wrote in message news:45d1ebf1$1_2(a)mk-nntp-2.news.uk.tiscali.com... > Pc frequentlyfails to boot into windows. Just before windows starts in > boot sequence, message comes up saying hal.dll file is missing or > corrupted, and advises reinstall file. When I try to reinstall this file > in Recovery Console, I get "access denied". Sometimes pc boots into > windows ok, and I'm able to use system restore to set up previously > working date, after which system works fine - for several days before the > prob returns. > What's the significance of this file, and is there any effective > workaround? Some help would be appreciated. BTW it's a system32file. >
From: carl.metellus on 13 Feb 2007 15:34 On Feb 13, 11:48 am, "steve marchant" <steve.c.march...(a)tiscali.co.uk> wrote: > Pc frequentlyfails to boot into windows. Just before windows starts in boot > sequence, message comes up saying hal.dll file is missing or corrupted, and > advises reinstall file. When I try to reinstall this file in Recovery > Console, I get "access denied". Sometimes pc boots into windows ok, and I'm > able to use system restore to set up previously working date, after which > system works fine - for several days before the prob returns. > What's the significance of this file, and is there any effective > workaround? Some help would be appreciated. BTW it's a system32file. ok Hal stand hardware abstraction layer and it allow the software to communicate with the hardware so it is critical to your system. what you need to do is use the MSCONFIG to extract the file from the CD and send it to the system32 folder and that should take care of the problem. ok you're probably wondering how you do that. here is how: click on Start and then click on Run then type in MSCONFIG then click on Expand File then in File to Restore type in hal.dll in Restore from type in X:\i386\hal.dl_ (x being your cd drive) then in save file in type C:\Windows\System32 and that should take care of it. Or another way to do that is to click on start and then run and type in "sfc / scannow" without the quotes. let me know whats up when its done
From: steve marchant on 13 Feb 2007 19:43 "Woody" <TheDuck(a)pond.net> wrote in message news:zYoAh.12079$O02.11032(a)newssvr11.news.prodigy.net... > Google is your friend. Do a google search on hal.dll gives lots of > information the most common appears to be a corrupt boot.ini file. Also > search Microsoft Knowledgebase. > Google does seem helpful. I fear that one of the links there (given below)suggests that if, having tried all the suggestions, a fresh install of Windows doesn't fix the problem, then it's likely to be a hardware fault in the hard drive. This in fact happened, so I'm now fearing the worst.
From: steve marchant on 14 Feb 2007 05:00 <carl.metellus(a)gmail.com> wrote in message news:1171398896.261698.71950(a)v45g2000cwv.googlegroups.com... > On Feb 13, 11:48 am, "steve marchant" <steve.c.march...(a)tiscali.co.uk> > wrote: >> Pc frequentlyfails to boot into windows. Just before windows starts in >> boot >> sequence, message comes up saying hal.dll file is missing or corrupted, >> and >> advises reinstall file. When I try to reinstall this file in Recovery >> Console, I get "access denied". Sometimes pc boots into windows ok, and >> I'm >> able to use system restore to set up previously working date, after which >> system works fine - for several days before the prob returns. >> What's the significance of this file, and is there any effective >> workaround? Some help would be appreciated. BTW it's a system32file. > > ok Hal stand hardware abstraction layer and it allow the software to > communicate with the hardware so it is critical to your system. what > you need to do is use the MSCONFIG to extract the file from the CD and > send it to the system32 folder and that should take care of the > problem. ok you're probably wondering how you do that. here is how: > click on Start and then click on Run then type in MSCONFIG then click > on Expand File then in File to Restore type in hal.dll in Restore from > type in X:\i386\hal.dl_ (x being your cd drive) then in save file in > type C:\Windows\System32 and that should take care of it. Or another > way to do that is to click on start and then run and type in "sfc / > scannow" without the quotes. let me know whats up when its done > Done as you suggest. Pc working fine at moment. Hopefully it will stay that way, but if it reverts to the familiar pattern, then I fear a hardware problem as mentioned to Woody in this thread. Thanks for help.
|
Pages: 1 Prev: Error code E02D02 and E02E05 on a Canon W8200 PG Next: task manager problem |