rec.autos.simulators

Works fine on mine (G6-400), only change is I have a 12 mb Voodoo 2.
Doesn't sound like it found your Voodoo 2 card, so you probably need to
download the old 3dfx files that F1RS looks for to determine if you have a
Voodoo card, they're on www.f1racingsim.com.  Or I think you can just copy
the "f1voo.exe" file from the CD to your F1RS directory, and point your
shortcut to this one.  But getting the files to "force" a Voodoo install is
probably better.

Other than that, I dunno.  When you say freeze, do you mean locked up or
pausing?  Mine paused some, like REAL bad after several laps, and this has
gone away after I disabled the virus program and other stuff in the
background, F1RS is butter-smooth on this rig.  If you're getting total
lockups, I dunno.  One thing, to make sure you're in Voodoo Glide mode,
check for Lens Flare, IIRC it isn't in the Direct 3D version.

Ken

P.S.  And this is in Win 98, that was pre-installed when I got the rig - and
no problems with Win 98 and games so far.

Is it always two laps?  I've just upgraded my machine, and F1RS seems lock
up after 3 or 4 laps.  I'm wondering whether it's time related, and it
locks up after x minutes.

All the peripherals (AWE32, Voodoo2, etc) I've taken from my old machine
where F1RS ran just fine.  I'm now running on a Pentium II at 450Mhz with
a different Graphics Card (ATI rather than Millenium), and OSR2, rather
than regular Win95.

When F1RS locks, the sound keeps going, but I can go back to the Windows
task manager, and kill the app.

I'm pretty much stumped.  If you find a solution, then please let me know.

Cheers,

Steve.

Okay, I think I've sussed this out.  Like you I have the 8Mb Creative
Voodoo2 running in a machine with a PII-400 (I'm actually overclocking
mine so it's running even faster).

The other symptoms that I had (which I failed to mention in my previous
posting) is that in about 1 in 8 failures I got some screen corruption
prior to the***.

This afternoon I picked up the latest reference drivers from www.3DFX.com,
but they made no difference (although at one point I did manage to drive
for half a lap which the screen looking like a cross between a psychedelic
pavement pizza and a 'magic eye' picture.)

I then reduced my clock speed to the regular 400Mhz, and the locking up
took longer to appear (about 8 laps).

"A-ha, cooling!" I thought.  I opened my machine, and re-slotted the
voodoo2 card into a slot which:

a.  Only has a card to the back of it (i.e. above the chip side is an
empty slot.)

b.  Is more in line with the fan on the front of the machine.

I also re-routed some cables to ensure that there was good air-flow, and
switched my fan on the front of the machine so that it sucks in cold air,
rather than blows out warm.

(I also took the time to move my memory to a slot further away from my
processor, but I suspect this isn't relevant).

Even with the machine back up to it's overclocked state, F1RS seems to be
running fine now - I've just completed a 50% race with no glitches.  Tom's
Hardware page said that the Creative card was less overclocking tolerant
than the Diamond card, and my guess is that a 400Mhz processor is pushing
out a hell of a lot of polygon requests, and F1RS is probably more
graphically intensive than stuff like Quake II, so the card is under more
load.  My overclocking probably didn't help much, but I wonder whether
you've picked a slot in your Gateway box that isn't getting as much
air-flow over the card as it might need.

Hope this helps.

Steve.