CODE
XexTool.exe -d resource default.xex
this will give you a folder called "resource" with files like "13146z" (patches_zephyr.bin for 13146) (z=zephyr, x=xenon, j=jasper, f=falcon) "lhelper" (lhelper.xex) and "launch" (launch.xex)... if you put lhelper.xex and launch.xex beside fbbuild exe, you can build images with it already installed. This will bypass any issues with the installer itself, and the rest is going to come down to ini issues. Using a USB key with a launch.ini on it is very helpful to try different settings to see if you can find the problem one, as USB keys are relatively fast (compared to USB hdd) and the USB ini will be loaded before/over any other.
QUOTE(Midnight Tboy @ Jun 19 2011, 08:20 PM)

BUT I do have other dashlaunch problems from the last version (usb/memory unit detection when not inserted on bootup)...so woulda been nice to see if it fixed it
This was initially thought to be a dash launch problem... but turned out to be a FSD problem. Give it a go, run anything
BUT FSD (xexmenu, nxe, games) and see if removing/adding a USB stick gives you an issue. If you still have a problem then, please post back.