home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
fax130m.zip
/
WHATS.NEW
< prev
Wrap
Text File
|
1994-07-27
|
6KB
|
123 lines
BGFAX 1.30 Revision M [ You can FREQ the magic name "BGBETA" from
TUE 26 JUL 94 1:106/400 to obtain this beta. ]
=====================
1. 16-bit OS/2 version of BGFAX2.EXE and MAKEFAX2.EXE included. Be sure
that you are using Ray Guinn's SIO.SYS as your OS/2 serial driver.
There are a few differences between BGFAX/2 and BGFAX:
a. In BGFAX.CNF, instead of using PO=3 to specify your com port, you
will need to use P2=3
This is done so that people can test running BGFAX and BGFAX/2
without having to keep changing their BGFAX.CNF file when they
need to specify non-standard addresses like PO=3e8x3
b. FOSSIL mode is not supported in BGFAX/2 since all communications
are done via system calls.
c. Specifying non-standard port addresses and IRQs are now supported
in BGFAX/2 since SIO.SYS nicely handles that for me
d. 2400 data modems not supported in 1200 mode (who is going to be
using a 2400 modem with OS/2 anyway??)
e. The NFAX.COM TSR "FAX" indicator is not supported
f. 50 line mode is not currently supported. I want to put 50 line
mode in it, I just don't know how at present.
2. If you were using a version of the Supra fax modem and were trying to
use in to answer calls in Class 1 mode instead of Class 2 mode, and
if you were getting +FCERROR messages, you might want to try the new
/DW switch on the BGFAX /HOST command line.
3. If you were storing faxes in QFX format, and you receive a 2D-MR style
comes in, BGFAX would save it, but it would be unusable because Quick
Link II does not support 2D-MR style faxes. Now, BGFAX will automatically
shift to ZFAX file format in the event this occurs so that you will get
a usuable fax file out of the connection.
BGFAX 1.30 Revision J
TUE 07 JUL 94
=====================
1. A new BGFAX.FNT file is included, it's 48K. A greater selection of fonts
is now available with the MAKEFAX utility. Here's a description:
/F0 16x16 /F0 /HR 16x32 [ 100 characters per line ]
( This /F0 font is actually a 8x16 font, the original BGFAX font )
/F1 16x16 /F1 /HR 16x32 [ 100 characters per line ]
/F2 24x16 /F2 /HR 24x32 [ 67 characters per line ]
The new fonts are modified versions of the ZyXEL's ZFAX font. These
fonts were added because many users claimed the original font (/F0)
was too ugly and small. /F2 should be very nice for you. Just keep
in mind /F2 only allows 67 characters per line!
A new executable is included: FNTEDIT.EXE. This is a font editing file
for the BGFAX.FNT file included with this beta. I did not have
enough time to get all the rough edges off of the new 67 char/line
font, but should have time by the next beta.
2. BGFAX /SEND mode now has the "makefax" utility built into it. What??
Well, before, in the release version of BGFAX 1.30, it would shell to
MAKEFAX.EXE to construct the top of page header files. Now, a shell is
no longer required, so it will build the header internally.
3. Many people reported problems with files being dumped all over the
place (the log files, the faxes, etc.) I've tried to get this problem
out.
4. New command line parameter: /HB
/HB means that an ASCII banner file (BGFAX.H$$) already exists. BGFAX
will then turn that into another temporary file BGFAX.HH$ (fax image
file). You should not really need to mess with this. If you don't use
this switch, BGFAX will construct its own ASCII banner file (using the
template information out of the config file), and then make the temp
fax image file. Confused? Top of page banner options:
/NB -> no top of page banners
/XB -> assume fax image banner file already exists (BGFAX.HH$)
(to use the /XB switch you must use MAKEFAX.EXE in /HDR mode)
/HB -> assume ASCII banner file already exists (BGFAX.H$$)
Again, the /XB and /HB switches are really for developers who want
to have complete control over what goes onto the top of the page.
5. New operation mode: /RING
Example: BGFAX /RING
This is basically a modified version of /HOST mode. In /HOST mode,
BGFAX waits for a "RING", then answers the phone. In /RING mode,
BGFAX will go into a /HOST-like mode, but will initialize the modem,
and then immediately send the answer string to the modem. What's the
reason for this? Some people have written their own programs which wait
for a "RING" (or ring-status-indicator) that take up much less CPU
resources than CPU-hog BGFAX /HOST. A DTE speed is o
6. New command line parameter for /HOST and /RING modes. /DTE:nnnnn which
force BGFAX to use the DTE specified, overring the SP= entry in the
BGFAX.CNF file. Ex: BGFAX /RING /DTE:57600
7. That silly BGFAX.DAT file that always pops up... Well, you can now
delete it and it will stay away. BGFAX.DAT is now used ONLY in /HOST
mode, the way it was really meant to be used for. (The BGFAX.DAT file
was never intended to exist in /Fxxx, /SEND, /INIT or /RING mode.)
BGFAX 1.30 Revision A
SUN 19 JUN 94
=====================
This is a public beta version. It is assumed you already have the
BGFAX130.ARJ, as this beta includes only updated files.
1. Believe I have fixed a major bug with BGFAX when in /SEND mode, when
using a Class 1 modem. BGFAX 1.30 would never get an acknowledgement
from the remote machine. This was because BGFAX was "filling" the EOL's
in the RTC sequence. Don't worry if you don't know what that means, but
it was a major problem that's now fixed. BGFAX users using /SEND mode
with a Class 2 or Class 2.0 modem should notice no change.
2. I documented something in BGFAX 1.30, that actually was not added. :-)
Well, now it will work. If you are using BGFAX in /HOST mode, BGFAX.DOC
said that you could specify a filename on the LO= or DO= line.
Actually, it was only working on one of the lines. There was also a
typo in the BGFAX.CNF file included with BGFAX 1.30. There was mention
of a ";lo=<load>" when it should have been ";do=<load>".
Regards,
bgfax author