All,
I have a PC with Windows 7 Pro 64-bit. I have a Space Explorer USP plugged in and use it for use with both NX and CATIA V5. The PC is used by multiple users and is shut down at the end of each work day.
In the morning, when the first user of the day logs in, all works as it should. The Space Explorer initializes properly and the controller works for all applications. When the next user sits down and selects 'Switch User', the Space Explorer does not work for any application including the test applications within the 3DConnexion folder. Upon login for the second user, a pop-up states that the device cannot be found.
I have tried stopping and re-starting the drivers, but with no success. I tried remotly logging in as a super-user and logging off the previous user, but again, no luck. The only success I have had is re-booting the PC so each user logs in as the first. Not exactly the solution I was looking for.
It should be possible for several users to be logged on at the same time, each with access to the device, but I'm at a total loss as to how it might be done.
Does anyone know a workaround for this?
Thanks.
Space Explorer lost when switching user in W7-64
Moderator: Moderators
Re: Space Explorer lost when switching user in W7-64
Hello cstevens -
When the 3Dconnexion process [3dxsrv.exe] looses connection with the device - either by switching users, logging off or with a hard drive configured to shut down during sleep mode - the process needs to be stopped before the driver will be available to start again.
The way this is typically handled in a multi-user environment is to have each user start the driver after logging on and stop it before logging off. If a user does not stop the driver prior to logging off, the 3dxsrv.exe process needs to be ended in Task Manager.
The reason for the behavior is that the current 3Dconnexion software uses an executable that does not run until connection with the device is established.
For software that integrates with the OS rather than running as an .exe, you may be interested in following the progress of the beta driver.
----------------
Barbara
When the 3Dconnexion process [3dxsrv.exe] looses connection with the device - either by switching users, logging off or with a hard drive configured to shut down during sleep mode - the process needs to be stopped before the driver will be available to start again.
The way this is typically handled in a multi-user environment is to have each user start the driver after logging on and stop it before logging off. If a user does not stop the driver prior to logging off, the 3dxsrv.exe process needs to be ended in Task Manager.
The reason for the behavior is that the current 3Dconnexion software uses an executable that does not run until connection with the device is established.
For software that integrates with the OS rather than running as an .exe, you may be interested in following the progress of the beta driver.
----------------
Barbara