Re: Is my hard disc faulty? (Boot failure, missing hal etc)
- From: HartleysXB@xxxxxxxxx
- Date: 27 Sep 2005 05:53:44 -0700
Hi!
Many thanks for the reply.
dividby0 wrote:
> the solution could begin with troubleshooting. your HDD seems to be
> fine, ince the Maxtor PowerMax s/w finds it that way.
> Next, if there'sa msg "DISK BOOT FAILURE, INSERT SYSTEMDISK AND PRESS
> ENTER", check that the IDE cable is properly attached and works fine,
> or else check the power cable. In BIOS, does it detect the HDD??
The BIOS in the ATA card detects the disc (as does Powermax.) I've
tried using different power connections and a different socket on the
controller card. I haven't tried replacing the cable, but it's only a
couple of weeks old and under some circumstances (see below) it can
read and write to the disc, so I think it's good.
> Now if everything is fine, check for the CPU fan (if you get the "BLUE
> SCREEN OF DEATH", the STOP msg with some text referring to memory
> locations), if the CPU cooling fan stops after some time, it is faulty.
Nope the CPU fan is fine, I haven't seen any BSODs
> If that also works fine, turn to the software. Make sure that the copy
> of the XP_SP2 that you have is perfect.
> Try installing the OS fromanother CD.
After I typed in this messge I dug out a copy of XP with SP1
slipstreamed, I tried installing that into a different directory on the
same partition. When the PC reboots it still fails to boot from the
hard disc. Examining the system in the recovery console shows the new
version of XP was apparently written to the hard disc successfully.
> The error saying hal.dll is missing, can only occur if there is a
> hardware driver conflict that is causing your hal.dll (hardware
> abstraction layer DLL) file to get corrupt or missing. Or it could be
> that the boot.ini file in the root is misconfigured:
> 1. Insert and boot from your WindowsXP CD.
> 2. At the first R=Repair option, press the R key
> 3. Press the number that corresponds to the correct location for the
> installation of Windows you want to repair.
> Typically this will be #1
> 4. Type bootcfg /list to show the current entries in the BOOT.INI
> file
> 5. Type bootcfg /rebuild to repair it
> 6. Take out the CD ROM and type exit
Tried that with no joy. The thing is however I've got the additional
ATA card in the system. The boot.ini generated refers to
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS. The BIOS thinks of this
card as a SCSI card so should the entry be SCSI instead of multi?
Shouldn't NTBootDD.sys be somewhere in evidence (it isn't) I'm
surprised it's disc / controller number 0 given it's on a in IDE
channel on a PCI card, wouldn't the motherboard provided IDE channels
be numbered first?
As I tried to explaining, I get the missing hal.dll error when I boot
off the floppy with the boot.ini above. When I try and boot off the
hard disc (which now has several XP installations it won't even show
the boot menu. Does this imply that ntdetect.com and ntldr are
inaccessable on that disc? If so I'm puzzled as to why I don't get an
explicit error rather than it just hanging.
> try this out and post again if it is still crapped
Sorry - still crapped. Any further thoughts are more than welcome! :-)
Thanks again
Kevin
.
- Prev by Date: Re: Windows Explorer vs File Manager
- Next by Date: Transfer XP to bigger hard drive
- Previous by thread: Re: Display Drivers
- Next by thread: Re: Is my hard disc faulty? (Boot failure, missing hal etc)
- Index(es):
Relevant Pages
|
