Document Management Software - DocuLex

Scanning Questions

How fast should the scanning/printing/OCR/PDF/Endorsing process be?

There are many variables that control the speed of different attributes of the DocuLex software. We have included a few hints below to help you get the most from your software.

Different scanners have different rated scan speed. Many scanner manufacturers quote rated speed of a production scanner by scanning low-DPI (200 DPI, for instance) images in binary (pure black & white) format. Scanning at a higher DPI will tend to reduce the number of pages per minute (ppm) that a scanner is capable of. Also keep in mind that scanner manufacturers often quote both pages per minute (ppm) and images per minute (ipm) with duplex scanners. A duplex scanner capable of 50 ppm is often capable of scanning 100 images per minute, but only if both sides of the page are being imaged. The rated speeds of most production scanners are available on the web site of the scanner’s manufacturer.

As with scanners, different printers have different rated speeds that are usually quoted at printing at a low resolution. DocuLex recommends printing at the same DPI of the images that are being printed through our software. For instance, if images have been scanned at 300 dpi, they should be printed at 300 dpi to achieve the highest print speed possible. Some print drivers do not allow the DPI setting to be changed, though many PCL drivers are interchangeable from one printer manufacturer to another, which allows the user to print to a printer from a driver that will allow such a setting.

Many factors such as processor speed and RAM will affect the speed of the OCR process. On today’s ‘average’ machine, DocuLex software will OCR between 400-800 pages an hour (8.5×11 images, 300 dpi, average letter text). Our OCR engine is optimized for 300 dpi images, images at a lower or higher resolution may affect OCR speed and/or quality.

The PDF process includes the OCR process mentioned above when OCR data is being included in the PDF file. PDF images with included OCR will achieve approximately the same pages per hour as mentioned above. PDF files created without OCR will be created on the average of 4000 images an hour.

The DocuLex endorsement process creates a small border below the bottom edge of the image and places the endorsement into this border. The endorsement process will create around 4000 endorsed images per hour.

Why is inserting a scanned page slow?

The insertion process in DocuLex software also involves a renumbering process. In a large batch, many pages may have to be renumbered in order for the insertion to take place. In some cases, this will cause the program to appear to ‘freeze’ while performing the renumbering process. It is best not to end task on the program while the renumbering process is being performed, for database corruptions may result.

In cases where a user is experiencing this effect during an insert, DocuLex Support recommends that the user make a backup of their tables before performing insertions into the batch.

What is Blank Page Removal, how do I use it?

Blank page removal allows the user to scan a mixture of simplex and duplex documents, and have the images removed that do not contain any useful text data (for instance, the back side of a simplex page). This process happens during scan time in DocuLex software.

In order to use blank page removal, open the DocuLex scanning product (Professional or Office┬áCapture) and click the ‘lock button’ in the top left hand corner of the Autoscan window. This will open the Main Autoscan Server window. On the Main Autoscan server menu, choose Commands\Image Processing settings and then select the Blank Page Removal tab.

Setting the back side of the page to active will remove the blank back side of simplex pages while scanning in duplex mode. On some scanning devices it may be necessary to change the margins in the Blank Page Removal settings so that the software does not include pages that are scanned with the edges of the paper showing.

With some TWAIN drivers, it is possible (and recommended) to allow the manufacturer’s TWAIN datasource to perform Blank Page Removal. Please see the documentation of your TWAIN-based scanner to see if this option is available with your scanner.

Can I use color paper for my Bookmark or Mark Detection pages?

Yes. We recommend the usage of lighter colored paper, pastels are preferred. A good method to test if a paper will work for mark detection is to scan a few sheets of blank paper in the color that is desired. If the scans are created as pure white, the color paper should work as well as white paper.

I keep receiving the error ‘scanner out of paper’, yet there is paper in my scanner?

The most common cause of a ‘Scanner out of paper’ error is a paper jam in the scanner. Double check to make sure that nothing is blocking the movement of the scanner, and look for loose items (staples, paper corners, etc) inside the scanner. Also, regular servicing of a production scanner by a professional is highly recommended.

If the error is not being caused by a paper jam, the error can sometimes be caused by the SCSI cables becoming loose on the scanner. We recommend unplugging both ends of the SCSI cable and refreshing the device manager of the operating system so that the scanner no longer shows up as an imaging device, then reattaching the scanner and refreshing the device manager so that the device is found again.

A final alternative is to close the DocuLex product and clear out the DocuLex *.ini file for Autoscan (SCSIAutoscan.ini or TWNAutoscan.ini) from the Windows or WinNT folder. To clear the *.ini file, open it with Notepad and delete the contents of the file. For the Autoscan.ini, it is useful to leave the first two lines of the *.ini file, to prevent receiving the ‘scanner.dll not found’ error.

I am receiving a solid black line on all of my images, what is causing this?

Cleaning the ADF portion of a scanner will resolve this issue. It is generally cause by an obstruction on the platen glass in the ADF portion of the scanner.

Why aren’t my Bookmarks/Barcodes/Targets/Mark Detect Forms being read?

Check that a clean scan is being received from the scanner. If the forms are being saved as images in the document population the barcode itself is not being read, which generally is caused by poor image quality. Open the created image with an image viewer (such as the default imaging program in Windows) and zoom in on the barcode portion of the form. Things to look for include excessive stippling (white dots) in the dark areas of the barcode (caused by scanner settings), black lines running through the barcode (caused by a dirty scanner), and white lines running through the barcode (caused by a bad CCD in the scanner).

Recommendations for Mark Detect forms:

  • They must be printed on a Laser printer using a Windows print driver designed for that particular printer. We find users have more success with PCL drivers.
  • Users tend to have better success when printing at 300 DPI and scanning at anywhere from 200 – 300 dpi
  • Use heavy duty paper for your mark forms (try a 24lb or 60lb paper weight). We also see users using light colored paper have better success.
  • We suggest if difficulties are encountered, use Large Check boxes and a large permanent ink marker to mark the marks on the form (Pencil is not recommended).
  • Users find that they have more success if the scanner is maintained regularly.
  • Be sure not to move the default elements of the Mark detect form (Barcode, registration marks, etc) from their default locations.
  • Make sure that after altering the Mark Detect form that the job profile is updated on the necessary batches.
  • Make sure that there is an event in the Global events as follows (the following example assumes scanning of a MARK.frx form). Set the Event type = Barcode, the Name =MARK, the Action = Evaluate, and the Parameter = mark.frx. Remember to update the job profile of batches after any changes.

Recommendations for Bookmarks/Barcodes/Targets:

  • They must be printed on a Laser printer using a Windows print driver designed for that particular printer. We find users have more success with PCL drivers.
  • Users tend to have better success when printing at 300 DPI and scanning at anywhere from 200 – 300 dpi
  • Use heavy duty paper for your mark forms (try a 24lb or 60lb paper weight). We also see users using light colored paper have better success.
  • Users find that they have more success if they clean the scanner regularly.

Factors for scanners:

  • Please make sure that you are scanning at 200-300 DPI.
  • The contrast, brightness, and threshold settings are very important. A simple change in one or all of these can cause the success or failure of barcode or mark detection.

All of my scan buttons are grayed out. Why can’t I scan?

This is generally caused by the Dongle/Crypto box or scanner not being detected. If an error is received that the Dongle/Crypto box is not found or the count is at 0, there are several things you can try:

  • Verify that the Dongle/Crypto box is attached to the parallel port or USB port. Make sure that the Professional Capture program is closed when removing or attaching the Dongle/Crypto box.
  • Install the drivers for the Dongle/Crypto box which can be download from our Dongle/Crypto box provider Marx at http://www.cryptotech.com/

If the scanner is not being detected try the following steps:

  • Verify┬áthat the scanner is turned on.
  • Verify┬áthat the scanner’s manufacturer driver is installed.
  • Power cycle the scanner and relaunch Professional or Office Capture.


Autoscan is running but the display window is missing. What can I do to get it back?

When the Main Autoscan Server Menu does not appear, it is usually hidden behind the display window. If you drag the display window to one side, you may find it. If not, we recommend trying the following:

  • Close all of your programs
  • Open SCSIAutoscan.ini or TWNAutoscan.ini file in the c:\Windows or c:\WinNT folder
  • Find the following lines and make sure yours match the ones below:

This will re-set the default location of the Autoscan Server back to a visible area of the screen.

When I open my batch I get an error, what should I do?

The DocuLex Batch repair utility will correct a number of known errors, such as:

  • Error #114

The DocuLex Batch Repair Utility (dclxrepr.exe) is installed along with Professional Capture, or can be downloaded from our Downloads Page. Use the following steps to correctly repair a damaged batch:

  • Close all programs on your computer, and then make a complete backup of your batch.
  • Run the DocuLex Batch Repair utility (dclxrepr.exe).
  • Select the batch you are attempting to repair.
  • Wait for the message box saying, ‘Rebuild Complete Press A Key.’

The batch should now successfully open in the DocuLex software.

Why aren’t my coding sheets read when I import files?

Coding sheets are not read while importing, they are only read while images are being scanned. You can ‘scan’ existing group IV tiff images into DocuLex software using the DocuLex Filelist driver.

I am using a TWAIN interface and having a problem. How can I correct the issue.

Most common TWAIN problems can be resolved by scanning using the TWAIN interface. Select the lock in the top left hand corner of the Autoscan Window and then select TWAIN > Acquire Via TWAIN Interface from the Main Autoscan Menu.

When you begin scanning, the manufacturer’s TWAIN dialog will appear, allowing you to make changes to the color, dpi, etc.

Get in Touch With Us!
Our Partners
2165 Technology Drive
Schenectady, NY 12308
Phone: 1-888-DOC-STAR