Post by: Xbox-Scene on March 03, 2011, 09:51:00 PM
| cOz released a new version of Dash Launch for JTAG 360s. What's new/fixed: * moved strictly to C, much smaller DLL * correct bug with busy CON/sometimes ignoring ini for boot time default item * made boot time quick launch buttons more reliable * added 1s delay to resolve autologin at boot issue and slower USB hdd issues * patches updated to remove min version check (DA2) Known Bugs: * Some users have found that freestyle set as a default item or returning to freestyle from NXE via miniblade hook is freezing the machine. If you have issue with this bug, please use the 2.08 launch.xex in the files directory and re-run the updater Official Site: n/a, by cOz Download: n/a (built with XDK) Full Readme/NFO: xbins.org |
Post by: DARKFiB3R on March 04, 2011, 12:53:00 AM
Post by: majinsoftware on March 04, 2011, 03:54:00 AM
QUOTE
patches updated to remove min version check
Doesnt work off disks but works fine once converted to god.
Post by: hfmls on March 04, 2011, 04:03:00 AM
Post by: non2100 on March 04, 2011, 04:12:00 AM
QUOTE(hfmls @ Mar 4 2011, 08:03 PM) 
where is this located in xbins? i can never find it :\
/XBOX 360/development/system apps/dash_launch/
Post by: hfmls on March 04, 2011, 04:13:00 AM
hope it fixes bootup problem freezing :\
edit: yes it's fixed and way faster (IMG:style_emoticons/default/smile.gif)
This post has been edited by hfmls: Mar 4 2011, 12:18 PM
Post by: cory1492 on March 04, 2011, 03:34:00 PM
QUOTE(majinsoftware @ Mar 4 2011, 03:54 AM)
Doesnt work off disks but works fine once converted to god.
If the 12625 updater is on the disk, it will try to force you to install it - breaking that would also break installing avatar and kinect data...
Post by: tommyvice on March 04, 2011, 03:47:00 PM
Post by: DARKFiB3R on March 04, 2011, 05:29:00 PM
You can patch the xex using xorloser's X360GameHack, but that would cause further issues with TU's and DLC in the future.
Dashlaunch saves the day... again
Post by: antisniperspy on March 04, 2011, 06:15:00 PM
Post by: DaBuisneZ on March 05, 2011, 06:02:00 PM
Post by: Toddler on March 06, 2011, 06:23:00 PM
Post by: Toddler on March 06, 2011, 07:48:00 PM
I have a Jasper 256 with AUD_CLAMP wiring, and a 750GB Western Digital Scoripo Blue (WD7500BPVT) in the internal shell. There is a jumper setting which enables RPS (Reduced Power Spinup), which does just what it says--it boots slightly slower in order to draw less power at spinup:
WD Scoprio Drive Jumper Settings
I jumpered my drive that way because doing so eliminated the 3-4 times out of 100 that my JTAG did not boot properly. Figuring the 360 would always take longer to startup than the drive will, I saw no reason not to enable RPS. However, this new 2.09 version supposedly boots more quickly than the older versions.
Knowing that, I thought Dashlauch may be looking for launch.ini file before the drive is even ready. It seems like that may be the case, because with the drive connected, I was unable to boot at all and consistently hung during the 360 startup logo. Without the drive connected, I booted with 100% success.
The "fix" for me was booting without the drive, then connecting it while powered on, which forced the 360 to warm reboot without Dashlaunch in the mix. I then ran the 2.08 installer, downgraded Dashlaunch, and now I am back in business.
I hope the final version handles this scenario a little more gracefully.
This post has been edited by Toddler: Mar 7 2011, 03:56 AM
Post by: cory1492 on March 07, 2011, 04:44:00 PM
QUOTE(Toddler @ Mar 6 2011, 07:48 PM)
I hope the final version handles this scenario a little more gracefully.
Did you have freestyle set as the default item, so that it starts that instead of NXE? If so see "known problems" in the opening post of this thread.
If anything, 2.09 should be more reliable provided what you have mentioned is the actual issue, as it just waits for ~3s longer before actually doing anything and 1s of that (always) before looking for ini on anything..
Post by: tk_saturn on March 07, 2011, 06:27:00 PM
The console does sit at the logo screen for 1-2 seconds before powering up and syncing controller with the Samsung connected, but that's down to the drive and not DashLaunch (did the same with 2.08).
This post has been edited by tk_saturn: Mar 8 2011, 02:34 AM
Post by: cory1492 on March 08, 2011, 03:04:00 PM
Post by: Toddler on March 08, 2011, 05:28:00 PM
Post by: Toddler on March 08, 2011, 08:38:00 PM
The issue was not the drive jumper settings. The issue was with my launch.ini file as posted above. For some reason, Dashlaunch 2.09 chokes with the brackets in the commented last two lines of the ini file. Makes no sense to me (1) why 2.08 has no issue but 2.09 does, or (2) why it matters at all since the lines are commented. At any rate, I removed the brackets and 2.09 is now running reliably with RPS jumpered on my WD drive.
Post by: cory1492 on March 09, 2011, 12:12:00 AM
Post by: Toddler on March 09, 2011, 11:57:00 PM