
J-Mouse device driver for OS/2 2.x VERSION 3.33

************************************************
To install J-Mouse for OS/2:

Boot OS/2 and then run setup.exe on this disk.

************************************************




Driver files:

KBD.SYS
	This is the actual driver.  This replaces the current keybard
	driver(KBD01.SYS or KBD02.SYS).  This contains the keyboard driver
	and the device dependent part of the mouse driver.  This file MUST
	relpace the one provided with OS/2 2.x; the name cannot change
	nor its location!  The orignal KBD01.SYS(KBD02.SYS) is renamed
	to KBD01.IBM(KBD02.IBM) (this can be changed).
	This file will typically be located in C:\OS2



Support files:
	The following files are typically placed in C:\OS2\JMOUSE

JMSETUP.EXE
	The OS/2 2.x PM GUI setup program.

JMSTART.EXE
	The program to initialize the J-Mouse driver for OS/2 2.x
	on boot up.  This command reads the JMOUSE.INI file and
	initialize the driver to that state.  There is a /d command
	line option to "debug" the JMOUSE.INI file.  The /d option
	just lists what the driver is being set to.

JMQUERY.EXE
	This program is like 'JMSTART /d' but does not read JMOUSE.INI
	and does not initialize the driver.  This just read and displays
	the current driver settings.

JMOUSE.INI
	This is the INI file for the OS/2 2.x J-Mouse driver.
	It should be compatible with the DOS and WINDOWS J-Mouse
	INI subsections.

JMSETUP.INF
	This is the help file for OS/2 2.x J-Mouse.

JMOUSE.TXT
	This contains the install log.

VMOUSE.SYS
	This is the Virtual Mouse driver for WIN-OS/2 and DOS BOXES.

README.1ST
	This file.


TBOOK.EXE
TBKBASE.DLL
TBKCOMP.DLL
TBKUTIL.DLL
	ToolBook and its DLLs.  This is the tutorial engine.
	The ToolBook and the J-Mouse tutorial run under WIN-OS/2.

JMDRV.DLL
	The WIN-OS/2 DLL that allows ToolBook to talk to the J-Mouse.

JMTUTOR.ICO
	The ICON for the J-Mouse tutorial.

JMTUTOR.TBK
	Instructions for ToolBook to do the J-Mouse tutorial.



KNOWN PROBLEMS:
	When running the J-Mouse tutorial, and the tutorial window covers
	another window, OS/2 will sometimes send the mouse button events
	to the covered window instead of the tutorial window.  The covered
	window's frame will come the foreground and it will have the focus,
	but the interior of the "covered" window will not be correct.  
	If this occurs, close the "covered" window and then set the
	focus back to the tutorial and continue.


Important IRQ information:

	The driver claims it is a bus mouse on IRQ 5 (the user can change this)
	with 3 buttons.  Thus when using WIN-OS/2 one needs to have the IRQ
	free or not have any other virtual devices claim the IRQ.

	*********************************************************************
	*******************  I M P O R A N T A N T  *************************
	*********************************************************************
	The J-Mouse does not use an additional interrupt!  However the
	Virtual DOS machine does, this affects both WIN-OS/2 and DOS BOXES.
	When selecting a VIRQ you are doing nothing to affect OS/2 and PM,
	but you are affecting WIN-OS/2 and DOS BOXES.  You need to make
	sure that VIRQs are unique.  The Virtual DOS machine uses a 1 to 1
	assignement of IRQs to VIRQs, and you are advised to select an unused
	IRQ as your VIRQ assignement.  If you NEVER run a DOS BOX or
	WIN-OS/2 then you can select any VIRQ you want since it will NEVER
	be used.  But be careful, you WILL probably run a DOS BOX or
	WIN-OS/2 even if you do think so or intend too.
	*********************************************************************


Miscellaneous:

	During install, if a MOUSE.SYS device line exists in the CONFIG.SYS
	file we assume there is already a mouse in the system and we install
	the J-Mouse as a secondary mouse, thus applications see the main
	mouse's information when requesting information on the mouse.
	If there was not a MOUSE.SYS device line we add one and set the
	J-Mouse as the primary mouse.

	MOUSE.SYS has several device dependent drivers in it; if
	one of these mice is used it must be the primary driver and
	present!  Thus one cannot boot with a serial mouse one time
	and not the next.

	ToolBook is a Windows application, thus it runs in WIN-OS/2.

	When running Windows applications, the J-Mouse does better if one
	uses WIN-OS/2 window - NOT full screen WIN-OS/2.  J-Mouse can be
	used in full screen WIN-OS/2 but the response does not feel as
	good.  Please try both and judge for yourself.


EXAMPLES from CONFIG.SYS:

no J-Mouse
	DEVICE=C:\OS2\MOUSE.SYS SERIAL=COM1

primary serial mouse, secondary J-Mouse
	DEVICE=C:\OS2\MOUSE.SYS SERIAL=COM1 STYPE=KBD$

primary J-Mouse
	DEVICE=C:\OS2\MOUSE.SYS TYPE=KBD$
