I am at a loss to find a solution or even a reason why this is occurring: We need to run a 16 bit program under Windows 2000 and need a minimum of 589K of free conventional memory or "Largest Executible program size". 3 machines (all Win2K) are networked to a server running Windows 2000 Server. The Server is an IBM x series and has only 575K of Free conventional memory after loading Windows and a files statement of FILES=250 (which uses about 7 or 8k of conventional memory). A workstation also is short at 581 K But the 2 other workstations have plenty of free conventional memory at: 615K and 608 K! These 2 machines are loading the DOSX.exe (dos extender program) into upper memory. For some reason the other machines with the low memory are loading dosx.exe into conventional. That is where the problem lies since this program (dosx.exe) is about 52.5 in size and uses about 34K of RAM. I do not see why it loads high on some machines and low on others. All machines are pretty much the same in their config.nt and autoexec.nt files. I can re-arrange the sequence of loading in the autoexec.nt file so that dosx.exe loads first then I get the program to load into upper memory area and ...walla I have enough free conv memory. But, the redir.exe is supposed to be loaded before dosx.exe according to MS info on that line's description. So as soon as that program is loaded before dosx.exe I don't seem to be able to have a large enough block of upper left to load dosx.exe high, and it loads low. Any ideas???? I am stuck unless I can get this solved. Even ibm support has no answers. They initally suggested re-formatting the drive and re-installing OS without using ibm's install utility CD. ...I did that and no difference to speak of. Out of curiosity, can others look at their memory configuration on Win2K machines? type "command" at the RUN menu in Win2K then at the command prompt type "mem/c" TIA for any help you can give me. -- John

I have encountered exactly the same problem and so far have been unable to find a fix. I have however, managed to work out how to increase convential memory to run DOS programs. That is by specifying different autoexec.nt and config.nt files for a particular shortcut. You need to make a copy of the autoexec.nt file in %systemroot%\system32. Edit this file and remark out the lines that load redir and dosx. Save this file as say, autoexec.new. Now create a shortcut to your DOS program. Under the program tab of the shortcut properties click on advanced tab and specify the autoexec file as your new file, autoexec.new. Now when you run the DOS program DOSX is not loaded and you have an extra 34K of conventional memory to use. If your DOS program runs from a batch file then you need to create the shortcut in a different way otherwise you won't be able to specify the different autoexec file. First, create a shortcut to any DOS .exe file. Then edit the shortcut to point to your batch, remembering to change the working folder also. I would still prefer to know how to force DOSX into upper memory but in the meantime this should work. Phil.