davidr@hplsla.HP.COM (David M. Reed) (08/18/90)
This is just an update, in case someone remembers my problem and was curious. One our our 386 systems (with DOS 4.0) will not load COMMAND.COM within MSWindows3 as long as the new HIMEM.SYS is used. No matter how we try to start it (from the "DOS Prompt" icon, from the File Manager, with or without a PIF file, irregardless of directory we place it in) when it starts up it (without PIF file) clears the screen, then almost immediately MSWindows is repainted, and MSWindows pops up a box saying "Insufficient memory". Without HIMEM.SYS, or using an old version, then we can start COMMAND.COM, but MSWindows does not get any of its "Enhanced" benefits. The only program we have such a problem with is COMMAND.COM. (There is, from running other DOS programs, apparently over 430K available to non- windows applications). We discovered a work-around the other day. Making a copy of COMMAND.COM with another name (e.g. COPY COMMAND.COM BOGUS.COM). We can then start BOGUS.COM without any problem, and it runs just as well as COMMAND.COM does on all our other 386 systems! Can anyone explain this? (And yes, Doug McDonald, I am also convinced that the new HIMEM.SYS is not really correct in its operation, for this and several other reasons I have come across.)