CompuServe Thread

#Mouse Probs in 3DS r.3

3 messages in this thread
#81928From: Joe Simons, AIAFeb 7, 1994 4:57 PM
Hmmmmm- I have a Graphics Ultra Pro 2MB. I guess that it is an OEM version, as it does NOT have a mouse port built into it. No big deal…..I like my serial mouse just fine. The problem is in running 3DS r.3, that have the built-in Vibrant drivers. Now, I have never had a problem with vibrant drivers, but get this: -If I set up the video to use ATI Ultra Pro, the resolutions and color depths test out fine, but when I go into Studio, No mouse. -If I use the ATI VGA Wnder XL, and DONT use the higher video modes (i.e. anything above 256 colors), the mouse works fine, but of course..what's the point? -Soooooo, I can only guess that the vibrant drivers expect the ATI Ultra Pro to have a bus mouse, and when it doesn't, 3DS load the woring mouse driver, and it doesn't work, BUT why does the mouse work with the ATI VideoWonder XL? That card also has a mouse port! Very Strange. BTW, my 3DS.set file does have the com-port setting to the correct port. Does Vibrant have new 3DS drivers (r.3) that will load separate from 3DS's vibrant drivers. As it is, I have a $400 card that can only perform like a $100 card (and still have mouse support). Thanks in advance- Joe
#81963From: Yost GroupFeb 7, 1994 7:09 PM
Bizarre. The Vibrant drivers do NOT require a mouse port on the ATI Ultra Pro, so that's not it. This is a first for me. I hope one of the hardware experts here on the forum have some ideas for you. – G
#82128From: Conrad StolzeFeb 8, 1994 1:50 AM
You may be having an interrupt or I/O base problem. Is by any chance your mouse using COM 3 or 4? You see, the ULTRA pro's are an 8514 compatible and have always had problems with com's 3 or 4 (and subsequent IRQ's and I/O bases). When you configure for a WonderXL you are using the VGA circuitry of the chip, not the accelerator, and subsequently the problem doesn't show itself. Boot 3DS3 in Ultra Pro mode and you are using the MACH32 chip (8514 compatible) and no mouse. If you have windows, use the MSD.EXE program that is in your WINDOWS directory to see where the mouse driver is loading. If you have a conflict, try to move the mouse somewhere else. Any additional information on your setup (COM Ports, IRQ's etc. would help). Chuck