NdisMEthIndicateReceive - porting to ndis 6.0

TheMSsForum.com: The Microsoft Software Forum

The MSS Forum ‹ Drivers
- Archive
  - Biz
  - MCSE
  - CRM
  - Drivers
  - Framework
  - ADO
  - ASP
  - Compact
  - Forms
  - Dotnet
  - C#
  - VB
  - FontpageGen
  - Excel
  - WorkSheet
  - Exchange
  - Setup
  - Fox
  - Fontpage
  - ASP
  - IIS
  - Entourage
  - Money
  - Messanger
  - PocketPC
  - Powerpoint
  - Project
  - Publisher
  - Excel
  - VB
  - Security
  - Portal
  - Services
  - SQLServerDev
  - SVCS
  - SQLServer
  - VB
  - VC
  - MFC
  - ExcelGen

- Previous
  - 1
    - Padding ethernet packet (net buffer list) with NdisRetreatNetBufferDataStart !? Hi, I m padding ethernet packet (= net buffer list) to make it 64B long. If I use NdisRetreatNetBufferDataStart then the data space allocated in net buffer list will be filled up with zeros? Please reconfirm.. Thanks a ton in advance! Shweta Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92871
  - 2
    - Evenafter IRR is set, the interrrupt service routine didn't execute Hi All, We have a board which has it's own 8253[PIT] and 8259[PIC]. The 8253 is configured to raise a timer interrupt on every 20ms and 8259 is configuered to fw that request to the device driver. In normal case, the things work fine, 8253 raises interrupt in every 20ms and driver interrupt service routine is executed. The problem happens if the application run for long time[ >1day], driver interrupt service routine is never called-up, eventhough the 8253 raises the timer interrupt. So I added some diagnostic code to dump the values of the 8253 and 8259 internal registers during failure cases. This shows that 8253 is counting and re-counting without any problem. IMR registers is not masking the timer interrupt, however IRR register shows that the bit which corresponds to the timer interrupt is already set, ISR register is not having that bit set. Based on this, I conclude that, 8253 raises the interrupt and IRR is set correctly, but 8259 is waiting for the CPU to sent the INTA, but it didn't happen, so it couldn't set ISR and fw the request to the driver. The question I have here is, What should be done to identify why the CPU didn't sent INTA? any other ideas? Thanks. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92870
  - 3
    - device driver upgrade problem Hi, I have a problem with upgrade. I have a package which includes updated .inf and .sys files. From log I see that files are copied to drvstore and installation/upgrade is done (fresh installation works fine) - but after that (in upgrade) difxapp finds another copy of the driver with same component ID and uninstalls it. Result is that when I try to do upgrade difxapp uninstalls my driver. The reason why it finds another copy of the driver is that in upgrade it copies files to different folder in drvstore than in fresh installation. Folder name includes a code or ID number (I'm not sure what code is it). So my question is ... should it behave like this ? why it copies files to different folder ? and what should I do to avoid this ? My driver is not signed (yet), I have mainly tested with XP (also win2000) and I'm using installshield 12 to make a package (but I dont think the problem is there ...). Any suggestions are welcome :) Jussir Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92869
  - 4
    - fail to write files in SystemRoot in Vista Hi, I have a driver that works well in WinXP. In this driver, device property page write some information in systemroot directory. (just like logging files). But in Vista, the property page fails to write because it has no authority, so some relative feature can't work. 1. I've tried to change the writing file to non-system directory, but I found that INF failed to use dirIDs failed. [DestinationDirs] CopyFiles.ProperPageLog = 53, VendorDir ;try to copy to user profile directory the 53 dirID works in winXP but no in Vista, I've tried "25 (Shared Directory)", "16427 (Program Files\Common)"...they all fail in Vista. 2. another question, if I copy the files in installation package, how to access this diretory in dirver (ex. "16427 Program Files\Common")? As far as know, the \\SystemRoot refer to "c:\windows", but can't access other directory. I think absolute directory like \\dosdevices\\c:\\ is bad idea. I'm not sure I'm in right way, please help me and thanks! Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92868
  - 5
    - peculiar observation with AMD64Bit and Intel Dual Core Machines, in Low Powered States Hi, I Have a peculiar observation with AMD64Bit and Intel Dual Core Machines in low Powered States. Operating System : WinXP SP2. 32 - Bit OS Machine : Intel PIV, Intel Chip Set With the above configuration machine, Go to low powered state, Disconnect the any USB device in the low powered state, ReConnect the USB device in the low powered state, and then come back from the low powered state. Under these conditions i get a if i try to access the device as soon as i am back from the low powered state i get a STATUS_DEVICE_NOT_CONNECTED status and then the driver unloads and reloads and works fine. But the same procedure if i follow with the following machine, Operating System : WinXP SP2. 32 - Bit OS Machine : Either Intel Core Duo or AMD 64 i do not get a STATUS_DEVICE_NOT_CONNECTED instead i get a STATUS_SUCCESS and device functions properly. Why is this happening ??? Thanks and Regards, Neo Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92867
  - 6
    - Padding ethernet packet (net buffer list) with NdisRetreatNetBufferDataStart !? Hi, I m padding ethernet packet (= net buffer list) to make it 64B long. If I use NdisRetreatNetBufferDataStart then the data space allocated in net buffer list will be filled up with zeros? Please reconfirm.. Thanks a ton in advance! Shweta Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92866
  - 7
    - Evenafter IRR bit is set there is no Interrupt service routine execution... We have a board which has it's own 8253[PIT] and 8259 [PIC]. The 8253 is configued to raise an interrupt in every 20ms. Everything works fine, However in long run the driver stopped to get the timer interrupt. So I added some diagnostics code which dumps the internal registers of 8253 and 8259 during the failure case. This log shows that the 8253 is counting correctly. The IMR is not masking the timer interrupt and the bit corresponds to the timer interrupt is set in the IRR. The timer interrupt bit is not set in the ISR register. So conclusion I made here is that, 8253 raised on timer interrupt and corresponding bit in IRR is set and it's waiting for the CPU to sent the INTA, however the CPU is not acknowledging, so driver interruptServiceRoutine is not called-up. Question I have here is, What should be done to identify why the CPU didn't send INTA? What should be done to identify why the InterruptServiceRoutine is not called-up? Thanks. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92864
  - 8
    - problem about 2 Notification Events Dear all: I create 2 event objs, one in Application and the other in Driver.I ues them to notify each other. 1) the App create a new thread to wait for the event Driver will set 2)Driver sets the event that the thread waits for, then Driver turns to wait for the other event <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< In Application : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< unsigned ThreadId; DWORD BytesReturned; // to get the Device handle // hDevice=CreateFile(MY_DEVICE_NAME,GENERIC_READ | GENERIC_WRITE,0,NULL,OPEN_EXISTING,FILE_ATTRIBUTE_NORMAL,NULL); // //create an event // hShareE = CreateEvent(NULL,TRUE,FALSE,NULL); // //send a IRQ to driver with the event handle // DeviceIoControl(hDevice,SHARE_EVENT_CRT,&hShareE,4,NULL,0,&BytesReturned,NULL); // //create a new thread // _beginthreadex(NULL,0,&ppppp,(void*)hShareE,0,&ThreadId); <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< In a new thread: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< unsigned __stdcall ppppp(void*(hShareE)) { while(1) { //wait // WaitForSingleObject((HANDLE) hShareE,INFINITE); // //notify user // ::MessageBox(NULL,"Event Set!",NULL,MB_OK); ResetEvent((HANDLE) hShareE); } _endthreadex(0); return 0; } <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< In Driver: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< //event name ,handle, pointer // WCHAR wEventNameBuf[]=L"\\BaseNamedObjects\\SharedEvent"; UNICODE_STRING uEventName; PKEVENT pEventApp,pEventDrv; HANDLE hEventDrv,hEventApp; // //mutex // KMUTEX H_FuncMutex; //IRQ about creating event // case SHARE_EVENT_CRT: RtlCopyMemory(&hEventApp,pIrp->AssociatedIrp.SystemBuffer,4); // //get the pointer from handle of event that the App created // ObReferenceObjectByHandle(hEventApp,EVENT_MODIFY_STATE,*ExEventObjectType,pIrp->RequestorMode,(PVOID*) &pEventApp,NULL); //driver creates the other event // RtlInitUnicodeString(&uEventName,wEventNameBuf); pEventDrv = IoCreateNotificationEvent(&uEventName,&hEventDrv); if(pEventDrv != NULL) KeClearEvent(pEventDrv); break; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< A hook func in Driver: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< //get in Critical section // KeWaitForMutexObject(&H_FuncMutex,Executive,KernelMode,FALSE,NULL); // //set the event to notify the new thread // KeSetEvent(pEventApp, IO_NO_INCREMENT, TRUE); //wait for the other event // KeWaitForSingleObject((PKEVENT)pEventDrv,Executive,UserMode,0,0); KeClearEvent(pEventDrv); //get out Critical section // KeReleaseMutex(&H_FuncMutex,FALSE); In the hook func, KeSetEvent is successful, but the thread is not active. and, if i delete the followings: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< //wait for the other event // KeWaitForSingleObject((PKEVENT)pEventDrv,Executive,UserMode,0,0); KeClearEvent(pEventDrv); <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< the thread will be active. somebody know what happen, and how to solve it. Thank you!! Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92856
  - 9
    - re:Cant_find_a_driver_this_site_will_Ask_MDREPAIRS Cant_find_a_driver_this_site_will_Email_Mark http://www.mdrepairs.com Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92854
  - 10
    - re:Cant_find_a_driver_this_site_will_Ask_MDREPAIRS Cant_find_a_driver_this_site_will_Email_Mark http://www.mdrepairs.com Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92853
  - 11
    - How to get ShutdownType and SystemState in kmdf driver? WDM power management irp provides ShutdownType and SystemState information. But the kmdf power management callback functions EvtDeviceArmWakeFromSx and EvtDeviceDisarmWakeFromSx don't have these information. How can the kmdf driver power management functions get these information from kmdf if it need these information? -- johnzchen Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92852
  - 12
    - How to track window changes ? Hi, I need to have a user application receive some notification whenever it's visibility changes. For example, I need to know when the window becomes partially or completely covered up, when something that had obscured part of the window is removed making more of the window visible, or when the window is destroyed, etc. I'm using windows XP / XP embedded. I am also writing a KMDF driver for a device that is display-related, but I am not writing, nor can I modify the display driver itself. Here is the original approach: The user app could pass the window handle to the driver. The driver could call EngCreateWnd, and specify a WNDOBJCHANGEPROC callback that would get invoked when GDI changes the window visibility. The driver could pass a list of visible rectangles back to the user app. The problem with this approach is that I don't have access to any of the SURFOBJ information that is needed by the EngCreateWnd call to create the window object. I have also considered the method identified in "Tracking Window Changes" http://msdn2.microsoft.com/en-us/library/ms797870.aspx but the application's ExtEscape call needs a device context. From what I can tell, this "Device Context" is different from a device context which I define for my device. That makes me think that the DrvEscape will be invoked in the display driver, not my driver. Does anyone know how a driver can get the needed information to do this ? Or better yet, is there possibly something we are missing in the user mode interface that can notify an application when when window visibility changes? (This would be more that just a Paint Event) Thanks in advance, Jay Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92850
  - 13
    - DTM: INFTest failure Hi All, I'm trying to complete "Driver Reliability" tests on the driver using DTM on Vista x86. And every time I got INFTest failure with the log like following: === Inftest is running ... Command line: "C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91\i386\inftest.exe" -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91 -f /LG -l C:\Windows\inf\ Current directory : C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91 Passing extra flags to Chkinf: /LG FindPerl : ChkinfPath = C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91 FindPerl : perl.exe found on the system! Setting chkinf directory as : C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91\chkinf.bat Processing command line ... Find First File operation failed! Bailing out ... Could not find user specified INF files. Bailing out ...Could not expand user supplied lists of infs into individual filenames. Running InfTest : Could not expand user supplied list of infs. Clearing list of infs ... Processing command line ... DONE! The inftest check failed to run. Please check the debug logs for more information. === Also, I cannot find any ways to contact DTM support team directly. Any help very appreciated! Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92844
  - 14
    - Removal of Protocol driver with Device Driver Is there an approved method for a driver to request the removal of a proprietary network protocol which is installed with the driver? The reason I ask is that I wish to change the interface name the protocol uses, and while the protocol gets installed with the driver, it does not appear to get uninstalled with the driver. When an updated driver is later installed, the protocol associated with it does not appear to get installed because the old protocol from the previous driver is still resident. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92829
  - 15
    - Driver unInstallation problem on Vista/XP - 64 bit Hi List, Basically I have a echo driver with the property (start type = 1). I am using DIFx API to install and unInstall this driver. Installation seems to go through fine. after this, for loading the echo driver, I reboot the system and drivers get loaded. Now if I try Un-Installing the drivers, it fails to do so. When I see the detailed log, it says "Trying to unload the driver", "retrying to unload the driver" and finally it gives up saying "you need to reboot the system". However as per the requirement I should be able to install and uninstall the drivers without reboot. My question is what may be the reason for this failure? Also Is there a way to tell DIFx API not to try unloading the driver; but simply uninstall them. Any pointers would be of great help. TIA Regards Jatin Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92825
  - 16
    - Error No 800B0101 While Using DifXApi.dll Hi, I have been trying to install a particular device driver using difxapi.dll on vista32 platform. Although i am able to load the dll but when i call the "DriverPackageInstallA" with the path of the inf file and other parameters, i am getting an error message 0x800B0101. I looked out for this error and found out that it means "A required certificate is not within its validity period.". But i am unable to understand how it relates to my module. Can anyone please tell me where the problem could be? Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92824
  - 17
    - problem about 802.11 miniport driver indicating NDIS_STATUS_DOT11_CONNECTION_COMPLETION I have a 802.11 miniport driver for Vista, and my user mode app use a private OID to transfer all the other OIDs(such as OID_DOT11_RESET_REQUST) to the miniport driver, to query or set. Then the app send OID to the miniport "bypass" the nwifi IM driver. For some reason I must use a app to control my miniport instead of ACM. The problem is: I use my app to make the driver connect a AP, the miniport driver connect the AP and indicate NDIS_STATUS_DOT11_CONNECTION_COMPLETION as well as NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION(I can see it by dbgview, auth and assoc is OK), but if I use ipconfig, it show that the media is disconnect. But I use the Vista's ACM to connect the AP with same miniport driver, and the driver also indicate the NDIS_STATUS_XXX, ipconfig show that media is connected. Why? Do the nwifi IM driver need some else information to decide the media state? Because of "bypass" the IM driver? I tried to send OID directly to IM, but some OIDs failed, such as OID_DOT11_RESET_REQUST. It seems that the IM driver do NOT allow some OIDs to get to miniport. Thanks for your help! -- Arthur Tu best regards Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92822
  - 18
    - Kernel Mode Encryption API's : Help Needed. I want to do kernel mode AES encryption beacuse i am developing a encryption filter driver. Is there any k-mode library available for the same? Plz Help. Regards, Aman. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92821
  - 19
    - Porting of TransferDataHandler function to ndis 6.0 Hi, I have this doubt regarding porting TransferDataHandler function that was previously getting registered to ndis 5.1 through NDIS_MINIPORT_CHARACTERISTICS -> TransferDataHandler. i just want to reconfirm if in NDIS 6.0, its getting registered through NDIS_MINIPORT_DRIVER_CHARACTERISTICS->MiniportOidRequest- >NDIS_OID_REQUEST->RequestType= NdisRequestTransferData . DDK says that this request type is redundant. Thanks a ton in advance! shweta Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92820
  - 20
    - update: WDK 6000 build.exe dependency issue I reported this issue to the NDIS team during our weekly call with MSFT. Now I got an ACK that the WDK team is able to reproduced in Redmond. It's being taken care of. -- Calvin Guan (expiring DDK MVP) Sr. Staff Engineer NetXtreme NTX Miniport Broadcom Corporation Connecting Everything(r) Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92796
  - 21
    - FilterAttach gives 0x80070032, different results on different computers, same code given usermode program tester.exe and kernel minifilter tester.sys and tester.inf, and cleaning out all tester.* from c:\winnt\*, and removing all pertinant "tester" fom the registery, using the same compiled code on two machines, I install the usermode program (which is a service) and the driver with: sc create testerService binpath= c:\tester\tester.exe rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 c:\tester \tester.inf sc queryex testerService sc queryex testerDriver and both are loaded. Everything else I can think of being equal, upon starting the service, one machine calls FilterAttach() successfully and one machine receives 0x80070032 from FilterAttach() !!! What to do!? it appears that the returned hr is encoding ERROR_NOT_SUPPORTED, so what to do! I can find ZERO documentation on this behavior short of my previous and somewhat related post. the difference being that this error is being received not on a single attempted FilterAttach(). Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92795
  - 22
    - FilterAttach gives 0x80070032, different results on different computers, same code given usermode program tester.exe and kernel minifilter tester.sys and tester.inf, and cleaning out all tester.* from c:\winnt\*, and removing all pertinant "tester" fom the registery, using the same compiled code on two machines, I install the usermode program (which is a service) and the driver with: sc create testerService binpath= c:\tester\tester.exe rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 c:\tester \tester.inf sc queryex testerService sc queryex testerDriver and both are loaded. Everything else I can think of being equal, upon starting the service, one machine calls FilterAttach() successfully and one machine receives 0x80070032 from FilterAttach() !!! What to do!? it appears that the returned hr is encoding ERROR_NOT_SUPPORTED, so what to do! I can find ZERO documentation on this behavior short of my previous and somewhat related post. the difference being that this error is being received not on a single attempted FilterAttach(). Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92794
  - 23
    - FilterAttach gives 0x80070032, different results on different computers, same code given usermode program tester.exe and kernel minifilter tester.sys and tester.inf, and cleaning out all tester.* from c:\winnt\*, and removing all pertinant "tester" fom the registery, using the same compiled code on two machines, I install the usermode program (which is a service) and the driver with: sc create testerService binpath= c:\tester\tester.exe rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 c:\tester \tester.inf sc queryex testerService sc queryex testerDriver and both are loaded. Everything else I can think of being equal, upon starting the service, one machine calls FilterAttach() successfully and one machine receives 0x80070032 from FilterAttach() !!! What to do!? it appears that the returned hr is encoding ERROR_NOT_SUPPORTED, so what to do! I can find ZERO documentation on this behavior short of my previous and somewhat related post. the difference being that this error is being received not on a single attempted FilterAttach(). Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92793
  - 24
    - DriverEntry return question After my driver is installed, it has discovered at DriverEntry time that the registry has not been set up correctly, it returns STATUS_REGISTRY_CORRUPT and the XP Home Sp2 system crashes.... bummer. What should be returned from a driver if the driver cannot initialize and wants to be taken out of the game? -- Gak - Finecats Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92790
  - 25
    - Error Handling In Port Monitor Is it appropriate to pause or cancel print jobs under error conditions (via SetJob) from a Port Monitor or Language Monitor rather than just return a null to the Spooler for StartDocPort / WritePort / EndDocPort? Is there a specification of what the spooler expects the PM / LM to do under error conditions? Thanks for your help! Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92789
- Next
  - 1
    - Protocol Removal Is there an approved method for a driver to request the removal of a proprietary network protocol which is installed with the driver? The reason I ask is that I wish to change the interface name the protocol uses, and while the protocol gets installed with the driver, it does not appear to get uninstalled with the driver. When an updated driver is later installed, the protocol associated with it does not appear to get installed because the old protocol from the previous driver is still resident. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92781
  - 2
    - Will DMA transfer diable the CPU completely as if it has been revoved from the socket? Below is my understanding, but I am not sure of its validity. I hope to get some comments from you. Provided that a program want to start a DMA transfer. 1, CPU sends a start command to a DMAC (DMA Controller); 2, The DMAC signals the CPU through the HOLD pin and waits for the CPU's acknowledgement; 3, CPU signals the DMAC through the HLDA pin; 4, Upon receiving HLDA, the DMAC starts to DMA transfer. From now on, the CPU stops all its activities. Until the DMA process is finished, all the interrupts can not get responses. But, the CPU's internal status are kept, and all the interrupts' status are also kept. 5, Upon finishing the DMA transfer, the DMAC deactivate the HOLD pin, the CPU continues to execute its instructions. My question is the same as the title: Will DMA transfer diable the CPU completely as if it has been revoved from the socket? Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92779
  - 3
    - HID minidriver with multiple report descriptors Hi, I write a HID minidriver with standard Mouse and Keyboard report descriptors. It is based on vhidmini in Windows Server 2003 DDK. The driver work fine and I can read/write the report from the device. The Device Manager shows it is HID-compliant device in HID class, but the Mouse Class and Keyboard Class have none. How should I do so that it can be a mouse device and keyboard device? Should I modify the INF file? My driver's INF is almost same as the vhidmini's. Thanks Ron Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92769
  - 4
    - page fault when KeResetEvent runs. dear all! I use share event in communication between app and driver. the follows are my source codes : void ppppp(PVOID event) { KeWaitForSingleObject((PKEVENT)event,Executive,UserMode,0,0); //......wait for the event...... } ...... WCHAR wEventNameBuf[]=L\"\\\\BaseNamedObjects\\\\SharedEvent\"; UNICODE_STRING uEventName; PKEVENT pEvent; HANDLE hEvent,hThread; ...... case IOCTL_******: RtlInitUnicodeString(&uEventName,wEventNameBuf); pEvent = IoCreateNotificationEvent(&uEventName,&hEvent); KeResetEvent(pEvent); RtlCopyMemory(Irp->AssociatedIrp.SystemBuffer,&hEvent,4); PsCreateSystemThread(&hThread,THREAD_ALL_ACCESS,0,0,0,ppppp,pEvent); In Applicationï¼? if(!DeviceIoControl(hDevice,IOCTL_******,0,0,&Handle,4,&Bytes,0)) MessageBox(\"DeviceIo Error!\"); esle{ wsprintf(str,\"%x,%x,%x\",hDevice,Bytes,Handle); MessageBox(str); if(!SetEvent((HANDLE)Handle)) ...... } but when it runs in KeResetEvent and KeWaitForSingleObject , a reg points to 0,then page faults. somebody know what happen, and how to solve it. Thank you!! Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92768
  - 5
    - IM(passthru) installation Hi All After install the IM driver , appear the "passthru driver" in "Network Properties" menu. then anyone can remove it easly. How to install the IM driver whitout appear "passthru driver" in Netwrok properties menu? Thanks. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92765
  - 6
    - Difxapp error list I've got a Difxapp error message in the log of my MSIEXEC output. My drivers and registry settings that are in the INF are not getting set correctly. I've got a 0x424 error (somebody must know what this means), but I don't know where to find this information? -- Gak - Finecats Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92758
  - 7
    - cancel-safe queues and Cleanup Assume a driver working with the same logic as the DDK Cancel sample implements. Suppose that one routine just removed a pending irp from the queue and then the Cleanup dispatch is called. Because the irp is not in the queue anymore, Cleanup won't find it and the irp won't be cancelled. In most cases this won't be a problem, the irp will be completed soon enough. But in some devices it is possible that the irp can't be completed for some reason. Then the irp would keep pending, possibly inserted again in the cancel-safe queue. In extreme cases the irp might be never completed, and it won't ever be cancelled either. Am I missing something, or do I need to take special care if irps removed from the queue might be not possible to complete? Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92751
  - 8
    - Propagating the Pending Bit "Any time a driver handling an I/O request returns the response of the next-lower driver, the value of the pending bit in its I/O stack location (SL_PENDING_RETURNED in the Control field of the IO_STACK_LOCATION structure) must be the same as that of the next-lower driver. " ...of course they are the same! "If the driver does not set an IoCompletion routine, the I/O Manager automatically propagates the value of the bit, freeing the driver of this responsibility. However, if the driver sets an IoCompletion routine, and the next-lower driver returns STATUS_PENDING, the current driver must mark its own I/O stack location as pending. " if the driver sets an IoCompletion routine, means it has sth need to cleanup before the irp is released, it is reasonalbe bcz device stack is a nesting arch. pls correct me. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92742
  - 9
    - ddkbuild.bat Vista DDK (6000) and making brower files (currently NOT) I searched for ddkbuild and DDK so I did my due diligence. We are upgrading from OSR DDKBUILD.BAT V5.1 to OSR DDKBUILD.BAT V6.10 and more importantly from DDK2600 to DDK6000. Yes I know, I know it was last released in 2002! The project is an XP NDIS 5.1 miniport driver. Now I am trying to coax a (*.bsc) file out of this and having no joy. The 6000 DDK says that I can not define: BROWSER_INFO=1 BROWSERFILE=drivername.bsc anymore. I saw some discussion from Mark Roddy about <ddkroot>\bin\verify.src and defining USER_ENV_BROWSER_INFO=1 to turn the error off but that still does not get me my drivername.bsc (no joy) It was in http://www.techreplies.com/drivers-43/visual-studio-net-driver-wizard-339156/ Does anyone know the magic invocations required to get a browse file. We really like using ddkbuild.bat and VS6 to manage the development environment. Thanks -Ron- Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92740
  - 10
    - Calling CreateFile / DeviceIOControl from a limited user account I need to be able to open a handle to a driver and communicate with it via IOCTLs. This needs to be done from a limited user account on Windows XP Pro SP2. I have a solution working when running from an administrator account but I can't get it to work from the limited user account and I cannot find any security settings the allow access. Is there a security setting of some sort that I can set to allow this functionality? Thank you. -- Matthew Townsend General Dynamics Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92737
  - 11
    - PsCreateSystemThread on Win2k The DDK states that PsCreateSystemThread under Win2K must be called from the system process context only. However checking older DDK versions and older samples seem to condtradict that statement. This suggest that it can, but it shouldn't perhaps because it exposes a bug or a security hole in Win2k. So the question is if it is still possible to call PsCreateSystemThread from an abritrary process context, perhaps taking special precautions. Yeah, I know that I can schedule a work item to create the system thread. But this creates an overly sinchronization complication between the dispatch routines, the work item and the system thread. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92726
  - 12
    - Tracking Info in 3 Documents At Once Hello All I have a question regarding trying to have 3 seperate documents, where when you make a change in one, the other two automatically get updated. I know there is a function in Excel that perfroms this task; however, it only allows one person to work on the document at one time. I need to be able to have this function that allows multiple team members to update one document where the other two are automatically updated as well. Do you know of any applications or databases where I can set this up? I would appreciate any feedback. -- Thanks a lot, Ilona -- Thanks a lot, Ilona Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92724
  - 13
    - Signing a Windows XP driver Hi, I'd like to sign our driver so it can be easily installed via the DIF for MSI. I tried several hours to obtain any USEFUL information on the winqual sites (which seem to be all updated for Vista, but I don't need Vista now). Usually posts like mine get answered by these two links: "Driver Signing Requirements for Windows" http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx "Summary of Windows Kernel-mode Driver Signing Requirements" http://www.microsoft.com/whdc/winlogo/drvsign/drvsign_perOS.mspx But actually these pages only circle around and everytime you want to follow a link "to see detailed information.." you end up on a page telling the same again (the first) or they are providing end user information (the latter) I once found something where the prices for a normal signing process were listed, but the procedure itself is still a mystery. So, I am lost in the depths of the weird half baked MSDN documentation (which only refers to vista). Can anyone provide a little step by step guide how to get my driver signed for Windows XP WITHOUT a full WHQL submission, distribution through Microsoft and logo stuff etc.pp. I just for now want that it installs on Windows XP without the warnings. thanks for any help and pointers doc Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92715
  - 14
    - Howto: find tdi behavior flag of a kernel sockets client Hello, Per WDK, a kernel sockets client can set a flag-- WSK_TDI_BEHAVIOR_BYPASS_TDI--that will cause WSK to bypass TDI filters. >From WDK: "If a native WSK transport exists for the address family, socket type, and protocol that are specified when the WSK application creates a socket, then, if this flag is set, the WSK subsystem ignores any TDI filter drivers and always uses the native WSK transport." How can I find out if this flag is set by a particular driver, or a particular kernel sockets client? Thanks. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92709
  - 15
    - Virtual comport with usbser.sys Hello NG, I wrote an Inf-File which installs a virtual comport using usbser.sys for my USB device. When I connect the device to the PC the Hardware wizard comes up an installes usbser.sys. After that I can communicate with the device via a virtual Com-Port. So far so good. Now I tried this on several machines and now I am facing a problem on one of my testing machines. The driver on this machine seems to be installed properly but the Hardware wizard comes again and again. When I open the device manager the device appears under ports without an assigned Com-Port. Looking into the registry I found the entry \Device\USBSER000 which value is set to "COM11" under HKLM\Hardware\DEVICEMAP\SERIALCOMM but my device is not accessible via that COM Port (Com 11). Any ideas? Benji Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92702
  - 16
    - "Fake" Keyboard or Mouse driver Does anyone know if is possible to get (and where is it of course...) a "fake" keyborad (or mouse) driver that can simulate key press or mouse click generated by code (like C++, VB.NET ecc) ? I would like to "simulate" some condition on a virtual machine, but I can't install any other SW in it because the OS installed is Linux. Thx in advance Sorry for my poor english .... -- I.d.N. .oO Please cut "-SOME TREES-" for reply Oo. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92699
  - 17
    - USB Compsite Device Driver loading and PnP events I have a question on the USB composite device. In DDK, it is said After the USB hub driver generates a PnP event for a Composite device with a set of compatible IDs that include USB\COMPOSITE, Windows searches the INF files in the inf subdirectory of the Windows installation (and, possibly, a vendor-provided floppy disk) for a match. If the device ID is matched, Windows loads the single driver that is indicated by the installation script and the generic parent driver does not come into play. If no device ID match is found, Windows uses a compatible ID, for which it loads the USB generic parent driver. I just want to know If the device ID is matched, Windows loads the single driver that is indicated by the installation scripts, then who will be responsible to generates PnP events for the multiple interfaces in the composite device? Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92694
  - 18
    - HClint can't find any hid mouse in Windows XP Sp2 X64 ENVIRONMENT Hi, all Why the sample code "HClient (\WINDDK\3790.1830\src\wdm\hid\hclient)" can't find any hid-mouse in Windows XP/2003 SP2 x64 eniornmenrt? I need to open hid mouse interface in windows xp (x64). how can i to do this job? Sincerely , Eliot Chang Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92687
  - 19
    - storport half-duplex mode Is HwInterruptRoutine called with the StartIo spinlock held in half-duplex mode? Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92676
  - 20
    - Driver differences Can someone point me to a page that lists or describes the differences between drivers for Windows XP and drivers for Windows Vista? I'm not a driver developer, but I've been tasked with getting a high level overview of the differences. I need to find out what changes will be required to port our existing NDIS driver to Windows Vista. Any help will be appreciated. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92672
  - 21
    - How to call LockWorkStation on Vista 64-bit? Not a driver question but - We we call LockWorkStation on Vista 32-bit is works and locks the workstation. On Vista 64-bit it doesn't work. What is the trick to make this call or is it unsupported on 64-bit? Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92671
  - 22
    - help files in printer driver user interface In all previous versions of our printer drivers (for Windows 98, NT, 2000, XP) we used the WinHelp API to display context sensitive help for the printer driver user interface DLL. Windows Vista no longer supports the WinHelp functions, so I converted the driver UI to use HtmlHelp and rebuilt the old HLP files into newer CHM files. This does does not seem to work though. I can debug the driver UI and see that I am passing correct parameters to HtmlHelp() function, but nothing gets displayed. Is there some trick to using HtmlHelp from driver UI DLL? Is there a better way to add context sensitive help to driver UI? Thanks in advance, Neal Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92670
  - 23
    - i will find drivers for you i will find drivers for you at mdrepairs Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92659
  - 24
    - How to use SetErrorMode() to ignore pop-up windows? Hi all, The code is: if(!SetupDiCallClassInstaller(DIF_INSTALLDEVICEFILES, hDevInfo, &deviceInfoData)) { // happen error here! errCall = "SetupDiCallClassInstaller"; goto failed; } When application run into SetupDiCallClassInstaller api, it will popup a error message about device installer error. There I want to disable this window pop-uped. Then application can execute normally. So I try to use SetErrorMode() like following: SetErrorMode(SEM_FAILCRITICALERRORS); if(!SetupDiCallClassInstaller(DIF_INSTALLDEVICEFILES, hDevInfo, &deviceInfoData)) { // happen error here! errCall = "SetupDiCallClassInstaller"; goto failed; } SetErrorMode(0); But it seems can't work... Do you have any suggestions about it? Thanks in advance! Eugene Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92650
  - 25
    - Volume control implementation In this post I am referring to Windows 2K/XP, things seem somewhat different in Vista and I haven't had a chance to investigate it] There is volume control in Windows Media Player (or Winamp, or any other player application) and there is one in Windows control panel. Can anyone explain what each of them actually does? My current understanding is that volume control in the player makes player application scale audio stream programmatically, after which audio stream is sent to the hardware. Volume control in the Windows Control panel doesn't change audio stream programmatically but instead works as a "knob" for hardware amplifier on the sound card. Am I correct? Is there any information on MS website that explains all this? So far I haven't found it. Tag: NdisMEthIndicateReceive - porting to ndis 6.0 Tag: 92643

Hi,

Please let me know if someone knows the mechanism of porting
NdisMEthIndicateReceive fuinction to ndis 6.0.

Theres no direct replacement; neither could i find the explained
theory of indicating ethernet packet to ndis 6.0.
Think it could be done with NdisMIndicateReceiveNetBufferLists.
Pleae reconfirm..

Tanks of thanks!
shweta

Top

RE: NdisMEthIndicateReceive - porting to ndis 6.0 by pavel_a

pavel_a
Tue Mar 13 08:53:00 CDT 2007

"shweta" wrote:
> Hi,
>
> Please let me know if someone knows the mechanism of porting
> NdisMEthIndicateReceive fuinction to ndis 6.0.
>
> Theres no direct replacement; neither could i find the explained
> theory of indicating ethernet packet to ndis 6.0.
> Think it could be done with NdisMIndicateReceiveNetBufferLists.
> Pleae reconfirm..
>
>
> Tanks of thanks!
> shweta

Reconfirmed. NDIS6 DDIs are not drop-in replacement of earlier NDIS.
--PA

Top