[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Suggestion
From: Alessandro Mandelli ####@####.#### Date: 14 Mar 2000 21:43:43 -0000 Message-Id: <38CEAE85.E5C40900@varicad.com> I would like to suggest this modification to be added to primax_scan.c after line 853 case 0x04: printf("\nLooks like a Storm Totalscan\n"); break; A question: On my storm totalscan the initialization routine (wakeup or powersequence, I don't know) goes fine until starting the actual scanning, then it exits with Floating point exception and the light does not switch off. But with "primax_scan -l off" it switches off fine. Then in file README it reads: The program is controled via a simple command line interface with several quite easy to remember parameters. To get full information about all the known parameters simply start the program with "./primax-scan -h" from your shell prompt. but it has to be "./primax_scan -h" I'm a no C-coder, but I will be glad to test any further advancements on my storm totalscan. Hope this helps. Ciao Alex. -- __ _ / / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable * / /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day* /____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Suggestion
From: Alessandro Mandelli ####@####.#### Date: 14 Mar 2000 21:47:09 -0000 Message-Id: <38CEAE85.E5C40900@varicad.com> I would like to suggest this modification to be added to primax_scan.c after line 853 case 0x04: printf("\nLooks like a Storm Totalscan\n"); break; A question: On my storm totalscan the initialization routine (wakeup or powersequence, I don't know) goes fine until starting the actual scanning, then it exits with Floating point exception and the light does not switch off. But with "primax_scan -l off" it switches off fine. Then in file README it reads: The program is controled via a simple command line interface with several quite easy to remember parameters. To get full information about all the known parameters simply start the program with "./primax-scan -h" from your shell prompt. but it has to be "./primax_scan -h" I'm a no C-coder, but I will be glad to test any further advancements on my storm totalscan. Hope this helps. Ciao Alex. -- __ _ / / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable * / /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day* /____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: Suggestion
From: Christian Ordig ####@####.#### Date: 16 Mar 2000 16:05:01 -0000 Message-Id: <XFMail.000316170043.chr.ordig@gmx.net> On 14-Mar-00 Alessandro Mandelli wrote: > I would like to suggest this modification to be added to primax_scan.c after > line 853 > > case 0x04: > printf("\nLooks like a Storm Totalscan\n"); > break; > Thanks. I'll add it to the code. > A question: > On my storm totalscan the initialization routine (wakeup or powersequence, I > don't know) goes fine until starting the actual scanning, then it exits with > Floating point exception and the light does not switch off. strange never had this problem... is there anybody out there also having this problem?? Are there any other programs, where you can see this effect? Sometimes this is a result of overclocking or computer parts which are used at their limits (Memory is a main thing which can cause troubles - as I had to find out with a computer some months ago...) > But with "primax_scan -l off" it switches off fine. > hmmm... ever tried to find out with a debugger where the program crashes? > but it has to be "./primax_scan -h" oops... damn SHIFT-key ;-) --- Christian Ordig | Homepage: http://thor.prohosting.com/~chrordig/ Germany | eMail: Christian Ordig ####@####.#### __ _ | / / (_)__ __ ____ __ | Why Linux? Because it is free, stable, and / /__/ / _ \/ // /\ \/ / | bugs can be fixed in source opposed to waiting /____/_/_//_/\_,_/ /_/\_\ | for a stable WinTendo from Micro$oft. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Suggestion
From: "J. v. Santen" ####@####.#### Date: 16 Mar 2000 20:09:17 -0000 Message-Id: <000701bf8f81$d5a9ee60$0501a8c0@athome> > > On 14-Mar-00 Alessandro Mandelli wrote: > > I would like to suggest this modification to be added to primax_scan.c after > > line 853 > > > > case 0x04: > > printf("\nLooks like a Storm Totalscan\n"); > > break; > > > Thanks. I'll add it to the code. Maybe you could add this to the code to: case 0x44 printf("\Looks like a Primax Colorado D600OEM\n"); break; I found out the error message I got: can not identify the scanner: error code 44 Although I don't now much about programming I found out it had something to do with the DEFINE MODE_F 0x0F line in primax_scan.h This value is 04 but just before switching the lamp on it got value 44, so I added the lines mentioned above and now the scanner is identified. > > A question: > > On my storm totalscan the initialization routine (wakeup or powersequence, I > > don't know) goes fine until starting the actual scanning, then it exits with > > Floating point exception and the light does not switch off. > strange never had this problem... is there anybody out there also having this problem?? As from driver 0.92a and above, primax_scan just freezes, the CCD is moving a millimeter and the does indeed not switch off. Nothing happens anymore. I can stop the process with ^C, after this primax_scan -loff works. I have mailed this before, but I have not found a solution yet, the scan output is still a black image, does anyone has a solution? I once read a mail from NicolasD, who has a Totalscan, and his output was also a black image. He doesn't not have a solution either. Joshua | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Suggestion
From: Alessandro Mandelli ####@####.#### Date: 16 Mar 2000 20:39:00 -0000 Message-Id: <38D140B2.8B841724@varicad.com> "J. v. Santen" wrote: > Maybe you could add this to the code to: > case 0x44 > printf("\Looks like a Primax Colorado D600OEM\n"); > break; > Actually I got error 44 either. Sorry it is not 0x04 but 0x44 even for the Storm Totalscan. But I don't get the scanning, not even the black scan. It just stops, reports the error and exits with light on. Ciao Alex. -- __ _ / / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable * / /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day* /____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |