From owner-cvs-all Sat Dec 2 12:58:50 2000 Delivered-To: cvs-all@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id D55DF37B401; Sat, 2 Dec 2000 12:58:44 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA50962; Sat, 2 Dec 2000 14:58:37 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 2 Dec 2000 14:58:36 -0600 (CST) From: Chris Dillon To: Kazutaka YOKOTA Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa psm.c In-Reply-To: <200012020346.MAA13647@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Dec 2000, Kazutaka YOKOTA wrote: > >My main problem is, I think, that I have a Microsoft Wheel Mouse > >attached to this KVM switch, which is then hooked up to yet another > >dual-user KVM switch, which has a regular old Logitech mouse for the > >other user station. If I switch between user stations on my primary > >Windows NT server, it also has sync problems, but it fairly quickly > >detects the problem and adjusts accordingly (Event Log entries > >actually show up to this effect). Now, if I switch back to using my > >workstation here with the Microsoft Wheel Mouse, and Windows NT still > >thinks it is talking to a Logitech mouse, it is going to screw with > >this mouse until it resets it again. At that point, if I switch back > >to my FreeBSD desktop is usually when I get the out-of-sync problems. > > Um, it's difficult to see exactly what configuration you have here. > Would you show me some sort of diagram showing how all these things > are connected? Best viewed with a fixed font, of course... KB/Monitor/MSWheelMousePS2 KB/Monitor/LogitechMousePS2 | | | /-------------\ | _____________|___________ | _________1__________2_________ | Belkin OmniCube 4port | * | Belkin OmniView 2userx8port| ^^|^^^^^^^^^^^^^^^^^^|^^^ | ^|^^^^^^^^^|^^^^^^^^|^^^^^^|^^ | \-----/ | | | | | | | | | FBSD4.2 FBSD2.2.8 FBSD3.5 FBSD4.2 NT4SP6a * = Cybex CAT5/UTP KVM Extender As you can see, in this situation, two different PS/2 mouse types can be presented to any of the machines on that 2x8 KVM switch, assuming it doesn't do some very complete mouse emulation. The NT4 box is the only one that is using the mouse, however, as the three FBSD boxen on it are keyboard-only. The FBSD4.2 box on the 4-port switch is my workstation, which needs a mouse. I only mentioned the above so that it might help some people understand what might be going on when this kind of thing happened. I don't know if there is any realistic software workaround that can be done in this situation, but NT seems to recover fairly well each time. I think the easiest thing to do in my case would be to make sure each mouse on the two consoles were the same type. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message