I'm having a heck of a time trying to get a TSR mouse driver to work right on my IBM 5155, running MS-DOS 5. I have a 90's Microsoft serial mouse plugged into the serial port of an AST SixPackPlus card. It's the only serial port in the system, and so the card is configured as such - COM1 and IRQ4.
Windows 3.0 detects and works with the mouse with no issues. But I'm having problems getting other software, which relies on a TSR driver, to work. The two programs I'm testing with are EDIT and DOSSHELL. I've tried three different mouse drivers - MOUSE.COM, CTMOUSE 1.9.1, and CTMOUSE 2.1b4.
With MOUSE.COM, EDIT works just fine. When I attempt to run DOSSHELL however, it just switches the video to 40-column mode and immediately goes back to the C:\ prompt, with no message. Any attempt to run DOSSHELL thereafter results in the message "Unable to load MS-DOS Shell".
With CTMOUSE 1.9.1, DOSSHELL works just fine, but when I start EDIT, it does start, but there is no video. If I crank the CRT brightness up, I can see flickering, with no intelligible video. I can exit EDIT, but there remains no video - I have to reboot to solve it. Oddly enough, however, If I run DOSSHELL first, exit, and then run EDIT, EDIT appears and works just fine, mouse and all.
When I try to run CTMOUSE 2.1b4, it successfully finds the mouse, and then reports "Divide overflow". It then steals all of the system memory, and I have to reboot.
Anyone know what might be going on here? Again, Windows 3.0 works just fine with the mouse, out-of-box, and I've also tested it with MOUSE.COM running, and it still works just fine.
Windows 3.0 detects and works with the mouse with no issues. But I'm having problems getting other software, which relies on a TSR driver, to work. The two programs I'm testing with are EDIT and DOSSHELL. I've tried three different mouse drivers - MOUSE.COM, CTMOUSE 1.9.1, and CTMOUSE 2.1b4.
With MOUSE.COM, EDIT works just fine. When I attempt to run DOSSHELL however, it just switches the video to 40-column mode and immediately goes back to the C:\ prompt, with no message. Any attempt to run DOSSHELL thereafter results in the message "Unable to load MS-DOS Shell".
With CTMOUSE 1.9.1, DOSSHELL works just fine, but when I start EDIT, it does start, but there is no video. If I crank the CRT brightness up, I can see flickering, with no intelligible video. I can exit EDIT, but there remains no video - I have to reboot to solve it. Oddly enough, however, If I run DOSSHELL first, exit, and then run EDIT, EDIT appears and works just fine, mouse and all.
When I try to run CTMOUSE 2.1b4, it successfully finds the mouse, and then reports "Divide overflow". It then steals all of the system memory, and I have to reboot.
Anyone know what might be going on here? Again, Windows 3.0 works just fine with the mouse, out-of-box, and I've also tested it with MOUSE.COM running, and it still works just fine.