#Mouse Probs in 3DS r.3
5 messages in this thread
Hi Chucky!
Long time no speck. Thanks for the reply; this problem has become very
puzzling to me. ATI has not responded to my message yet (a copy of what you
read), and Gary Yost doesn't believe it to be 3DS/ Vibrant related.
Worse yet is that David @ the Wichita Office had an OEM version of the card
also (his was in a Gateway 486-66vlb; mine in a WD 486-66vlb), and both of us
run our serial mouse on com 2; he did not seem to have a problem.
I clipboarded in MSD's report on my mouse, com ports, IRQ status, and device
drivers (BTW I did this shelled out of windows):
Microsoft Diagnostics version 2.00 2/08/94 10:21am Page 1
========================================================================
——————————- Mouse ———————————
Mouse Hardware: Logitech Serial Mouse
Driver Manufacturer: Microsoft
DOS Driver Type: Serial Mouse
Driver File Type: .COM File
DOS Driver Version: 7.04
Mouse IRQ: 3
Mouse COM Port: COM2:
Mouse COM Port Address: 02F8H
Number of Mouse Buttons: 2
Horizontal Sensitivity: 50
Mouse to Cursor Ratio: 1 : 1
Vertical Sensitivity: 50
Mouse to Cursor Ratio: 1 : 1
Threshold Speed: 50
Mouse Language: English
Microsoft Diagnostics version 2.00 2/08/94 11:19am Page 1
========================================================================
—————————– COM Ports ——————————-
COM1: COM2: COM3: COM4:
—– —– —– —–
Port Address 03F8H 02F8H 03E8H N/A
Baud Rate 2400 1200 2400
Parity None None None
Data Bits 8 7 8
Stop Bits 1 1 1
Carrier Detect (CD) No Yes No
Ring Indicator (RI) No Yes No
Data Set Ready (DSR) No No Yes
Clear To Send (CTS) No Yes Yes
UART Chip Used 8250 8250 16550AF
—————————– IRQ Status ——————————
IRQ Address Description Detected Handled By
— ——— —————- —————— —————-
0 D5F6:0000 Timer Click Yes Unknown
1 16E8:185A Keyboard Yes Block Device
2 1545:0057 Second 8
Joe,
The only thing I noticed was the data and parity settings on COM2. Do you
really need them set for 7,E,1? Seems a little strange.
Try running MSD from DOS, as I think Windows is "playing with the results".
Also, does your mouse die on COM1 also? Could be an interesting possibility
to try!
Chuck
Chuck-
How was your trip. From what I hear, you are not just nation-wide now but
international as well. Congrats! oh…………..
FYI – It was a com port problem (technically a user problem <g>). The mouse
worked fine on com1 & com3. After testing ports, I found that I did not have
com4 properly disabled. I did not notice this problem until I tried to use
higher video modes, and that was with 3DS r.3; To be honest, I am surprised the
video worked at all.
Check ya' later-
Joe
p.s. – your right, Windows MSD was different on com2 that was DOS'S MSD. I
cant explain it…….
Joe Dude,
If it's workin' now, we won't fix it!!!!
Shakin' off the jet lag,
Chuck
Hey Chuck!!
Hope your trip was great; you took your suntan lotion, right? <bg>
Joe