IBM OS/2 Joystick device driver.
Program is distributed as ZIP package: download to temporary directory and unpack to destination folder. See below for download link(s).
Following ones are the download links for manual installation:
OS/2 Joystick Device Driver v. 2.0 (24/7/2002, Jose Da Silva) | Readme/What's new |
Installing GAMEDD.SYS from GAMEDD2.ZIP:
---------------------------------------
1)Install IBM joystick GAMEDD.SYS files from IBM's JOYSTICK.ZIP.
2)Find IBM's GAMEDD.SYS file and replace it with this GAMEDD.SYS file.
3)If you need to insert options, then in your CONFIG.SYS file find the
line containing GAMEDD.SYS and add any options you may need. The normal
default line found in CONFIG.SYS (drive and directory may be different)
DEVICE=C:\OS2\GAMEDD.SYS
These are default values based on IBM's original GAMEDD.SYS and you do
not need to enter them. They are shown here as an example and this will
make GAMEDD.SYS function just like the line above:
DEVICE=C:\GAMEDD.SYS /P:201 /W:400 /C:1E
Defaults here are 2 analog joysticks on joystick Port201h with a Wait
of 400h polling checks maximum and a Calibration of 1Eh (or 30%).
This example allows two digital joysticks to work as if they are analog.
Gravis_Xterminator=joystick1, Microsoft_Sidewinder_Gamepad=joystick2,
and it was determined that the wait loop should be increased to 450 hex.
DEVICE=C:\GAMEDD.SYS /D1gx /D2mg /W:450
This example allows one digital joystick and one analog joystick.
Gravis_Xterminator=joystick1, Analog=joystick2, wait loop is default.
DEVICE=C:\GAMEDD.SYS /D1gx
This example shows two digital joysticks. Only joystick1 will be seen by
DOS and IBMcompatible mode because it is translated into a CH compatible
mode used by certain flying programs. Joystick2 can only be seen by the
extended joystick access instructions. It was determined that for this
computer that the wait loop could be decreased from 400h down to 250h.
DEVICE=C:\GAMEDD.SYS /D1gx /D2gp /CH /W:250
Options you can add in CONFIG.SYS:
----------------------------------
All these options take effect when you start your computer.
/P:hhhh (default is /P:201)
If you have an odd joystick port which uses port 301h or another location
you can use /P:hhhh where hhhh is the joystick I/O address (in hex).
/W:hhhh (default is /W:400)
Default built-in WAIT is 400hex wait loops.
With today's very fast computers, you might not find the joysticks because
your computer stops looking before the joystick finishes doing it's work.
Some joystick ports run as much as ten times faster or more in some cases.
Some computers may be very fast yet have a very slow joystick port. For
example, you can only see an ISA slot AWE32 soundcard up to 66000 times a
second maximum because that is how fast the card can run regardless of if
it is a 386 or a PentiumXYZ. On the other hand, if you have a PCI soundcard
installed, you will probably need to use this /W option to increase the wait
counter. This appears to be mostly a problem with analog joysticks where for
example one user reported having to use /W:1600 for their analog joysticks.
The value you require depends on what sound card and joystick you have.
If you have a fast joystick port, then you may find this tip helpful.
You may want to slowly increase this value in the config.sys file until
you finally get propper joystick values. You need to reset the computer
for the changes in the config.sys file to take effect. Suggestion is to
increase the /W: value in small increments like /W:600 /W:800 /W:A00 ....
You could put in something very large like /W:FFFF but it would put a huge
speed penalty on your computer and you may find your computer behaving
oddly since your computer will be ignoring all other processes while
waiting for a response from your joysticks. Joysticks are still a polled
device, so in other words /W:FFFF may be a bad idea.
For you speed demons out there... you may realize a pushbutton gamepad
will only go up to 200h or some small number....therefore you may want to
use a /W:250h to decrease the waiting time for non-existant joysticks.
Why waste time? Suggestion is about 20% more than maximum value your
joystick reports back.
Digital joysticks require time to fill the built in buffer, because they
are also a polled device. Follow the same steps above if you are getting
intermittent joystick readings.
Note: some digital joysticks run faster than the joystick port can handle,
therefore you may need to replace your joystick port in those cases.
For example, the Microsoft Sidewinder runs faster than a Creative Labs
AWE32-ISA-Slot soundcard joystick port, therefore you will get
intermittent output regardless of the /W option. Choose another faster
joystick port or choose a different digital joystick.
/C:hh (default is 30%, which in hex values is 1E)
You should center your joysticks before calling a program that uses the
joysticks. "Calibration" happens when the computer powers up, therefore
your joysticks should be centered before you power up your computer.
Calibration is a useful way of making an analog style joystick act like
a pushbutton gamepad. For the default of 30%, here is what you get using
the X-axis of 100,0=center as an example:
lower trip point becomes 100-30%=70, upper trip point becomes 100+30%=130.
0,0-----------100,0-----------200,0
| | |
70,0 100,0 130,0
<--lower->|<--center->|<-right->
50 | 100 | 150
When your joystick X-axis is within 70...130, the joystick returns 100,
and when your joystick X-axis is below 70, it returns 50, while above 130,
it will return 150.
To make your joystick appear more sensitive, try 10%=0A or 5%=5, and you
will notice that you do not need to move the joystick much to give a
digital response. A larger number means you need to move your stick more
before returning a lower/upper value. You are allowed to set the
calibration anywhere from 10% to 45% ( /C:A .... /C:2D in hex) otherwise
it is set to default of 30%.
Here is graphical examples of 45% and 10% calibration values for X-axis:
0,0-----------100,0-----------200,0
| | |
55,0 100,0 145,0
<--lower|<----center--->|right->
50 | 100 | 150
0,0-----------100,0-----------200,0
| | |
90,0 | 110,0
<-----lower->|<-c->|<-right---->
50 | 100 | 150
You can see this happen for JOYS_DOS.EXE by changing the "DOS SETTING" of
"GAME_DIGITAL_RESPONSE" to ON and "GAME_DIRECT_ACCESS" to OFF, then run
JOYS_DOS.EXE. Note, you must have GAMEVDD.SYS installed to simulate the
joystick port for DOS programs (see JOYSTICK.ZIP by IBM). Users with PCI
cards will have to have GAMEVDD.SYS installed if their joystick port is
set at a value that is not 201h.
/CH
Your Joystick1 appears as CH Flightstick for DOS & IBMver2.0 programs.
/TM
Your Joystick1 appears as Thrustmaster for DOS & IBMver2.0 programs.
/D1xx and /D2xx
Digital joystick1 or digital joystick2, you may mix & match some sticks.
These are the actual joysticks plugged into the joystick gameport:
/D1ch -- ----- Analog CH Flightstick Pro tested
/D1ch -- ----- Analog Thrustmaster need volunteer to test
/D1gb or /D2gb Gravis Blackhawk need volunteer to test
/D1gp or /D2gp Gravis Gamepad Pro tested
/D1gx or /D2gx Gravis Xterminator tested
/D1mg or /D2mg Microsoft Sidewinder Gamepad tested by Bret Johnson
These are DOS & IBMver2.0 output limits.
/D1xx options return 4 pushbuttons if no second joystick is attached.
/D1xx options return 2 pushbuttons if a second joystick is attached.
/D2xx options return 2 pushbuttons only.
Note: Current sidewinder algorithm re-writes own buffer space, therefore
do not install a second digital joystick as /D2xx. If you own 2 digital
joysticks then install sidewinder as /D2mg, for example /D1gx /D2mg works
fine. /D1mg /D2?? won't work. This routine will be re-written in future
so that this condition is fixed, but for now, enjoy.
PCI Soundcards And The Joystick Port Help Tips:
-----------------------------------------------
Some users have reported trouble installing the joystick driver on newer
PCI style sound cards versus the older ISA style sound cards. Here are a
few things that you need to consider. With the older ISA style sound cards
the joystick port usually is found at 201h, therefore you do not have to
use the /P:xxxx option since 201h is the default port location.
With some newer PCI sound cards, the joystick may be located at a much
higher address and you will need to use the /P:xxxx option to set it, for
example the address may be /P:DC00 or /P:EF00 or some other address.
Currently, I haven't written any programs to help you find this address,
but if you look for the latest SoundBlaster drivers, I believe there is a
utility included with it to help you find the location of the PCI joystick
port. If you have a PCI soundcard with a high joystick address, you need
to get IBM's GAMEVDD.SYS if you do not already have it (located on
JOYSTICK.ZIP) and install it on your computer to translate the GAMEDD.SYS
data to a virtual 201h address for DOS programs since DOS programs usually
expect to see 201h as a normal joystick address.
Some users have mentioned their PCI sound cards appear not to work at the
new PCI address. Testing the address is easier using an analog joystick or
gamepad. If you get pushbutton actions, then you have the correct /P:xxxx.
If the X/Y axis do not work correctly, then you need to fine tune the /W
option. One user mentioned having to change the /W option to /W:1600 to get
their joystick to work (use that as a suggestion since your computer and
joystick combination may need a different /W value to work).
Once the /P and /W options seem to work correctly, leave them as
is if you decide to later install digital joysticks. The /W option may be
something you want to consider because even though computers and PCI sound
cards run much faster, joysticks still require time to process. Follow the
/W option tips above to tune your port to minimize CPU wasted time.
Digital Style Joysticks And DOS Games:
--------------------------------------
DOS games are looking for generic style linear Joysticks and do not know
what to do with digital data even if your joystick port is viewable at
port 201h. You require IBM's GAMEVDD.SYS (see JOYSTICK.ZIP) to translate
GAMEDD.SYS information to DOS.
GAME$ Programming:
------------------
For those of you wishing to write programs to use the joystick port, you
may want to look at JOY_IBM.CPP for programming help. This example should
be compatible to IBM's JOYSTICK.ZIP driver of 1995, so it should help you
be compatible from 1995 up to today in terms of GAME$ access.
GAME$ Compatibility Chart:
--------------------------
There may be confusion due to the number of drivers existing for OS/2.
As of Feb 10, 2002, GAMEDD2.ZIP is backwards compatible with GAMEPORT.SYS,
GAMEPRT2.SYS, and IBM's GAMEDD.SYS device drivers. As of Feb 15, 2002 it
is mostly compatible with Vesa's GPP_DRIV.ZIP.
1989,1992 1999,2000
GAMEPT.ZIP GAMEPRT2.ZIP
GAMEPORT.SYS--->GAMEPRT2.SYS--------+
Frank Ivan Jose DaSilva | ^ 80286 or better
V -----------------
19??..1995 1999..2002 v 80386 or better
JOYSTICK.ZIP,JOYDOCS.ZIP GAMEDD2.ZIP
GAMEVDD.SYS-----+-------------->(use original GAMEVDD.SYS)
GAMEDD.SYS------|+------------->GAMEDD.SYS
IBM, ver2.0 || Jose Da Silva, Canada
|| 1999
|| GPP_DRIV.ZIP
|| EJOYOS2_V21.ZIP
|+->GAMEDD.SYS
+-->GAMEVDD.SYS
Vesa Jääskeläinen, Finland
History:
--------
Jul 24,2002 Tested /d1ch, /ch, /tm. Added /d1tm
Jul 22,2002 JOYS_DOS.EXE bugfix. JOYS_DOS.C source included
Mar 09,2002 Race condition bug fix for digital joysticks
Feb 15,2002 Added /d1ch, /ch, /tm options
Feb 10,2002 Now compatible with GPP_DRIV.ZIP instructions 21h,23h..28h
Nov 19,2001 Added JOY_IBM.CPP joystick.zip compatible programming example
Jun 28,2001 Button config /D1gp & /D2gp. DOS Digital Response fixes
Jun 12,2001 Tested/debugged /D1gp /D2gp /D2gx
Jul 16,2000 Now backwards compatible to GAMEPORT.SYS & GAMEPRT2.SYS
May 05,2000 Added /D1 and /D2 options for more digital joysticks
Mar 29,2000 Added /D1 option for Gravis Xterminator
Jan 13,2000 Added /C and /S option for Analog Joysticks
Dec 30,1999 Added /P and /W options
Files in GAMEDD2.ZIP:
---------------------
GAMEDD2.DOC = This file
GAMEDD.SYS = OS/2 Joystick Device driver (to replace IBM's GAMEDD.SYS)
JOY_PORT.CPP = Source code (GAMEPORT.SYS compatible, simple but nonstandard)
JOY_PORT.EXE = OS/2 test program (GAMEPORT.SYS compatible)
JOY_IBM.CPP = IBM <joyos2.h> compatible program example for programmers
JOYS_DOS.C = DOS test program source code
JOYS_DOS.EXE = DOS test program (must have GAMEVDD.SYS installed)
Thanks To These People For Their Help:
--------------------------------------
Feb 15,2002 Vesa Jääskeläinen for donation of his CHflightstick routines
used for the /d1ch and /ch options.
for donation of his gamedd.sys code to help further gamedd2
Sep 09,2001 Ruediger Ihle and Sander van Leeuwen for info on PCI soundcards
and showing info on how to connect joystick drivers to SBlive.
May 05,2000 Bret Johnson for his sidewinder routines of /D1mg and /D2mg.
Mar 29,2000 Vojtech Pavlik of SuSE labs (Linux joystick drivers fame) for
helping in digital algorithms for Gravis digital joysticks.
These are options /D1gp /D1gx /D1gb, /D2gp /D2gx and /D2gb.
Dec 30,1999 Jason Stefanovich for hosting the contest and website where
GAMEPRT2.ZIP and GAMEDD2.ZIP were initially located.
Minimum tested system: 486 computer at 40MHz
by J DaSilva, Silva@JoesCat.com, Jul22/2002 |
hobbes.nmsu.edu/download/pub/os2/system/drivers/misc/GAMEDD2_2002-07-24.zip | local copy | |
OS/2 Joystick Device Driver v. 1.2 (1/7/2000, Jose Da Silva) | Readme/What's new |
GAMEPRT2.SYS is an OS2 joystick interface driver.
It is an updated version of GAMEPORT.SYS.
--------------------
Installation:
1)Insert GAMEPRT2.SYS in your OS2 directory.
2)If you already have GAMEPORT.SYS installed, please change the
CONFIG.SYS file so that the line which has:
DEVICE=C:\OS2\GAMEPORT.SYS
...is changed to...
DEVICE=C:\OS2\GAMEPRT2.SYS
3)If you do not have GAMEPORT.SYS installed, then insert
DEVICE=C:\OS2\GAMEPRT2.SYS in your CONFIG.SYS file, where C is
likely the drive where your OS2 directory is found.
4)Add command line options if required, for example:
DEVICE=C:\OS2\GAMEPRT2.SYS <--default value
or
DEVICE=C:\OS2\GAMEPRT2.SYS /VB /P:201 /W:7D0 <--also default
Where:
/VB displays the gameport header at startup.
/P:hhhh is the joystick port (hhhh=hex address of port)
/W:hhhh is the wait run-a-way counter (hhhh=waiting time).
The joystick port is unlikely to be found at another location,
so the /P:201 is set as the default value.
The /W option may come in useful if you run a very fast computer
and find that the joystick can't be found.
If you can't find the joystick, I recommend increasing the value
of /W:hhhh a little at a time, don't put a large value like
/W:FFFF since you may find your computer running very slow.
For myself 7D0 as per the original program is more than adequate
since I get maximum values of 172 (so in my case I would want to
drop the value down to /W:1BC so that my machine doesn't sit idle
in the gameport polling loop).
If you want to set the /W option, then run JOY_PORT.EXE and move
your joystick back-n-forth to see what values come back. Then add
something like 10%-20% to the value as a safety margin to make sure
the joystick is read every time. For example, my gamepad gives a
maximum of 172, so /W:1BC is a good value.
--------------------
Who did what:
GAMEPORT.SYS by Frank Ivan, ICA Systems Group
See GAMEPT.ZIP for original GAMEPORT.SYS joystick driver
GAMEPRT2.SYS by Jose DaSilva, Vancouver, BC, Canada
based on GAMEPORT.SYS driver
GAMEPRT2.DOC = This file
GAMEPRT2.SYS = OS2 joystick device driver
GAMEPRT2.ASM = Updated version of GAMEPORT.ASM
GAMEPRT2.BAT = DOS batch file to create GAMEPRT2.SYS
JOY_PORT.EXE = Test program for GAMEPORT.SYS or GAMEPRT2.SYS
JOY_PORT.CPP = Example source code for JOY_PORT.EXE
--------------------
Compatibility Chart:
1989,1992 1999,2000
GAMEPT.ZIP GAMEPRT2.ZIP
GAMEPORT.SYS--->GAMEPRT2.SYS--------+
Frank Ivan Jose DaSilva | ^ 286 or better
V -----------
19??,1995 1999,2000 v 386 or better
JOYSTICK.ZIP,JOYDOCS.ZIP GAMEDD2.ZIP
GAMEDD.SYS--------------------->GAMEDD.SYS
GAMEVDD.SYS-------------------->(use original GAMEVDD.SYS)
IBM, ver2.0 Jose Da Silva
This chart lets you know that GAMEPRT2.SYS is compatible to
GAMEPORT.SYS, but not with the standard gameport driver
written by IBM named GAMEDD.SYS and GAMEVDD.SYS
GAMEDD.SYS located within GAMEDD2.ZIP is compatible with
GAMEPORT.SYS, GAMEPRT2.SYS and IBM's GAMEDD.SYS so if you
are running a machine better than a 80286, you may decide
to use the updated GAMEDD.SYS instead.
--------------------
History:
Jul 01,2000 1.2 update and add gameprt2.asm, Joy_Port.cpp
Jun 25,2000 Created Joy_Port.cpp to test GAMEPRT2.SYS
Jun 07,2000 Added compatibility chart to documentation
Dec 11,1999 1.1 Initial version 1.10 of GAMEPRT2.SYS
Have fun and enjoy |
hobbes.nmsu.edu/download/pub/os2/system/drivers/misc/Gameport2_1-2.zip | local copy | |
OS/2 Joystick Device Driver v. 1.0.0 (11/6/1996, International Business Machines Corporation (IBM)) | Readme/What's new |
!!!!!! IMPORTANT !!!!!!
BEFORE FURTHER UNZIPPING, UNPACKING OR USING ANY OF THE CODE
AND/OR DOCUMENTATION CONTAINED HEREIN, YOU MUST FIRST READ THE
LICENSE AGREEMENT THAT GOVERNS YOUR USE OF THE CODE AND
DOCUMENTATION. FURTHER UNZIPPING, UNPACKING OR USING THE CODE
AND/OR DOCUMENTATION INDICATES YOUR ACCEPTANCE OF THE TERMS
AND CONDITIONS OF THE LICENSE AGREEMENT. THE LICENSE
AGREEMENT IS CONTAINED IN THE LICENSE.TXT FILE.
Package README - GAMEDD.ZIP
This readme file contains information on how to install the GAMEDD.ZIP
joystick device driver package.
This OS/2 driver supports base joystick functions.
README.1ST CONTENTS:
1.0 SYSTEM REQUIREMENTS
2.0 INSTALLATION
3.0 PROBLEM DETERMINATION & TECHNICAL SUPPORT
4.0 DRIVERS.ZIP CONTENTS
5.0 TRADEMARKS
1.0 SYSTEM REQUIREMENTS
Before you install GAMEDD.ZIP, make sure that you have installed
OS/2 WARP Version 3.00 or later.
2.0 INSTALLATION
Having unzipped GAMEDD.ZIP, you should now perform the
the following steps:
1. Read LICENSE.PKG.
2. If you agree with the LICENSE terms and conditions, using PKUNZIP2,
unzip DRIVERS.ZIP.
3. Backup the unzipped files to diskette.
4. Follow the installation instructions found in the JOYSTICK.DOC file.
5. Upon installation of the joystick driver, shutdown OS/2 and REBOOT.
3.0 PROBLEM DETERMINATION & TECHNICAL SUPPORT
If you should experience any problems with this device driver, contact IBM
technical support (1-800-992-4777).
4.0 DRIVERS.ZIP CONTENTS
This package contains the following files:
- GAMEDD.SYS The actual device driver
- GAMEVDD.SYS The virtual device driver
- CONTROL.SCR
- JOYSTICK.SCR
- JOYSTICK.DOC The actual DD Readme
- JOYSTK.CH
- JOYSTK.ICO
5.0 TRADEMARKS
The following terms, denoted by an asterisk (*) in this file, are
trademarks or registered trademarks of IBM Corporation in
the United States and/or other countries:
IBM
OS/2
OS/2 JOYSTICK DEVICE DRIVER
This package contains:
o An OS/2 Joystick device driver
o This README file
You can:
o Use the Table of Contents to
help you locate specific topics.
o Use the Find option in the Edit menu of the
OS/2 System Editor to help you locate
specific information.
o Print the file.
IMPORTANT
PLEASE READ THE FOLLOWING TERMS AND CONDITIONS. YOUR
USE OF THE OS/2 JOYSTICK DEVICE DRIVER
INDICATES YOUR ACCEPTANCE OF THE FOLLOWING
TERMS AND CONDITIONS:
o YOU ARE A PRIOR LICENSEE OF OS/2.
o YOU MAY MAKE COPIES OF THE OS/2 JOYSTICK DEVICE DRIVER
EQUAL TO THE NUMBER OF LICENSED COPIES OF OS/2 YOU POSSESS.
o ALL OTHER TERMS AND CONDITIONS OF YOUR OS/2
LICENSE AGREEMENT APPLY TO THIS OS/2 JOYSTICK DEVICE
DRIVER; HOWEVER, THIS DOES NOT EXTEND ANY WARRANTY OUTLINED
IN SUCH AGREEMENT.
CONTENTS
________
1.0 Compatibility
2.0 Installation with MMPM/2 Installed
2.1 Installation without MMPM/2 Installed
3.0 Tested Joysticks
1.0 COMPATIBILITY
_____________
This device driver is compatible with OS/2 Warp 3.0
2.0 INSTALLATION WITH MMPM/2 INSTALLED
___________________________________
To install joystick support:
1. Make sure Joystick is physically connected to the Game Port or
Sound card.
2. Insert the OS/2 Joystick Device Driver diskette in drive A
3. Type MINSTALL at a command prompt.
4. Select the source drive; JOYSTICK SUPPORT is highlighted.
5. Press INSTALL.
The OS/2 Joystick Device Driver installation adds
the following statements to the CONFIG.SYS file:
DEVICE=X:\MMOS2\GAMEDD.SYS
DEVICE=X:\MMOS2\GAMEVDD.SYS
X: is the drive where MMPM/2 is installed
5. Shut down and then restart your computer for the Joystick
Device Driver to take effect.
2.1 INSTALLATION WITHOUT MMPM/2 INSTALLED
______________________________________
If MMPM/2 is not installed on the machine follow this procedure
to manually install the driver.
1. Make sure Joystick is physically connected to the Game Port or
Sound card.
2. Copy GAMEDD.SYS and GAMEVDD.SYS from this diskette to the
\OS2 directory of your boot drive.
3. Add the following statements to the end of your OS/2 CONFIG.SYS
DEVICE=X:\OS2\GAMEDD.SYS
DEVICE=X:\OS2\GAMEVDD.SYS
X: is the drive where OS/2 is installed
4. Shut down and then restart your computer for the Joystick Device
Driver to take effect.
3.0 TESTED JOYSTICKS
________________
Because joysticks use a generic interface, most joysticks should work.
The following joysticks have been tested with this driver:
Advance Gravis Analog Joystick
Advance Gravis GamePad
Advance Gravis Analog Pro
CH Products Flightstick
Dexxa Joystick ( Infrared )
Kraft Thunderstick
Logitech WingMan Extreme
Logitech Wingman
Thrustmaster XL Action Controller |
service.boulder.ibm.com/ps/products/os2/os2ddpak_cur/gamedd.zip | ||
OS/2 Joystick Device Driver v. 1.0 (27/9/1992, Frank Ivan) | Readme/What's new |
Gameport.sys is a small driver that samples the game port about
10 times per second. It also checks and debounces the switches.
To install Gameport.sys, just put a line in your config.sys as follows:
DEVICE=C:\OS2\GAMEPORT.SYS
and copy gameport.sys to the OS2 subdirectory.
To use it, just have your application open device GAME$ and issue
DevIOCtl calls using the file handle.
To Read the Joystick Status Issue A DevIOCtl call as Follows:
DosDevIOCtl(&stJoyStatus, NULL, 0x20, 0x80, shGameHandle);
Where shGameHandle is the handle returned from the open
and stJoyStatus is the status structure to be returned.
struct joystatus {
SHORT sJs_AxCnt; // A Joystick X position
SHORT sJs_AyCnt; // A Joystick Y position
SHORT sJs_BxCnt; // B Joystick X position
SHORT sJs_ByCnt; // B Joystick Y position
USHORT usJs_ButtonA1Cnt; // Button A1 Press Count
USHORT usJs_ButtonA2Cnt; // Button A2 Press Count
USHORT usJs_ButtonB1Cnt; // Button B1 Press Count
USHORT usJs_ButtonB2Cnt; // Button B2 Press Count
UCHAR ucJs_JoyStickMask; // Mask of Connected Joystick Pots
UCHAR ucJs_ButtonStatus; // Bits of Switches Down
LONG lJs_Ticks; // Total Clock Ticks (60 Hz)
} stJoyStatus;
To save time (with interrupts turned off), the driver only samples pots
that are connected. To get the driver to start sampling a channel again,
you can issue a DosDevIOCtl call passing it a mask with the bits set for the
channels you wish to resume sampling.
UCHAR ucNewMask;
ucNewMask = 0x01 // resume sampling Joystick A, Horz
DevIOCtl(NULL, &ucNewMask, 0x60, 0x80, shGameHandle);
Have fun and enjoy
Frank Ivan
ICA Systems Group
1949 Weybridge Lane
Reston Va. 22091
(703) 620-5835
[75300,1406] |
hobbes.nmsu.edu/download/pub/os2/system/drivers/misc/Gameport_1-0.zip | local copy |
This work is licensed under a Creative Commons Attribution 4.0 International License.
Add new comment