Re: [Flexradio] I recovered from the Fatal Error syndrome!!!
Tim Excellent tip. Downloaded the latest ATI drivers for my FireGL X1-128, uninstalled the old drivers (ugh forgot what a crummy display BASIC windows video drivers produce), cold boot W2k FOUND new video device, hit cancel, ran ATI setup !voila! display is good in P8 with DirectX now. There is some flickering of the vertical horizontal lines when you move the console around but that may be refresh rate related. Phil, K3IB - Original Message - From: Tim Ellison [EMAIL PROTECTED] To: FlexRadio@flex-radio.biz Sent: Sunday, December 18, 2005 12:09 AM Subject: [Flexradio] I recovered from the Fatal Error syndrome!!! OK, here is the skinny. After reading all the posts today on the Fatal Error Syndrome, it kept occurring to me that something in the video driver / DirectX arena was probably the culprit, so I focused my energy there. I ran DXDIAG, an it said everything was fine and dandy, but I had my suspicions since it took forever for the Direct Draw test to start. Bottom line is that Windows really can't 100% fix itself. You have to do it for it. After trying just about every combination of driver setting, I decided to punt. 1.) I downloaded the latest version of DirectX (again) and installed it. It was the entire package of DirectX, not the updates. 2.) I downloaded the latest video driver for my NVIDIA GeForce 6200 3.) I went into Device Manager and I wiped the video driver clean off the system (files and Registry settings). Rebooted when it asked to. 4.) Once the system rebooted, I allowed it to install the standard VGA driver. 5.) Then I ran the NVIDIA driver install program and rebooted (again) 6.) Once it rebooted I re-ran DXDIAG and Direct Draw was MUCH faster. Direct 3D ran about the same. 7.) I crossed my fingers and sacrificed an effigy of Bill Gates in the back yard (this step is optional, but it makes you feel a lot better) 8.) I started Preview 8 and low and behold, it loaded. The PowerSDR Setup Wizard never looked so SWEET! Let the testing begin. -Tim --- Tim Ellison mailto:[EMAIL PROTECTED] Integrated Technical Services http://www.itsco.com/ Apex, NC USA 919.674.0044 Ext. 25 / 919.674.0045 (FAX) 919.215.6375 - cell PGP public key available at all public KeyServers ___ FlexRadio mailing list FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Re: [Flexradio] I recovered from the Fatal Error syndrome!!!
Tim Ellison wrote: OK, here is the skinny. After reading all the posts today on the Fatal Error Syndrome, it kept occurring to me that something in the video driver / DirectX arena was probably the culprit, so I focused my energy there. I ran DXDIAG, an it said everything was fine and dandy, but I had my suspicions since it took forever for the Direct Draw test to start. Bottom line is that Windows really can't 100% fix itself. You have to do it for it. After trying just about every combination of driver setting, I decided to punt. With thanks to Tim, I followed his instructions, loaded new DirectX and Nvidia driver and lo and behold...Beta 8 works! Bad news part. CPU usage 7-8% with GDI+, jumps to 68-72% with DirectX! -- _____ / \ / \ / \ / \ / \ John L. Sielke ( W )( 2 )( A )( G )( N ) http://w2agn.net \_/ \_/ \_/ \_/ \_/ CRUSTY OLD CURMUDGEON, AND PROUD OF IT
Re: [Flexradio] I recovered from the Fatal Error syndrome!!!
John, The only way I get my CPU utilization down is to cause an Unhandled Exception. Once that happens, CPU utilization is about 3% -Tim --- Tim Ellison ( [EMAIL PROTECTED] ) Integrated Technical Services ( http://www.itsco.com ) -Original Message- From: w2agn [mailto:[EMAIL PROTECTED] Sent: Sunday, December 18, 2005 10:52 AM To: Tim Ellison Cc: FlexRadio@flex-radio.biz Subject: Re: [Flexradio] I recovered from the Fatal Error syndrome!!! Tim Ellison wrote: OK, here is the skinny. After reading all the posts today on the Fatal Error Syndrome, it kept occurring to me that something in the video driver / DirectX arena was probably the culprit, so I focused my energy there. I ran DXDIAG, an it said everything was fine and dandy, but I had my suspicions since it took forever for the Direct Draw test to start. Bottom line is that Windows really can't 100% fix itself. You have to do it for it. After trying just about every combination of driver setting, I decided to punt. With thanks to Tim, I followed his instructions, loaded new DirectX and Nvidia driver and lo and behold...Beta 8 works! Bad news part. CPU usage 7-8% with GDI+, jumps to 68-72% with DirectX! -- _____ / \ / \ / \ / \ / \ John L. Sielke ( W )( 2 )( A )( G )( N ) http://w2agn.net \_/ \_/ \_/ \_/ \_/ CRUSTY OLD CURMUDGEON, AND PROUD OF IT
