The NEW Build Your Own Arcade Controls
Main => Monitor/Video Forum => Topic started by: FractalWalk on March 24, 2003, 12:02:49 am
-
I've got an ASUS A7V333 Mobo and a AMD Athlon 1800+ CPU with ArcadeVGA video on a WG 7400 monitor. I've got my system up and running, but at seemingly random time intervals, I get a beep code from the Mobo and then my screen blinks off and then on. In rare instances, it blinks off and then does not come back on at all. Other than that, the video seems fine. I get Windows and I get MAME at all the different resolutions that Andy's card supports.
The particular beep codes (3 short and 1 long) are not listed at all in the Mobo user manual nor can I find anything on the web. This didn't happen when I had the system hooked to a standard computer monitor and so it leads me to believe it is either my WG 7400 or the ArcadeVGA card.
Anybody have anything similar or any idea where I can find out what these codes mean?
-
Sounds like you need to reseat the video card. Try this site http://www.bioscentral.com/ it
-
deadhead:
Thanks for the suggestion but unfortunately I know very little about the BIOS in general and therefore that site isn't helping me out. I don't even know what BIOS I have! When interrupting the boot-up procedure, there is a screen that says I have an ASUS ACPI BIOS Revision 1015, which isn't listed at the site you reference.
I swapped out cards and monitor and got the same beep codes along with a Windows pop-up about video drivers. Once the proper driver was found I never got the beeps again. So this makes me think it is a video driver issue.
So I swapped back to the ArcadeVGA and K7400. I got the beeps. I re-installed ArcadeVga drivers and I still get the beeps. I double checked that the drivers in place are the exact same files that came on Andy's disk. The monitor displays everything as if the drivers are correct and yet I am getting the alarm that says I dont have the right drivers. But I am only getting it and somewhat random times.
I am extremely confused.
-
Sorry, I
-
If the first word of your BIOS is ASUS, it is made by Asus. Then, check their web site for the codes.
-
The ASUS web site and manual was no help. That code is not listed. I have sent an e-mail to them asking to verify that it is a video card issue. However, seeing as it went away when I swapped out cards, I think it almost has to be that.
The speech reporter on my Mobo doesn't provide any verbal message, rather just the beep codes. I don't think it is a bad motherboard as it worked perfectly with a different video card.
-
I have the same mobo and if the spech wasnt on as default you need to go into the bios and select it .
On boot up my pc says " No floopy disk detected" "now booting ........"
Also
Award BIOS Beep Codes
Beep
Meaning
One long beep followed video card not found or video card
three short beeps memory bad.
JD
-
Award BIOS Beep Codes
Beep
Meaning
One long beep followed video card not found or video card
three short beeps memory bad.
JD
Yeah, I saw that in the manual, but my codes are 3 short followed by one long. I don't know what that means but assume it is video related.
I set the speech in the BIOS last night and I'm pretty sure I rebooted after that and if so, there was no speech during bootup. I'll have to double check that tonight.
-
If you have installed more than one video card lately what you should do is go back to square one. That means remove all the video card drivers and bring the system up without any drivers and install the Ultimarc drivers using the setup CD.
This may help clear up any driver confusion that exists on your system.
BobA
-
If you have installed more than one video card lately what you should do is go back to square one. That means remove all the video card drivers and bring the system up without any drivers and install the Ultimarc drivers using the setup CD.
This may help clear up any driver confusion that exists on your system.
BobA
BobA:
I think you were right . . . again.
I tried what you suggested and couldn't get it to work, but of course I might have not been pulling the right files. So I re-formatted and started over. So far, so good.
Thanks all! I'll let you know if it happens again.