#DEC Mouse & Windows 3.0
5 messages in this thread
OK Len, I edited the System.INI file and placed the name of my mouse
driver, DECMouse.sys in it. Now when I start windows, I immediataly get
the C:> prompt back and windows does not work. When I take the
DECMouse.sys line out of the file, windoews works again, but without the
mouse. Looks like it doesn't like my driver name.
I do not have a driver from "2.1" as you thought, rather this driver came
with PCSA version 3.0. When I place the PCSA installation disk in the
drive during the Windows set up process, it gives me the message, "Unable
to find driver." Even when I know the driver is physically located on the
disk and direcotory I specified.
I am stimied! Any ideas?
Mike,
If your driver's name is really decmouse.SYS then it's likely not a Windows
mouse driver at all, but rather a DOS mouse driver, i.e., meant to be
loaded in CONFIG.SYS. That would certainly explain Windows SETUP couldn't
find the mouse driver!
A Windows mouse driver is a totally different animal from a DOS mouse
driver.
You'll have more success with the Windows driver from 2.1. I take it that
version 3.0 of PCSA doesn't include Windows 3.0. Otherwise you would have
had a file named DECMOUSE.DRV at hand.
–Len
While we're on the subject, Len, how feasible would it be to write a
Microsoft Mouse DOS driver for the Rainbow?
Writing a mouse driver for DOS would probably be no trickier than writing
the one for Windows. The unknown is Code Blue, which might not be
altogether well-behaved. It could easily trash the mouse while reaching
for the printer port, for instance.
What DOS software did you hope to mouse on the Rainbow, Mike?
–Len
Mike,
GO VAXFORUM… PCSA is covered there, not here. This forum covers DEC
personal computers themselves, not the VAX integration products.
-Bill