Hello Robert,

On Thu Sep 07 2017 00:02:12, Robert Wolfe wrote to All:

 RW> The problem I have is that when passing the com port to Max/2 in
 RW> EXEBBS.CMD, Max returns with a message say that it cannot load the
 RW> comm driver.  When I pass al lthe contents of the % variables to a log
 RW> file, I get the following:

 RW> {0}[c:\ftn\fd] type fd.out
 RW> Speed: 57600
 RW> Port: 1
 RW> Event Time: 10080
 RW> Task #: 1
 RW> Connection Msg: /ARQ/TEL_FROM_127.0.0.1
 RW> CID: N/A
 RW> Port Handle: 12

 RW> I pass the port number as well as the speed and handles to Maximus/2
 RW> but it still doesn't accept the connection and I get the following
 RW> error message is the logs for this particular node:

 RW> {0}[c:\ftn\fd] type \max\Max.Log

 RW> + 06 Sep 23:51:53 MAX  Begin, v3.01 (task=1)
 RW> ! 06 Sep 23:51:53 MAX  SYS0032:  Cannot open com port (com1)
 RW> ! 06 Sep 23:51:53 MAX  Communications driver not properly installed

 RW> However, whenever I run Maximus/2 in WFC mode, I do not get the above
 RW> error message.

So let me get this straight.

In the first instance, FrontDoor is loading Maximus/2? And in the second
instance you're just running Maximus/2? normally?

The only issue I can see is that it states "Communications driver not properly
installed", so is there a difference in the way you're executing Maximus/2 from
 the command line versus executing it from FrontDoor? Should you be adding
something (ie: in a batch file) that pre-loads your fossil driver before
passing off to Maximus/2 from FrontDoor?

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
 * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)