by Ice Cream Jonsey » Mon May 13, 2024 9:01 am
So I think there were three "families" of DOS drivers for mice in the 1980s and early 1990s.
Logitcech, Microsoft and Mouse Systems. There may be more!
ctmouse.exe is meant to be a lightweight driver that gets you setup on any old mouse. What I saw is that they arranged flags to not look for Mouse Systems mice. I assume there is a good technical reason for this, so I won't get into it, but I did have that moment of realization where I was like, the goddamn driver everyone tells you to use intentionally doesn't look for the kind of pointing device I have.
Installing a driver from the Mouse Systems heritage works differently than the others. When I use cutemouse.exe or what I think is an era-specific driver from Mouse Systems specifically, code is clearly stored in RAM without checking that the actual mouse is there. I am not seeing any evidence in DOS that the trackball I bought works. But Fallout's installer won't work if it doesn't see a mouse attached... once I load the Mouse Driver driver, it will start, the mouse (trackball in my case) just doesn't do anything.
This Mouse Driver trackball DID work on Windows XP last night, via the serial port. So the device is fine. This makes me wonder if I am not interfacing with the hardware pins on the motherboard correctly. There are two UART ports on the motherboard for my DOS machine and I am assuming that they function as COM1 and COM2. To ensure that this is right, I could get a loopback device and a terminal program like ole PROCOMM or TELIX from the BBS days, and see that what I am typing is reflecting back. I guess that is my next step.
So I think there were three "families" of DOS drivers for mice in the 1980s and early 1990s.
Logitcech, Microsoft and Mouse Systems. There may be more!
ctmouse.exe is meant to be a lightweight driver that gets you setup on any old mouse. What I saw is that they arranged flags to [i]not[/i] look for Mouse Systems mice. I assume there is a good technical reason for this, so I won't get into it, but I did have that moment of realization where I was like, the goddamn driver everyone tells you to use intentionally doesn't look for the kind of pointing device I have.
Installing a driver from the Mouse Systems heritage works differently than the others. When I use cutemouse.exe or what I think is an era-specific driver from Mouse Systems specifically, code is clearly stored in RAM without checking that the actual mouse is there. I am not seeing any evidence in DOS that the trackball I bought works. But Fallout's installer won't work if it doesn't see a mouse attached... once I load the Mouse Driver driver, it will start, the mouse (trackball in my case) just doesn't do anything.
This Mouse Driver trackball DID work on Windows XP last night, via the serial port. So the device is fine. This makes me wonder if I am not interfacing with the hardware pins on the motherboard correctly. There are two UART ports on the motherboard for my DOS machine and I am assuming that they function as COM1 and COM2. To ensure that this is right, I could get a loopback device and a terminal program like ole PROCOMM or TELIX from the BBS days, and see that what I am typing is reflecting back. I guess that is my next step.