http://library.avsim.net/esearch.php?CatID...util&DLID=43489Howdy gang!FSAutoStart v1.0 Build 4a is now available in the library.Here are the changes:***FIXED bug where program crashes when trying to handle dependencies***Added ability to run on Windows 9x/MEAdded ability to Force Idle Tasks to Execute (XP only)Added ability to shutdown all instances of a program. Needed in Windows 9x/ME since a program would only be listed once but have multiple windows openRevamped help system for services and programsAdded ability to detect dependencies for services and recursively close the dependencies as neededAdded ability to remember programs that were previously configured but are not currently running in the GUINOTE 1: I did not include the help for services. I am waiting on approval for displaying the information. When/if I receive approval, I will release the information in the next build.NOTE 2: For those users that received a test build, please install this as there are some differences in what you received and the final version.I appreciate all the positive feedback. I plan one more release unless you guys come up with more features you want to see.Sorry for the re-building because of the bug.

THANKS!

Thanks for the update!

Hi Ken,Just three questions:1. Can I install this build directly over the previous or should I uninstall build 3 first?2. If build 4a is installed over build 3 will the configuration settings in Fsautostart.ini be preserved?3. Could you explain the purpose of the 'Force Idle tasks to Execute' check box, please.Really appreciate what you are doing here for us :)Thanks,Mike

1) Uninstall build 3 first2) Yes3) http://www.microsoft.com/whdc/hwdev/platfo...ion1261211201204) Thanks!

Once again, THANKS A LOT Ken! You did it again :)Bruno Francescoli.

I went ahead and installed build 4a after first copying the old Fsautostart.ini and uninstalling build 3.I replaced Fsautostart.ini in the Windows folder before doing the build 4 install and compared the old ini file with the new one.It appears that the build 4a install modifies the previous Fsautostart.ini without deleting the configuration data. So, I guess the answer to my second question is... Yes. The configuration settings would be lost otherwise and FSAutostart would have to be reconfigured unless the file was copied and preserved prior to uninstallation as I did. Alternatively, it may be that the ini file is left in the Windows folder as part of the uninstall process.MikeEdit: Sorry, I didn't notice your reply before I posted :(BTW, I noticed a mispelling of Execute (Exceute)

Yes, the ini files are left during uninstall for that reason - so you don't have to configure if you install again.BTW, you know you can kill the desktop by setting the explorer.exe to stop. But Win XP will automatically restart it. You can turn this off in the registry:HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionWinlogonName = AutoRestartShellSet to zero (0). Reboot.What does this give you? More memory and CPU. Is it beneficial? I don't know...judge for yourself! :-)

"you know you can kill the desktop by setting the explorer.exe to stop. But Win XP will automatically restart it. You can turn this off in the registry".....interesting, but would this affect my ability to access the task bar during a simming session? Currently the only other program I start with FS is FSCamera. I might, however, decide to start a weather program after FS is running and to accomplish this I would need to be able to access the Start menu.The other thing that concerns me a little about killing the auto restart of desktop is I have occasionally encountered a problem with an errant program causing the system to 'crash' momentarily. The desktop clears of icons, blanks and then promptly resets itself. Would this automatic recovery capability be lost?What do you think - is it really worth doing? Might be worth the performance penalty (if any) just to preserve this feature.Mike

Well I'm not sure...I'm doing some experimenting so we'll see. I normally have everything I need to my flight running, so I have no need for the desktop.You could run the taskmanager as an autostart program - it will give you the ability to run programs.On my system the desktop uses on average 22MB of memeory.

Hi Ken,I do have one suggestion you might consider for the next build (apart from the spelling error - 'Exceute' ;) Sorry to mention it again, but I'm sure we have all encountered fine software out there that has been spoiled by silly spelling errors).I'm sure it hasn't escaped your attention that this very useful utility has far wider applications than its use with FS. Would it be possible to modify the 'Path to FS' section in the configuration window to allow multiple paths to be entered and remembered? The user could then access his chosen application via a drop down arrow. The 'Path to FS' could be renamed to something like 'Path to Application'. Maybe this is asking too much as I can see each different path would have to be bound to unique settings made elsewhere in the configuration screen.Just a thought, but do feel free to ignore it...lol Cheers!Mike

Spelling error = fixed in next build.As to your other request, that is why you can setup different "profiles". You could setup your main profile, then create copies and change the fs exe to be whatever you want.

"You could setup your main profile, then create copies"...I know I'm probably being a bit thick but could you explain how this works in practice?I can't get my head around the fact that if I set up a different configuration for another application, wouldn't the settings be saved in the FSautostart.ini file in the Windows folder and overwrite any previous settings?I thought about making multiple copies of the FSAutostart executable, changing the path/configuration settings for each selected application....and then realised the above stumbling block would get in the way :(You do state in the provided readme: "Fsautostart.ini : This is the configuration file for FSAutoStart. It is located in the Windows folder. Other configuration files can be created and stored anywhere."Clearly, from what you are saying, I'm missing something obvious - perhaps I'm alone with this one as no one else has chipped in. As I said.. thick, thick, thick!Ahhh, now, wait a minute. I think the light may be beginning to dawn!"Other configuration files can be created and stored anywhere".... Does this mean that each application specific configuration file does not need to reside in the Windows folder and can be moved to the same folder as the application's executable? But this still means we would need to create multiple copies of FSAutostart....and that wouldn't work either as each copy needs to know where the specific configuration file is to reference the chosen application's executable.Oh I give up :( Can you put me out of my misery...lolCheers!Mike

I apologize - my documentation is not very clear.The default configuration file is the fsautostart.ini located in the Windows folder. This is the file that is opened when you start the GUI.When you run the GUI, the menu options under File are New and Open. If you select New, you can choose a blank configuration or a copy of the currently loaded configruation. You then will be give a file dialog window to choose where to save the new file and what file name to use.Once you create the new file, it will be loaded in the GUI. You can then make whatever changes you want.When you click Start - the currently loaded file will be used.To use the file again, start the GUI and select Open. Or you can use the Most Recently Used list under the Exit option, which will show up to the last 4 configuraiton files opened.Therefore, you can make as many configuration files as you want. They can launch different applications and have different service/programs if you choose.I hope that is clearer. :-)

"I hope that is clearer".......much, much clearer :) Thank you! Copied and pasted STAT!I just knew it, I knew it, I did miss something so obvious I'm now feeling, cough..cough, embarrassed :(I just can't believe I never thought to look at the File menu. What an idiot!Well, if nothing else, perhaps this will have helped a few others to exploit your fabulous utility to the full. I think your helpful and gracious support alone deserves a click on the 'D' button ;)Thanks again,Mike