Topic: Dash Launch v2.10 Beta (Read 479 times)

harrytasker · « **Reply #15 on:** March 13, 2011, 12:58:00 PM »

QUOTE(TheRealJPizzle @ Mar 13 2011, 07:42 PM)

change to

[QuickLaunchButtons]
Default = Hdd:\fsd2\default.xex

Thanks! that worked! bit strange though cause all is installed on Hdd1. Thanks anyway!

GARRYB · « **Reply #16 on:** March 13, 2011, 02:14:00 PM »

i cant even seem to find this on xbins anyone want to help me out please?

CopyLifted · « **Reply #17 on:** March 13, 2011, 03:02:00 PM »

I can also confirm that the 360 crashes when trying to launch a xbox 1 game.

Hopefully there will be a 2.11 soon with this fixed.

Thanks for the hard work.

dough4you · « **Reply #18 on:** March 13, 2011, 03:11:00 PM »

Do we still have to add the 30ms ping remover patch separately, or does DashLaunch 2.1 include it natively now?

dough

soulwarrior · « **Reply #19 on:** March 13, 2011, 03:55:00 PM »

QUOTE(dough4you @ Mar 13 2011, 05:11 PM)

Do we still have to add the 30ms ping remover patch separately, or does DashLaunch 2.1 include it natively now?

dough

If by this you mean do you have to put kxam.patch in the root of hdd1; the answer to this has been no since around the time of Dash Launch v2.0 which was released in September of 2010. Hence the option to set ping to true while you are running the dash launch installer and/or manually adding to your launch.ini:

[settings]
pingpatch = true

If this is not what you are referring to, disregard.

- soulwarrior

antisniperspy · « **Reply #20 on:** March 13, 2011, 05:54:00 PM »

QUOTE(danthaman673 @ Mar 13 2011, 02:44 AM)

Thanx again guys for your commitment to addressing issues as they come-up (Dash launching seems to be a finicky business :-)

Oh yeah, I've noticed some probs occuring when two MS-MU's AND one or more USB-MU's are connected (eg; MU's don't mount, bounces to NXE and wont re-launch from mini-blade)

I haven't updated BTW (I'm still on 2.08) I'll let u know if 2.10 solves any/all issues
Brgds/Dan

I noticed this also that if I plug in a MU with the xbx already running it wont mount the MU. I think this works fine on my normal xbox.

antisniperspy · « **Reply #21 on:** March 14, 2011, 10:18:00 AM »

QUOTE(cory1492 @ Mar 13 2011, 11:23 PM)

Need to know exactly where this is happening, I haven't been able to reproduce using a MU, USB MU and USB stick without a usb MU on it in NXE using various random reinserts of any of them.

What happens is I have dash launch set to launch the newest fsd. So when I start the xbox and its sitting on the FSD screen I will insert a MU which has my gamertag and saves. But the xbox wont pick up the newly inserted MU. Even if I go back to the original microsoft dash it will not pick it up. I dont know if its a problem with FSD or Dashlaunch but my JTAG use to pick up newly insert memory cards.

antisniperspy · « **Reply #22 on:** March 14, 2011, 10:20:00 AM »

Still can't edit my posts but I have
-dashlaunch 2.11
-newest freeboot
-Jasper 512

RRoD420 · « **Reply #23 on:** March 14, 2011, 12:41:00 PM »

QUOTE(brwcrw @ Mar 12 2011, 09:23 PM)

lol

I'm not BI-POLAR, what does that even mean? i'm BI-WINNING.

cory1492 · « **Reply #24 on:** March 14, 2011, 08:26:00 PM »

QUOTE(antisniperspy @ Mar 14 2011, 09:18 AM)

What happens is I have dash launch set to launch the newest fsd. So when I start the xbox and its sitting on the FSD screen I will insert a MU which has my gamertag and saves. But the xbox wont pick up the newly inserted MU. Even if I go back to the original microsoft dash it will not pick it up. I dont know if its a problem with FSD or Dashlaunch but my JTAG use to pick up newly insert memory cards.

I'm told this is a FSD issue, something to do with it not having the code yet to handle parsing content on newly inserted devices. As to why it affects NXE (even if you pull the drive out again and put it back) I have no clue - but I'm sure it'll be fixed somewhere down the line.

antisniperspy · « **Reply #25 on:** March 14, 2011, 10:23:00 PM »

QUOTE(cory1492 @ Mar 14 2011, 09:26 PM)

I'm told this is a FSD issue, something to do with it not having the code yet to handle parsing content on newly inserted devices. As to why it affects NXE (even if you pull the drive out again and put it back) I have no clue - but I'm sure it'll be fixed somewhere down the line.

Ok thanks it was just weird that even after returning to NXE that it still wont see the new MU.

xboxhaxorz · « **Reply #26 on:** March 16, 2011, 01:12:00 PM »

QUOTE(soulwarrior @ Mar 14 2011, 12:38 PM)

Sorry if this comes off as rude but you couldnt have looked in every folder otherwise you would have found it where it's always been: xbox360-development-system apps-dashlaunch

well there are a lot of folders, and i would have no idea to look in that directory myself

but hey now we know

Author Topic: Dash Launch v2.10 Beta (Read 479 times)