When final shutdown dialog pops up the focus in on “Cancel”. You can’t
move it by any means, TAB or arrows. You can’t really cancel it either,
since Enter is ignored just as well. Have to use mouse.
I already had my RTP installation gone due to that, because my damned
mouse went berserk after switching betwen comps. So, I had to hit reset
and that corrupted DOS filesystem, thus it never booted again 
Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:
When final shutdown dialog pops up the focus in on “Cancel”. You can’t
move it by any means, TAB or arrows. You can’t really cancel it either,
since Enter is ignored just as well. Have to use mouse.I already had my RTP installation gone due to that, because my damned
mouse went berserk after switching betwen comps. So, I had to hit reset
and that corrupted DOS filesystem, thus it never booted again >
You know… if you went to QNXStart and got that devi-hirun that supports
wheel mice, your mouse wouldn’t go berzerk when you switched between
Windows and RTP anymore.
We’ll have official wheel mouse support for PS/2 mice as soon as I can
figure out how to keep it from screwing up people with USB mice that are
being emulated as PS/2 by the BIOS
pete@qnx.com wrote:
Igor Kovalenko <> Igor.Kovalenko@motorola.com> > wrote:
When final shutdown dialog pops up the focus in on “Cancel”. You can’t
move it by any means, TAB or arrows. You can’t really cancel it either,
since Enter is ignored just as well. Have to use mouse.I already had my RTP installation gone due to that, because my damned
mouse went berserk after switching betwen comps. So, I had to hit reset
and that corrupted DOS filesystem, thus it never booted again >You know… if you went to QNXStart and got that devi-hirun that supports
wheel mice, your mouse wouldn’t go berzerk when you switched between
Windows and RTP anymore.
Hmm. It is actually even worse. Mouse goes berzerk on every switch now,
NO exceptions.
Wheel works, although there is slight problem with applications. Neither
helpviewer nor voyager don’t set focus into view pane when they start,
so you have to click there before wheel works.
We’ll have official wheel mouse support for PS/2 mice as soon as I can
figure out how to keep it from screwing up people with USB mice that are
being emulated as PS/2 by the BIOS
I have USB mouse connected to PS/2 port through adapter.
Driver started as devi-hirun kbd fd -d/dev/kdb ps2 kb -2.
Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:
pete@qnx.com > wrote:
Hmm. It is actually even worse. Mouse goes berzerk on every switch now,
NO exceptions.
Interesting. I have a switchbox at home, and it works fine as long as
I use the wheel enabled devi-hirun. When I get home, I’ll email you what
kind of switchbox it is.
Packets from a wheel mouse are 4 bytes long. Packets from a non-wheel
mouse are three bytes long.
If RTP is expecting three byte packets and Windows sets your mouse to
send four byte packets, things aren’t going to work very well.
My suspicion is that when your switchbox switches the mouse, it actually
resets it or something. Windows is probably detecting this and reinitializing
the mouse, but we’re not.
I have USB mouse connected to PS/2 port through adapter.
Driver started as devi-hirun kbd fd -d/dev/kdb ps2 kb -2.
As long as the mouse is connected to the PS/2 port, wether with an adapter or
not, it’s really a PS/2 mouse.
pete@qnx.com wrote:
Igor Kovalenko <> Igor.Kovalenko@motorola.com> > wrote:
pete@qnx.com > wrote:Hmm. It is actually even worse. Mouse goes berzerk on every switch now,
NO exceptions.Interesting. I have a switchbox at home, and it works fine as long as
I use the wheel enabled devi-hirun. When I get home, I’ll email you what
kind of switchbox it is.Packets from a wheel mouse are 4 bytes long. Packets from a non-wheel
mouse are three bytes long.If RTP is expecting three byte packets and Windows sets your mouse to
send four byte packets, things aren’t going to work very well.
Perhaps. I did not install specific driver for that mouse on Windows
though. Standard PS/2 mouse driver works fine and wheel works too.
My suspicion is that when your switchbox switches the mouse, it actually
resets it or something. Windows is probably detecting this and reinitializing
the mouse, but we’re not.
There is noticeable delay before mouse starts responding when I switch
to Win98, but then it works fine. They probably indeed to something like
that. Why can’t RTP do the same?
Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:
pete@qnx.com > wrote:
Perhaps. I did not install specific driver for that mouse on Windows
though. Standard PS/2 mouse driver works fine and wheel works too.
If the wheel works, then it’s using the standard' four byte packet PS/2 driver and not the standard’ 3 byte packet PS/2 driver.
There is noticeable delay before mouse starts responding when I switch
to Win98, but then it works fine. They probably indeed to something like
that. Why can’t RTP do the same?
Lack of time and manpower. We plan to do that when we overhaul the Input
methodology.
pete@qnx.com wrote:
Igor Kovalenko <> Igor.Kovalenko@motorola.com> > wrote:
pete@qnx.com > wrote:Hmm. It is actually even worse. Mouse goes berzerk on every switch now,
NO exceptions.Interesting. I have a switchbox at home, and it works fine as long as
I use the wheel enabled devi-hirun. When I get home, I’ll email you what
kind of switchbox it is.
It’s a `Cybex’ switchbox.