I managed to get the Epson drivers installed, with a few tweaks during install scripts (details below). Unfortunately the resulting driver provides very few options (only media size, quality and color) compared to the extensive set of options provided by the CUPS+Gutenprint driver - and there's no option to reverse the page output order anyway.
I'll probably try the Turboprint evaluation at some point to see if it does work, but for my usage it's not really worth paying for the full version just for this option. They don't appear to have an SX100 driver, but the SX110 one might be close enough.
Epson driver installation details in case anyone is interested...
I used the Ubuntu 8.10 version from
Epson's downloads. Slightly confusingly, this downloads a file named pips-snx100-ubuntu8.04-3.5.0-CG.tgz - with "ubuntu8.04" in the name. Just running
sudo ./pips-snx100-ubuntu8.04-3.5.0-CG.install
would unpack the compressed data at the end of that file and run an install script (install-pips.sh) contained within. In order to inspect what it would do first and work through step-by-step, the following just extracts the files without running the install script:
Code: Select all
$ cd Downloads
$ tar -zxvf pips-snx100-ubuntu8.04-3.5.0-CG.tgz
$ ./pips-snx100-ubuntu8.04-3.5.0-CG.install --noexec --keep --target ./extracted
$ cd extracted
Having inspected the install-pips.sh script and the .deb packages which were unpacked, I realised some parts would fail but the scripts were likely to carry on regardless, possibly compounding the problems. Instead, I ran the following commands, determined by reading that script:
Code: Select all
$ sudo dpkg --install pips-common_3.5.0-1_i386.deb
The post-install script of this package creates a link from /sbin/pidof to /bin/pidof, which some of the installed scripts rely on. That link is not removed on uninstall (presumably in case anything else also uses it). Not really a problem, just seems a bit odd...
Code: Select all
$ sudo dpkg --install pips-ubuntu8.04_3.5.0-1_i386.deb
This installs, among other things, a script at /usr/local/EPAva/distro/ekpdsetup. One of the options to that script is used by other scripts to determine which CUPS service is used, but that detection no longer works. After line 141 (just before the closing
fi
of the
if dpkg...
block) add:
Code: Select all
elif apt-cache show cups-daemon >/dev/null 2>&1 ; then
spooler="$funcdir/cups"
Continuing package installation...
Code: Select all
$ sudo dpkg --install pips-snx100_3.5.0-1_i386.deb
The post-install script of this package fails, leaving the package in "half-configured" state. That's due firstly to the same CUPS package detection as above. Even if that were fixed, it would still fail since it attempts to work out where to place PPD files based on searching for known names installed by the CUPS package, none of which are present. Rather than trying to fix that more generically, I just edited /var/lib/dpkg/info/pips-snx100.postinst to remove lines 27 to 62 (code blocks beginning
Remove Get_cups_filelist=
and
installdir=
up to the next blank line) and replaced with
installdir=/usr/share/cups/model
. A similar fix is required to /var/lib/dpkg/info/pips-snx100.prerm (lines 23 to 58) otherwise the package can't be uninstalled in future (completing reproduction of the Windows installation experience on Linux
). After those edits, complete configuration of the package, which should now succeed:
Code: Select all
$ sudo dpkg --configure pips-snx100
And some further configuration which would be done by the install-pips.sh script:
Code: Select all
$ sudo cp ./install-pips.sh /usr/local/EPAva/printer/snx100/uninstall-snx100.sh # It looks like the uninstall part of this script should work, although I haven't actually tried it
$ sudo chmod 755 /usr/local/EPAva/printer/snx100/uninstall-snx100.sh
$ sudo cp ./*.lc /usr/local/EPAva/printer/snx100/
$ sudo /usr/local/EPAva/core/printersetup -i -p snx100 -s cups -a me300 -a ssx100 -a stx100 -a stx101 -a stx105 -a stx106
$ gksudo ekpd-tool
Click "OK" in the ekpd-tool application. I'm not sure whether it's actually necessary to run that unless changes need to be made. To set the new driver as the default printer: