GPL: sudden framerate problem

I generally consider myself fairly capable with regards to PC tweaking, etc., but this problem is driving me crazy: My GPL is suddenly running at about 0.5 fps. I have a Creative TNT card, and use the Open GL driver. I have downloaded the latest Creative drivers, and tried the nVidia drivers, but neither has helped. A few weeks ago I tried some of the Open GL tweaks (from the Display Properties...) and so this may have something to do with it - although I have since tried several different settings. I have also recently upgraded to a 20.5 GB hard-drive, and am using a Side Pro-66 ATA-66 controller. I have also just added a HP-9110i CD writer to my system, and installed ZoneAlarm a couple of days ago. I don't know if anyone knows of any problems with these. . . . ANY suggestions are greatly welcome! Ryan

Ryan I had this exact fault recently. System has a TNT card and I'm using the Open GL driver on GPL, Quake etc etc. I used the diagnostic programme Msconfig which is included in Win98 to track down the fault by disabling everything to establish that the system was ok and then zeroing in gradually. Its time consuming and lots of re-boots but it worked. In my case something (I don't know what!) had inserted a line in the win.ini file under the section shown below: [DrawDib] . . . DVA=0 I don't know what this stands for (direct video access?) but I assumed it was a switch. I changed the setting to DVA=1 and everthing is working with no detectable problems. You might want to check here first as it may be the same fault and you can save some time and effort if so. Good luck -- Ross Hearne Remove "nospam" from return email address if mail reply "Ryan Mitchley" <[email hidden]> wrote in message news:8bnbsb$72e$[email hidden]... > I generally consider myself fairly capable with regards to PC tweaking, > etc., but this problem is driving me crazy: > > My GPL is suddenly running at about 0.5 fps. I have a Creative TNT card, and > use the Open GL driver. I have downloaded the latest Creative drivers, and > tried the nVidia drivers, but neither has helped. A few weeks ago I tried > some of the Open GL tweaks (from the Display Properties...) and so this may > have something to do with it - although I have since tried several different > settings. I have also recently upgraded to a 20.5 GB hard-drive, and am > using a Side Pro-66 ATA-66 controller. I have also just added a HP-9110i CD > writer to my system, and installed ZoneAlarm a couple of days ago. I don't > know if anyone knows of any problems with these. . . . > > ANY suggestions are greatly welcome! > > Ryan > > > >

"Ross Hearne" <[email hidden]> wrote in message news:hSGD4.4982$[email hidden]...

Quoted text (7 lines)

> Ryan > I had this exact fault recently. System has a TNT card and I'm using the > Open GL driver on GPL, Quake etc etc. I used the diagnostic programme > Msconfig which is included in Win98 to track down the fault by disabling > everything to establish that the system was ok and then zeroing in > gradually. Its time consuming and lots of re-boots but it worked. > In my case something (I don't know what!) had inserted a line in the

win.ini > file under the section shown below: Thanks! This was EXACTLY the problem. Now I wonder which cheeky piece of software caused it . . . Good detective work, BTW! In the future I'll make a point of trying this detailed MSconfig method when my other options have run out. I would probably have been on my way to re-installing Windows if you hadn't responded ;-) Ryan

Glad to have helped! This method has worked for me a couple of times when all seemed lost. Regards -- Ross Hearne Remove "nospam" from return email address if mail reply "Ryan Mitchley" <[email hidden]> wrote in message news:8bpsk8$5eg$[email hidden]... > > "Ross Hearne" <[email hidden]> wrote in message > news:hSGD4.4982$[email hidden]... > > Ryan > > I had this exact fault recently. System has a TNT card and I'm using the > > Open GL driver on GPL, Quake etc etc. I used the diagnostic programme > > Msconfig which is included in Win98 to track down the fault by disabling > > everything to establish that the system was ok and then zeroing in > > gradually. Its time consuming and lots of re-boots but it worked. > > In my case something (I don't know what!) had inserted a line in the > win.ini > > file under the section shown below: > > Thanks! > > This was EXACTLY the problem. Now I wonder which cheeky piece of software > caused it . . . > > Good detective work, BTW! In the future I'll make a point of trying this > detailed MSconfig method when my other options have run out. I would > probably have been on my way to re-installing Windows if you hadn't > responded ;-) > > Ryan > > > >