Prev: CVTRES : fatal error CVT1109: target machine "THUMB" requires "/WI
Next: DirectShow issue with Windows Mobile 5
From: gp on 2 Feb 2006 13:05 Guys, applied all the Authenticode settings Authenticode signature : YES Certificate:SHA-1 Hash=1049B790EDA3C369E9C206B44AF16B2657CC1555 Provison Device : NO and able to built pass thru driver so which is good created registry like [HKEY_LOCAL_MACHINE\Comm\PASS] "Group"="NDIS" "ImagePath"="newpassthru.dll" "NoDeviceCreate"=dword:1 and copied newpassthru.dll to \windows directory on emulator but it's not loading newpassthru.dll under device.exe tried ActivateDevice(_T("Comm\\PASS"), 0); but failing with acces denied anu idea??? "MSenne" wrote: > Here's a starting page on MSDN about SIDs: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceddk40/html/cxconStreamInterfaceDrivers.asp > > Here's the page on ActivateDevice that I mentioned above: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceddk/html/wceddkactivatedevice.asp > > That documentation will do a better job of explaining the entire > process of what you want to do. > -MSenne > >
From: gp on 2 Feb 2006 15:07 MSenne, for my first step i just want to run sample pass thru driver on emulator can you tell us what registry settings we need to create for that. -Gautam "gp" wrote: > Guys, > > applied all the Authenticode settings > > Authenticode signature : YES > Certificate:SHA-1 Hash=1049B790EDA3C369E9C206B44AF16B2657CC1555 > Provison Device : NO > > and able to built pass thru driver so which is good > > > > created registry like > > [HKEY_LOCAL_MACHINE\Comm\PASS] > > "Group"="NDIS" > "ImagePath"="newpassthru.dll" > "NoDeviceCreate"=dword:1 > > and copied newpassthru.dll to \windows directory on emulator but it's not > loading newpassthru.dll under device.exe > > tried ActivateDevice(_T("Comm\\PASS"), 0); but failing with acces denied > > anu idea??? > > > "MSenne" wrote: > > > Here's a starting page on MSDN about SIDs: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceddk40/html/cxconStreamInterfaceDrivers.asp > > > > Here's the page on ActivateDevice that I mentioned above: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceddk/html/wceddkactivatedevice.asp > > > > That documentation will do a better job of explaining the entire > > process of what you want to do. > > -MSenne > > > >
From: MSenne on 3 Feb 2006 09:58 gp, You may need to modify your source to export the DriverEntry entry point correctly. Download a free app called DependencyWalker and check out your .dll, it should export DriverEntry. That could be one problem, but also make sure you have installed the SDKCerts.cab on the emulator that you want to test on. The registry settings should be the same for the emulator vs. device, but put your settings in \COMM\PASSTHRU\ Your driver will add items to \COMM\PASS\ automatically, and when your driver gets loaded the instance will create \COMM\PASSTHRU1\ based on your original settings. -MSenne
From: gp on 3 Feb 2006 11:28 Can you tell me how to load NDIS.DLL file in dependency walker it's complaing and i am not able to locate NDIS.dll on my PC. 2) i have added passthru.def file in my project any addition step or any addition coding required for making DRIVERENtRY as export function 3) what to verify in dependency walker 4) how you guy's debug passthru driver using vs5.0 can you tell me steps. -gp "gp" wrote: > MSenne, > > Thanks for reply > > couple of questions for you > > 1) I am Using Sprint PCS 6700 device and i want to modify all the ip packets > going out and coming in from wifi or ev-do interfaces can it possible with > ndis pass thru driver? > > 2)please send me link for how to sign driver with a test certificate. > > thanks > > "MSenne" wrote: > > > The changes between 4.2 and 5.0 were small (2 or 3 changes in 2 or 3 > > files I believe) but commenting out the new 5.0 stuff didn't help with > > my problems. The source code is virtually the same except for those > > small improvements, which are not essential to working on CE5.0 > > systems. The difference is what libraries you link against. > > > > Knopper, > > > How can i access directly to the IM driver ? > > What do you want to do? I added code to make my 4.2 version a Stream > > Interface Driver and use IOControl codes to control it. If you want to > > read and write data I think that CreateFile might be the way, but I > > haven't done that, just basic comm using control codes. > > > > > And is there other upper protocol interface exitsted ? > > I don't quite understand what you mean, but if you mean are other > > adapters using your driver besides the TIACXWLN then the answer is No. > > If you have an internal WiFi card (which you do since you have the > > internal TIAC...) and an SDIO slot you can plug in a WiFi SDIO card and > > bind both adapters to your passthru driver (both will appear as subkeys > > of \\Pass\\). But WiFi is the only thing that binds. One of the small > > improvements in the CE5.0 code is a list that will skip adapters that > > won't bind such as PPTP, IR, ASYNCMAC, etc. > > > > > Can i send modified packets upper to the protocol interfaces to the application ? > > You have pointers to the actual packet data and have the ability to > > pass on or NOT pass on the data. You can also modify the packets > > before passing them on (up or down the stack, depending on whether you > > are in a MiniportSend or ProtocolReceive function). > > > > gp, > > You need to compile the passthru example as a DLL in Visual Studio 2005 > > or eVC++4.0 (usually you need VS2005 for WM5 projects, but this is a > > platform builder example and doesn't use any VS2005 libraries). > > You need to make sure it is exporting your DllEntry function properly > > (check exports with DependencyWalker). > > You need to sign your driver with a test certificate (this info is on > > various message boards and MSDN library or I can provide links). > > You need to put your driver in the \Windows folder and load the > > appropriate registry settings (mentioned above). > > If you have any specifc problems please let us know but that should get > > you started I hope. > > > > -MSenne > > > >
From: MSenne on 3 Feb 2006 13:22
You should be exporting the function OK with those steps. With the DLL in Dependency Walker the second pane from the top on the right should list DriverEntry. If that pane is blank then you have a problem. I can't debug the device driver so I'm using logging to provide the info I need. -MSenne |