Discussion:
Problems with IBM's latest mouse driver (scroll wheel, 10.163)
(too old to reply)
Lars Erdmann
2007-05-10 23:09:38 UTC
Permalink
Hallo,

eCS 1.2R, Snap Build No: 505:

I experience complete system freezes when using that mouse driver. I
even have the impression that somehow the interrupts are left completely
disabled (CLI) as the keyboard also does not seem to do much at the
point of the freeze.
The bug is pretty random but it appears to be triggered by switching
back and forth between the PM session (where all PM progs and OS/2
windowed consoles run in) and OS/2 fullscreen sessions. As it is random,
it's either some timing glitch, an uninitialized variable in some driver
or not fully restored registers.
By the way: I am using an USB mouse with the corresponding USBMOUSE.SYS
(also 10.163).

Looking at the DDK code I have noticed that for USB mice, USBMOUSE.SYS
calls into MOUSE.SYS via the IDC entry point but instead of MOUSE.SYS
arming a context hook, MOUSE.SYS synchronously executes the call. Maybe
that is a problem ?

Is anyone else also experiencing this problem ?

Lars
Uwe Pilgram
2007-05-20 17:07:01 UTC
Permalink
Hi Lars,

I have some problems since I changed to a USB-mouse. I use versions 10.152 of USBMOUSE.SYS and
10.153 of MOUSE.SYS. These are from the "SingleMouse" (Release 1.3 dated 2004/09/14) package
distributed by IBMs Passport Advantage Maintenance for OS/2. My impression is, that after using the
USB-mouse the numbers of locked WPS has drastically increased. But in contrast to your experience my
system is never frozen. It is merely stuck in a WPS hang.

BTW: from where have you gotten version 10.163?

Regards
Uwe

-----------------
Post by Lars Erdmann
Hallo,
I experience complete system freezes when using that mouse driver. I
even have the impression that somehow the interrupts are left completely
disabled (CLI) as the keyboard also does not seem to do much at the
point of the freeze.
The bug is pretty random but it appears to be triggered by switching
back and forth between the PM session (where all PM progs and OS/2
windowed consoles run in) and OS/2 fullscreen sessions. As it is random,
it's either some timing glitch, an uninitialized variable in some driver
or not fully restored registers.
By the way: I am using an USB mouse with the corresponding USBMOUSE.SYS
(also 10.163).
Looking at the DDK code I have noticed that for USB mice, USBMOUSE.SYS
calls into MOUSE.SYS via the IDC entry point but instead of MOUSE.SYS
arming a context hook, MOUSE.SYS synchronously executes the call. Maybe
that is a problem ?
Is anyone else also experiencing this problem ?
Lars
Lars Erdmann
2007-05-20 23:22:59 UTC
Permalink
Post by Uwe Pilgram
Hi Lars,
I have some problems since I changed to a USB-mouse. I use versions
10.152 of USBMOUSE.SYS and 10.153 of MOUSE.SYS. These are from the
"SingleMouse" (Release 1.3 dated 2004/09/14) package distributed by IBMs
Passport Advantage Maintenance for OS/2. My impression is, that after
using the USB-mouse the numbers of locked WPS has drastically increased.
But in contrast to your experience my system is never frozen. It is
merely stuck in a WPS hang.
BTW: from where have you gotten version 10.163?
the latest eCS update (smd10163.zip). Jesus, the DDK code is a real mess
(but it seems to reflect about a fairly new version).
Well, in some way I also am mainly affected about the WPS failing big time.
The mouse driver is full of CLIs and STIs (disabling and enabling
interrupts) and I guess that at some point, there is a complete lockup.
What's even more, it registers with a bunch of other drivers, amongst
those the keyboard driver, to inject keyboard events when, for example,
the mouse wheel is used (for those apps that only process keyboard
events, for example).
I have the bad feeling that that code fails somehow as it runs with
interrupts completely disable during the whole generation of keyboard
events. I wonder how well that does for the system.

Lars
Peter Brown
2007-05-21 12:26:44 UTC
Permalink
Hi Lars and Uwe
Post by Lars Erdmann
Post by Uwe Pilgram
Hi Lars,
I have some problems since I changed to a USB-mouse. I use versions
10.152 of USBMOUSE.SYS and 10.153 of MOUSE.SYS. These are from the
"SingleMouse" (Release 1.3 dated 2004/09/14) package distributed by
IBMs Passport Advantage Maintenance for OS/2. My impression is, that
after using the USB-mouse the numbers of locked WPS has drastically
increased. But in contrast to your experience my system is never
frozen. It is merely stuck in a WPS hang.
BTW: from where have you gotten version 10.163?
the latest eCS update (smd10163.zip). Jesus, the DDK code is a real mess
(but it seems to reflect about a fairly new version).
Well, in some way I also am mainly affected about the WPS failing big time.
The mouse driver is full of CLIs and STIs (disabling and enabling
interrupts) and I guess that at some point, there is a complete lockup.
What's even more, it registers with a bunch of other drivers, amongst
those the keyboard driver, to inject keyboard events when, for example,
the mouse wheel is used (for those apps that only process keyboard
events, for example).
I have the bad feeling that that code fails somehow as it runs with
interrupts completely disable during the whole generation of keyboard
events. I wonder how well that does for the system.
Lars
You may want to try the amouse driver to see if it is an improvement - I
think it is. Click on the Software link here http://www.nbsoftware.de/

Regards

Pete
Lars Erdmann
2007-05-21 20:50:47 UTC
Permalink
Post by Peter Brown
Hi Lars and Uwe
Post by Lars Erdmann
Post by Uwe Pilgram
Hi Lars,
I have some problems since I changed to a USB-mouse. I use versions
10.152 of USBMOUSE.SYS and 10.153 of MOUSE.SYS. These are from the
"SingleMouse" (Release 1.3 dated 2004/09/14) package distributed by
IBMs Passport Advantage Maintenance for OS/2. My impression is, that
after using the USB-mouse the numbers of locked WPS has drastically
increased. But in contrast to your experience my system is never
frozen. It is merely stuck in a WPS hang.
BTW: from where have you gotten version 10.163?
the latest eCS update (smd10163.zip). Jesus, the DDK code is a real
mess (but it seems to reflect about a fairly new version).
Well, in some way I also am mainly affected about the WPS failing big time.
The mouse driver is full of CLIs and STIs (disabling and enabling
interrupts) and I guess that at some point, there is a complete
lockup. What's even more, it registers with a bunch of other drivers,
amongst those the keyboard driver, to inject keyboard events when, for
example, the mouse wheel is used (for those apps that only process
keyboard events, for example).
I have the bad feeling that that code fails somehow as it runs with
interrupts completely disable during the whole generation of keyboard
events. I wonder how well that does for the system.
Lars
You may want to try the amouse driver to see if it is an improvement - I
think it is. Click on the Software link here http://www.nbsoftware.de/
Yes, that's the driver I normally use. But currently, that driver also
fails for me (it generates a trap). The Amouse guys and me have spotted
the failing instruction and I have already sent a fix to them to
incorporate in Amouse.sys.
An additional problem seems to be that the last SNAP driver (build 505)
comes with a GRADD update that seems to have a bad influence on the
whole scenario that I have not been able to nail down yet, maybe in
conjunction with the key event injection code (there are so many cross
dependencies ...)
Maybe PMDD.SYS (the SINGLEQ$ driver) also does some bad things to the
system. That is the driver that draws the mouse cursor in PM session
(all PM apps and OS/2 windows apps) and its IDC (Inter device
communication) routine is called from within MOUSE.SYS / AMOUSE.SYS.

Lars
Peter Brown
2007-05-22 23:09:47 UTC
Permalink
Hi Lars
Post by Lars Erdmann
Post by Peter Brown
Hi Lars and Uwe
Post by Lars Erdmann
Post by Uwe Pilgram
Hi Lars,
I have some problems since I changed to a USB-mouse. I use versions
10.152 of USBMOUSE.SYS and 10.153 of MOUSE.SYS. These are from the
"SingleMouse" (Release 1.3 dated 2004/09/14) package distributed by
IBMs Passport Advantage Maintenance for OS/2. My impression is, that
after using the USB-mouse the numbers of locked WPS has drastically
increased. But in contrast to your experience my system is never
frozen. It is merely stuck in a WPS hang.
BTW: from where have you gotten version 10.163?
the latest eCS update (smd10163.zip). Jesus, the DDK code is a real
mess (but it seems to reflect about a fairly new version).
Well, in some way I also am mainly affected about the WPS failing big time.
The mouse driver is full of CLIs and STIs (disabling and enabling
interrupts) and I guess that at some point, there is a complete
lockup. What's even more, it registers with a bunch of other drivers,
amongst those the keyboard driver, to inject keyboard events when,
for example, the mouse wheel is used (for those apps that only
process keyboard events, for example).
I have the bad feeling that that code fails somehow as it runs with
interrupts completely disable during the whole generation of keyboard
events. I wonder how well that does for the system.
Lars
You may want to try the amouse driver to see if it is an improvement -
I think it is. Click on the Software link here http://www.nbsoftware.de/
Yes, that's the driver I normally use. But currently, that driver also
fails for me (it generates a trap). The Amouse guys and me have spotted
the failing instruction and I have already sent a fix to them to
incorporate in Amouse.sys.
An additional problem seems to be that the last SNAP driver (build 505)
comes with a GRADD update that seems to have a bad influence on the
whole scenario that I have not been able to nail down yet, maybe in
conjunction with the key event injection code (there are so many cross
dependencies ...)
Maybe PMDD.SYS (the SINGLEQ$ driver) also does some bad things to the
system. That is the driver that draws the mouse cursor in PM session
(all PM apps and OS/2 windows apps) and its IDC (Inter device
communication) routine is called from within MOUSE.SYS / AMOUSE.SYS.
Lars
I noticed something "funny" about mouse drivers a couple of years ago.

I usually use MultiDesk/2 to enable all my systems as multi-user, each
with their own Desktop.

Around about the time of eCS1.1 (MCP2) it became impossible to create
New User Desktops that included a mouse. All user Desktops boot from the
same configuration file as the original Desktop that does have a mouse.
All mouse related INI file entries seem to be present when compared to
the original Desktop INI files.

It seemed to me to be something that had changed in the mouse related
files and possibly also somewhere within SNAP.

Using the amouse driver when I create New User Desktops sometimes they
have a mouse, sometimes they don't and those that did have a mouse on
creation may not have the next time that Desktop is booted...

I have even tried creating those new User Desktops using the VGA driver
instead of SNAP but still had the same problem. Guess that takes the
SNAP code out of the equation but not any of the GRADD updates that SNAP
applied.


Interestingly if I Ctr-Alt-W to bring up Watchcat on a "mouseless
Desktop" the cursor can be controlled by the mouse...

Come to think of it I have also had a mouse in a winos2 session when the
eCS Desktop in use did not have a mouse...

Basically, something mouse related seems broken in comparison to Warp4
and eCS1 (MCP1). Yes, the trackball in use has not been changed at all
during that time so I know it is not a "hardware issue" - when I
switched from ps/2 to usb connection (I was using an adapter) shortly
after installing eCS1 there was no problem.

Hopefully you have found and fixed some part of the problem. Maybe my
vague description of mouse problems when trying to create New User
Desktops will help track down any other cause(s).

Regards

Pete
Dave Yeo
2007-05-23 01:38:00 UTC
Permalink
Post by Uwe Pilgram
Hi Lars
Post by Lars Erdmann
Post by Peter Brown
Hi Lars and Uwe
Post by Lars Erdmann
Post by Uwe Pilgram
Hi Lars,
I have some problems since I changed to a USB-mouse. I use versions
10.152 of USBMOUSE.SYS and 10.153 of MOUSE.SYS. These are from the
"SingleMouse" (Release 1.3 dated 2004/09/14) package distributed by
IBMs Passport Advantage Maintenance for OS/2. My impression is,
that after using the USB-mouse the numbers of locked WPS has
drastically increased. But in contrast to your experience my system
is never frozen. It is merely stuck in a WPS hang.
BTW: from where have you gotten version 10.163?
the latest eCS update (smd10163.zip). Jesus, the DDK code is a real
mess (but it seems to reflect about a fairly new version).
Well, in some way I also am mainly affected about the WPS failing big time.
The mouse driver is full of CLIs and STIs (disabling and enabling
interrupts) and I guess that at some point, there is a complete
lockup. What's even more, it registers with a bunch of other
drivers, amongst those the keyboard driver, to inject keyboard
events when, for example, the mouse wheel is used (for those apps
that only process keyboard events, for example).
I have the bad feeling that that code fails somehow as it runs with
interrupts completely disable during the whole generation of
keyboard events. I wonder how well that does for the system.
Lars
You may want to try the amouse driver to see if it is an improvement
- I think it is. Click on the Software link here
http://www.nbsoftware.de/
Yes, that's the driver I normally use. But currently, that driver also
fails for me (it generates a trap). The Amouse guys and me have
spotted the failing instruction and I have already sent a fix to them
to incorporate in Amouse.sys.
An additional problem seems to be that the last SNAP driver (build
505) comes with a GRADD update that seems to have a bad influence on
the whole scenario that I have not been able to nail down yet, maybe
in conjunction with the key event injection code (there are so many
cross dependencies ...)
Maybe PMDD.SYS (the SINGLEQ$ driver) also does some bad things to the
system. That is the driver that draws the mouse cursor in PM session
(all PM apps and OS/2 windows apps) and its IDC (Inter device
communication) routine is called from within MOUSE.SYS / AMOUSE.SYS.
Lars
I noticed something "funny" about mouse drivers a couple of years ago.
I usually use MultiDesk/2 to enable all my systems as multi-user, each
with their own Desktop.
Around about the time of eCS1.1 (MCP2) it became impossible to create
New User Desktops that included a mouse. All user Desktops boot from the
same configuration file as the original Desktop that does have a mouse.
All mouse related INI file entries seem to be present when compared to
the original Desktop INI files.
It seemed to me to be something that had changed in the mouse related
files and possibly also somewhere within SNAP.
Using the amouse driver when I create New User Desktops sometimes they
have a mouse, sometimes they don't and those that did have a mouse on
creation may not have the next time that Desktop is booted...
I have even tried creating those new User Desktops using the VGA driver
instead of SNAP but still had the same problem. Guess that takes the
SNAP code out of the equation but not any of the GRADD updates that SNAP
applied.
Interestingly if I Ctr-Alt-W to bring up Watchcat on a "mouseless
Desktop" the cursor can be controlled by the mouse...
Come to think of it I have also had a mouse in a winos2 session when the
eCS Desktop in use did not have a mouse...
Basically, something mouse related seems broken in comparison to Warp4
and eCS1 (MCP1). Yes, the trackball in use has not been changed at all
during that time so I know it is not a "hardware issue" - when I
switched from ps/2 to usb connection (I was using an adapter) shortly
after installing eCS1 there was no problem.
Hopefully you have found and fixed some part of the problem. Maybe my
vague description of mouse problems when trying to create New User
Desktops will help track down any other cause(s).
Regards
Pete
Sometimes when the mouse cursor is missing E.exe will bring it back.
Might be worth trying
Dave
Peter Brown
2007-05-23 18:23:32 UTC
Permalink
Hi Dave
Post by Dave Yeo
Post by Uwe Pilgram
Hi Lars
Post by Lars Erdmann
Post by Peter Brown
Hi Lars and Uwe
Post by Lars Erdmann
Post by Uwe Pilgram
Hi Lars,
I have some problems since I changed to a USB-mouse. I use
versions 10.152 of USBMOUSE.SYS and 10.153 of MOUSE.SYS. These are
from the "SingleMouse" (Release 1.3 dated 2004/09/14) package
distributed by IBMs Passport Advantage Maintenance for OS/2. My
impression is, that after using the USB-mouse the numbers of
locked WPS has drastically increased. But in contrast to your
experience my system is never frozen. It is merely stuck in a WPS
hang.
BTW: from where have you gotten version 10.163?
the latest eCS update (smd10163.zip). Jesus, the DDK code is a real
mess (but it seems to reflect about a fairly new version).
Well, in some way I also am mainly affected about the WPS failing big time.
The mouse driver is full of CLIs and STIs (disabling and enabling
interrupts) and I guess that at some point, there is a complete
lockup. What's even more, it registers with a bunch of other
drivers, amongst those the keyboard driver, to inject keyboard
events when, for example, the mouse wheel is used (for those apps
that only process keyboard events, for example).
I have the bad feeling that that code fails somehow as it runs with
interrupts completely disable during the whole generation of
keyboard events. I wonder how well that does for the system.
Lars
You may want to try the amouse driver to see if it is an improvement
- I think it is. Click on the Software link here
http://www.nbsoftware.de/
Yes, that's the driver I normally use. But currently, that driver
also fails for me (it generates a trap). The Amouse guys and me have
spotted the failing instruction and I have already sent a fix to them
to incorporate in Amouse.sys.
An additional problem seems to be that the last SNAP driver (build
505) comes with a GRADD update that seems to have a bad influence on
the whole scenario that I have not been able to nail down yet, maybe
in conjunction with the key event injection code (there are so many
cross dependencies ...)
Maybe PMDD.SYS (the SINGLEQ$ driver) also does some bad things to the
system. That is the driver that draws the mouse cursor in PM session
(all PM apps and OS/2 windows apps) and its IDC (Inter device
communication) routine is called from within MOUSE.SYS / AMOUSE.SYS.
Lars
I noticed something "funny" about mouse drivers a couple of years ago.
I usually use MultiDesk/2 to enable all my systems as multi-user, each
with their own Desktop.
Around about the time of eCS1.1 (MCP2) it became impossible to create
New User Desktops that included a mouse. All user Desktops boot from
the same configuration file as the original Desktop that does have a
mouse. All mouse related INI file entries seem to be present when
compared to the original Desktop INI files.
It seemed to me to be something that had changed in the mouse related
files and possibly also somewhere within SNAP.
Using the amouse driver when I create New User Desktops sometimes they
have a mouse, sometimes they don't and those that did have a mouse on
creation may not have the next time that Desktop is booted...
I have even tried creating those new User Desktops using the VGA
driver instead of SNAP but still had the same problem. Guess that
takes the SNAP code out of the equation but not any of the GRADD
updates that SNAP applied.
Interestingly if I Ctr-Alt-W to bring up Watchcat on a "mouseless
Desktop" the cursor can be controlled by the mouse...
Come to think of it I have also had a mouse in a winos2 session when
the eCS Desktop in use did not have a mouse...
Basically, something mouse related seems broken in comparison to Warp4
and eCS1 (MCP1). Yes, the trackball in use has not been changed at all
during that time so I know it is not a "hardware issue" - when I
switched from ps/2 to usb connection (I was using an adapter) shortly
after installing eCS1 there was no problem.
Hopefully you have found and fixed some part of the problem. Maybe my
vague description of mouse problems when trying to create New User
Desktops will help track down any other cause(s).
Regards
Pete
Sometimes when the mouse cursor is missing E.exe will bring it back.
Might be worth trying
Dave
Thanks for the thought but I've already established that most tricks do
not work including that 1 :-)

It seems to be a case of the Desktop does not know it has a mouse when
running 1 of the New User Desktops described above; not simply a case of
the cursor not visible. If I use the keyboard to Tab to a Desktop object
there is no RMB working which should work if the problem is only that
the cursor is missing.

Regards

Pete
Lars Erdmann
2007-06-04 19:43:35 UTC
Permalink
Peter Brown schrieb:


Hallo, never mind, it had nothing (or very little) to do with the mouse
driver. The IWF (Integrated Workframe) that comes with VAC3 was so
screwed up that it completely hung my system (obviously even with
disabled interrupts, my system was completely dead).
After reinstalling I had no more severe hangs (except for a single mouse
driver trap, but I know the failing location and cause).

Now to your problem:
it most likely is not a mouse driver problem. The reason for this is
that the graphic mouse cursor and the switch from one OS/2
windowed/PM/DOS windowed to another is entirely managed by PM because
all these apps run in a single session.
The mouse driver however only manages the mouse switch between sessions
(for example, it keeps track of the cursor position for each of these
individual sessions) and this only applies to OS/2 fullscreen/DOS
fullscreen/detached sessions.
Therefore the behaviour you describe (switching from PM to a detached
session or a DOS fullscreen/Windows fullscreen gives you an "alive and
kicking" mouse cursor) is a good indication that the mouse driver works.

Have you XWorkplace running ? Just for a test I would deinstall and see
if the problem goes away (XWorkplace is quickly reinstalled, I have done
it a couple of times).

Lars
Post by Peter Brown
I noticed something "funny" about mouse drivers a couple of years ago.
I usually use MultiDesk/2 to enable all my systems as multi-user, each
with their own Desktop.
Around about the time of eCS1.1 (MCP2) it became impossible to create
New User Desktops that included a mouse. All user Desktops boot from the
same configuration file as the original Desktop that does have a mouse.
All mouse related INI file entries seem to be present when compared to
the original Desktop INI files.
It seemed to me to be something that had changed in the mouse related
files and possibly also somewhere within SNAP.
Using the amouse driver when I create New User Desktops sometimes they
have a mouse, sometimes they don't and those that did have a mouse on
creation may not have the next time that Desktop is booted...
I have even tried creating those new User Desktops using the VGA driver
instead of SNAP but still had the same problem. Guess that takes the
SNAP code out of the equation but not any of the GRADD updates that SNAP
applied.
Interestingly if I Ctr-Alt-W to bring up Watchcat on a "mouseless
Desktop" the cursor can be controlled by the mouse...
Come to think of it I have also had a mouse in a winos2 session when the
eCS Desktop in use did not have a mouse...
Basically, something mouse related seems broken in comparison to Warp4
and eCS1 (MCP1). Yes, the trackball in use has not been changed at all
during that time so I know it is not a "hardware issue" - when I
switched from ps/2 to usb connection (I was using an adapter) shortly
after installing eCS1 there was no problem.
Hopefully you have found and fixed some part of the problem. Maybe my
vague description of mouse problems when trying to create New User
Desktops will help track down any other cause(s).
Regards
Pete
Peter Brown
2007-06-05 02:20:41 UTC
Permalink
Hi Lars
Post by Lars Erdmann
Hallo, never mind, it had nothing (or very little) to do with the mouse
driver. The IWF (Integrated Workframe) that comes with VAC3 was so
screwed up that it completely hung my system (obviously even with
disabled interrupts, my system was completely dead).
After reinstalling I had no more severe hangs (except for a single mouse
driver trap, but I know the failing location and cause).
Glad you have resolved the issue(s).
Post by Lars Erdmann
it most likely is not a mouse driver problem. The reason for this is
that the graphic mouse cursor and the switch from one OS/2
windowed/PM/DOS windowed to another is entirely managed by PM because
all these apps run in a single session.
The mouse driver however only manages the mouse switch between sessions
(for example, it keeps track of the cursor position for each of these
individual sessions) and this only applies to OS/2 fullscreen/DOS
fullscreen/detached sessions.
Therefore the behaviour you describe (switching from PM to a detached
session or a DOS fullscreen/Windows fullscreen gives you an "alive and
kicking" mouse cursor) is a good indication that the mouse driver works.
Yes, exactly what I thought.

Now, Why is the mouse missing from the OS/2(eCS) Desktop that is active?

It is not that the cursor has failed to appear. If that was the case
then RMB would still produce a popup menu. That simply does not happen.
As far as any extra user Desktops are concerned there is No Mouse.

If I use the keyboard to get into the System Setup and check the Mouse
object all appears to be fine and there should be a mouse...


As stated before there was no problem until sometime around the release
of eCS1.1 and the updates that included.
Post by Lars Erdmann
Have you XWorkplace running ? Just for a test I would deinstall and see
if the problem goes away (XWorkplace is quickly reinstalled, I have done
it a couple of times).
I installed it once a long time ago and did not like it so, No, no
e/xworkplace on this system.

Regards

Pete
Post by Lars Erdmann
Lars
Post by Peter Brown
I noticed something "funny" about mouse drivers a couple of years ago.
I usually use MultiDesk/2 to enable all my systems as multi-user, each
with their own Desktop.
Around about the time of eCS1.1 (MCP2) it became impossible to create
New User Desktops that included a mouse. All user Desktops boot from
the same configuration file as the original Desktop that does have a
mouse. All mouse related INI file entries seem to be present when
compared to the original Desktop INI files.
It seemed to me to be something that had changed in the mouse related
files and possibly also somewhere within SNAP.
Using the amouse driver when I create New User Desktops sometimes they
have a mouse, sometimes they don't and those that did have a mouse on
creation may not have the next time that Desktop is booted...
I have even tried creating those new User Desktops using the VGA
driver instead of SNAP but still had the same problem. Guess that
takes the SNAP code out of the equation but not any of the GRADD
updates that SNAP applied.
Interestingly if I Ctr-Alt-W to bring up Watchcat on a "mouseless
Desktop" the cursor can be controlled by the mouse...
Come to think of it I have also had a mouse in a winos2 session when
the eCS Desktop in use did not have a mouse...
Basically, something mouse related seems broken in comparison to Warp4
and eCS1 (MCP1). Yes, the trackball in use has not been changed at all
during that time so I know it is not a "hardware issue" - when I
switched from ps/2 to usb connection (I was using an adapter) shortly
after installing eCS1 there was no problem.
Hopefully you have found and fixed some part of the problem. Maybe my
vague description of mouse problems when trying to create New User
Desktops will help track down any other cause(s).
Regards
Pete
Loading...