Stephen,
>>> I'm about to get a new system (133 mhz P5 & ET6000 vid. card)and am wondering:
>>> o With 133-200 mhz. Pentiums and Soundblaster 16 or 32 PnP
>>> soundcards, is a dedicated gamecard (e.g., TM or CH) really necessary?
>I was using my AWE32 in a P90, and had no problems with the built-in
>gameport.
>I recently upgraded to a P166, and using the same AWE32 card, I've
>been having lots of probs.
>In Grand Prix 2, it works fine. Then, in for eg. Screamer, the Y axis
>doesn't register.
>I would like to know wether a dedicated gamecard will solve these
>probs before forking out $39.
It will indeed, despite all you've read here. Used to be Creative Labs put
a paragraph in the back of the SB manuals that pretty much said the same thing.
If you are experiencing difficulty, then get a better game card and disable the
one on the SB card (although they hinted it was the software's fault and not
theirs. Couple years ago or so they removed that and said nothing except that
they admitted there could be problems with the game port on SB cards with high
speeds on the bus.
Lately, however, they seem to be saying everything is just 'hunky-dory' with the
SB game port. I haven't seen any changes to the design of it to suggest that
is true, of course, there is that:
"You CAN disable it in Win 3.1, and DOS (the SB pnp built into the motherboard
on some computers), but "Win 95 has a bug in it..." that won't allow you to
disable it...
Win 95 doesn't have a bug, it's pnp and it is detecting a pnp sound card with
a game port on it that CL did not put a hardware (jumper) provision to allow
you to disable it. Geeze, this is not a big deal CL.
Put a half cent jumper on the damned thing and the problem will go away. Blaming
it on a Win 95 bug is the wrong thing to do.
You will note that it will likely work fine as a game port for most software. But
sooner or later, the majority of people will run into games that have a joystick
routine that cannot work properly with a non speed-adjustable game card on a
sound card or multi i/o card - they simply do not reset fast enough (among
other things to work with some joystick routines.)
Never mind that the danged software's joystick routine is as much to blame for
this - it could be written to avoid this type problem and make speed adjustable
cards unnecessary in almost all situations. But, the fact of the matter is,
there are some games that do have joystick routines that lack this type of
attention.
The facts are:
1. The Creative Labs sound cards with game ports are excellent (the best IMHO)
sound cards that happen to have some shortcomings in the game port area - to wit:
a. Lack of a jumper to disable the pnp ones - that was extremely short sighted
IMHO.
b. Lack of high enough quality components or speed adjustability to allow ALL
users to get around problem joystick routines. Leaving this up to the software
companys is not a PRO-ACTIVE solution - it's an avoidance solution.
2. Many people can operate most games just fine with a sound card game port.
3. Many people cannot operate all games just fine with a sound card game port.
It ain't just the game port or the software - it's the whole danged system -
including the game port AND the software and how they work together with a
person's particular motherboard and what different cards he has in that system.
4. IF ALL software had the best joystick routines that handled every possible
problem that can arise in a joystick routine - motherboard (bus speed, power
levels, etc) - game port then speed adjustable game ports would be totally
unnecessary.
5. Think about it:
a. The joystick consists of wires, pots and buttons - nothing else affects the
game port - the extra electronics in the programmable ones only use the keyboard
line.
b. The game port has the electronic circuitry on it that controls how the stick
responds to the software's joystick routine and the signals it sends to the
game port.
c. The software's joystick routine has more to do with it than many people want
to admit, but it's natural for programmers who are excellent at doing graphics
and other things well to misunderstand how to interface with hardware properly.
Especially if they don't know that some game ports can reset too fast (or over
run the counter, among other things) on really fast computers and muck things
up they know should work perfectly well in their program code.
What this all adds up to is this:
In ThrustMaster's (and CH's - I've talked to them) tech support, a major share
of the problems we deal with every day are caused by people running a game
with a joystick or other controller (gamepad, whatever)on a sound card game port.
In fact, they are the biggest problem and have been for years. A speed
adjustable game card will solve about 90+ % of these problems.
Getting a pnp sound card with no hardware provision to disable it, thus forcing
the end-user to use the game port on it in Win 95 does not assist the problem
in any way - it simply makes it more difficult.
Calling it a "Win 95" bug does not help either. Adding a half a cent jumper
that allows the user to disable it if he chooses or finds he has a situation
where he needs to disable it would help.
It's that simple.
Buzz