[gscan2pdf-help] chroot problem

[Andreas v. H. <106...@co...>]

Dear Jeffrey, hello all,

in my SunRay thin client environment I am running gscan2pdf inside a 
32-bit chroot on an amd64 box. This is because the scanning command 
needs to be prefixed with a 32-bit wrapper that encapsulates USB in a 
proprietary TCP protocol, thereby address the scanner via the LAN on the 
stateless ultra thin client. This worked very well so far on my previous 
32bit server. Thanks again, Jeffrey, for providing the possibility to 
enter a prefix!

Now I start gscan2pdf with

   # /usr/bin/dchroot -d /usr/bin/gscan2pdf

and in the gscan2pdf settings I defined the said prefix that inside the 
chroot points to the bin directory, executing correctly the command 
"$PATH/utusbrun $PATH/scanimage".

Scanning works perfectly this way with an Avision scanner but my vintage 
Epson 1200 USB that worked well in the previous 32bit environment now 
cannot use its settings. The file ~/.gscan2pdf is being created but 
scanning yields only very coarse, unusable b/w scans (like 50dpi perhaps 
or less).

Could this be a problem with 64-bit perl being addressed from within 
gscan2pdf in 32-bit chroot? But then why does the Avision scanner work? 
Might there be a problem that could be worked around?

Or should I just use the 64 bit version of gscan2pdf and tweak some line 
in order to use the chroot only for adressing the scanner? Unfortunately 
I know a bit pf bash but no perl and wouldn't know how and where to do that.

  # /usr/bin/dchroot -d /opt/SUNWut/bin/utusbrun

as prefix seems not to be able to reach and use scanimage inside the 
chroot, perhaps beacuse the path for scanimage inside the chroot would 
need to be provided.

Best regards,

Andreas v. Heydwolff