[fprint] UareU 4000

[Daniel Drake]

Michael Cole wrote:
> Jono you are correct i posted back to the web site the fix that i created on 
> xmas day, I now have it working on my laptop. It works fine, and actually 
> looking at working on some additions later to the project. So far my only 
> input has been thoughts on the changes Daniel was proposing.

I think the best approach here is to maintain a list of known possible 
locations for the encryption control byte in the driver. Then at 
runtime, use some simple pattern matching to find the one that applies 
to that particular device.

If I remember correctly, the preceding byte is "ff" and the proceeding 
byte is "01" (e.g. ff 17 01). We could use a simple technique like this 
to find it.

Daniel