If you guys are having problems with it, it needs to be fixed... obviously that is going to require some coherent information to find out what the problem actually is (or at least a method to reproduce the issue, "tried everything" is a little too vague, because I've literally
tried everything at least twice, on both a jasper and falcon console, and never had similar issues.)
The 1.0 version of swap.xex is going to cause problems, be sure it's not
set as a plugin in any of your ini files or at least make sure you are using the 1.1 version. Dig around on the root of your drives, and make sure there is no kxam.patch anywhere, the new check for version should remove that as a problem source... but you never know.
Pay attention to what the installer is saying, if it says it wants to install patches for a xenon when you have a falcon... or asks you (with a warning) to install patches twice, something is definitely wrong. Make sure you aren't copying the install folder over a previous version, you won't get the current launch.xex/lhelper.xex if you do that and that can cause big problems. Older versions of freestyle/fsd had problems that became apparent when "autologin doesn't work, often" was fixed in dash launch, make sure you aren't using an old version of freestyle.
Last but not least, you can use xextool to extract the installer's resources
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.
Edited by cory1492, 20 June 2011 - 04:56 AM.