Cannot Disable X-ecuter v2.2 PRO Modchip?!?!?

Discussion in 'Xbox - General discussion' started by globalwar, Aug 22, 2003.

  1. globalwar

    globalwar Guest

    I have tried everything I can think of and this is a desperate attempt for some help.

    The thing is, I cannot disable my X-ecuter v2.2 PRO modchip to boot the into the normal Microsoft bios/dash. Everything went excellent with my recent mod: flashed my X2.2 pro chip with 4 banks of the latest X2 bios (4977), installed the latest version of Evox (v1.8.3752) to my HDD (note: I do have both evoxdash.xbe & xboxdash.xbe on the C drive), successfully locked my new Maxtor 120gb HDD w/ config magic, etc...But for some reason when I try to disable the modchip with the supplied Xecuter v2.2 Pro switch, nothing changes. Even when it is in the OFF position and the LED light is OFF it STILL boots up with the "XBox" logo and the tag "XECUTER2" (instead of Microsoft)?!?!?

    I have tried various combinations of the dip switches with the enable/disable switch set to disabled, but still the same result, boots with X-ecuter chip?!?

    Can anyone give me some advice?

    NOTE: Does it matter that I flashed my X2 with 4 banks of 4977, because that is the only thing I can think of.

    Here the specs of my mod:
    X-ecuter v2.2 PRO (flashed w/ X2 4977 bios)
    Evox v1.8.3752
    Locked Maxtor 120gb HDD

    Thanks,
    Globalwar
     
  2. Zero-X

    Zero-X Guest

    Man thats a funky problem. I know of ppl that have pre flashed the bios on the xbox mother board so they wouldn't need a chip but i don't think u did that. Hmmm I don't know how really to help u but i got some ways u can find out whats happening. K one just take the chip out and boot and see if u still see xecuter2. Or it could be a bad swtich.
     
  3. globalwar

    globalwar Guest

    I figured it out, I blew out my D0 connection!!! Because D0 was blown to the Xbox's original processor, it never booted to there, but X-ecuter was still grounded and I can only assume the X-ecuter took over as the processor?!?! After repairing my D0 I am up and running w/ both chips. Thanks.
     

Share This Page