[b]EDIT 3: I seem to have solved the problem, at least under Windows XP. I just didn't edit my post here until now because I'm lazy. It seems that the trick to get Windows XP to detect the Orb is to, shortly after using "Scan for new devices" in the Device Manager, start pressing random buttons on the Orb. I haven't tested it in Windows 2000 yet. About the only problems I'm having right now are:
-the SpaceOrb is ALWAYS the primary controller; very annoying when a 4-axis joystick with HAT switch would be more convenient for some games
-I still get Spaceware ActiveX error 429, even with the new setup file (but that's for a different thread!)[/b]
[b]EDIT 2: Great, my legacy system stopped detecting my Orb again. This is just getting weird. I wonder why it always works fine under W98SE, but not under an NT-based OS...maybe I should order another SpaceOrb to use on both machines, and also find out if the problem is Orb-specific or system-specific.[/b] [b]EDIT: It turns out that my legacy machine now detects the SpaceOrb under Windows 2000. Why it suddenly does this, I do not know. Chances are my newer XP-based machine will also give satisfying results.[/b]
I tried it. The problem is that I just get a "The specified directory does not contain information about your hardware" message. You see, I don't get a "Found New Hardware" popup on boot, or anything in my Device Manager that says "Spaceball" or anything like that.
The weird thing is that it used to work fine, and only recently has it been doing this. I'm hoping there's a solution...just why would it act up when I'm going to try out other games like Independence War and Terminus? 6DoF games just don't feel right when you're not using a true 6DoF device like the SpaceOrb.