|
|
|
|
ACCFAX Technical Support Issues
|
1.
MODEM IS NOT DIALING - option 1
While in the \FAXDIR
subdirectory try to use the command FAXSEND to send
out a file to test my fax modem and no dialing
happens. The message may say it was sent
successfully.
Ensure that you have
the correct COM port selected in the SETUPFD profile
for your fax/modem.
Ensure the fax queue
is empty by going to \FAXDIR directory and running
CLEARLOG from the DOS prompt.
There are several
other settings to check in the SETUPFD profile.
(1) "Select time to wait for dial tone" -
This should be set at 60.
(2) "Select comma delay" This should be
set at 1 or 2. The comma can then be used in your
dialing numbers to pause between numbers as they are
dialed. For example, to get an outside line you may
have to dial 9 and then wait a second. You can use
9,331-6603 as your dialing sequence.
(3)"Select touch tone duration" ensure
that this is set to at least 70 milliseconds. If the
duration is too short your phone line may not
recognize the dialing.

2.
MODEM IS NOT DIALING - option 2
This answer assumes
that you have tried it independently without ACCFAX,
just using FAXDIR and the FAXSEND command and it
dials and faxes fine.
Check -
Sometimes there could be an interrupt conflict in
terms of ACCFAX communicating to the FAXDIR program.
Some network configurations do not let the call to
the driver go through. ACCFAX was designed as a
standalone PC doing fax distribution. It does not
need the rest of ACCPAC data to fax. Install ACCFAX
on a local PC(the one with the fax board) and copy
the *.FAX file from the network to the PC. Re-boot
the PC without logging onto the network. Start
ACCFAX and try a "TEST" fax with the job
that was copied.
Check FAX file
- Another area to check is that the *.FAX file was
created properly from ACCPAC. When you go into
"SEND FAXES" in ACCFAX, the job name, the
spec name and the graphic name should all appear
instantly. You should not have to edit the job to
get this info to appear. The ALT 159 "f"
character control line must the first line in the
*.FAX file. No blank line preceding. You can use the
DOS EDIT command to look at the xxx.FAX file. The
ALT 159 character and control line must be on the
first line in the file.
Check memory -
ACCFAX rasterizes the text from ACCPAC with a
graphic PCX file which requires a lot of
conventional memory. You should have at least 604K
of free memory available when your fax drivers and
ACCFAX are loaded. Type MEM at the DOS prompt to
verify.
3.
ACCFAX DOES NOT WORK ON MY NETWORK.
Loading of the CASMGR
can only be done if you have a fax/modem in your
local PC.
What fax/modem do you have?
*MultiModem
ZPX (ISA) is recommended. Model#: MT5634ZPX.
Instructions for setup of
above modem with ACCFAX
For Windows use, you
must follow the procedures in our technical
script
Were you able to
run SETUPFD?
ACCFAX has been
designed as a self contained fax distribution
product for ACCPAC. Users on the network print their
*.FAX files to the ACCFAX work subdirectory. In many
cases, ACCFAX can read the *.FAX files directly from
the network and fax them out. Some network
configurations cause ACCFAX not to dial on the
fax/modem due to application interrupt conflicts.
Try running the FAXSEND (appdx C) command without
ACCFAX. You can try installing ACCFAX on your C
drive. The user only has to install WSM and ACCFAX.
ACCFAX dos not require any ACCPAC applications or
data to work. The user would copy the *.FAX files
created on the network to the local PC, reboot as a
standalone PC and start the fax sending. ACCFAX runs
independent of everything else, keeps an activity
log and error reports.

4.
I AM ON A NETWORK AND ACCFAX HANGS DURING THE MERGING
STEP.
Many users do have
good success on networks. Sometimes, changing the
loading order of the FAXDIR before or after NET and
try loading it HIGH as well may be successful.
ACCFAX requires a minimum of 580k of conventional
memory to load and rasterize the graphic images for
faxing. Its is very memory intensive. Load as much
as you can into high memory. That is why running on
some networks may be a problem due to the amount of
free conventional memory that is required.
5.
I AM TRYING TO GET ACCFAX WORKING UNDER WINDOWS 95?
6.
I AM USING ORDER ENTRY 6.1B TO PRINT ORDERS FOR
ACCFAX. I KNOW I HAVE DEFINED THE ACCFAX CONTROL LINE
IN THE SPECIFICATION PROPERLY. THE FAX FILE I CREATE
DOES NOT SHOW UP CORRECTLY IN THE SEND FAX SCREEN IN
ACCFAX. IT DOES NOT HAVE THE DESCRIPTION OR THE SPEC
FILE NAME DISPLAYED ON THE SCREEN.
Using a DOS Editor,
edit the xxx.FAX file that you have created from the
OE print function. It is typically printed to the \ACCFAXWK
directory. This is the file containing the orders,
or invoices etc that you want to fax. Look to ensure
that the ACCFAX control line begins with the ALT 159
"f" character. If it does not, make sure
you have defined it in your OE specification. See
Appendix E in the ACCFAX manual for examples.
If is defined
correctly then -
If Order Entry (ver.6.1b) prints the
specification without the alt159 "f"
character then you require a fix to OE. There is an Order
Entry PTF diskette from CA that fixes its
inability to print any character that has an ascii
value greater than 128. This also caused a problem
with anyone wanting to print some alternate
characters for other languages as well.
7.
ACCFAX SENDS THE FIRST 10 TO 20 FAXES OK AND THEN IT
HANGS THE SYSTEM OR EVERY FAX AFTER THAT GETS AN ERROR
SUCH AS "USER CANCELED EVENT"
Typically if you are
sending more than 15 faxes at a time in a batch you
require a high quality fax modem that is designed
for fax broadcasting. This is a big cause of faxing
problems with ACCFAX. Fax broadcasting requires a
fax/modem to handle hundreds of faxes one right
after another. Most class 1 and 2 type fax/modems in
the marketplace are not capable of this type of work
and break down or are unable to reset themselves
after only a few faxes. Speed is not the issue, it
is the quality of the modem. MultiModemZPX,
ISA fax modems have been designed for this type
of use and ACCFAX works great with them. The model
you pick must be ISA.
- 8.
I am using ACCFAX with Novell and am getting huge
files. What is causing this?
The huge file is
called a sparse file and it has nothing to do
with ACCFAX or ACCPAC. It is usually caused by
bad NIC's or hardware somewhere. This issue has
been around since Netware 3.12 at least. It
shows up as a very large file that takes up
enough room that it cannot be duplicated on the
same drive. The problem is not unique to ACCPAC,
we have seen it in other applications as well,
including DOS-based ones running on DOS-only
workstations and with various versions of the
Netware Client. For information about how to
deal with it visit the Novell site at: http://www.novell.com/documentation/lg/nw5/docui/index.html#../usreflib/ecod_enu/data/h0001187.html
.

|
|
|
|