Path: utzoo!utgpu!watmath!clyde!att!rutgers!bpa!cbmvax!uunet!portal!cup.portal.com!jxh From: jxh@cup.portal.com (Jim - Hickstein) Newsgroups: comp.sys.ibm.pc Subject: Re: IBM PS/2, OS/2, Mouse Message-ID: <12224@cup.portal.com> Date: 6 Dec 88 10:49:47 GMT References: <422@nvuxk.UUCP> Distribution: na Organization: The Portal System (TM) Lines: 32 You seem to be confusing the PS/2 mouse port with a serial port, such as COM1 or COM2. I am running MS OS/2 1.1 (PMSDK 1.05); I have a Mouse Systems (now MSC) PS/2 mouse; I configured things with mousea05.sys which, if you believe the comments in the distributed config.sys file, is for PS/2 mouse- port mice. Other files mousea0[0-4] are for: mousea00 = Mouse Systems mousea01 = Visi-On mousea02 = Microsoft serial mousea03 = Microsoft Bus mousea04 = Microsoft Inport on the AT. I also have a Mouse Systems serial mouse, but have never tried using it on this machine. I understand that the PS/2 mouse port is, indeed, serial in nature (at least at the connector), but is not the same as a "serial mouse," which, I assume, means one coming in COM1 or COM2. Interestingly, it doesn't need to know who made the PS/2 Mouse Port mouse: I surmise they are, dare I imagine, COMPATIBLE with one another and, even, with the IBM mouse. My office-mate has a Compaq 386S (80386SX inside) which has a PS/2-like mouse port, but something he installed assumed that, since it is an AT-class machine, it did not have such a port. Fortunately, one could override this assumption and everything works as it should. BTW, how's IBM OS/2 1.1SE? Did you get any header files such as pmwin.h or pmgpi.h? In short, how are you supposed to write programs for it? We paid the 3 kilobucks for the MS SDK (an embarassment of riches), but I'm dying to find out what the policy is going to be for the .h files and end users. -Jim Hickstein jxh@cup.portal.com ...!sun!portal!cup.portal.com "Hmmm. I musta taken a wrong toin at Albuquoique." -Bugs Bunny