tbronez wrote:-----------------------
I'd like to help you take a shot at developing a packet capture application for the Pocket PC. Like you, I'd be happy to get such an application running with ANY chip set. I've got a couple of different WiFi-enabled Windows CE devices. If you've got working code for Pocket PC 2002 (Windows CE 3.0), I don't expect it will be difficult to upgrade it to Windows Mobile 2003 (Windows CE 4.2). Assuming we can legally examine the source, of course. Contact me!
Tbronez,
I am very excited to hear that there is somebody else that would like to work on this with me. I will be privately communicating my email address with you.
I am very intersted in obtaining any course matterial that you might be able to share]www.ipaqdevelopers.com[/url], an HP organized site dedicated to helping developers develop applications for iPAQS. To gain developer access you either need to pay a $200 yearly subscription, or work very closely with HP and product development. The forums are not as usefull as I had hoped for, but I did get some information that might help.
Before CE4.0, it seems most manufacters needed to produced a .dll that applications could communicate with to find out certain properties of a network devices, as well as set them, with CE4.0, Pocket PC now supports NDIS5 interfaces. I know that NDIS5 doesn't directly support monitory or permiscuous mode for wireless connections. I've ready many reports in the forums of people who used to get values (such as signal level) from the provided manufacturer object; and as of CE4 that object no longer retreives a value - although no errors are thrown. Many people have changed their code to look at the .NET Compact Frameworks NDIS5 objects.
I personally have an iPAQ PocketPC h4100 series, this device uses Pocket PC 2003, the network card is provided by Texas Instruments although they won't support it, and directed me to HP. I have not been able to get an answer from anyone about weather or not the network card even supports monitor mode at the hardware level; let alone driver capabilities.
I have access to an iPAQ H3800 that runs Pocket PC 2002; That device also has a PCMCIA sleeve that I could get for testing, if we wanted to study how software runs in 2002, however I have no intentions of trying to write software that is backwards compatible with 2002. 2003 is my goal platform.
I have access to a Dell TrueMobile 1150 Wireless PCMCIA card, an 802.11B card that supports 40 and 128 bit WEP and uses the Prism2 chipset.
I have access to an Orinoco GOLD 802.11b wireless PCMICA card.
-------------------------------------------
I have done very very little work with Microsoft emmbedded C++, and even that work was done years ago. I know C/C++ from the conceptual level very well; however i've never actually used it over a long period of time so my syntax is VERY rusty and I am not very familiar with most class libraries or includes. I use VB.NET for most of my .NET programming, however I can READ C# code just as fast as I can read VB because I know the syntax and am familiar with the libraries.
--------------------------------------------
I do have access to a copy of emmbedded C++ but do not have it installed at this time. I don't have any good books or reading sources outside of the MSDN library at this time, so any reading recomendations would be appreciated.
--------------------------------------------
I would like to do most of my work with the equipment I have now, but come next month, I will have a small amount of financial rescources I can allocate to this project.
--------------------------------------------
I would appreciated if anybody has had experience cracking drivers for ANY platform, if they could contact me and provide for me the written resources they used to accomplish this task.
--------------------------------------------
The current step i'm on is this:
Deturmine which hardware is physically capiable of what I want to do, and what is not. Out of these possibilities, deturmine, based on the resources available, which equipment should be chosen as a test platform for an alpha product.
after I've deturmined this i'll go to work attempting to force the device into monitor mode and view packets at a very very low level.
Next I'll develop a class library with tools used to grab this information and organize it into objects that will be consumed more easily by my User Interface level code.
I'm not planning further ahead than this; as I don't want to widen my scope to far beyond where I am.
--------------------------------------
What prompted you to take a course on Driver Development? What types of projects have you completed? You can respond both publically or privatly, depending on if you wish to share with the entire group.
-17hz