🚀 go-pugleaf

On 10 Dec 1996 21:11:03 -0700, Mike Hales <mhales@primenet.com> wrote:

>Leo Hau wrote:
>> 
>> As far as my understanding TWAIN is a software standard not specifically to
>> serial port. 

   True.

>So, I ask my vendor what color scanner to buy that will work with NT 4.0
>WS. Vendor consults his Hardware Compatibility List (provided by
>Microsoft) and sells me the HP 4P Scanner. 

   Which is also what I have.

>After spending most of a day
>trying to install it, I call HP, who says _they_ didn't put their
>scanner on the list, Microsoft did. 

   Figures.

>I find out, from an exhaustive
>Internet search, that I can get this all to work with an Adaptec SCSI
>card and drivers. 

   True, I use a 1542 at the moment, soon to be a 2940.

>Another call to the vendor and another $150.00 and I
>spend two more days trying every combination of IRQ, PNP/noPNP, and some
>unholy mantras to boot, all to no avail. 

   At this point, getting the SCSI adaptor to work is the first
priority (actually, the scanner follows pretty much by itself).

>from this is a fellow on Usenet who posted a link: 
>http://www.ahoynet.com/~scanman/sjonnt.htm#in32 
>to some very good instructions (that I can't get to work).

   Worked for me out of the box. Once you've got SCSI going, the rest
is just installing a couple programs off floppies.

>I can't seem to resolve the IRQ conflicts I'm getting between the Olicom
>PCI Token-ring  card, the Creative AWE SB32 sound card, and the Adaptec
>1522b SCSI card.

   This is your problem (has little to do with scanners). I can't help
you out on this one, 

>TWAIN, SCSI and DDE are all standards, so why does Microsoft claim I can
>run this hardware when I can't? And why didn't they write support into
>the OS? 

   It's there. Called SCSI, works fine. If your hardware creates
conflicts, software can't resolve it. Might be a motherboard problem,
but is certainly centered around resolving those IRQ settings on the
PCI bus.

>Should not Microsoft be responsible for making the drivers
>available if they put the device on the list? 

   If they test it and find it to work OK, there's no need for
additional drivers, they can put it on OK.

   Have you tried pulling out the Olicom (which I BTW have bad
experiences with), and the sound card? Just to see the Adaptec work on
its own.

>Microsoft, Adaptec, and HP have all washed their hands of providing any
>support for this hardware. Who's looking out for the consumer in this
>marketplace?

   Well, things do get complex. MS has tested it and it works fine.
Works great here too. HP has decided not to support it until
NT-specific drivers (or even the tiny SCSI-adaptor) are 100% ready -
much in line with the quality commitment I've come to expect from HP. 

   Bottom line:

   Try pulling out some of the other stuff to gain experience.

   I know for sure the Adaptec (1542 ISA, though) / HP4P combo works,
but conflicts _are_ tricky.


					-Henrik