| Title |
Description |
| Windows NT4 Support |
The minimum driver versions
required to provide Windows NT support are:
| SCSI* |
VistaScan 2.33 (CD1.02) or later
MagicScan 3.0 or later |
| Parallel |
VistaScan 2.36 (CD1.03) or later |
| USB |
Windows NT4 does not support USB. |
* Owners of "UC" scanners should use the
NT-specific build of MagicScan 2.41.
Note: VistaScan 2.4.3 before SCSI CD1.12 / Parallel CD1.03 has a known
NT-specific installation bug.
Presto PageManager
Version 1.x is not compatible with Windows NT; version 2.x is compatible although only
later versions supported NTFS (uncompressed) volumes. Version 4.x and later fully support
NT and uncompressed NTFS volumes. |
| Windows 2000
Support |
In general we cannot
provide technical support for Windows 2000 prior to its full release (scheduled Feb 2000)
- for information on driver compatibility please visit our developer
pages. |
| A Service Failed to
Load at Startup |
UMAX's drivers tend to
install a large number of Devices on NT systems, only a few of which are relevant to each
installation - this may sometimes cause the error "A Service Failed to Load at
Startup", although the scanner will often still function.
General note: we recommend switching the scanner on before booting an NT PC, as the UMAX
services will attempt to detect the scanner when they start.
The UMAX drivers are installed and controlled via the Devices (not Services) control
panel:
| Device |
Startup Mode |
Description |
| UMAXIS11 |
Automatic |
Driver for the UMAX
UDS-IS11/ISA SCSI card; this driver requires the ISA card to be installed and working
correctly in order to load. If UMAXIS11 fails to load an error is written to the Event
Log. As with other SCSI card drivers this can only be loaded at startup (ie after reboot). |
| DMX3191 |
System |
Driver for the Domex
UDS-IS11/PCI SCSI card (VS3.1+ MS4.2+); as above this driver will only load if the card is
present (note: resources required for PCI card). |
| AEC671x |
System |
Driver for the Domex
OEM PCI "A-Card" SCSI card (VS3.1+ MS4.2+); as above this driver will only load
if the card is present. |
| ASC |
System* |
Driver for the UMAX
PCI SCSI Host ControllerI card (VS3.5+ MS4.2+); as above this driver will only load if the
card is present. |
| UDNT |
Automatic |
32-bit SCSI scanner
driver, used by all SCSI models irrespective of controller type. As an Automatic class
device this will launch when NT boots however it will fail if no scanner is detected
(despite the error message the event won't be logged). If you prefer to switch your
scanner on after the system has booted you can ignore the error and use
the Tape Devices control panel to refresh the SCSI card later. UDNT can also be
started by an application or manually in the Devices control panel, provided the scanner
is available. |
| UMAXDRV |
Automatic |
16-bit version of SCSI
scanner driver, used by Scanner Test and Copy Utility in earlier versions of the driver
(not required in VS3.x or MS4.x). |
| UMAXPCLS |
Automatic |
Parallel port scanner
driver used before VistaScan 2.4.3. In VistaScan 3.1 this device is sometimes loaded by
mistake (in addition to PPSCAN), but can be disabled to prevent errors at startup. |
| PPSCAN |
Automatic |
Parallel port scanner
driver used in VistaScan 2.4.3 and above. |
| UMAXMINI |
Disabled |
Win9x device driver
sometimes mistakenly loaded if scanner isn't detected during installation - not compatible
with NT< should always be Disabled. |
|
| Scanner Not Found
or Not Ready |
The most common cause of
this problem is not having the scanner switched on and connected during startup - SCSI
devices can be refreshed (see above). Other "Link" or "scanner not
found" issues should be treated as per Win9x, and are covered in the SCSI and Parallel FAQs. |
| Link or Hardware
Fail when logged on as a USER |
All of the scanner drivers
and software can only be installed on an NT system when logged on as a member of the local
Administrators group (in a domain network environment a Domain Admin will normally also
have sufficient permissions). However the VistaScan parallel driver also requires the user
to logon with at least local Administrator permissions in order to successfully scan -
non-local-Admin level logons will only see a "Link or Hardware Fail" error
message. This limitation is caused by the parallel driver architecture and we are not
aware of any workarounds. Further info will be posted here if future driver releases add
support for non-Admin users. |
| Sharing scanners
with NT4 |
The "Networking Scanners - PC" technical note includes
advice for NT users trying to share scanners between two NT systems or between an NT scan
server and Win9x clients. |
