rec.autos.simulators

Hi Jim (and anyone else who may be reading this);

I am having a N2 display problem that I cannot***. I've posted an
earlier note re: this problem but have not found a solution. Here is
the situation: I run N2, I calibrate my wheel (T2), I select a race
(assume Taladega for this example), I enter the race (whatever
session, it does not matter, for this example assume Practice
session), I begin travelling down pit row, and display stutters/pauses
very very briefly about every 10 - 15 secs. It is real quick, almost
like it pauses for a split second, then tries to correct itself. As I
progress around the track, the display continues in this pattern,
pausing very briefly approx. every 10-15 sec. Coming out of turn 4 and
into the tri-oval the car pulls real hard to the left almost
uncontrollably.

My system configuration is as follows:

32mg ram
Gigabyte HX motherboard
Cyrix P166+ processor
Intergraph Intense3D 1000 graphics card
Quantum Bigfoot HD
SB 16PnP sound card (using joystick port)
Thrustmaster T2 wheel/pedal combo
Mitsumi PnP 8x CD Rom

Things I have tried to correct the problem:
-Install the patches
-Reinstall the game
-Disable most programs running in Win95 (Norton Crashguard, MS Office,
ICQ) I still have the anti virus software running (McAffe VirusScan)
but I have this running on another machine running N2 and have no
issues.
-Run from Dos instead of Windows95
-Set Minimum value to Disk Cache size.
-Disable screen savers
-Set properties in Short Cut to the Renddma and N2 files so as not to
include the Fast ROM emulation and Dynamic memory allocation props. It
is also set for running in full screen and not allowing screen savers.
I changed EMS requirements from Auto to None.
-Run in 4bit graphics mode (-4 switch with the latest patch).
-Disabled AutoPlay on my CD Rom.

I am real frustrated, Jim. I have tried all the tricks I know or can
find, but nothing seems to work. Can you shed some light as to what is
happening and how to correct it? Is there something I should check in
my Bios? Please help me.

Torrey
Most sincerely from the desk of BT Nagle

"I reckon so..." - Clint
No spamming, please

<lotsa stuff snipped>

With my M-Tech r534 Mustang board, Cyrix P200+, Matrox Mystique I have
found that changing the ISA bus speed made a big difference in the
smoothness of the wheel using the soundblaster joystick port.
The best setting I have found is 1/3 of the PCI bus speed which calculates
out to 12.73mhz. (75mhz/2=37.5mhz/3=12.7333)

Don't know if this will help anyone or not but it did make major improvement
here.

It sounds more like you have trouble because you are using Win95. I won't
have Win95 until I get around to making a separate partition for it to live
on so it can't***with the rest of my system.
If I was writing software that uses a joystick/wheel I would be a little
upset with MS for their thoughtless changes to the way it handles the
joystick ports. I have had digital joystick drivers for my computer for over
three years now and never had any trouble like people are having now.

Getting off the soapbox now  :)

<more snipping>

Just maybe my tip will help you, should be able to change it in the BIOS
Ralph Williams

/----------------------------------------------------------------------\
/Ralph Williams      My real .sig file is in the shop getting repaired.\

/----------------------------------------------------------------------\

Are you running it from Win 95? If so try running it from DOS
(NOT Dos box but full Dos)

--

Nigel of Lakewood Motorsports
Nascar Coruba & Coke Chevy
Hamilton
New Zealand

Yes, I tried the DMAdiag utility, no real difference. Still seeing the
same condition.

I tried running from pure Dos, no difference. I even tried
reinstalling to a new directory, no difference.

First off try this....CAD all but explorer and systray...those are the only
2 files needed to operate win95.

the fact that all is well on another computer means nothing even if they
are nearly identical.
.
If that does'nt isolate the problem then check your bios for cyrix specific
features, enable and disable features one at a time.

That's my 2 cents...good luck.


I'm having a N2 display problem that I cannot***.