From: kla!M_Morris%pid.csd@SUN.COM (Mike Morris)
Newsgroups: bit.listserv.novell
Subject: Re: GET LOCAL TARGET STACKS
Date: 18 Nov 92 23:14:05 GMT
Reply-To: Novell LAN Interest Group <NOVELL@SUVM.BITNET>
Organization: KLA Instruments Corporation
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Priority:     normal
X-Mailer:     Pegasus Mail v2.3 (R4).
content-length: 3903

=> Hi all, I have recently had a program which hangs when it attempts
=> to send messages to multiple stations. As we are running ODI, the
=> suggestion was made to put GET LOCAL TARGET STACKS = 5 in my NET.CFG
=> and this would cure it. Well, it has. Only thing is I'm unsure WHY
=> it works. Can anyone out there explain what the problem was & why
=> this fix works please.
=>

Here's a compilation of messages from another list (Pmail-updates) on
which this was discussed. None of the below is mine, and separate
messages are separated by rows of asterisks.

HOPE THIS HELPS!!
****************************************************************
>>My machine hangs if I send a message to myself. (I don't do this
often, but I
>>was writing a utility which uses Novell's message sending recently.)
>>
>>The problem occurs with Novell's SEND command, and with other
programs which
>>use the message sending facility.
>>
> Include a "Get Local Target Stacks=n in your net.cfg . That should
solve the
> Problem (Solved it here).

This doesn't actually solve the problem, it just makes it go further
away.

The problem seems to occur with programs that issue a SEND to self and
then exit immediately.  One the n'th repetion, the system hangs (where
n is your get local target stacks number).  I can make this problem go
away by putting the line  DELAY(500);  in the software I'm writing.

I'm suspicious that this may not be unique to sending to self, but is
associated with any message that comes in as any program exits.

The problem occurs using ODI drivers, but not with IPX.

****************************************************************
Hello,

> > When using ODIPKT with Pegasus, I have found the following problem:
> > If a user sends mail to him/herself, immediately after the "New mail
> > from Joe ..." screen Pegasus dies a brutish death. Selecting any
menu
> > item will entirely freeze the 'puter. If run under Windows, Windows
will
> > terminate Pegasus with a VERY nasty error-message ("This
applications has
> > violated system integrity and will be terminated. Exit Windows and
restart
> > your computer")
>
> This may well be nothing to do with Pegasus.  Trying doing a few
> SEND's to yourself and let us know what happens.

To extend that - this looks like a known Novell problem. If you
use 3.26 Shells, apply the keybfx patch to them and include a
"GET LOCAL TARGET STACKS=10" in your NET.CFG.

****************************************************************
>
> > The solution is to download DOSSUP5.ZIP and
> Thanks for this info, can you only tell me where to get this patch?

I downloaded DOSSUP5.ZIP from Novell's tech support library on
CompuServe. It turns out that the patch is also there by itself in a
much smaller file named kbd326.zip. But even that is more than you
need: The entire patch can go into your net.cfg file, which will cause
the memory image of netx to be patched at load time. Here's what I put
in my net.cfg file (apparently it needs to be in the directory that is
current when you load netx.com, which for me is my c: root directory):

GET LOCAL TARGET STACKS = 10
PATCH= 24744, 144
PATCH= 24745, 144
PATCH= 24746, 144
PATCH= 24747, 144

That's it! If you run EMSNETX instead of NETX, uses addresses starting
from 33795 instead of 24744 like I do. If you run XMSNETX, start with
32151.

****************************************************************
> Do you have the equivalent starting addresses for the Burst-mode
> shell, BNETX?

Whoops, sorry, I forgot to include that. The patch for BNETX starts at
25304.



     ===========================================================
         Mike Morris  --   Internet:  sun!kla!csd!pid!mikem
                         CompuServe:  70142,1653
                          Facsimile:  (408) 434-4261
                              Voice:  "Mike"
     ===========================================================