HP ScanJet IIcx scanner, Win95 & DTC SCSI card.HP ScanJet IIcx scanner, Win95 & DTC SCSI card.
Posted on 1997-11-23
HP ScanJet IIcx scanner, Win95 & DTC SCSI card.
November 23, 1997
My problem is with running HP's DesksScan II
version 2.6 (sj137en.exe), which is a HP Win 95 driver,
under Windows 95, for my HP ScanJet IIcx scanner.
When I click on Deskscan.exe my computer freezes up.
Several times prior to a freeze-up I would get a blue
screen error message:
"Windows - A fatal exception OE has occurred at
0028:C13E157B in VXD dtc328x.mpd(01)+ 0000157B".
FYI: dtc3c8x.mpd is my SCSI driver. Also, on a
couple of occasions where I did a cold reboot,
after a freeze up, I would get the message:
"NO ROM BASIC-SYSTEM HALTED" prior to Win 95
loading, and after a couple of reboots my computer
would finally boot up to my Win 95 Desktop.
The scanner ran flawlessly for over two years
under Windows 3.11/DOS 6.2
486DX2-66MHz, EISA, VLB (4 years old)
SCSI ID 7 - SCSI card - DTC (Data Technology Corp/USA)
#3270VL VESA SCSI Host Adapter
SCSI ID 6 - Scanner - HP ScanJet IIcx (3 yrs old)
SCSI ID 4 - Iomega Jaz Drive/SCSI External (6 mos old)
SCSI ID 0 - Hard Drive - Toshiba #MK-537FB, 1 Gig
Device Manager>SCSI Controllers>DTC3280/3270/3250 Driver>
Before installing Win95 OS, I FDISKed my hard
drive and installed all new Win95 drivers and Win95
software upgrades (i.e. nothing was installed over an
older version). I partitioned my hard drive with
Partition Magic just as I had done under Win3.11.
HP DeskScan v 2.6 install info:
I used C:\HPDS\DISK1\SETUP2.EXE for installing and
followed the install instructions in README.WRI that
came with ver 2.6 and that of HP's bps01376 on the
HP website, and chose "MODIFY" and "Use an existing
compatible SCSI card" (my DTC SCSI card) during the
installation proccess, with the following results:
Device Manager>HP ScanJet Scanners>HP ScanJet IIcx>
There were no conflicts, designated by a yellow ! or red x.
Control Panel>HP ScanJet Scanners>
General tab>Default Scanner = ScanJet IIcx
General tab>Info = Product ID returned from
the selected address: HP C2500A 3332
Test tab> (clicking button freezes computer)
SCSI tab>DTC 3280/3270/3250 Driver
Available SCSI addresses: 1, 2, 3, 5
Regarding the following statement about entries to the
Config.sys, I tried running v2.6 several different ways:
-with the Config.sys entries and without vhpscand.vxd,
using either ASPI3X70.SYS or ASPI3X80.SYS
-without Config.sys entries and with vhpscand.vxd
-with both Config.sys entries and with vhpscand.vxd
The following entries were made to CONFIG.SYS, that were
not added automatically, but that I added manually per
instructions in DeskScan II ver 2.6 README.WRI notes:
per C:\Windows\Hardware.txt regarding ScanJet IIcx:
FYI: The following is the "Scanner" excerpt from the
C:\Windows\Hardware.txt that is included with MS-Win 95
when installing MS-Win95 on a hard drive (note Mirosoft's
specific mention regarding a ScanJet II scanner):
Windows 95 will detect most scanner hardware, but does
not supply protected-mode drivers for any scanner model.
All SCSI scanners use a feature called ASPI to talk to
the controller in question. Windows 95 supports ASPI in
protected mode. Hence, a scanner, although listed as an
"unknown device" in Device Manager, is supported through
protected-mode drivers in Windows 95, if there is a
protected-mode driver for the SCSI controller in question.
Note that theoretically you would not need the ASPI manager
real-mode driver (such as Aspi2dos.sys) in your Config.sys
file. However, some programs, such as HP ScanJet II and its
associated real-mode drivers, Sj!!.sys and Sjiix.sys, require
the real-mode ASPI manager to be in the Config.sys file or
they will fail to load. In these cases, you would need to
keep the real-mode drivers in the Config.sys file, but
Windows 95 will still support the scanner through the
protected-mode SCSI miniport driver (if one exists for
the SCSI controller in question).
The following folder was added:
C:\Deskscan (28 files & 1 Folder named Restart)
The following files were added to C:\Windows\:
There was one entry to the WIN.INI:
There were no were no entries to the SYSTEM.INI
All files mentioned above where checked to see if they
were in their proper locations.
Thank you in advance for your input,