[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-05-27 09:19, Giuseppe Sacco wrote: > please find the new patch, where I correct one small error and tested it > with LS-50. The code you pointed out seems to be a correction of a > previous bug, so I think it will not break any working scanner. I just applied your patch to CVS. > Test results with LS-50: > > Blank and white negative film: not working > Color negative film: not working > Color positive film: working, but I think there is still a problem with > autoexposure, since all scanned images are very dark. For now I used status "minimal" for the LD 50 ED/V ED and "untested" for "Coolscan LS-5000 ED". Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Henning Meier-Geinitz ha scritto: [...] > you (or somebody else) post a patch that includes my and > your comments? I.e. that can't break support for the other scanners? > And that is tested with the LS-50? Hi Henning, please find the new patch, where I correct one small error and tested it with LS-50. The code you pointed out seems to be a correction of a previous bug, so I think it will not break any working scanner. Test results with LS-50: Blank and white negative film: not working Color negative film: not working Color positive film: working, but I think there is still a problem with autoexposure, since all scanned images are very dark. Bye, Giuseppe -- next part -- A non-text attachment was scrubbed... Name: cs2-ls50-full.patch Type: text/x-patch Size: 7295 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060527/2afde609/cs2-ls50-full.bin From g3t4l...@hotmail.com Sat May 27 13:15:23 2006 From: g3t4l...@hotmail.com (Get A. Long) Date: Sat May 27 13:32:58 2006 Subject: [sane-devel] Parallel Port as SCSI In-Reply-To: <20060526150312.ga28...@fales-lorenz.net> Message-ID: Hi all, Thank you all for your helpful comments! I went out and bought a PCI-SCSI card (Adaptec AHA-2904) + a noname optical mouse + a set of El Cheapo SoundBlaster speakers + an Animatrix DVD . All for 16$. So, I feel it was worth the 400 yd walk. :) The system recognizes the Adaptec card, but still no luck with the scanner... :( Any tricks up the sleeve? Thanks in advance for any help! >From: Peter Fales >To: "Get A. Long" >CC: sane-devel@lists.alioth.debian.org >Subject: Re: [sane-devel] Parallel Port as SCSI >Date: Fri, 26 May 2006 10:03:12 -0500 > >Apple came out with a SCSI bus using DB-25 connectors. (I believe >they were the first to do this, and though it probably violates the >SCSI standards, they carry enough market weight that it has now become >a de-facto standard and you can now buy 25-pin SCSI cables and connectors) > >There are also various flavors of parallel port to SCSI converters >around. But, since your equipment actually says "SCSI" on the port, >that's probably what it really is. You would need to refer to the >documentation to know for sure. > >My Microtek scanner has both 25-pin and 50-pin SCSI connectors on it. But >both are true SCSI - I believe the 25-pin connector is there to cater >to Apple users. > >-- > >Peter Fales >Peter "at" fales-lorenz.net > >On Fri, May 26, 2006 at 03:31:19PM +0200, Get A. Long wrote: > > Hi again, > > > > Looking at the pictures at howstuffworks.com it is seems I do have a > > parallel cable, and two parallel ports (both DB-25, 'females') in the > > scanner. Funnily, on my scanner both these ports > > (http://computer.howstuffworks.com/parallel-port1.htm) are labelled >"SCSI" > > with large (8 mm) letters. > > > > The SCSI cable is illustrated at > > http://computer.howstuffworks.com/scsi1.htm but does not look like >anything > > I have and would not fit anywhere in the scanner, or the computer. So, I > > understand your surprise! :) > > > > >From http://computer.howstuffworks.com/parallel-port.htm : > > > > >Parallel ports can be used to connect a host of popular computer > > >peripherals: > > > > > > * Printers > > > * Scanners > > > * CD burners > > > * External hard drives > > > * Iomega Zip removable drives > > > * Network adapters > > > * Tape backup drives > > > > Apparently, parallel ports are used for scanners, and the UMAX Astra >1200S > > has it, despite labelled as SCSI. I guess then there is some software > > emulation or something like that somewhere, or did I misunderstand it? > > > > Thanks for any help on how to proceed before I buy that card! > > > > David > > > > _ > > Express yourself instantly with MSN Messenger! Download today it's FREE! > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > > > > -- > > sane-devel mailing list: sane-devel@lists.alioth.debian.org > > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > > Unsubscribe: Send mail with subject "unsubscribe your_password" > > to sane-devel-requ...@lists.alioth.debian.org _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-05-13 21:01, Giuseppe Sacco wrote: > another problem I think I found on this patch is at about line 1525 of the > patched file, where it is "i = (xfer_len_in && 0x3f);" while it should be > "i = (xfer_len_in & 0x3f);" with a single ampersand. Ok. Could you (or somebody else) post a patch that includes my and your comments? I.e. that can't break support for the other scanners? And that is tested with the LS-50? Thanks, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Giuseppe, Henning, > another problem I think I found on this patch is at about line 1525 of the > patched file, where it is "i = (xfer_len_in && 0x3f);" while it should be > "i = (xfer_len_in & 0x3f);" with a single ampersand. I'm afraid I haven't had time recently to do anything about the coolscan2 backend, and SANE-devel email delivery has been quite intermittent over here (I only got one copy of this email, for instance, although you sent it both to the list and to me separately). I'm so tied up in other things that I won't have time to work on SANE for a while, so I'd appreciate it if someone else took care of coolscan2 instead. I only have an LS-4000 and therefore can't really help with the LS-5*, which I've tried to get working several times by remote access (without success, though). The one thing I'd like to avoid is seeing SANE development retarded because of me. I'd like to believe that the backend is written in a reasonably readable way, so adding support for new scanners shouldn't be hard provided the new code is either tested for backward compatibility or made conditional based on the type of scanner. I've also found that it's a good idea to use case switches for this without specifying a default case -- gcc will then warn you if you've forgotten to list any type of scanner. Andras
[sane-devel] Nikon CoolScan IV and next sane release
Hi, another problem I think I found on this patch is at about line 1525 of the patched file, where it is "i = (xfer_len_in && 0x3f);" while it should be "i = (xfer_len_in & 0x3f);" with a single ampersand. Bye, Giuseppe
[sane-devel] Nikon CoolScan IV and next sane release
Hi,
On 2006-05-08 08:51, Giuseppe Sacco wrote:
> It was posted to this list on the 27th october 2005 by Ariel Garcia,
> here it is. There were some mail with comments on about the C code on
> that thread.
I've just forwarded the patch again to the backend maintainer.
Let's try:
coolscan2.c: In function 'sane_coolscan2_read':
coolscan2.c:1523: error: syntax error before '/' token
coolscan2.c:1525: error: 'i' undeclared (first use in this function)
[...]
Ok, "illegal" "//" comments. Fixed.
coolscan2.c: In function 'sane_coolscan2_read':
coolscan2.c:1524: warning: ISO C90 forbids mixed declarations and code
Fixed now.
More comments:
> + sanei_usb_attach_matching_devices ("usb 0x04b0 0x4001", cs2_attach);
> + sanei_usb_attach_matching_devices ("usb 0x04b0 0x4002", cs2_attach);
Which scanner is id 0x4002? According to our lists, it's the "Super
Coolscan LS-5000 ED". Does this also work?
> @@ -2324,14 +2352,14 @@
>s->resx_max = 256 * s->recv_buf[20] + s->recv_buf[21];
>s->resx_min = 256 * s->recv_buf[22] + s->recv_buf[23];
>s->boundaryx =
> -65536 * (s->recv_buf[36] + 256 * s->recv_buf[37]) +
> +65536 * (256 * s->recv_buf[36] + s->recv_buf[37]) +
> 256 * s->recv_buf[38] + s->recv_buf[39];
Well, I don't know nothing abot that backend but wouldn't this break
the already existing scanners?
>s->resy_optical = 256 * s->recv_buf[40] + s->recv_buf[41];
>s->resy_max = 256 * s->recv_buf[42] + s->recv_buf[43];
>s->resy_min = 256 * s->recv_buf[44] + s->recv_buf[45];
>s->boundaryy =
> -65536 * (s->recv_buf[58] + 256 * s->recv_buf[59]) +
> +65536 * (256 * s->recv_buf[58] + s->recv_buf[59]) +
> 256 * s->recv_buf[60] + s->recv_buf[61];
Same here.
Just to be sure, use
if ((s->type == CS2_TYPE_LS50) || (s->type == CS2_TYPE_LS5000))
here?
Bye,
Henning
[sane-devel] Nikon CoolScan IV and next sane release
Il giorno dom, 07/05/2006 alle 20.31 +0200, Henning Meier-Geinitz ha scritto: > Hi, > > On 2006-04-26 10:45, Giuseppe Sacco wrote: > > Is there any chance the next sane-backends release will include the patch > > for supporting CoolScan IV (LS-50 ED)? > > I haven't seen any response from the backend maintainer (Andras Major) > until now. Could you resend the patch to this list, please? It was posted to this list on the 27th october 2005 by Ariel Garcia, here it is. There were some mail with comments on about the C code on that thread. > > This patch was proposed before the current release was prepared and it was > > never changed/updated. The patch still have some problem, but it works for > > colour negative film. > > So there are no compilation/build problems any more? > > Are the Coolscan IV and LS-50 ED really identical? Our lists say, > "Coolscan V ED" and "LS 50 ED" are the same, but don't mention > Coolscan IV. I apologize since I wrote IV instead of V. The complete name I read on the scanner is "Nikon Coolscan V ED" and, on the rear, "Nikon LS-50 ED film scanner". Bye, Giuseppe -- next part -- A non-text attachment was scrubbed... Name: cs2-ls50-full.patch Type: text/x-patch Size: 7274 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060508/78d57ce8/cs2-ls50-full.bin From son...@mathematik.tu-chemnitz.de Mon May 8 13:29:14 2006 From: son...@mathematik.tu-chemnitz.de (Ralph Sontag) Date: Mon May 8 13:29:29 2006 Subject: [sane-devel] LiDE 500F: how to go further? In-Reply-To: <445d1051.5050...@pirsoft.dnsalias.org> References: <200605021417.39020.chri...@attglobal.net> <200605021830.56197.chri...@attglobal.net> <200605032139.27907.chri...@attglobal.net> <445d1051.5050...@pirsoft.dnsalias.org> Message-ID: Hi Pierre and list, first I want to thank for the help and the information. I put my data on http://www-user.tu-chemnitz.de/~sontag/sane/ > Please try the attached patch. It may already get scanimage past > initialization. If not, please also send a debug log without win98 > initialisation. OK, first time after patching the scanner makes terrible noise ... :-) It clatters very much ... A scan does'nt start. After replug the scanner croons, bot does nothing. I make some new logs, but where ends the win98-initalisation? See below ... > If you want to, i can send you some perl scripts and instructions on how > to use them. I don't understand all details of the protocol, so there > are some "unknown"s. I found some scripts under http://john.daltons.info/lide60/ If you have some scripts for the LIDE500F, they are welcome. But the scripts from John Dalton produce also some usefull information. I've put the raw files and the analysis with these scripts to http://www-user.tu-chemnitz.de/~sontag/sane/ (actual the last for lines: usblog-xp/00index.html analysed files from XP 500 k 8. 5. 2006 usbsnoopxp.bz2 raw file from XP770 k 8. 5. 2006 usblog-w98/00index.html analysed files from W98 450 k 8. 5. 2006 usbsnoopw98.bz2 raw file from W98 2.1 M 8. 5. 2006 ) How can I see, where the nessesary information starts? Then I can cut the parts before ... Thanks and Greetings! Ralph. -- Ralph Sontag | Str. der Nationen 62/B204 | 09107 Chemnitz | MIME | e-mail: son...@mathematik.tu-chemnitz.de | Tel. +49 371 531 31384 | welcome! |
[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-04-26 10:45, Giuseppe Sacco wrote: > Is there any chance the next sane-backends release will include the patch > for supporting CoolScan IV (LS-50 ED)? I haven't seen any response from the backend maintainer (Andras Major) until now. Could you resend the patch to this list, please? > This patch was proposed before the current release was prepared and it was > never changed/updated. The patch still have some problem, but it works for > colour negative film. So there are no compilation/build problems any more? Are the Coolscan IV and LS-50 ED really identical? Our lists say, "Coolscan V ED" and "LS 50 ED" are the same, but don't mention Coolscan IV. Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Is there any chance the next sane-backends release will include the patch for supporting CoolScan IV (LS-50 ED)? This patch was proposed before the current release was prepared and it was never changed/updated. The patch still have some problem, but it works for colour negative film. Bye, Giuseppe
