(This txt file is the Thrustmaster TESTCARD.BAT file converted to be an explanation of GAMEPORT.EXE.) To use this program, simply unplug your ThrustMaster Mark II WCS and plug your ThrustMaster FCS or PFCS directly into one of the 15-pin connectors you see on the back of your computer. Then run GAMEPORT.EXE. GAMEPORT.EXE will check to see if it sees the FCS or PFCS at the connector you have plugged it into. If it does see it there, it will give you a warning that the card you have plugged your FCS or PFCS into is active and should be disabled if it is not the card you intend to use. YOU MUST DISABLE ALL GAME CARDS ON AN IBM COMPUTER THAT YOU DO NOT INTEND TO USE. This is a function of the way the IBM computer system was designed. Many systems come with a Multi I/O Card installed that includes a game card connector that is not very stable. These cards may be active in your system without you knowing it. You may even be doing fine using the card with a 2-button joystick. When you plug a multi-button joystick in you may have problems and may immediately assume it is the joystick that is creating the problem when it is due to more than one active game card. The extra game card that is active senses the presence of the first card and ATTEMPTS to disable itself by defaulting to the second joystick port. A multi-button joystick uses the second joystick port and this causes an immediate conflict between the two game cards as they both attempt to use the second joystick port. Do not assume you do not have this condition existing in your computer system. Half of our technical service calls are caused by this problem alone. Take the time to check it. It is an easy one-time test. Just look at the back of your computer and look for any connectors that you can plug a 15-pin joystick cable into. Then, test each one by plugging only your FCS or PFCS into that connector. Then run TESTCARD from the C&CC. TESTCARD will inform you if that card is active, but you MUST have plugged a joystick into it or TESTCARD will not see it. (For additional troubleshooting help, see TMSA.EXE and TMSA.TXT)