Dashlaunch 2.33 Installation (JTAG)

To accompany FSD, you need one very cool little tool. Dashlaunch, lets you you automatically boot whatever dash you want without having to specifically run it's executable file.

This means when you boot your 360, whichever dash you want will automatically load. You can also assign buttons to act as triggers, that when held during boot, will load seperate dashes, or any xex file you wish.

As of the latest Kernel (13599), you'll want to be using Dashlaunch 2.33.


Step 1) Download & extract Dashlaunch 2.33 to its own folder




Step 2) Open & use the "sample_launch.ini" file as a template, ammending the settings to suit your own console/directory structure. Here you can see I have the sample on the left, & one customised for my own console on the right.

• Button X is defaulted to run XeXmenu when held during boot - I've left that setting alone.
• The Default trigger I've changed from USB to HDD, as I'm using an MS drive for this job. Also the default name for FSD is wrong, so I've ammended that too.
• It's also worth noting that while it's not shown in the template, I had to change Hdd1:\ to Hdd:\ (drop the 1) for the console to recognise the directory.

Step 3) When you extraced the Dashlaunch archive into its own folder, you will notice there is a subfolder called "Installer". Inside this folder is a "default.xex" which needs to be transferred to your jtag. I created a folder called "Dashlaunch" on the root of the jtag's hdd, & placed this "default.xex" file & my modified "launch.ini" file inside via an ftp transfer




Step 4) On your jtag now, navigate to where you placed both the default.xex & launch.ini files. Execute the xex file, which will then present you with the flashing menu





(apologies for the blurry pics)


Step 5) Press A to confirm flashing of the launch.ini settings into flash, & if its a first time install, A again to change settings (I won't cover this as it runs through loads of different settings which users can customise to their liking).








If all has gone well, you will confirm a shutdown. Upon booting back up, Dashlaunch is now active & will actively use the settings in your launch.ini file. If you just turn the console on, FSD should auto load without having to do a single thing






It puts a nice touch on a JTAG, no more fumbling around in XeXmenu etc etc. Also, with the above launch.ini file, Button X will load XeXmenu, & the RB button will load the standard dash (NXE) (The RB button is hard-coded for this, that's why there's no reference to it in the launch.ini file).

Only hold the trigger buttons down when the pad syncs on bootup, if you hold it beforehand, the pad will sync but the button press won't be registered.

Enjoy