Not enough DOS environment space (AREV Specific)
At 03 DEC 2001 04:08:52PM Ted Archibald wrote:
One of my clients has recently converted from Novell 3.2 to Novell 4.12 and the DOS workstations(6 or 7) are having problems with environment space. I have not seen this problem on the W98SE workstations.
The message is:
"run-time error R6009 - not enough space for environment"
I can give the original DOS partition any size of environment that I want: 256 to 4096 etc. but when AREV does a shell out to Dos using a PC or SUSPEND then that DOS is stuck with 256 and apparently there are some functions that this is now (in Novell 4) too small and the error message ensues.
I have looked at the dos command comspec but it does not have /e: for environment setting of the invoked DOS via command.com. I have looked everywhere but no luck. Maybe the setting is in AREV?
Anybody with ideas on what is going on here?
Thanks
Ted Archibald in Tsawwassen BC
At 03 DEC 2001 04:48PM Bob Carten wrote:
Ted:
The novell client has a bigger footprint, so there is less room for other DOS apps.
can you run MEMMAKER, see if that helps?
Bob
At 03 DEC 2001 05:09PM Ted Archibald wrote:
Hi Bob
I use QEMM 8 (remember that one?) and get lots of DOS space, over 609 KB. Memmaker is a piker when it comes to using memory. Poor old QEMM.
It is not the memory in the DOS partition that is the problem, it is the 256 bytes of the default environment as setup in the dos shell that is initiated by PC or SUSPEND. I thought that it would copy the size from the existing or last DOS.
I am using
command.com /e:2048 /c k:\arev\arev.exe %1 /sxm4096in a bat file to start arev
Arev gets an environment of 2048 but the dos from a PC or SUSPEND gets only 256 and commands issued there sometime give the error message mentioned above. I know that it is only 256 because I do the prior command without the arev.exe and use \QEMM\MFT to look at the size of the environment. I can also see the size from MEM /p/d
Cheers
Ted
At 03 DEC 2001 06:23PM Richard Hunt wrote:
Maybe thiw would help…
SUSPEND COMMAND.COM /E:2048 /C PROGRAM.EXE
Add a new command processor with the specs you need.
At 04 DEC 2001 02:54PM Jonathan Bird wrote:
Are you calling NPRINT? NPRINT in Netware 4 is MUCH bigger on memory than in version 3. If you are calling NPRINT with an arev pcperform, it will not work in Netware 4. Two fixes:
Get the Netware 3 NPRINT.EXE and copy it to your Netware4 server.
Change your Arev pcperform to perform "suspend…."
JB
At 04 DEC 2001 08:22PM Warren wrote:
Check the system login script etc. to see what is happening to your comspec.
Try typing set when you shell out to DOS from ARev to see what your comspec is set to.
At 05 DEC 2001 05:52AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Check the Novell login script settings (using SYSADMIN) - check that you are exiting the script cleanly, and that you are pointing to identical copies of the command shell (ie. your local copy and the network copy as the COMSPEC= does. The default Netware setting points to the network copy - use c:\command.com for these Novell users - ask your network administrator to work through it with you.
The R6009 is a standard Microsoft C compiler message for DOS executables.
World leaders in all things RevSoft
At 05 DEC 2001 11:28AM Dean Todd, Computer Resource Team - Orlando wrote:
The default DOS environment is 256, which sometimes is not adequate because lots of stuff is stored there. From a dos prompt, type set, to view what's being maintained. It will be similar to the following:
winbootdir=C:\WINDOWS
COMSPEC=C:\WINDOWS\COMMAND.COM
BLASTER=A220 I7 D1 H5 P330 T6
CTSYN=C:\WINDOWS
EXPAND=YES
DIRCMD=/O:N
TEMP=C:\temp
TMP=c:\temp
PROMPT=$P$Q$G
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\ILIB;C:\MENU;C:\IBMTOOLS
windir=C:\WINDOWS
—
Here's a sample config.sys file with the environment set at 512:
device=C:\WINDOWS\himem.sys /testmem:off
COMMON
SHELL=C:\COMMAND.COM C:\ /E:512 /p
fileshigh=100
dos=high,umb
Notice the SHELL= command which sets the environment at 512,
i.e, via, /E:512
Hope this helps. My last experience with Novel was in the 3.xx days.
At 05 DEC 2001 04:08PM Ted Archibald wrote:
Thanks all for the input.
The solution that was simple and direct was from Richard Hunt
with some minor changes.
In the R/BASIC pgm I needed to end a Novell capture
In Novell 3 I used pcperform ENDCAP
In Novell 4 the following seems to work
SUSPEND 'COMMAND.COM /E:1024 /C CAPTURE.EXE EC ALL ] NUL 'notice the quotes
Cheers
Ted Tsawwassen BC
At 06 DEC 2001 04:31AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
There is an $endcap program for AREV which may work in your setting. It was written to solve the memory issues for Novell 3 & 4.
http://www.state-of-the-art.com.au/util12.zip
World leaders in all things RevSoft
At 06 DEC 2001 01:42PM Victor Engel wrote:
A PDISK PRN from Arev should satisfy the needs of most places needing an ENDCAP. The Capture, command, however, is also overly large, and I see that zip file also has a replacement capture.