home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
fax140c.zip
/
WHATS.NEW
< prev
Wrap
Text File
|
1995-01-28
|
5KB
|
113 lines
BGFAX 1.40 rev C FREQ file as magic name BGBETA from 1:106/400
SAT 28 JAN 95 also...FTP to 199.3.234.248, "bgfax" directory
================
1. Attempted to fix a bug in the /LP (legal paper) print option in 1.40B.
BGFAX 1.40 rev B
FRI 27 JAN 95
================
This beta release contains a hodgepodge of miscellanenous fixes and minor
new things...
1. I have attempted to fix the problem in VIEW 1.40A that was causing it
to not print on many printers. Please send feedback on whether or not
this corrects the error.
2. A new command line switch for VIEW, /LP --- this switch means you plan
to use 'legal sized' paper on your laser printer. (Legal sized paper
is 8.5 x 14" instead of the normal USA 8.5 x 11" size).
3. BGFAX/2 should now allow programs such as Binkley/2 work with BGFAX
by passing of the com handle, rather than the com port number. For
example, if the handle is 187, start BGFAX/2 like this:
bgfax2 /fax c:\bgfax h187 z
Since I have no idea whether the handle is in decimal or hex, if your
com handle is, say hex:406, start BGFAX/2 like this:
bgfax2 /fax c:\bgfax h$406 z
One of those ways should prevent the Openport{32} error from occuring
during an OS/2 spawn.
4. BGFAX /HOST mode can now be terminated by semaphore files. When BGFAX
is running in /HOST mode, if you put a file called "EXITnnn.SEM" in the
BGFAX directory, it will cause BGFAX to exit with errorlevel nnn.
i.e., "EXIT72.SEM" will cause /HOST mode to terminate with level 72.
This is useful on multitasking or networked systems.
5. BGFAX will now pass a second parameter to the DOPRINT.BAT (DOPRINT.CMD)
file. The second parameter will be the remote fax ID, with underscores
replacing spaces. This can be used in case your EXEPRINT.BAT/CMD file
will need to scan for certain bad numbers (fax advertising) and not
print them, or, can be used to pass to programs designed to page you
with the remote fax ID. Confused?? Don't worry about it. Here is a
sample of the new DOPRINT.BAT/CMD file:
CALL C:\BGFAX\EXEPRINT.BAT C:\BGFAX\FAX0872.FAX (old way)
CALL C:\BGFAX\EXEPRINT.BAT C:\BGFAX\FAX0873.FAX 713_893_9124 (new way)
6. Some of the older Class 1 modems do require a 19200 shift. I thought
all Class 1 modems behaved like the Hayes Optima 288, but apparently
I was wrong about that. (The Optima 288 doesn't use 19200 shifting,
while I recently discovered modems such as the Hayes Accura 14400 do
require 19200 shifting.) To handle this situation, a new com port
modifier is available, the minus sign. Example:
bgfax /fhay:713_555_1212 c:\bgfax 2- z
The above line would tell BGFAX to use Class 1 mode on COM2, but it
will perform 'old-style' Class 1 DTE shifting. (Notice it is "2-"
instead of "2"). If you are using a Hayes Accura 14400 in BGFAX's
/HOST mode, make your BGFAX.CNF file say po=2- if you are using COM2.
7. If you were receiving a 2D-MR coded fax and BGFAX was not receiving
a valid 2D-MR RTC code at the end of the page, BGFAX was trying to
'help' by adding a 1D-MH RTC code. (It should have added a 2D-MR
RTC code, as this version should now do.)
8. I have attempted to fix a problem during PCX conversion that existed
in VIEW 1.40 and 1.40A. I think it's fixed, but am not sure.
BGFAX 1.40 rev A
FRI 06 JAN 95
================
I assume you have already downloaded and installed BGFAX 1.40. If not,
you need to FREQ it as the magic name "BGFAX" if your in Fido, or grab
it from ftp://199.3.234.248 in the "BGFAX" directory.
A 'major' change to VIEW.EXE, and a very minor change to BGFAX.EXE and
BGFAX2.EXE is included in this beta.
1. Many people have reported problems trying to print faxes on Laser or
Desk Jet printers. This VIEW.EXE update tries to fix the problem by
sending printer output via software interrupt $17, rather than opening
'LPT1' as a 'binary file'. The printing screen has had an overhaul as
well. Here is some example command line parameters:
view /p40 will print to LPT1 via Int 17 (new way)
view /p40:lpt1 will print to LPT1 via Int 17 (new way)
view /p40:lpt2 will print to LPT2 via Int 17 (new way)
view /p40:hello.you will print to file 'HELLO.YOU' via binary file
view /p40:+lpt1 will print to LPT1 via binary file (old way)
Under OS/2, it appears as if printing the old way is faster, that's why
I made it possible to print using the old way (by inserting the plus).
Under DOS, I didn't really notice a difference in print speed. Please
send me reports as to if this works better than the old VIEW.EXE.
2. A user with a new Practical Peripheral's V.FC modem reported trouble
sending faxes. Apparently, the modem would echo "ATDTphonenumber "
...instead of "ATDT phonenumber"
which would confuse BGFAX and BGFAX/2. The extra spaces in the modem
output are the problem. This update to BGFAX should fix this problem.
Regards,
bgfax author