G

Guest

Guest
Archived from groups: alt.comp.hardware.pc-homebuilt (More info?)

I have a second pc which I use as a file server. It is running windows
xp pro which I access using remote desktop.

The other day for some reason the machine did a reboot all by itself.
Now I cannot connect to it. On closer inspection it can't even load
the OS. It seems to get stuck at the POST and cannot load the SATA
drive with the OS on it. The point of failure goes like this:

"Via VT8237 Serial ATA BIOS Setting Utility V 2.10

Scan Devices Please Wait!
Press <Tab> key into user window!

(Tab doesn't work BTW)

Hardware Initiate Failed Please Check the Device!!!
The BIOS does not be installed. Press <g> to continue"

It then tries to boot from Network which fails because this was never
setup as an option.

My configeration is as follows:

MSI Motherboard - Via KT600 chipset KT6 Delta Series AMIBIOS 09/05/03
(about 6 months old, original BIOS, never been flashed)
AMD Barton 2600 cpu
512 mb Ram
Main H/D Samsung Spinpoint 160 gb SATA(30 gb OS partition, 130 gb data
partition)
LG DVD Rom
Second H/D Samsung Spinpoit IDE 120 GB

I have checked the boot options in the BIOS but I can't see the SATA
drive?
I have also tried to clear the CMOS but this made no difference.

Micrsoft patches are up to date.
Virus definition is up to date.

Options I think I have are:

1. Rebuild the machine (drastic!)
2. Flash my BIOS to latest in the hope that I can see my drives and
then just reboot into my working Win XP OS. Only problem is how? Can I
just build a DOS boot disk from any XP Pro machine and then copy BIOS
flash onto a floppy disk and run from floppy?

Help please! I would describe my experience as intermediate..... I
built the machine and it worked with no problems for about 6 months.

Not sure if this is more hardware or OS related so apologies if posted
in the wrong group.
 
G

Guest

Guest
Archived from groups: alt.comp.hardware.pc-homebuilt (More info?)

My first thought wou.d be to check the SATA cables haven't edged themselves
out.

The second thing I would do, would be to plug the HDD into another machine
to see if it is OK.

Have you reset the CMOS ?

Also, some HDD manufacturers have self bootable disks to test hardware.

the_gnome

"Neville Henderson" <neville@urgentmail.com> wrote in message
news:bd32d9f0.0407280100.5bf6ccd@posting.google.com...
> I have a second pc which I use as a file server. It is running windows
> xp pro which I access using remote desktop.
>
> The other day for some reason the machine did a reboot all by itself.
> Now I cannot connect to it. On closer inspection it can't even load
> the OS. It seems to get stuck at the POST and cannot load the SATA
> drive with the OS on it. The point of failure goes like this:
>
> "Via VT8237 Serial ATA BIOS Setting Utility V 2.10
>
> Scan Devices Please Wait!
> Press <Tab> key into user window!
>
> (Tab doesn't work BTW)
>
> Hardware Initiate Failed Please Check the Device!!!
> The BIOS does not be installed. Press <g> to continue"
>
> It then tries to boot from Network which fails because this was never
> setup as an option.
>
> My configeration is as follows:
>
> MSI Motherboard - Via KT600 chipset KT6 Delta Series AMIBIOS 09/05/03
> (about 6 months old, original BIOS, never been flashed)
> AMD Barton 2600 cpu
> 512 mb Ram
> Main H/D Samsung Spinpoint 160 gb SATA(30 gb OS partition, 130 gb data
> partition)
> LG DVD Rom
> Second H/D Samsung Spinpoit IDE 120 GB
>
> I have checked the boot options in the BIOS but I can't see the SATA
> drive?
> I have also tried to clear the CMOS but this made no difference.
>
> Micrsoft patches are up to date.
> Virus definition is up to date.
>
> Options I think I have are:
>
> 1. Rebuild the machine (drastic!)
> 2. Flash my BIOS to latest in the hope that I can see my drives and
> then just reboot into my working Win XP OS. Only problem is how? Can I
> just build a DOS boot disk from any XP Pro machine and then copy BIOS
> flash onto a floppy disk and run from floppy?
>
> Help please! I would describe my experience as intermediate..... I
> built the machine and it worked with no problems for about 6 months.
>
> Not sure if this is more hardware or OS related so apologies if posted
> in the wrong group.