Build Your Own Arcade Controls Forum
Main => Monitor/Video Forum => Topic started by: diverdown on July 01, 2011, 09:34:27 pm
-
yesterday i swapped my arcade PC over and went from AGP to PCIe MB so happily i had pre ordered a new ArcadeVGA card from Andy. (this was my 3rd). I pulled the old AGP card out last week and sold on ebay (with a brand new one i had bought for a "getroundtoit" project 3 years ago!).
Card arrived yesterday and after failing to get it to work i figured i may as well read the instructions - ALL SWEET now.
However (and the point of this post) - During P.O.S.T the Arcade (and PC LCD) show solid white screen. As the normal text of POST appears the place where the text appears on the screen gets "overwritten" with white text on black background (i.e. it looks fine), but ONLY where there is text. The rest of the screen remains white.
When Windows loads all is OK - the issue is only during POST.
Andy is on Summer Holidays (and so are my kids) so as i am in no hurry to pull the card out and return accross the globe.
I am not trying to "air a companies dirty laundry" in a forum. Please be aware i LOVE ULTIMARC products, and Andy's immediate support :burgerking: etc. I would not go with any other product if simmilar was available from Ultimarc.
If this is a normal feature of an AVGA card then all is OK - if not then Andy will surelly swap it over.
Have any others had this issue? Is it worth doing without for a fortnight (after school holidays)?
-
Is your CRT 15hrz only if so and you have the jumpers set on the avga then it will split signal untill the drivers load in windows so it doesnt damage your monitor and so you get some post info
-
CRT is 15Hz
The POST only shows on the LCD - I am happy with this, and once Win7 loads the arcade monitor works fine (incidently I had it set so only the arcade monitor was connected and post also showed the issue on the arcade monitor too.
The issue is that the POST is white - the "Energy Star Compliant" image during POST is not legible on the LCD
-
Do you have both the crt and the lcd hooked up, I never had any luck getting them to work together, if your running strait from the avga to the crt you post screen is going to scrambled/not viewable all together because the avga doesn't output 15hrz till the drivers are loaded, a picture of the problem would be great though
-
Do you habe both the crt and the lcd hooked up, I mever had any luck getting them to work together, if your runnimg strait from the avga to tje crt you post scteen is going to scrambled orun viewable all togethwr because the avga doesnt output 15hrz till the drivers ate loaded, a picture of the problem would be great though
I have BOTH the CRT and monitor hooked up. Once AVGA installed - go to desktop settings in Windows and add the second monitor - Extend to that ( i added the Arcade montor as the 2nd). You cannot clone but an LCD makes further tinkering more pleasurable than trying to view on a big arcade monitor.
I am running straight from the AVGA to the LCD and from the AVGA to a J-PAC to the Arcade monitor.
And you are correct - so Picture attached
-
oh wow yea that's definitely not a signal issue, that's corrupt graphics normally cause by bad ram but it could be anything from a heat issue "not likely" to a bad avga "known to happen". Email Andy with that picture and a good description of what exactly is going on and I'm sure he'll take care of you. But to make sure all basses are covered ensure that all your connections from the jpac to the monitor are solid with no ground outs and make sure on the jpac you have the jumpers on 15hrz and 31hrz. If all that is in place only thing else i can tell you is try to another video card laying around that might work with Calamity's drivers and see if you get the same result if you don't it's most certainly the AVGA
-
Thanks KALAIS.
Issue solved - I got a reply from Andy at Ultimarc:
"Hi,
This is normal, the first screen contains left over RAM contents until the first time it is cleared.
Regards
Andy"
I will leave this post for others info who find the same issue that is no longer an issue.