Understood. Mine is completely lacking in the skills required
to operate a real or virtual vehicle of any kind.
Regards,
---Wayne.
Understood. Mine is completely lacking in the skills required
to operate a real or virtual vehicle of any kind.
Regards,
---Wayne.
QAZ: (believe were talking about no joystick response when running N2 from
windows on a certain machines)
RADO:
REPLY:
Seems clear to me.
RADO:
QAZ:
RADO:
REPLY:
I'll still stand by what I say as a possibility. I have two systems that are
100% harware exact. One system had 95b the other 95. 95b would calibrate under
win '95 for the life of it. After a week of trying the obvious stuff. I
reinstalled 95 as this was the only system I had with 95b running. And it
worked for me, what can I say?
QAZ:
RADO:
REPLY:
Are you still having troubles?? Luck with computers is sometimes all we have.
Not all problems like the one were discussing is documented anywhere, so what
do you have left? Ok it's not luck it's just trying everything possible and
hoping that one of countless ideas comes through.
RADO:
REPLY:
Hold on I'm having no problem. This is getting like a Twighlight Zone episode.
I simply gave an idea on what the problem could be if somebody isn't getting a
joystick calibrated running N2 through '95B. I would like to add though that
I'm not using the adapter on any of my 4 systems, and they all are running
through Win 95. I believe you need the converter for Win '95 games and/or
calibrating the wheel inside of Win '95.
REPLY:
Then please tell me what was the problem with my system?? :)
You now for sure there isn't a particular setup in which win 95b could be
causing a problem with N2? Hey you might be right, I can't prove it, just a
possible lookse for someone with this problem in the future.
You can tell a diff. between TM ACM and SB joyport?
Q.B.M.
Hehehe...it'd sure help if you knew, 'cause that's probably the only OS
software difference between our base OS installations.
Win95 Operating System Release 2, Win95b, Win95 (Build 4.00.95.1111)
all=the same animal, and are only available OEM (supposedly..hehehe)
with new systems. The only difference on any two systems doing a default
install is whether they choose to use 16 or 32bit FAT if the disk is
unpartitioned. If you didn't specifically run FDISK, (re-)partition and
(re-)format prior to installation, you've probably just used the 16bit
FAT anyway without knowing.
I have it loaded on 3 seperate Win95 peer LANned systems in home and it
outperforms the original release by miles in terms of stability and
features. I've had it installed for several months now and thoroughly
flogged it...so I'm not speaking from an e***d new buyers academic
perspective. <G>
"some sytems (sic)" usually = a hardware problem...or "finger
trouble".<G>
Luck isn't what is required. Knowledge is, but thank you for the
spiritual benediction. <G>
I launch N2 either from a shortcut I've constructed on the desktop &
start menu which shuts down Win95 & launches N2 in an exclusive DOS 7.1
session, so I'm running under DOS 7.1 with only the Win95 stub in memory
which is inconsequential in terms of performance, or I simply boot from
an already launched exclusive DOS 7.1 session.
In both cases, my T2 has previously been set up *CORRECTLY*, calibrated
and tested in Win95 and again upon booting into DOS, set up, calibrated
and tested under TM's TMS.EXE prior to launching N2 where I have
similarly selected wheel (linear) & calibrated the unit. (Only
nescessary once upon install and setup of NASACAR2)
I am using the T2 signal/axis 'converter' which you need if you are
gonna' run ANY game with a T2 under Win95 be it release 1, or 2.
Are you using this, as if not this could be the source of your problem?
For instance Need For Speed SE won't even see your T2 if you don't have
this device. NASCAR2 should, but you won't get a reliable T2 response if
you are running in a Win95 virtual DOS window. Running under DOS without
the converter should be fine though.
I reiterate, the problem isn't Win 95b. BTW, I am also running the T2
through a TM ACM speed adjustable gamecard and not the port on my
(disabled) SB16PnP, although the SB16PnP seems to work 'reasonably' well
for the CH joystick connected to PC#2.
================================================
--- PC Support Fee Schedule ---
================================================ *
* AUD $---.50c/hr ...for pushing the button * *
* AUD $199.50c/hr ...for knowing which button to push *
- Keiron RADO, Brisbane, AUSTRALIA *