1. mscan241.exe Driver
2. README.TXT File Contents

README.TXT Driver File Contents (mscan241.exe)

MagicScan Readme V2.41

Welcome to MagicScan Version 2.41

Please read this document carefully, it contains important information not 
included in the documentation.

Topics covered in this document include:

     * System Requirements
     * Driver Information
     * Network Scan Notes
     * Troubleshooting

[System Requirements]
     Windows 3.1 or later
     Windows 95

If you installing in a Windows 3.1 system, a single MagicScan Program Group
will be created afrer the installation. If you installing in a Windows 95
system, both the MagicScan Program Group for 16-bit applications and the
MagicScan32 Program Group for 32-bit applications will be created after the 
installation.

[Driver Information]

Software Name                     Application Specific Software Driver

TWAIN Compliant Applications      MAGIC.DS    V2.41
                                  MAGIC32.DS  V2.41

TypeReader /LE                    TR_UMAX.PXW V1.55
				  PIXDFLT.DLL

OmniPage 386/Pro                  UMAX.PXW    V1.55
				  SCANMGR.LST

OmniPage Direct 1.0               UMAX.PXW    V1.55
				  SCANMGR.LST

WordScan V1.0a/Plus V1.0b         UMAX.PXW    V1.55
				  PIXDFLT.DLL

WordScan V2.0                     UMAX.PXW    V1.55


[Network Scan Notes]

1. Under certain conditions, the NetHeapSize in Windows must be reset to 
   a larger value.  Please use the value suggested by Windows.
2. Both the server and client require a NETBIOS driver loaded before scanning  
   (for example, NETBIOS.EXE in Novell Netware).
3. The Scanner Test program can only test the local scanner. It cannot test 
   the network scanner.
4. ISIS drivers for some OCR packages do not support network scanning.


[Troubleshooting]
1. Whenever you fail to invoke MagicScan from an application, do one of
   the following:
   (1) If there is more than one way to start MagicScan, try another way
       instead. For example, try 'Select TWAIN32' instead of 'Select TWAIN".
   or,
   (2) Re-install MagicScan driver to restore some possibly overwritten files.

2. When this message "ASPI Allocate Memory Error!" appears, the driver will 
   modify the UMAXDRV.INI file located in the Windows directory. By rebooting 
   the Windows environment, the driver should work fine. If there is any 
   problem and you need to go back to the original status, use a text editor 
   to modify the UMAXDRV.INI file. The content of UMAXDRV.INI should look 
   like that shown below:

	   [UMAX_Drivers]
	   DriverType=umaxaspi

	   [UMAX_SCSI]
	   InterfaceType=UDS-IS11
	   VxDAllocateMemory=1

   The driver will have changed the "VxDAllocateMemory" value to 1. 
   Change the value back to 0 to restore the original value.

Note: If you have a UMAXMEM.SYS driver in CONFIG.SYS file, please remove it.
      There is no need for the UMAXMEM.SYS driver if "VxDAllocateMemory=1". 
      This entry will accomplish the same thing as the UMAXMEM.SYS driver.

3. If you are using an Adaptec-Compatible SCSI card with your UMAX scanner, 
   then you must install an ASPI manager for DOS, (e.g. ASPI4DOS.SYS), 
   in your CONFIG.SYS

   If you encounter some problems after installing the ASPI manager for DOS, 
   it may be due to a conflict between the ASPI manager for DOS and the 
   Windows 95 SCSI miniport driver. Some users may see the MagicScan window 
   appear but not be able to use it to scan.

   To correct this problem, you should disable the SCSI miniport driver that 
   controls the SCSI card to which the UMAX scanner is attached. The SCSI 
   miniport driver is located in \WINDOWS\SYSTEM\IOSUBSYS\. You can disable 
   the driver by simply renaming it, (e.g.  aha154x.mpd to aha154x.mmm). 
   Be sure to reboot your PC afterwards to make the changes take effect. 
   The scanner driver should work fine after this.

4. If the NETBIOS error message "ncb_bridge field not 00 or 01" appears, you 
   must run network setup to select a NETBIOS driver such as NETBEUI or 
   NETBIOS over ipx/spx to the default protocol for both the server and the 
   client. In both Windows 3.1 and Windows 95, network setup is located in 
   the Control Panel.

*************END OF README FILE***********************