The "ENTER" is incorrect syntax for PAUSE. Also, you need the COMSPEC in
the ZIP RETURN (ZIP RETURN &vComSpec /C EXIT). The PAUSE message disappears
when you do the ZIP RETURN. I do ZIP RETURN &vComSpec /C TYPE file.mes
(message file) so that a message stays on the screen throughout the whole
resetting process. Also, I check for the value of (ISTAT('TOTALALLOC')) to
see if it is too high or the value of (ISTAT('MEMORY')) to see if it is too
low instead of just doing it "whenever" and just for 'WinNT'. This should
work for any COMSPEC and will only do it when it needs to (as long as you
can determine the values to reset at). I usually run this test at a place
that all users tend to pass thru periodically (like maybe a menu file).
-----Original Message-----
From: Albert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 2:53 PM
To: [EMAIL PROTECTED]
Subject: RE: Reports and Views
Under Win2000, >>> or for that matter, WinME <<< memory does not properly
free up. An annoyance to the users, but they will grudgingly accept it when
they realize their computer doesn't blow out to death and cold restart if
they put up with it is to periodically dump out. Note that this file WILL
NOT WORK FOR ME because the comspec looks just like 98. If you have ME
machines either upgrade to 98SE <g> or don't bother checking for the
operating system directory.
-- Restart.cmd
SET VAR vComSpec = (ENVVAL('ComSpec'))
IF vComSpec CONTAINS 'WinNt' THEN
PAUSE 3 USING 'Freeing up your memory to avoid the crash!!' +
AT 1 ENTER WHITE ON GREEN
ZIP RETURN EXIT
ENDIF
RETURN
The 'EXIT' on the end of the line cuts a second or so out of the return
time. On our networks and our clients' networks this takes 2-3 seconds,
thus the message bar
