5
« on: 06:20 PM - 02/11/09 »
Just got my XIM360 yesterday and have been doing some configuration testing with it. I have observed today that while it works as it should when connected to my desktop PC, it does some very unusual things when connected to my laptop. Here's a rundown of the situation:
- I have a custom-built desktop PC which is about 5 years old. It's still running an old P4 processor paired with an Abit IC7 MAX3 motherboard. Power supply is 400w.
- My laptop is only 3 years old. It's a Dell Inspiron 6400 which my school bought for me.
- Both my desktop PC and my Xbox 360 are connected to the same monitor and are on the same desk. I have a KVM switch which allows me to select the video feed to the monitor. In this regard, I can have both my PC and 360 running at the same time so that my XIM software can be running on the desktop.
- For order of operations (which I have done since I built my first XIM), I power on the PC and have the KVM set so that the PC's images are being transmitted to the monitor. I then power on the 360, wait for the indicator on the front face to confirm that controller 1 (the XIM) is plugged in, and then I launch the XIM software. I then switch the KVM over to the 360 display.
- After reading about how to use the XIM 360's Deadzoner software, I realized that I was going to need to be able to see both displays at the same time in order to create configurations (i.e. accurate figure out the deadzone) for some of my games. To accomplish this, I installed the XIM 360 software on my laptop and went through the exact same installation procedures as I did with my desktop.
- When the XIM 360 is connected to the desktop PC, it works perfectly fine. However, when connected to the laptop, the first thing I noticed is that I could not power up the 360 by holding down the guide button. (Everything was powered off when this was done. I have tested to see if I could power on the 360 by doing this even when the XIM software is not running, and it works when it's plugged into my desktop.) After attempting this a few times, I finally just pushed the power button on the 360. It booted up, but just before going to the Dashboard, it suddenly rebooted. It did this 3 times before I pulled the XIM cable out of the 360. After the cable was pulled, the 360 did not reboot.
- I powered everything down and reconnected the XIM to the laptop. I then turned on the 360 by pressing its power button. It went to the Dashboard, but then the controls proceeded to go haywire and start selecting things that I was not doing. The XIM software was not running on my laptop, but the on screen display was going every which way. I could not manually "drive" the controller to make it stop, but I was pressing B furiously to try to get it to quit what it was doing. It eventually got into the Marketplace screen and attempted to buy something, but I hit the power button before a download was started.
- I unplugged the XIM from the laptop and connected it back to the desktop. I then pressed the Guide button on the controller, and the 360 came right on. I launched the XIM software, and it functioned normally.
- I powered down, reconnected everything back to the laptop, and tried to push the Guide button again. No dice. I pressed the 360's power button, and it booted up, went to the Dashboard, and then went crazy again.
- I have attempted to connect the XIM into all 4 USB ports on my laptop, thinking that this was a voltage issue. I've also connected the XIM into all 6 USB ports on my desktop. It works in every single port on the desktop, but none on the laptop.
- The laptop has been both unplugged running on battery and has also been plugged into its AC adapter. Same results both ways.
- The XIM has had its calibration program run with both the desktop and the laptop.
- I have gone back to connecting it to the laptop, and messed with some guesswork configurations for about 2 hours earlier. I see no indication that it's experiencing any kind of technical problems when connected to the desktop.
- I'm not sure what else to do here. I feel like I've been pretty thorough up to this point in troubleshooting. Is there something stupid which I'm missing...?