Date: Thu, 29 Mar 2012 18:58:44 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-hackers@freebsd.org Cc: "Chris.H" <bsd.chris@yahoo.com>, Chris Rees <utisoft@gmail.com> Subject: Re: Reverse engineering; How to... Message-ID: <201203291858.44717.hselasky@c2i.net> In-Reply-To: <CADLo83_We6x7QnZBVCHOeSXcij8YpRWG7RGwu8f4%2B3%2BP8yG9Zw@mail.gmail.com> References: <942975b7-aa54-416d-b049-a50563bbf2a7@email.android.com> <CADLo83_We6x7QnZBVCHOeSXcij8YpRWG7RGwu8f4%2B3%2BP8yG9Zw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 29 March 2012 18:15:59 Chris Rees wrote: > On 28 Mar 2012 21:23, "Chris.H" <bsd.chris@yahoo.com> wrote: > > Greetings, > > > > I can unpack the setup file to extract the .sys files. While I _could_ > > utilize the ndisulator to load them, that's not my goal. Should I unpack > the .sys file, and attempt to decompile/disassemble it? Or attempt to load > it, and dump it from memory? Hi, You could install a USB sniffer and figure out how the basic programming goes. Search for USB snoopy on Google. Or, install the driver from within VirtualBox. Then sniff your device using the "usbdump" utility. This approach should give you a very clear picture about what is going on. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203291858.44717.hselasky>