Print

[DeadManWalking]

M8 is flamed to me

[arallsopp]

Same here with mine. V1.1 box, with Xecuter 2.3 (lite, I think). Black screen. Got M7 on bank 3+4, so flipped back, and all is good.

Still no go on m8 though. Game region shows as Region 4 (rest of world) in UnleashX, so I'm pulling down configuration magic too. See what goes... Will post back.

[Instinct[DA]]

this is why im just gonna stick with the m7ef................
even though i have the xbit...........

[arallsopp]

QUOTE (grug @ Jul 23 2004, 02:09 AM)

Ok. I solved the Error 21 problem. Somehow my Video setting in the EEPROM got screwed up. Even though everything was in PAL, ConfigMagic listed "Unknown, Region 4" instead of PAL or NTSC. So I fixed that and now everything loads again. The unpatched M8 is working 100% now....

Can you tell us more about this?

My v1.1 X2.3 (I think) showed the game region as PAL Region 4, DVD region 0.

With a 1024 M7 or 4981 on Banks 1+2+3+4, all is well.
With a 512 M7 or 4981 on Banks 3+4, all is well.
With a 512 M8 on Banks 1+2, or 3+4 (with M7 on 1+2) I get the black screening, disk spinning, fans rolling, no a/v problem.

I've not tried a 1024 M8, cos I can't recover from it if it doesn't work.

I used ConfigMagic to set the game region to PAL Region 2.

No change. M7 fine, 4981 fine, M8 blackness.

Doesn't seem to matter whether its patched, IGRd, official, unofficial, showing the TM symbol, whatever.

I tried patching with the two preceeding versions of EVTool too. Still no joy.

On the plus side, Crimson Skies (which previously couldn't load with 4981 now seems to work )

[cyberdork33]

Well, I am pretty sure that my prblem is linked to the eeprom settings too, but config magic isn't letting me access the settings now... does the xecuter2 bioses have embedded eeproms? is that why these are working for me and the evox bioses are not?