Ok first up this isn't a flame in any way at nghtshd or jbone- just want to know if what i'm saying makes sense- and if it does maybe it can be a warning to other flash happy people out there
Ok i wanted to check out jbone's modified coloured animation, so got it from the usual place and as i have all mod related stuff on my f:partition got xbtool 1.0.22 to edit the boot sequence to launch avalaunch from the f:partition.
While i was doing it i also checked the embed eeprom box.
stupidly i didn't paste my own valid eeprom into the patch data folder, but unlike the previous version of xb tool i used (1.0.19b2) there must havebeen an eeprom.bin file in the patch data folder (just opened up the rar file and there is one there) because no error popped up saying no eeprom (or words to that effect) as there was when i tried to embed an eeprom before using 1.0.19b2- (in that instance i then pasted my eeprom in there and embeded it and flashed it and it worked fine)
anyway saved the bios ftped it over to the xbox and flashed it with "Xflash for SST49lf020 v2" (got a cheapmod).
Rebooted the xbox and got the green flash once followed by the flashing red, which from the errors page is a bad/corrupt/missing eeprom.
Turn the modchip off and the xbox boots to the m$ dash fine.
I'm not 100% sure but does that mean that the eeprom i embeded in the bios was corrupt?
If so maybe it'd be a good idea if that eeprom was removed from the patched data subdirectory?
Could anyone conifrm if my reasoning here is correct?
If my reasoning is correct at least it proves that the eeprom embeding is actually working
but i guess you guys already knew that This post has been edited by nimbles: Mar 12 2004, 11:30 PM