For those who uses MenuX (and GDFimage.exe) I would just like to tell you a glitch I found out from trial and error that will cause the game to be unbootable or unrecognised buy the Xbox (I have a Samgsung drive BTW).
MenuX consists of the a folder called "iso" and inside the folder "iso" there is a folder called "menux" (which contains all the MenuX sound and graphics).
As the instuctions tells us we should put a game inside the folder "iso" but each games should be in their own folders.
As we all know when GDFImage creates and image the image will be built in alphabetical order of the folders.
I have found out that IF you put games with a letter before "M" referring to the "menux" folder when you create an image of the folder "iso" the folder "menux" will be put at the end of the image.
Since "default.xbe" is in the folder "iso" "default.xbe" will be put at the start of the image, and if the folder "menux" is at the end of the image the xbox will have problem booting the game becuase "default.xbe" and the contents inside the folder "menux" is too far apart.
At first I thought it was just the media or I burnt it wrong but after trying many times the result was the same. So I tryed making "default.xbe" closer to the folder "menux".
As you can see I put a "X" infront of the game folders, the reason was so when i build the image it will build the contents inside "iso" then "menux" then "xct3" then "xhalo" which then makes "default.xbe" (which is inside folder "iso") closer to the contents inside the folder "menux".
This has worked perfectly for me everytime, the only explaination of not booting I can think of was becuase when the drive boots "default.xbe" it will look for the contents in folder "menux" straight away, scanning through all the game data files then finding the file it needs at the end of the disc. This delay was too much and caused trouble during booting.
I have also found out that this problem onl occurs when the disc is near full and with game folders before "m".
Please correct me if I have anything wrong.
Also this problem might only occur if you happen to have a Samsung drive
Edited by viper_8548, 13 February 2003 - 09:11 AM.