David Blum wrote in a message to Jim Brown:
 JB> Yes    Ok, lets start with the obvious. Do you have an 'm'
 JB> directory? Is it a subdirectory of 'max'? Does it have the
 JB> above referenced mex files in it? Have they been compiled
 JB> (with mex)?
 JB> Yes    The less obvious. Does your batch file for local login
 JB> change to the 'max' directory and then start maximus? Does
 JB> your batch file for remote login change to the 'max'
 JB> directory and then start maximus? Have you set the 'maximus'
 JB> environment variable?
 JB> Yes     The ridiculous. Did you install maximus? :-)
DB> You set me to thinking of which could be dangerous!!  I discovered
DB> that if I shell from Binkley and load MAX locally I get the same
DB> thing as a remote caller. Now if I drop out of BINKLEY completely
DB> evrything works just great.  It is a memory problem.  What I have
 How are you passing from Binkley to Maximus?  Doing a BBS Batch
 uses a _lot_ less memory on DOS systems.  Seems only OS/2 people
 can use BBS Spawn.
DB> done is this.... New HD 5.1 used win95 dos to format it FAT32 .....
DB> also am using WIN95 DOS *but* not windows itself as I haven't had
DB> the time to set down and get it setup properly. Did Use memmaker and
DB> have 615 free but maybe it don't work well with that version of DOS
DB> 7.10.   Now I have a question, will DOS 6.22 work with FAT32 or
DB> should I get a version of QEMM.  I have 20meg onboard.
 DOS 6.22 will not be able to read a FAT32 partition.  Nor will QEMM
 probably, unless it's made to handle it.  Check the box carefully.
 The only DOS that can read FAT32 is the DOS in a DOS window under
 the Win95-B shell.  And a suitable bootdisk, of course.
 You probably don't need QEMM anyway.  Try BBS Batch and see what happens. 
 Patrick
--- timEd 1.10
---------------