QUOTE(HackDaBox @ Nov 13 2005, 04:16 PM)
Bank 3 is the only bank for a 512k bios yes but when you tried Evox M8 Plus V1.6 did you try to flash it to Bank1 (256k bank) or to bank3 (512k bank)

HackDaBox !
PS anyone with a Spider GX and Evox M8 Plus V1.6 working please reply to this !!!
I have a SpiderGX in a v1.6 Xbox, and both the standard EvoX M8+ 1.6 BIOS and the Yoshihiro debug version work. Well, I have problems, but they boot OK. The EvoX BIOSes seem to dislike booting to any dash other than the EvoX dash more than once, for example if I install UnleashX it works first time, but after the first reboot I get the service screen and have to boot to a dash on CD to repair. I installed EvoX BIOS to bank 1 (256K), X2.5035 on bank 3 also seems to work, and will boot any dash any number of times. Although flashing to bank 3 seems to break the BIOS on bank 1, and flashing to bank 1 seems to break what's on bank 3. Bank 2 seems unaffected (currently holding the test BIOS).
One problem I'm finding with my setup is that XBEs may not launch from the dash unless I do things a certain way. If I boot the machine (using EvoX BIOS) from off, I get the flubber animation, then the big X logo, then the dash comes up. No XBEs will launch - it hangs at the EvolutionX logo screen. If I instead choose "reboot", the Xbox powers down, then back up, but no flubber! It goes to the X logo, then to the dash, and I can launch whatever XBE I like. I still have a problem with XBMC hanging when trying to play AVIs (which I know work on the same XBMC build on someone else setup, but anyway....).
If I use the X2 BIOS, I get the Xconfig live screen, then the flubber animation always appears before the X logo, even on reboots, and I can never launch XBEs from the dash.
Any ideas what's going on? I have 2 possible theories:
1. The diagram shows the D0 wire to be cut for a 1.6 wrongly, and I have cut the wrong wire.
2. The SpiderOS shows my Xbox version as 1.0-1.5, even though I have a 1.6. Is this why the 1.6 D0 LED goes out when the chip is activated - does the chip only activate one of the D0s depending on what version Xbox it thinks it's in, meaning my D0 is doing nothing?
Or I could just have a bad contact, I guess - hard to say (all 5 LEDs light with the chip disabled).
One addition (sorry for the marathon post, but I've been having a lot of trouble with this chip) is that the first chip I had would boot 3 times and FRAG to a blank screen, as some others have described. I returned the chip to Divineo (UK), they sent a replacement, which is the one I am using now - it worked the first time I installed it.
Hope some of that is useful, and it would be even better if someone knows how to fix my problems
