#Mouse Trouble?
8 messages in this thread
I'm configuring another 486/66 in the office to run 3DS. I can't get 3DS to
recognize the mouse. On startup, a cursor is drawn at the center of the
screen, but it doesn't move.
It's a real Microsoft serial mouse. It works fine under Windows with or
without MOUSE.SYS. I even installed MOUSE.SYS (v8.20) and MOUSE.INI properly,
and Microsoft's 'MSD' recognizes that a Microsoft serial mouse is on the serial
port. Nothing else regarding interrupts or ports is unusual.
The 3DS.SET file is set up for the mouse on the correct port. When I bring up
the Configure dialog and press 'A' for 'Area', it reports that it can't find
the device. What should I try next?
Try mouse.com in the autoexec.bat and that should fix it. I've seen a number of
systems that didn't allow 3DS to see the mouse when the mode was loaded into
the config.sys.
Paul
I tried running MOUSE.COM in the 'autoexec' instead of MOUSE.SYS in the
'config', and I get the same results… everyone else thinks the mouse is
there except for 3DS. I even tried the test program that came with another
mouse, and it said it was there.
YUCK!!!!!!
I've had various mouse problems with 3DS over the years but never anything like
that. The next obvious approach would be looking for a memory management
problem, but beyond just starting to try various combos, I unfortunately have
no suggestions.
Sorry ……. Paul
I was very confused last night… I was convinced I'd stripped the machine's
config and autoexec down to nothing (null files) and I'd run the MOUSE.COM and
still I'd get no movement.
This new office computer came with DOS 6.21, which I've never installed here
before, so I decided to re-install DOS 5.0 (as well as undergoing the tedious
"emergency repair" of the boot loader because this machine also has WinNT on
it.) Wow, even that didn't make it go away, but at least I could boot with
null config and autoexec and run MOUSE and I would get mouse movement. (I know
I was twiddling two variables at once here, but heh, I'm a scientist. 🙂
Through process of elimination on the autoexec, I discovered a line 'set
SERIALDEBUG=00' that had migrated from the autoexec on a development machine.
Yes, new rodent was on COM1. Yes, that machine was running 3DS v3.1.5 $$$.
Problem solved, left as an exercise to the IPAS-savvy reader. 🙂 It works
now. Gentle Public, suffice it to say that this bug will never appear on
consumer machines, it's a developer-specific virus. Jonas, add it to the log
book.
John,
Try Mouse.com as suggested. Also, does the Mouse work in other DOS
applications? Like EDIT? EDIT a file and see if you have mouse control in
there. If you don't then _no_ DOS app will have a mouse. If you do, then it is
a 3DS problem, and we can take it from there.
-Brian
Yes, the mouse works in Edit. I've at least proved that I can boot a minimal
floppy, run MOUSE.COM, and then 3DS will recognize the mouse. So now it'll just
be a long, boring process of trial and error to figure out where the conflict
might be… and I'll report after that's happened.