Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ogicse!cs.uoregon.edu!akm From: akm@cs.uoregon.edu (Anant Kartik Mithal) Newsgroups: comp.windows.ms.programmer Subject: Re: What the heck is this AUX device? Summary: com1:/aux/mouse/ox.sys conflict? Message-ID: <1991Feb4.182331.22995@cs.uoregon.edu> Date: 4 Feb 91 18:23:31 GMT References: <1991Jan31.182905.7337@javelin.es.com> <161@cf_su20.cf_su10.Sbi.COM> Sender: news@cs.uoregon.edu (Netnews Owner) Organization: Department of Computer Science, University of Oregon Lines: 24 In article <161@cf_su20.cf_su10.Sbi.COM> nee@cf_su14.Sbi.Com (Robert Nee) writes: >I would like to point something out to programmers with a >second monitor. If you run the device driver OX.SYS then >you can tell the SDK spy application to route it's output >to COM1 a.k.a AUX a.k.a your second monitor. This is >very helpful and I use it alot. Two questions. First, I have my mouse on Com1:, will using OX.sys screw the mouse up? Second, is OX.sys part of the SDK? If so, where is it documented in the SDK? If not, where can one get it from? cheers! kartik -- Anant Kartik Mithal akm@cs.uoregon.edu Research Assistant, (503)346-4408 (msgs) Department of Computer Science, (503)346-3989 (direct) University of Oregon, Eugene, OR 97403-1202