DF> I am running Win95 on a p166 mmx system.  I run 
 DF> maximus for DOS under win95 with frontdoor on node 1 
 DF> and WFC on node 2.
 DF> My problem is that when someone calls and then logs 
 DF> off, maximus locks up my system as soon as the .bat 
Ok..... here are a few possibilities:
 DF> cd\max
 DF> rename d:\max\ipc\ipc01.bbs ipc01.not
 DF> MAX.exe MAX -s115200 -b115200 -n1 -ld:\max\log\node1\max1.tmp
       /\    /\   why?
 DF> If Errorlevel 12  goto Export
 DF> If Errorlevel 11  goto Mash
 DF> If Errorlevel 10  goto End
 DF> If Errorlevel 5   goto Acall
Looks like you are using parts of the BINKLEYTERM SPAWNBBS with FroDo, and 
since I don't know FroDo, I can only say the commands you listed don't match 
the FroDo samples in the docs (this may not matter, but then again it could)
 DF> D:
 DF> cd \max
 DF> scanbld -c
What do you think this is doing? The section is too long to put here, but 
review scanbld in the docs, section 8.11 page 138 MAX 3.x docs
 DF>           cd d:\max\log
 DF>           if exist node1\val1.tmp copy cbv.log+node1\val1.tmp cbv.log
 DF>           if exist node1\val1.tmp del node1\val1.tmp
 DF>           if exist node1\ul1.tmp copy uploads.log+node1\ul1.tmp  DF>     
      if exist node1\ul1.tmp del node1\ul1.tmp
 DF>           if exist node1\max1.tmp copy 
 DF> callers.log+node1\max1.tmp callers.log
 DF>           if exist node1\max1.tmp del node1\max1.tmp
 DF> if exist d:\max\cdch?-n1.use rename D:\max\cdch?-n1.use cdch?-n1.not
To me, it seems that how you have your after caller processing and calls to 
scanbld structured need reworking.
--- Maximus 2.02
---------------