When I start Solidworks 2008, I normally (always now) get an error message stating that the driver could not be loaded.
If I attempt to run the 3DxWare control panel, nothing happens. If I try to start the driver from the start menu, nothing happens. The spaceball also does not seem to work with any application (tried Google earth and photoshop as well).
I have tried rebooting several times, both SW and my computer.
I'm running XP Pro, as an administrator on a computer that is only about 2 weeks old. The driver has only worked intermittently from the get go, but now it doesn't seem to work at all. I've tried uninstalling and reinstalling the driver a couple of times, to no avail. I'm using a Spaceball 5000 USB, not that the model should really make a difference for this problem.
Ideas? Any assistance would be greatly appreciated.
Thanks.
Unable to start driver
Moderator: Moderators
Hello Scott,
have you already tested the device on another computer? Which driver version are you running? If its also "dead" on the other computer after installing the latest drivers, you should contact our support.
have you already tested the device on another computer? Which driver version are you running? If its also "dead" on the other computer after installing the latest drivers, you should contact our support.
Robert Stadie
I've done some more checking and I saw that there was a USB device with a "?". I removed it and scanned for changes and it seems to recognize the device now. I will have to play around with this some more to find out if it's always becoming an unknown device, or if this fixed it for good.
I know I've had a similar problem in the past with another computer not liking it when I had a USB storage device and a certain USB camera attached at the same time, maybe this is a similar problem. I think I'll need to reboot a few times to tell for sure.
I know I've had a similar problem in the past with another computer not liking it when I had a USB storage device and a certain USB camera attached at the same time, maybe this is a similar problem. I think I'll need to reboot a few times to tell for sure.