Print

[Teldin]

Never got patcher.exe to work with my setup so I just hex edited it myself. Like adil said, it was very easy.

[nickrivers]

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?

[Teldin]

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.

[nickrivers]

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

[Australian Rat]

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

[adil786]

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.

[adil786]

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,..

[adil786]

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!

[chimpanzee]

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.

[nickrivers]

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.

[YoshiKool]

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..

[ldots]

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.

[GeToChKn]

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.

[ldots]

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.

[ldots]

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.