\\Application Data\3Dconnexion and that under %appdata%\3Dconnexion) and 2 registry folders (HKCU\Software\3Dconnexion and HKLM\Software\3Dconnexion). In that case I would recommand to completely remove 3DxSoftware, remove 2 folders (. It can be that a previous installation had some settings which could cause problems in a newer installation. We would encourage the machine to be restarted without the 3dcontroller attached prior to the above correction to help pinpoint which device is added when the 3dcontroller is re-attached. Note: It is important not to disable devices critical to the operation of the operating system. Verify the operation of the 3dcontroller using one of the 3dxware demos. Note that the power MUST BE completely OFF prior to restarting the machine! A warm reboot may not correct the conflict!ġ2. Shutdown (turn OFF) and restart the machine. Note that Windows has placed a red X over the device entry icon.ġ1. Change the "Device usage:" pull-down box to "Do not use this device in the current hardware profile (disabled)"ġ0. Double-click the entry to load the device's property page.Ĩ.
Under the "Mouse and other pointing devices" category find a "Microsoft Serial BallPoint" or similar device entry.Ħ. The "Device Manager" can be displayed from the "Hardware" tab.ĥ. From the "Control Panel", launch the "System" window.Ĥ. Using the "Start" menu select "Settings" and launch the "Control Panel".ģ. Logon to the system using an account with Administrator privileges.Ģ. The difference is in the environment interface.ġ. The solution on Windows 2000/XP systems has the same concept as Windows NT. This effectively locks the COM port from use by other software applications like the 3dxware driver.
On some NT/2000/XP systems, mouse drivers incorrectly identify the Spaceball as a Ball Point Mouse or similar device on the COM port. The key seemed to be following the "Clean Uninstall" steps. I followed the instructions and was able to get the Spaceball working again. Our IT department had a couple documents about Device Manager Interference and Registry-edits from past troubles. At that point the PC stopped working with the 'ball at all (no UG, no Inventor, no CATIA). Unfortunately, driver 2.8.2 rejects the Spaceball 3000, but only after it ran the full install.
I searched these forums and found the "hack", and tried it. It had been working just fine on the PC, we installed SW 2008, and then the 'ball wouldn't work with it. I had a similar problem using a Spaceball 300 Serial.