Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uunet!zephyr.ens.tek.com!tektronix!nosun!qiclab!neighorn From: neighorn@qiclab.uucp (Steven C. Neighorn) Newsgroups: comp.windows.ms Subject: Re: Win3.0 vs. LogicTech Mice Message-ID: <1990Sep3.185220.367@qiclab.uucp> Date: 3 Sep 90 18:52:20 GMT References: <255@pb2esac.UUCP> <2169@lectroid.sw.stratus.com> Distribution: comp Organization: SCN Research/QIC Laboratories of Tigard Oregon Lines: 29 In article gokita@cadence.com (Glen Okita) writes: >Just some random thoughts... >DON'T load logimenu and click, all you need is the mouse driver for >the Logitech serial mouse to work with Windows. >Also, the mouse must be on COM1, and -- I don't know if this is >necessary -- but I edited my WIN.INI to set the baud rate for >COM1 to 2400. Absolutely right, and undocumented as far as I can find. I had a 19200 direct connection to another unix machine on COM1:, A logitech mouse on COM2:, and an internal modem on COM3:. Win 3.0 would come up *with* the mouse working about 1/3rd of the time. There seemed to be no rhyme or reason to when the mouse would work and when it would not work. Three-fingered salute, big-red-switch, nothing... Regardless of what I did before starting up Win3, mouse operation seemed random. The really frustrating thing was I could run programs like mtrack40 and Word Perfect 5.1 from inside windows and the mouse would work find and dandy - But other windows apps, nada. I switched the mouse to COM1: and the direct connection to COM2:, and I haven't had any mouse-related problems since. I think the key words in that last sentence are "mouse-related"... -- Steven C. Neighorn cse.ogi.edu!qiclab!neighorn OR neighorn@nosun.West.Sun.COM Sun Microsystems, Inc. "Where we DESIGN the Star Fighters that defend the 9900 SW Greenburg Road #240 frontier against Xur and the Ko-dan Armada" Portland, Oregon 97223 work: (503) 684-9001 / home: (503) 641-3469