TIP: Click on subject to list as thread! ANSI
echo: maximus
to: MATTHEW LAIRD
from: JACK SMITH
date: 1997-09-06 17:32:00
subject: Max, Mex, & NT

On Sep 04, 1997, Matthew Laird wrote to All:
 ML> users.  If I log on locally, the message area header, time
 ML> bank, and all those other lovely little MEX programs work
 ML> fine, but if I log on remotely, I get the following two
 ML> lines:
 ML> ! 24 Aug 13:01:12 MAX  MEX:  out of memory reading file
 ML> ! 24 Aug 13:01:12 MAX  MEX:  file format error in 'm\headmsg.vm'
 ML> Now does anyone have any idea why these might be appearing?
 ML> Or better yet, what exactly they mean?  If anyone could help
 ML> me out, that'd be great!  Thanks in advance!
I know why, Matthew, but I can't tell you exactly how to fix it.  You don't 
have enough free conventional memory in the window when Max comes up from 
remote. Apparently, there is more mem available when logging on locally.  You 
need to increase your free memory so that Max will have enough to run the MEX 
files. Also, since you're running NT, you might want to check out the 
NT-specific version of Max.  I'd guess that would completely eliminate the 
mem problem since Win32 programs are not restricted to (DOS) conventional 
memory.
Best,
 -Jack
  ogre@nashville.com
--- Squish/386 v1.11
---------------
* Origin: UltraTech - Nashville, TN ftpMS Hub {V.34/V.FC} (1:116/30)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.