I just realized that while I can use BlueWave 4.01 with PcBoard no
problems while logged in locally, remote callers do *NOT* see the
BlueWave screen.  I can see from the board side but all they see is
the commmand to open the door.  Like this:

 Main Board Command? op 1

and the remote user's screen *never* changes.  On the BBS side, I can
see the BlueWave door menu, etc (like the remote user should see).

I'm running NetFoss 1.0 with PcBoard 15.22 and BlueWave 4.01

My pcboard.bat file that NetFoss calls is

Command=d:\netfoss\nf.bat /n*N /h*H c:\pcb\pcboard.bat *N

The pcboard.bat is

{at}ECHO OFF
share
CLS
SET PCB=/NODE:%1 /PORT1F:
SET PCBDRIVE=C:
SET PCBDIR=\PCB\NODE%1
SET PCBDAT=C:\PCB\PCBOARD.DAT
SET NODE=%1
:top
%pcbdrive%
cd %pcbdir%
if exist remote.bat REN remote.bat remote.sys
if exist door.bat   DEL door.bat
if exist endpcb     DEL endpcb
c:\pcb\pcboardm /file:%pcbdat% /C:115200
if exist remote.bat CALL remote.bat
if exist door.bat   CALL door.bat
if exist event.bat  CALL event.bat
if NOT exist endpcb GOTO top
:end

The /PORT1F: is telling PcBoard to use the fossil driver.

PcBoard QWK and file transfers work perfectly; the BlueWave door does
not.  The batch file that calls BlueWave is

{at}ECHO OFF
C:
CD \PCB\BWAVE
BWMAIL.EXE /PCBDAT=%PCBDAT% /PCBUSER=%PCBDRIVE%%PCBDIR%
IF "%INPCB%"=="Y" EXIT
%PCBDRIVE%
CD %PCBDIR%
BOARD

I've checked BlueWave's configuration via BWSETUP and I don't see
anything that needs to be changed.

The pcboard.bat file is straight out of the NetFoss manual.  Does
anyone have any suggestions for me?  Thanks!
 
--- MultiMail/Win32 v0.49