Launch.ini

[Elwanda Menhennett]

Juststart dashlaunch and let it save a new ini file. You have to set anything new up but standart settings are mostly used. If you need special settings just do it with dashlaunch. There is mostly a description to each option.

There is a launch.ini option that disables the hud. Find it in the launch.ini and set it to false, or remove that line completly. You can also use dashlaunch installer to easily change this on the xbox. when done, reboot the console.

Dont know if this is related to launch.ini.

I Have copyed 2 games folder's to my new hdd and fsd dont see them. I did this through xexmenu from internal hdd to usb hdd. When I put the new (usb) hdd in the console it wont see the folders and also the origanal hdd wont be seen as a usb drive.

Is ther some setting I need to alter?

Forgot to mention I put exemenu, fsd and dashlaunch via usb drive. (Fresh install)

Do I need to transfer a file from FSD

I Have copyed 2 games folder's to my new hdd and fsd dont see them. I did this through xexmenu from internal hdd to usb hdd. When I put the new (usb) hdd in the console it wont see the folders and also the origanal hdd wiont bw seen as ausb drive.

It's really hard to say, it could be many reasons... i don't know what your paths look like, i don't know what format you used, i also don't know what settings you've got... you need to supply more information to get further assistance with this matter...

Well, if you can't work with the paths, your FSD installation is broken and you need to redo it, delete all FSD files and install them fresh... (download the latest release and install) or better yet; move to Aurora which is the new dashboard from the same ppl, it's faster and generally just better!

I think the problem is with the original HDD (320gb which was a standard HDD hacked to be a Microsoft HDD) Somewhere down the line I think something as got corrupted as I used to be able to see some not all the contents when booted with stock nand and now I don't see anything

I would recommend that you completely format that 1TB harddrive on your internal port then put everything back there from scratch, not copying from your old hdd, but put them there fresh, and check if it shows and so on, if not, then you have a very strange console...

If that works, i'd recommend going from there by cutting your losses with the old drive and format it aswell... (tho that has to be formatted in the original dash in order to work properly with the original dash!)

DashLaunch is a custom dashboard, usually used as a tool for tweaking deep system settings. The most common usage for DashLaunch is to set a custom dashboard to be the default one on system startup, and to manage target fan settings, and install plugins. Keep in mind that you must save your changes if you make any modifications by going to the "Save \ Load launch.ini" menu and pressing X on HDD.

This menu allows you to load (A), delete (Y), or save (X) a launch.ini config. To save the config, highlight the desired location to save it to, and press X. It is recommended to save config files to HDD to have them run at startup.

(The only other question I have is, do I need to fully install the application to have access to the extracted files? Or should everything be compiled from the Standalone Install File of the program I am working with?)

Launcher.ini (the generic working title we give to the file, it never will actually be called that) isn't documented in the format specification, I assume because once upon a time it wasn't part of the spec at all, and still is not 100% required (Firefox Portable, among others, doesn't use it), but it is required if you use the PortableApps Launcher to generate the portable executable.

This is the file that tells the Launcher which executable it should run within App\AppName\ on launch, and also tells it the other necessary details like registry, file and folder handling that are needed for portability.

Okay so I now understand a great deal with the launch.ini.

1st. You say it is required if I utilize the launch generator to create the ported exe. Is there a better way to generate the portable exe? I only assume this was the only option as all the tuts and docs I read told me to use it.

2nd. If I go ahead with my setup(use the launch.ini method) do I point the [launch] program.exe= to the standalone install file (firefox_setup.exe just example) or do I install the program to a seperate directory and then point it to the launch.exe there and compile everything?

Basically I am missunderstood on where some of the automated compiling of the app will happen(take all necessary data from the standalone install file) or if I am going to manually compile everything on my own(install the program and extract what data and files I will need[and how will this result in portability if im just copying what is already in another directory])

I am sorry for the detailed inquiry. I really want to picko up on this and if it helps I do have a bachelor s degree in Information Technology and I just wasnt able to fit any programming type classes in my schedule.

The PortableApps Launcher doesn't automatically compile anything in regard to the base app you are trying to make portable, as I said above you have to copy the installed application into the directory structure for your soon-to-be-portable app.

This will give you a list of all the registry changes made during the running of the app (note that not all of them will actually be associated with the app, and some may be about the app but not from the app (they may be from a firewall, antivirus or Windows itself, it takes time and a little immersion to come to know the what the difference is). From this you can determine the registry entries that need handling (and if the app uses a version of QT that needs handling, as well) and can put the necessary entries into your Launcher.ini.

Also with RegShot you may want to set it up to scan a folder or folders for changes. I have mine setup to scan my user directory (eg. C:\Users\Ken) as this is where 99.9% of file changes are going to take place in modern software on a modern Windows OS. Thus it will also give you most of the file/folder handling that you need to add to your Launcher.ini.

Anything else you need to know, just let us know. You don't need programming knowledge to put apps into PortableApps format, the primary skill you do need is analytical problem solving. If you are good at thinking through a problem, you will pick this up reasonably easily. As an example, an app that requires the working directory to be set isn't going to tell you that, but with a little problem solving and some trial and error you can figure it out.

1 more thing. I noticed some portable suites like cameyo etc. Claim to copy / embed registry strings that an app needs to run and package them with the portable app. Is there a way to do this the portablapps.com way? I plan to use portable apps on protected systems that may not allow registry access to 3rd party or usb apps so is there any way to make an app work within its own directories and subs by packaging something or equal to the registry: without direct access to the local pc registry?

I've honestly never tried one of our apps on a system locked down to that level before so can't give you a definitive answer. The best case you could hope for is the app to not need those entries for proper operation and it will run fine but be missing some settings. You would just have to test it, I guess.

Off the top of your head do you know of any apps on the Download page that utilize the \Launch.ini method as something of a reference for me to compare my setup with. I dont wish to download every app to see if they use that type of launch.ini but I guess I will if I have too.

3a8082e126