On Feb 01, 1998, David Blum wrote to gary:
 DB> ! 01 Feb 15:23:55 MAX  MEX:  can't read file 'm\headmsg'
 DB> ! 01 Feb 15:24:15 MAX  MEX:  can't read file 'm\headmsg'
 DB> ! 01 Feb 15:24:51 MAX  MEX:  can't read file 'm\headfile'
 DB> ! 01 Feb 15:25:03 MAX  MEX:  can't read file 'M\fbrowser'
 DB> ! 01 Feb 15:25:03 MAX  MEX:  can't read file 'm\headfile'
 DB> ! 01 Feb 15:25:04 MAX  MEX:  can't read file 'M\fbrowser'
 ------
 DB> Now here is the funny part, if I sign on local MAX will read
 DB> those files and I won't get these nastgrams as you can see
 DB> what I get.  But log in otherwise and remotely and I get the
 DB> nastygrams.  I have 2 phone lines so I call from the othe
 DB> machine and that is the result,  got any ideas?
Been there, seen this, David.  It wasn't obvious in the least but what was 
happening was that there wasn't enough free conventional memory when the 
REMOTE node was logged into.  The problem never arose on the local node.  
Gave the remote node's window more free mem and all went well after that.
Cheers,
 -Jack
  ogre@nashville.com
--- Squish/386 v1.11
1:116/30)
---------------