• How do you...
  • correct an "out of environment space error" [Windows - CHECK.BAT run manually] ?
  • correct an "out of environment space error" [Windows - CHECK.BAT icon] ?
  • correct an "out of environment space error" [Windows 95 - CHECK.BAT icon] ?
  • correct an "out of environment space error" [Windows NT login script] ?
  • correct the error "MPR.EXE (not responding)" ?
  • adjust your NetWare login script to handle both VLM and Client32 workstations ?

If you have a question that is not answered on this page, contact Technical Support

I've installed SE_UTIL properly but when I test the installation and manually run CHECK.BAT, I keep getting an "Out of environment space" error message; why is that ?

COMMAND.COM requires environment space to store variables. If enough space is not specified, this error message will appear. Increasing the environment space will be required. If this is Windows for Workgroups (WFWG) 3.1x, use PIF Editor and edit the DOSPRMPT.PIF file to include enough space for the environment. Add /E:1024 on the "Optional Parameters" line. For Windows 95, edit the properties for the MS-DOS Prompt icon and add /E:1024 to the end of the CMD LINE entry.

I've created an icon to run CHECK.BAT and when I click on it, I get an "out of environment space" error message. What should I modify?

In the program group of your choice, place the icon that will reference CHECK.BAT. Then, select FILE and choose NEW ITEM. Fill in the following values:

Item name: CHECK
Command line:

c:\command.com /e:1024 /c s:\css\antivir\check.bat

I've created an icon on the Windows 95 desktop to run CHECK.BAT. When I double-click it, I get an "Out of environment space" error message. What should I modify?

On a blank area of the desktop, click the right mouse button and select NEW, then choose SHORTCUT. Use the BROWSE button to locate CHECK.BAT. After finding CHECK.BAT, click OPEN and then choose NEXT. Type a name for the shortcut, CHECK, and click FINISH. Next, right-click on the icon you just created and choose PROPERTIES. Select the PROGRAM tab and fill in the following values:

Item name:
CHECK

Cmd line:

s:\css\antivir\check.bat

I have installed SE_UTIL correctly and want to implement it in a Windows NT login script. The login script is basically a DOS batch file so I know when you want to execute a batch file from a batch file you should use a CALL statement. When I use the following command CALL S:\CSS\ANTIVIR\CHECK.BAT the login script indicates an "Out of environment space" error message. What should I modify?

Instead of using CHECK.BAT in the login script, use a batch file called CHECK2.BAT. An example :

NET USE S: \\NTMAIN\NT40 CALL S:\CSS\ANTIVIR\CHECK2.BAT

This batch file creates a command environment with enough space to process the environment variable usage of SE_UTIL.

I've put the syntax to run SE_UTIL within the login script but now it is hanging. One error message I am seeing is "MPR not responding". What might be causing this ?

MPR is an acronym for Multi-Protocol Router and is installed with Windows 95. When connecting to a Novell NetWare 4.1x server with Client32 running, it was discovered that there was a syntax problem that could cause this error if SE_UTIL was being used in the login script. The original syntax was:

#command /e:1024 /c s:\css\antivir\check.bat 

To correct the problem and eliminate the error, change the above syntax by substituting @ for the # symbol as follows

@command /e:1024 /c s:\css\antivir\check.bat 

* Do not indent the line in the login script. Client32 does not "like" indentions.

Using SE_UTIL from a Novell logon script and Client32 with Win95 workstations and getting MPR not responding when SETUP.EXE executes. Other workstations not using Client32 did not have the problem. If an @ symbol was in the login script, no longer would there be an MPR (not responding) error, however the workstations that worked properly now received an error that it didn't recognize a command in the login script.

SOLUTION:
The network login script requires use of the @ symbol when running CHECK.BAT and using Client32. Since not all users were using Client32 though a modification to the login script was required to check for both types of client connections:

*THE FOLLOWING IS
AN EXAMPLE OF
*CLIENT32 & VLM IMPLEMENTATION
*OF SE_UTIL IN A LOGIN SCRIPT
*
* OS_VERSION="V7.00" ARE NOT CLIENT32
* OS_VERSION="V4.00" ARE USING CLIENT32 

size="2" face="Courier New">IF
OS_VERSION="V7.00" THEN BEGIN
* Do not indent this line!
#C:\COMMAND /E:1024 /C S:\CSS\ANTIVIR\CHECK.BAT
END 
IF
OS_VERSION="V7.00" THEN BEGIN
GOTO DONEFP
ELSE
IF OS_VERSION="V4.00" THEN BEGIN
@C:\COMMAND /E:1024 /c S:\CSS\ANTIVIR\CHECK.BAT
END 
DONEFP:
*SUBROUTINE JUMP

If you have a question that is not answered on this page, contact Technical Support