To:	DJGPP AT SUN DOT SOE DOT CLARKSON DOT EDU, dj AT ctron DOT com
From:	A DOT APPLEYARD AT fs1 DOT mt DOT umist DOT ac DOT uk
Date:	25 Aug 93 13:32:50 GMT
Subject:	Gnu C and mouse

  I have go32 version 1.08, gcc version 2.2.2, gas version 1.38.1, bison
version 1.16, flex version 2.3.7.

  I have DOS 4.01: on booting it displays this (with blank lines removed):-
TANDON MS-DOS 4.01 DISK OPERATING SYSTEM - Rev. 1.1
(C) Copyright 1990 Tandon Corporation
Research Machines Ethernet-AT, Multi-Protocol Support
Version 1.00I
Copyright 1990 (c) Research Machines Ltd
C>ECHO OFF
Tandon MS-DOS  4.01
Microsoft (R) Mouse Driver Version 7.00
Copyright (C) Microsoft Corp. 1983-1989.  All rights reserved.
Mouse driver installed

  My C:\MOUSE directory is:-
directory c:\mouse\*.*, has 4 entries
mouse.com         26677 1990 Jan 18 12.34.38
mouse.drv          3667 1990 Jan 18 12.34.50
mouse.sys         26514 1990 Jan 18 12.35.06
os2mouse.sys      13028 1990 Jan 18 12.35.52
I have a 2-button Tandon serial mouse.

  I have experienced miscellaneous odd behaviour by djgpp and Gnu C++ programs
after a Gnu C++ program has activated the mouse:-
  - On testing today, sometimes djgpp stops without remark in compilation
after a previous Gnu C++ program has used the mouse, but after warm boot the
same program compiles OK.
  - After a call of 'GO32 A.OUT' has called the mouse, the next call of 'GO32
A.OUT' exits without entering the program which is in A.OUT; but if I type
'GO32 A.OUT' again at once it enters the program in A.OUT correctly.
  - On previous occasions I have had bouts of a big Gnu C++ program ignoring
those special keys (alt, F11, F12, etc) that on "ax=7, int21" return "0 and
then a number over 127", when the mouse is active.
  My remedy so far is not to use the mouse in Gnu C or Gnu C++ programs; but
this is unsatisfactory for me. So please anyone: Is this the fault of my DOS
4.01 or of djgpp? Which if any version of DOS or djgpp if any has this bug
been put right in?

- Raw text -