GET.EXE Ver 2.6, Bob Stephan's DOS BATch file
enhancer for Environment and ErrorLevel BATch
services. GET26UPD is an upgrade for users of
Ver. 2.5 and requires the documentation from
Ver. 2.5. Many new features are described in
the file GET26NEW.DOC incl. string handling,
arithmetic, file dates, return codes from
other programs and much more.
Shareware: No nags, no crippling, no delays.
Registration: $15+S&H see ORDER.GET.

GET.EXE Ver 2.6, Bob Stephan's DOS BATch file
enhancer for Environment and ErrorLevel BATch
services. GET26UPD is an upgrade for users of
Ver. 2.5 and requires the documentation from
Ver. 2.5. Many new features are described in
the file GET26NEW.DOC incl. string handling,
arithmetic, file dates, return codes from
other programs and much more.
Shareware: No nags, no crippling, no delays.
Registration: $15+S&H see ORDER.GET.The main documentation for GET is currently included with Version 2.5
Version 2.6 supplementary documentation is in GET26NEW.DOC.

Because of its large size, GET.DOC, the file containing the 70 page
manual for GET Version 2.5 may be compressed in the archive file
GETDOC.COM. Uncompress GETDOC.COM by executing it on a hard drive or on
another diskette with more room.

If you want to print the documentation yourself, note that it is
formatted for printing on a laser printer using Vern Buerg's LJBOOK
laser jet printing utility. This will print 4 pages on one sheet of
paper front and back. If you do not have a laser printer or do not
use LJBOOK, it is suggested that you set your printer for 8 lines per
inch and reduce the font point size if possible.

EXTRA INFORMATION FOR USERS OF SHELLS:

If you get "Out of environment space" when you try to use GET read the
following.

One recurring reason for this problem is running the BATch file from a
so-called "shell" - PC Shell, Norton Commander, Xtree, etc. etc. etc..
When you run a BATch file from a shell, it invokes a second copy of
COMMAND.COM (a true shell), but DOS is stingy with the environment
space it passes to a "child" program such as this second copy of
COMMAND.COM. There are a couple of solutions - if this is, in fact,
the problem.

1. If you can get your shell to run your BATch file with the command
C:\COMMAND.COM /E:512 /Cyourbat
then you can specify how much environment space you want with the
/E:nnn parameter. Of course put in the real name and location of your
command processor where I have put C:\COMMAND.COM.

2. In your autoexec set a large dummy variable in your Environment
with the SET command, such as SET DUMMY=a large variable here but make
it longer. Then when you run a BATch file from a shell, make the
first statement in the BATch file SET DUMMY= and it will clear up the
space for use by GET.

3. Use 4DOS or NDOS for your command processor instead of COMMAND.COM.
4DOS and its alter-ego NDOS allow you to specify how much free
environment space you want for child processes. Only 4DOS does it the
way it should be done. MS never has handled the Environment space
problem very well.

I try to address the "Out of environment space" problem in several
sections of the manual on disk, but it is difficult to cover all
cases. I also include an entire Appendix on the subject in the
printed manual, but due to space considerations don't include it on
the shareware distributed version.