• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 321
  • Last Modified:

r6009 "not enough memory in environment"

On our new Computers we are getting this message when executing Novell login scripts.   What do I have to change to fix it and why is it only happening to new computers?

Background : we have many computers on win 95 not having this problem.   tcpip and ipxspx - microsoft client for novell - ethernetII -
0
markje
Asked:
markje
  • 2
  • 2
  • 2
  • +2
1 Solution
 
G0LIATHCommented:
Maybe a stupid question and I apologize for any insult but in the properties for "Client for Novell Networks" is "Enable logon script proccessing" checked?
0
 
markjeAuthor Commented:
"Enable logon script proccessing" is checked.
0
 
e5haizCommented:
Please show the contents of the script- the scripts is calling on an executable that obviously can't run. In addition I would suggest using the most recent Client32 client from Netware.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
The default environment memory is 160 bytes (as found in the Microsoft document here - http://support.microsoft.com/support/kb/articles/q68/9/27.asp).  The environment memory is used to store things such as the path and location of the temp directory.  At a dos prompt, type "SET" and you'll see a list of things using the environment memory.  Once you are out of environment memory, any further SET or PATH statements are unsuccessful and return a message "Out of Environment Memory".  Try adding this line to config.sys - it tells the computer on boot up to make the environment 512 bytes instead - more than 3 times the size.  (My guess - and I'm not a novell person) is that your path and other environmental variables are using too much of the memory and Novell is trying to store variables in the memory).

Anyway, here's the line to add to config.sys

SHELL=C:\DOS\COMMAND.COM C:\DOS /p /e:512
0
 
mark2150Commented:
Leew's answer is correct for this symptom. Login scripts frequently toss user name, MAC address, Server ID, etc into system environment. 512 may also be marginal. 1024 or 2048 won't kill you and will give some headroom. As a test, boot, get error, shell to DOS and do:

SET > X
DIR X

Note size of X file in bytes. This is equal to environment in use. Then use LeeW's suggestion with, say, /e:2048 as the environment and repeat the above test. This will show you what the environment actually is. If you're *close* to 512, move it up to 1024, or next 512 increment past size of X file.

M

0
 
markjeAuthor Commented:
I would still like to know why this happens on one machine (newer version of 95) and not another (older version of 95)?
Must be the O.S version.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
comment out the change on the fixed computer and reboot it and another you believe to be otherwise identical in programs and startup (different versions of 95 won;t make a difference).  Then, from a command prompt on both machines, type set > environ.txt.  Now you can compare both files and see which machine is using more environment space and for what.  (and by commenting out the fix, it will show you where it stopped adding to the environment).
0
 
mark2150Commented:
Older machines already had SHELL statement in CONFIG.SYS, Newer ones didn't. OS ver has nothing to do with it.

M

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now