rec.autos.simulators

by **Geoff Sta** » Wed, 16 Dec 1998 04:00:00

I was having lock up problems with my Voodoo 2 when switching to it in
various sims. I hoped the newest drivers would help, but as most
people realize the newest V2 DX6 drivers cause more problems. Below
is something that may help.

I may have found a solution to one or both problems (the old driver
lock up and some of the new driver problems).

Deep in the Diamond Voodoo 2 troubleshooting FAQ is a small blurb
saying something to the point that, the V2 card does not like to have
it's memory range for it's driver close to any other hardware.

To achieve this they recommend the following: (paraphrased)

Go to the System control panels and find your Voodoo II, double click
for Properties and the go to the Resources tab.

Click on Memory Range and select Change Setting (you will have to
uncheck the automatic settings box).

Move 5 clicks up and 5 clicks down to see if any other devices are in
this range. If so move 5 clicks away from a conflicting device.

Diamond wants 5 clicks up and down with no other devices to avoid
conflicts. The troubleshooting FAQ (e-mailed from Diamond when I
complained about the lock ups and 2.05 GPL problems) is the ONLY place
I have ever seen this mentioned.

I had to move mine a significant amount to achieve this. Also
remember that if new devices are installed or others reinstalled
memory ranges may change resulting in a conflict again.

This fixed my lock up problem but did not seem to fix a 2.05 driver
issue with F1RS (I did not try GPL, so it may help some, at least with
the lock ups). I am now back with 2.03 drivers, but with no lock ups.

One more note, on every new V2 driver install the setting will go back
to auto.

Hope this helps someone

(Disclaimer, invoke this fix at your own risk, I make no promises of
anything what so ever.)

Geoff Stahl

by **Jalo** » Wed, 16 Dec 1998 04:00:00

-Snip-

I was also having problems running GPL (and Microsoft Combat Flight sim),
with Monster3D II v2.05. My computer would lock up on me. I switched back to
v2.03, and every thing works great.
I do not have F1RS, but I did not have any problems with Monaco (F1RS2) with
V2.05.

by **Robert Youn** » Thu, 17 Dec 1998 04:00:00

That's interesting stuff. GPL used to lock up whilst playing with any driver
on my system - I solved it by removing all applets except systray and
explorer in Win98 and by turning my voodoo 2 down to minimum speed settings
in the Voodoo properties box. So far no lock ups, but maybe the memory range
is too close as well?

Robert

>I was having lock up problems with my Voodoo 2 when switching to it in
>various sims. I hoped the newest drivers would help, but as most
>people realize the newest V2 DX6 drivers cause more problems. Below
>is something that may help.

>I may have found a solution to one or both problems (the old driver
>lock up and some of the new driver problems).

>Deep in the Diamond Voodoo 2 troubleshooting FAQ is a small blurb
>saying something to the point that, the V2 card does not like to have
>it's memory range for it's driver close to any other hardware.

>To achieve this they recommend the following: (paraphrased)

>Go to the System control panels and find your Voodoo II, double click
>for Properties and the go to the Resources tab.

>Click on Memory Range and select Change Setting (you will have to
>uncheck the automatic settings box).

>Move 5 clicks up and 5 clicks down to see if any other devices are in
>this range. If so move 5 clicks away from a conflicting device.

>Diamond wants 5 clicks up and down with no other devices to avoid
>conflicts. The troubleshooting FAQ (e-mailed from Diamond when I
>complained about the lock ups and 2.05 GPL problems) is the ONLY place
>I have ever seen this mentioned.

>I had to move mine a significant amount to achieve this. Also
>remember that if new devices are installed or others reinstalled
>memory ranges may change resulting in a conflict again.

>This fixed my lock up problem but did not seem to fix a 2.05 driver
>issue with F1RS (I did not try GPL, so it may help some, at least with
>the lock ups). I am now back with 2.03 drivers, but with no lock ups.

>One more note, on every new V2 driver install the setting will go back
>to auto.

>Hope this helps someone

>(Disclaimer, invoke this fix at your own risk, I make no promises of
>anything what so ever.)

>Geoff Stahl

by **Paul Jone** » Thu, 17 Dec 1998 04:00:00

> Deep in the Diamond Voodoo 2 troubleshooting FAQ is a small blurb
> saying something to the point that, the V2 card does not like to have
> it's memory range for it's driver close to any other hardware.

That's incredible! What are they using? Approximate memory addressing?
"Don't use a memory address close to ours or we'll blat it!?" So how come
it doesn't blat itself? The sofware driver must use memory not allocated
to it (or have been coded by Bugsy Gremlin). Rather than issuing such
statements they should fix their bugs - memory addresses are absolute and
have no effect on memory addresses in close proximity. (In NT they'd get a
memory exception - pity Windows 95 and 98 are so tolerant - it enables
people to release dodgy software).
Paul

by **Bob Jiantoni** » Thu, 17 Dec 1998 04:00:00

I had been having all the trouble that have beenmentioned until I loaded the
3dfx reference drivers (NOT the beta dx6 ones!)

All is right in my GPL world now.

by **Roy Berub** » Fri, 18 Dec 1998 04:00:00

Someone else suggested placing the glide2x.dll(version 2.53) and the
accompanying glide3x.dll(version 3.0) into the GPL directory so I tried
that. No more lockups, it works! I have win98, diamond monster2, Directx
6.1, and latest voodoo2 DX6 reference drivers.

The files come from the 'voodoo2 drivers' install on the 3dfx download
page. Reference drivers for win95/98.

Roy Berube

> I had been having all the trouble that have beenmentioned until I loaded the
> 3dfx reference drivers (NOT the beta dx6 ones!)

> All is right in my GPL world now.

rec.autos.simulators

Possible Voodoo 2 lock up solution

Possible Voodoo 2 lock up solution

Possible Voodoo 2 lock up solution

Possible Voodoo 2 lock up solution

Possible Voodoo 2 lock up solution

Possible Voodoo 2 lock up solution

Possible Voodoo 2 lock up solution