Re: SBS 2003 - Hal.dll Getting Currupt

Hardware raid? software raid? OS drive is raid 1, or 5?

How about drive and/or controller diagnostics available from the boot screen?

Is this a desktop (workstation) grade machine, or a server grade? Make?

I think you're going to need to start at the lowest hardware level possible, and run some diagnostics.

--
Les Connor [SBS-MVP]


____________________________
"Irving Duran" <iduran@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:45FE5159-BB5D-4F7D-9C68-551141560A2A@xxxxxxxxxxxxxxxx
Is a RAID drive and the motherboard is a Intel Duo Core. Yes, I have done a chkdsk, and the first two times I did not received any type of error but on the third time the chkdsk didn't even start.

Which it make me guess that my main hd is dying, but I do not want to believe that.

Any recommendations would be appreciate it.

Thank You in advance.

"Les Connor" <les.connor@xxxxxxxxxxxx> wrote in message news:eu57T6ZVJHA.200@xxxxxxxxxxxxxxxxxxxxxxx
What kind of disk/motherboard subsystem do you have (i.e. disk type, raid, etc.)

Have you done chkdsk? Under the circumstances, I'd suspect hardware failure of some type (resulting in disk corruption).

--
Les Connor [SBS-MVP]


____________________________
"Irving Duran" <iduran@xxxxxxxx> wrote in message news:37156F4B-D48F-4588-904E-4C51D4A05995@xxxxxxxxxxxxxxxx
i am having a really big problem lately. i have a sbs 2003 and every so
often in the last month my hal.dll has been corrupt and/or deleted. i am
receiving the following error 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."

and i tried to do the tutorial that are online but no luck yet. what i've
been doing in order to resolve this problem would be reinstalling the OS and
it works fine for a while but then goes back to have the hal.dll corrupt.

any ideas what it could be causing the problem?



.

Relevant Pages

  • Re: SBS 2003 - Hal.dll Getting Currupt
    ... Consistenly getting that error would mean, in my mind, a strong possibility of disk corruption - especially with a raid set. ... If you have hardware raid, you should be able to enter the raid diagnostics at boot time, and run some tests on the controller, disks, and raid set from there. ... "Windows could not start because the following file is missing or corrupt: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 - Hal.dll Getting Corrupt
    ... I haven't changed any hardware on the machine. ... sometime this weekend and see is there is any type of error message. ... Are you using hardware raid? ... "Windows could not start because the following file is missing or corrupt: ...
    (microsoft.public.backoffice.smallbiz)
  • Re: MotherBoard Change
    ... If she boots she'll start detecting hardware changes. ... HAL' can be forced and work on the new mobo (see MS about forcing HAL ... The procedure for going from what was software RAID on the old system to ...
    (microsoft.public.windows.server.sbs)
  • Re: [opensuse] Raid 5 installation
    ... I also purchased 4 WD 400G SATA drives to make a 1.09T ... raid5 array under Linux, SUSE 10.2. ... (which would defeat the hardware raid controller builtin to the MB). ...
    (SuSE)
  • Re: MotherBoard Change
    ... If she boots she'll start detecting hardware changes. ... and work on the new mobo. ... The procedure for going from what was software RAID on the old system to ...
    (microsoft.public.windows.server.sbs)
Loading