dashlaunch should be pretty easy to use. it will detect your firmware, then ask if you want to install it. hit okay or whatever it says and done. the only problem is I'm not sure how to reinstall it if it's detected.
fat32, btw, I thought the launch.ini you want was called sample_launch.ini instead of info_launch.ini unless they renamed it.
nm, just checked. it is info_launch.ini that you want.
yes, I was mistaken.wait...wait...
I want to rename info_launch.ini to launch.ini and put that on my fat32 flash drive?
Well, not exactly. The other will work but it won't make any adjustments to any other parameters other than what has values assigned in the .ini file. So if you have a bad default opening path but nothing to change it, it will still try going to that bad default opening path.yes, I was mistaken.
it's possible it was the one to use way back when. I've been using dashlaunch since 2.xx, when it would use older files if they hadn't been deleted causing a soft-brick. op, that error has been fixed, so don't worry about it.Well, not exactly. The other will work but it won't make any adjustments to any other parameters other than what has values assigned in the .ini file. So if you have a bad default opening path but nothing to change it, it will still try going to that bad default opening path.
That's exactly why they did the read order the way they did. Ask anyone that ever used a stealth server plugin lol, more brick city than New Jersey.iirc, the launch.ini on external will supersede the one on internal, in case you have one there, so you don't have to worry about something like that. I assume it's a failsafe in case something is catastrophically wrong.
the vita is the same way. that's why I suggest people put a fresh config.txt on ux0 in case something is corrupted with the inaccessible ur0.That's exactly why they did the read order the way they did. Ask anyone that ever used a stealth server plugin lol, more brick city than New Jersey.
that's right. you need to have default set to FSD or Aurora, then you should be good. put the directory listing in there. if you don't know it, put xex menu on a flash drive or burn the disc. it's read as a demo, so it will work even without a flashed drive, probably for this very reason. then go into it, and search for your FSD or Aurora folder.okay plugging in flash drive with the launch.ini and booting up xbox it IMMEDIATELY booted into (sorry for my bad terminology here) the "standard" xbox dash (not fsd)
no, use xex menu to find FSD or Aurora, then use that path in default under boot or whatever it's called in the launch.ini.I just remembered also that I can scroll over to games, and launch XEX MENU 1.1 and get to my games that way.
Does this mean it's an issue with FSD?
Or what do I need to do so that it ALWAYS boots up immediately like this?
FSD is more geared towards just games, Aurora is kinda bloated with a lot of features that you may or may not want. I think it has voice commands, though FS3 might as well. I use FSD2.Aurora/FSD -> is one more stable than the other? I've used FSD since the beginning but doesn't mean it's the best
it was good thinking to see if he could get into xell. though, it would have to be pretty bad corruption if xell didn't work. iirc, it's the first 50 blocks of the nand.Oops. We fixed it on accident.