W95+Nascar2+No Joystick or T2... Survey

I am conducting a fact finding mission on my own to try to resolve this mysterious dilema with Nascar2 not allowing gameport devices to be calibrated while running under Windows 95. Please note that this is not T2 specific but rather any joystick, gamepad, or wheel device which works fine in other software under dos and/or w95, but will not work with the combination of W95+N2. I am narrowing it down to a possible problem with the Win95 (B) build but have yet to confirm. Please include all vital system info you can in your response (s) and if posting here as a followup, please email me also. My system: Mtech R528WP mb w/512k pb Award Bios v4.51 Rev.Gu 166mhz MMX, 32 meg EDO Intergraph Reactor video *Addonics Soundvision 500 <<Sound/gamecard *Version (B) of Windows95 *Devices which do not respond to Nascar2 under W95 -T2 (Thrustmaster) -Gravis Analog Joystick -Gamepad (Reveal) The items listed with a * in front are the most important for my research. Thank you, Ron

My gamepad works fine in windows 95 if you go into the control panel and calibrate your gamepad there first. Philip Young

I have ECS P5VX-B mb w/512k pb Award BIOS v5.41 166mhz, 32 meg EDO Intergraph Reactor with Orchid Righteous 3D Awe32 with 8 meg ram and MediaVision Daugterboard addon Windows95 (B) The devices I have which don't work are TSW Steering Wheel Gravis Analog Joystick Gravis GamePad Microsoft Sidewinder PRO P.S. - I think you may be right about the Win95 (B) version creating the conflict.

Quoted text (26 lines)

> I am conducting a fact finding mission on my own to try to resolve > this mysterious dilema with Nascar2 not allowing gameport devices to > be calibrated while running under Windows 95. Please note that this is > not T2 specific but rather any joystick, gamepad, or wheel device > which works fine in other software under dos and/or w95, but will not > work with the combination of W95+N2. I am narrowing it down to a > possible problem with the Win95 (B) build but have yet to confirm. > Please include all vital system info you can in your response (s) and > if posting here as a followup, please email me also. > My system: Mtech R528WP mb w/512k pb > Award Bios v4.51 Rev.Gu > 166mhz MMX, 32 meg EDO > Intergraph Reactor video > *Addonics Soundvision 500 <<Sound/gamecard > *Version (B) of Windows95 > *Devices which do not respond to Nascar2 under W95 > -T2 (Thrustmaster) > -Gravis Analog Joystick > -Gamepad (Reveal) > The items listed with a * in front are the most important for my > research. > Thank you, > Ron

I am using a Thrustmaster GP1 wheel w/ TM's ACM card. After following TM's setup for N2, it works fine under W95. It sure beats the H... out of driving with a joystick.

Quoted text (19 lines)

> I am conducting a fact finding mission on my own to try to resolve > this mysterious dilema with Nascar2 not allowing gameport devices to > My system: Mtech R528WP mb w/512k pb > Award Bios v4.51 Rev.Gu > 166mhz MMX, 32 meg EDO > Intergraph Reactor video > *Addonics Soundvision 500 <<Sound/gamecard > *Version (B) of Windows95 > *Devices which do not respond to Nascar2 under W95 > -T2 (Thrustmaster) > -Gravis Analog Joystick > -Gamepad (Reveal) > The items listed with a * in front are the most important for my > research. > Thank you, > Ron

Quoted text (9 lines)

>I am conducting a fact finding mission on my own to try to resolve >this mysterious dilema with Nascar2 not allowing gameport devices to >be calibrated while running under Windows 95. Please note that this is >not T2 specific but rather any joystick, gamepad, or wheel device >which works fine in other software under dos and/or w95, but will not >work with the combination of W95+N2. I am narrowing it down to a >possible problem with the Win95 (B) build but have yet to confirm. >Please include all vital system info you can in your response (s) and >if posting here as a followup, please email me also.

I have heard (but have not investigated) that Win95(b) has a different virtual joysick device driver... Why this is the case, I have no idea... ---Jim Sokoloff, Papyrus

The Sierra 'Nascar Forum' mentions the problem IS related to the WIN 95B version. http://www.sierra.com/support Go to the forums section and check out tech support sims and nascar forum. Good Luck, Alan http://www.infochase.com/games/simshop

Quoted text (9 lines)

> I am conducting a fact finding mission on my own to try to resolve > this mysterious dilema with Nascar2 not allowing gameport devices to > be calibrated while running under Windows 95. Please note that this is > not T2 specific but rather any joystick, gamepad, or wheel device > which works fine in other software under dos and/or w95, but will not > work with the combination of W95+N2. I am narrowing it down to a > possible problem with the Win95 (B) build but have yet to confirm. > Please include all vital system info you can in your response (s) and > if posting here as a followup, please email me also.

Well, I am running the 'B' release (also known as OEM Service Release 2) and I work fine with N2 and my T1 in 95. I just have to make sure I have it set correctly in Control Panel, Joystick (or in my case because I have the drivers for the Sidewinder Game Pad loaded, Control Panel, *** Devices - maybe this might make a difference) If I ever have a problem with it, is is usually solved with a reboot. I don't know if this helps or hurts the possible explanations... RRoddy

Quoted text (22 lines)

> The Sierra 'Nascar Forum' mentions the problem IS related to the WIN 95B > version. > [link lost in import] > Go to the forums section and check out tech support sims and nascar > forum. > Good Luck, > Alan > [link lost in import] > > I am conducting a fact finding mission on my own to try to resolve > > this mysterious dilema with Nascar2 not allowing gameport devices to > > be calibrated while running under Windows 95. Please note that this is > > not T2 specific but rather any joystick, gamepad, or wheel device > > which works fine in other software under dos and/or w95, but will not > > work with the combination of W95+N2. I am narrowing it down to a > > possible problem with the Win95 (B) build but have yet to confirm. > > Please include all vital system info you can in your response (s) and > > if posting here as a followup, please email me also.

I use a Quickshot Professional Joystick model QS-123A. I have no problems using it with N2 under windows. The very first time I set up N2 it did not recognize it. I went into control panel, and recalibrated it, and it has never had a problem since. I have used it since N2 was released. I am thinking about getting a T2, but will probably wait until I hear that some of the bugs have been worked out of N2. -- > I am conducting a fact finding mission on my own to try to resolve > this mysterious dilema with Nascar2 not allowing gameport devices to > be calibrated while running under Windows 95. > My system: Mtech R528WP mb w/512k pb > Award Bios v4.51 Rev.Gu > 166mhz MMX, 32 meg EDO > Intergraph Reactor video > *Addonics Soundvision 500 <<Sound/gamecard > *Version (B) of Windows95 > *Devices which do not respond to Nascar2 under W95 > -T2 (Thrustmaster) > -Gravis Analog Joystick > -Gamepad (Reveal) > The items listed with a * in front are the most important for my > research. > Thank you, > Ron

What build of Win95 are you running? The problem seems to be with the OSR 2 build. Win95 recognizes the T1/T2/MS Sidewinder and will let me calibrate it, but none of these are available in N2 when running from Win95. This is using the Microsoft driver that came with Win95.

First off, thanks to everyone who has responded. I am convinced that the problem is with the W95 (b) version. Some of you have reported that your gameport device (s) work fine with N2 and W95 but without knowing if your running version (b) of W95, this means little as I too had no problem with the original W95 and N2 on my other system. My only question remains if the problem is soley the W95(b) or a certain combination of sound/gameport cards along with this. My next step is to try a dedicated gamecard such as the ACM. P.s.: For those of you that have reported success with your wheels, joysticks, and/or gamepads within W95 while running N2... Please check your W95 version build by right-clicking My Computer and selecting properties/General Tab. If the second line under the description area (System:) has the letter B after it, then you do infact have the B release which I believe is the problem. If it is (a), then you have the first W95 release. Ron

It can't be OSR2 in and of itself, as some people have their T2s working with it. More likely it's OSR2 related, but also dependent on another variable. Unfortunately this may not be as easy to determine as it may seem. I've seen two systems both with OSR2 and the T2 plugged into a SB16's Gameport. Interestingly enough one works, while the other doesn't. -- The IWCCCARS Project: Q & A Representative http://www.theuspits.com/iwcccars/index.html http://userwww.service.emory.edu/~ebusch/

: First off, thanks to everyone who has responded. I am convinced that : the problem is with the W95 (b) version. Some of you have reported : that your gameport device (s) work fine with N2 and W95 but without : knowing if your running version (b) of W95, this means little as I too : had no problem with the original W95 and N2 on my other system. My : only question remains if the problem is soley the W95(b) or a certain : combination of sound/gameport cards along with this. My next step is : to try a dedicated gamecard such as the ACM. : P.s.: For those of you that have reported success with your wheels, : joysticks, and/or gamepads within W95 while running N2... Please check : your W95 version build by right-clicking My Computer and selecting : properties/General Tab. If the second line under the description area : (System:) has the letter B after it, then you do infact have the B : release which I believe is the problem. If it is (a), then you have : the first W95 release. It might be nice to know also if the Win95b versions installed are legit. In other words was this a "new and clean" install or is it installed over a previous Win95a version. The registry has a way of keeping old hardware settings about even though new ones have been installed. There is a possibility that this is what is causing the problems with the joystick in some people's Win95b and not others. Of course this is pure speculation... -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

>First off, thanks to everyone who has responded. I am convinced that >the problem is with the W95 (b) version. Ok, last night I did a clean install of osr2 ( version 4.00.1111 ), using the the original joystick driver that came with 95, i cant calibrate in n2. So, i installed the software that came with my sidewinder pro, still doesnt work. Next ill try the ms *** devices software form the net. I dont think it'll help, since thats what i had before. I would really like to use it though, since it allows you to remap buttons. It would be nice to be able to assign functions to the base buttons, like alt b and alt L. On the subject, I get the same problems with nascar 1. In this case i'd love to assin\gn hawaii chat keys, like "pass high =====) " so i dont have to fumble for the keyboard. :-) As far as hardware goes, I've got a ms sidewinder pro plugged into the game port of a sound blaster sb32, there might be something in control panel to install a different driver to that device, Im lookin for something now. Will let yall know.

Quoted text (7 lines)

> It might be nice to know also if the Win95b versions installed are > legit. In other words was this a "new and clean" install or is it > installed over a previous Win95a version. The registry has a way of > keeping old hardware settings about even though new ones have been > installed. There is a possibility that this is what is causing the > problems with the joystick in some people's Win95b and not others. Of > course this is pure speculation...

REPLY: 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.

Quoted text (8 lines)

>First off, thanks to everyone who has responded. I am convinced that >the problem is with the W95 (b) version. Some of you have reported >that your gameport device (s) work fine with N2 and W95 but without >knowing if your running version (b) of W95, this means little as I too >had no problem with the original W95 and N2 on my other system. My >only question remains if the problem is soley the W95(b) or a certain >combination of sound/gameport cards along with this. My next step is >to try a dedicated gamecard such as the ACM.

Ron, thanks for your persistance in chasing down the joystick problems which appear to be occuring for some users running the OEM version of greatly appreciate any conclusions or clues which arise from the various people who've described their problems. With a bit of luck we might be able to figure out what is going on and either fix it or offer a workaround .. thanks again. Charlie Heath Papyrus

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

Quoted text (20 lines)

>> P.s.: For those of you that have reported success with your wheels, >> joysticks, and/or gamepads within W95 while running N2... Please check >> your W95 version build by right-clicking My Computer and selecting >> properties/General Tab. If the second line under the description area >> (System:) has the letter B after it, then you do infact have the B >> release which I believe is the problem. If it is (a), then you have >> the first W95 release. >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.

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...

Quoted text (30 lines)

> : First off, thanks to everyone who has responded. I am convinced that > : the problem is with the W95 (b) version. Some of you have reported > : that your gameport device (s) work fine with N2 and W95 but without > : knowing if your running version (b) of W95, this means little as I too > : had no problem with the original W95 and N2 on my other system. My > : only question remains if the problem is soley the W95(b) or a certain > : combination of sound/gameport cards along with this. My next step is > : to try a dedicated gamecard such as the ACM. > : P.s.: For those of you that have reported success with your wheels, > : joysticks, and/or gamepads within W95 while running N2... Please check > : your W95 version build by right-clicking My Computer and selecting > : properties/General Tab. If the second line under the description area > : (System:) has the letter B after it, then you do infact have the B > : release which I believe is the problem. If it is (a), then you have > : the first W95 release. > It might be nice to know also if the Win95b versions installed are > legit. In other words was this a "new and clean" install or is it > installed over a previous Win95a version. The registry has a way of > keeping old hardware settings about even though new ones have been > installed. There is a possibility that this is what is causing the > problems with the joystick in some people's Win95b and not others. Of > course this is pure speculation... > -- > **************************** Michael E. Carver ************************* > Upside out, or inside down...False alarm the only game in town. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

>It is a problem with win95b.... all we need now is to know how to fix >it,. >>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. Works okay for me, too, with OSR2/FAT32 and a T2. I'm using a cheap speed-selectable joystick card. 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. --