From owner-freebsd-current Tue Aug 14 9: 3:35 2001 Delivered-To: freebsd-current@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 2586B37B408 for ; Tue, 14 Aug 2001 09:03:27 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) 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 LAA23973; Tue, 14 Aug 2001 11:03:05 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 14 Aug 2001 11:03:04 -0500 (CDT) From: Chris Dillon To: Terry Lambert Cc: Kazutaka YOKOTA , Sean Kelly , Subject: Re: FreeBSD's aggressive keyboard probe/attach In-Reply-To: <3B77A796.7D4C22E0@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 13 Aug 2001, Terry Lambert wrote: > Chris Dillon wrote: > > Occasionally I'll have mouse sync problems when I switch between > > FreeBSD and NT when the NT box has had difference mice (wheel vs. > > non-wheel MS mice, apparently) used on it via the dual-user KVM > > switch. NT seems to handle that case fairly well by resetting the > > PS/2 port and/or the mouse (not sure which) and redetecting the mouse > > type. > > There is actually a Cybex-specific "Microsoft Knowledge Base" > article which discusses the registry setting you need to pound > on to make NT not attempt to detect the mouse wheel (FWIW). I've found it. This will apply to any case where you would want to disable the wheel mouse detection in NT. For archive purposes, here it is: http://support.microsoft.com/support/kb/articles/Q165/3/25.ASP > > FreeBSD doesn't like when NT has done that to the mouse, > > though, and spews sync errors when I switch back. Usually I can kill > > moused and restart it to fix the problem. > > The 0x8000 flag fixes exactly this problem! I see that this flag exists in -STABLE but is undocumented as of yet. I'll give it a try. Luckily this problem is not too common since I rarely use the second user on the other KVM switch. [...snip...] > > Hmm... I'll have to check, maybe thats why mine works. :-) > > Little square sticker with rounded corners on the bottom, about > 1/2" by 1/4", with just the version, e.g. "1.9"... The 4-port OmniCube on my desk only has version 1.5, but that probably doesn't matter (how would I upgrade it? I have a ROM burner). I can't find the firmware version on my OmniView Matrix. The only caveat with these two KVM switches hooked together is that it is a real PITA when I hit Scroll Lock twice to change consoles on the remote KVM that sometimes the local KVM will see the same sequence and think I want to change consoles on it instead. I wish there were a way to disable the keyboard shortcuts on the OmniCube and just use the front-panel button. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64 (Itanium), PowerPC, and ARM architectures under development - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message