Well, I've tried a used Thrustmaster FLCS / WCS II /RCS on my DOS 6.2 Pentium 100 to play Strike Commander (CD version).

I use the Strike Commander FLCS script included with the Thrustmaster DOS software I've downloaded from the Thrusmaster Website, as well as the RT200 patch (for Pentium II and above; fast computers).

When I run Strike Commander, the intro and the menu worked fine. But when I started flying, the game just gave me a black screen with "Runtime Overflow Error" message.

What happened? What line should I modify in the scripts?

I am sure it wasn't joystick problem because my TM works fine as normal joystick (keyboard connector unplugged), and the script downloaded successfully. What's wrong?

I don't know whether this matters, but my joystick is plugged into a Soundblaster 16 Vibra. I also connect through Creative Labs' MIDI/joystick "split cable", but there is no MIDI device connected to the cable.

Is the split cable that caused the problem? I hope not. I hope it is possible to simultaneously connect both MIDI device and TM setup (with pedals) through the MIDI/joystick split cable.

Also, I just purchased a Yamaha DB50XG MIDI daughterboard from ebay, but I read that a plugged joystick can cause the daughterboard to mute. The workaround is to use a MIDI/joystick split cable; the one from Creative could be better.

So is it possible to have joystick/throttle/pedal setup through the MIDI/joystick split cable?

Many thanks.
-Kresh

Does the game run at all?

What does the script do?
Does it work in a texteditor?
Does it have any functions that generate a lot of keystrokes?

Yes, the intro and the menu works fine, but when I start flying, the error happened.


Basically it maps keyboard buttons to the chip inside the Thrustmaster. See, TM merely 'emulate' keyboard keystrokes; that's why it works in DOS and driver-less.


Yes.


Yes, a lot. Especially when using WCSII as digital throttle. See, in digital throttle mode, moving the throttle back and forth actually emulates the keys needed to increase and decrease the throttle with keyboard.

I suspect it is actually keyboard instead of joystick problems, because like I said, the Thrustmaster works fine as normal joystick (the keyboard connector is unplugged from the stick).

By the way, I'm not sure whether it is related or not, but the Creative 16 Vibra soundcard I use to connect my TM setup was dead shortly after. It was completely dead; not only the joystick port, but the entire sound card as well. When I rebooted my P-100 to Windows 95, the soundcard is not detected at all, as if there's no soundcard being plugged to the mobo.

I'm not sure whether it was the joystick setup that killed the soundcard, or the amplifier. See, after Strike Commander hung because of the "Runtime Overflow Error", I punched the reset button without turning off the power amp. Thus I got a loud 'DUB!' sound and everything went awry.

Thrustmaster made a patch for this I think.

http://ts.thrustmaster.com/eng/

You'll have to register in order to get the patch file for the WCS II.