What we did was to add a ZIP RETURN every 3 passes - it's a kludge pending further
resolution - but at least the system doesn't freeze up and corrupt the database any
more. I'm not sure what percentage causes w2k to freeze, but basically, all the memory
gets used up and w2k leaves. No warnings. Just black screen of death.
[EMAIL PROTECTED] wrote:
>
> Do you have any calculations generally (i.e., % of installed memory in use)
> that you use as an indicator of when you should reload the command
> processor?
>
> tia
>
> Dave Ebert
> [EMAIL PROTECTED]
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Albert Berry
> > Sent: Thursday, June 28, 2001 12:19 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Novell Tuning for RBase
> >
> >
> > We have a caveat for dos sessions under w2k - we have had to add
> > zip returns to the code to free up memory when running rbdos on
> > w2k. The memory in use keeps increasing until w2k shuts the machine down.
> >
> > We suggest that, if you are using rbdos, you fire up a session on
> > w2k along with the monitor and watch the usage climb as you
> > navigate through your system.
> >
> >
> >
>
>
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
