Subj : Re: Exit to BBS
To   : Nick Andre
From : Deon George
Date : Tue May 19 2020 04:06 pm

  Re: Re: Exit to BBS
  By: Nick Andre to Deon George on Thu Apr 30 2020 10:31 am

 NA> On 30 Apr 20  21:55:48, Deon George said the following to Nick Andre:
 DG>> FOO 38400 2 999 *L CONNECT 38400
 DG>> IE: The *L wasnt changed to the "line". I was expecting it to be
 DG>> changed to 
 NA> Let me look at the code later today or tomorrow that does this and if a
 NA> fix is necessary I'll publish an update.

Hi Nick,

I'm just circling back to this - did you find out why *L is not being used?

I've noticed something strange, that I would be interested to know if it is workable. I'm leveraging an old frontend BAT file for DB (DB.BAT), which would load the fossil, load DB and when there is a human caller, DB should exit with an error level, so DB.BAT knows to spawn the BBS (instead of exiting).

The reason for *L is I currently have DB as "Node 2" and DB.BAT is called with a "2" argument, which means it would look for the batch file that DB should create "BBS2.BAT". (At the moment I have BBS*L.BAT, which is not working).

When I hard code "BBS2.BAT", I've noticed it is NOT created initally. IE: 

In Advanced -> BBS Configuration -> DOS commands, I have
echo \FOSSIL\X00\X00 E > BBS2.BAT
echo SPAWNBBS *B *P *T *L *C >> BBS2.BAT
*X

When I connect first connect (BBS2.BAT doesnt exist) - I am presented with "Press ESC...", and DB reports "Anxious BBS Caller..." and exits. It does *NOT* create BBS2.BAT.

Because it doesnt exist, the DB.BAT cycles round and reloads DB. When it does DB recognises that there is a connection and re-shows "Press ESC...", pressing ESC this time has BBS2.BAT created.

If I hangup and call it again, I have to go through the 2 "Press ESC" cycles to get into the BBS on the "same" connection.

Hope this makes sense...?
....лоег

.... Money is a sixth sense without which you cannot make use of the other five
--- SBBSecho 3.11-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

.