Installing HP DeskScan II 2.3

Installation instructions for both NT 3.51 and 4.0 when installing HP DeskScan II 2.3.

rick gould

November 30, 1996

2 Min Read
ITPro Today logo

The following installation instructions apply to both NT 3.51 and NT4.0:

  1. Install HP DeskScan II 2.3 from the floppy disks.

  2. Check that the following files are in the directories listed:

    c:winntsystem32hpscanmgr.dll

    hpsj32.dll

    hpscanmgr.hlp

    hpscntst.dll

    winaspi32.dll

    c:winntsystem32driversaspi32.sys

    (Some users report that only the Advanced SCSI Programming Interface (ASPI)layer supported by Hewlett-Packard works, although other users say that thelatest ASPI drivers from Adaptec are the only solution.)

  3. With Notepad or another text editor, add the following line to the win.inifile:

    Default source = C:WINNTTwain_32HPDS23.DS

  4. Open the Registry editor, and make the following changes. (If you useDeskScan II 2.3.1, the installation program makes these changes for you.)

    a. Under hkey_local_machinesystemcurrentcontrolsetservices, add a Keycalled aspi32 and create the following values:

    ErrorControl:REG_DWORD:1

    Start:REG_DWORD:2

    Type:REG_DWORD:1

    b. Under hkey_current_usercontrolpanelmmcpl, create the following line:

    HP_ScanJet:REG_SZ:%SystemRoot%system32hpscanmgr.dll

    The Registry changes configure NT to load the appropriate programs to run HPDeskScan II.

  5. Shut down the system, and then reboot.

Even when you follow the above steps, problems can occur. For example, oneInternet posting on the CompuServe Forum HPPER said HP DeskScan II 2.3'sinstallation program sometimes displays a dialog for entering the location ofthe Visioneer PaperPort software. According to the user posting the message, youcan ignore this request either by pressing Cancel or by running the installationprogram's setup2.exe program.

Another Internet user reported that HP DeskScan II 2.3's installationprogram thinks it's installing under Windows 3.x, not Windows NT, and thusinstalls Win32S and other Windows 3.x files in the wrong place. Win32S, anApplication Programming Interface (API), is a 32-bit dynamic link library thatWindows 3.x can use to run some 32-bit programs within a 16-bit environment. IfWin32S were successfully loaded into NT, it could cause some major conflicts.

The user's solution was to modify the hpsetup.ini file on the HP DeskScaninstallation disks. There are two important blocks on this file, in the [Win3.1]and [WinNT] sections, respectively. The user copied the [WinNT] block over the[Win3.1] block to make the two blocks identical. Both blocks then look like thefollowing:

[Win3.1] or [WinNT]

Block1=PROGRAM

Block2=PROGRAMNT

Block3=WINDOWS

Block4=SYSTEMNT

Block5=TWAIN

Block6=SYSTEM32DRIVERS

Thus, the installation program still thinks it's working with Windows 3.xbecause one block's heading still says Win3.1, but the new block fools it intoloading the appropriate files in the right directories. (For more informationabout online sources of information for HP ScanJet and other scanners, see "OnlineInformation Sources.")

Read more about:

HP
Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like