No problems or conflicts with drivers. At OS level, OS see the chip attached.
I can not even open X-control, which is why I posted. I get the error as stated before when I click to open X-control on the exe itself, or from the start menu.
With the Chip hooked up, or not hooked up i still get same error, and X-control does not open. I never get to see the GUI.
I even tried W2k, 98, NT compatablity mode, but no success.
I found two MS KB articles regarding DEP (data execution protection) KB 878474 and KB 875352, however following the instructions on disabling DEP, does not change my situation.
I have a 1.6 Xbox, will I be able to put in the chip without flashing the bios first, and it should boot to Cromwell without frying my system? Once chip is in and I if I did not flash with correct BIOS Should I be careful of pressing any buttons during boot up? Don't want to activate any of the secret BIOS that are not designed for my system, and have a doorstop.
I will check on the 1.1 Legacy port option in BIOS. I beleive it is enable since I know I have some non 2.0 USB things connected.
Thanks for the reply Christine.