I have MXM menu running just fine with the Matrix skin however my menu refuses to display the game content of the G drive at the same time as the F one. I have tried a search regarding this topic but have drawn a blank. Any help would be greatly appreciated. My bios can't be the problem as Evox configured with no problem to autolist PxHDD directories or F,G and E at the same time. Thanks.
What I basically want to do is select 'Games on Hard Drive' and have the menu read games in the three drive locations, E,F,G.

OK, I what I am trying to say is that MXMenu doesn't see my G drive and as such doesn't auto add the games stored there.
When I was running Evox, the machine had no problem at all combining the contents of F: and G: in one list of games.
Is this possible with MXMenu. Thanks aneone that can help.

Post your menu.xml here (if you have one)

If I'm not mistaken, MXM is supposed to automatically scan/mount your drive G if you have one.

If you FTP into your xbox while running MXM, do you see your drive G? If yes then it's a menu issue. If no, then theres something else going on that maybe BJ can chime in on.

What version are you using?

Hi Guys, thanks very much for interest so far:

I am running Media X Menu Version 0.9n.6Beta

My MXM.xml looks like this:

<Config>
<Main>
<DiscTitle>Media X Menu</DiscTitle>
<DiscSubtitle> </DiscSubtitle>
<SkinsPath>c:\mxm</SkinsPath>
<LoadSkin>retro</LoadSkin>
</Main>

<!--
<URL>http://www.xbox-scene.com/xbox1data/xbox-scene.xml</URL>
<AllowVideoSound>True</AllowVideoSound>
-->

<Network>
<UseDHCP>True</UseDHCP>
<IP>192.168.1.110</IP>
<DNS1>192.168.1.1</DNS1>
<DNS2>192.168.1.1</DNS2>
<DefaultGateway>192.168.1.1</DefaultGateway>
<SubnetMask>255.255.255.0</SubnetMask>
</Network>

<FTPServer>
<ServerPort>21</ServerPort>
<AllowAnon>False</AllowAnon>
<AnonRoot>\</AnonRoot>
<User>
<Name>xbox</Name>
<Password>xbox</Password>
</User>
</FTPServer>

</Config>

<Menu>
<SubMenu>
<Title>Play Games From HD</Title>
<item>
<Autodir>F:\HDDLoader</Autodir>
</Item>
</SubMenu>
<SubMenu>
<Title>Emulators</Title>
<Item>
<AutoDir>F:\Apps\Emulators</AutoDir>
</Item>
</SubMenu>
<SubMenu>
<title>Mediaplayer</title>
<item>
<AutoDir>F:\Apps\Mediaplayer</AutoDIR>
</item>
<item>
<dir>F:\Apps\dvdx</dir>
<exe>F:\Apps\dvdx\default.xbe</exe>
<title>DVD-X2 DVD-Player</title>
</item>
</SubMenu>

<submenu>
<title>System Management</title>
<item>
<exe>F:\APPS\x-switch\default.xbe</exe>
<title>X-Switch</title>
</item>
<item>
<exe>F:\APPS\dvd2xbox\default.xbe</exe>
<title>DVD 2 XBOX</title>
</item>
<item>
<exe>F:\APPS\HDDLOADER\default.xbe</exe>
<title>Copy Game to HD</title>
</item>
<item>
<exe>F:\APPS\boxplorer\default.xbe</exe>
<title>XboXplorer</title>
</item>
<item>
<exe>F:\APPS\xcommander\default.xbe</exe>
<title>Xcommander</title>
</item>
<item>
<exe>F:\APPS\xtoolbox\default.xbe</exe>
<title>Xtoolbox</title>
</item>
</Submenu>

<SubMenu>
<Title>Programs</Title>
<item>
<AutoDir>F:\Apps\</AutoDIR>
</Item>
</SubMenu>

</Menu>

I have Evox running still on the F drive (Boot) if required and if I boot from there the G is always identified.

Hope this helps further.

I am feeling generously kind today

Thanks very much guys for taking time out to read and edit my post.

I have cut and pasted the edited file with G drive references onto my XBox (And reset the menu cache after doing so) but unfortunately still no joy.

One other point of note is that when I use FlashFXP to examine/ edit the contents of the XBox hard drive that will not open the G drive content either, reporting 'Directory not found'.

I still have no problem at all accessing the G Drive if I boot to Evox on the F Drive.

Do you have any more ideas??

What is the reported sizxe of your F:? MXM will only access G: if your F: is a specific size... this is due to the fact that X2 BIOSes will hang if you attempt to access G: and there is no partition available for it.


The MXM_Patcher can also "force" the issue, but only run the patched version as an app before installing it as a dash, in case it hangs.

What BIOS, and what sort of patch are you using to get G:?

Hi Ben, thanks very much for support:

MXMenu reports in System Information that my F Drive is 129,493,207,680 bytes in size.

I am currently running Evox M7, LBA48 G. bios.

I installed both the bios and MXMenu using Firefu**ers XDisk 0.93.

MXMenu also reports in System Information that no G drive is present. Even if I drop out of MXMenu into Evox using the menu commands in my MXM.xml (As listed in full above) I get full G drive functionability.

Well, 0.9n.6 fully supports G:, and your F: size is fine.


Try the MXM_Patcher and create a special version. Beyond that, I don't know... you are the first person to report this problem after several months of G: support.

sorry, i have the same problem and 2 of my friends too...
i use an 4981.67 Bios an i tried all but cant see the g drive.

so i use avalaunch, when i want to play from g and other times MXM...

i´ve searched the whole forum too about this problem, but every try dont help

the g drive will not mounted form MXM

when i start my xbmp from MXM, its not a problem and i have access to g

Yeah I was going to say when you dload the .rar file there is the default.xbe inside of it as well as a program called MXM Patcher, use that to patch the file with whatever loading screen you want. Then in the bottom of the patcher window ther is two check boxes one for drive f: and one for drive g:, make sure both of those boxes are checked off.... Then patch it and rename the defalut.xbe to whatever is your default dash name (ex. evoxdash.xbe or mxmdash.xbe), or if you run as an app then you just leave it named default.xbe...

If this does not fix your problem then you will want to flash a new BIOS to your mod or TSOP as it is the thing not giving you proper g: support....

Thanks very much guys for all the support.

Just tried the patcher with same result so I will check and double check all the info you have given me so far. It must now be down to user error, so I'll keep at it.

Thanks again, great support.

Try using the X2 4981.67 BIOS and tell me if that works.

what exactly is the benifit to drive G? I keep hearing about it but does it really matter where u store the games and apps?

DrunkPenguin

It works.

I eventually got it going using my original Bios. Just deleted the launcher and then did a fresh upload using a newly downloaded file. I guess I must have had some problems with the original download. Thanks again for all your help.

PS Fantastic work on the launcher.

Just to answer the question above, the G Drive is additional storage over the 137Gb limit of the supported F drive. Basically if you install a hard drive over 137Gb then the additional storage is configured as G drive.

Oh yeah I almost forgot to ask. What "original bios" are you using now to get MXM to recognize your G drive?

Congrats on getting up and running again.

Sounds like he re-downloaded MXM. Perhaps he got a messed up version, originally?

I am currently running Evox M7, LBA48 G. bios

whoops misread the post. i thought u changed your bios. either way, glad to see your up and running with MXM