(2nd post)
Hello !
Can someone please help me get F1RS run on my machine. I'm only able
to drive for 3-4 laps (in any mode) before F1VOO.EXE crashes with
the same error messages. (Invalid page fault in module WAVX2BVR.DLL
at at 0157:01704c84) .
I've tried everything
eg set min/max vcache to 4096
set min/max swapfile 128/132
change Default=WAVX2 to WAVPW in [DLL_Sxd] --- (in this case, the
error message just change to module WAVPWBVR.DLL)
make a full installation in the same drive as Win95
run F1RS with the minimum details available
but still the same thing happens.
The only way to make it work is for me to delete snd_cpa.ini , ie
without any sound at all.
So what the hell is wrong wit my copy of F1RS. All my other 3DFX games
(Turok, Tomb Raider, Longbow2) run without any glitches at all.
Could it be the Ensonic AudioPCI ? Anyone with similar card around ?
System Spec : (as reported by dxinfo.exe)
Windows 95 : 4.0 Build 1212 B
CPU : Intel Pentium 200 MMX
Physical memory: 32 MB RAM
Hard Disk : Quantum Fireball 4.3G
DirectX Version(Registry): 4.05.00.0155.55
Display
Card name : STB Nitro 3D, with STB Vision 95
Manufacturer : STB Systems, Inc. (OEM)
Chip type : S3 385
Display Memory : 4 Meg
Driver : stbvisn.drv
Version : 4.03.00.2121 "4.03.00.2121-1.52A" Final Retail
Date and Size : 06/09/97 01:52:00 176832 bytes
Current files : stbvisn.drv,*vdd,stbnt3d.vxd
Refresh rate : 0 (uses Default rate)
Resolution : 800 x 600
Colors : 65536 (16 Bits/Pixel, 1 Plane(s))
Direct3D (DirectX) Display
Card name : Pure3D DirectX5 Driver
Driver : Pure3D32.dll
Version : 4.10.01.0013 "4.10.01.0013-1.20.02" Final Retail
Date and Size : 11/13/97 01:20:00 223232 bytes
Glide Version : 2.43-1.20.02
Sound
Card name : ENSONIQ AudioPCI
Wave Out Device: AudioPCI Wave Out
Driver : eapci95.drv
Version : 4.05.00.1038 "4.05.1038" Beta Retail
Date and Size : 12/23/97 12:08:20 81264 bytes
Current files : eapci95.drv, eapci.vxd(12-23-1997)
Joystick
Model : Thrustmaster Formula T1/T2 with adapter
Usage Settings : 0x00000006 Joystick is present
Driver : Default
Seeing as the problem only occurs when you have sound enabled, that would
(as you have guessed) seem like a good place to start looking <g>
OK, you've got a very recent driver, but it is designated as 'beta'.
Maybe it has some bugs in it? Can you get hold of an older, non-beta
driver and see if that helps. If not, a report of the bug to Ensoniq
might help them fix the bug before they make the current driver a full
release version.
Cheers,
Richard
