Have you set explorer.exe to be stopped? That will remove your desktop, which IMHO is a good thing. Just use CTRL+ALT+DEL to bring up task manager and then you can do File->Run. Or use FSAutoStart to auto start the programs you want. Or both.

Thanks Ken - will do.RegardsSimon

Ken,As you may remember from my previous notes, I could not get any FSAS to start after build 1.5. Just getting frustrated that others were working all the builds OK, I decided today to just spend a number of hours to find out why it would not work for me.What I found out is really interesting. I had to uninstall all previous versions of FS AutoStart. Then I had to go to EVERY location that FSAS had placed files: Windows, Document and Settings, C:/program files/FS auto start. It took about an hour to find everything.Then I installed Build 11, and it then worked. However one had to make sure that no calls were made to the old .ini file. If I could make a suggestion is that you write a bat file to make sure that FSAS has cleaned all previous version out of the system. This was the most difficut installation I have gone through, however all is well and working just fine now.CheersBob

"If I could make a suggestion is that you write a bat file to make sure that FSAS has cleaned all previous version out of the system."...please Ken, NOT the user .ini files and profiles folder! Or, if you do, please display a BOLD reminder to back these up before doing an uninstall. In fact, the program, as it stands, is perfectly fine. Bob, once you have achieved a good install you just have to remember to uninstall the existing version before updating with the new. The above files and folder are preserved intact.Mike

"...please Ken, NOT the user .ini files and profiles folder!"Agreed. I don't want to risk losing my .ini files everytime Ken releases a new version or I might reinstall the app for whatever reason. Sorry Bob, the .ini files are the heart and soul of each user's FSAutostart set-up. I'd kill for mine!!Greg

Thanks for the info, I'll keep that in mind.

>Ken,>>As you may remember from my previous notes, I could not get>any FSAS to start after build 1.5. Just getting frustrated>that others were working all the builds OK, I decided today to>just spend a number of hours to find out why it would not work>for me.>>What I found out is really interesting. I had to uninstall>all previous versions of FS AutoStart. Then I had to go to>EVERY location that FSAS had placed files: Windows, Document>and Settings, C:/program files/FS auto start. It took about>an hour to find everything.>>Then I installed Build 11, and it then worked. However one>had to make sure that no calls were made to the old .ini file.> If I could make a suggestion is that you write a bat file to>make sure that FSAS has cleaned all previous version out of>the system. This was the most difficut installation I have>gone through, however all is well and working just fine now.>>Cheers>>BobI bet that this is the problem that I am having.

Ken:I am still using Ver.1, Build 6a. It works great.Is your latest version any faster/more efficient? Should I upgrade?Thanks for producing a fantastic utility for FS!JS

The latest version should be faster at shutdown/restart of services and programs. Also, the interface is more user-friendly IMHO :-).

Hi Mike and Greg, I know what you mean about "killing for the current .ini file" :-), about 45 minutes last night creating a new one yuck :-(.I think what I meant to say was preserve the .ini file but make the upgrade semmless. Having said that, the install process from one version of FS AutoStart to another IMHO is combuersome. I had files all over the place and yes I lost my good .ini file in the process. For example FS Realtime, does an auto remove and then an install, but does not wipe out the .ini file, this would be my suggestion to Ken for FSAS.Bob

OK, Ken, thanks for the reply.JS

FWIW,After build 6, I moved the location of the ini files to the more logical documents and settings folder. That is why you had files all over the place...If you uninstall, the profile ini files are not removed.

Listen to Ken. Updating after build 6 should now be painless for everyone. All you have to do is first uninstall your existing version via Add or Remove Programs and then install his latest version. You don't even have to reboot. Simple as that and all your hard work setting it up the way you like will be preserved - guaranteed :)Mike

Ken:Well, the latest version rocks. I installed it (while turning blue!) but it took first time perfectly and it is faster both closing stuff down as well as restoring it after finishing FS9.Super work. Thanks!JS

For those like me who always worry when updating any of this kind of stuff, don't even uninstal (yet): just cut out the entire folder of FSautostart with your existing earlier version from your Windows Program Files and place it on your Windows desktop so you've got everything preserved in case you screw up the instal of the latest version. JS