New MOBO - Cyclic Reboot

  • Thread starter Thread starter GSteven
  • Start date Start date
G

GSteven

I have just purchased and installed a RadiSys Endura EM945G MOBO with my old
PATA HDD (Seagate ST38001A) and have hit a brick wall. First of all I put the
IDE to SATA adapter on the HDD and applied power and data cables. The drive
will not spin up at all. I tried changing the bios (Phoenix Award 5J1R2P34)
options for the SATA to every option (combined, enhanced and SATA only) to no
avail. Any clues on that would be helpful, however...

to circumvent this and just get the PC running I put the drive on the IDE
controller by itself. It spins up and attempts to boot but goes into a cyclic
reboot. I suspect it is being caused by the old AGP driver being loaded. This
MOBO has onboard PCI graphics so I don't need the AGP driver at all. I've
tried every safe boot option but still no go. Back in the old days you could
do a step by step confirmation to loads selected drivers. Is that possible
with WinXP (SP2)?

I could try making a bootable CD and putting the CD drive on as a second
(slave) drive on single IDE controller but don't know how I would
modify/delete the AGP driver if I did get it to boot.

Any help will be appreciated.
 
GSteven said:
I have just purchased and installed a RadiSys Endura EM945G MOBO with my
old
PATA HDD (Seagate ST38001A) and have hit a brick wall. First of all I put
the
IDE to SATA adapter on the HDD and applied power and data cables. The
drive
will not spin up at all. I tried changing the bios (Phoenix Award
5J1R2P34)
options for the SATA to every option (combined, enhanced and SATA only) to
no
avail. Any clues on that would be helpful, however...

to circumvent this and just get the PC running I put the drive on the IDE
controller by itself. It spins up and attempts to boot but goes into a
cyclic
reboot. I suspect it is being caused by the old AGP driver being loaded.
This
MOBO has onboard PCI graphics so I don't need the AGP driver at all. I've
tried every safe boot option but still no go. Back in the old days you
could
do a step by step confirmation to loads selected drivers. Is that possible
with WinXP (SP2)?

I could try making a bootable CD and putting the CD drive on as a second
(slave) drive on single IDE controller but don't know how I would
modify/delete the AGP driver if I did get it to boot.

Any help will be appreciated.
Click to expand...

If the new MB is radically different (new chipset, etc.) from your old
board, you will more than likely end up doing a repair installation of
Windows. If you have SP2 installed, slipstream your XP CD with SP2 before
attempting this. It'll save you a lot of time.

Putting an IDE drive on a SATA channel is not going to speed anything up,
either. It's only going to operate as fast as the slowest component, and the
drive is probably slower that the SATA interface.

SC Tom
 
SC Tom said:
If the new MB is radically different (new chipset, etc.) from your old
board, you will more than likely end up doing a repair installation of
Windows. If you have SP2 installed, slipstream your XP CD with SP2 before
attempting this. It'll save you a lot of time.

Putting an IDE drive on a SATA channel is not going to speed anything up,
either. It's only going to operate as fast as the slowest component, and
the drive is probably slower that the SATA interface.

SC Tom
Click to expand...

If you are not sure about the repair install read through this first.
http://michaelstevenstech.com/XPrepairinstall.htm

Neil
 
The AGP drive is not likely the problem, since safe mode uses plain VGA
drivers that should be compatible with almost any video card (or built-in
video). That is the beauty of safe mode, it can be used to boot XP when you
have driver problems. And, if that had been the problem, you could have
used safe mode to install new drivers.

By the way, even built-in video may require drivers. Most motherboards come
with a CD of drivers for nearly all built-in components, inclduing chipsets,
video, audio, networking, etc. With XP drivers are not required for USB or
firewire, but would be with older operating systems. The point is that just
because it is built-in do not assume that XP knows what to do with it !

However, the other response's suggestion of needing a repair install if
probably true.

Here are some links about how to do it:

http://support.microsoft.com/default.aspx?scid=kb;en-us;315341 (if
unavailble search Micrtosoft for 315341)



http://www.webtree.ca/windowsxp/repair_xp.htm



http://www.extremetech.com/print_article/0,3998,a=23979,00.asp



http://www.geekstogo.com/forum/Repair-Windows-XP-t138.html


Note that "repair" is only an option for retail XP CDs, not for OEM CDs nor
for pre-installed XP.

Finally, you could test the hardware, distinct from software, including
drivers, by booting from a live LINUX CD, such as KNOPPIX. KNOPPIX runs
from CD (or DVD) and usually automattically loads drivers, well beyond what
XP can do automatically. And, by default KNOPPIX will not write to internal
hard drive; you can, of course change that. If interested download a free
ISO image from:

http://www.knopper.net/knoppix/index-en.html

By the way, stick with KNOPPIX version 5.3. 6.0 is experimental, and has
poorer driver support at this time.
 
Back
Top