FULLSCREEN CONTENTS Project Home Page
.APPENDIX....: /V When Using 4Dos, Ndos, And Umb
.ALIAS.......: vwhus4d
.DISCUSSION..:
I have received the following report from Aran Spence about circumstances in which Fdate /V will not set a variable in the master environment. This report leads me to believe that Fdate /V may also fail to work with MS-DOS if you put the command processor or the environment in Upper Memory. Note, however, that this behavior has not been tested with Fdate 8.4's new environment-handling routines.

--------------------------------------------------------------

Steve,

There are options with 4DOS and NDOS to load the environment and part of the command processor into upper memory blocks. When one of these options is used, Fdate /V can't find the environment and produces the message:

ERROR
@echo ERROR: Master environment not found
@pause

If you have a 4DOS.INI file, it has to contain these lines for Fdate /V to work:

UMBEnvironment = No
UMBLoad = No

If you have NDOS, the SHELL statement in CONFIG.SYS cannot contain any reference to UMB loading via /U (which puts NDOS.COM in UMB), nor can it contain a statement of the form:
/E:xxxU (which puts xxx bytes of the environment in UMB via the "U" parameter).

Also, NSTART.BTM or 4START.BTM cannot contain
SET NDSHELL=/e+xxxU /U in which both U's represent UMB loading of the command processor and the environment during secondary shells.