I am running Win XP Pro. I am logged on as the administrator. Build 5 worked fine for me.Pat

With Build 6 I moved all the configuration files and profiles to the following directory (on XP):Documents and SettingsApplication DataFSAutoStartProfiles are stored in a profiles folder in this directory.Do you see files in this folder?

I am not sure. I am at work & will check it out when I get home. Thanks.Pat

Ken,This program deserves a long thread !It's great !Thanks a lot.Hessel Posten

I'm having similar problems. On my system (XP, logged in as administrator) the program will save the configurations, but when I restart the program, it wants to reinstall. Then if I reconfigure the services and programs, when I try to start FS9, I get an error message saying that it can't start the program. Then FSAutoStart restores the services and programs and FS9 starts but without the benefit of FSAutoStart.I have been using Build 5 with no problem and I used the same settings with Build 6. In fact, Build 6 won't work even if no services or programs are selected to be stopped. I have removed Build 6 and am successfully using Build 5 again.Ray

Hi. I'm not sure about the reinstall - that is the windows installer.As to the error - what is the error code? Can you get a screenshot?

HiThanks for the new version. What happens with XP admin login is that everytime you start the program there is an initial dialog saying: "FSAutostart now stores all configuration..."Then "if you created profiles..."After the two messages the program runs and everything seems normal.Whe you run the profile you get the shell waiting for the 30S, the shell closes but no program was launched (tested with AS2004). Tried to put a shortcut in the desktop but the shell opens and closes very fast.WindowsXP Home in English;Changed desktop and My documents default dirs, the user and local app settings are in the default place;Jos

Yeah, known bug - the shortcut it makes is missing quotes (") around the ini file.Right click on the shortcut, then go to properties.In the target field, look for the path that contains the ini file and surround this with quotes.Here is what mine looks like (after I fixed it manually):"C:Program FilesFSAutoStart v1.0 Build 6fsasctl.exe" "C:Documents and SettingskenApplication DataFSAutoStartprofilesfsautostart.ini"I have already fixed this and will be releasing a new build shortly.

Hey Ken, thanks for this great utility! I started using it quite "late", but I found that it's really great thing for starting FS and bunch of online programs.But I was wondering, if something could be easily implemented? Each time I close the FS, there are two applications which stay open... dplaysvr.exe and WISPTIS.exe. My question is, is there a possibility for you to include in the program a field in which one could specify to "close" certain programs on exit, like you did with field in which one can add programs on boot?? I think that would be a great addition :)Thanks and keep up the great work!

>Hi. I'm not sure about the reinstall - that is the windows>installer.>>As to the error - what is the error code? Can you get a>screenshot?When the application starts, after the 30 sec wait, the next message is "unable to open process. error code 87". The services and programs are then restarted and the application closes. Then FS9 starts, but without the benefit of FSAutoStart.Ray

Okay, try this: open the profile in notepad or another text editor. The default profile is located in documents and settingsapplication datafsautostartprofilesfsautostart.ini Look for a line MainAppExe=. It should be near the bottom. Is it there? If so, delete the line and save the file. Then try FSAutoStart. Let me know what you find.

Thanks for the kind words! Let me see if I understand you...these programs are not auto started by FSAutoStart, but you want FSAutoStart to kill them when it finishes? Do these programs start when your OS boots? Or are they started by MSFS?

All,There is a bug in this build which will cause FSAutoStart to launch MSFS, wait, then give a "error 87" and restart everything even though MSFS is running.Here is the workaround: open the profile in notepad or another text editor. The default profile is located in documents and settingsapplication datafsautostartprofilesfsautostart.ini Look for a line MainAppExe=. It should be near the bottom. Is it there? If so, delete the line and save the file. Then try FSAutoStart. I will be fixing this today and releasing a patch. Plus a few other minor things will be added.EDIT: I have fixed the above problem. If you are interested in the fix, please email me and I will send you the patch until I can release it publically.Sorry about this!

These programs are not started by OS, they are started by one of the applications which boot with MSFS. I already got rid of the WISPTIS (apparently it's some unneeded file for Tablet PCs...), but there's still an issue of dplaysvr.exe, which is started I believe with sbrelay. And sometimes I noticed some other .exe files stay open, like msiexec.exe and some others...What I'd like is an option to be able to tell FSAutoStart that on exit it should just "kill" that (those) app(s). As I mentioned in my previous post, as there's an option to start the app, it would be nice if there was also additional option to kill the app (any app). :)

Okay, I'll take a look at it...thanks for the suggestion!