Help!

[ezlor]

I just installed, and every time I try to start it up it gives me an error and exits

winfah.exe has generated errors and will be closed by Windows.

The sequence of events is like this.
1) I start the application up, and the little red gear show up in the tray.
2) I click on the gear and the display opens up.
3) Letters strart printing across the top __really slowly___
4) The the error pops up and it closes down.

I tried using the screensaver only version, but the same thing happens.

I'm running win2k on a pIII, 512megs of ram with a Matrox G450 Dualhead graphics card. I only bring up the graphics card because I'm running two mis-matched monitors off of it (viewsonic PF790 and optiquest Q71), and that has given other apps issues in the past. (can't run jspager, because it looses track of windows on screen 2).

In any case, I'm not running folding@home full screen or on screen 2, so it really shouldnt be a problem.

 

[Kendan]

Well it is the graphics card. you have two choices. one is to just not open the graphic. two is to download the console ver. place it in your folding directory and run it. you can monitor F@H with foldmonitor which there is a link on the Overclockers folding team page located thru the link in my sig. You might try updating you video drivers as this has helped some. good luck and fold on!!!!

 

[ezlor]

Ok, thanks!

The folding monitor works just fine.

BTW - Updated the driver and didn't make a difference ( except that it wont let me go over 60Hz refresh when running 1280x1024 and 32bit True Color anymore, had to drop to 24bit ) oh well...

 

[JetMech]

BTW - Updated the driver and didn't make a difference ( except that it wont let me go over 60Hz refresh when running 1280x1024 and 32bit True Color anymore, had to drop to 24bit ) oh well...

Did you clean install the updated driver? Change to standard vga driver. Remove the old driver completely from the system. Reboot and install updated driver. It's possible that someting in the registry is trying to install part of the old driver or deny update of certain files. Also check the version of direct x you're running and be sure your vid card supports it. Finally run the direct x diagnostic to see if you can get through it without crashing and be sure you have open gl running.