Re: HELP: DOS - mouse problems under Windows 2000 on an IBM Laptop
Alan Pollack <[email protected]>
| Newsgroups | gmane.os.freedos.devel |
|---|---|
| Message-ID | <[email protected]> |
Thank you for your help, Arkady. As I recall CTMOUSE said nothing when it installed, other than those messages about not getting access to COM1 and COM4. Yes, I believe those error messages were from Windows. They appeared in a typical windows box, with an OK button, and said the program would be terminated because it could not read the COM ports. And thanks for the suggestion about partitioning. - alan ------------------------------------------------------------------------- X-Comment-To: Alan Pollack Hi! 29-Сен-2002 11:25 [email protected] (Alan Pollack) wrote to [email protected]: AP> I'm in trouble trying to use a DOS program under Windows 2000 on an IBM AP> Thinkpad 570E. Running under either COMMAND or CMD, my DOS program AP> starts fine. But it won't recognize the mouse, neither the built in AP> TrackPoint nor an extermal mouse. Windows 9x/Me presents for DOS programs access access to mouse through own drivers. I don't know if NT/2k/XP does same (although in theory they should). AP> I tried loading up CTMOUSE (version 2.0), There nothing guaranteed when running DOS mouse driver in Windows (9x or NT) DOS box. AP> but got error messages saying that CTMOUSE could not access COM1 or COM4. This message from Windows? AP> Running my program did seem slightly different, nonetheless, AP> after CTMOUSE was run: a mouse pointer appeared on the screen, although AP> but did not respond to the mouse movement, nor did mouse clicks do What CTMOUSE says when it installs? AP> anything. (Withour CTMOUSE running, no mouse pointer icon appears at AP> all on screen.) Any solution? Not enough information. If I right understand, both TrackPoint and external mouse are PS/2 devices? And CTMOUSE says something like "Installed at COM1 (03F8h/IRQ4) in Mouse Systems mode"? This mean that CTMOUSE not detects PS/2 mouse (as expected - Windows not givess access to devices which it controls itself) nor erial mouse and installs handlers at COM1 for Mouse Systems mode. All of this explained in CTMOUSE.TXT. Unfortunately, we can't help you in this case, you should install some other _Windows_ mouse drivers from IBM and/or external mouse manufacturer. AP> If there is no way to get the my DOS program to read a mouse under the AP> Windows 2000 DOS utility, Looks so. AP> maybe I can partition my hard drive to let me AP> boot from DOS at startup when I need to use the DOS program, and from AP> Windows 2000 at other times. If that's be best I can do, it would be AP> OK, as long as my program will then read the mouse or TrackPoint. I'd It should (through CTMOUSE or other DOS mouse driver). AP> even resort to booting from a DOS floppy if needed, if that works. But AP> here are my other problems: I don't know how to partition and use AP> multiple OS's; You should try Partition Magic from PowerQuest or Partition Commander from V communications - they allow nondestructive partitions management (resizing, moving, creating). After this you may use W2k bult-in boot manager to select which partition load at startup (see BOOT.INI file description). AP> and if resorting to floppy boot is the only option, I AP> don't seem to have a DOS system disk anywhere. AP> Can you help out this confused neophyte? (In the 60's and 70's I was a AP> programmer, but left the field and know nothing about the art of Windows AP> work.) 29-Сен-2002 12:52 [email protected] ([email protected]) wrote to [email protected]: pn> ctmouse will find the com port mouse correctly if you use the /v switch. There is another trouble and /V not helps for this. pn> Otherwise it will always find the PS2 (trackpoint) mouse pn> first and it is not supported under DOS. Who says "it not supported"? If it will be finded, then it will be supported. But it not finded (because W2k prevents this). pn> This worked for me. ---------- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [email protected]