QUOTE(shanebuss @ Jul 14 2005, 01:54 PM)
thanks for the reply.
Even when i disable the chip i still get error 16. For whatever reason when i connect my external programmer it gets code FFFF and cannot read/write the bios.
I see some posts where error code 16 is a corrupt dash. I am thinking about trying to hot swap the drive and rebuild the C partition.
Should there be a LED on the Xecuter 2 pro V2.0? There isnt one lighting up if there is.
yes, corrupted dash could also be the problem. From my experience, error 16 is mostly rare. It happens when the clock looses it's setting (power unpluged for a while) and the dash cannot be loaded to reset it. As soon as the kernel detects an invalid clock, it tried to load the dash. When it can't, it outputs error 16. This means that your dash is either completely missing or corrupt. Either way, it can't be booted.
This problem usually doesn't happen when you have a chip installed since almost every recent hacked bios bypasses the clock problem and allows a boot no matter what.
I assume your only possibilities would be to flash your chip (if you can get your PC to recognize the chip) or to hotswap and restore the MS dash. (make sure it's xboxdash.xbe and not something else).