rec.autos.simulators

My system was 95b from the factory with the new fat. I was ***y happy to rid
of it and don't really care what the problem was now. It cost me a week on
this system before I decided to go the whole route of starting from sratch,
again... There is something there though.

Q.B.M.

Actually, if it is (a), then their version has had the Service Pack 1
applied.  The original Win95 doesn't have the letter after the version.
:-)  

But I get your drift.  I have the (B) version,  and all is fine in Win95
games.  N2 doesn't recognize any of my controllers when running from Win95.
 The game port I am using is the SB16 port.  All is fine when running from
straight DOS.

The only problem I have with blaming it on version (b)  is that Eric is
using the same version (b), and his SB port, and his works fine.  Go
figure.

My OSR2 was installed from scratch on a newly formatted drive.   The N2 /
T2 / Win95 combo doesn't work here....  Eric?

Just to avoid any confusion here, OSR2 can be identified two ways.  On
the System Properties General Tab (right-click on My Computer and
select Properties) it will show 4.00.950 B, 4.00.950.1111, or 4.00.950
C (OSR2 w/ Plus Pack I think).  The original version will show 4.00.950
or 4.00.950 A, depending on if Service pack 1 has been installed.  Also
typing "ver" at a DOS prompt will report: Windows 95. [Version
4.00.1111].

--

The IWCCCARS Project: Q & A Representative
http://www.theuspits.com/iwcccars/index.html
http://userwww.service.emory.edu/~ebusch/

Not on a newly formatted drive, but I did decide to nuke my previous
windows folder and install OSR2 from scratch.

--

The IWCCCARS Project: Q & A Representative
http://www.theuspits.com/iwcccars/index.html
http://userwww.service.emory.edu/~ebusch/

I thought of another thing.... Does anyone else having this problem
have directx 3.0 installed? I do, and the DirectInput sdk might be
whats messing everything up. The timing may be right for that if my
memory serves me. Now, where did I put that copy of directX 2 ......

DirectX 3.0a here, and my T2 is still working.

--

The IWCCCARS Project: Q & A Representative
http://www.theuspits.com/iwcccars/index.html
http://userwww.service.emory.edu/~ebusch/

I have the directx 3.0 loaded, with OSR2, and no JS in N2.

Charlie Heath
Papyrus

It is a problem with win95b.... all we need now is to know how to fix
it,.

Yesterday I tried it on a CLEAN OSR2 install - did not work. I tried it
on a CLEAN OSR1 install - it worked!!!!

I tried it with FAT32 and without FAT32 with OSR2 - did not work on
both!!!

says...

Two things that may be different between my machine and others:

1. I have "*** devices" instead of "joystick" in my control panel,
   courtesy of the drivers for my Microsoft gamepad.  That may mean
   that I have different joystick DLLs and whatnot than most people
   running OSR2.  If you have a MS joystick or pad, there are updated
   drivers for it at www.microsoft.com.  (If you don't, you may or
   may not be able to do something with them anyway.)

2. I have an entry in my devices list for my gamecard.  I had to
   tell Win95 that it's a Thrustmaster ACM, since there's no entry
   for a generic game card.  Initially I didn't have my gamecard
   in my devices list, just my joysticks, and that worked with
   most games, but not Monster Truck Madness.  I had to add the
   gamecard entry before MTM would look for a joystick or wheel.

Anyway, that's a couple more things to try, unless someone already
mentioned them while I wasn't paying attention.

--