[sane-devel] Nikon LS-1000 fails with sane-backends-1.0.15

2006-01-18 Thread Bob Hepple
On Thu, 12 Jan 2006 18:03:55 +1000 Bob Hepple wrote: > Help!!! > > I recently dusted off my old Nikon LS-1000 SCSI negative/slide scanner > and tried to scan in some negatives with xscan. > > After the scan, I get this message: > > "Backend sends more image data

[sane-devel] Nikon LS-1000 fails with sane-backends-1.0.15

2006-01-12 Thread Bob Hepple
can] sane_close Calling sane_exit [coolscan] sane_exit scanimage: finished Any help to get this running again would be most welcome ... Thanks Bob -- Bob Hepple mailto:bhep...@freeshell.org http://bhepple.freeshell.org Public Key: http://bhepple.freeshell.org/public_keys.txt

Fw: [sane-devel] Nikon LS-1000 breaks on 0.92 and later???

2005-01-16 Thread Bob Hepple
_descriptor 0 ... error dialog showing message about options [coolscan] sane_close [coolscan] do_cancel [coolscan] do_eof [coolscan] do_cancel: kill reader_process [coolscan] sane_exit -- Bob Hepple mailto:bhep...@freeshell.org http://bhepple.freeshell.org Public Key: http://bhepple.freeshell.

[sane-devel] Nikon LS-1000 breaks on 0.92 and later???

2005-01-15 Thread Bob Hepple
le to debug shared library initializers and track explicitly loaded dynamic code. Cheers Bob On Sat, 8 Jan 2005 18:39:08 +1000 Bob Hepple wrote: > G'day from sunny Brisbane > > I recently upgraded to xsane 0.95 (from 0.91) and and sane-backends-1.0.14 > (from 1.0.11) and sin

[sane-devel] Nikon LS-1000 breaks on 0.92 and later???

2005-01-09 Thread Bob Hepple
ly suspect that of being my current problem. Thanks Bob -- Bob Hepple mailto:bhep...@freeshell.org http://bhepple.freeshell.org Public Key: http://bhepple.freeshell.org/public_keys.txt --Signature=_Sun__9_Jan_2005_08_27_17_+1000_=hNQ+u6cNtoNyMTu Content-Type: application/pgp-signature ---

[sane-devel] Nikon LS-1000 breaks on 0.92 and later???

2005-01-08 Thread Bob Hepple
_ACTION_GET_VALUE, &xsane.num_elements, 0) != SANE_STATUS_GOOD) { xsane_back_gtk_error(ERR_OPTION_COUNT, TRUE); sane_close(xsane.dev); xsane_exit(); /* will never come to here */ } ... but I guess it's in the back-end somewhere. That's as far as I got help -- Bob Hepp