Post by: Xbox-Scene on March 12, 2011, 06:05:00 PM
| cOz released a new version of Dash Launch for JTAG 360s. What's new/fixed: * reworked hooking to be a bit more dynamic and simpler to update * ini parser fixed, glitch when comment line last line with no blank line after (thanks Toddler!) * disables updaters (DA2 and other disks; safety) * minor tweaks to boot time delays, further improves on previous autologin issue Known Bugs: * Thanks to excellent testers, none were corned by the time of this writing. If you find any during use, find the release thread at xbox-scene and please report them there. * in freestyle 1.7 and earlier, there was a minor glitch that caused console crashing for some people under rare circumstances, if you haven't updated to RC1.8 or newer please do so. Official Site: n/a, by cOz Download: n/a (built with XDK) Full Readme/NFO: xbins.org |
Post by: DARKFiB3R on March 12, 2011, 07:15:00 PM
Post by: brwcrw on March 12, 2011, 07:23:00 PM
QUOTE(DARKFiB3R @ Mar 13 2011, 03:15 AM) 
#WINNING
lol
Post by: Tiduss on March 12, 2011, 07:57:00 PM
Because i have 1tb 32mb Wd green drive and e76 problem(drive spin up to much time and xbox think its damaged)
When i plug hdmi cable after drive spin up its all ok.
Post by: Unimatrix47 on March 12, 2011, 08:03:00 PM
Post by: juggahax0r on March 13, 2011, 12:28:00 AM
Post by: danthaman673 on March 13, 2011, 12:44:00 AM
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
Post by: 40_ounce on March 13, 2011, 01:04:00 AM
Post by: Chandy12 on March 13, 2011, 01:45:00 AM
Cheers
Post by: Knasen on March 13, 2011, 07:23:00 AM
I understand it has to do with Dragon Age 2, but what is the problem now? The game booting issue was fixed with the previously released version.
This post has been edited by Knasen: Mar 13 2011, 02:24 PM
Post by: Dwack on March 13, 2011, 09:55:00 AM
QUOTE(Knasen @ Mar 13 2011, 08:23 AM) 
Anyone care to explain what the following does exactly: "disables updaters (DA2 and other disks; safety)".
I understand it has to do with Dragon Age 2, but what is the problem now? The game booting issue was fixed with the previously released version.
It patches the system so that the newest games(wave 11/12??) will play without asking for you to update the system. Another reason why a 12625 rebooter is not necessary.
Post by: schubi on March 13, 2011, 10:29:00 AM
QUOTE(Chandy12 @ Mar 13 2011, 09:45 AM)
Thanks for this only one problem it turns xbox 360 off when I try to boot xbox 1 games, I have gone back to v2.09 no problem booting xbox 1 games with that version
Cheers
can anoyne confirm or disprove this xbox1-games bug ? thanks...
Post by: Xfreaks on March 13, 2011, 11:01:00 AM
QUOTE(Chandy12 @ Mar 13 2011, 03:45 PM)
Thanks for this only one problem it turns xbox 360 off when I try to boot xbox 1 games, I have gone back to v2.09 no problem booting xbox 1 games with that version
Cheers
Same problem here. even with re-installed the xbox1 patched files.
it need fix !!!
Post by: harrytasker on March 13, 2011, 11:18:00 AM
[QuickLaunchButtons]
Default = Hdd1:\fsd2\default.xex
Any idea??
BTW Falcon MB
This post has been edited by harrytasker: Mar 13 2011, 06:21 PM
Post by: TheRealJPizzle on March 13, 2011, 11:42:00 AM
QUOTE(harrytasker @ Mar 13 2011, 12:18 PM)
thanks, but i can't get it to work installation works fine no errors, but keeps booting in NXE:
[QuickLaunchButtons]
Default = Hdd1:\fsd2\default.xex
Any idea??
BTW Falcon MB
change to
[QuickLaunchButtons]
Default = Hdd:\fsd2\default.xex
Post by: harrytasker 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!
Post by: GARRYB on March 13, 2011, 02:14:00 PM
Post by: CopyLifted on March 13, 2011, 03:02:00 PM
Hopefully there will be a 2.11 soon with this fixed.
Thanks for the hard work.
Post by: dough4you on March 13, 2011, 03:11:00 PM
dough
Post by: soulwarrior 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
Post by: antisniperspy 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.
Post by: antisniperspy 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.
Post by: antisniperspy on March 14, 2011, 10:20:00 AM
-dashlaunch 2.11
-newest freeboot
-Jasper 512
Post by: RRoD420 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.
Post by: cory1492 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.
Post by: antisniperspy 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.
Post by: xboxhaxorz 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