Is there any way to speed up the mouse? I could have
sworn I saw dozens of messages on this board about this
problem, but they have all since dissapeared!
On Tue, 03 Oct 2000 08:41:21 GMT, Rayiner <heliosc@aircor.net> wrote:
Is there any way to speed up the mouse? I could have
sworn I saw dozens of messages on this board about this
problem, but they have all since dissapeared!
OK. I’ve already posted this under a different thread, but this
title is better.
Here’s what I did to get better mouse speed… Perhaps a
more prominent expert can suggest a better way…
Find the command line for the current input driver
bash# ps | grep devi
The response is in the form of (thread id, parent thread id, command
line)
4333600 1 devi-hirun kbd fd -d/dev/kbd msoft fd -d /dev/ser1
Highlight the third field (beginning with devi-hirun) with the mouse
and ‘copy’ it.
Paste the old command line at the shell prompt, then add an option.
bash# devi-hirun kbd fd -d/dev/kbd msoft fd -d /dev/ser1 rel -G 3
(The reference page for devi-hirun gave me this option, you can use
the help menu under “utilities” to read it, or type “use devi-hirun”
at the shell prompt.)
Either way, the mouse should be 3 times as responsive now.
Kill the old input driver by thread number
bash# kill 4333600
At this point, I was happy with stuff. You might want to play with
other options as listed in the “use” equivalent to a manpage.
Rick Evans
Here’s what I did to get better mouse speed… Perhaps a
more prominent expert can suggest a better way…
Ouch…I tried that with a PS/2 port and the mouse got real flaky and popup
menus starting happening
without clicks and even when I tried to kill the new ‘devi-hirun’ and
restore the old it just crashed
the system…
Where are the options stored in the bootup?? I would expect them in a
sysinit.1 file or something but
after some searching I can’t seem to find the inputtrap which the docs say
start devi-hirun with the
right options…
Thanks…
~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
Ouch…I tried that with a PS/2 port and the mouse got real flaky and
popup
menus starting happening
without clicks and even when I tried to kill the new ‘devi-hirun’ and
restore the old it just crashed
the system…
Quick note: ***do NOT kill devi-hirun WITHOUT another copy running!! ***
If you kill it, your keyboard and mouse will not respond, so you must be
sure to either load the optional command line arguments in your local.rc
file or first execute devi-hirun a second time and THEN kill the old one. I
(stupidly) tried this the wrong way, and it totally nuked me. I’d also like
to note that you really, really do not want to put a new devi-hirun into
bootup unless you are 100% sure it’s going to work; otherwise (if booting
directly to the GUI) it will lock up waiting for response from input device
instead of giving you the login prompt. To fix this, you’d have to hit the
space bar at bootup, and a menu will appear; select the option to load
‘safely’ without the GUI, and you can fix the offending file(s).
Where are the options stored in the bootup?? I would expect them in a
sysinit.1 file or something but
after some searching I can’t seem to find the inputtrap which the docs say
start devi-hirun with the
right options…
When inquiring about the devc-ser8250 driver for serial ports, I was
informed by a QNX tech to create and use /etc/rc.d/rc.local for all such
bootup options/commands. For instance, my rc.local starts off by slaying
devc-ser8250 and starting up the new one.
Also, did you try using the command line supplied by Rick Evans? His
command line went:
devi-hirun kbd fd -d/dev/kbd msoft fd -d /dev/ser1
This is not necessarily what you want. It loads the driver for a
Microsoft-style mouse on serial port 1. If you’re using PS/2, you’ll have
to run over the docs on what options to use. I … haven’t perfected this
yet 
I usually end up losing my mouse in my experimentations. What I’ve
posted in here already has been a collection of my experiences in doing the
wrong things. chuckles
I hope some of this info helps. Blast me if not. 
–Charles
Here is the best way to change the mouse speed. I’m running QNX RTP.
- create /etc/config/trap/input.localhost
When you run the ph script file to start photon, it executes inputtrap.
Inputtrap first checks for a input.(node) file, if it exists, each line is
used as arguments for devi-hirun. If the file doesn’t exist it will detect
your input and loads devi-hirun accordingly.
- add your arguments to input.localhost. Here is what my file looks like
(yours might not be the same):
kbd fd -d/dev/kbd
ps2 kb -2 rel -G 2
Note: I put two lines in the file which loads devi-hirun twice. I had to do
this because when I used 1 line with rel -G 2, devi-hirun wouldn’t load and
I couldn’t do anything in photon, so I had to reboot. It could be a bug, I
don’t know, I got tired of rebooting to try and figure it out. If the
input.localhost file causes your kb or mouse not to work when photon starts,
all you have to do is restart, hit space bar and select 3, login and remove
the input.localhost file. Also putting devi-hirun in the rc.local script is
not the best way because if you don’t want to use photon, devi-hirun will
still be running the background probably trying to send information to
photon.