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
Working:
s:\css\antivir
Batch file:
Run:
Normal
[x] Close on exit
Next, select the MEMORY tab and enter the following values:
Total:
640
Initial Environment:
Auto
The above example assumes that CHECK.BAT is on the S: drive:
be sure to substitute the correct drive letter for your system.
Environment:
Windows NT
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.
Environment:
Windows 95 / Novell NetWare / Client32
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.
Environment:
Windows 95 / Novell NetWare / Client32 & VLM
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