Dasboard Font Patcher
Changes :
19/7-2004 : Fixed a bug that produced an output xbe larger than the input xbe for the windows version.
I still see numerous posts by people having trouble hexing a copy of their M$ Dash to look for the original fonts after installing a font hack.
To hopefully make this a bit more simple I made a small command line tool to be run from a DOS prompt that patches the name of the "fonts" folder or the .xtf extension in a dashboard file.
This can be used on your original M$ Dash or any of the replacement dashboard based on the M$ Dash (tHC, blackstromx, ...).
Get the tool from 'the usual places' (PC section, xbe tool).
Copy your dashboard xbe to the patcher folder and run the tool. The output file from this tool is out.xbe. The syntax is given below :
| CODE |
Usage: patcher [xboxdash-file] [-bak] [-f0nts]
You must specify either the -f0nts or -bak flag to specify which string to patch.
Example : patcher xboxdash.xbe -f0nts |
This post has been edited by ldots: Jul 19 2004, 07:40 PM
thanks idots,
going to grab it now!
i cant get this to work, when i click on patcher.exe it gives me a black screen for 1 sec then goes away 
whats wrong?
It's a command line utility. Like in the good old DOS days 
Copy your xboxdash.xbe to the patcher directory.
Open a command prompt and navigate to the patcher dir.
Then execute the patcher as described in the first post (patcher xboxdash.xbe -f0nts).
Awesome ldots.. A very helpful utility, many people have problems hexediting for some reason. Hopefully, this changes all that.
Yeah, this will help a lot of people, if they don't do xboxhdm
Great work, as usual.
i ended up hex editing myself,
it was suprisingly MUCH easier than i first expected!
regards
Does this thing has a linux version or it may already be in your package ?
It's already in the mini-linux included in both the Memcard UDE installer and on xboxhdm. Same name, same syntax.
So if I use "patcher.exe thclite.xbe -f0nts" it will allow me to run thclite with UDE? I tried that but it didn't work. Running the edited thclite.xbe just boots MXM.
may be the xbe needs to be signed again with habibi ?
I'm not trying to boot with it yet, just get it to run. I'm using UDE so I can run whatever unsigned code I want I think.
If it says it patches some "fonts" strings then the tool most likely worked. If tHClite does not work it could be you dont have the original *.xtf fonts in the C:\f0nts folder ar that some files are missing for tHC.
ldots - I tried your patcher on my original xboxdash.xbe. It said it patched successfuly 2 times. I have the basic UDE setup with the f0nts dir. When I manually launch out.xbe it just hangs. Any ideas on what I could be doing wrong?
| QUOTE (nickrivers @ Jul 16 2004, 08:01 PM) |
| ldots - I tried your patcher on my original xboxdash.xbe. It said it patched successfuly 2 times. I have the basic UDE setup with the f0nts dir. When I manually launch out.xbe it just hangs. Any ideas on what I could be doing wrong? |
is this with tHc,
in this case, the correct file/folders also need to be in c:
Never got patcher.exe to work with my setup so I just hex edited it myself. Like adil said, it was very easy.
Thanks for the information. I tried to hexedit it..but I was unable to find the string font/ or the hex value they had for that on the UDE post. What did you search for?
Do a Latin Unicode search for "fonts" then change the "o" to "0" (zero). There should be 2 occurances. After you change them, do a "save as" then FTP it to your box.
Well I'm closer!! I was able to find fonts\ but I actually found 3 cases. I tried to change them to f0nts\ but when I launched the .xbe i got an error 21. When I installed UDE it used a directory called fønts not f0nts. Could this be the problem? To remedy the situation I created a f0nts dir cand put everying in fønts into it. I thought that might help..but it didn't seem to. Any help is appreciated. Thanks
This should be included in the UDE Package. Assuming the package has the most up to date fonts (haven't checked recently), this would be exactly what people need.
Then there is the memory card installer too... but some people might like to do it themselves
| QUOTE (nickrivers @ Jul 16 2004, 11:47 PM) |
| Well I'm closer!! I was able to find fonts\ but I actually found 3 cases. I tried to change them to f0nts\ but when I launched the .xbe i got an error 21. When I installed UDE it used a directory called fønts not f0nts. Could this be the problem? To remedy the situation I created a f0nts dir cand put everying in fønts into it. I thought that might help..but it didn't seem to. Any help is appreciated. Thanks |
there should only be 2 cases,
also, just change the fonts folder to: "f0nts" makes it easier.
| QUOTE (Kyro @ Jul 17 2004, 09:02 PM) |
i m under win xp pro sp1 and i wanted to use the patcher with the -f0nts option, i patched successfully but wasn t able to go from evox to msdash
so i used a hexedit software to patch manually and then i had no pb
so i may be wrong but i thing the win32 version of the patcher has some issues, cause i tested the linux version and got no problem to go to the msdash
hope it can help some people |
hmm, shouldnt make a difference,
there should have been a good small tut using a hex editor exactly how to do it.
would save all problems,..
| QUOTE (nickrivers @ Jul 18 2004, 06:08 AM) |
| I'm seeing 3 instance of fonts and I changed them to f0nts. I also made sure my dir was named f0nts. Still gives an error 21 when I boot. Could I have a funky default dash? if so is there another one I can use somewhere? |
like i said,
THERE ARE ONLY 2 INSTANCES,
THIS IS WHY YOU ARE GETTING AN ERROR!
| QUOTE (nickrivers @ Jul 18 2004, 07:46 PM) |
| You seemed to miss my point. In my XBE there are 3. Does that mean my original has a problem or what? I undertand its supposed to only have 2..but mine has 3. Any help would be appreciated. |
to make sure we all understand each other, why not give the following :
1. your dash file size
2. file date/time
3. md5sum
4. xbedump -dc output
then we may know if there is some strange dash out there.
I think I said there were 3 instances before. Actually there are 4. This is confirmed when I run ldots patcher it says 4 occurences. But it still doesn't work. There must be something weird in my file.
this font patcher is only for UDE - you should be using UDE now anyway as it is faster and way safer than all other font exploits to date..
I'm not completely gonna rule out any chance of a bug in this tool, but if it doesn't work the best bet is that some files are missing for the dash to run. If you patch with -f0nts the original, and only the original, fonts should be in C:\f0nts with the original extension (*.xtf). If you patch with -bak a post-live dash will first look for *.bak fonts in C:\fonts, and then in C:
Remember all settings files etc. need to be available for the patched dash too, and if you dont run PBL or nkpatcher your need to resign the patched dashboard.
If you have a game save exploit on your HDD try uninstalling your current font exploit and verify that the dash runs normal in an unexploited environment.
This patcher is the same as the one in the memcard UDE installer. I tried it on XP and the patched dash worked fine.
Ldots: I ran your package on a 5659 (from the msdash, it tells me it is 5959.03) xboxdash.xbe to use with the UDE2 and it would keep returning me to the dashboard when I tried to launch it. The patcher said it worked fine and found 4 occurances. I hexed a copy myself and it worked fine. On further examination, I noticed the xbe from your patcher was 9492 bytes bigger than xbe which shouldn't be since it should only be replacing a 'o' with a '0' there shouldn't be an size changes at all. Just wanted to let you know my observations.
Also nice work on the hdmakers, loads eeproms from floppy and creates a locking floppy. Things I was gonna request but you already beat me to it. Now I don't have to reburn the cdrw everytime with the new eeprom everytime I do a new HD for someone.
Hmm - that sounds like the bug I didn't want to rule out completely. Strange though, worked on WinXP for me
I'll have a look and see if I can spot the error.
What do you know 
I found a bug in the font patcher. Hopefully that should be the last of them. Please some of you guys that tried out the font patcher before without success, plaese try again with the version attached below. I know it's a huge post. Will remove it an replace the font patcher at the usual places if you find that it works now.
Edit : Dammit, seems the code section is too long for the forum software to handle.
Hmm, i think that post screwed up the page ldots
but no probs, you have your new patcher released 
What do you use to encode to b64?
edit: ok so it def. did screw up the page... seems like the quote merged with your sig o_O
Well apparently there is a limit to how long code sections can be. Please try grabbing the patcher from 'the usual places' instead. Thanks!
ldots does your mem card installer 1.7.2 automaticallly patch the dashboard or do I have to use this because I cannot boot to the dash from UnleachX but when I uninstall your package the dash works fine?
| QUOTE (Ns0mNiA @ Aug 8 2004, 08:12 PM) |
| ldots does your mem card installer 1.7.2 automaticallly patch the dashboard or do I have to use this because I cannot boot to the dash from UnleachX but when I uninstall your package the dash works fine? |
yes it auto matically does it,
mabye unleash needs tto look for moddash.xbe? or exited to look for f0nts? but i though that was the xbe's job
| QUOTE (scrupul0us @ Aug 9 2004, 01:06 AM) |
| I'd like to see this also be able to hack the live tab to say text of your choice and also have it link to a dash.xbe of your choice as well.. just a thought |
isnt it pretty easy?
just hex edit the m$ dash xbe.
Thx Idots for all your tools 
unable to download from this link : http://dwl.xbox-scen...ont_patcher.rar
is there any other mirrors available ?
thx
-hihan
Try the usual places. Was there the last time I checked!
this might be a stupid question, but
is it supppose to launch on the pc or the xbox, and if on the xbox, where?
nevermind, i never got the patcher to work,
but i restore the original c drive,
then ran ude2 with pblmetoo, with m8.....and it ms dash works
thanks
PLEASE I NEED IT!!!!!!!!!!!!
alrightie, now i tried hexing the file myself, i couldnt find any occurance of 'fonts' anywhere,
now i tried the patcher, and it returns string not found! its the xboxdash.xbe file from my 1.6 pal xbox
whatsup?
@rex
Read the tutorial on how to get files from "the usual place". The file is not hosted on "public" internet, so u can't get a direct link. There isn't any.
.....i hope he wasn't in a hurry for that answer......
lol
Man sorry to say so but the patcher is still bugged.
-> stock c setup ALL FILES ACCOUNTED FOR
-> f0nts folder
-> patched the xboxdash.xbe from slayers 2.6
-> error 21
I'm gonna go grab a hexeditor somewhere. 
BTW im testing this on a chipped box so dun even have to think about signed/unsigned code.
ever heard of nkpatcher 10? or a shadow c drive? you don't even need to patch anything anymore....i mean, you did like 3 months ago when this thread was active....but not anymore....
OMGOMGOMG
I spent 3 hours figuring this shit out and getting error 21 like a dozen times.
Ah fuck it.
I wont even bother anymore. Although a nice pre-live dash would be nice to have in "the usual places"
did the patch using command prompt, patched xboxdash.xbe to -f0nts (with a zero, not a capital O) replaced file, turned on xbox, error 13. PLEASE HELP ME. i have a backup of my c: drive saved, but obviously i can't get into the ftp server to fix it.
please help me!
you don't need to patch anything anymore.
just setup a shadow C and make it stock.
but if you feel compelled to go the old way of things, then it is msdash.xbe.
search around the forum for nkpatcher 10
This program does not run under Windows XP x64 Edition - any chance you could recompile it as Win32 Console application? I think it still uses 16-bit code or an incompatible compiler.
I did it manually so it is no biggee