7 replies
by erikdr
It might be that the combination of W2K batch (in its VDM) and the Novell utils is not very easy with environment memory. Did you try running a Novell login script instead of a batch? The script runs not in the VDM of the workstation but in the context of the NW client.
At your service,
- The Netherlands
by tsun
It?s a pure DOS problem. None of the reasons you mention can raise the "Out of..." error.
Perhaps the batch file contents instructions like "SET AppPath=c:\windows\winApp32"
These variables (like AppPath)are the ones that consumes the environment space of the current DOS session.
Step 1 Identifying the error
Do This:
a.- Start a DOS session
b.- Type SET at the command prompt.
What you see is the current environment DOS table. Many of this SET's became from windows, login scripts, exe files, etc.
By counting char by char of this table you can get a near value of your environment table
c.- Run manualy each line of the .bat file
d.- Take a look at the contents of the SET command, to see if it has change and how.
This will help you to identify the command that is causing the error.
The most common reason of this errors are very long "path" variables, many of them can be easily fixed renaming the directories included in the path with something more short.
If you find "strange unwanted things" in your environment table...
Add a: SET =
as the first line of your .bat file. This will remove unwanted variables, freeing some space from the environment table.
Be carefull...
SET User=Esteban
is not the same as
SET User = Esteban
Watch case and spaces.
edt@bancobgn.com
by tsun
I made a mistake!!!!
the correct issue is:
SET USER="ESTEBAN"
Allways between " " to limit the size ot the variable.
Carefull!!!!
SET USER="ESTEBAN "
when you type SET at the DOS prompt you don?t see where the string ends!!!
by tsun
by tsun
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending