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 SettingsI 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