Nuance omnipage direct 2 for windows User Manual
Operation Problems
Technical Information 47
Operation Problems
Direct works but operates slowly and frequently accesses the
hard disk drive.
hard disk drive.
As a Windows application, Direct is able to take advantage of the
Windows swap file when running low on memory. This may occur with a
minimally configured system (only 4MB of RAM), if memory has become
fragmented with use, or if other applications are running in the
background. When low memory conditions occur, Windows will use disk
space to simulate the RAM it does not have available. Disk access time is
much longer than RAM access time; the computer system will run much
slower when it has to use a swap file.
Windows swap file when running low on memory. This may occur with a
minimally configured system (only 4MB of RAM), if memory has become
fragmented with use, or if other applications are running in the
background. When low memory conditions occur, Windows will use disk
space to simulate the RAM it does not have available. Disk access time is
much longer than RAM access time; the computer system will run much
slower when it has to use a swap file.
A quick fix for memory fragmentation problems is to quit Direct and
Windows and reboot your system. This will clear any fragmentation of
memory that has occurred (until, of course, it happens again).
Windows and reboot your system. This will clear any fragmentation of
memory that has occurred (until, of course, it happens again).
Try closing any other applications that are running in the background.
This will usually free enough memory for Direct to operate without using
the swap file. If you regularly work with long, complex documents,
adding more RAM to your system would be the best solution.
This will usually free enough memory for Direct to operate without using
the swap file. If you regularly work with long, complex documents,
adding more RAM to your system would be the best solution.
For more information on optimizing your system and application
performance under Windows, refer to the Windows User's Guide.
performance under Windows, refer to the Windows User's Guide.
The scanner will begin to scan and stop. The entire system locks
up and you have to reboot your computer.
up and you have to reboot your computer.
You may have an interrupt conflict between your scanner and another
device. If you have a bus mouse and you usually do not use the mouse and
scanner at the same time, check the interrupt used by the scanner and
mouse for a possible conflict. The interrupt address typically used by some
network cards may cause the same problem.
device. If you have a bus mouse and you usually do not use the mouse and
scanner at the same time, check the interrupt used by the scanner and
mouse for a possible conflict. The interrupt address typically used by some
network cards may cause the same problem.
Images appear inverted (like negatives).
TWAIN scanners not 100% compliant with the TWAIN standard must
have correct entries in the scanmgr.ini file located in your Windows
directory. See “TWAIN Scanners Not Listed” on page 41.
have correct entries in the scanmgr.ini file located in your Windows
directory. See “TWAIN Scanners Not Listed” on page 41.
Your system hangs when you try to scan (TWAIN scanners only).
If you select Auto Intensity you must also select Grayscale as the scan mode
within the dialog box of your TWAIN data source. Also, TWAIN scanners
not 100% compliant with the TWAIN standard must have correct entries
in the scanmgr.ini file located in your Windows directory. See “TWAIN
Scanners Not Listed” on page 41.
within the dialog box of your TWAIN data source. Also, TWAIN scanners
not 100% compliant with the TWAIN standard must have correct entries
in the scanmgr.ini file located in your Windows directory. See “TWAIN
Scanners Not Listed” on page 41.