At 02:23 AM 11/5/96 -0300, you wrote:
Thanks for your help. I have now realized that the problem stems from lack
of hardisk space - i.e. I recompacted my HD using Norton Utilities and
maanged to add inalmost twice the messages before the out of memory message.
If I am to follow the neccesary implication, I should realize that I need to
replace my old 386 5Mb (1.5 Mb smartdrive - rest is XMS) CPU for something
better :-)
5 megabytes of physical memory, 1.5 of it devoted to Smartdrv, is probably
not enough to run BigPerl in a DOS box since most of the remaining 3.5
megabytes will be taken up by Windows (even with virtual memory).
A faded recollection says that BigPerl's runtime support uses twice as much
memory under Windows as it does for the same script under plain DOS. In
plain DOS (no Windows involved) you might be able to process the full file.
One problem daunts me though, when I try to run mhonarc from within a Dos
Box in win 3.1 (65% resources / 13299 kb virtual memory), I get the
following dump:
DOS/4GW Professional Protected Mode Run-time Version 1.97
Copyright (c) Rational Systems, Inc. 1990-1994
NGetOpt 1.13 -- called from main
ERROR: Unable to access .
I am using Perl Kit, Version 4.0 at least at patchlevel 36
That "unable to access" message is one I can't find in MHonarc 1.2.1 source
or documentation (don't have 1.2.3). I think it is either from an error when
trying to enumerate files in the current directory (".") (are you sure you
specified -mbox ?) or from trying to open a file in the current directory
with an empty name.
Sorry, I'm out of ideas.
-- SP
