All,I just uploaded FSAutoStart v1.0 Build 6a to the library. http://library.avsim.net/esearch.php?CatID...util&DLID=48260It addresses the following:* Fixed bug where shortcut was not created properly if long filenames were used* Fixed bug where Configuration Setting

Again many thanks Ken !Hessel

>"Again many thanks Ken !".....yes indeed! And now perhaps we will soon be able to leave you with time to rediscover the joys of MSFS ;)Mike

There will be some delay getting this posted. If anyone is having problems, please email me and I will send you the new version.

Ken,I'm really happy with your last release (Build 5)(really happy!). If its been working flawlessly for me, is there any pressing reason to "upgrade"? Any performance-boosting benefits?Thanks,Joel

This build mainly focuses on managing multiple profiles. There are no perfomance boosting additions.

Ken:Please email to me: [email protected] thanks for this essential add-on.

You've got mail.

Many thanks Ken

Okay, I have re-released it, you can find it here:http://library.avsim.net/esearch.php?CatID...util&DLID=48260Those of you who have sent emails will not need to download this.

Hi Ken,I have been a user of FSAutoStart from your first build version. Build 5 just works like a champ on my system, can't be more pleased.However build 6 has been quite a pain. First I lost all my configuration settings. I get the message at the start of build 6 that it moved everything to Document and Settings folders, but when it starts nothing was retained from my old settings. It was if I had to reset everything. Next when I hit start, FSA just flew off into the desktop and nothing started.Did a restart of FSA and again the same message appreared about moving config files etc. Even tried an un-install and install. Nothing worked.Went back to my download save files got Build 5 back and everything is back working like a champ. I don't know what went wrong, but build 6 almost drove me crazy.Do you have any ideas on what could have gone wrong?CheersBob JohnsonDenver

Yeah - first off the first two releases of build 6 and 6a were a bit buggy, and for that I apologize.Second, FSAutoStart looks to see if you have any fsautostart ini files in your windows directory and tries to move them. If it fails for some reason this can get you stuck in the loop.My advice is:First, backup your fsautostart ini files in your windows directory, then remove them.Second, install the 6a build from avsim that I posted today.Third, run FSAutoStart. It should create a default fsautostart.ini file. Quit FSAutoStart.Fourth, copy your backup of fsautostart.ini to the folder c:documents and settingsapplication datafsautostartprofiles. You will overwrite the one that is there.Finally, restart FSAutoStart. Your old profile should now be in place.

Thanks Ken. Had the same problem. Followed your instructions above and everything looks OK for Build 6a.Regards,Tom Stewart

Ken,To be honest, build 5 is so rock solid, I will leave it up to others to go through your procedures for build 6a. I really think that to further your excellent work, that these changes need to be automated. I tried, really tried, and I was not happy.I am a trusted user, but I am going to just sit on build 5 and wait for the bugs to be "killed" YOu have done an excellent job Ken, and I love FSA, but I am going to stick with what works on MY system. Not going to cuss anymore today (ha ha ha)CheersBob

I understand your viewpoint. It was "supposed" to be automated, and it was on my test system. For some reasons it doesn't quite work on some other systems.Like I said earlier, there is nothing in Build 6a that promotes further performance. It only attempts to address the ability to have multiple profiles.So, if Build 5 is working for you and you don't need the profile management, then by all means stay with what works.In the meantime I will be working to figure out better ways automate the program.