Any ideas on GPL

I know guys have posted and complained of lockups in GPL. I also know that for most guys simply adding the 2.53 glide driver in the GPL folder fixed their problem. But that is not the case for me. Mind you it helped, I can now run a few laps before it locks up . :-( I get screen freeze but I can still hear the car! Here are the particulars of my system. Any advice will be much appreciated. What is really weird: after it locks up and ctrl alt del to get out, my whole system runs slower than a 286! After rebooting everything returns to normal. Pent. 450 with 128MB Viper550 and 12mb Monster II 2.53 glide in gpl folder with 2.54 in windows /system( I also tried 2.53 here but no dice) 6.1 Directx (4.06.02.0436) Direct3D version 4.10.01.0207 3.01 winglide 3.x Monster driver = mnstr2.drv version 4.10.01.0205**** My Directx diagnostics says that this driver(mnstr2.drv) is not certified. Whatever that means? Thanks in advance for any input. Please also note that I can run nascar2 and nascar99 just fine in 3dfx mode. Allen A-Boyd

I'm right with you - I did the same and unless I have not done it properly (how hard is it though!) it has not helped me either. I can tell you though that you don't need to completely reboot. When the screen goes blank but you can still hear the car, you Control-Alt-Del as you stated closing the Papyrus Window, then you Control, Alt. Del again and choose to end "GPL" - it will do the usual "not responding , do you want to end task" thing - answer yes and machine speeds up again. It seems that everyone having these probs has a monster II card - I'm about to ditch and switch because I'm really tired of this crap.

I have a P-350,128MB,W98,Direct X6.1,Matrox Mellinium,M3D 2 12mb in SLI with driver version 207 and Stealth cooling fans, and the 2.53 Glide2x.dll file in the GPL directory. GPL runs fine if I keep the M3d 2 at 90Mhz. I have found that it will jump back up to 95MHz if I dont reboot after turning down the setting to 90MHz. A driver that is not certified just means that they didn't wait for MS to give its stamp of approval but it can still work fine. Lutrell :-) D Sport Racer #74 http://www2.scca.com/amateur/club_racing/runoffs/photogal/dsr-74.jpg

Quoted text (8 lines)

>I know guys have posted and complained of lockups in GPL. I also know that >for most guys simply adding the 2.53 glide driver in the GPL folder fixed >their problem.... >Thanks in advance for any input. Please also note that I can run nascar2 and >nascar99 just fine in 3dfx mode. >Allen >A-Boyd

Try putting 2.53 glide driver in windows/system also >I know guys have posted and complained of lockups in GPL. I also know that >for most guys simply adding the 2.53 glide driver in the GPL folder fixed >their problem. But that is not the case for me.

s.net>... When GPL was first released, we saw several reports of people having lock-up problems using Voodoo II boards with the same symptoms you describe. We had never seen this problem, and were unable to reproduce it in-house. So we bought a machine that exhibited this problem from a customer. We've been working with 3Dfx to identify the problem. We determined that, after a while, the board simply stops responding to Glide. As near as we can tell, this not due to GPL either sending improper data to Glide, or, in general, using Glide improperly. It also does not appear to be because of any adverse interactions between the affected Voodoo II board and the system it's installed in. We can take the affected Voodoo II board, put it in any number of different systems, and it exhibits the same problems, even when other Voodoo II boards do not exhibit problems in those same systems. This leads us to believe that the problem is hardware related, and that neither Glide, nor GPL are operating improperly. The only thing that helped was to underclock the Voodoo II board. The more it was underclocked, the longer it would run before locking up, though it would eventually lock up even then. The more it was overclocked, the sooner it would lock up. Although it is possible that the problem is heat related, this could only be so due to a faulty component on the board; one that is not capable of operating within its design specifications. We've sent the board to 3Dfx so that they can analyze it. My suggestion would be to return the board to your retailer and exchange it. Due to the multitude of issues that can lead to similar symptoms (screen savers, overclocking, DUN disconnects, incompatible drivers, etc.), I can't tell whether one manufacturer's boards are more susceptible to the problem than another. Try bring up the task list (hit ctrl-alt-del while at the desktop) and look for a task named either "GPL" or "Papyrus Window". If either exists, kill it. When it's dead, check once again (I think generally, you'll see "Papyrus Window", kill it, then "gpl" will appear, which also needs to be killed). Randy

Randy, My neighbor has a Monster 3dII that works just fine with GPL. So I tried his card in my machine with the same results. The outcome was the same. It still locked up. So that makes me wonder how it could be my card when his card did the same thing but works fine in his machine. I did underclock the Monster card to 90 as was suggested on this thread and ran a few laps to test it. It did fine but then again I didnt play long. It is very discouraging that you mentioned that it will eventually freeze up again. If that is the case, I give up. I don't know what else to do or try. :-( Allen This leads us to

Just a shot in the dark, but have you tried moving your PCI cards into different slots? This either sounds like a motherboard issue or the order that Windows has installed the hardware (and thus some sort of conflict). Also check with your motherboard vendor, this maybe a BIOS issue on their part. % Randy, % My neighbor has a Monster 3dII that works just fine with GPL. So I tried % his card in my machine with the same results. The outcome was the same. It % still locked up. So that makes me wonder how it could be my card when his % card did the same thing but works fine in his machine. I did underclock the % Monster card to 90 as was suggested on this thread and ran a few laps to % test it. It did fine but then again I didnt play long. It is very % discouraging that you mentioned that it will eventually freeze up again. If % that is the case, I give up. I don't know what else to do or try. :-( % Allen % This leads us to % >believe that the problem is hardware related, and that neither Glide, % >nor GPL are operating improperly. % > % >The only thing that helped was to underclock the Voodoo II board. The % >more it was underclocked, the longer it would run before locking up, % >though it would eventually lock up even then. The more it was % >overclocked, the sooner it would lock up -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

A week ago "someone" reported that using the Glide wrapper from http://www.grandprix2.com/gpl/patches/glide2x.zip helped. Using it results in a small delay during GPL glide calls, because it passes them through to the original glide driver. However, as I experience those lockups too (but very seldom, approx. once in two or three weeks, and I usually can play GPL for hours without freezing), it seems a bit strange to me that it should be a overheating problem. Games that use both TMUs of my Voodoo2 like Unreal or Half-Life run fine for hours, and IMHO GPL doesn't use the Voodoo2 that much that it would be more likely to cause overheating than those games. And, when it actually happens, I can close GPL + Papy Window, restart GPL, and play again for 2 hours or so. Doesn't look like a overheating problem to me... btw, 90 MHz isn't really underclocking, you should also try 85 MHz. Or try to place the V2 in another slot. Or put a fan on your Monster, if it doesn't have one already. Daniel -- Daniel Lichtenberger, Vienna/Austria "If I ate spinach I'd be called spinach D"