The *Official* Asus A7N8X (Deluxe) Thread

[Shockwave]

Originally posted by: magomago

Originally posted by: Shockwave
BAH! I definately get static on the audio. So far its only been intermittently in Counter Strike, but something needs a changin.

Are you using the new 2.03 Nforce drivers that are supposed to specifically address the mcp-t problems? Try that

I heard nvidia is taking a beating now, so i'll grab them later (and if they are under 5 megs I'll upload them...storage is not my problem - it is my 56k modem)

Using the Asus 1.16 driver set. Waiting for later today when web servers cool down a bit to download the newest Asus Mobo BIOS, and the latest drivers. Then, gonna flash and Format C and go from ground up again.

 

[Macro2]

RE:"Replace the 1001G bios which sucks with this one - and it displays the CORRECT temperature"

That BIOs 1002.001 or any other makes no difference in the temperatures.

OTOH, DO anyof these BIOes unlock the 2400+?
If I run say the 7x/15x stetting it just runs at 7x133. Says I have like a 933 Mhz Athlon XP.

Mac

 

[Shockwave]

Originally posted by: Macro2
RE:"Replace the 1001G bios which sucks with this one - and it displays the CORRECT temperature"

That BIOs 1002.001 or any other makes no difference in the temperatures.

OTOH, DO anyof these BIOes unlock the 2400+?
If I run say the 7x/15x stetting it just runs at 7x133. Says I have like a 933 Mhz Athlon XP.

Mac

The newest version of the BIOS is supposed to fix this. More then one person has that problem. My XP shows up as under 1 gigahertz if I use any multiple over 12.5. I've heard others have this problem also.

Anyways, this is my last post for a while. Going to flash now.

 

[transam117]

Hi everyone,

I decided that since the 1002 BIOS has arrived, that I would give it a whirl and see what happens. After flashing to the new BIOS, I couldn't get my 2800+ CPU to be seen as anything higher than 916 MHz, even when putting the correct multipliers and what not. So, after that, I decided to downgrade to the 1002_001 BIOS, and had the same problems. So in the end, I decided to go back to the original (and properly working) 1001C BIOS, but that also was now messed up, and I can only get the best performance when set to a 12.5/13 multiplier, which makes me a 2600+. Has anyone encountered problems like these, or do I just suck or the like. Thanks for any suggestions.

- Joe

 

[Shockwave]

Originally posted by: transam117
Hi everyone,

I decided that since the 1002 BIOS has arrived, that I would give it a whirl and see what happens. After flashing to the new BIOS, I couldn't get my 2800+ CPU to be seen as anything higher than 916 MHz, even when putting the correct multipliers and what not. So, after that, I decided to downgrade to the 1002_001 BIOS, and had the same problems. So in the end, I decided to go back to the original (and properly working) 1001C BIOS, but that also was now messed up, and I can only get the best performance when set to a 12.5/13 multiplier, which makes me a 2600+. Has anyone encountered problems like these, or do I just suck or the like. Thanks for any suggestions.

- Joe

Right there with you. All multi's of 12.5 and less work fine, anything above that and suddenly I'm using a CPU thats the equivelent of something from 3 years ago. Had this problem with both 1002 official and 1002.001.
No idea as of yet. Upping FSB speeds gets me up to the 2200XP I'm supposed to be at, but it gets kinda touch and go at 166 FSB. 133 works fine, but then the clock multi becomes and issue.
Boy, I'm really thinking Asus has dropped the ball on this board. Hopefully that will change.

 

[Macro2]

If you go back to AUTO my 2400+ runs at the proper speed, 2000 Mhz. I recall having to do a total shutdown and restart for it to take effect.
The multiplier selector is for unlocked processors or so says the manual. If you have a 2800+ I would think it's unlocked but I dunno.

 

[transam117]

Just wanted to tell everyone, I was messing around with the bus speed and accidentally put my puter into a state of no return, hence I had to open up the case and flush the CMOS. After this process, my 2800+ was recognized correctly again, so that is cool. Guess maybe I don't have the BIOS upgrading strategy down right. Maybe you gotta manually flush the CMOS before (or after) upgrading the firmware? I usually go back to system defaults, upgrade the firmware and then work from there, but if there is anything I'm doing wrong there, let me know. Anyways, thanks for the suggestions, and I'll stay with 1001C for now until I feel like trying 1002+ again.

- Joe

 

[Shockwave]

Heck, I'm open to anything other then a glass of water right now. I'll reset my BIOS soon as I get this video driver downloaded and installed.
640x480 @ 256 is killin me! :disgust:

 

[Shockwave]

That did it!
Using the 1002 final with XP2200 auto detected correctly. Had to pull the power cord and yank the battery, but its up and working fine.

 

[transam117]

Shockwave,

Glad to hear that flushing the CMOS worked out for you. Maybe I'll give the 1002 final BIOS another try a little bit later and see if that will work for me as well. If not, at least I know how to get the 1001C BIOS to work right again, hehe. Anywho, I'll post back later to tell if I had any luck.

- Joe

 

[transam117]

Figures...

I went to upgrade to the 1002 BIOS this time and it worked just fine...without doing anything at all. Guess just sometimes stuff works without a hitch, and sometimes it can act up for no apparent reason. Anyway, I'm glad to finally get this working...guess I'm gonna go make dinner now. Later all.

- Joe

 

[Shockwave]

Originally posted by: transam117
Figures...

I went to upgrade to the 1002 BIOS this time and it worked just fine...without doing anything at all. Guess just sometimes stuff works without a hitch, and sometimes it can act up for no apparent reason. Anyway, I'm glad to finally get this working...guess I'm gonna go make dinner now. Later all.

- Joe

I can dig the sometimes it works, sometimes it doesnt. EXCEPT in the case of the bios, if onyl for the simple reason is if your bios frizts up, your out the mobo. Isnt like a format C: fixes it ya know? Anyways, glad to hear it worked for you. Either way, I stick by my guns on this one. Asus serisouly dropped the ball BIOS wise here. Which is such a shame, the mobo is SO powerful in terms of what it has and can do. Kinda like a Ferrari with a engine that burns oil...
Ah well. Guess this hobby wouldnt be half as fun without problems eh?

 

[tharef]

How do I install the 1002.001 BIOS update file?

 

[magomago]

Install ASUS UPDATE from your CDROM

and then choose install bios from file...

and click on the extension and change it to "all files"

and select your mobo



Btw, I heard that 1002Final was the uber 3

 

[Shockwave]

1002 Final ahsnt been anything too special for me really. Havent played with it much though. Did have to reset my BIOS after flashing to get it to recognize my CPU though. Just a heads up for those goin the 1002 Final route

Otherwise, you can flash as said above, or download 2 files
awdflash and the bios name. Put both on an empty floppy, boot from a boot disk to DOS, run awdflash. Type in the EXACT file name for the Bios image and away you go.

 

[touchmyichi]

The new nvidia nforce drivers weren't working to well for me. It didn't detect cd drives and i was treated to slllllllooooooooooow boots. I tried reinstalling them twice. I didn't click that IDE thing either. I switched back to the older ones and everything is working fine now. Anyone else had trouble w/ the new drivers?

 

[transam117]

Yeah, I noticed slow bootups too while using the Nvidia 2.03 Unified driver (along with Nvidia's IDE driver). It's kinda odd, because other than the slowup, I've also noticed that the Windows XP Professional bootup "splash screen" (assuming you're using Windows XP) first appears very light, then all of the sudden it appears at normal brightness. Maybe that occurred before, but I don't recall that ever happening. Regardless, I'll stick with the 2.03 Unified (apparently the newer 1.16 drivers from Asus are basically the same drivers) for now. Well, guess that's all I got.

- Joe

PS: You can also update the BIOS by simply copying the updated BIOS file to a floppy, then hitting ALT+F2 during POST. Doing that will load the motherboard's built-in flash utility, which you then type in the filename of the BIOS file on the floppy and hit Enter. Then it goes through the update process and does the triple beep deal and reboots. You could also make a bootable floppy and include the awdflash utility as mentioned, but I find it easier to just hit ALT+F2 and having the BIOS load its version of the flash utility (which is a bit flakier in appearance than loading the actual utility from a DOS prompt). I never tried the Asus Update version of the flash utility, but I'm sure it works just fine also.

 

[touchmyichi]

Asus live update works wonderful. No problems at all here. I updated my bios to 1002.001 beta.

 

[transam117]

I'm using the 1002 final BIOS right now, but next time I'll be sure to try the Asus Update method of upgrading the BIOS, as it should be more convenient. Also, I noticed a couple things lately on Asus' site that has bothered me slightly.

1.) The links for the 1002 final BIOS do not work (and the file isn't even on ftp.asus.com.tw). Because of this, I had to get the final BIOS from ftp.asuscom.de .

2.) Didn't version 1.16 of the nForce2 drivers already exist? I have a version here of a file dated 12.5.2002 with the same exact filename (nf2v116_wxp.zip in my case), so I find that kind of odd. Unless they are the same file (just re-released on 1.29.2003?), but I kinda think they aren't, as I'm pretty sure the newer 1.16's have the 3.17 audio driver and the old ones had 3.11's or something. In any case, I find the numbering scheme odd, if indeed there is a difference between this set of drivers and the ones from 2002.

Well, guess I'm gonna head out for the night, but just figured I'd type my few gripes with Asus' website and driver labeling scheme. Good night everyone.

 

[snidy]

[(except everytime I shut it down, I have to do the power-on "trick")

What's the power on trick?

 

[DoubleL]

After working with a couple A7N8X's makes me wish they would hurry up with the KT400A's, I have had some kind of problem on every one of them, The last one everything runs fine but the harddrive knocks once and then I get all kinds of errors then it will run for about three hours then the same thing again, I have tried everything, It is a WD 60 GB SE, When I check the harddrive it checks ok, I will keep working with this one to see what I can do,

 

[Macro2]

RE:"PS: You can also update the BIOS by simply copying the updated BIOS file to a floppy, then hitting ALT+F2 during POST. Doing that will load the motherboard's built-in flash utility, which you then type in the filename of the BIOS file on the floppy and hit Enter. Then it goes through the update process and does the triple beep deal and reboots"

That's what I used. Works well.

Now I'm thinking maybe I should re-jumper the BIOS or pull the battery. What's the easiest way to pull the battery? Fingernails?
I'm still hoping by BIOS temp will read closer to the one reading the diode in MBM.
Did anyone get a temperature (BIOS CPU) drop after flashing a new BIOS? What BIOS and did you have to clear the BIOS or pull the battery?

Jim

 

[mordrid52]

Originally posted by: snidyWhat's the power on trick?

I'm assuming he's referring to the cold boot problem I also have. With my FSB at 190, my computer won't POST from a cold boot. I have to hold down the insert key before powering up to boot with default bios settings, then restart the comptuer to get it to boot with the overclocked values.

 

[magomago]

Hey guys, I''m still experiencing this error after RMAing both Mobo and RAm

What could it be? Perhaps the a7n8x doesn't like my ram?

http://ammarm.web1000.com/error.jpghttp://ammarm.web1000.com/error.jpg

 

[transam117]

Now I'm thinking maybe I should re-jumper the BIOS or pull the battery. What's the easiest way to pull the battery? Fingernails?
I'm still hoping by BIOS temp will read closer to the one reading the diode in MBM.
Did anyone get a temperature (BIOS CPU) drop after flashing a new BIOS? What BIOS and did you have to clear the BIOS or pull the battery?

To get out the battery, I just simply pry the metal retaining clip (it makes contact with the right "side" of the battery) away from the battery. The clip runs perpendicular to the face of the battery, and essentially holds it in place. Once you pry the clip back (radially away from the battery) with a flat blade screwdriver (or some other prying device, preferably plastic) the battery will pop up. You can then use your fingers to grab it. Then the manual says to move the jumper CLRTC1 (directly to the right of the battery) from pins 1&2 (default) to pins 2&3 for a second or so, then back to the original position (pins 1&2). After this, you push the battery back into place. It'll take some pressure, and playing with the clip a bit might be necessary. Before you begin putting the battery back in, however, make sure you have the positive (+) side facing up (as the battery was before you took it out). With some slight pressure, it should pop back into place, at which point you can power up again.

I didn't play with the temperature monitoring to see how it compared in MBM and with just straight from the BIOS, but if I do, I will post back with results.