10 Nov 98 02:45, Brad Reddekopp wrote to All:

 BR> echo b=%2 p=%3 t=%4 s=%1 >>frombink.log

 BR> Would that show me the values being passed by Bink if they're
 BR> being passed?   The file FROMBINK.LOG looked like this:

Well, it OUGHT to.

 BR> b= p= t= s=

How odd.

Uh-oh. This might do it. A segment from my Bink batch...

  ...
  BTO386 %BINKADD% TASK=1
  IF %?==255 GOTO BNKERROR
  IF %?==254 GOTO CFGERROR
  IF EXIST BBSBAT01.BAT GOTO PHAENIXR
  IF %?==249 GOTO MAINT
  ...
  :PHAENIXR
  CALL BBSBAT01.BAT
  GOTO BINK
  ...

Remember that your Bink batch, if you follow the "Spawn" route
[signified by the "BBS Batch" verb], must call a batch named
"BBSBATxx.BAT" where xx is a the task number in hex.

BBSBATxx is generated by Binkley and contains exactly one line.

  SPAWNBBS [whatever the passed variables are]

It's SPAWNBBS that must contain the Max start routines. A segment follows...

   ...
   iff "%1"=="*LOCAL*" then
       max
       set maxerr=%?
     else
       SET MSTRING=%{at}INSTR[3,6,%{at}INSTR[%{at}INDEX[%5,TX=],9,%5]]
       SET REALBAUD=%{at}INSTR[0,%{at}INDEX[%MSTRING,/],%MSTRING]
       max -s38400 -b%REALBAUD -p%3 -t%4
       SET MAXERR=%?
     endiff
   ...

[Well, that's overly complex. I've got shortcuts for one-key local and
parsing routines for this dreadful excuse for a connect string my modem
hands me rigged in here. Those functions you may notice are gifts from
4DOS, Rex Conn's gift to sysops everywhere.]

If your Bink batch is executing SPAWNBBS directly, then those variables
will be empty, creating the outlined problem.

Note that if this situation exists, ensure that stray or orphaned BBSBATxx
files are cleaned up before Bink starts.

I may be wandering off completely, but this is could be one thing that's
troubling you. It at least explains the lack of variables.

Asher Densmore-Lynn 
... All things are difficult before they are easy.

--- Squish/386 v1.11