Some sugestions if possible: - a list of the different profiles in main GUI allowing with a double click to choose one;- Moving the private profile files from the windows directory to the FSAutostart directory;ThanksJos

Many thanks, Ken. Having Windows ME I was keen to see this build and I'm very pleased with it - much more convenient than thrashing around with msconfig and/or EndItAll. Some observations.I noticed it had some difficulty with ZoneAlarm - I ended up with multiple ZA icons in the systray but it didn't seem to do any harm. The one problem which is troubling me is that it failed to terminate NAVAPW32.EXE: went into a loop terminating it again and again (I left it for about 5 minutes). This is the Norton AntiVirus autoprotect process. I usually run FS with autoprotect off as I'm never online at the same time as I 'fly'. I find autoprotect dramatically slows the loading of texture files etc - very noticable with the excellent Visual Flight UK VFR scenery which has a vast number of files for Norton to inspect. I tried diabling autoprotect from the systray icon before running FSAutostart but it still looped on closing NAVAPW32.EXE. Any idea what might be amiss with this?I also had a couple of instances of Windows shutdown hangs after using the application but couldn't work out the pattern to reproduce the problem. Perhaps I was overzealous in closing applications! I'll investigate that another time.Thanks once again: it's an excellent utility in both concept and implementation.John4m NW of EGHI (Southampton UK)FS2002 Standard on Intel PIII 733 MHz, 256MB with 32M GeForce2MX graphics and Windows ME

I think the ZA icons come from the ZLCLIENT.EXE. The "meat" of ZoneAlarm is in VSMON.EXE, which you should leave running.As to NAVAPW32.EXE, I don't have a copy, so I can't test it in my Windows 98 SE OS.FSAutoStart tries 2 methods of terminating a program. First, it sends the program a WM_CLOSE Windows message. If the program responds and shutsdown, then its all good.If it doesn't, the program waits for the selected amount of time, then uses an API function called TerminateProcess. On Windows 2000 and XP, this will certainly kill a program if I have security access to it (i.e. it is not a service).Now on Windows 98/ME, I cannot guarentee any reliability since Windows 98/ME is basically a DOS wrapper, IMHO ;-)

Thanks Ken. I'll try leaving VSMON.EXE running - I hadn't understood the relationship between the 2 processes.Will be interesting to see if anyone else with ME has problems (or not)with Norton autoprotect shutdown.I'm not surprised that there are limitations on ME - my personal view is that it is a weak member of the Windows family (I'm *not* trying to start a digression on this thread) but it was the standard bundle on PCs when I bought mine...Cheers, John.4m NW of EGHI (Southampton UK)FS2002 Standard on Intel PIII 733 MHz, 256MB with 32M GeForce2MX graphics and Windows ME