Can't get Dashlaunch working...boots to NXE

[mike523]

Ok everything was working mostly fine on my RGH but I couldn't get any of my DLC content working and since I was using an older Dashlaunch (2.26) I figured the first thing I should do is update.

I downloaded the DL 3.0 beta and installed that from USB via my Xexmenu disc. Unfortunately upon reboot the xbox just went to NXE.

I spent 4 hours last night and another half hour this morning before work trying to figure this POS out and I'm gonna try to make a long story short here. This seems to be an issue with launch.ini. I have tried editing the paths in the launch.ini file to make certain they point to my Freestyle directory on HDD1 but it would either just outright not work or sometimes I think Dashlaunch would overwrite the file and undo my changes.

The only marginal success I had was with DL 2.29 which for some strange reason would install and work instantly without any screwing around on my part. Only problem is once I did that ALL of my XBLA games became locked even though I unlocked them all with XM360.

*sigh*

I've read every Dashlaunch install tutorial I can find and I still can't figure this mess out.

Where EXACTLY does the launch.ini file need to be placed for DL to find it and load FSD?

Does it need to be placed in the DL Installer folder BEFORE running the install?

Where does DL put the launch.ini file after install? I see one on my HDD1 root but is it possible that DL is putting one in the flash memory as well that I have so far been unable to find?

Any help with this would be greatly appreciated guys.

 

[Ticallion]

Is this with a trinity by any chance? I've had a few that would not run FSD off the 250gb hdd no matter what when simply editing launch.ini, had to use the FSD live installer (setting it to update to latest version) before it would take effect. I suggest using that, as it will implement dashlaunch 3.0 anyway and should resolve any issues you're having.

 

[mike523]

No its a Jasper, and I don't think I can use the FSD live installer because I burned out my ethernet port when I did my RGH install LOL

 

[BL4K3Y]

The DashLaunch 3 installer lets you choose a destination for your configured launch.ini.

You are also able to set the path to your default item (FSD) and if this isn't correct, FSD won't automatically boot with the console.

Are you able to post the contents of your launch.ini file here?

 

[talby71]

just to let you know with DL2.29 have to set contpatch=false for XBLA to be unlocked
think it was for 2.30 as well then it was changed back to true for DL 2.32

 

[mike523]

The DashLaunch 3 installer lets you choose a destination for your configured launch.ini.

You are also able to set the path to your default item (FSD) and if this isn't correct, FSD won't automatically boot with the console.

Are you able to post the contents of your launch.ini file here?

Unfortunately I won't be able to post the launch.ini file until I'm home this evening but I tried multiple configurations...

The installer never asked me to choose a destination, in fact the install process was very brief and abrupt, it wasn't like the installs for 2.29 and 2.30...makes me think something else was wrong.

The 3.0 installer is kind of a GUI right? I would run it and it would tell me I had 2.26 or 2.29 or whatever already installed and I would click OK if I wanted it to update. Then I'd get the message telling me I had to reboot and all that. Anyways, I've seen screenshots of this GUI on the web and they looked different from mine, the browser windows were full of options and files and stuff and mine were all empty no matter which one I was on, if that makes any sense.

---------- Post added at 12:49 ---------- Previous post was at 12:48 ----------

just to let you know with DL2.29 have to set contpatch=false for XBLA to be unlocked
think it was for 2.30 as well then it was changed back to true for DL 2.32

Yeah I was reading about that, I kept changing that line in the launch.ini but it wasn't working...maybe I was messing with the wrong launch.ini.

 

[Martin C]

Dashlaunch and FSD are two entirely different things. ANY version of dashlaunch should allow FSD to boot provided you edited the ini file correctly to point to it.

Your launch.ini can either live on an internal MU, Flash, HDD or USB device. You will need to post the contents of it before anyone can advise.

 

[Ticallion]

Ahhh dude scroll all the way down for the "default" tab on DL3.0 and then navigate to where the FSD default.xex is on your hdd, this will tell it where to look for FSD, and select the "save default.ini to hdd" (or something like that) option, this should see you right, I had the same problem when I first tried DL3.0.

 

[mike523]

Ahhh dude scroll all the way down for the "default" tab on DL3.0 and then navigate to where the FSD default.xex is on your hdd, this will tell it where to look for FSD, and select the "save default.ini to hdd" (or something like that) option, this should see you right, I had the same problem when I first tried DL3.0.

I'll see if I can find that "default" tab later when I get a chance to work on it again and report back.

---------- Post added at 13:20 ---------- Previous post was at 13:19 ----------

Dashlaunch and FSD are two entirely different things. ANY version of dashlaunch should allow FSD to boot provided you edited the ini file correctly to point to it.

Your launch.ini can either live on an internal MU, Flash, HDD or USB device. You will need to post the contents of it before anyone can advise.

So what if I had a launch.ini located in the root of my HDD1 that I keep editing, but DL was automatically installing one on my internal MU or someplace I couldn't find it? That might explain some of my difficulties.

 

[BL4K3Y]

So what if I had a launch.ini located in the root of my HDD1 that I keep editing, but DL was automatically installing one on my internal MU or someplace I couldn't find it? That might explain some of my difficulties.

I think Flash/Internal memory take priority, although I haven't ever put launch.ini on any of these devices (I use the internal HDD).

You can easily move or delete multiple launch.ini entries from their respective locations - you only need one configured launch.ini.

 

[Martin C]

I think the order is USB, HDD, IntMU, Flash. This makes sure that a launch.ini on a USB stick takes priority for recovery reasons.

 

[mike523]

Ahhh dude scroll all the way down for the "default" tab on DL3.0 and then navigate to where the FSD default.xex is on your hdd, this will tell it where to look for FSD, and select the "save default.ini to hdd" (or something like that) option, this should see you right, I had the same problem when I first tried DL3.0.

Maybe you mean the "Miscellaneous" tab on the DL3.0 installer. There is an option called Install This and it is described as "Copies this program to DL30\default.xex in the folder you choose". When I click that it goes to the "Browse" tab and its just blank, it doesn't show any folders or anything and I can't navigate anywhere.

---------- Post added at 22:00 ---------- Previous post was at 21:59 ----------

Here is an idea of what one of my launch.ini files looks like :

[QuickLaunchButtons]
Default = hdd:\FreeStyle\default.xex

[Settings]
nxemini = true
pingpatch = false
contpatch = true
fatalreboot = true
regionspoof = true
xblaexitdash = true
debugout = false
livestrong = true
remotenxe = true

 

[Martin C]

Did you write the launch.ini yourself or was it created for you?

Can you confirm what's in 'FreeStyle' on your HDD?

 

[mike523]

And this is the one I found in my flash memory:

The difference is the 1 after hdd

[QuickLaunchButtons]
Default = hdd1:\FreeStyle\default.xex

[Settings]
nxemini = true
pingpatch = true
contpatch = false
fatalreboot = true
regionspoof = true
xblaexitdash = false
debugout = false
livestrong = true
remotenxe = true

---------- Post added at 22:14 ---------- Previous post was at 22:12 ----------

Did you write the launch.ini yourself or was it created for you?

Can you confirm what's in 'FreeStyle' on your HDD?

It was created for me although after multiple failures I did edit it and try to stick it on there myself.

Inside my Freestyle directory on HDD1:

Data
Docs
Media
Plugins
Skins
default.xex
nxeart

 

[BL4K3Y]

If you have FSD on your internal hard drive, the default line would be: Default = Hdd:\FreeStyle\default.xex (where FreeStyle is the name of the folder).

 

[mike523]

To reduce any confusion, where should my ONE launch.ini file be located? I've been trying to install DL3.0 again today and failing that have begun trying to install 2.32. When doing 2.32 it tells me during the install that it finds a launch.ini at \Device\Mass1\ and another one at \Device\Harddisk0\Partition1\

 

[BL4K3Y]

As I said in one of my previous posts, your hard drive is fine.

I have FSD located on my internal hard drive and I put launch.ini on the root of said hard drive.

 

[mike523]

Ok and it doesn't matter if there are others floating around? I'm just trying to rule out having more than one launch.ini floating about my xbox and them not having the same contents would make it harder to troubleshoot.

 

[BL4K3Y]

It *shouldn't* matter but I would remove them anyway seeing as they won't be used at all.

 

[Martin C]

If you put a copy of launch.ini on a USB stick, this should be read first. You can have it pointing to the install on your HDD too.