RD> I'm trying to run it from drive F on the network machine.  If I run
RD> it from drive D on the BBS machine it works fine.
 DH> Sounds to me like MAX.CTL refers to the drive as D, so 
 DH> when FB looks at it it's lost.  What paths are in 
 DH> filearea.ctl?
 RD> Yes, Max.Ctl has to show D: because the BBS runs on 
 RD> that machine.  That's what I'm trying to work around.
My solution.  Actually, I implemented two solutions, either one would work on 
its own, but both give me increased flexibility.
First of all, since all of my file areas, message areas, and everything else 
Maximus cares about, are all on the same drive (G: in my case), I simply 
changed everything to not refer to the drive.  i.e., my maximus directory is 
\bbs\max.  In my batch files (rexx scripts in OS/2, actually), I ensure I'm 
in the right directory for Maximus before launching it.  Thus, when it looks 
at "\bbs\mail\netmail" it goes to "G:\bbs\mail\netmail".  Note, however, that 
I do have the SET MAXIMUS in my config.sys (or autoexec if you're on DOS) 
pointing to G:\BBS\MAX\MAX.PRM - this doesn't hurt because each machine would 
have a different setting.
Second, even though I no longer have two machines, I have my network going 
anyway.  I just have my BBS machine net use to itself - since G: is shared, I 
have it used as S:.  This is simply the standard I chose.  Any new machine I 
put on here will be able to share it as S:, and it will work.  (They 
obviously point MAXIMUS to S:\BBS\MAX\MAX.PRM.)  In this scenario, I could 
tell Maximus to use the S:\BBS\MAIL\NETMAIL directory without any problems.  
However, this way I still have the freedom to NOT use S: at some point in the 
future if I so choose.  (Feel free to use whatever drive letter you want, of 
course.)
Another addition has been the ability to use a "BBSDIRS" command file.  In 
DOS, I would simply have it set up all my directories in the environment.  In 
OS/2, however, I use REXX which allows it to return a value - if I ask for, 
say, the maximus directory, it returns "S:\bbs\max".
OS/2:
  call directory bbsdirs(maximus)
  'maxp ...'
DOS:
  call bbsdirs
  cd %bbs_drive%
  cd %maximus_dir%
  max ...
NT would be the same as DOS, excepting the Maximus executable name, of 
course. Warning for the DOS method: You may need a larger environment on your 
command processor... I have over 30 directories and other pieces of 
information in there myself for Max, Bink, Bluewave for Max, GoldEd, 
Hubroute, junktick, logfiles (and the backup logfile dir), makenl, nodelists, 
inbound files, qnode, sqaverw, squish, ... :-)
Good luck!
--- Maximus/2 3.01
---------------