A8N-SLI Deluxe

1landshark

Member
Jul 8, 2005
140
0
0
I built my system a little over 3 years ago and had to replace the board after a year and a half. Now my computer is no longer booting up. First it would not boot up sporadically - now it just just stops/dies in the middle of the boot up and I think the board is bad.

Is there a way that I can tell if it's the battery?

My other question is that I was told if I change the board to a different board that I might have to reinstall Windows XP Pro but if I use the exact same model I will not have to reinstall Windows. Is that accurate?

I am thinking of buying the A8N-SLI Premium.

Would appreciate any advice that anyone can offer. Thanks
 

1landshark

Member
Jul 8, 2005
140
0
0
Can anyone direct me to a website that gives info on replacing motherboards. I am trying to find out if I would be able to keep my hard drives in tact or if I would have to reinstall Windows and lose my data with a different motherboard
Thanks
 

LordGestle

Senior member
Jan 2, 2001
764
0
0
If your staying with the same chipset type (nforce 4), you should be ok. I went from a nforce 2, 2 ultra, Nforce 4, Nforce 4 SLi, and jumped over to a nforce 650i all on the same OS. I even changed between chipset vendors, but that's not a given.
Just make sure to let it install all the plug n play items on first boot. Don't worry about video and sound drivers. Let it reboot when asked and then reinstall the nforce chipset drivers and etc.
The only problem you may have now is finding a replacement board.
 

Rakewell

Platinum Member
Feb 2, 2005
2,418
1
76
LordGestle is most likely correct. If you have any troubles with your OS after the board swap, though, just run a windows repair.

If you experience any wonkyness after that, ie videocard or soundcard, it might be worth backing everything up and wiping/reinstalling XP.
 

lizrdfishr

Junior Member
Aug 16, 2008
3
0
0
I also own an A8N-SLI Deluxe. I have had it since 2006. I loved this board even though I had to update the BIOS twice to fix the nraid glitches that plagued it early on.

This board is not ACPIP compliant. It will not run XP pro SP3 unless you employ a work around using a USB2 device. To keep my machine running, I have had to roll back to SP2 and disable Microsoft update.

I am now considering replacing this board with a FOXCONN 939 board. I will not be purchasing the ASUS Striker II Extreme I had in the budget this year.

I will not own an ASUS product again.

The blogshpere is full of angst where customers purchased this board and ASUS having discontinued this board will NOT fix the problem.

Here in writing is my own experience. If you follow the link it will take you to the ASUS member web site where you can read the response to my ticket from their site as they published it.

If you are receiving a BSOD on boot or the message Non ACPIP compliant BIOS detected, welcome to the sinking ASUS ship.

http://vip.asus.com/eservice/t...D=WTM20080723055597034
 

Quiksilver

Diamond Member
Jul 3, 2005
4,725
0
71
Originally posted by: lizrdfishr
This board is not ACPIP compliant. It will not run XP pro SP3 unless you employ a work around using a USB2 device. To keep my machine running, I have had to roll back to SP2 and disable Microsoft update.

Interesting, cause I'm using an A8N-SLI Deluxe with XP SP3 just fine with only two USB devices. One being my keyboard; the original Logitech G15 (eg. not the newly redesigned one) which isn't USB 2.0. The other being a Logitech G5; also first revision (eg. not the blue one that's got the extra button) which I don't believe is USB 2.0 either.

EDIT:

Also from your own support ticket your experience does not relate to this thread at all. As your motherboard is an A8N32-SLI Deluxe not A8N-SLI Deluxe there is a difference.

Also, in your trouble ticket you claim to not have any USB devices at all, so... why not do the work-arounds posted on their forums like you claim "you have read" when that is to disable USB function. So i don't see why your so angsty, when they have posted work-arounds that don't require a USB devices to fix it nor claim to not release a BIOS fix...