paulb@minster.york.ac.uk (02/15/91)
Does anyone know how to get Windows to recognise the mouse when running in the DOS box? I can get ordinary programs to recognise it, but not windows. I assume that this is because Windows uses it's own mouse driver. Thanks, Paul +--------------------------+-----------------------------------------------+ |Paul Butcher | JANET: paulb@uk.ac.york.minster | |Dept. of Computer Science | EARN: paulb@minster.york.ac.uk | |University of York | UUNET: ..!uunet!mcsun!ukc!minster!paulb | |York YO1 5DD ENGLAND | ARPA: paulb%york.minster@nsfnet-relay.ac.uk | |Tel: (0904) 432760 | Alternative address: | | (+44 904) 432760 | PRAB1@uk.ac.york | +--------------------------+-----------------------------------------------+
goldman@mbcl.rutgers.edu (02/18/91)
In article <666630891.22483@minster.york.ac.uk>, paulb@minster.york.ac.uk writes: > Does anyone know how to get Windows to recognise the mouse when running > in the DOS box? I can get ordinary programs to recognise it, but not > windows. I assume that this is because Windows uses it's own mouse > driver. > > Thanks, > > Paul I've been able to get Windows to recognise a microsoft Inport mouse with its jumper set to COM3. Otherwise, I can't get Windows to recognise the mouse either. As an idea (one that I will probably try out too) how about reordering your config.sys so that com0X.sys line comes before the POINTDD section? I assume that you have noticed that, on boot, the COM0X.sys driver doesn't recognise the port to which the mouse is attached. Adrian -- Adrian Goldman | Internet: Goldman@MBCL.Rutgers.Edu Molecular Biology Computing Laboratory | Bitnet: Goldman@BioVAX Waksman Insitute, | Phone: (908) 932-4864 Rutgers University, | Fax: (908) 932-5735 Piscataway, NJ 08855 USA |
wbonner@eecs.wsu.edu (Wim Bonner) (02/19/91)
In article <316.27bfba96@mbcl.rutgers.edu> goldman@mbcl.rutgers.edu writes: >In article <666630891.22483@minster.york.ac.uk>, paulb@minster.york.ac.uk writes: >> Does anyone know how to get Windows to recognise the mouse when running >> in the DOS box? I can get ordinary programs to recognise it, but not >> windows. I assume that this is because Windows uses it's own mouse >> driver. > >I've been able to get Windows to recognise a microsoft Inport mouse with its >jumper set to COM3. Otherwise, I can't get Windows to recognise the mouse >either. As an idea (one that I will probably try out too) how about >reordering your config.sys so that com0X.sys line comes before the POINTDD >section? I assume that you have noticed that, on boot, the COM0X.sys driver >doesn't recognise the port to which the mouse is attached. A few things, If you want the mouse to work in PM, and your mouse is attached to a com port then you had better have the mouse stuff before any COM0x.sys line. The Inport mouse connects to a MS Mouse card, the jumpers on it allow you to select the interrupt the mouse is going to use. Did you mean that the mouse was using interrupt 3? I don't really think that the interrupt should make any difference in the DOS box, as if you are having any problems with the interrupt selection, it will usually show up before you ever get to the dos box. I know that with Version 1.1 of PM, if you ran things in VGA mode in the dos box, you didn't get mouse support. This had to do with limitations with PM. There may be similar problems with things running in super-vga mode in the dos box. (I don't run with a dos box myself so am not sure about this) When Windows was installed? Was it installed in the DOS Box, or was it installed in straight dos? I believe the install program recognizes that it is in the dos box, and may make some differences. Wim. -- | wbonner@yoda.eecs.wsu.edu | | 27313853@wsuvm1.csc.wsu.edu | | 27313853@Wsuvm1.BITNET | | 72561.3135@CompuServe.com |