From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-14 00:10:30
|
> I was able to scan some small images using sane. > Unfortunately, for large > images, the scanning went into 'D' (hardware block?) before > the scans were > finished. Resetting the PSC a number of times didn't help, > and the module > couldn't be unloaded or the scan processes killed (expected). > I didn't try > printing large files, but small files worked fine. > > What is the best way to debug this kind of stall? Hi, Daniel. I've occasionally seen this problem, where the process hangs and can't be killed, and ieee12844pp can't be unloaded, but I haven't been able to reproduce it reliably to try to track it down. What sequence of steps do you take to cause the problem (i.e. resolution and geometry settings, preview versus non-preview scans, number and frequency of scans, etc.)? > Also, does anyone have (or know how to get) a list of valid > OID codes for the > PSC 500? The LCD display codes didn't work. I've found trial and error to be the most reliable way to determine which OIDs are supported by which models. According to my testing very few are supported by the 1150, 117x, R series, and PSC500. That's why I put an "X" for xojpanel and these models on http://hpoj.sourceforge.net/suplist.shtml. > This last bit is off-topic, but xscanimage wasn't recognized by gimp. > According to the sane docs, all I have to do is put it in the > gimp plugin > directory. This didn't work, and gimp skipped it with an > "unrecognized > plugin" error. If anyone knows how to integrate this into gimp, I'd > appreciate an e-mail. Try looking around in the SANE mailing list archives (http://www.mostang.com/sane). I think there has been some discussion about this problem there in the past, but I don't remember the solution. Was gimp installed when you configured and built SANE? Was SANE's configure script able to find GIMP? Alternatively, you could try xsane, which is linked from there. xscanimage isn't really being maintained anymore. David |