DUNORD'S I-20xx and I-30xx Families of Scanner Interfaces
April 30, 1997
Copyright Dunord Technologies, Inc. , 1994, 1995, 1996
--------------------------------------------------------------------------
TABLE OF CONTENTS
Introduction
Version Notes
Access to Dunord's BBS
Internet and Compuserve Access
Dunord's Windows drivers
DUNORD's PCI drivers for I-30xx PCI boards
Dunord's DOS driver
Windows driver installation (including Vscand.386 and vscand.vxd)
More than 16 Mb of memory with I-2000 or I-2500/I-2505
I-20xx EISA boards special parameters
Win95 installation complement
ISIS driver
Standard ISIS installation procedure
Supported ISIS software
Calera M Series Professional (MPRO)
Filemagic
OMNIPAGE Version 5
OMNIPAGE Version 7
TEXTBRIDGE
TYPEREADER
WATERMARK
WORDSCAN - Important note
WORDSCAN 1.1
WORDSCAN and WORDSCAN PLUS 2.0
WORDSCAN PLUS 3.0
TWAIN driver
Standard TWAIN installation procedure
Supported TWAIN software
TMS driver
PROBLEMS AND TIPS
Multiple copies of drivers
Machines with more than 16 Megs of RAM
ATI and ORCHID display controllers
Cornerstone High-definition monitor
Adaptec 1541 and 1542 SCSI controllers
Pentium (AST)
PS/1 with SCSI
QEMM and 386MAX
Weak Power Supply
Repeating black vertical bars in scanned image
Conflict with a network card
STRING NOT FOUND with ISIS
Legal size document support on flatbed for Fujitsu 3093
Users of IBM DOS 6.1
FUJITSU 3099 hopper time-out
--------------------------------------------------------------------------
Introduction
This document contains additional information to the Interface User's
Guide that caame with your scanner interface card. It covers installation
procedure for certain products, as well as an up to date list on known
problems and fixes.
--------------------------------------------------------------------------
Version Notes
The most recent version of Dunord's drivers are as follows.
I2000.EXE
The current version of I2000.EXE is 2.0. Versions 1.08 and 1.07 are
still available upon request.
DUNORD.DLL and DUNKERN.DLL
DUNORD.DLL and DUNKERN.DLL most recent versions are 2.08.
ISIS drivers
The current version of the ISIS driver is 1.8.
--------------------------------------------------------------------------
Access to Dunord’s BBS
Dunord maintains on its BBS a complete set of up-to-date drivers, as well
as documentation (like this document) in electronic format. The telephone
number to reach our BBS is :
(514) 284-1040
Our BBS is open 24 hours a day to anyone who asks for a user ID.
It is unattended between 6 PM and 8 AM Eastern Time.
Please call or send a FAX to get yourself a user ID and Password.
Please do not leave messages on our BBS. All communications should be done
through an uploaded file after calling or faxing us to inform us that you
are sending a file.
The maximum modem speed supported is 14.4 kbs and the protocol is 8N1.
Upon reaching the BBS, login with your first name, family name and a
password. Password is up to any 8 characters given by you the SYSOP
upon request by phone or FAX. Once you have
logged in, you will be able to list files available for transfer, select
the required files and transfer them to your machine.
--------------------------------------------------------------------------
Internet and Compuserve Access
dunord can be reached by e-mail on Internet and Compuserve.
Internet address is dunord@dunord.com
Our WEB page is at http://www.dunord.com
Compuserve address is 75027,3360
Both can be used for e-mail. If a file has to be sent, it has to be
attached to a mail message on Internet. It can be sent as a file
on Compuserve.
On request by email, dunord may send a file either to an FTP site,
or attached to an email message through Internet.
Files can be sent directly on Compuserve.
--------------------------------------------------------------------------
DUNORD's Windows driver
Dunord's Windows drivers consist of seven files for
Windows (DUNORD.DLL, DUNKERN.DLL, vscand.386(win 3.1) or vscand.vxd
(Win95), DUNDLG.DLL, DUNDLG.HLP, CTL3DV2.DLL and DUNORD.INI).
The installation procedure for these drivers is described in your
Interface User's. This User's Guide is shipped with every scanner
interface. If you have misplaced yours, an electronic copy can be
obtained from our BBS. Consult also the next section for up-to-date
information on the Windows driver.
--------------------------------------------------------------------------
DUNORD's PCI drivers for I-30xx PCI boards
(Windows 3.x and Windows 95 only )
Insert the PCI board in the PC PCI slot (preferably the first slot).
Insert the cable to the board and to the scanner.
Power up the PC and then the scanner.
*If you are running Windows 95 it may report on bootup
that a new "PCI BRIDGE" was found.
It will give you the option of installing a driver.
Select the option and select the DUNORD.INF File on the diskette or
on your hard disk ( just specify the path ).
This file will not install drivers but will make our board
known to windows 95.
Copy all the contents of the Dll directory into the windows\system directory.
Copy the dunord.ini to the windows directory. If you are not using com port 1 edit the
dunord.ini and specify which com port you are using.
Run the S2F.EXE application.
If the application reports the error "Cannot communicate with scanner 2"
there is a problem with one of the following:
-com port
-Cable
-scanner communication
If the application reports the error "Cannot communicate with scanner 48"
The card is not recognized and you should run the PCITEST program
and get in touch with Technical Support @ -- (514)284-3123 (voice)
(514)284-7433 (fax)
TechSup@dunord.com (internet)
Once board is installed, proceed with installing other applications as explained below.
PCI support is provided by using and extra dll, dunpci.dll. This dll is added to dunord.dll
automatically when a PCI board is used. This file is distributed only
on the diskette or by private email. It is being adjusted for a final production release and
will be made available on the WEB and BBS when final release is acheived.
--------------------------------------------------------------------------
DUNORD'S DOS driver
A DOS TSR ( I2000.exe is still provided on the diskette for older type of
applications. Unless you are specificaly asked to use that TSR, it should
not be used. It is distributed only for convenience and for test purposes.
Note that if you still load the DOS TSR and your application runs
exclusively under Windows, DUNORD.DLL will detect if I2000.EXE
is loaded and will then use the memory reserved by the DOS TSR.
--------------------------------------------------------------------------
Windows driver installation
**************************************************************************
If you already have an older version installed, you must remove some files
manually. These new drivers use an enhance memory management feature,
compatible with both Win 3.1 and Win 95. Vi2000.386 must be removed.
Please edit system.ini and remove the line that references vi2000.386.
File Vi2000.386 should also be removed from your Windows/system directory.
If you are upgrading, please make a backup copy of dunord.ini. It has all
the working settings and it should be kept. A backup to diskette is the
best way to make sure it will not be destroyed. Except for dunord.ini, you
may now remove all dun*.* files, ( they should all be in windows\system ).
**************************************************************************
To install Dunord's Windows drivers, copy DUNORD.DLL, vscand.386 or
vscand.vxd ( .386 for Windows 3.1 and .vxd for Win 95), DUNDLG.DLL,
DUNDLG.HLP, CTL3DV2.DLL and DUNKERN.DLL to your \WINDOWS\SYSTEM directory.
Copy also DUNORD.INI to your \WINDOWS directory. Update this last file to
reflect the operating environment of your computer. Refer to the Interface
User's Guide for additional information.
For Windows 3.1 & 3.11,
Add device = vscand.386 in the [386enh] section.
For Windows 95,
Add device = vscand.vxd in the [386enh] section.
***************************************************************
!!!! Make sure only one of vscand.386 (Win 3.11 or WFW 3.11 )
or vscand.vxd (Win 95) is used
***************************************************************
--------------------------------------------------------------------------
*** More than 16 Mb of memory with I-2000 or I-2500/I-2505
If you have more than 16 Mb of memory and you use an I-2000 board (Fujitsu)
or an I-250x(Panasonic), you may sometimes get a message that tells you it
cannot get find memory in the first 16Mb. These boards are AT type and
thus cannot address memory outside the first 16 Mb. You must restrict the
system to the first 16Mb
To solve this memory allocation problem, please do the following:
add a section named [Dunord] in system.ini
add a line
PrivateMemory=xxxx
in that section
where xxxx is the number of 1K blocks to use in the first 16 Mb of memory.
This memory will be set aside in priority to Dunord programs. It will not
limit your scan but if your scan is greater than this value, this block
will not be used, and a new one will be used instead, if memory can be
found.
Save the file and restart Windows for the modification to take effect.
New: Jan 6, 1997:
Vscand now supports up to 6 Mb of private memory, allowing a scan of
Legal @ 600 dpi on the new Fujitsu 3093DE.
When allowing Private memory, one should allow only the required
memory for the largest scan. Otherwise memory is wasted. Here is
the formula to compute the number of blocks to reserve:
using inches: (width * length * resolution * resolution / 8 / 1024) +2
N.B. normal width for a scanner is 8.64 "
with this formula, a Letter size page @ 200 dpi is
(8.64 * 11 * 200 * 200 / 8 / 1024 )+2 = 466 blocks
at 400 dpi:
(8.64 * 11 * 400 * 400 / 8 / 1024 )+2 = 1858 blocks
at 600 dpi:
(8.64 * 11 * 600 * 600 / 8 / 1024 )+2 = 4178 blocks
Legal at 600 dpi:
(8.64 * 14 * 600 * 600 / 8 / 1024 )+2 = 5317 blocks
using pixels: (width * length / 8 / 1024 ) + 2
N.B. normal width for a scanner is 1728 pixels @ 200 dpi
The value of this private memory depends on document size and scan
resolution. The following table gives the value of mmmm for some
frequently used combinations:
Document resolution mmmm
LETTER SIZE 200dpi 475
LETTER SIZE 300 1100
LETTER SIZE 400 1900
LEGAL SIZE 200 610
LEGAL SIZE 300 1400
LEGAL SIZE 400 2400
DOUBLE LETTER 200 1000
DOUBLE LETTER 300 2200
DOUBLE LETTER 400 3900
A3 200 1000
A3 300 2200
A3 400 3900
--------------------------------------------------------------------------
*** I-20xx EISA boards special parameters
For I-20xx EISA type boards, in the same [Dunord] section add 2 lines:
HardwareBufferBoundary=64
HardwareBufferSize=128
For Duplex TwinStream scanners, set
HardwareBufferSize=256
Save the file and restart Windows for the modification to take effect.
**************************************************************************
*** Win95 installation complement
To make sure that the resources used are identified to the dunord board,
do the following:
In Control Panel, choose System, then Device Manager. Then, Click
Computer and open the Reserve Ressources TAB.
Add a ressource reservation for the 3 following types:
Set the values to the ones that will be used in the dunord.ini
IO_addr ( I-2000 uses 4 values, 3xC - 3xF,
x being the value of the switches i.e. 0-f)
( I-250x uses 8 values, 3x0-3x7
x being the table value for the switch setting )
EISA and PCI boards need not to worry about this setting.
DMA 5, 6 or 7
IRQ 5, 11 or 12 for AT type boards ( I-2000 and I-250x )
or 10,11,12 or 15 for all other boards.
This will make sure that no other device will be able to use the same
settings.
**************************************************************************
ISIS driver
**************************************************************************
Standard ISIS Installation Procedure
Dunord ISIS driver is now certified. In a few months, it should be part
of the installation procedure of most ISIS applications. If it is not
yet seen directly by the application, follow the directions given below:
The driver floppy supplied with the interface, as well as file
DUNISIS.ZIP from our BBS, contain the following files:
README.TXT This file
DUNISIS.PXW The ISIS driver. In directory DUNISIS
The current relase of DUNISIS does not require DUNDVI.EXE or VBRUN300.DLL
that used to be required with former versions.
To install the ISIS driver, do the following unless otherwise specified in
the installation procedure of the application you will use.
ISIS driver installation:
Install DUNORD Windows driver according to procedure.
Copy DUNISIS.PXW to your WINDOWS\SYSTEM directory. If you have an older
version of this file, make sure that the most recent is
in your WINDOWS\SYSTEM directory.
On newer relases of ISIS, a Windows\Pixtran has been created and
contains all *.PXW files. If it is the case in your installation, copy
DUNISIS.PXW in this directory (windows\pixtran) instead of
Windows\system
Some ISIS application may require special installation procedures.
Secial notes for ISIS:
***Normally, under ISIS, applications that require a dialog box will get
dunord's dialogs, same as S2F.
If you want to use the simpler dialogs from ISIS, create a section
named DUNISIS in dunord.ini and add the line ISIS_DVI = 1
The section should look like this:
[DUNISIS]
ISIS_DVI=1 ; set to 0 to use dunord's std dialogs
***You may also use this section to change the default resolution or
document size used by ISIS. By default, ISIS uses Legal document size
at 300 dpi.
You may set the default to one of the supported sizes or resolution.
Add the following lines in the [Dunisis] section of dunord.ini
ISIS_Document=7 ;letter other values are:
15-legal, 3-A3 5-B5 6-Double Letter
ISIS_Resolution=200 ;can be any resolution supported by scanner/memory
***When a duplex scanner is attached and the application does not handle
duplex scanning, it is possible to trick the system by scanning duplex.
Two lines must be added to the [dunisis] section:
Duplex_Documents = 1
Duplex_Default = 1
Duplex_Documents tells the system to create new document sizes which
are 2 sided versions of regular docuemnt sizes. Hence, you will see
Letter and Letter Duplex, A4 and A4 duplex, and so on. Selecting the
duplex version will set the scanner in duplex mode. The first scan
will return the front, the next scan the back, etc.
Duplex default tells the system to set the default document size
to duplex or not. One could set Duplex_Documents to 1, asking for
duplex capabilities, but setting duplex default to 0, asking
for single sided default setting. setting duplex_default default to 1
would ask for a duplex default setting.
These settings work only when a duplex scanner is connected:
Panasonic KV-SP505, Bell+Howell 6338 or Fujitsu 3099.
**************************************************************************
Supported ISIS Software
You will find in the following list PC imaging software that support ISIS
drivers. Our apologies to software developpers whose product is not inclu-
ded in the list. Please contact us to let us know about you product and
it will be included in future updates of the list.
Product name Manufacturer Installation procedure
AutoData PRO AutoData
Axxis Axxis
PaperKeyboard Datacap
File Magic Plus Westbrook Technologies X
M Series (MPro) Calera X
OmniPage Ver. 5 Caere X
Paper Bridge Teamworks Technologies
Recollect Mindworks
Teleform Ver. 3 Cardiff
Textbridge Xerox X
Type Reader Expervision X
Watermark ISIS X
Wordscan 1.0 Calera/Caere X
Wordscan 2.0 Calera/Caere X
Wordscan 3.0 Calera/Caere X
Zymage Zylab
+ many more
**************************************************************************
Installation Procedure for Calera M Series Professional (MPRO)
Install the ISIS drivers as stated above, but copy DUNISIS.PXW to
the MPRO directory.
If you are planning to use other ISIS programs, also copy DUNISIS.PXW
to your WINDOWS\SYSTEM directory.
**************************************************************************
Install procedure for FileMagic:
Follow the ISIS installation procedure. Then:
Install FileMagic.
Run FileMagic.
From the main menu,
Choose SETUP / SCANNER SETTINGS
Choose "DUNORD I20x0 Scanner Interface"
Click OK
You may now scan with Filemagic.
**************************************************************************
Installation Procedure for OmniPage Version 5
Install OmniPage
Install DUNORD.DLL, DUNKERN.DLL and DUNORD.INI according to the procedure.
Copy DUNISIS.PXW to the OmniPage directory.
Edit the file SCANMGR.LST in the OmniPage directory:
Find the highest ID used. ATTENTION! There is often a comment line at
the beginning of this file which indicates the Highest ID used. Use
this number only as an indicator, since it could be in error. Always
check in the list of devices to find the highest device number used.
Add a line at the end of the list of scanners in the format:
id | DUNORD_I20x0_Scanner_Interface | SCMGR07.EXE | IDUNISIS
where id is the highest ID number +1
n.b. spaces are not important, but underscores are,
each column is separated by the vertical bar (pipe char.).
Save the file , start Omnipage and select the scanner. Choose
DUNORD I20x0 Scanner Interface.
This driver will work with all Dunord boards and any scanner
connected to it.
**************************************************************************
Installation Procedure for OmniPage Version 7
Install OmniPage and Scan Manager
*** When Installing Scan Manager Choose the "Scanjet Plus w/ ISIS" scanner ***
Install DUNORD.DLL, DUNKERN.DLL and DUNORD.INI according to the procedure.
Copy DUNISIS.PXW to the Windows\Pixtran directory.
Befor running OmniPage Run the Scan Manager and do the following steps:
- Choose browse on the Scanner Setup window
- Enter "Dunord Scanner Interface" for Scanner
- Select" browse" to find the DUNISIS.PXW file in the windows\pixtran directory
- If it asks you to replace The driver say Yes
- Press "ok"
- select" add" on the Scanner Setup window
- It will ask you for the directory of the scan Manager setup.exe file
- A list will show up once it has found the setup.exe
- "Dunord Scanner Interface" will be the last one on the list
Select it and select the install button
- Under Installed scanners you will have dunord and scanjet select dunord and press
the "select the set default scanner"
-you are now ready to start Omnipage 7
This driver will work with all Dunord boards and any scanner
connected to it.
**************************************************************************
Installation Procedure for TypeReader
Copy DUNISIS.pxw in the typereader directory
for TypeReader pro version 2, rename DUNISIS.PXW to DUNISIS.TRS
Add the following lines to SETSCAN.INI
[DUNISIS]
Setup=Yes
Change the [Scanner] section to:
[Scanner]
Driver=DUNISIS
**************************************************************************
Installation Procedure for TextBridge
Follow the ISIS installation procedure. Then:
Install TextBridge.
RUN TextBridge Scanner Setup.
Choose TYPE and Select ISIS
Choose FILE, Select SOURCE.
If you see the choice DUNORD I20x0 Scanner Interface, select it.
Otherwise, press ADD and when prompted for the A:\ drive, change the
prompt to C:\windows\system and press Enter.
Select DUNORD I20x0 Scanner Interface. This will copy DUNISIS.PXW
to the TextBridge directory and setup the .INI files.
Choose FILE, ACQUIRE to test the scanner.
N.B.
You should delete DUNISIS.PXW from the TextBridge directory. By
doing so, only one copy of the driver will be residing on your
system, (in Windows\system directory), and it will be available to
all ISIS applications. Updates to the driver will then automati-
cally be applied to all applications and disk space will also be
saved.
**************************************************************************
Installation Procedure for Watermark
Follow the ISIS installation procedure. Then:
Install Watermark.
Start Watermark and select SCAN / SELECT SCANNER from the menu.
Choose the scanner DUNORD I20x0 Interface.
Set the scanner settings by choosing SCAN / SCANNER SETTINGS and scan by
choosing SCAN / SCAN
**************************************************************************
WORDSCAN - Important note
*********************************************************
* IMPORTANT NOTE for WORDSCAN USERS !!!! *
* *
* WORDSCAN VERSION 1.1 WILL NOT HANDLE MORE THAN *
* 4096 PIXELS IN WIDTH AND 4096 PIXELS IN LENGTH *
* *
* WORDSCAN VERSION 2.0 AND 3.0 WILL NOT HANDLE MORE *
* THAN 3400 PIXELS IN WIDTH AND 4096 PIXELS IN LENGTH *
* *
* This means than if you select Letter @ 400 *
* it will fail and give you errors. *
* *
* The default is Legal @ 300 which is longer than 4096 *
* (it is 4200 pixels) but WordScan will cut it. *
* Larger sizes may produce crashes. *
* *
* Dunord's drivers can limit size for CALERA *
* *
* In DUNORD.INI, add the following 2 lines: *
* *
* [Calera] *
* Limit_Size=1 *
* *
* When Limit_Size is not zero, DUNISIS will make sure *
* that no line will be wider than 3400 pixels *
* and no document will have more than 4096 pixels *
* *
* If you are using other applications that need *
* DUNISIS.PXW, you should have 2 copies of DUNORD.INI *
* *
* The main DUNORD.INI should be in Windows and should *
* not contain the above 2 lines. *
* *
* The other copy of DUNORD.INI should be in the Wordscan*
* directory and should contain the above 2 lines. *
* When Wordscan is started, it will read the ini *
* file in its directory. All other application will *
* read it from Windows. If both directories are in the *
* path, make sure Windows is to the left of Wordscan *
**************************************************************************
Installation Procedure for WORDSCAN 1.1
Install DUNORD.DLL, DUNKERN.DLL and DUNORD.INI according to the procedure.
Obtain special driver DUNISIS.WDR from our BBS in file DUNISIS.ZIP.
Install Wordscan 1.1
Copy DUNISIS.PXW to CALERA\BIN directory
Copy CALERA\DUNISIS.WDR obtained from our BBS
Copy CALERA\LIB\UUI\SYSTEM.DAT to SYSTEM.DA0 (to keep old copy)
Modify CALERA\LIB\UUI\SYSTEM.DAT
Find the line that starts with CDP= and ends with ,0+xxxxxx
where xxxxxx is the chosen driver
Replace xxxxxx with DUNISIS (the line will now end with ,0+DUNISIS)
Save
Copy WINDOWS\SETSCAN.INI to WINDOWS\SETSCAN.INO (to keep old copy)
Modify WINDOWS\SETSCAN.INI
Add following 2 lines at the end of the file
[DUNISIS]
Setup=Yes
Under the scanner heading : [Scanner], change
Driver=FUJDUN to Driver=DUNISIS
Save
WORDSCAN in now ready for operation.
**************************************************************************
Installation Procedure for WordScan and WordScan Plus v2.0 .
Follow the ISIS installation procedure. Then:
Install WordScan and select a Canon scanner with feeder.
Delete file SETSCAN.INI if it is present in the Windows directory.
Edit WORDSCAN.INI that was created in the your \WINDOWS directory.
Find the line that starts with CDP= and ends with ,0+xxxxxx
where xxxxxx is the chosen driver
Replace xxxxxx with DUNISIS (the line will now end with ,0+DUNISIS)
Save
Start WORDSCAN and do a scan.
If WORDSCAN displays and ERROR 4700, verify that parameters are set
properly in DUNORD.INI. Verify also that all drivers and files have been
put in the proper directory and that you do not have different versions
of the same file on your computer (read section on Multiple copies of
drivers later in this document).
**************************************************************************
Installation Procedure for WordScan Plus v3.0 .
Follow the ISIS installation procedure. Then:
Install WordScan and select a Canon scanner with feeder.
Delete file SETSCAN.INI if it is present in the Windows directory.
Delete any copies of DUNORD.DLL, DUNKERN.DLL and DUNISIS.PXW
in the Wordscan 3.0 directory, usually WORDSCAN, or subdirectory.
Before starting Wordscan,
Edit file WS30.INI that was created in your \WINDOWS directory.
Change the following lines in the [scan] section to:
[Scan]
Driver=DUNISIS.pxw
Name=DUNORD Interface
Save
Start WORDSCAN and do a scan.
If no SCANNER POSSIBILITY appears under ACQUIRE, verify that parameters
are set properly in DUNORD.INI.
--------------------------------------------------------------------------
TWAIN driver
**************************************************************************
Standard TWAIN Installation Procedure
Dunord's TWAIN drivers consist of two files working in team with Dunord's
own drivers set. These files are :
I2KTWAIN.DS
TWAIN.DLL
that are included in the TWAIN directory of the driver floppy shipped with
your Scanner Interface board.
Installation procedure for Dunord's TWAIN drivers.
First remove any existing version of I2KTWAIN.DS and TWAIN.DLL
Install DUNORD Windows driver according to procedure.
Create a subdirectory of your windows directory, (usually \WINDOWS),
called TWAIN. Create a subdirectory of \WINDOWS\TWAIN called DUNORD. Copy
the I2KTWAIN.DS file to that last subdirectory.
Copy the TWAIN.DLL file to your Windows directory, usually \WINDOWS.
The following diagram shows the diagram structure and the location of the
files.
C:\WINDOWS-------|---C:\WINDOWS\TWAIN---|---C:\WINDOWS\TWAIN\DUNORD
- dunord.ini | | - i2ktwain.ds
- twain.dll |
|---C:\WINDOWS\SYSTEM
- dunord.dll
- dunkern.dll
- dundlg.hlp
- dundlg.dll
- ctl3dv2.dll
- vscand.386 or .vbx
Operation:
Start Windows and run the TWAIN enabled application. If the
application doesn't have the 'SCAN' menu item enabled it can't
find TWAIN.DLL, verify that it properly located.
The application should also have a 'Select Source' menu item which
will display a list of TWAIN drivers. Choose "Dunord I2000" from
the list. If you fail to get this driver you haven't set up the
directories correctly.
Then select 'Acquire' from the application menu. The DUNORD user
interface dialog box will appear. When all options are set choose
'Accept' and the scanner will begin scanning.
Dunord's TWAIN driver currently supports only NATIVE memory transfers.
Please read TWAIN.TXT in the TWAIN directory of the distribution diskette
**************************************************************************
Supported TWAIN Software
You will find in the following list PC imaging software that support TWAIN
drivers. Our apologies to software developpers whose product is not inclu-
ded in the list. Please contact us to let us know about your product and
it will be included in future updates of the list.
Product name Manufacturer
Corel Corel
ELA Office Com Com Systems
Lotus Notes Document Imaging Lotus Corporation
PageKeeper Caere
OmniPage Pro Caere
ScanW Nexys
Watermark Watermark
WinFax Delrina
--------------------------------------------------------------------------
TMS driver
Dunord's TMS driver is contained in file TMSDUN.DRV. This file is normally
supplied by your TMS application supplier. However, should it be lost or
misplaced, it can be obtained from Dunord's BBS.
Installation instructions will be supplied with your TMS application.
--------------------------------------------------------------------------
PROBLEMS
**************************************************************************
Multiple copies of drivers
One of the common source of problem encountered when installing a Dunord
Scanner Interface card is multiple copies on your computer of the same
file at different revision levels.
Dunord's drivers consist of a set of programs that must exchange commands
and information with each others. To be able to do this in a coherent
fashion, the programs must be at revision levels compatible with each
others. All programs contained in the driver floppy or obtained at the
same time from Dunord's BBS are compatible with each other.
Some symptoms of this problem are the following:
getting weird messages from your application or from the drivers;
Windows is crashing;
Windows is giving error messages like General Protection Failure.
Use the File Manager FIND function, or your preferred search utility, to
identify multiple versions of programs or INI files, and delete all older
versions of these files. If you must maintain two copies of the same file
in your machine, make sure that they are identical and that they are
compatible with other Dunord's programs.
**************************************************************************
Machines with more than 16 Megs of RAM
If you have a machine with more than 16 Mb of memory and an I-2000 or
I-2500/I-2505 You might get a message from Windows telling you that there
is not enough memory available. This situation comes about ecause AT bus
type devices cannot access memory above 16 Megs of RAM.
See above section "More than 16 Mb of memory with I-2000 or I-2500/I-2505"
in Windows Driver Installation for a fix for this problem.
**************************************************************************
ATI and ORCHID video display controllers and I2000.EXE DOS TSR
ATI and ORCHID video display controllers use the same software interrupt
as the one specified by the default value of the I2000.EXE DOS TSR. You
can change the default value by using the v= parameter on the I2000.EXE
command line. You will have to try different value until you find one
that does not conflict with any other equipment on your machine.
Be aware that the old Scan2tif program will not work when the v parameter
is modified.
This problem exists only with the DOS TSR. It will not be present if you
use the Windows drivers without loading the I2000.EXE program.
**************************************************************************
Cornerstone High-definition monitor
Testscan will produce an Illegal Function Call when used with a
Cornerstone High-definition monitor.
One solution is to use a different monitor/adapter combination. Some
drivers will allow TESTSCAN to run in a DOS box under Windows, but not
in native DOS.
**************************************************************************
ADAPTEC 1541 and 1542 SCSI controller
If you have an Adaptec 1541 or 1542 SCSI controller installed on your
machine, add the following 2 parameters to the DEVICE=ASPI4DOS command
line located your CONFIG.SYS:
/F12 /N4
Failure to do so might result in scanned images with missing lines.
**************************************************************************
Pentium (AST) with SCSI controller
When installing a I-2000 Scanner Interface board on an AST Pentium machine
with a SCSI controller, it is not possible to change the DMA channel used
by the board to 6 or 7. You must let the I-2000 use DMA channel 5 and
change the DMA channel used by the SCSI controller to another value.
**************************************************************************
IBM PS/1 with SCSI controller
IBM PS/1 machines with SCSI controller frequently use 2 DMA channels. You
must instruct the I-2000 to use DMA channel 7.
**************************************************************************
QEMM or 386MAX
Intermittent problems have been experienced by users of QEMM and 386MAX.
Factors causing this problem may vary from the version of QEMM, software
installed, even the chip set.
To avoid any problem, use HIMEM.SYS and EMM386.EXE supplied with DOS or
Windows.
**************************************************************************
Weak Power Supply
On some low end clones, the power supply is not strong enough to provide
enough electric power to the I-2000 when it is located in a slot that is
distant from the power supply.
Move the I-2000 to a slot closer to the power supply or switch to another
machine.
**************************************************************************
Repeating black vertical bars in scanned image
If the bars are 8 pixels wide and repeat themselves every 16 pixels
(... 8 good pixels, 8 black pixels, 8 good pixels...), you most probably
have a conflict with a device that was not detected when the driver was
loaded. Try changing I/O address or dma channel to solve the problem.
If the bars are 1 pixel wide and repeat themselves every 8 pixels, the
probable cause is a faulty video cable. If you have another video cable,
try replacing the faulty cable to see if the problem disappears. Contact
your hardware supplier for instruction to obtain a replacement cable.
**************************************************************************
Conflict with a network card
Network cards can have DMA channel or I-O address that conflict with the
AT bus Interface cards. The procedure to solve these conflicts is
described in the User's Guide. Sometimes, however, the conflict is with
both type of resources. In that case, the simples thing to do is to flip
the two middle dip switches located on the top of the board, and to use
I-O address 36f (p= or IO_Addr=) and DMA channel 7.
**************************************************************************
STRING NOT FOUND with ISIS
This problem might happen when updating ISIS drivers.
Delete SETSCAN.INI from your Windows directory.
Delete DUNISIS.PXW that is sometimes found in PIXEL directory
Restart Windows.
**************************************************************************
Support of legal size document on flatbed for Fujitsu 3093
Although the Fujitsu 3093 does not support LEGAL size on the Flatbed,
DUNORD driver will allow a user to select LEGAL size from the flatbed.
This is to ensure compatibility with some software that do not distinguish
between ADF and Flatbed. If the ADF is malfunctionning, a software that
insists on legal will stop working. DUNORD driver will allow scanning
LEGAL from the flatbed but will return only the maximum number of lines
read by the flatbed at the chosen resolution (equivalent to A4 document
size).
**************************************************************************
Users of IBM DOS 6.1
Using HIMEM.SYS and EMM386.EXE from IBM DOS 6.1 can sometimes result in
scattered images or images with missing parts. Use HIMEM.SYS and
EMM386.EXE from WINDOWS.
**************************************************************************
How to change FUJITSU 3099 Hopper Time-out
The default value of the Hopper Time out on Fujitsu M3099 is sometimes
too short for some applications that take too long to request the next
scan. Lengthen the time by doing the following:
1. Power OFF scanner
2. Hold <MODE 2> and Power UP scanner
==> Scanner is now in CE Mode
3. Hit <MODE 1> until "TEST 09"
4. Hit <MODE 2> ==> "START" flashes
5. Hit <MODE 1> ==> "EEPROM" mode is selected
6. Hit <START> ==> Display shows EEPROM #00-00
7. Hit <Mode 2> ==> First 2 digits flash
8. Hit <Mode 1> until first 2 digits are "08"
9. Hit <Mode 2> ==> Third digit flashes
10. Hit <Mode 2> ==> Last digit flashes
11. Hit <Mode 1> until digit is set to proper value.
( a good value is : EEPROM #08-0F )
12. if third digit changed and must be reset:
Hit <Mode 2> until third digit flashes
Hit <Mode 1> until proper value is shown
13. Hit <Start> to save values
14. Hit <Stop> twice ==> Scanner goes back to "Warming up Now"
**************************************************************************
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.