From: Charlie Smith To: All Thread: BGFAX Problem? (1/3) Date: 18-Sep-97, 7:44pm (Ref# 5733) Hello All. I've been working on an OS/2 REXX script that will is executed by NetMgr/2 when a caller enters a message to "FAX". Basically, NetMgr/2 writes the message out as a file and then does a RunExternal with my REXX script passing in the from, subject (phone) and filename (message) as parms. In the script, I copy the file that NetMgr/2 creates using a unique filename, run MAKEFAX/2 to create the fax format file and the run bgfax/2 to send it. The copy and MAKEFAX/2 steps work fine. BGFAX/2 however does not run. It appears that the program is trying to start but does not get very far. Here is a screen capture of the session during my testing: === Cut === bgfax2 /send c:\bbs\fx\outgoing\26080317.fax XXX-XXXX $c:\bbs\fx\bgfax.cnf OS2/BGFAX/UART1: {Open Port}: 32 === Cut === Can any shed any lite on what this message means? There are NO other programs running at this time trying to access the port. The port is in fact the same port that the BBS runs on. The REXX scripts runs as part of the AfterCaller processing in SPAWNBBS.CMD. Thanks for any help. And yes I am a registered user of BGFAX. Charlie --- GoldED/2 2.50 UNREG * Origin: The CyberSpace BBS * Indianapolis, IN * (317) 856-3441 (1:231/992)
From: Doug Reynolds To: Charlie Smith Thread: Re: BGFAX Problem? (2/3) Date: 19-Sep-97, 11:21am (Ref# 5735) CS> $c:\bbs\fx\bgfax.cnf OS2/BGFAX/UART1: {Open Port}: 32 CS> Can any shed any lite on what this message means? There are NO other CS> programs running at this time trying to access the port. The port is CS> in fact the same port that the BBS runs on. The REXX scripts runs as CS> part of the AfterCaller processing in SPAWNBBS.CMD. I take it you are running Binkley? Well, Binkley keeps the port open during a shell.. you might try using the port handle to send it.. I dunno if you can do that in /send mode though. the maverick # http://www.microserve.net/~mav/ # mav@microserve.net ... Free the indianapolis 500. --- Telegard/2 v3.08.b08/mL * Origin: the rebel multiline 1X % 3.100Gs % 412/459.7290 (1:2610/0)
From: B.J. Guillot To: Charlie Smith Thread: BGFAX Problem? (3/3) Date: 19-Oct-97, 10:11am (Ref# 5771) > bgfax2 /send c:\bbs\fx\outgoing\26080317.fax XXX-XXXX $c:\bbs\fx\bgfax.cnf > OS2/BGFAX/UART1: {Open Port}: 32 Code 32 means "ERROR_SHARING_VIOLATION", so there is still something that is touching the port. My suggestion would be to modify the port that BGFAX uses by putting the letter "V" in front of it, i.e., V1 instead of just 1. The "V" prefix tells BGFAX2 to open the port in a different manner than normal, and sometimes it is able to overcome "sharing" errors. Regards, bgfax author