"in the next build FSAutoStart will remember programs that were running even if they aren't currently. A new column has been added to indicate if the program is currently running."....now, that will be useful. Your proggie is becoming more flexible by the day, or is it minute ;)Mike

Hi,Turns out 'The Concise Oxford Dictionary' was to blame. I usually have it running in the background whenever I'm compiling letters or posting (which is why you don't see too many spelling mistakes in my posts ;)). It is an older 16bit application which still serves me faithfully nonetheless.Anyway, I now know it will be quite safe to 'Stop' ntvdm.exe in FSAutostart unless, of course, any 16bit addons (see previous post) require it, in which case it will probably restart as required.Sorry about this diversion but it has clarified one or two things for me at least :)Mike

Hi Mike,Just to back you up, I have made sure not to shut down anything relating to clipbook, on the assumption that FSScreen would probably need it. So I agree that most likely isn't the problem. I'll try your settings too.Thanks,Todd

Solved for me! Wasn't really broken it turns out. I did a quick test, took a screen shot after starting FS using FSAutoStart. FSScreen numbers shots sequentially - I noticed this test shot was fsscr080.bmp....80! Quick search for fsscr*.bmp yielded the answer for me - FSScreen is now saving screen shots to the FSAutoStart directory! Any way to change the startup directory for a program in the start list, Ken? Found your shots, Todd?Thanks!sg

That is fixed in the next build.

Hi sg,Why not do as I do and start FSScreen either before you run FSAutostart (in which case the setting will be set by default to 'No Action') or after the sim has started? Works for me and files are saved to the FSScreen folder. I'm still using version 1.1 - I didn't realize there is a newer version - I'll check it out now :)Mike

Hi Mike,. I tried with Clipbook set to Auto, Manual, and Disabled. FSScreen works fine for me here when Clipbook is set to Auto and Manual, but not when set to Disabled. All I can figure is that I have my some other service set in such a way that Clipbook is unuseable when set to Disabled that in some way effects FSScreen.I don't know enough about all this to hazard a guess. I'll do more research. I'm running XP w/SP1, but have added a number of MS updates. Also, I'm not using FSAutoStart. I've taken a look at it and it is indeed a great add-on, but I don't run enough external apps to warrant it's use here. My FS9 install is pretty clean... some added terrain mesh and landclass (FS Genesis), RealAir's airplanes, the Maule and a couple other nice GA freeware birds. On a tip from you a few days ago I realized that I still had ATI Hotkey service set to Auto... I don't use it and now have 17 services running when TaskManager is started. System runs very well and stable. These boxes of bits certainly do come in a huge variety of flavors :-).

Yep - that's what I've started doing until Ken's update!Best,sg

Hi Greg,Need a good shampoo?...lolAre you by any chance using Matthias's latest version of FSScreen called YAFSScreen (YA=Yet Another!). If so, that may be why we are seeing differences in behaviour (see link below). My older version 1.1 seems quite well behaved, although does not offer all the bells and whistles provided by YAFSScreen.http://www.marian-aldenhoevel.de/YAFSScreen/Mike

Mike... I tried YAFScreen, but went back to FSScreen 1.1. I like it's simplicity. It just works.

Couldn't agree more :)Mike

Got'em SG. Thanks. Saved some gems I thought were gone forever. It's really no problem looking there instead of FSScreen, once you know where they are. And thanks Ken for your great program :-)Todd