[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Primax Colorado D9600
From: Miletics Tamas ####@####.#### Date: 16 Jun 1999 19:21:28 -0000 Message-Id: <Pine.LNX.4.10.9906162107290.5603-100000@r2.euroweb.hu> Hello ! I tried use the v0.2 program, and I am not happy. I have linux 2.2.9 (static lp) and a colorado direct 9600 whit these chips : GM71c4263cj60 (9815) and eicio93900 (9836e). Windows drivers : ... -rwxr-xr-x 1 root root 14167 Mar 31 15:13 vpmx2d.vxd* -rwxr-xr-x 1 root root 148992 Apr 3 03:42 viceo.dll* -rwxr-xr-x 1 root root 8628 May 23 17:16 twain.gid* -rwxr-xr-x 1 root root 8901 Jun 13 17:57 Hardware.ini* -rwxr-xr-x 1 root root 160 Jun 13 17:58 config.dat* ./primax_scan --verbose=99 --dim=1x1 --res=300 --lamp=on parse_options: debug level: 0x99 dimension: 1.0x1.0 inch resolution: 300 dpi lamp: on dimension: 300x300 pixel parse_options: switching lamp epp_on: Probing port 0378 SPP port present EPP 1.9 with hardware direction protocol wakeup: done timeout: 81 -- we are in trouble timeout: 81 -- we are in trouble timeout: 81 -- we are in trouble timeout: 81 -- we are in trouble :-( Scanner did not switch to EPP mode.....not compatible? timeout: 81 -- we are in trouble timeout: 81 -- we are in trouble .. timeout: 81 -- we are in trouble timeout: 81 -- we are in trouble init_timer: 929559413.569846 s wait until: 929559413769846 timeout: 81 -- we are in trouble ... timeout: 81 -- we are in trouble power_sequence: failed - TIMEOUT init_timer: 929559413.575014 s wait until: 929559428575014 epp_off: Miletics Tamas ------------------------------------------------------------------------ ===== EuroWeb Rt ===== Thomas Miletics - System Administrator ===== ===== H-1122 Budapest Varosmajor utca 13. ===== http://www.euroweb.hu ===== Tel.: +36 1 2244000 Fax: +36 1 2244100 ------------------------------------------------------------------------ On Wed, 16 Jun 1999, Christian Ordig wrote: > > On 15-Jun-99 Christoph Adomeit wrote: > > Hmm, > > > > my D600 doesn't say anything, even after changing the above > > lines. The Problem might even be with my kernel/ or hardware > > setup. I enabled SPP/EPP in my Bios, but when I run > > primax_scan -lon I receive the following message: > > > > parse_options: > > lamp: on > > dimension: 0x 0 pixel > > parse_options: switching lamp > > Probing port 0378 > > SPP port present > > PS/2 bidirectional port present > > EPP 1.9 with hardware direction protocol > > > >:-( > > Scanner did not switch to EPP mode.....not compatible? > > > > Any ideas what I can try ? What modules besides parport > > should be loaded ? BTW: I still run a 2.1.132 kernel on > > this machine.... > > > Well, > > I had some problems with my printer, when I compiled the parport stuff as > module.... (Kernel 2.2.x). I didn´t try the scanner with this config, but when > I compiled the parport stuff directly into the kernel the printer works (and > the scanner also... ;-) > > Not sure if this helps... > > But I think the really significant difference between you and Colin is the > Windows95 driver... (I think your D600 driver is named vpmxd2.vxd, isn´t it?) > > Marco found out that there are quite large differencies between the vpmxd and > the vpmxd2 driver... Perhaps Colin´s scanner is named D600, but is not an > original one. > > Knowing the IC types would help us very much! > > Thank you. > > > --- > Christian Ordig | The Primax Scanner Driver Project for Linux/UN*X | > Germany | http://thor.prohosting.com/~chrordig/Primax/ | > __ _ | | > / / (_)__ __ ____ __ | Why Linux? Because it is free, stable, and | > / /__/ / _ \/ // /\ \/ / | bugs can be fixed in source opposed to waiting | > /____/_/_//_/\_,_/ /_/\_\ | for a stable WinTendo from Micro$oft. | > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Primax Colorado D9600
From: Dobrica Pavlinusic ####@####.#### Date: 16 Jun 1999 19:50:27 -0000 Message-Id: <Pine.OSF.4.00.9906162138210.27180-100000@barok.foi.hr> On Wed, 16 Jun 1999, Miletics Tamas wrote: > Hello ! > > I tried use the v0.2 program, and I am not happy. > I have linux 2.2.9 (static lp) and a colorado direct 9600 whit these chips > : GM71c4263cj60 (9815) and eicio93900 (9836e). [...snip...] > wakeup: done > timeout: 81 -- we are in trouble > timeout: 81 -- we are in trouble > timeout: 81 -- we are in trouble > timeout: 81 -- we are in trouble I had the same problem. It seems that our scanner isn't really supported with 0.2 version of driver. Some time ago, Marco was really helpfull in trying to make my scanner to work, but my lack of SoftIce knowledge kept me off. However, nowadays I installed bochs and I'm thinking about dumping our scanner communication with parallel port to file under it. However, we now have NDA, so I'm not completly sure it this would help at all. Should I try to dump communication or just wait for NDA to came with spec? Dobrica Pavlinusic ####@####.#### ####@####.#### Unix addict. Internet consultant. http://www.foi.hr/~dpavlin | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Primax Colorado D9600
From: Marco Foglia ####@####.#### Date: 16 Jun 1999 21:58:56 -0000 Message-Id: <3768142E.88E4E248@physik.unizh.ch> Miletics Tamas wrote: > I tried use the v0.2 program, and I am not happy. > I have linux 2.2.9 (static lp) and a colorado direct 9600 whit these chips > : GM71c4263cj60 (9815) and eicio93900 (9836e). The central ASIC (EICI093900) is not the same. I have an EICI072100. There is much confusion around. I am talking with Primax to make things clear. The GM71c4263cj60 is just the memory. It is 256K x 16, 60ns and it is from LG Semicon (http://www.lgsemicon.co.kr/dram/dram/dram.htm). The ADC part number would be (more) interesting. > -rwxr-xr-x 1 root root 14167 Mar 31 15:13 vpmx2d.vxd* > -rwxr-xr-x 1 root root 148992 Apr 3 03:42 viceo.dll* As a general rule: If the Win driver is using vpmx2d.vxd the current version is not supporting your scanner. Marco | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Primax Colorado D9600
From: Marco Foglia ####@####.#### Date: 16 Jun 1999 22:17:48 -0000 Message-Id: <37681898.914B3C09@physik.unizh.ch> Dobrica Pavlinusic wrote: > However, nowadays I installed bochs and I'm thinking about dumping > our scanner communication with parallel port to file under it. However, we > now have NDA, so I'm not completly sure it this would help at all. Should > I try to dump communication or just wait for NDA to came with spec? I tried bochs several times a long time ago without success. The traces were done by a combination of Softice/W32dasm and a modified vpmxd. The modified vpmxd is only working in EPP-mode because i used the nibble-mode part for the logging code. If you can dump the scanner communication with bochs, do it, but don't waste too much time. Marco | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |