hah hah. now you see why i said to use the business card instead of 4x6 :) cat foo.log | perl spike3.pl > foo.out
less foo.out 1. do you see any sort of packets repeating every few seconds? should be a clear pattern, that is usually the system asking the scanner it's current status (paper status, lid status, buttons status, lamp hot status, etc) 2. go down through those repeated packets and look for a change in the contents of a packet from the scanner. that will be lamp getting hot, or you doing something to the scanner. see how the system responds... you should be able to get a feel for what a 'command' looks like. ie: on a fujitsu, you see something like: 31 byte command goes down to scanner, another block of varying length goes either back to the system or down to the scanner, and a 13 byte status command is read back from the scanner. so then you can build a list of 'this command writes a block, this one reads, etc' allan On Wed, 10 Dec 2003, Keith Watson wrote: > OK I've run a snoop session and got a 290Mb log file. > > What's the next step? > > Keith > > -- "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera
