Archived from groups: alt.comp.periphs.scanner (More info?)
Hi,
I had a weird experience yesterday: Having just received two Epson
Perfection 1640 SU flatbed scanners, I connected one of them via UBS
cable to a brandnew IBM thinkpad, as it came out of the box with Windows
XP SP1.
The scanner light was green and all seemed well. I told the XP scanner
and image wizard thingy (Programs, accessoires, cameras and scanners) to
do a prescan of an image, and something came up in the prescan window
that resembled the image I had placed on the glass. I then told the app
to do a real scan. It created a bit of weird noise, as if fine
positioning the sliding image scanning head, and spit out a large yet
completely white bitmap. I tried again, same thing.
To add insult to injury, the slider with the imaging head and lamp are
now stuck in front of the scanner, and do not go back even when I power
cycle the scanner or restart the computer, or even disconnect the two.
The scanner LED that is supposed to be steady on green flashes red.
Thinking that one of the scanners I had received was sort of DOA, I
hooked up the other one - same effect. In seconds, WXP SP had appears to
have trashed two scanners. I am baffled. Digging at the MS help or
"knowledge" base ( what a neat name for "bug listing site" !) I found
that SP2 is supposed to fix a prescan issue. Nevertheless, I cannot
believe that XP should be able or allowed to issue commands that push an
imaging unit so far off that it gets stuck.
I have now upgraded to SP2, but of course, that does not get the scanner
unstuck.
Now I would like to know:
(a) Does anybody know how to fix this?
(b) Has it happened to others as well?
Thanks in advance & cheers, Stefan
Hi,
I had a weird experience yesterday: Having just received two Epson
Perfection 1640 SU flatbed scanners, I connected one of them via UBS
cable to a brandnew IBM thinkpad, as it came out of the box with Windows
XP SP1.
The scanner light was green and all seemed well. I told the XP scanner
and image wizard thingy (Programs, accessoires, cameras and scanners) to
do a prescan of an image, and something came up in the prescan window
that resembled the image I had placed on the glass. I then told the app
to do a real scan. It created a bit of weird noise, as if fine
positioning the sliding image scanning head, and spit out a large yet
completely white bitmap. I tried again, same thing.
To add insult to injury, the slider with the imaging head and lamp are
now stuck in front of the scanner, and do not go back even when I power
cycle the scanner or restart the computer, or even disconnect the two.
The scanner LED that is supposed to be steady on green flashes red.
Thinking that one of the scanners I had received was sort of DOA, I
hooked up the other one - same effect. In seconds, WXP SP had appears to
have trashed two scanners. I am baffled. Digging at the MS help or
"knowledge" base ( what a neat name for "bug listing site" !) I found
that SP2 is supposed to fix a prescan issue. Nevertheless, I cannot
believe that XP should be able or allowed to issue commands that push an
imaging unit so far off that it gets stuck.
I have now upgraded to SP2, but of course, that does not get the scanner
unstuck.
Now I would like to know:
(a) Does anybody know how to fix this?
(b) Has it happened to others as well?
Thanks in advance & cheers, Stefan
Facebook
Twitter
Instagram