Print

[DaddyJ]

QUOTE(chief7 @ Feb 9 2005, 03:00 PM)

how does compiling give you more freedom?

Hexing only gives you the ability to change a path, you cant extend the path if needed.

By recompiling you can make the path as long as you wish, without worring about messing anything up.

[chief7]

that was probably my problem.  i have been trying to extend the path using a hex editor.

so to extend the path i would need to :
open the xbe file in notepad, edit it, compile with nasm and then sign it with habibi

is this correct

can you extend the path in a xtf file using a hex editor?

[krayzie]

you open the source. not the xbe file. and yeah that was probably your problem

[chief7]

great thanks, i'll try that tonight

[chief7]

alright i tried edit a fresh dualboot.asm to the paths i wanted, used nasmw to compile the xbe, and signed the xbe with habibi but still no change.

the only other problem i can think of is an error in the font file.  im using the bert_ate_ernie-generic.xtf from the UXE package.  i simply hex-edited the path to the dualboot.xbe.  i probably extended the path here as well though.  can you do that?  i looked but didn't see a way to compile an xtf.

[krayzie]

the problem probably was and still is your font. you cannot extend anything using a hex editor. And compiling an xtf source is the same as compiling any other source. there is even a tut about it in the tuts topic......

[chief7]

i finally got the dualboot and shadow c setup working... yeah!!!

thanks to everyone for your help and patients, especially krayzie.

the only other question i have is why my original dash isn't working.  i setup shadow c (it works fine), deleted everything on the virtual c except c:/fonts/dash/evox, added all retail files to virtual c, added item to evox dash "MS Dash","c:/xboxdash.xbe", rebooted and tried to run MS Dash from evox but it came up with a error 21.  i could have sworn i saw the retail dash flicker first though.  is there something im missing?