Le jeudi 7 d?cembre 2006 22:59, Tymoteusz.Drozd a ?crit?: > Hi I have done scan under windows and i have decode of usbsnoop.log. > > This log should contain only preview scan but im not sure that. > Log may contain more then only preview scan and i dont know how > decode.sh and cmd.sh work in such situation. > Also im not sure how those scripts work on cuted logs(for example on log > which contain preview scan and interupted log of scan in 600dpi) > Cuted log is becuse my windows become very slow and unstable after > enabling of usbsnoop, > i tried 600 dpi scan but i have to giveup after 45 minuts and 220MB log > size. > In attachment i sent results of decode.sh & cmd.sh (bzip2 compressed). > I will read something more about those scripts and logs but i have busy > week before/after :>. > i think i should have time in next week to do more logs and read gl646 > documentation. > > regards
Hello, since data is logged in hexadecimal, it expands a lot in logs. So when logging high dpi scans, you have to reduce the target area to the smallest possible area. The log you sent ends too early. I guess the raw data has something scripts can't handle. Can you send me the raw usbsnoop.log of a color preview ? I'll try to understand what's going on. Regards, Stef