halFILE for Windows Hardware/Software Issues
Using a Fujitsu ScanPartner 10 Scanner
1. KOFAX KF-920 version 1.11 or later
2. Adaptec 40 series controller (1542C)
3. APSI4DOS drivers
4. Install only KF-920 files during 920 install
5. Make sure PIXPERM.DLL and PIXDFLT.DLL is in \WINDOWS\SYSTEM directory
only and not in \WINDOWS and their dates should be same as the FJSP.PCX
in the \WINDOWS\PIXTRAN directory
Using a KF-9250 and the Panasonic SP-505 Scanner
There is a resistor on the KF-9250 identified as S17 or SP17 that should
be removed if you are using this card with the above scanner. You should
find this resistor as the farthest one from the socket. The symptoms of
having the resistor in place are (1) the scanner will not scan or (2) the
scanner scans but lines are displayed across the page or (3) the scanned
image has speckles on it.
Kofax Software Engines
KOFAX Software Engines provide various software imaging features used by
halFILE. The engines include:
Adrenaline 32-bit - requires halFILE 32-bit scan module
ImageControls 1.01 - 16-bit scanning
KF-911 - image viewer
KF-920 - 16-bit SCSI scanning
KF-940 - image printing
An Adrenaline hardware or software engine and the halFILE 32-bit scan module is required to perform 32-bit scanning.
Adrenaline drivers provide many image scanning and enhancement features such as deskew, despeckle, line removal, streak removal, bar code detection and more.
ImageControls is the software driver that provides image scanning features.
It talks to KOFAX Hardware cards that drive the scanner. ImageControls
must be installed for halFILE to work. Refer to the halFILE User Manual
for installation notes.
The KF-911 Software Engine is a royalty free image decompression and viewing
engine that is automatically installed when ImageControls is installed.
Refer to the halFILE User Manual for installation notes.
The KF-920 Software Engine is an add-on engine that provides for SCSI-based
scanning. With this software engine, which is sold individually for each
PC that has a SCSI scanner, you do not need a KOFAX card to driver the
scanner. We prefer using a KOFAX card because it seems to be more reliable.
However, if you want to use a SCSI scanner you should use an Adaptec 1542C
SCSI card or better if you want it to work. Refer to the halFILE User Manual
for installation notes.
The KF-940 Software Engine is an add-on engine that provides for image
printing to a Windows-based PCL printer. This product, sold separately
as a site license, is required for printing of images in halFILE. It works
with a variety of printers but is most reliable with Hewlett-Packard models.
To ensure fast print speed, increase the memory on the printer to 6MB.
Refer to the halFILE User Manual for installation notes.
Kofax Hardware Engines
KOFAX hardware engines come in a variety of models depending on requirements
for scanner support, speed, document size and resolution. These cards includes Adrenaline and KF-Series cards.
Some scanners require a certain KOFAX card. High speed scanners require better
KOFAX cards with more memory in order to run the scanner at its rated speed.
More memory is required on the card as you scan pages that are larger,
scan at a higher resolution or use special features such as deskew. Computing
Kofax Hardware Engine Memory Requirements To compute the approximate memory
required use the following formula:
600K + (Number of Images * Raw Image Size)
Number of Images = # of prescans (set in Scanner
+ 1 (for image processing features including rotation, deskew, bar code,
Raw Image Size
Example #1: Scanning letter pages at 200 dpi with 1 prescan plus deskew
and rotation enabled. The amount of memory required on the KOFAX card is:
467K (letter/A4 at 200 dpi)
1051K (letter/A4 at 300 dpi)
935K (B-size/A3 at 200 dpi)
2103K (B-size/A3 at 300 dpi)
600K + ((1 + 1 + 1) * 467K)) = 2.0 MB
Example #2: Scanning B-size pages at 300 dpi with 2 prescans and no
image processing. The amount of memory required on the KOFAX card is:
600K + ((2 + 1 + 0) * 2103K) = 6.9 MB
In general, 1 prescan is sufficient for scanners up to 35 pages per
minute and 2 prescans are recommended for faster scanners. The maximum
memory for the different KOFAX hardware controllers is:
KF-7300 3.0 MB
KF-9210 3.0 MB
KF-9250 6.5 MB
KF-9275 50 MB
VB Error 7 - Out of memory
If you are scanning, this is typically caused by inadequate memory on the
KOFAX scan card to perform the task that you are asking it to do. We see
this most often when deskew is enabled and pre-scan cache on the scanner
settings is set to 0. A 2.5 MB or 3.0 MB KOFAX card does not have enough
memory to deskew and cache the images. In this case, either turn off deskew
(and deskew selected pages using the deskew icon) or turn pre-scan cache
You can also get this message by trying to scan a page that is too large
using a resolution that is too high. For instance, scanning a B-sized document
at 400 dpi. VB Error 52 - Bad file name or number This is usually caused
when the scan operation tries to write a file and the drive or directory
to write to does not exist. For instance, if you were scanning to a Novell
Mapped drive/directory of K:\images and then logged in as a different user
where the login script did not map in K:\images, when you scanned this
error would occur.
Corrupted MS-Access Databases
(NOTE: halFILE databases stored in MS-Access are Access 2.5 databases.)
If you get an error opening an Access Database, it may be the database
is corrupted. Corruption typically occurs because the system crashed (power
outage, Windows lockup) while the database was open. Within halFILE, there
are some ways to repair certain corrupted databases. If the parameters
database (PARAMTRS.MDB) is recognized as being corrupted, the system will
automatically run repair on the database. If the basket
database is corrupted, you must first determine which basket database is corrupted
and then repair it. The basket database resides in the halFILE program directory and
is named xxxddnnn.mdb where xxx is the application id, dd is the database id and nnn is a sequential counter.
While the halFILE Image Database can be set up in Access, it is strongly recommended that an
ODBC-compliant database such as Microsoft SQL Server or Sybase SQL Anywhere is used. If the halFILE Image
Database is in access and becomes corrupted, the file to repair is xxxHFWdd.mdb where xxx is the application
id and dd is the database id. This database can be repaired using Tools | Repair Database.
For other Access databases, you must either use VISDATA or Microsoft
Access to repair the database.
Using VISDATA to repair corrupted Access databases
VISDATA is a program that can be used to design, view, repair and compact
Microsoft Access databases. It can also view ODBC databases. VISDATA should
have been installed as an icon in your halFILE group. If a database is
corrupted, when you try to open it with VISDATA, you will get a `database
is corrupted or not an Access database' message. To repair a corrupted
Access database, perform the following steps:
1. Open a database other than the corrupted one using File-Open Database-MS
2. Select Utility-Repair Database and select the corrupted database.
3. The database will be repair and, upon completion, you will be asked
if you wish to open the repaired database. You can open it to make sure
the repair went ok.
Compacting Access Databases
Like most database or index structures, Access databases require periodic
compacting to rebuild the indexes and eliminate unnecessary or deleted
space. It is also recommended that, after repairing a database, you compact
it. Within halFILE, you can compact (or refresh) either a Basket database
(xxxBSKT.MDB) or an image database (xxxHFWdd.MDB) using Tools-Refresh.
If you wish to compact another Access database you must use VISDATA
or Microsoft Access. To compact an Access database using VISDATA:
1. Open any Access database using File-Open Database-MS Access.
2. Select Utility-Compact and select the database to compact.
3. Enter the database name to compact to. We suggest using the same
file name but with a .CMP extension.
4. After the compact is complete, you must rename the compacted database
to its original name from DOS or the Windows File Manager.
8111 LBJ Freeway, Suite 860
Dallas, TX 75251
(800) 442-9273 or (214) 691-4700