JS> I know why, Matthew, but I can't tell you exactly how to fix it.  You 
 JS> don't have enough free conventional memory in the 
 JS> window when Max comes up from remote. Apparently, there 
 JS> is more mem available when logging on locally.  You 
 JS> need to increase your free memory so that Max will have 
 JS> enough to run the MEX files. Also, since you're running 
Maybe I'll try using a different method of spawning max from Binkley.  It's 
been so long since I've run the DOS version, I've been using the OS/2 version 
for almost 3 years.
 JS> NT, you might want to check out the NT-specific version 
 JS> of Max.  I'd guess that would completely eliminate the 
 JS> mem problem since Win32 programs are not restricted to 
 JS> (DOS) conventional memory.
I origianlly had the NT version installed, but you can't run DOS online games 
from the NT version, and since I run a Bre league, it's pretty important for 
me =)  Thanks for the help anyways!  I wouldn't think MEX programs would take 
up that much room, but maybe it's a matter of kilobytes left and the MEX 
program just over-ran it.  Thanks!
--- Maximus/2 3.00
---------------