Jan 18 2004, 07:16 AM
I used Gouki's guide to softmod. I have evox up and running, but it is flashing red and when i load a game to e:/games/gamenamehere or try to run one from the dvdrom i get the error 21 screen. I can still ftp and i have signed pheonix bios loader 1.3 can i use this. Do i want to try this?
|The version of your XBOX looks okay; I know people with those specs that have gotten it to work.CODE |
Do those files match the files in the package you're using? Also, you can simply open boot.cfg with a text editor and copy-paste the RC4 and EEPROM keys from the signed one to the newer PBL 1.3.5 and resign the XBE file in the PBL 1.3.5 package.
NOTE: If your RC4 keys and EEPROM keys consist of all 00's (0X00 0X00 ... 0X00), those are default invalid keys... you need to find the right keys.
Let me know if the files above are the ones you have so I know which version you're using. If your files match what I originally stated, it should have had a Bioses folder... if not make a folder named Bioses and move the xboxrom.bin file in there.
EDIT: BTW, the X2 4979 BFM BIOSes won't work with PBL 1.3 (forgot to mention that), if you really must use PBL 1.3, get the 4977 BIOS
The tutorial I gave was based on the idea that you'd be using PBL 1.3.5. If you don't have a "Bioses" folder, you're probably using an older version, perhaps 1.3. In that case, the BIOS goes in the same folder as PBL so your layout would look like this:
Jan 18 2004, 07:31 AM
Hmm, that post looks awfully familiar,
. Anyway, have you been resigning your XBE's with the font signature? If not, then that's why you're getting the Error 21. If you only use the font hack to directly load the evox dash, you need to resign every XBE file you want to run with xbedump.
|xbedump default.xbe -font|
Resigns default.xbe with the font signature... xbedump actually resigns it but saves the resigned version as out.xbe. You can move/disgard the original default.xbe and rename out.xbe to default.xbe
If you don't want to deal with signing all the time, yes, PBL is the way to go. I wouldn't use that section that you copied, as if you look at an earlier section of that post, I have a file layout of setting up PBL 1.3.5i. Try look at a previous post on that thread for the walkthrough. It's pretty straight forward, but if you have questions I can try help you out (again, if I have the time).
EDIT: Oh, the reason I recommend 1.3.5i is because I usually don't know what version XBOX the guys I'm helping have. The newer 1.4/1.5 have a focus encoder that doesn't work with PBL 1.3. Those require you to use 1.3.5i and the X2 4979 or higher BIOS.
Jan 18 2004, 07:38 AM
Easy noobie question... I obtained the X2 4980 bios and in the rar is has 2 different bios files....4980.67_BFM.bin and 4980.06_BFM.bin. I'm guessing I need to edit the boot.cfg for PBL 1.3.5i and point at one of those instead of xboxrom.bin.... my question is which is the one I should include with PBL 1.3.5i and point to in the boot.cfg.
Jan 18 2004, 07:55 AM
bah even when I do 1.3.5i i still get flickering... I know it's showing like an animation first, then I get a black screen that flickers with a green line... i'm guessing that's some sort of error but I dunno.
Jan 18 2004, 08:46 AM
Jan 18 2004, 08:48 AM
So nothing is broken yet, thats good to hear. Can you direct me on exactly what i want to do now because seriously i am dumber than lazy. I have not signed any xbe. yet and do not want to go that way. So what are my options now on getting this thing going.
Jan 18 2004, 10:06 AM
Ok zogger this is what im stuck at now, I have found 1.3.5 and 4979.67. Do i need hd_gen.tar.gz for the rc4 key and do you use eeprom_dumper.iso for the eeprom.You say text editor just use notpad to copy Rc4 and EEPROM ? Are all Rc4 keys the same ? Im not exactly sure how to do this can anyone give me a holla back asap thanks again. Im very confused now.
|You need to setup the boot.cfg file. It requires a debug RC4 key and two EEPROM keys.|
Jan 18 2004, 03:09 PM
The major difference between the .06 and .67 BIOSes if is you have a large hard drive (> 137 GB), if you're using your stock retail HD, it doesn't matter which one you use. Also, could you check kernel and dash your XBOX has. The squiggly lines generally indicates you have a newer XBOX (one with a focus encoder); if you have the newest (5530 kernel), unfortunately PBL 1.3.5i won't work (no version of PBL released yet will work with that).
If you don't want to spend too much time trying to find the RC4 keys, there are packages which have the boot.cfg filled with the proper keys. You mentioned you already had the Signed PBL 1.3 package, so try extracting the boot.cfg from that, then opening it with a text editor. If the RC4 and EEPROM keys look like (0X00 0X00... 0X00) it hasn't been properly filled, but if it has actual hex values, you're all set.
All the Debug BFM Bioses use the same RC4 key, so once you find that, you won't need to worry about updating it when you swap BIOSes. As for the EEPROM, as long as you have the v1.0 and v1.1 key you'll be okay (that's more about the specs for your xbox that the specific BIOS).
EDIT: Sorry had to get some sleep... was programming all day straight...
Jan 18 2004, 04:27 PM
Luckily, my kernal is 5101... this leads me to believe that it could be my fault why it is not working right. Are there any tutorials for installing PBL 1.3.5? I was trying to do the gamesave trick with 1.3.5i so it would load everytime I load the gamesave, which inturn would load evox on my system. I could make out what looked like a PBL animation, so it might just be the way my evox files are setup or my bios files or something? Another solution would be if I could actually downgrade my dash, that way I could do a font hack and just learn to deal with having to sign xbes.
Jan 18 2004, 04:47 PM
If you want, here's the link that NaDes has been talking about:http://forums.xbox-scene.com/index.php?act...T&f=44&t=156437
It's a thread about how to setup PBL 1.3.5i with the font exploit (so no more signing).
As for using it with a gamesave, the MA/007 is a good source, although it's designed with 1.3 if I remember correctly. http://forums.xbox-scene.com/index.php?act...ST&f=44&t=79331
The setups are somewhat the same although there are a few differences, notably 1.3.5i looks for the BIOS in a folder Bioses in the same directory as the PBL default.xbe. For example, with the MA/007 tutorial, your default.xbe is here:
E:\UDATA\4d530017\62D648EBF155\default.xbe (for MA)
E:\UDATA\4541000d\000000000000\default.xbe (for 007)
The BIOS should then be here (if you're using 1.3.5i):
E:\UDATA\4d530017\62D648EBF155\Bioses\xboxrom.bin (for MA)
E:\UDATA\4541000d\000000000000\Bioses\xboxrom.bin (for 007)
You might need to use XBTool to modify the BFM Bios if you try to launch evox from a different location other than it's standard C:\evoxdash.xbe ... and if you use a regular PBL 1.3.5i build you'll need to use xbedump to habibi sign the default.xbe
Because you have a focus encoder, PBL will still show up squiggly, but after you load the 4979 BIOS and boot into EvoX it should be fine. Make sure 1) you're using the newer X2 4979 or above BIOSes (or EvoX M7), and that the filename you're saving it as matches the filename in the boot.cfg
Jan 18 2004, 05:15 PM
K, no luck so far with the 007/MA gamesave... trying out a few bios and etc to make sure. There's not anyway to mess up by doing this so I guess I'll just keep fooling around. Maybe you can help with a bigger problem though--downgrading my dash. When I overwrote my xboxdash and files with the ones that are included in slayer's iso (4920), I got an error 21. I don't think I misplaced any files... so do I need to sign the xboxdash.xbe maybe? Nothing I've read on downgrading dashes has mentioned this, but a 21 error usually means unsigned xbe right? Thanks for all the help, greatly appreciated.
Jan 18 2004, 05:18 PM
First thing first... don't resign your xboxdash.xbe... that'll mess things up pretty good. Had to make sure I said this first above all other things.
EDIT: The BIOSes you should use with your xbox are the X2 4979 and above, and the EvoX M7... other BIOSes won't work properly as you have the focus encoder. Secondly make sure they are BFM Bioses, not regular BIOSes (it'll say BFM in the filename if you got it from a "usual place").
Jan 18 2004, 05:26 PM
Wow, thanks... I didn't, haven't, and won't.
EDIT: About the bios, yes they are BFM and I'm trying out 4979, 4980, + M7, but I must be setting up something wrong on the evox side I think, my gamesave looks pretty good and it seems like I configured the boot.cfg right. I get the flickering colors and then a black screen, it looks like there's 1 line of white text that stays for about 3 seconds and disappears.
Jan 18 2004, 05:41 PM
Hmm, that one line is probably when PBL is saying:
"Press A to load a bios" (or something to that extent)
Normally you don't need to hit A because as long as your boot.cfg has a bios file listed to be autoloaded, it'll autoload that first. If I remember correctly, if PBL does load the BIOS, BUT you have your evoxdash misplaced, it'll kick you to the MSDash.
I know this is going to sound a little stupid too, but how many controllers do you have in your xbox? My friend (and I've observed this), with PBL 1.3.5 if you have 3 or more controllers in, either PBL hangs or it takes a really long time to load. Having 1 or 2 was okay, but 3 just caused us headaches ... yeah... weird.
Anyway, all I can say is check the keys to make sure they're right, also check that your bios is in the "Bioses" folder and that the name in the Bioses folder matches the name in your boot.cfg.
PS. If you still can't get it working, try explain the layout of your files
EDIT: I can't think of off hand why you're getting an error 21 when you're downgrading. It should work fine if you followed the directions Morden gave. What it could be is maybe the ISO file is corrupt or the files are corrupted in the extraction process. What tool are you using to extract the files?
Jan 18 2004, 08:03 PM
I've tried the newest X2 bios but with no luck... although one time I did hit A and it took me to what appeared as a blurred bg.jpg image, the one included in 1.3.5i. In the boot.cfg where it says RomFile... i'm just copying the name of the ROM I am including, should I add the directory so it's listed Bioses/romfile.bin in boot.cfg? As far as downgrading the dash, it seems simple... but for some reason it didn't work and gave me a 21 error... I'll try extracting the iso with a different program this time and see what the results are.
Jan 18 2004, 08:23 PM
For the romfile, you shouldn't have to put a filepath. It will look for the Bioses folder in the directory that your PBL default.xbe is.
When you hit A, it took you to the BIOS select screen. You could try see if going to that then hitting A again selects the BIOS because maybe it's simply the setup of the boot.cfg and romfile name. If you're file is called "romfile.bin" your bootcfg line would simply be:
For extracting, I'd recommend xdfsextract... simple yet effective command-line extracting tool. You can experiment with the other tools though. (Don't use ISO buster or a regular ISO tool, as they don't handle XBOX ISOs well...)
Jan 18 2004, 08:30 PM
Well good news on the extraction... I did use an xiso extraction tool before but this time when I extracted with another program it seems there are more files
.... so I'm gonna try downgrading again and see how it goes this time. Bad news on the PBL tho, cause I don't know what else I should do.. unless it takes a while to load bioses? I've let mine sit on the flickering black for like a minute before, but I figured just letting it sit there in a state might damage something...whether it be hardware or my eyes.
Jan 18 2004, 08:38 PM
It shouldn't take that long to load a BIOS... 5 to 10 seconds max. If you can tell me your file setup (a checklist), I can try see if there's something wrong.
1) Do you have the right keys, RC4 and EEPROM keys?
2) How are you launching EvoX? at your C: partition or in the gamesave folder
2b) If you're doing it in the gamesave folder, have you properly editting the BFM Bios
with XBTool to look for the dash in that folder?
3) You could try removing your evox.ini file (if it's not there, it loads default settings) to see if it's a ini file problem
EDIT: I figure I should point out, that if you really can't get PBL working with the gamesave, you could just launch EvoX instead. You'll have to sign all your XBE, but I figure since you can't eject your disc and use a a DVD backup anyway... you'll be running software of the HD.
EDIT: EDIT: Another advantage of getting EvoX up first, is that at least you're up and running. You can then try get PBL to work by running it as an app at your own pace.
Jan 18 2004, 09:09 PM
Well VERY good news... I just downgraded my dash to 4920, now I am free to use to do the exploits if need be.
1) I grabbed the keys from a signed PBL 1.3 zip
2) I FTPed evox.ini,evoxdash.xbe some skins onto the C drive (through a evox gamesave, but then I edited the gamesave, took out evox and put in PBL)
3) Not sure about this... are you on IRC anywhere or have an instant messager? (I understand if you don't want to talk or are busy... just figured it'd be easier to communicate)
Jan 19 2004, 09:57 AM
Thanks for clearing things up a little Zogger. So now what i want to follow this exactly and then im done ? The boot.cfg that came with my pbl 1.3.5i is in this format and starts.
RC4Key 0x58 0x62
The 1.3 Signed format is and starts like
RC4Key 0x59 0x36
Can i just use the 1.3.5i boot.cfg that has the values and format stated above. The reason i ask this question is becasue in the notes.txt included in pbl it says RC4 key is not in boot.cfg but it looks like there is an rc4 key in the boot.cfg.
I compaired it to the 1.3 Singed version boot.cfg and they are different format should i use the boot.cfg that came with 1.3.5i and am i ready to just rename default.xbe to evoxdash.xbe and copy the pbl files into c:/ ? Even though this thread provided lots of feedback. I really dont want to wreck this in anyway and am still waiting for what i exactly step for step want to do. Thanks again I hope im almost done. So should i just start doing this now ?
Rename it to evoxdash.xbe. Then, copy all the files for PBL to your C partition. You should end up with these files:
C:default.xbe (PBL 1.3.5 XBE)
C:evoxdash.xbe (Evox dash that was originally named default.xbe)*
C:evox.ini (optional file; EvolutionX configuration)
C:Skin (optional folder; EvoX Skin folder)
What happens is when you boot up your XBOX, the fonts load, causing C:default.xbe to run. C:default.xbe is PBL which loads the bios file C:Biosesxboxrom.bin. The BIOS file (unless it was modified) is designed to look for C:evoxdash.xbe.
Jan 19 2004, 12:08 PM
Umm Zogger. So i can rename and copy over these files now right. Im guessing i have the right boot.cfg and it has the right keys if they are not all 00x0 am i correct. Does the format of the boot.cfg I have match the format of your 1.3.5i ? Thanks again im waiting for your response and thanks.
C:default.xbe (PBL 1.3.5 XBE)
Jan 19 2004, 12:48 PM
As I mentioned to someone else, there are packages out there with the keys already in them. The notes.txt is usually left unchanged, so that's why the two seem to conflict... and good thinking on extracting the keys out rather that using the 1.3 cfg with 1.3.5i. It's always better to simply reuse the required data than overwriting/replacing a config designed for an different version.
Let's see... first note: always keep a backup of all the files you have. If you're really worried about things goofing up, make sure you have another solid method of getting back into EvoX (gamesave for example). Then, when you're set with this here's a recap of what you need to do:
If you are sure that your keys are correct (if you got the keys from, let's say a signed PBL 1.3, they probably are) then you shouldn't need to modify your boot.cfg (as long as you follow the walkthrough).
- First, take your PBL default.xbe and use xbedump to font sign that. Don't forget that xbedump resigns the XBE and calls the signed file out.xbe. Move/disgard your original PBL default.xbe and rename out.xbe to default.xbe.
- Next, rename your current C:\default.xbe (EvoX) to C:\evoxdash.xbe.
- Finally, copy all the PBL files to your C partition:
|C:\default.xbe (PBL 1.3.5 XBE)|
C:\notes.txt (this is optional, but if you want to keep it you might as well)
Make sure that you copy the font signed PBL default.xbe, otherwise when the fonts load, they'll try to load your new PBL C:\default.xbe, but if it's not font signed, you'll run into an Error 21. The boot.cfg are usually set with:
So which is why I've named the file in the Bioses folder xboxrom.bin. You can have a different name, but you need to make sure they match correctly.
EDIT: Cut-Paste of boot.cfg [in case you're wondering]
|RC4Key (key removed)|
EEPROMKey1_0 (key removed)
EEPROMKey1_1 (key removed)
Jan 19 2004, 01:44 PM
I should be more specific ok i have PBL1.3.5i_signed_font_exploit.zip do i still need to do the xbedumb to sign and make an out.xbe ? Im gonna do it soon as you reply. Thanks u rock.
Jan 19 2004, 02:20 PM
Hmm, looking at an archive I have, that filename looks legit, so it should be already font signed. In that case you can skip the whole using xbedump to resign the PBL default.xbe. Use the default.xbe as it is.
EDIT: Of course, it doesn't hurt resigning an already signed XBE. But based on that filename though, you shouldn't have to.
Jan 19 2004, 03:27 PM
Sweet everything worked i think. Real games work on it. But when evo loads now i have no launch menu. I put something in e:/games and still no launch menu. Also how do you get ms dash going also.
Jan 19 2004, 03:36 PM
For the Launch Menu, you need the evox.ini to be properly configured. I don't know which version evox you are using, but the syntax is pretty standard.
If you don't have an evox.ini in your C partition... that's the problem
If you do, try search the file for the [Menu] section.
Somewhere within the two outer curly braces (open and close braces) check that you have these lines
| Section "Launch Menu"|
If you want, find the latest EvoX 3935 Build and use it to both upgrade (if you have an earlier version), as well as to obtain a properly configured ini file. It might have excess options (trainers, for example), but you can always delete the options you don't want.
If you do upgrade, don't forget to resign the XBE file and rename it to evoxdash.xbe if it isn't named that already.
EDIT: I've already explained this in a few other threads, so rather than using up more server hd space, I'll point you straight to the posts.
---Link to my post that link to other tutorial posts---
---Link to my post to help you out if things don't work the way they should---
I'd read them both first (especially my second one... while it may not make sense the first time you read it, it'll be more clear what I mean when you start following the tutorials in the first one). The second one is about an error a lot of people make when relinking the dash.
Jan 19 2004, 03:44 PM
This is what i have there
Line "- Auto Items -",2
Jan 19 2004, 04:03 PM
Hmm.. <scratch head>
Let's see... first you could try commenting all the Sort related commands and seeing if anything shows up after you restart/reload EvoX. If that works, you could try commenting out the first "SortAll" that you have within the SortStart and SortEnd, or move it outside of the "SortStart" "SortEnd" section. You seem to have the proper AutoAddItem lines... and make sure the apps/games in the folders have a XBE by the name of default.xbe or else they won't show up.
PS. You could try copy and paste my code above to see if a menu shows up.
Jan 19 2004, 08:24 PM
Zogger u rox. Ok you were right about everything so far the comment's worked for my launch menu. Now all I have is this lousy dash to get going and im set. Ive downloaded hexworkshop and went to edit find 78 00 74 00 66 and 00009FE8 and it does not find any of those am i doing something wrong ? And in the tutorial when it says relink the evo.ini ms dash to the new one is that the top entry. Thanks again.
MSDashBoard = "c:xboxdash.xbe"
Jan 19 2004, 08:52 PM
His reference to 00009FE8 was about an address and not an actual hex value. Both tutorials revolve aorund the same principle, but interestingly they're slightly different in that the first one tells you to change a single reference of X T F, versus the second one saying to change all references of X T F.
That aside when you're using Hex Workshop, first open a copy of your xboxdash.xbe file, then goto:
EDIT --> FIND
You should get a dialog box with pulldown menus.
Under Type: Select Hex Values
As Value Enter: 7800740066
Select for Direction: Down
What might have happened was you were looking for the text string "7800740066" in which case it wouldn't work.
An alternative way, if you don't seem to like hexadecimal values is searching for the string.
Under Type: Select Text String
As Value Enter: xtf
Select for Direction: Down
And Under Options Select: Unicode String
Jan 19 2004, 11:33 PM
Sweet you are right once again i changed all the xtfs to xfts. Saved it. Now ive never signed anything and tried avoiding it. I navigated through dos to a folder when i put the renamed dashboard how do i sign it. When i type xftdash.xbe windows file association pops up. How do I do this? I should have just gave this to someone else all this reading makes me sleepy.
Jan 20 2004, 12:05 AM
I have some good news. You've never signed anything... if you've gotten PBL up and running, you never will. I'm guessing you're following one of the final steps on the relinking tutorials as it mentions to use xbedump to sign the XBE with the font signature. That relinking tutorial was written for those with this configuration: Font exploit ---> EvoX
Because yours is: Font exploit --> PBL --> EvoX, the BIOS loaded by the middle man removes any signature and security checks. All you need to do now is 1) rename it from it's original xboxdash.xbe to something different... for example, hackdash.xbe, 2) copy hackdash.xbe to the root of your C partition, 3) edit your evox.ini to point to the hacked dash.
Look for the line (in evox.ini):
|MSDashBoard = "c:\xboxdash.xbe"|
Change it to:
|MSDashBoard = "c:\hackdash.xbe"|
After you do that and restart, the MS Dashboard option should take you to your original MS Dash.
EDIT: If you really need to know though, you'll need a program called xbedump. Copy the file xbedump.exe to the same folder as the XBE you want to sign. Refer back to the second post or so on this topic if you want to see xbedump's usage
EDIT: EDIT: One last check, make sure you have renamed your original font files (Xbox.xtf and Xbox Book.xtf to Xbox.xft and Xbox Book.xft).
Jan 20 2004, 06:14 AM
Zogger owns. That sounds great about not having to sign anything. But do I still need to hex edit and change the xtfs to xfts in the dashboard im going to rename. Next time Im expecting not to ask any questions. Is there a tutorial on how to undo what I just did or can you.
Jan 20 2004, 07:39 AM
Let's see... you still need to change the xtfs to xfts but it's just that you don't need to resign them. As for undoing what you just did... do you mean switching the xfts back to xtfs or uninstalling all the exploits you just installed? As for the xtf issue, I'd recommend keeping a backup instead of trying to switch the values back. As long as you have a working backup copy you won't have to worry about things going awry when you try to do that.
If you mean uninstalling the exploits you just installed, if you really want, I guess I could write up an uninstall guide and append that to one of the threads (probably the Bert and Ernie Reloaded help one, since that's the one with the walkthrough). Let me know if this is what you were referring to, and if so, I'll try write one up later this week.
Jan 20 2004, 03:24 PM
Another question zoggs, will this work with all versions of xbox. Can you do this exploit with the xbox at wallmart right now in the Quest pack that has Swkotor ? Like using the mad gouki's and then doing the pbl thang.
Jan 20 2004, 04:07 PM
I haven't had access to every make and model of XBOX's out there, so I could be wrong about this.
For the most part, every XBOX out there seems to be exploitable to some extent. If a user can gain access* to their hard drive there they have a chance. I know I've heard about Beast packs giving people trouble, but people have said they have gotten it up and running (I think this was more of a focus encoder problem, but someone can correct me if I'm wrong about this).
Now that I've brought up the issue with the focus encoder, I need to say this. You can use PBL 1.3.5i to load a BFM BIOS that supports the focus encoder BUT if you have an XBOX with the newer 5530 kernel there is no version of PBL up to this date that successful loads. While this may cause a major setback, you can still get the font exploit up and boot into EvoX. The only problem now is that you'll have to resign all your XBE's with the font signature.
I'd check what the manufacture date on the Quest pack is, then check to find out what version it is (or do a search on the forums to see if someone's already posted info regarding to this).
EDIT: *Either through a gamesave (MA/007 and now Splinter Cell) or hotswapping
Jan 20 2004, 05:43 PM
Will it work if the sticker says 2003-07-17 and then product ID 551 5160531 32905 ? Where is the link on how to tell which are which. Thanks again.
Jan 20 2004, 05:46 PM
Will it work if the sticker says 2003-07-17 and then product ID 551 5160531 32905 ? I think it is 05=China, do you know if this should work? Thanks again.
Jan 20 2004, 11:36 PM
For future reference, here's a few links on determining the version by looking at the serials (it should be mentioned that this isn't a 100% way to figure it out...you'd have to open the box for that. Anyway, here's the links:http://www.xbox-scene.com/versions_0.php
--More info (especially about China XBOXes)--http://xbox-linux.sourceforge.net/docs/ver...onsfinding.html
A comparison with your serial is:
|551 5160531 32905|
So using the guides above, it's a China XBOX, Week 29 of Year 2003, Production Line 5. According to Xbox-Linux's website, they haven't obtained enough info (or haven't updated the page), but it seems to fall between a 1.3 and a 1.4
Both should be exploitable, the 1.4 having a focus encoder, but exploitable.
Jan 21 2004, 06:25 AM
Sweet zoggs more stuff to play around with ehh. So is mine this xbox 1.4 then and whats this focus encoder does this one have it?
Jan 21 2004, 06:45 AM
The Focus video encoder replaced the original Conexant one in the earlier XBOXes. If you had a focus encoder, when PBL boots up, the screen will be garbled/scrambled. If you can see the bird clearly, you do not have a focus encoder.
While 1.4/1.5 do have focus encoders, even if the screen is garbled, the program should still work fine. People with the focus encoder will need one of the newer BFM files, X2 4979 or above, and the EvoX M7 when using PBL 1.3.5i.
Jan 21 2004, 07:07 AM
Thanks again. I'll giver a go right away. So I can use the Free-XEvox version of evox that came with mad gouki's guide. I ask this becasue you mentioned "People with this focus encoder will need one of the newer bmf files and EvoX M7". Simple yes and no answers are good enough for me and I would like to thank you once again because without your support I could'nt be where I am today
. So I can follow the same procedure with verison as I did with the first, Is this correct?
Jan 21 2004, 07:09 AM
Jan 21 2004, 07:42 AM
You can try using them. If they don't work, try the Reloaded fonts, as I know that they work on the 5105 and 5530 kernel.
I would do the Mad Gouki Guide first to get to EvoX. Then, just to save yourself some headaches (although the unit you mentioned should have an earlier kernel) double-check what kernel it has. You can do this either in EvoX or in MS Dash under Settings and System Info.
Let it scroll and you'll see K: 1.00.xxxx... and D: 1.00.yyyy... where xxxx is your kernel number and yyyy is your dash number. If it is 5530, this is as far softmodding as you can go and will need to font sign things. If your yyyy > 4920, you might need to downgrade your dash. Morden has a great walkthrough on how to do this here:
--- Morden's Exploit Installer/Remover (link to walkthrough [page 52]) ---http://forums.xbox-scene.com/index.php?act...&t=86133&st=765
If it is any kernel number lower than 5530, use my conversion walkthrough to get PBL 1.3.5i running. If you followed my walkthrough, you should be using the X2 4979 BFM Bios on your current XBOX. That one is compatible with the focus encoder, so you shouldn't need to worry about finding another version. Good luck on your second venture... the info I just posted may seem overwhelming, but to summarize:
- Do Mad Gouki's Tutorial first
- If for some reason neither the Free-EvoX nor the Reloaded fonts work, downgrade your dash
- Then, Double check your kernel
- Lastly, use my conversion to setup PBL if the kernel < 5530
Jan 21 2004, 08:37 AM
Top of da mornin to ya. It worked fine. Have a few other questions, what about the red light all my entries are gggg but it still flashes red (its no biggie though). What is the program that is supposed to be better and easier to use than xmenu. Have you got xbmp player working ? Where do you make a movie folder and where do you put the avi. Thanks again.
Jan 21 2004, 03:35 PM
1) The flashing has to do with the sequence programmed into the fonts. There's a guide on changing the reloaded fonts here:http://forums.xbox-scene.com/index.php?act...hl=flashing+red
You could always try switching to a different font set (unless altered they all usually launch C:\default.xbe) and see if the color sequence executed by them are more to your liking.
2) By XMenu, I'm guessing you're talking about the multigame compliation program. There are a few alternatives, Menu-X and MXM (which is also another alternative dashboard). If you don't like configuring files, you could look into obtaining Craxtion and using it's Multigame wizard which can setup discs with both Menu-X and MXM. As a sidenote, a lot of people shun Menu-X as it's basically a hacked version of the XBOX demo disc (and because people have said it's buggy), so try MXM. I know there are other multigame launchers out, and if I haven't mentioned yours I apologize. I've mentioned these two because I figured NaDeS would probably want to use Craxtion's wizard feature. I haven't dabbled too much in multigame compliations (only used Menu-X a couple of times ... blasphemy, I know
) so if anyone else has any recommendations, feel free to post em
3) As for XBMP, the config.xml needs to be configured if you want to get the full usage of XBMP. Each section is broken up by the types of files it can handle. For video, look for the XML Tag:
This contains video related config info. For videos off the HD, check inside the <videos> section for this sub section:
Notice my "e:\videos"; that's the path I'm telling telling XBMP to look for your videos. You can put the videos directly in the e:\videos folder or put folders in that, then search through the folders in XBMP.
Jan 22 2004, 05:06 PM
Thanks again Zogger. Another question is there anything you can't do ?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here