|
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 |
Full Version: Dash Launch v2.09 Beta
nice 
QUOTE
patches updated to remove min version check
Doesnt work off disks but works fine once converted to god.
where is this located in xbins? i can never find it :\
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/
thank you very much.
hope it fixes bootup problem freezing :\
edit: yes it's fixed and way faster
hope it fixes bootup problem freezing :\
edit: yes it's fixed and way faster
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...
The only thing i don't understand is why do we need this to play DA2? if DA2 has a new update ( an ew dashboard) wouldn't it make sense to wait for a new freeboot? or am I missing something?
It doesn't have the update on the disc, but it does have have a minversion of 12625, so you would need to update via live or USB/CD in order to run it, even on a stock box.
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
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
Nice job keep up the good work
Thx. Honestly im just happy someone released anything for jtag......... getting mighty dry around here.
So I was at 2.08 and applied this 2.09 version--now my JTAG hangs at startup. It gets partway into the swirling startup logo, stutters for a moment and then locks everything. Not quite sure what to do now. Any advice?
Solved (sort of), in case anybody else runs into this same issue.
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.
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.
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..
I have a Samsung F4 2TB and FSD2 set as the default boot, DashLaunch 2.09 gives me no issues regardless of when the drive powers up.
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).
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).
QUOTE(cory1492 @ Mar 7 2011, 05:44 PM)
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..
Nope, I use NXE primarily. Here's my launch.ini, if anyone cares:
QUOTE
; launch.xex V2.0 config file
; parsed by simpleIni http://code.jellycan.com/simpleini/
; note that Right Bumper is ALWAYS default to return NXE
; currently supported devices and paths:
; internal hard disk Hdd:\
; usb memory stick Usb:\
; memory unit Mu:\
; USB memory unit UsbMu:\
; big block NAND mu FlashMu:\
; CD/DVD Dvd:\ (not recommended to use this one)
; buttons can point to any xex, or any CON with default.xex in it on any of the above devices
[QuickLaunchButtons]
; Default is what loads when you hold no buttons, leave this blank if you want NXE as default
; example default entry
; Default = Hdd:\FreeStyle\default.xex
Default =
BUT_A =
BUT_B =
BUT_X = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_Y = Hdd:\Freestyle\default.xex
Start =
Back =
LBump =
[Plugins]
; example plugin entry
; plugin1 = Usb:\plugin\aplugin.xex
plugin1 =
plugin2 =
plugin3 =
plugin4 =
plugin5 =
[Settings]
; if true, brining up miniblade in NXE and then pressing Y will cause launch.xex to relaunch for you
; note you must release Y button then press desired QuickLaunchButtons after or use default item
; if not present default is TRUE
nxemini = false
; if true ping limit will be removed for system link play (thanks FBDev!)
; if not present default is FALSE
pingpatch = true
; if true (most) xbla will no longer need yaris patching (thanks mojobojo!)
; if not present default is FALSE
contpatch = false
; Normally when a fatal error occurs the xbox will just freeze, setting this to false will cause a reboot or powerdown
; if not present default is FALSE
fatalfreeze = false
; when fatalfreeze is set to false, setting this to true will cause the box to reboot, setting it to false will instead have the box shut down
; note that this option does NOTHING when fatalfreeze is set to true
; if not present default is FALSE
fatalreboot = false
; when set to true, it is possible to hold RB when launching a game to have the region that the game gets from xam spoofed
; if not present this is set to false
regionspoof = false
; when regionspoof is true, you set your region here in hex, for examle devkit would be region = 0x7fff
; if not present but regionspoof is set to true, this is set to 0x7FFF
region = 0x7FFF
; when set to false, ejecting a dvd video returns you to your default item, set to true to auto exit to dash
; if not present this is set to false
dvdexitdash = false
; when set to false, using the exit item in an XBLA game returns you to your default item, set to true to exit to NXE arcade menu
; if not present this is set to false
xblaexitdash = false
; when set to true, using miniblades system setting options will not exit to NXE
; if not present this is set to false
nosysexit = false
; all comments and fields in this file are optional, you can remove anything you don't need
; section headers [] are required for any used options under the section
; parsed by simpleIni http://code.jellycan.com/simpleini/
; note that Right Bumper is ALWAYS default to return NXE
; currently supported devices and paths:
; internal hard disk Hdd:\
; usb memory stick Usb:\
; memory unit Mu:\
; USB memory unit UsbMu:\
; big block NAND mu FlashMu:\
; CD/DVD Dvd:\ (not recommended to use this one)
; buttons can point to any xex, or any CON with default.xex in it on any of the above devices
[QuickLaunchButtons]
; Default is what loads when you hold no buttons, leave this blank if you want NXE as default
; example default entry
; Default = Hdd:\FreeStyle\default.xex
Default =
BUT_A =
BUT_B =
BUT_X = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_Y = Hdd:\Freestyle\default.xex
Start =
Back =
LBump =
[Plugins]
; example plugin entry
; plugin1 = Usb:\plugin\aplugin.xex
plugin1 =
plugin2 =
plugin3 =
plugin4 =
plugin5 =
[Settings]
; if true, brining up miniblade in NXE and then pressing Y will cause launch.xex to relaunch for you
; note you must release Y button then press desired QuickLaunchButtons after or use default item
; if not present default is TRUE
nxemini = false
; if true ping limit will be removed for system link play (thanks FBDev!)
; if not present default is FALSE
pingpatch = true
; if true (most) xbla will no longer need yaris patching (thanks mojobojo!)
; if not present default is FALSE
contpatch = false
; Normally when a fatal error occurs the xbox will just freeze, setting this to false will cause a reboot or powerdown
; if not present default is FALSE
fatalfreeze = false
; when fatalfreeze is set to false, setting this to true will cause the box to reboot, setting it to false will instead have the box shut down
; note that this option does NOTHING when fatalfreeze is set to true
; if not present default is FALSE
fatalreboot = false
; when set to true, it is possible to hold RB when launching a game to have the region that the game gets from xam spoofed
; if not present this is set to false
regionspoof = false
; when regionspoof is true, you set your region here in hex, for examle devkit would be region = 0x7fff
; if not present but regionspoof is set to true, this is set to 0x7FFF
region = 0x7FFF
; when set to false, ejecting a dvd video returns you to your default item, set to true to auto exit to dash
; if not present this is set to false
dvdexitdash = false
; when set to false, using the exit item in an XBLA game returns you to your default item, set to true to exit to NXE arcade menu
; if not present this is set to false
xblaexitdash = false
; when set to true, using miniblades system setting options will not exit to NXE
; if not present this is set to false
nosysexit = false
; all comments and fields in this file are optional, you can remove anything you don't need
; section headers [] are required for any used options under the section
Toddler, any disk in the dvd drive? Also, check to see if auto start disk is on or off in the system settings, some have claimed this affects dash launch regardless of whether there is a disk in the drive.
Thanks, but nope--no disc in the drive, and I don't have auto start turned on.
- RESOLVED -
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.
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.
Good catch Toddler! If you read the change log you'll know that while the ini still follows the same format, it's no longer (from 2.08 to 2.09) using the C++ code from simpleini to do the parsing... which means the ini parser in the dll is entirely new, and easily explains this problem. Turns out the bug is actually not related to the [] but instead in not having a newline/carriage return at the end of that comment line (and even then, depending on the size of the ini it was only a tiny chance of hitting the bug.) Reported as fixed for next version.
Ah yes, that makes sense now. When I removed the last two lines, I left the blank line above them in place. I shouldn't have assumed it was the brackets--if it had been my own project, I would have kept testing further and nailed it down--sorry about that. Thanks for taking it seriously and figuring it out.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.