Mechinstaller-Phoenix

[GKrobo]

Well i manually installed teh mechinstaller-feenix files...I wanna know if this set has an advantage over those...some times when I first boot up my XBOX it does a few soft boots before goin to the pheonix tabbed dash

[catfish]

I won't make any promises about the clock-loop.
But until we have verified proof that these fonts fail on any Xbox I'll have to say yes, they avoid it very well.
I have been testing these for about a month and I've forced about a dozen clock-resets during that time (2-6 loops). I have found that powering off before looping is more likely to bring a dead clock out in 3 loops or less. In the readme I have mentioned a "no-boot" loop which is more likely to occur than a reset clock.
No matter what, I still recomend getting a backup onto your PC as soon as posible.

[GKrobo]

either ways great job catfish...one question when i try to load the gamesave for the installer I cant get passed the parsing screen i have taken the bios file and have made both rom bins and help?

[underthebridge]

nice work man! thanks alot

[catfish]

Originally posted by GKrobo
Well i manually installed teh mechinstaller-feenix files...I wanna know if this set has an advantage over those...some times when I first boot up my XBOX it does a few soft boots before goin to the pheonix tabbed dash

These fonts have the security checks disabled thanks to PedrosPad. Also, these new fonts will boot backups directly, which in the case of Crimsom Skies may be the answer everyone is looking for :-Þ
I have also changed the default.xbe locations a bit, to avoid conflict with the first release.
I can't even remeber if the first release would boot retail games, but I know in the new ones, I discovered that they wouldn't until I changed them.

[catfish]

If anyone gets the installer to start PBL and PBL freezes, check the boot.cfg file and verify the BIOS is good.
Dbl-check "required.txt" for sizes and path locations for files and boot order for the edited BIOS.
There are several packages in the "usual places" which contain a working boot.cfg file. Obtain this and use the keys in XBtool to edit your BIOS.

The BIOS versions listed in "required.txt" is only for my beta-tester to assure compatibilty with all versions. Anyone making the package for themselves only needs a BIOS compatible with their own system.

[catfish]

I also forgot to mention,
If u want to avoid the ST.DB corruption causing error 21, make 26 copies of E:\Phoenix\default.xbe and rename each one with 1 letter of the alphabet, a-z. ("e" should already exist)
This will only prevent error 21, not the other type of corruption.
Would anyone object to this being done automatically in the official release? It only consumes about 8 meg of space, but kinda clutters up the E:\Phoenix dir.

[catfish]

If anyone can confirm a successful install with dash 5659 with dir C:\xboxdashdata.17cdc100 , I would like to know about it.
Also, dash 4627 (no xboxdashdata dir).

[Hajaz]

right. I had the mechfonts installed manually as described in bluhdebluhs thread on X-S.
Now, i just overwrote the old mechfonts with the ones you just posted, and while the phoenix option still shows in msdash, it just jumps straight back to msdash when i select it.
Anything i overlooked?

[catfish]

yeah, the readme file and this entire thread...
The paths have changed, rename E:\feenix to E:\Phoenix and all is well.

U can also make a bootable CD now and gain access that way.

[Hajaz]

ok, cheers

[shag]

Congrats first of all..
I just have a quick qn regarding the above comment about the boot order.. I'm trying to create my own bootable cd and am a bit unclear on what you mean by

Originally posted by catfish
[B]They will run Habibi-signed xbe's in this order...
1st, D:\catfish.xbe (habibi-signed from the DVD along side of any "default.xbe"

Anyways, what I did was habibi signed evoxdash.xbe and renamed it to catfish.xbe. Then renamed the original evoxdash.xbe to default.xbe. And place these two xbe's along with evox.ini onto a cdrw. Booting up with this cd in the drive works, it loads up evox. Sometimes it doesnt but i suspect that is due to the cdrw.
I also tried habibi signing pbl 1.3.5i and renaming it to catfish.xbe.. This also works.. ie. causes evox to load..
I cannot get it to boot without a habibi signed xbe named catfish.xbe on the cd.

So how does it actually work? Does it check for the file catfish.xbe which must be habibi signed, then loads the default.xbe? Originally I thought it would execute catfish.xbe, but from signing the pbl 1.3.5i and renaming it catfish.xbe, it doesn't.

Thanks,
Shag

[shag]

oops.. im wrong..
it does execute the pbl that i signed..
must've confused myself by all the attempts in creating a bootable cd

[shag]

hmm.. this is confusing me even more...
ok the cd i have 3 files..
catfish.xbe -> habibi signed evox
default.xbe -> audio signed pbl 1.3.5i
evox.ini

when i boot off this cd it tries to load default.xbe...
i'm getting some strange results here...

could you clarify what is suppose to happen? i'm gonna do some more testing..

thanks,
shag

[catfish]

The fonts will allow a retail DVD to load, this file is always named "default.xbe".
They check for for the presence of "catfish.xbe" before running default.xbe. If found, then habibi key is used.
*edited for accuracy, thanks shag*

The fonts only patch the public key when Live is selected or when it detects "catfish.xbe" on the DVD. They also appear to check both xbe's to make sure they are xbe's but only "default.xbe" needs to be habibi-signed.