Frequently Asked Questions

DUNORD's Windows driver

Dunord's Windows driver consists of seven files:

• DUNORD.DLL
• DUNKERN.DLL
• VSCAND.386(win 3.1) or VSCAND.VXD (Win95)
• DUNDLG.DLL
• DUNDLG.HLP
• CTL3DV2.DLL
• 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. You can also get an electronic copy can also be obtained from this Web. Go to the Technical support page to obtain it.
Consult also the next paragraphs for late minute additions to the User's Guides

If you have an older version installed, you must manually remove some files that might be present.
Edit file SYSTEM.INI (using the Sysedit utility or a text editor) and remove the line that references vi2000.386. File Vi2000.386 should also be removed from your Windows/system directory.
If you are upgrading, 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 your WINDOWS\SYSTEM directory).

To install Dunord's Windows driver, copy files DUNORD.DLL, VSCAND.386 (Windows 3.1x)or VSCAND.VXD (Windows 95), DUNDLG.DLL, DUNDLG.HLP, CTL3DV2.DLL and DUNKERN.DLL to your \WINDOWS\SYSTEM directory.
Copy also DUNORD.INI to your \WINDOWS directory. Update it to reflect the operating environment of your computer. Refer to the Interface User's Guide for additional information.

Edit file SYSTEM.INI and add one of the following lines in section [386enh]
For Windows 3.1 & 3.11, add:
   device = vscand.386
For Windows 95, add
   device = vscand.vxd

!!!! Make sure only one of VSCAND.386 (Windows 3.1x ) or VSCAND.VXD (Windows 95) is used

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 thus tell your system to use memory in the first 16Mb.

To do this, do the following:
Add a section named [Dunord] in file SYSTEM.INI
In that section add the following line
   PrivateMemory=xxxx
where xxxx is the number of 1K blocks to use in the first 16 Mb of memory.
Save the file and restart Windows for the modification to take effect.

A block of memory of the size requested will be set aside in priority for Dunord driver. Memory requirements depend on scan resolution and document size. The following table states the number of 1k blocks required for various combinations.

If you try to scan a document/resolution combination that cannot be stored in the memory set aside for Dunord, the driver wil ask Windows for enough memory to store the whole image, making it very unlikely that you will be able to do as successful scan.
Versions of VSCAND prior to January 6, 1997 are able to request memory only up to 4 Mb. Later versions can request up to 6 Mb of memory to accomodate scanning legal documents at 600dpi on a Fujitsu M3093DE.

If you are using one of the I-20xx EISA type boards, add a section named [Dunord] in file SYSTEM.INI
In that section add the following 2 lines:
   HardwareBufferBoundary=64
   HardwareBufferSize=128
Save the file and restart Windows for the modification to take effect.

For Duplex TwinStream boards, set HardwareBufferSize to 256

To make sure that the resources used by the Dunord board are reserved by Windows and used by no other device, 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 DUNORD.INI

Insert the PCI board in one of the PC's PCI slot (preferably the first) and connect the cable to the board and to 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 this option and select the DUNORD.INF file from the diskette. 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 file to the windows directory.

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:

• Cable
• Scanner
• Scanner communication

Make sure that the scanner is on, that the cable is properly seated and attached to the right connectors.

If the application reports the error "Cannot communicate with scanner 48", the card ss not recognized. Run the PCITEST program to try to determine a possible cause.

In both cases, if the problem persist, and get in touch with Dunord Technical Support

A DOS TSR ( I2000.exe is still provided on the diskette for older type of applications. Unless you are specificaly required by your application to load 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 that I2000.EXE is loaded and use the memory reserved by the DOS TSR.

Dunord supplies an ISIS driver free of charge with all its boards. If it is not seen directly by the application, follow the directions given below to install it:
The driver floppy supplied with the interface and file DUNISIS.ZIP available from our Web site or BBS contain the following files:

To install the ISIS driver, do the following unless otherwise specified in the installation procedure of the application you will use.

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.

Using standard ISIS scanner settings dialog

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 it to 0 to use dunord's dialogs.

Changing default resolution

You may also use the DUNISIS section to change the default resolution or document size used by ISISwhich are Legal (81/2 x 14) at 300 dpi.
You can set the default to any of the supported sizes or resolution by addin 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

Forced Duplex scanning with ISIS

Some ISIS applications cannot handle duplex scanning. It is possible however to make them scan duplex when a duplex scanner is connected by adding the following two lines DUNISIS section:

   Duplex_Documents = 1
   Duplex_Default = 1

Duplex_Documents instructs the driver 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 side of the document, the next scan will return the back and so on.

Duplex default tells the driver to set the default document size to duplex or not. Setting Duplex_Default to 0 means that the default setting will be single side. Setting Duplex_Default default to 1 asks for duplex default setting. Duplex_Default is meaningful only when Duplex_Documents is set to 1.

These settings work only when a duplex scanner is connected: Bell+Howell 6338, Fujitsu 3099 or 3093D, Improvision's IS520, InoTec Scamax duplex and .Panasonic KV-SP505 or KV-SV55

.

You will find in the following list PC imaging software that support ISIS drivers. Our apologies to software developers 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.

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.

Follow the ISIS installation procedure. Then:

You may now scan with Filemagic.

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:

Save the file , start Omnipage and select the scanner. Choose

This installation will work with all Dunord boards and any scanner connected to it.

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.

Before running OmniPage Run the Scan Manager and do the following:

• 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 installation will work with all Dunord boards and any scanner connected to it.

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

Change the [Scanner] section to:

Follow the ISIS installation procedure. Then:

Install TextBridge.

RUN TextBridge Scanner Setup.

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.

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

IMPORTANT NOTE for WORDSCAN USERS !!!!

Dunord's drivers can limit size for CALERA: in DUNORD.INI, add the following 2 lines:

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

Install DUNORD.DLL, DUNKERN.DLL and DUNORD.INI according to the procedure. Obtain special driver DUNISIS.WDR from our BBS or our Web site in file DUNISIS.ZIP.

Install Wordscan 1.1

Copy DUNISIS.PXW to CALERA\BIN directory
Copy CALERA\DUNISIS.WDR obtained from our BBS or Web site
Copy CALERA\LIB\UUI\SYSTEM.DAT to SYSTEM.DA0 (to keep old copy)

Modify CALERA\LIB\UUI\SYSTEM.DAT

Copy WINDOWS\SETSCAN.INI to WINDOWS\SETSCAN.INO (to keep old copy)

Modify WINDOWS\SETSCAN.INI by adding the following 2 lines at the end of the file

Under the scanner heading : [Scanner], change

WORDSCAN in now ready for operation.

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.

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).

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:

Start WORDSCAN and do a scan.

If no SCANNER POSSIBILITY appears under ACQUIRE, verify that parameters are set properly in DUNORD.INI.

Dunord's TWAIN drivers consist of two files working in team with Dunord's own drivers set. These files are :

They are included in the TWAIN directory of the driver floppy shipped with your Scanner Interface board.

First remove any existing version of DUNTW16.DS and TWAIN.DLL. You might also find older versions under the name DUNTWAIN.DS or I2KTWAIN.DS.

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 DUNTW16.DS file to that last subdirectory.

Copy the TWAIN.DLL file to your Windows directory, usually \WINDOWS.

The following table shows the diagram structure and the location of the files.

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

You will find in the following list PC imaging software that support TWAIN drivers. Our apologies to software developers 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.

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 or from our Web site.

Installation instructions will be supplied with your TMS application.

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:

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.

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 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.

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.

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:

Failure to do so might result in scanned images with missing lines.

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 machines with SCSI controller frequently use 2 DMA channels. You must instruct the I-2000 to use DMA channel 7.

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.

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.

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.

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.

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.

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).

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.

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 to save values
14. Hit twice ==> Scanner goes back to "Warming up Now"