Xbox:Dashboard Installation

There are a variety of dashboards available for original Xboxes. If your console is not already modded, head to our Xbox:Getting Started guide first. Once it is modded, you may find yourself wanting to change its default system menu.

Managing Files

There are a number of ways to manipulate the files on an Xbox hard disk drive.

As a general rule, it's a bad idea to delete or copy over a program while actively running that program, as files in use may fail to be modified.

• Xbox:FATXplorer allows for a HDD connected to a PC running Windows 7 SP1 or later to be read or written to through Windows Explorer. It can also format new drives from scratch, and once you've backed up a copy of your system's Xbox:EEPROM, it can furthermore manage your drive's locking status. Since FATXplorer can still be launched through your PC even if you accidentally render your Xbox HDD unbootable, it's the safest way to proceed.
• Xbox:XboxHDM is an older tool that allows a PC to write batches of files to an Xbox drive. Unlike FATXplorer, it doesn't offer reading functionality, however it can be used by older PCs which may not be able to run the modernised tool. It can either be booted directly (v1.x, supporting PATA interfaces only), or launched within Windows through a VM (v2.x, additionally supporting disks connected through USB adapters).
• A modded console can run an Xbox:FTP service to allow management of its disk through its Ethernet socket. Most homebrew dashboards automatically start offering FTP access as soon as they launch. Some high-end Xbox:Modchips can launch special firmware-based menus that also offer FTP - for example, Xbox:XeniumOS for Xenium chips. When managing boot files, FTP is safer for hardmods rather than softmods, since hardmodded consoles can always boot a dashboard from DVD to recover if mistakes are made on the HDD. On the other hand, messing up the file system structure of a softmodded machine may softbrick it, after which the HDD will most likely need to be connected to a PC for repair through FATXplorer.
• Most dashboards offer their own on-screen file managers. Xbox:UnleashX and Xbox:XBMC are each able to access other FTP servers, which is useful if you want to copy files directly from other consoles on the same local area network.
• Xbox:Xplorer360 was popular as a graphical tool for reading from or writing to Xbox drives through Windows, but it suffers from bugs which may lead to file system corruption. It's no longer recommended.
• Xbox:Chimp allows an Xbox to clone its own drive structure to a new HDD. It requires a hotswap operation, which comes with a risk of hardbricking your equipment, but can be handy for softmodded users who wish to install a new drive without making use of a PC.

Installation Locations

Xbox executables use XBE file extensions and are functionally quite similar to EXE files. Dashboards, games, emulators, etc - they all launch through XBEs. Setting up a new dash to load on start up is largely just a matter of copying its executable and accompanying files to your disk, and then reconfiguring your mod to launch that new executable.

In times past, dashboard files were usually placed directly onto the root of the C volume, mixing their files in with whichever others happened to be there. As dashboards have become larger and more complex over time, it's now usually best to create specific folders for them with appropriate titles, placed onto either the root of C or one of the console's other partitions.

Partition	Letter	Size	Purpose
1	E	4.78GB	User data. Intended for storing saves, soundtracks, game updates, and DLCs.
2	C	500MB	System data. Intended for storing the MS Dash.
3	X	750MB	Cache volumes used for temporary storage. Although their presence is required by most retail games, they're unsuitable for installing your own software, as any files kept within them will occasionally be wiped.
4	Y	750MB
5	Z	750MB
6	F	(Variable)	First extended partition, not required for normal system function. Generally accounts for whatever storage is still available after the preceding volumes have been defined.
7	G	(Variable)	Second extended partition, for cases where F hits its size limit. Others still may follow, but this is uncommon.

For example, you might extract Xbox:XBMC4Gamers into E:\XBMC4Gamers, resulting in an executable path of E:\XBMC4Gamers\default.xbe.

Smaller dashboards (eg Xbox:UnleashX) may fit into C, but those which cache their own thumbnails (eg Xbox:XBMC) may run out of space there. The Xbox:Microsoft Dashboard does require its content files and subfolders to be placed on to the root of C, and will attempt to load them from there regardless as to where its executable file is launched from.

E offers a lot more room, but if this partition is overloaded then many programs will cease to function. It's also the dedicated volume for game saves, updates, and DLCs. Aim to leave at least 100MB free there at all times.

Some stock Xbox hard drives have approximately 2GB of space left over which can be allocated to create a small extended F volume. Aftermarket HDDs will usually have a lot more space assigned to F, and possibly some to G as well. You may fill these volumes with whatever content you like.

Xbox:XBMC-Emustation installations may become very large, potentially including dozens of gigs worth of emulators, preview media, and of course ROMs. This dashboard in particular is best suited to a well-sized F or G.

Changing Your Startup File (Softmods)

On start up, an Xbox running stock firmware will either launch D:\default.xbe from the optical drive (starting a game, if a valid retail Xbox disc is inserted), or otherwise C:\xboxdash.xbe (starting the Xbox:Microsoft Dashboard menu application from the internal HDD). Without mods, third-party executables put in place of the stock dashboard's XBE will be rejected by the system's DRM mechanisms, resulting in a crash to a service screen (displaying either error 13, 14, or 16).

A softmodded console has patches its font files, exploiting the original dashboard into patching the kernel each time C:\xboxdash.xbe is launched (or possibly into loading a brand new kernel, depending on the softmod in use). Control is passed to some other XBE. Many older softmods simply switch off to C:\evoxdash.xbe.

With a system configured by Rocky5's Xbox Softmodding Tool, by default Xbox:Dashloader will load the first dashboard it can find on your system. Prior to adding any other dashboards to your console, this file will be C:\Dashboard\default.xbe - a copy of Xbox:UnleashX included with the softmodding tool. Other dashboards can simply be dropped into folders on your drive, and if placed where Dashloader expects them to be, it'll automatically load them instead of the default dash. Alternatively, Dashloader Customiser can also be copied to your drive and used to select a specific executable for Dashloader to boot, as well as to assign other executables to your controller buttons.

If you're not already using a softmod with Dashloader (or if you're simply not sure), start out by copying the files from Rocky5's Quick Upgrade.zip over to your console and running it in order to switch. Note that this will re-write your C partition, so back up the contents first if you feel it holds anything of value.

If you're currently unable to run software from your Xbox hard drive at all (eg say you broke your file system, or you're wanting to set up a new disk from scratch), use Xbox:FATXplorer to totally clear any data from C and then to place the files from Rocky5's XBHDM Build.zip there instead. If you're working with a new drive, remember to use FATXplorer's Security Tools panel to enable Xbox:Drive Locking - for which you'll need the HDD key from your Xbox:EEPROM backup.

Changing Your Startup File (Hardmods)

Hardmodded consoles (which have either had their TSOP flashed or a modchip installed) boot directly into a modded state using custom firmware, and are then able to immediately launch third-party executables without first loading any exploit files. Replacement BIOSes usually first check the optical drive for D:\default.xbe (attempting to start a game disc in the same manner as stock firmware does), but if no bootable disc is present then they'll follow on through a list of other possible dashboard locations on the HDD. Whichever file happens to be found first gets launched.

The lists of sought executables vary from BIOS to BIOS - however, in most all cases C:\evoxdash.xbe is at or near the top, and C:\xboxdash.xbe is at or near the bottom. If you have a hardmodded console and C:\evoxdash.xbe exists on your drive, then it's most probable that this is the file your BIOS will be launching for you. Note that it isn't necessarily the EvolutionX dashboard's executable - other dashboards often have their executables renamed to use the same title, as a simple way to ensure that most every BIOS will be able to find them.

If you wish to change your default boot path, one option is to reconfigure your BIOS. Another is to set up a shortcut application to start your dashboard from a different location instead.

BIOS Configuration

Depending on which BIOS you're using, reconfiguration may require you to reflash your TSOP or Modchip - for eg, an EvoX BIOS needs to be tweaked through the PC-based EVtool application and then re-written into your firmware chip. If you *are* presently using such a BIOS, then since you'll be reflashing anyway you might consider switching to CerBIOS, which reads boot path settings from an INI kept on your console's HDD.

The following table lists the default dash pathes searched by later versions of few common BIOS types. Paths may vary for earlier versions. Most BIOSes can be expected to fall back to C:\xboxdash.xbe if none of the "configured" paths lead to an actual file.

	EvoX	iND	X2 4XXX	X2 5XXX	CerBIOS	Stellar
Dash1	C:\evoxdash.xbe	C:\evoxdash.xbe	C:\avalaunch.xbe	C:\avalaunch.xbe	C:\evoxdash.xbe	E:\dashboard\default.xbe
Dash2	C:\avadash.xbe	C:\nexgen.xbe	C:\evoxdash.xbe	C:\evoxdash.xbe	C:\avalaunch.xbe	-
Dash3	C:\nexgen.xbe	C:\avalaunch.xbe	C:\mxmdash.xbe	C:\unleashx.xbe	C:\nexgen.xbe	-
Dash4	-	-	-	C:\xbmc.xbe	-	-
Dash5	-	-	-	C:\xboxdash.xbe	-	-
Reconfiguration	EVtool, then reflash	C:\ind-bios.cfg	XBtool, then reflash *	E:\x2config.ini	C:\cerbios.ini	Unconfigurable (?)

* The final BIOS supported by XBtool is the X2 4981 release. The X2 4983 cannot be reconfigured.

Using Dashloader with a Hardmod

Instead of reconfiguring your BIOS to check through a different list of pathes, you may instead place the hardmod version of Xbox:Dashloader at one of the pre-configured locations (eg C:\evoxdash.xbe). Actual dashboards can then be dropped into folders on your drive, and if found where Dashloader expects them to be they'll be launched automatically. Dashloader Customiser can also be copied to your drive and used to select a specific executable for Dashloader to boot, as well as to assign other executables to your controller buttons.

Installing Other Software

Once you've selected and installed your dashboard of choice, you'll also want to install some other applications for your dashboard to launch for you. Copying them to folders on your hard drive is easy enough, but exactly how you reconfigure your dashboard to list them depends on the particular dash you're working with.

Fortunately, many dashboards are pre-configured to look for other programs in certain locations, and if you're aware of where these are then you shouldn't need to spend much time looking at config files.

Retail Xbox game discs each include a default.xbe file on their root. When placed into your console's DVD (D) drive, the system looks for D:\default.xbe and launches it. Due to this convention, homebrew dashboards likewise expect any other programs copied to your Xbox HDD to use a file titled default.xbe as their main executable. Some programs, homebrew in particular, may be downloaded with different XBE titles: it's fine to rename these so that your dashboard can find them.

If you wish to install Xbox game disc images from your PC, Repackinator can largely automate this process for you, setting them up through either Xbox:FTP or Xbox:FATXplorer. For game discs that you own yourself, Xbox:DVD2Xbox allows an Xbox to dump them directly to its own hard drive.

For manual installation, software should then be placed into subfolders on E, F, or G like so:

• Retail games should be placed into Games.
• Homebrew games should be placed into Homebrew or Ports.
• Emulators should be placed into Emulators.
• Demo disc dumps (eg Official Xbox Magazine disc images) should be placed into Demos.
• Other utitilies (including dashboards, if you want them to be listed in the menus of other dashboards) should be placed into Apps or Applications.

Using these folder structures will not only ensure that most dashboards will be able to find your software "out of the box", but it will also enable the Xbox:Xbox Artwork Installer to find them automatically as well.

For example, a simple layout might look something like:

   💽F
   └📁Games
    ├📁Fable TLC
    │├📄default.xbe
    │└📄other game files...
    └📁Halo 2
     ├📄default.xbe
     └📄other game files...
   💽G
   └📁Games
    └📁Time Splitters 3
     ├📄default.xbe
     └📄other game files...

A standard dashboard such as Xbox:UnleashX would then be expected to present a single "Games" menu listing Fable, Halo 2, and Time Splitters 3 together. Note that most dashboards will also read game titles from within default.xbe files - the names of the folders your individual games are stored in usually won't have any impact on how your final menu will appear. Some dashboards, such as Xbox:UnleashX or Xbox:XBMC, also offer functions allowing you to edit the titles embedded into XBEs.

The Xbox:Microsoft Dashboard is a tripping point, since it needs to load its content files from the root of the C volume. If you want it to be listed within another dashboard's menu system, then that dashboard will need to be specifically configured to find its C:\xboxdash.xbe executable file.

Fortunately again, most dashboards are already configured to do this by default and will offer a dedicated "MS Dash" link somewhere within their front menu structure. A "catch all" workaround for those dashboards which are not configured this way is to copy C:\xboxdash.xbe to E:\Applications\MS Dash\default.xbe. Note that the other files which make up the MS dash still need to exist on C - but so long as they're sitting in their usual location, launching the copied MS dash executable from another volume will work just fine.

CerBIOS BFM

Some users may wish to make use of the CerBIOS custom firmware package (which allows for larger hard drives than most other kernels, as well as support for compressed image mounting), but they may not have the means to flash it into a firmware chip. For example, 1.6 systems lack a flashable TSOP, and without the purchase and installation of a modchip are limited to softmods. Some cheaper modchips also can't be rewritten without the use of external hardware, meaning some unlucky hardmodders will still find it difficult to flash new firmware.

Fortunately, whether softmodded or hardmodded, if reflashing is a problem then it's easy to load a BFM (Boot From Media) version of CerBIOS from the HDD instead, and to have CerBIOS load your dashboard afterwards. The following instructions describe how to set up a BFM BIOS loader to run automatically on boot.

CerBIOS BFM (Softmods)

1. If you haven't already, use one of Rocky5's installers to softmod your system in the usual ways - either a Xbox:Game Save Exploit to set up stock system with a new softmod, the Quick Upgrade.zip package to move up from an older softmod, or the XBHDM Build.zip package if you're preparing a new disk from scratch. If you are installing a larger drive, you should specifically use Xbox:FATXplorer to format it for use with CerBIOS. Do not, however, attempt to resize the C/E/X/Y/Z volumes away from their default capacities.
2. If you haven't already, use Rocky5's Extras Disc to install the Xbox:Microsoft Dashboard. Note that you may optionally launch an image of this disc from your HDD without burning it by following the instructions in the Documents and Extras folders.
3. Rocky5 makes use of NKpatcher to enable a feature called ShadowC on your system. Each time your softmod is loaded from your C partition, it immediately hides that volume - instead mounting a virtual disk in its place. This virtual disk won't be available whenever CerBIOS loads, and the associated image file consumes nearly all space available on your real C volume, so extract your desired dashboard to a folder on E or F instead. If you're using a CerBIOS-formatted drive then you'll require FATXplorer to manage F at this stage in the process.
4. Obtain a copy of the latest CerBIOS build and extract it to a folder on your PC. Both a flashable and a BFM copy of the firmware package will be included in the archive.
   1. Copy the Pheonix Bios Loader (sic) folder to your Xbox disk somewhere. Feel free to rename the folder if you wish. Placing it alongside the MS dash files inside your virtual C partition is fine.
   2. Modify the DashPath1 value within Cerbios.ini to point to your dashboard executable on E (Partition1) or F (Partition6).
   3. Cerbios.ini must be placed in to your true C partition, outside of your ShadowC volume. To achieve this, either launch the NKpatcher Settings application and connect over Xbox:FTP while it's running, or use Xbox:FATXplorer through your PC.
5. Launch the default.xbe file within your Pheonix Bios Loader directory and verify that the dashboard you specified within Cerbios.ini starts correctly. You should also notice that your virtual C partition isn't mounted, and so C:\Cerbios.ini is visible.
6. Reboot to unload CerBIOS (and re-activate ShadowC), then download and install Dashloader Customiser to your console. Launch it and set PBL's default.xbe file as your "custom dash" (to be automatically started on boot). Additionally set C:\xboxdash.xbe to a controller button - holding this on start up will allow you to load the MS dash in future. You should furthermore assign Dashloader Customiser's own executable to a controller button.
7. Press Start to save and exit Dashloader Customiser. On the next boot, your softmod will start Dashloader, Dashloader will start PBL, PBL will load CerBIOS, and CerBIOS will start your preferred dashboard. Should you need to start the MS dash, holding the controller button you assigned it to will prevent CerBIOS from being loaded, allowing the stock menu system to be launched from ShadowC.

DO NOT simply extract the MS dash to your true C partition! This action will break your softmod, reverting your system to stock!

CerBIOS BFM (Hardmods)

You should either use Xbox:FATXplorer for all file operations here, or you should FTP in while running a dashboard that is located outside of your C partition.

1. If you're setting up a new hard drive, first use FATXplorer to format it for use with CerBIOS. Do not, however, attempt to resize the C/E/X/Y/Z volumes away from their default capacities.
2. Extract your desired dashboard to a folder on either C, E, or F. (If you're using a CerBIOS-formatted drive then you'll require FATXplorer to manage F at this stage.) If you wish to have the Xbox:Microsoft Dashboard as well, extract its files directly to the root of C.
3. Obtain a copy of the latest CerBIOS build and extract it to a folder on your PC. Both a flashable and a BFM copy of the firmware package will be included in the archive.
   1. Copy the contents of the Pheonix Bios Loader folder to the root of your C partition. Rename the default.xbe file to evoxdash.xbe.
   2. Modify the DashPath1 value within Cerbios.ini to point to your dashboard executable on either C (Partition2), E (Partition1), or F (Partition6). Copy the altered INI to the root of your console's C partition.
4. On the next boot, your modchip's BIOS will start PBL, PBL will load CerBIOS, and CerBIOS will start your preferred dashboard for you.