>>WinNT/2K uses the CONFIG.NT file and FILES=; the alternative is to right click on the app, select Properties, and create a custom profile for the VDM
>
>(What is VDM ???) , which can include both a custom AUTOEXEC and CONFIG file.
>

VDM is a Virtual DOS Machine; it's the process environment for the application being run. Win16 apps can either all run in a shared WOW-VDM (Win16 emulator environment) like they would under Win 3.x or Win9x, or can each run in their own process space. Runing in their own process space tends to make the overall Win16 environment more stable, since if one Win16 app crashes, it will not affect any other Win16 apps running, but it will use more memory, since each WOW-VDM has it's own DOS/Win16 operating system copy running, rather than just sharing one for all Win16 apps.

>Pardon my ignorance, but where do I access the CONFIG.NT, on my Win NT Server I can type SYSEDIT at the run command, but on Win 2K Pro my client says it says file not found.
>>

CONFIG.NT, if needed, is located in the root directory of the system partition, the drive where the Win2K loader and basic OS files reside. It is not always created, and some default base values are assumed if it is not specified, which are outlined in the Win2K on-line help.

You can also right-click on a DOS or Win16 app and bring up it's Property sheet; the property sheet will allow you to construct a set of custom initialization files that will be used whenever that executable is started, and can indicate if it runs separately, maximum open files, and memory configuration details, as well as DOS environment variables. I'm not sure that SYSEDIT is a part of Win2K; you can create the CONFIG.NT using Notepad, and you can configure the Environment variables directly through the System COntrol Panel Applet. I'm inclined to set custom properties for the few Win16 and DOS apps I still run under Win2K at this point, this way I can tailor the memory and work environment for the application rahter than juggle the base configuration used by legacy apps to comprimise on a setting that, while acceptable generally, may not reflect the preferred operating environment foreach app. Since I now use a handful of DOS and Win16 apps, the work involved in customizing their runtime environment is very minimal; in fact, aside from FPDOS 2.6, Vern Buerg's LIST and an old Form Editor that I use to create PCL laser macros, I can't think of any DOS or Win16 apps I run now (a couple of games, but I have a boot disk for them, since they need 'real' DOS, and get run on my ME box anyway.) I do have clients that still run DOS apps under Win2K (FPDOS apps which they never converted, using Y2KFox for Y2K compatibility, some QuickBASIC utilities, and a few Clipper apps thatend-users assured me were 'about to be scrapped' two years ago, but like my '87 Continental, with 235,000 miles on it, refuse to die. Again, creating custom PIFs for the Clipper apps, with their own DOS environment variables and memory configurations, is what probably lets them work well under Win2K.)

There's a lot of information in the on-line help file, and on the Win2K and NT FAQ site in my sig block.