From: "Mark C. Otto" <Mark_Otto@FWS.Gov>
To: 9fans@cse.psu.edu
Subject: [9fans] PS2 vs Com1 Mouse Problems
Date: Tue, 27 Feb 2001 09:08:49 -0500 [thread overview]
Message-ID: <3A9BB4F1.D1697CF0@FWS.Gov> (raw)
In-Reply-To: <200102010808.AAA00583@tammananny.tiger>
I made the mistake of having a PS2 mouse and a serial mouse hooked up at
different times during the install process (indecision and a dearth of 3-button
mice). My setup seems confused about which it has. If I run echo $mouseport, I
get the proper ps2, but aux/mouse -n $mouseport returns
aux/mouse: can't open #t/eiapsctl - file does not exist
From reading uart(3) p. 438, it seems to be treating the mouse as a serial
device and expecting $mouseport to be 0 or 1 in
bind -a #t/eia^$mouseport^ctl /dev
Not having a mouse or rio, this is hard to see where to correct this. Thanks
for any help.
Mark
next prev parent reply other threads:[~2001-02-27 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 11:27 [9fans] plan 9 wiki experiment Russ Cox
2001-02-01 8:08 ` Quinn Dunkan
2001-02-01 8:01 ` Dan Cross
[not found] ` <cross@math.psu.edu>
2001-02-01 19:38 ` Tom Duff
2001-02-05 18:55 ` Dan Cross
2001-02-14 21:43 ` [9fans] KFS Crash Mark C. Otto
2001-02-14 21:57 ` Scott Schwartz
2001-02-27 14:08 ` Mark C. Otto [this message]
2001-02-27 15:48 ` [9fans] PS2 vs Com1 Mouse Problems Mark C. Otto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A9BB4F1.D1697CF0@FWS.Gov \
--to=mark_otto@fws.gov \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).