Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: djgpp AT delorie DOT com Date: Tue, 6 Jan 1998 17:13:28 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Writting a mouse driver... looking for help (this isn't a FA In-reply-to: Precedence: bulk I taked this thread already started. I saw the Shawn's reply to Jeff that starts with: > From: Shawn Hargreaves > Jeff Weeks writes: > >I have a fair bit of mouse programming docs around here and I seem to > >remember that the mouse can be accessed from port 3F8. > > If it is a serial mouse, yes. But there are many other types of mice > that won't work if you bypass the standard driver in this way, and your > program will probably also cause problems with things like win95 that > emulate the int 0x33 driver but may not support raw serial access... [snipped] I agree with Shawn and I'll point a couple of things: 1) In a couple of years "COM-serial mouse" will be obsolete. Right now all the new Pentiums have PS/2 connectors and all the market is going in this direction (better because it leaves one free COM ;-). This interface is different. 2) Loose 95 blocks ANY kind of access to the COM port used by the mouse you'll get nothing from this port because Loose 95 will block it totally. This idea is only usefull if you plan to make DJGPP applications that will work in special machines that you can control. These machines won't run Loose 95 or any mouse driver and will have the COM-mouse thing ... that's very restrictive. SET ------------------------------------ 0 -------------------------------- Visit my home page: http://set-soft.home.ml.org/ or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013