This is my story. I have already fitted a xecuter 2.6 ce into my xbox and a friends. Version 1.6 and 1.0 respectively. During that time I burnt evox to a cd-rw and a dvd-r. I also used evox to upgrade my friends hdd by fiddling with the .ini file and including the backup keys from the old hdd. So everything worked okay, then. Now I just installed another xecuter 2.6 ce to another friends xbox v1.1 and by luck I still had the previously burned evox dvd-r. These still worked fine. Only when I had to create a new evox cd for the hdd upgrade (so it could use the backup keys from this xbox), the xbox doesnt read it. It doesnt read on mine either. I thought it might be the cd-rw but when I burnt dvd2xbox and then avalaunch and then nexgen on the cd-rw and they all worked fine on both mine and his xbox's, I was confused as hell. I even tried just burning a normal evox dashboard onto the cd-rw and got nothing. It seems evox doesnt like me now 
. I used the same method this time as I did in the past, that is to say putting a 100mb dummy file in the evox folder, changing the evox xbe file to say default.xbe. Make a xiso with craxtion 4 and then burn it with alcohol 120%. The other dashboards work fine but evox doesnt, I really dont know what the hell is going on.
. I used the same method this time as I did in the past, that is to say putting a 100mb dummy file in the evox folder, changing the evox xbe file to say default.xbe. Make a xiso with craxtion 4 and then burn it with alcohol 120%. The other dashboards work fine but evox doesnt, I really dont know what the hell is going on.
Last edited: