*BSD News Article 19480


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!news!neon.house.gov!neon.house.gov!not-for-mail
From: dorian@neon.house.gov (Dorian Deane)
Newsgroups: comp.os.386bsd.questions
Subject: busmouse problems: bus vs PS/2-type
Followup-To: comp.os.386bsd.questions
Date: 13 Aug 1993 09:26:22 -0400
Organization: House Information Systems
Lines: 29
Distribution: world
Message-ID: <24g4pu$6vc@neon.house.gov>
NNTP-Posting-Host: neon.house.gov
Keywords: busmouse 386bsd


Has anyone had problems installing Sandi Donno's 386bsd port of 
Eric Forsberg's Microsoft Busmouse?  

I can't even get the test program (testmse.c) to open.  I get a
"device not configured" error.  As far as I know, I've done all
the right things, putting the code in the right places, recompiling,
etc.

My first question is simple:  should the Microsoft busmouse work
with the Microsoft PS/2 busmouse?  Are they one and the same thing?

The device driver uses inPort 0x23c as the primary and 0x238 as the
secondary.  Do these change for the PS/2 version?

Specifically, I have a Dell 450DE/2 DGX, which is an EISA bus machine.
The mouse is a Microsoft mouse with the little round (DIN 6)
connector on the back.  The documentation describes it as a true,
PS/2 compatible mouse, for what that's worth.  I'm running 386bsd 0.1.16

Any help would be much appreciated.  Replies by email, please, and I'll 
post a summary if there's any interest.

dorian

-- 
Dorian Deane  dorian@cobalt.house.gov
House Information Systems
Washington, DC  20515