My device performs flawlessly. However, the driver does NOT autoload when windows boots up like it USED to. I tryed adding it to the start up programs path and all I get when windows boots is a missing .dll file? Even tried reinstalling and Updating... Still does not "Autoload".
Any help would be very appreciated. I REALLY enjoy this device and when I hit the Lottery I will purchase the Space Pilot Pro.
Release version: 3.8.1
Driver Version: 6.8.1
Firmware Version: 3.18
Thank you
Space Navigator NOT starting with windows
Moderator: Moderators
Re: Space Navigator NOT starting with windows
Hi Mudslung,
which DLL is missing? Did you search it on your machine?
Please enable the logging of the driver. This can be done in the 3Dconnexion control panel with "Tools -> Write Log File". Activate the Autostart and right after logging in take the logfile and post it here (if it is not too long). You will find it at: C:\Documents and Settings\<your_user_name>\Application Data\3Dconnexion\3DxWare
which DLL is missing? Did you search it on your machine?
Please enable the logging of the driver. This can be done in the 3Dconnexion control panel with "Tools -> Write Log File". Activate the Autostart and right after logging in take the logfile and post it here (if it is not too long). You will find it at: C:\Documents and Settings\<your_user_name>\Application Data\3Dconnexion\3DxWare
Uta
3Dconnexion
3Dconnexion
"Activate Autostart" I don't see this option Anywhere?
11:6:39.213: 3DxWare driver startup: 11/2/2009 11:6:39
11:6:39.214: 3DxWare Driver Version 6.8.1 : September 25, 2009
11:6:39.214: -quiet -- disabled
11:6:39.215: -shutdown -- disabled
11:6:39.215: -protocol -- none given. All protocols enabled.
11:6:39.215: -com -- Disabled, using spcware.ini file settings.
11:6:39.216: -dev -- Disabled, using spcware.ini settings.
11:6:39.216: -eps disabled sending each event.
11:6:39.217: -log enabled
11:6:39.218: -logLevel ffffffff
11:6:39.218: -logFile C:\Users\Mudslung\AppData\Roaming\3Dconnexion\3DxWare\3DxWare.log
11:6:39.219: -searchWarnDlg not enabled
11:6:39.219: -showGUI enabled
11:6:39.219: -hideGUI not enabled
11:6:39.220: UdCtl: Attempting to find (ID=1033) 'English' locale in EN_US
11:6:39.220: UdCtl: Found resource DLL in C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\EN_US\3dxsrv.dll
11:6:39.225: UdCtl: initialization successful.
11:6:39.226: UdCtl: Attempting to open Any Device (-1) on USB.
11:6:39.227: UdCtl: Attempting to load device DLL: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdDev\HIDDev.dll
11:6:39.233: UdDev: Attempting to open 3Dx-supported HID device on USB
11:6:39.248: UdDev: Beeping the device
11:6:39.249: UdDev: SpaceNavigator opened
11:6:39.249: UdCtl: Using device layer Any Supported 3Dconnexion USB Device supporting 0xffffffff
11:6:39.250: UdCtl: Device 0 (Any Device(-1) on USB) -- enabled.
11:6:39.251: Device Type: 6
Num Buttons: 2
Num DOF: 6
CanBeep: 1
Device Name: SpaceNavigator
Port Name: USB
Firmware: HID Firmware Version 3.18
Version 3.18
Orientation 0
11:6:39.253: UdCtl: Attempting to load UI DLL: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdUi\udui.dll
11:6:39.259: UdUi->InitDLL: UI DLL Initializing
11:6:39.415: UdUi->SetOrientation: About to create windows.
11:6:39.590: SetOrientation: B4 ResetAppNameBox call
11:6:39.591: 11:6:39.599: SetOrientation: After ResetAppNameBox call
11:6:39.623: UdUi->SetOrientation: Windows Created.
11:6:39.624: UdCtl: UI (3DxWare UI v3.0) initialized.
11:6:39.627: UdUi->UdUiSetMode: SI_UI_ALL_CONTROLS
11:6:39.629: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\kbdtrans.dll.
11:6:39.631: kbdtrans: Keyboard transport layer initialization
11:6:39.631: kbdtrans: Function table load successful
11:6:39.633: kbdtrans: Sendkey.dll successfully loaded.
11:6:39.633: UdCtl: Transport DLL: kbdtrans.dll -- enabled
11:6:39.633: Name: Window Keypress 1.0
11:6:39.634: Protocol ID: 50
11:6:39.635: Event Mask: 0x100
11:6:39.636: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\mwmtrans.dll.
11:6:39.638: mwmtranslog - Messages were registered
11:6:39.639: mwmtranslog - Opened hidden window
11:6:39.642: Mwmtrans: Username: Mudslung
11:6:39.643: mwmtrans: MagellanRPCServerInterface: endpoint is Magellan3DController
11:6:39.643: mwmtrans.dll:UdTransInit: NOT Terminal Services Environment
11:6:39.644: UdCtl: Transport DLL: mwmtrans.dll -- enabled
11:6:39.644: Name: Windows Messaging
11:6:39.645: Protocol ID: 10
11:6:39.646: Event Mask: 0x76
11:6:39.650: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\pxytrans.dll.
11:6:39.654: Loading Proxy DLLs
11:6:39.655: UdCtl: Transport DLL: pxytrans.dll -- enabled
11:6:39.655: Name: Proxy
11:6:39.655: Protocol ID: 5
11:6:39.656: Event Mask: 0x76
11:6:39.657: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\s80trans.dll.
11:6:39.659: s80trans: SpaceWare 8.0 transport layer initialization
11:6:39.659: s80trans: Function table load successful
11:6:39.663: s80trans: Memory map loaded successfully
11:6:39.664: UdCtl: Transport DLL: s80trans.dll -- enabled
11:6:39.664: Name: SpaceWare 8.0
11:6:39.665: Protocol ID: 30
11:6:39.665: Event Mask: 0x76
11:6:39.666: UdCtl: numWaitHdls: 2 numTransHdls: 1 numDevHdls: 1
11:6:39.668: UdCtl: udfenNT.dll loaded sucessfully
11:7:35.310: UdCtl: Received WM_QUERYENDSESSION, shutting down.
11:7:35.315: UdCtl: Received WM_ENDSESSION, shutting down.
11:6:39.213: 3DxWare driver startup: 11/2/2009 11:6:39
11:6:39.214: 3DxWare Driver Version 6.8.1 : September 25, 2009
11:6:39.214: -quiet -- disabled
11:6:39.215: -shutdown -- disabled
11:6:39.215: -protocol -- none given. All protocols enabled.
11:6:39.215: -com -- Disabled, using spcware.ini file settings.
11:6:39.216: -dev -- Disabled, using spcware.ini settings.
11:6:39.216: -eps disabled sending each event.
11:6:39.217: -log enabled
11:6:39.218: -logLevel ffffffff
11:6:39.218: -logFile C:\Users\Mudslung\AppData\Roaming\3Dconnexion\3DxWare\3DxWare.log
11:6:39.219: -searchWarnDlg not enabled
11:6:39.219: -showGUI enabled
11:6:39.219: -hideGUI not enabled
11:6:39.220: UdCtl: Attempting to find (ID=1033) 'English' locale in EN_US
11:6:39.220: UdCtl: Found resource DLL in C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\EN_US\3dxsrv.dll
11:6:39.225: UdCtl: initialization successful.
11:6:39.226: UdCtl: Attempting to open Any Device (-1) on USB.
11:6:39.227: UdCtl: Attempting to load device DLL: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdDev\HIDDev.dll
11:6:39.233: UdDev: Attempting to open 3Dx-supported HID device on USB
11:6:39.248: UdDev: Beeping the device
11:6:39.249: UdDev: SpaceNavigator opened
11:6:39.249: UdCtl: Using device layer Any Supported 3Dconnexion USB Device supporting 0xffffffff
11:6:39.250: UdCtl: Device 0 (Any Device(-1) on USB) -- enabled.
11:6:39.251: Device Type: 6
Num Buttons: 2
Num DOF: 6
CanBeep: 1
Device Name: SpaceNavigator
Port Name: USB
Firmware: HID Firmware Version 3.18
Version 3.18
Orientation 0
11:6:39.253: UdCtl: Attempting to load UI DLL: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdUi\udui.dll
11:6:39.259: UdUi->InitDLL: UI DLL Initializing
11:6:39.415: UdUi->SetOrientation: About to create windows.
11:6:39.590: SetOrientation: B4 ResetAppNameBox call
11:6:39.591: 11:6:39.599: SetOrientation: After ResetAppNameBox call
11:6:39.623: UdUi->SetOrientation: Windows Created.
11:6:39.624: UdCtl: UI (3DxWare UI v3.0) initialized.
11:6:39.627: UdUi->UdUiSetMode: SI_UI_ALL_CONTROLS
11:6:39.629: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\kbdtrans.dll.
11:6:39.631: kbdtrans: Keyboard transport layer initialization
11:6:39.631: kbdtrans: Function table load successful
11:6:39.633: kbdtrans: Sendkey.dll successfully loaded.
11:6:39.633: UdCtl: Transport DLL: kbdtrans.dll -- enabled
11:6:39.633: Name: Window Keypress 1.0
11:6:39.634: Protocol ID: 50
11:6:39.635: Event Mask: 0x100
11:6:39.636: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\mwmtrans.dll.
11:6:39.638: mwmtranslog - Messages were registered
11:6:39.639: mwmtranslog - Opened hidden window
11:6:39.642: Mwmtrans: Username: Mudslung
11:6:39.643: mwmtrans: MagellanRPCServerInterface: endpoint is Magellan3DController
11:6:39.643: mwmtrans.dll:UdTransInit: NOT Terminal Services Environment
11:6:39.644: UdCtl: Transport DLL: mwmtrans.dll -- enabled
11:6:39.644: Name: Windows Messaging
11:6:39.645: Protocol ID: 10
11:6:39.646: Event Mask: 0x76
11:6:39.650: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\pxytrans.dll.
11:6:39.654: Loading Proxy DLLs
11:6:39.655: UdCtl: Transport DLL: pxytrans.dll -- enabled
11:6:39.655: Name: Proxy
11:6:39.655: Protocol ID: 5
11:6:39.656: Event Mask: 0x76
11:6:39.657: UdCtl: Attempting to load transport DLL C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\UdTrans\s80trans.dll.
11:6:39.659: s80trans: SpaceWare 8.0 transport layer initialization
11:6:39.659: s80trans: Function table load successful
11:6:39.663: s80trans: Memory map loaded successfully
11:6:39.664: UdCtl: Transport DLL: s80trans.dll -- enabled
11:6:39.664: Name: SpaceWare 8.0
11:6:39.665: Protocol ID: 30
11:6:39.665: Event Mask: 0x76
11:6:39.666: UdCtl: numWaitHdls: 2 numTransHdls: 1 numDevHdls: 1
11:6:39.668: UdCtl: udfenNT.dll loaded sucessfully
11:7:35.310: UdCtl: Received WM_QUERYENDSESSION, shutting down.
11:7:35.315: UdCtl: Received WM_ENDSESSION, shutting down.
Hmm ... this logfile looks good. 
The driver found the device and started. And it was stopped. Was this a start from the Startup folder while logging in?
No, there is no option "Activate Autostart". During installation a shortcut is saved in the Startup folder. You can create it by copying the "Start Driver" link from Start -> Programs -> 3Dconnexion -> 3Dconnexion 3DxWare to your Startup folder.
Or do a full uninstall and re-install of the driver.
Please let me know if you could solve the problem. If it continues to exist please post the full error message you get.
The driver found the device and started. And it was stopped. Was this a start from the Startup folder while logging in?No, there is no option "Activate Autostart". During installation a shortcut is saved in the Startup folder. You can create it by copying the "Start Driver" link from Start -> Programs -> 3Dconnexion -> 3Dconnexion 3DxWare to your Startup folder.
Or do a full uninstall and re-install of the driver.
Please let me know if you could solve the problem. If it continues to exist please post the full error message you get.
Uta
3Dconnexion
3Dconnexion
After initially installing the driver it was never placed in the startup folder, so I copied it there manually, thats when I received the missing .dll file. I then removed it and un-installed and did a fresh install, but again, it did not place it in the startup location again. I will try to manually set it again and see what happens, if I receive another error I will post it here.
Thank you very much for the rapid response and care for this issue. I love your product and will continue to support the 3dconnexion name.
Thank you forthe help.
Patrick
Thank you very much for the rapid response and care for this issue. I love your product and will continue to support the 3dconnexion name.
Thank you forthe help.
Patrick
Mudslung wrote:AHhhh... Works like a charm.
Thanks again for the help.
Good to hear that you could solve it. Enjoy the device!
Uta
3Dconnexion
3Dconnexion