gabbadoo

Maybe you'll find some usefull reading below, though it seems you've already gone through some of it. Windows 2000 does support multiple processor... http://www.tek-tips.com/viewthread.cfm?qid=1273347&page=1 How to add support: http://support.microsoft.com/kb/234558/en-us

Had a similar "detecting array" (running raid-0) issue on my dfi nf4 ultra-d, which seemed to only happen after my system froze due to Mosfet temps at around 60 degrees C.

Here's a review that was written around release-time: http://www.tbreak.com/reviews/article.php?id=346

I would visit the Asus forum's for that particular board, to see what issues users are having. I've heard some crappy tales regarding that board, but those might be noobflaming. Generally I think Asus are rising towards the levels of DFI, but still the a8n-sli is quite an old generation - i mean from where asus weren't nowhere near DFI, in regards to performance. The a8n32-sli was a state of the art motherboard, where the discussion, as to whether the board would actually "threaten" the DFI boards, kind of enden with the question: "do you really need 2 16x PCIe lanes for SLI" . my thoughts.

thanks, me too

My NF4 Ultra-D just died on me, so atm. I don't have access to my SATAII raid 0 setup, where I've stored all my music, vids and games etc :sad: I've found a used NF4-D, which - according to DFI.com.wt - only supports RAID I, however my disks are able to work in SATA I mode (with the use of a jumper). Will the array be lost, or would it remain unharmed, if I use the latest NF4-D bios? Are the raid-bios'es for the NF4 Ultra-D and the NF4-D the same, despite the fact that they support different SATA specs?

I've had, roughly speaking, the same issue with a dying GPU due to lack of power. It is also possible for you to buy a pre-flashed BIOS chip off of Tmod I believe. Try to PM him.

To me it sounds more like something has been overheating over time, and died. I'd question the Mosfet temperatures or the Chipset temps, but it could easily be your PSU. I reckon you can't check the temps on the Mosfets and Chipset, but maybe you should try to clean you PSU and check if the fans are able to spin around. Try another PSU, if u haven't already.

Think I may have found out what went wrong. One of the cornerpins of my Opty146 was bent so much it seemed to have contact with an adjacent one. I've straigthened it out, so with a little luck I now have 3 A64 cpu's lying around, and only a dead socket on my NF4 Ultra-D :eek:

Hi Was thinking of getting me that Biostar NF4 Ultra-A9A board, since it's so damned cheap, and it's even got SATAII support aso. Havent been able to find any reviews on it, so I'm here to get some response from you users, who tried it or heard of it, on how well it performs, and if the Bios is worth working with from an oc'ers point of view.

Alright. Just bought myself a very cheap watercooling setup. Did the leak testing and so on. The cpu-block is custombuilt, I believe it can be used with a phase-setup too. Only problem is that you need to figure out some alternative mounting method - and so I did. In order to test if the setup would work and actually cool the cpu, I found my old Opteron 146 (unlidded! ) , because I didn't want to possibly destroy my "new" Opteron 170. I mounted the thing using my "very alternative" mounting method :eek: , but once I turned the thing on, it went from very short 4 LEDS on to stay with 3 LEDS on (checking cpu), while beeping a 1sec long beep - 3 secs pause - 1sec long beep - 3 secs... continuously. I turned the thing off and removed the cpu-block (maybe! a bit carelessly), to find that there was some as5 residue on some of the IC's beside the die. My pulse started pounding, since it seemed I no longer had any way to test the water-setup without involving my new Opteron 170, and since the Opteron 146 worked flawlessly before switching it with the Opteron 170. To excuse myself :angel: - to myself and give myself some hope... I figured that maybe the residue wasn't there as I turned the thing on, but got there as I pulled of the cpu-block, which is a bit tricky (there's definately a higher chance of touching the rest of the cpu when pulling off the cpu-block, than when mounting it). I cleaned the cpu and tried reinstalling it along with my old AC 64 Freezer Pro, but got the exact same error. Then I tried the same with my Opteron 170, using the AC 64 Freezer Pro, but the exact same error. As I uninstalled the Opty170, I saw that there was some cracks at one side of the die, and very small ones at some IC's on the same side. The ones on the die has been there for like 6 months or so, causing no problems, but I couldn't rule out that I'd just destroyed two A64's :sad: Those cracks were made by the AC64Freezer Pro though. Since all i new about the LEDS was that if 3 LEDS stay lit, it means there's a problem with the cpu, so I figured - since a new A64 cpu these days come rather cheap - that I would buy myself a new cheap A64, by asking my brother to borrow me the money, and so I did. Today the new A64 X2 3800+ came with the mail, and first thing I did, was to just plug it in without the cooler and switch on the board, to see if the error was the same, and it was. Possible causes of the error: 1. AS5 residue on the IC's while having it turned on 2. Shorting the IC's on the cpu with the cpu-block due to mounting the block in a non-leveled way (meaning the cpu-block had a slight tilt) 3. Ruining something in the socket by applying to much pressure on the cpu. I'm currently resetting the cmos, by removing the battery, setting the jumper to reset, draining capacitors by pressing power button once, ... and waiting - do I really need to? Is the board toast? What do you think of the beeps, what do they mean?

Alright. Just bought myself a very cheap watercooling setup. Did the leak testing and so on. The cpu-block is custombuilt, I believe it can be used with a phase-setup too. Only problem is that you need to figure out some alternative mounting method - and so I did :eek: In order to test if the setup would work and actually cool the cpu, I found my old Opteron 146 (unlidded! ) , because I didn't want to possibly destroy my "new" Opteron 170. I mounted the thing using my "very alternative" mounting method, but once I turned the thing on, it went from very short 4 LEDS on to stay with 3 LEDS on (checking cpu), while beeping a 1sec long beep - 3 secs pause - 1sec long beep - 3 secs... continuously. I turned the thing off and removed the cpu-block (maybe! a bit carelessly), to find that there was some as5 residue on some of the IC's beside the die. My pulse started pounding, since it seemed I no longer had any way to test the water-setup without involving my new Opteron 170, and since the Opteron 146 worked flawlessly before switching it with the Opteron 170. To excuse myself - to myself :angel: and give myself some hope... I figured that maybe the residue wasn't there as I turned the thing on, but got there as I pulled of the cpu-block, which is quite a messy procedure (there's definately a higher chance of touching the rest of the cpu when pulling off the cpu-block, than when mounting it). I cleaned the cpu and tried reinstalling it along with my old AC 64 Freezer Pro, but got the exact same error. Then I tried the same with my Opteron 170, using the AC 64 Freezer Pro, but the exact same error. As I uninstalled the Opty170, I saw that there was some cracks at one side of the die, and very small ones at some IC's on the same side. The ones on the die has been there for like 6 months or so, causing no problems, but I couldn't rule out that I'd just destroyed two A64's :sad: Since all i new about the LEDS was that if 3 LEDS stay lit, it means there's a problem with the cpu, so I figured - since a new A64 cpu these days come rather cheap - that I would buy myself a new cheap A64, by asking my brother to borrow me the money, and so I did. Today the new A64 X2 3800+ came with the mail, and first thing I did, was to just plug it in without the cooler and switch on the board, to see if the error was the same, and it was. Possible causes of the error: 1. AS5 residue on the IC's while having it turned on 2. Shorting the IC's on the cpu with the cpu-block due to mounting the block in a non-leveled way (meaning the cpu-block had a slight tilt) 3. Ruining something in the socket by applying to much pressure on the cpu. I'm currently resetting the cmos, by removing the battery, setting the jumper to reset, draining capacitors by pressing power button once, ... and waiting - do I really need to? Is the board toast? What do you think of the beeps, what do they mean?

Anyone here who knows the distance between the two holes used to mount the chipset heatsink? I was thinking of getting myself an XSPC x2o VGA block with a diagonal measure between the holes of 44-82 mm. - I'm not sure that it can be used due to the height of it tho. Anyone?

bump

Anyone who've tried the in-title-mentioned ( NF4Ultra-D, HR05-SLI, 8800GTS & HR-03 Plus? ) configuration? Currently my 8800GTS' stock cooler just touches my chipset cooler (HR05 SLI), although it hasn't affected the HR05 Sli "lock" on the Chipset. I wan't to mess with some overclocking aswell as I like the cooling performance of the HR03 Plus compared to stock-cooler ( - 20 degrees C at load ) Remember: there's no room to mount the HR-03 Plus on the backside of the 8800GTS due to the size of my AC Freezer 64 Pro Cpu-cooler !