<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><span style="-webkit-text-size-adjust: auto;">Hi!</span><br><div dir="ltr"><span style="-webkit-text-size-adjust: auto;"></span><br style="-webkit-text-size-adjust: auto;"><blockquote type="cite" __apple_fixed_attribute="true" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;">On 08.03.20 at 13:02 Shawn Rutledge wrote:<br></blockquote><blockquote type="cite" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;">Shawn Rutledge <<a href="https://gitlab.com/ec1oud" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="2" style="color: currentcolor;">https://gitlab.com/ec1oud</a>> commented:<br></blockquote><blockquote type="cite" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;"><br></blockquote><blockquote type="cite" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;">I have definitely used this scanner with 64-bit systems for a long time. I don't <br></blockquote><blockquote type="cite" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto;">remember when the looping issue started though; that went on for a long time too.<br></blockquote><span style="-webkit-text-size-adjust: auto;">[...]</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">Seems there's some misunderstanding: The Plustek backend seems to have two issues:</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">* 3rd scan on a Epson Perfection 1260 shows red and yellow artefacts</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">* CanoScan N650 is no longer recognized</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;"></span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">The first issue might be a 32-/64-bit issue, especially regarding pointers. This is</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">my suspicion. </span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">The second one is IMO related to USB3 ports. We have enough report that on older</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">HW (using the ehci driver) the scanner works, with xhci the issue pops up.</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;"></span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">Regards,</span><br style="-webkit-text-size-adjust: auto;"><span style="-webkit-text-size-adjust: auto;">Gerhard</span></div><div dir="ltr"></div><blockquote type="cite"><div dir="ltr"><div class="footer" style="margin-top: 10px;"><br>
</div>
</div></blockquote></div><style>img {
max-width: 100%; height: auto;
}
</style></body></html>