From: news.rcn.com on
I posted this problem with my 8900 continuously giving hardware-lock error
messages a year or more ago and no one had any real idea why the scanner
which Visioneer had just so generously given me (when they couldnt get their
last scanner to stop giving mysterious Windows Error 20 messages) wasnt
working reliably.

Suddenly a few weeks ago, someone at Visioneer accidentally let slip that
the real reason I am getting these hardware lock messages is that something
in their driver conflicts with something in Service Pack 2, they couldnt fix
it and therefore this new scanner (or line of scanners?) was immediately
marked as 'end-of-life'!

Does anyone know if there is a work-around for this real problem please? Is
there any reference to it on any Microsoft support bulletin? Or a reference
to which other scanners it affects?


From: CSM1 on
"news.rcn.com" <fountainpen(a)amexol.com> wrote in message
news:McOdnac_vr_oMMLVnZ2dnUVZ_h7inZ2d(a)rcn.net...
>I posted this problem with my 8900 continuously giving hardware-lock error
>messages a year or more ago and no one had any real idea why the scanner
>which Visioneer had just so generously given me (when they couldnt get
>their last scanner to stop giving mysterious Windows Error 20 messages)
>wasnt working reliably.
>
> Suddenly a few weeks ago, someone at Visioneer accidentally let slip that
> the real reason I am getting these hardware lock messages is that
> something in their driver conflicts with something in Service Pack 2, they
> couldnt fix it and therefore this new scanner (or line of scanners?) was
> immediately marked as 'end-of-life'!
>
> Does anyone know if there is a work-around for this real problem please?
> Is there any reference to it on any Microsoft support bulletin? Or a
> reference to which other scanners it affects?
>

Well, I see two things you can do.

1. Remove SP2, go back to SP1
2. Get a new scanner that is supported on Windows XP SP2 and SP3.

There are much better scanners now for less than $100.

Example.
http://www.usa.canon.com/consumer/controller?act=ModelInfoAct&fcategoryid=120&modelid=13810

--
CSM1
http://www.carlmcmillan.com
--


From: Don Kirkman on
It seems to me I heard somewhere that CSM1 wrote in article
<BTO7k.12650$mh5.3055(a)nlpi067.nbdc.sbc.com>:

>"news.rcn.com" <fountainpen(a)amexol.com> wrote in message
>news:McOdnac_vr_oMMLVnZ2dnUVZ_h7inZ2d(a)rcn.net...
>>I posted this problem with my 8900 continuously giving hardware-lock error
>>messages a year or more ago and no one had any real idea why the scanner
>>which Visioneer had just so generously given me (when they couldnt get
>>their last scanner to stop giving mysterious Windows Error 20 messages)
>>wasnt working reliably.

>> Suddenly a few weeks ago, someone at Visioneer accidentally let slip that
>> the real reason I am getting these hardware lock messages is that
>> something in their driver conflicts with something in Service Pack 2, they
>> couldnt fix it and therefore this new scanner (or line of scanners?) was
>> immediately marked as 'end-of-life'!

>> Does anyone know if there is a work-around for this real problem please?
>> Is there any reference to it on any Microsoft support bulletin? Or a
>> reference to which other scanners it affects?

>Well, I see two things you can do.

>1. Remove SP2, go back to SP1
>2. Get a new scanner that is supported on Windows XP SP2 and SP3.

FWIW have you tried configuring the compatibility options for an older OS like
WinSE or Win98?

But try SP3 before considering going backwards. ISTM quite a few who have
upgraded are pleasantly surprised. And for me SP2 was definitely superior to
SP1, though I had stopped using my Visioneer before SP2 came out--I've just sent
it off to my son and his family where his kids will be the main users.

From: news.rcn.com on

"Don Kirkman" <donsno2(a)charter.net> wrote in message
news:1rpv54pqnodhgbi2g4ifhglrlon6ehbvfq(a)4ax.com...
> It seems to me I heard somewhere that CSM1 wrote in article
> <BTO7k.12650$mh5.3055(a)nlpi067.nbdc.sbc.com>:
>
>>"news.rcn.com" <fountainpen(a)amexol.com> wrote in message
>>news:McOdnac_vr_oMMLVnZ2dnUVZ_h7inZ2d(a)rcn.net...
>>>I posted this problem with my 8900 continuously giving hardware-lock
>>>error
>>>messages a year or more ago and no one had any real idea why the scanner
>>>which Visioneer had just so generously given me (when they couldnt get
>>>their last scanner to stop giving mysterious Windows Error 20 messages)
>>>wasnt working reliably.
>
>>> Suddenly a few weeks ago, someone at Visioneer accidentally let slip
>>> that
>>> the real reason I am getting these hardware lock messages is that
>>> something in their driver conflicts with something in Service Pack 2,
>>> they
>>> couldnt fix it and therefore this new scanner (or line of scanners?) was
>>> immediately marked as 'end-of-life'!
>
>>> Does anyone know if there is a work-around for this real problem please?
>>> Is there any reference to it on any Microsoft support bulletin? Or a
>>> reference to which other scanners it affects?
>
>>Well, I see two things you can do.
>
>>1. Remove SP2, go back to SP1

No I wouldnt dream of going back to such an old unsupported product with
ancient dlls and gaping security holes &malware invitations, especially just
because of one driver on another unsupported product with SP2!
>>2. Get a new scanner that is supported on Windows XP SP2 and SP3.
>
> FWIW have you tried configuring the compatibility options for an older OS
> like
> WinSE or Win98?
>
> But try SP3 before considering going backwards. ISTM quite a few who have
> upgraded are pleasantly surprised.
I was actually unaware that SP3 even existed as a standalone product, - isnt
it just a rolled up accumulation of all prior patches?

And for me SP2 was definitely superior to
> SP1, though I had stopped using my Visioneer before SP2 came out--I've
> just sent
> it off to my son and his family where his kids will be the main users.

Yes, OK right I get the message but all I want to do is to get a scanner
working properly and I thought that this would be a good idea IF there was a
workaround which visioneer wont tell me about. I have become relatively
used to the paperport software and didnt necessarily want to change.

I also have a CanoScan N1220U which I have connected now and which seems to
be working reasonably well while we are on the subject of getting older
scanners working. I also have a Umax Astra 1220U as well but thought that it
was a considerable step DOWN from the others? BTW I also have a 9450 and
wonder whether this will work in SP2 either

Is this time to dump products not supported by their manufacturer? (and of
course dump the manufacturer thereafter if they behave like this: Was it
their fault that their driver wouldnt work with the offending security patch
within SP2 or COULDN'T they have produced a driver for it?)



From: Don Kirkman on
It seems to me I heard somewhere that Don Kirkman wrote in article
<1rpv54pqnodhgbi2g4ifhglrlon6ehbvfq(a)4ax.com>:

Clarification

>It seems to me I heard somewhere that CSM1 wrote in article
><BTO7k.12650$mh5.3055(a)nlpi067.nbdc.sbc.com>:

>>"news.rcn.com" <fountainpen(a)amexol.com> wrote in message
>>news:McOdnac_vr_oMMLVnZ2dnUVZ_h7inZ2d(a)rcn.net...
>>working reliably.
>
>>> Suddenly a few weeks ago, someone at Visioneer accidentally let slip that
>>> the real reason I am getting these hardware lock messages is that
>>> something in their driver conflicts with something in Service Pack 2, they
>>> couldnt fix it and therefore this new scanner (or line of scanners?) was
>>> immediately marked as 'end-of-life'!

>>> Does anyone know if there is a work-around for this real problem please?
>>> Is there any reference to it on any Microsoft support bulletin? Or a
>>> reference to which other scanners it affects?

>>Well, I see two things you can do.

>>1. Remove SP2, go back to SP1
>>2. Get a new scanner that is supported on Windows XP SP2 and SP3.

>FWIW have you tried configuring the compatibility options for an older OS like
>WinSE or Win98?

To be clear, I mean the compatibility options in WinXP which let legacy
applications perform as if they were running on an earlier version of Windows.

>But try SP3 before considering going backwards. ISTM quite a few who have
>upgraded are pleasantly surprised. And for me SP2 was definitely superior to
>SP1, though I had stopped using my Visioneer before SP2 came out--I've just sent
>it off to my son and his family where his kids will be the main users.