Installing HP Scanners under Windows NT (Intel Only).
November 30, 1995
Revised April 26, 1996


DISCLAIMER:  I do not work for Hewlett-Packard and no one at HP, at least to my knowledge, has even looked at this file, much less approved it. HP is not responsible for its content. I offer this file on an as-is basis to those who care to use it. It has worked for many NT users, but I cannot guarantee that it will work for everyone or for your particular installation. If it doesn't do the trick for you, we can try to help out on the CIS HPSCANJET forum or in the AOL HP Scanner Products for PCs message board folder. However, in the end, the usability and functionality of your HP scanner under NT is not currently supported by any entity, commercial or private. Many of the terms and product names used in this file are trademarked by the respective companies.

Gary Melendez April 26, 1996
 
This file contains the following sections:

1. PRELIMINARIES
2. HARDWARE and COMPATIBILITY CONSIDERATIONS
3. 16-BIT VERSUS 32-BIT VERSION CONSIDERATIONS
4. FILE LOCATIONS
5. INSTALLING 16-BIT DESKSCAN 2.2 AND HP COLOR COPIER 1.0
6. INSTALLING 32-BIT DESKSCAN 2.3.1 and HP SCANJET COPY UTILITY 2.01
7. IF IT STILL DOESN'T WORK

1. PRELIMINARIES
The file is intended to be fairly comprehensive in its coverage. For those of you who are not starting from scratch, I apologize, but I'm afraid you'll have to wade through the other stuff to get to the meat you're after. The section headings listed above are intended to help with this. However, I do recommend that you at least briefly review sections 2, 3, and 4 for general information and compatibility considerations. I strongly recommend that you read through the complete procedure appropriate to your configuration before beginning the installation process.

If you would like to help improve the information in this file, please feel free to send suggestions or contributions to me. I will try to update this file from time to time with new information. To offer contributory information, please eMail me, Gary Melendez, at CIS ID 71024,1232, AOL screen name GaryM NT, or at gmelendz@ix.netcom.com.

For questions or problems in setting up a scanner under NT, please DO NOT SEND AN EMAIL TO ME. Instead post a message to All in the CIS HPSCANJET forum ScanJet II/3/4 section (message Section 8) or in the Scanner Products for PCs Folder of the HP message boards on AOL. I'm afraid that requesting help on a ScanJet problem via private eMail will only get you a boilerplate response asking you to post your question in the CIS HPSCANJET forum or the AOL HP message board.

Good Luck and Best Regards,
Gary Melendez



2. HARDWARE and COMPATIBILITY CONSIDERATIONS

A.
Installation of the 4c, 4p, 3c, 3p, IIcx, IIc, and IIp scanners under NT 3.5 and later (Intel platform only) are all addressed under these instructions. Note that, of these scanners, the earlier scanners were shipped with HP interface cards that will not function under NT. The specifics on this are addressed below in paragraph 2.D. The original ScanJet and the ScanJet Plus scanners are not NT compatible devices and cannot be installed under NT as they require a proprietary interface that is not supported under NT. The ScanJet 4s is a serial device and is not addressed in this file. The ScanJet 4si is a network capable machine designed for Novell Netware and it is also not addressed here. I know of no way to install HP scanners on Alpha, MIPS, or PowerPC platforms running NT and none of these instructions apply to those platforms.

B. HP PictureScan, shipped with the 4p, will not install under NT. One of the DeskScan versions must be downloaded and installed. The 4p itself works well under NT with the DeskScan and copier software.

C. The Visioneer PaperPort version 3.0.1 software shipped with the later 4c and all 4p scanners will install under NT, after a fashion, but I have found it to be unreliable under NT and to cause problems with other, unrelated applications and with 16-bit stability in NT. Versions earlier than 3.0.1 had a problem utilizing SCSI scanners and will try to access the scanner through a COM port, thereby causing other problems. My recommendation as far as PaperPort under NT is: Forget it, at least until the follow-on version to 3.0.1 is released.

D. Under NT, the scanner must be attached to a SCSI compliant interface card. This means that the HP C2502-66500 (ISA) or C2503-66500 (Microchannel) interface cards that shipped with later IIcx and all subsequent SCSI scanners or an NT compatible SCSI controller must be used. Use of the HP interface card (later referred to as simply the C2502) will require assignment of a hardware interrupt. For DS 2.2, the only valid assignment is IRQ5. For DS 2.3.1, valid assignments are IRQ 3, 4, 5, 7 or 9. If you cannot reassign IRQs to free an appropriate interrupt, then you must use a 3rd party SCSI controller.

E. The scanner should be installed as the last physical device on the external SCSI chain and terminated using active termination. Use of a 3rd party controller will likely require purchase of a standard SCSI cable of good quality and adequate shielding. The use of the HP-supplied cable or of one of the passive terminators should only be attempted if the scanner is to be a stand-alone device; i.e., as the only device on the SCSI controller to which it is attached.

F. If using an HP ScanJet IIcx or earlier, active termination will require the addition of a 3rd party active pass-through terminator on the 50-pin Centronics port of the scanner. The use of the HP-supplied passive 25-pin terminator on these scanners may work but is not recommended due to reliability considerations and the possibility of data corruption.

G. I strongly recommend that you use properly shielded 50-conductor SCSI cables and active termination when using 3rd party SCSI cards. Particularly if there are other devices on the same SCSI bus. If you use the scanner on a SCSI bus with write devices such as a hard drive and you do not use proper cabling or you use passive termination, you can pretty well count on some degree of data corruption on the write device.

H. I have no personal experience installing this software under versions of NT other than 3.51. Installing under NT 3.5 should work but I have not done so myself. For NT 4.0, installation of DS 2.2 and HP Copy 1.0 is essentially identical to installing under NT 3.5x. Installation of DS 2.3.1 and SJ Copy 2.01 under NT 4.0 or under NT 3.51 with the NewShell preview is possible but requires a workaround. This is addressed further in paragraph 3.D. below and in the procedures in paragraph 6. I should also add a disclaimer that I have not personally installed the HP C2502 interface since this card was not shipped with my SJ IIcx. Others have reported success using this card under NT but there have been reports from some users that the C2502 card will not work on their systems.

I. Keep in mind that Hewlett-Packard does not officially support their scanners or scanner software under NT. They do provide information for scanner use with NT on an as-is basis, but for HP scanner problems under NT we users are on our own. At least for the present. Much of the improvements in the DS 2.3.1 and SJ Copy 2.01 installation routines are NT specific. One might view this as an indication that the HP policy with respect to scanners and NT will change in the not-too-distant future.

3. 16-BIT VERSUS 32-BIT VERSION CONSIDERATIONS

Before installing or even downloading the software, you first need to make a decision about which versions of DeskScan and the Copy utility you want to run. You may, of course, install the 16-bit versions first and then move to the 32-bit versions later if you wish. Some points to consider in deciding on which versions to use:

A. DS 2.2 and Copier 1.0 are 16-bit and simple to implement. DS 2.3.1 and SJ Copy 2.01 are 32-bit and are easier to install under NT. DS 2.3 and SJ Copy 2.0 are 32-bit but had an NT 'unfriendly' installation routine and were quite a bit more complicated to install. DS 2.3 and SJ Copy 2.0 are the versions that have shipped with most 4c scanners to date. If you have DS 2.3 and SJ Copy 2.0, I highly recommend getting DS 2.3.1 and SJ Copy 2.01. The instructions for DS 2.3 and SJ Copy 2.0 have been removed from this file, but the pertinent procedures from the original instructions are still available, without revision, in Library 9 of the HPSCAN forum. The file name for the DS 2.3 and SJ 2.0 instructions is SJ_NTOLD.TXT. This is in consideration of 4c owners who received these versions with their scanner and cannot, for whatever reason, reasonably acquire the DS 2.3.1 and SJ Copy 2.01 archive files. Also, these instructions remain for foreign language users until these versions of DS 2.3.1 and SJ Copy 2.01 are released by HP.

B. DS 2.3.1 and SJ Copy 2.01 should give you better performance under NT and also provide a Twain_32 data source as well as OLE 2.0 connectivity.

C. Either solution will give you 16-bit HP AccuPage support under NT.

D. Use of the 32-bit versions under NT 4.0 or under NT 3.51 with the NewShell preview require Adaptec's EZ-SCSI 4.0 or the Adaptec versions of ASPI32.SYS and WNASPI32.DLL. Without the Adaptec versions of these files, DS 2.3.1 will cause a blue-screen system halt under NT 4.0 and NT 3.51 with the NewShell preview. If you do not have EZ-SCSI 4.0, the Adaptec versions of ASPI32.SYS and WNASPI32.DLL are available from Library 3 of the Adaptec CIS forum (GO ADAPTEC). The file name is ASPI32.EXE.

E. The 16-bit version archive files are considerably smaller than the 32-bit files and download time is much less.

F. DS 2.2 requires the use of IRQ5 with the C2502 card. DS 2.3.1 provides a method to use the C2502 card on IRQ 3, 4, 5, 7, or 9.
The installation instructions in sections 5 and 6 below are independent of each other; i.e., you only need to perform one of these procedures based on your choice of a 16-bit or one of the 32-bit solutions.

4. FILE LOCATIONS

File locations, names and sizes for the English versions at the time of this writing are as follows:
(NOTE: These are the Compuserve locations. The file names, however, are linked to the HP ftp site. Click to retrieve)

16-bit:        DeskScan 2.2   DS22EN.EXE   HPSCAN Lib 9   1203K
                  HP Copier 1.0  CC10EN.EXE  HPSCAN  Lib 9   680K

32-bit:        DeskScan 2.3.1 SJ120EN.EXE HPSPECIAL        3987K
                                             interactive download area
                                             (GO HPL-116)

                  HP SJ Copy 2.01 SJ130EN.EXE HPSPECIAL     2299K
                                             interactive download area
                                             (GO HPL-116)

All language versions of the files are in HPSCAN Library 9 as DS22nn.EXE, CC10nn.EXE, SJ120nn.EXE and SJ130nn.EXE, where nn designates the language version, and the file sizes differ slightly. However, at the time of this writing, the SJ120nn.EXE and SJ130nn.EXE foreign language versions in HPSCAN Lib 9 are still the DS 2.3 and SJ Copy 2.0 versions. They will be replaced with the DS 2.3.1 and SJ Copy 2.01 foreign language versions as soon as they are available from HP.

These files are also available from the HP web and FTP sites. At these sites, the 16-bit copier files are named CP10nn.EXE vice CC10nn.EXE (don't ask me why). The URLs for these sites are:
http://www.hp.com:80/cposupport/indexes/swin_dos.html
ftp://ftp.hp.com/pub/scanners/software/
IP address for the FTP site is 192.170.128.20 specify /pub/scanners/software/ as the initial remote directory.
Foreign language versions of DS 2.3.1 and SJ Copy 2.01 may become available on the HP web and/FTP sites before they appear on the HPSCAN forum so you may want to check there if you require a foreign language version.

They can also be obtained at media and S&H cost from the HP Distribution center. In the U.S. and Canada, phone 970-339-7009 or fax 970-330-7655. For other locations download the HPNUM.INF text file from Library 1 of the HPSCAN forum for contact information on the HP Fulfillment center nearest you.

5. INSTALLING 16-BIT DeskScan 2.2 and HP Copier 1.0

A.
Copy the downloaded DS22EN.EXE file to an empty subdirectory. Expand it by running DS22EN.EXE from DOS, an NT DOS prompt, or using the Open Archive | Extract function of WinZip 6 for NT. Copy the contents of the temporary subdirectory to a formatted 1.44MB floppy. You can now delete the temporary directory and all of its contents. Its a good idea to save the DS22EN.EXE file somewhere on your hard drive, at least until you have a successful install, in case you need it again. Repeat this procedure for expanding the CC10EN.EXE archive (CP10EN.EXE if downloaded from Internet) if you plan to install the copier program.

B. This step assumes you have physically installed the interface card you plan to use and connected the scanner to it. Verify that your SCSI adapter is properly installed with its own driver in NT and skip down to subsection 5.C. Or, if you are using the HP C2502 card, follow the steps below taken directly from the HP README.NT file that comes with DeskScan 2.2. I have modified it slightly to save an unnecessary reboot and I've inserted a <clarification> in step 6):

1) Double Click the Main program group in the Program Manager

2) Double Click the Windows NT Setup icon.

3) The WINDOWS NT SETUP dialog box appears. Select Add/Remove SCSI Adapters from the Options menu.

4) The SCSI ADAPTER SETUP dialog box appears. Click the Add button.

5) The SELECT SCSI ADAPTER OPTION dialog box appears. Scroll down and select Other in the Adapter combo-box.

6) The INSERT DISKETTE dialog box appears. Insert the disk with the HP SCSI drivers into drive A: <this is the DeskScan 2.2 floppy you made in step 5.A., also I know of no reason this wouldn't work from a B: drive>. Overwrite the drive path with A:\ and click OK.

7) The SELECT OEM OPTION dialog box appears. Select the NCR SDMS 53C400A SCSI driver -- HP400NT - 3.00.02 and click OK.

8) You will return to the SELECT SCSI ADAPTER OPTION dialog box. Select the NCR SDMS 53C400A -- HP400NT - 3.00.02 option and click Install.

9) The WINDOWS NT SETUP dialog box appears -- asking for the full path to the OEM SCSI adapter files (A:\). Click Continue.

10) You will return to the SCSI ADAPTER SETUP dialog box. Click Close.

11) You will return to the WINDOWS NT SETUP dialog box. Select Exit from the Option menu. Do not reboot the system yet.

C. So much for the C2502 card. The next step is to Verify the following files are present in the subdirectories indicated of your NT directory:

HPSCAN32.DLL in \system32
HPSCAN16.SYS in \system32\drivers

Note: If these files are not present, you may use EXPAND.EXE to manually expand them from your NT installation source media.

D. Once you have verified the files are in place, manually edit the CONFIG.NT file in the \system32 subdirectory using NOTEPAD.EXE or other ascii text editor and add following line:

device=%SystemRoot%\system32\drivers\HPSCAN16.SYS

Save the modified CONFIG.NT file

E. Ensure that any running programs are shut down before running the setup program. Two places to check:

1) Look in the Startup group and move anything in this group to another group temporarily. You can put these back into the Startup group after you have completed the installation.

2) Using REGEDIT32.EXE (can be launched from File | Run if you have not installed it with an icon in your system), look in the following registry location on the HKEY_CURRENT_USER page:
/Software/Microsoft/Windows NT/CurrentVersion/Windows
If there is a 'load' line ensure that the string value is blank. If not, double click on the 'load' line, write down the string for later reinsertion and then delete the string. Click OK to save the change. You can replace this string after completing the setup.

F. Shut down NT and reboot.

G. You're now finally ready to install DeskScan 2.2. Put the floppy you made back in step 5.A. into the drive and use File | Run to run its setup program, making appropriate choices for directories, scanner model and interface/scsi card. Do not allow the setup routine to modify any system files. After completing setup, reboot and you should be up and running with DeskScan 2.2 and HP AccuPage support. If you wish, you may now also install HP Copier 1.0 in the same manner. Reboot should not be necessary after the copier install unless you did not install DeskScan. I haven't tried it myself but installing HP Copier 1.0 without DeskScan 2.2 should work. Note that the SCSI Bus Address applet that comes with DeskScan 2.2 will not work under NT. It will report a scanner at every SCSI ID on the bus. Just ignore it and delete the icon that runs it.

6. INSTALLING 32-BIT DESKSCAN 2.3.1 AND HP SCANJET COPY 2.0.1

A.
Copy the downloaded SJ120EN.EXE file to an empty subdirectory. Expand it by running "SJ120EN -d" (without the quotes) from DOS, an NT DOS prompt, or by using the Open Archive | Extract function (make sure the Use Directory box is checked) of WinZip 6 for NT. This will create four subdirectories: DISK1 through DISK4. Now transfer the contents of each of those subdirectories to its own formatted 1.44MB floppy. You can now delete the subdirectories in the temporary directory and all of its contents. Its a good idea to save the SJ120EN.EXE file somewhere on your hard drive, at least until you have a successful install, in case you need it again. Repeat this procedure for expanding the SJ130EN.EXE archive if you plan to install the copier program. This will involve only two subdirectories and floppies.

B. Ensure that any running programs are shut down before running the setup program. Two places to check:

1) Look in the Startup group and move anything in this group to another group temporarily. You can put these back into the Startup group after you have completed the installation.

2) Run the hpresset program from your DeskScan directory using the Program Manager's File | Run command or explorer's Start | Run command. Set the IRQ to the interrupt identified in step 1). In some cases this file (hpresset.exe) will not install. If you get a "file not found" when trying to run it, you can copy it from disk 1 to the DeskScan directory on your hard drive. If there were any programs in the startup group or if you had to make changes to the registry to remove a string value from the load line, then shut down NT and reboot.

C. This step assumes you have physically installed the interface card you plan to use and connected the scanner to it. If you are using a 3rd party SCSI card, verify that your SCSI adapter and its driver are properly installed in NT. Run the HP DeskScan II setup program, making appropriate choices for directories, scanner model and interface/scsi card, BUT DO NOT REBOOT. If you intend to install SJ Copy 2.01, now is the time to do it. Just run its setup program but, once again, DO NOT REBOOT. I haven't tried it myself but installing SJ Copy 2.01 without DeskScan 2.3.1 should work as long as the other steps are followed as if you were installing DeskScan 2.3.1. At this point, the instructions branch depending on your configuration:

1) For NT 3.5x and a 3rd party SCSI card, you're done. Just shut down NT and reboot and you should be up and running.

2) For NT 3.5x and the C2052 card, perform step 6.D. before rebooting.

3) For NT 4.0 (or NT 3.51 with the NewShell preview) and a 3rd party SCSI card, perform step 6.E. before rebooting.

4) For NT 4.0 (or NT 3.51 with the NewShell preview) and the C2502 card, perform both steps 6.D. and 6.E. before rebooting.

D. If you are using the HP C2502 card, follow the steps below taken directly from the HP READ_NT.WRI file that comes with DeskScan 2.3.1. I have modified this procedure somewhat because it was apparently written with Win95 dynamic resourcing in mind. I have also inserted a <clarification> in step 6). Also, I have not tested this procedure myself since I do not have a C2502 card.

1) Find an available interrupt (run Win NT Diagnostics in the Administrative tools group). The valid choices are 3, 4, 5, 7, or 9. If none are available try to reassign the interrupt for one of the conflicting devices. If you cannot, then you must use another SCSI card.

2) Run the hpresset program in your HP DeskScan II program group. Set the IRQ to the interrupt identified in step 1).

3) From Program Manager, run Windows NT Setup (usually in the Main group). Under the Options menu, Select Add/Remove SCSI Adapters...

4) When the SCSI ADAPTER SETUP dialog box appears, click the Add button.

5) In the SELECT SCSI ADAPTER OPTION dialog box, scroll down and select Other in the Adapter combo-box.

6) The INSERT DISKETTE dialog box appears. Insert the disk with the HP SCSI drivers into drive A: <this is the DeskScan 2.3.1 DISK1 floppy you made in step 6.A., also I know of no reason this wouldn't work from a B: drive>. Overwrite the drive path with A:\ and click OK.

7) The SELECT OEM OPTION dialog box appears. Select the Symbios Logic 400a (HP Version) SCSI Adapter and click OK.

8) You will return to the SELECT SCSI ADAPTER OPTION dialog box. Select the Symbios Logic 400a (HP Version) SCSI Adapter option and click Install.

9) The WINDOWS NT SETUP dialog box appears -- asking for the full path to the OEM SCSI adapter files (A:\). Click Continue.

10) You will return to the SCSI ADAPTER SETUP dialog box. Click Close.

11) You will return to the WINDOWS NT SETUP dialog box. Select Exit from the Option menu.

12) If using NT 4.0 or NT 3.51 with the NewShell preview, perform step 6.E. before rebooting. If using NT3.5x, reboot now and you should be up and running.

E. If running NT 4.0 or NT 3.51 with the NewShell preview, you must replace the ASPI32.SYS and WNASPI32.DLL files installed by DeskScan 2.3.1 before rebooting. Rebooting with these files installed may result in a blue-screen system halt. If you do reboot and then launch DS 2.3.1 without having replaced these files, you will definitely get a blue-screen system stop. Adaptec's EZ- SCSI 4.0 contains versions of ASPI32.SYS and its attendant WNASPI32.DLL that are compatible both with NT 4.0 and with DeskScan 2.3.1. If you have EZ-SCSI 4.0, simply install it after installing DeskScan 2.3.1 and the offending versions will be replaced automatically. If you do not have EZ-SCSI 4.0, the Adaptec versions of ASPI32.SYS and WNASPI32.DLL are available from Library 3 of the Adaptec CIS forum (GO ADAPTEC). The file name is ASPI32.EXE. The ASPI32.SYS file is located in the \system32\drivers subdirectory of the main NT directory. The WNASPI32.DLL file is located in the \system32 subdirectory of the main NT directory. To replace them manually, just rename the existing versions and then copy the Adaptec versions to the same locations. Note that EZ-SCSI 4.0 and the Adaptec ASPI32.SYS and WNASPI32.DLL will work with other than Adaptec controllers.

F. If you have not already done so, at this point shut down NT and reboot. You should now be up and running with DeskScan 2.3.1, Twain_32, OLE 2.0 support, and HP AccuPage support.

G. If you decide to install HP ScanJet Copy 2.01 later, then be aware that it will replace the ASPI32.SYS and WNAPSI32.DLL files with the HP versions. If using NT 4.0 or NT 3.51 with the NewShell preview then either EZ-SCSI 4.0 must be reinstalled or the driver files manually replaced before rebooting and using SJ Copy 2.01.

7. IF IT STILL DOESN'T WORK

A. Other than the information on hardware I've mentioned in section 1 there isn't a lot more I can tell you for general troubleshooting purposes. I've seen indications that, regardless whether you are using NT 4.0 or not, the Adaptec versions of ASPI32.SYS and WNASPI32.DLL are generally more reliable than the HP versions, at least under NT. You might try installing EZ-SCSI 4.0 or replacing these files manually to see if it helps your problem.

B. I do not recommend using the NewShell preview at all. Although I have not tested it myself, using the Adaptec versions of ASPI32.SYS and WNASPI32.DLL should work with the preview. However, the NewShell preview is alpha code and it is quite buggy. It is bound to cause other problems. These problems may be minor on your particular system and you feel you can live with them, but the preview reduces the stability and reliability of NT and you are better off without it. You can never be sure how or when it might create a significant problem, one that you cannot overlook.

C. Some people have had problems with event 11 and event 15 errors in the event log. These can be few or numerous enough to require the event log to be manually cleared periodically. These errors may not necessarily be related to a SCSI cabling or other SCSI hardware error. Whether it causes problems or not seems to be related to the specific SCSI bus configuration and set of device drivers being used. The only sure way to eliminate this problem is to isolate the scanner from all other SCSI devices by placing it on a separate SCSI controller. If you experience this problem, moving the scanner up to SCSI ID 6 may help to mitigate it. At least one person I know of could only get these problems to disappear by moving the scanner to its own adapter. Luckily, he had a later model with the HP C2502 card and it worked on his system and didn't have to purchase another controller. You might also want to try using the Adaptec ASPI32.SYS and WNASPI32.DLL versions in this case as well. They are, in general, better behaved drivers than the HP versions contained in DS 2.3.1 and SJ Copy 2.01.

D. If you've tried everything else to get DS 2.3.1 working and it still won't perform on your system, I can only suggest you try dropping back to DeskScan 2.2. If you are using the C2502 card, I would recommend going to a 3rd party, NT compatible SCSI controller. Finally, you can always post a description of the problem in the ScanJet II/3/4 section (section 8) of the HPSCAN forum and hope another user who has had the same sort of problem drops by and helps out. As I indicated in the last paragraph of Section 2, HP Tech Support is currently not an option for us NT users as far as scanners go.

Back to NT Tips & Info