![]() 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.
0 Comments
Leave a Reply. |