Ken -I would have emailed this to you, but I didn't see your email in the FS Autostart documentation...I have a couple of suggestions to really make FSAS really great:1) Move the default fsautostart.ini out of the Windows directory. In general I prefer to not have any applications with write privilages there.2) In the past, I used an autostart application much like yours(I forget the name...), and it had a nifty feature that inhibited applications of your choice from being executed until there was a FSUIPC connection available. This would be nice for starting applications that will crash if there is no FSUIPC connection...for me to emulate this feature now I have applications starting 6 or 7 minutes after fs9.exe is executed. Yes, my beast is slow.3) Seperate the configuration utility from the execution utility. Ie have one application you run to make changes to the .ini files, and then have another that will startup fs9. That way you avoid having to create .bat files to execute FSAS without seeing the configurationg GUI.4) It would be nice to be able to run certain applications before fs9.exe is executed. For instance, all of my flightplanning software could be executed, then FSAS waits for all of these applications to stop being executed, and then executes fs9.exe. I know this is probably the dumbest of things, but still :)Ken, I really, really appreciate what you have done with FSAS. I use FSAS, and love it. Thank you sir!

I had a feature request too - an extension from my 'planets' thread:Now that I have FSAS configured, all I do from the first window is click start. I'd love to have a command line so I could make another icon that skips loading the first window, and just launches everything as configured, straight away. I'm lazy, I know. "I have to DOUBLE click the icon, AND click the START button?!?! Can I skip that last step?" I'm just looking for that one click access to get my FS fix. ;)I use FSAutoStart all the time - a priceless utility; thanks again!Best,sg

That goes along with my third feature request.

Thanks for the feedback. I am working on a new build, fyi ;-)1) Okay :-)2) One way to do this is set the delay after MSFS is started before starting other software to a high value. I think I defaulted to 60 seconds, but this can be changed in the configuration screen. So you can set it to something like 3 minutes (180 seconds), which will give MSFS enough time to load and init FSUIPC before starting the other apps.3) They are separate. Look in your install folder, you will see a program called fsasctl.exe. This is the execution program. It takes one command line, the path to the ini file to use. So you can create a shortcut to this program with the command line you want. In the next build I will be making this process (and management of multiple profiles) much easier.4) In the works ;-)

Thanks Ken, you are the man! :D I am looking forward to your new build.