[sane-devel] Normal or destructive behaviour when SANE starts?

[Alisdair]

Thanks Jose, fortunately I seem to have found a fix, but I'm waiting to be sure.

Things have progressed - from the other thread with an almost identical name (I got 
confused over addresses so the original got sent twice)!:

'...it's possible I've solved the problem by commenting out all the details listed for 
other scanners in snapscan.config.

A couple of reboots and starting Xsane each time has produced a perfectly uneventful start 
for the scanner.

I'm none the wiser why this should be doing the trick, unless sane is checking all the 
options and some are causing a response from the e20 - that's my theory anway.'


Regards, A.




Jose Paulo Moitinho de Almeida wrote:
> On Friday 14 March 2003 13:03, Alisdair wrote:
> 
>>..
>>
>>1. The scanner spends about 15 seconds making rather worrying grinding
>>noises (the scan head does not move at this time);
>>
> 
> 
>>From the PROBLEMS file:
> 
> - Avoiding damage on Mustek flatbed scanners
>         Most Mustek flatbed scanners have no protection against exceeding
>         the physical scan area height.  That is, if a scan is attempted with
>         a height that exceeds the height of the scan surface, the scanner
>         begins making loud noises and the scan mechanism may be damaged.
>         Thus, if you hear such a noise, IMMEDIATELY turn off the scanner.
> 
> I once had a  scanner (neither Mustek nor Agfa) damaged because of this. Don't 
> know about your case, but I would be most carefull.
> 
> Regards
> 
> ZP
> 
> .
>