Print

[Xbox-Scene]

Dash Launch v2.01 Posted by XanTium | September 17 21:46 EST | News Category: Xbox360

cOz released a new version of Dash Launch for homebrew 360s. What's new/fixed: * corrected flash mu mount point (thanks Antho02 at l-s) * added kernel version check to installer as some xbr using folks seem incapable of reading the first line of this file Official Site: n/a, by cOz Download: n/a (built with XDK)

[ZBeeblebrox]

Not exactly sure it caused it, but when I installed this with the included installer, I ended up with a blank hard drive.
I have a 320gb drive formatted by XBR (but been on Freeboot .032 since it came out) that has been working fine. I installed Dashlaunch 2.0 with no errors (updated but didn't change any settings in the ini). I then installed Dashlaunch 2.01 today with the installer (as I have a Jasper 256), updated the ini, as well as changing settings (ini on HDD). When I rebooted the system, I ended up back in NXE and the hard drive showed as Unformatted. I flashed back to plain Freeboot, but the HDD still showed as empty. I'm refilling it now, and then will install Dashlaunch 2.01 again to see if it's repeatable.

[bengrimsy]

thats scary that people dont even check the readme or the nfo and just flash it while running XBR. but if you are still running XBR you probably paid someone to jtag for you, so they probably dont have a clue. but come on people read up before you attempt anything if you dont understand whats going on.

[Big_Ted]

I have a falcon, running 9199, using fsd, I found before patching with dash launch v1 some of my xbla games didn't work from usb using fsd, after installing v1 all xbla worked fine, I put this down to a region free patch.
now I have updated to v2.01 and xbla only some work again, feeding frenzy is the one i tried. Any sugestions??


Ted

[crook iz back]

same problem i have always had with v1 straight to nxe on boot even though ive put something for default but when im in a game and i click y to go to dashboard it takes me to wha i specified in the ini now with 2.1 none of my QL buttons work they did in v1 idk man this is buggy

[MrFlooD]

I am running a 512 Jasper. Installed Fine but simply wont boot into anything.

Here is what my ini looks like.

[QuickLaunchButtons]
BUT_A = Hdd:\Freestyle\default.xex
BUT_B = Hdd:\Apps\xm360\XM360.xex
BUT_X =
BUT_Y =
Start =
Back  =


my default is blank.


Hope someone can help me solve this.

[RyZombie]

Hey MrFlood,

I'm Fairly certain that your ini should read like this:

[QuickLaunchButtons]
BUT_A = Hdd1:\Freestyle\default.xex
BUT_B = Hdd1:\Apps\xm360\XM360.xex
BUT_X =
BUT_Y =
Start =
Back =


Try that and you should be good!

[MrFlooD]

QUOTE(RyZombie @ Sep 19 2010, 10:46 PM)

Hey MrFlood,

I'm Fairly certain that your ini should read like this:

[QuickLaunchButtons]
BUT_A = Hdd1:\Freestyle\default.xex
BUT_B = Hdd1:\Apps\xm360\XM360.xex
BUT_X =
BUT_Y =
Start =
Back =
Try that and you should be good!

THANK YOU! Works perfectly now

[cory1492]

QUOTE(MrFlooD @ Sep 19 2010, 05:39 PM)

THANK YOU! Works perfectly now

Wish I knew how that could be the case... not able to replicate and the code clearly uses

CODE

    {"Usb:",        MOUNT_MASS0,    3, (strlen(numDevs[0].mountPoint)-1)},
    {"Hdd:",        MOUNT_HDD,        1, (strlen(numDevs[1].mountPoint)-1)},
    {"FlashMu:",    MOUNT_SFC,        1, (strlen(numDevs[2].mountPoint)-1)}, // flash memory unit big block
    {"Sfc:",        MOUNT_FLASH,    1, (strlen(numDevs[3].mountPoint)-1)},
    {"Mu:",            MOUNT_MU0,        2, (strlen(numDevs[4].mountPoint)-1)},
    {"UsbMu:",        MOUNT_USBMU0,    3, (strlen(numDevs[5].mountPoint)-1)},
    {"Dvd:",        MOUNT_CDROM,    1, (strlen(numDevs[6].mountPoint)-1)},

Hdd: as the text to look for in the ini file.

[tsb128]

I can confirm the issue/feature too.

There is an inconsistency with parsing the HDD path.

Default only works with "Hdd:"
QL buttons only work with "Hdd1:"

Default = Hdd:\FreeStyle2\default.xex
BUT_X = Hdd1:\FreeStyle\FreestyleDash.xex

[cory1492]

I'm still not seeing any inconsistency... the ini file I have on the flash drive for testing this stuff:

CODE

[QuickLaunchButtons]
BUT_A = Usb:\test\default.xex
BUT_X = Hdd:\Freestyle\FreestyleDash.xex
BUT_Y = Hdd1:\Freestyle\FreestyleDash.xex
Default = UsbMu:\Content\0000000000000000\00000001\00080000\000000010F586558

and the log of the parse, the final mount is for the actual launch of the default item and the initial mounts are looking for the launch.ini and kxam.patch

CODE

launch.xex: mount \Device\Mass0\ to dlaunch: sta:Success
launch.xex: mount \Device\Mass1\ to dlaunch: sta:Success
launch.xex: mount \Device\Mass2\ to dlaunch: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1\ to dlaunch: sta:Success
launch.xex: mount \Device\BuiltInMuSfc\ to dlaunch: sta:Success
launch.xex: mount \Device\Flash\ to dlaunch: sta:Success

parsing: Default
lpath: UsbMu:\Content\0000000000000000\00000001\00080000\000000010F586558
Mount: dlaunch:\Content\0000000000000000\00000001\00080000\000000010F586558
launch.xex: mount \Device\Mass0PartitionFile\Storage\ to dlaunch: sta:Success
FOUND! dlaunch:\Content\0000000000000000\00000001\00080000\000000010F586558

parsing: BUT_A
lpath: Usb:\test\default.xex
Mount: dlaunch:\test\default.xex
launch.xex: mount \Device\Mass0\ to dlaunch: sta:Success
FOUND! dlaunch:\test\default.xex

parsing: BUT_X
lpath: Hdd:\Freestyle\FreestyleDash.xex
Mount: dlaunch:\Freestyle\FreestyleDash.xex
launch.xex: mount \Device\Harddisk0\Partition1\ to dlaunch: sta:Success
FOUND! dlaunch:\Freestyle\FreestyleDash.xex

parsing: BUT_Y


launch.xex: mount \Device\Mass0PartitionFile\Storage\ to dlaunch: sta:Success

You'll notice that BUT_Y never mounts or checks anywhere (and also does not work while the others work fine), because "Hdd1:" is completely unknown to the parser while "Hdd:" is not... is there anything else you guys are doing consistently (like saving the file as unicode instead of utf-8) that should be done to reproduce the problem? I can't make it happen with release or builds with debug text, it always works just like it should...

This post has been edited by cory1492: Sep 20 2010, 07:22 AM

[tsb128]

Cory thanks for checking into this.
After leaving the xbox overnight the parsing is now working as expected.
I have no idea why.
I then tried a hundred different things to get the same behaviour as before but the parsing is working perfectly.

I have noticed something else, on boot only the standard ms dash or "default"  will load regardless of which button is being pressed.
Everything is fine when using the mini blade, seems to not work on bootup.
Can anyone else confirm?

[CVLAIS]

QUOTE(tsb128 @ Sep 21 2010, 04:03 AM)

I have noticed something else, on boot only the standard ms dash or "default"  will load regardless of which button is being pressed.
Everything is fine when using the mini blade, seems to not work on bootup.
Can anyone else confirm?

You have to wait until after the controller has synced to the console before you hold down a button.

CVLAIS

[RyZombie]

QUOTE(MrFlooD @ Sep 20 2010, 12:39 AM)

THANK YOU! Works perfectly now

No problem, it's how it worked for me aswell

And Cory1492
What type of xbox are you using to replicate the problem, We are both using BB 512 Jaspers, I know my Internal MU is Unformatted, and I'm not sure about MrFlooD's. Also I'm running dash launch straight from the Hdd not a external usb stick or usb hard drive? I'd be glad to help you out in any way possible to help you solve this.

Also I saved the .ini in notepad with the default notepad save button when i edited it.

[cory1492]

Can you pass me your ini? Just zip it up and stick it on some server and PM me (don't upload the plain text ini without zipping, just in case.)

I'm using a falcon and a jasper 256M BB for testing and I've not been able to replicate any ini parsing issues on this end.