Did you *fully* uninstall the older drivers first? If not do so now
and try again. If still no go. Try reinstalling the game. It might
need to profile the new drivers in some way. If still not, try
returning to previous drivers.
Good luck
"Fred" <[email hidden]> wrote in message
news:[email hidden]...
> I can't run GP3 anymore.
> After all the lights have turned red, the screen turns blue and Iget
> one of those wonderful messages in white text. It says somethingabout
> VXD error and then a lot of numbers (memory addresses?). I can'teven
> run the calibration-thing!
> I have a TNT2 Ultra 64 - card. What is wrong? I even triedreinstalling
> Win98, that didn't work.
>
> PLEASE HELP!!
>
> /Fred
>
looks like ur GP3 has been detonanted! j/k! just had to say it! good luck man!
VXD is Virtual Acces Sometng I don't know
I'm almost sure the videocard is not able to do GP3 for you.
Look for updated drivers at the manufacturers side.
I had, I guess, the same problem when trying Gp500 with my viper550
2 weeks later it was solved with a new driver.
Don't have any more information.
Dirk
"Fred" <[email hidden]> wrote in message
news:[email hidden]...
Quoted text (12 lines)
> I can't run GP3 anymore. > After all the lights have turned red, the screen turns blue and I get > one of those wonderful messages in white text. It says something about > VXD error and then a lot of numbers (memory addresses?). I can't even > run the calibration-thing! > I have a TNT2 Ultra 64 - card. What is wrong? I even tried reinstalling > Win98, that didn't work. > > PLEASE HELP!! > > /Fred >I can't run GP3 anymore.
After all the lights have turned red, the screen turns blue and I get
one of those wonderful messages in white text. It says something about
VXD error and then a lot of numbers (memory addresses?). I can't even
run the calibration-thing!
I have a TNT2 Ultra 64 - card. What is wrong? I even tried reinstalling
Win98, that didn't work.
PLEASE HELP!!
/Fred
> VXD is Virtual Acces Sometng I don't know
> I'm almost sure the videocard is not able to do GP3 for you.
> Look for updated drivers at the manufacturers side.
> I had, I guess, the same problem when trying Gp500 with my viper550
> 2 weeks later it was solved with a new driver.
hehe - the detonator 3 _are_ the newest drivers ;-)
VXD problems often indicate an interrupt problem: check if your graphics
card shares the ICQ with some other card. be sure that every card has
its own IRQ. I know that PCI 2.x specifies IRQ-sharing, but normally the
drivers don't ...
if the VXD causing the problem is VMM32.VXD, you might need to rebuild
it. you can find out how on this page:
http://www.infinisource.com/techfiles/vmm32.html
maybe you also want to check out this page:
http://support.microsoft.com/support/kb/articles/Q174/0/18.ASP
Lio
> It is probably VMM32.vxd that causes the problem because it says something
> like "Exception error! VXD - VMM(01)" and alot of numbers. I don't think
> there's an interrupt problem. The problem occured after I reformatted my
> harddrive and installed win98se instead of win98. Could my win98se
> install-cd contain a corrupt vmm32.vxd? Would it be possible to rebuild it
> if it's corrupted from the beginning?
the vmm32.vxd is build at installtime and updated from time to time
(check the 2nd link I posted). I don't think that it could be corrupt
from the bginning, but you could have had a crash or something that
caused a corruption, so give a rebuild a try!
Lio
It is probably VMM32.vxd that causes the problem because it says something
like "Exception error! VXD - VMM(01)" and alot of numbers. I don't think
there's an interrupt problem. The problem occured after I reformatted my
harddrive and installed win98se instead of win98. Could my win98se
install-cd contain a corrupt vmm32.vxd? Would it be possible to rebuild it
if it's corrupted from the beginning?
/Fred
Quoted text (16 lines)
> hehe - the detonator 3 _are_ the newest drivers ;-) > > VXD problems often indicate an interrupt problem: check if your graphics > card shares the ICQ with some other card. be sure that every card has > its own IRQ. I know that PCI 2.x specifies IRQ-sharing, but normally the > drivers don't ... > if the VXD causing the problem is VMM32.VXD, you might need to rebuild > it. you can find out how on this page: > > http://www.infinisource.com/techfiles/vmm32.html > > maybe you also want to check out this page: > > http://support.microsoft.com/support/kb/articles/Q174/0/18.ASP > > LioOk, now I've rebuilt it and it WORKED! ... 1 time, then it kept crashing again.
And it didn't help to rebuild it again.
Fred
> the vmm32.vxd is build at installtime and updated from time to time
> (check the 2nd link I posted). I don't think that it could be corrupt
> from the bginning, but you could have had a crash or something that
> caused a corruption, so give a rebuild a try!
>
> Lio
