Ndis Miniport Driver with WPP

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
    - Reading the Configuration Space of ICH4 in a WDM Driver Hi, I have n newbie question. I want to write a WDM device driver witch reads the configuration space of the ICH4 Southbridge from Intel. Iâ??ve tried these Code samples from Microsoft: First with IRP_MN_QUERY_INTERFACE http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q253232 and then with IRP_MN_READ_CONFIG http://msdn.microsoft.com/library/default.asp?url=/library/en-us/kmarch/hh/kmarch/IputOput_1526c9e1-7391-4746-818b-8d4f384bd572.xml.asp None of these worked. In both samples the IoCallDriver() Function failed. Iâ??ve written the vendor and device ID in the INF File: [Manufacturer] %MfgName% = Device [Device] %FeatureDevice%=Feature_DDI, PCI\VEN_8086&DEV_24C0&SUBSYS_00000000&REV_02 I canâ??t see the error Iâ??ve made. Could some of you give me some hints? Tag: Ndis Miniport Driver with WPP Tag: 69563
  - 2
    - Function Driver was not specified for this device instance Hi , I written a win2k plug n play driver for PCMCIA 16 bit PC card.I written the code up to the device detection. While installing the drivers I given the path of our device inf file and it has asked the path of driver file (.sys file). I given the path of driver file also.After completion of installation the following message deplays. //////////////////////////////////// "The installation failed because a function driver was not specified for this device instance" /////////////////////////////////// What could be the reason. Please guide me bye, Mahi Tag: Ndis Miniport Driver with WPP Tag: 69561
  - 3
    - OEMUI and OEMUNI Hi Vipin Sir, I developed a Rendering plugin and it works properly as expected. But now I'm developing the UI Plugin, and from that I want to change the image size, i.e. if I give say height = 1 in and width = 1 in, then I should get the image size i.e. 1 x 1. Right now, I'm providing 3 x 3 paper size, and I'm getting the image size as 3 x 3 only. Also I've defined a customsize option in paper size. i.e. I want to develop a UI plugin so that the rendering plugin will draw a Image of that size only and not more than that. How to do so, plese tell me. Actually I'm having the plugin i.e. UI plugin, which does the same thing what I wanted but I don't have source code for that. so can you please guide me, i.e. please tell me in which function I shoul make these changes? Thanks Adi -- adibhapse ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: Ndis Miniport Driver with WPP Tag: 69560
  - 4
    - PCL5e and PCL6 Hello, anybodies knows what is the difference between PCL5 and PCL6? Thanks Keshav Tag: Ndis Miniport Driver with WPP Tag: 69550
  - 5
    - newbie linking IoXxx routines problem While writing a small test driver (mainly for experience purposes) from scratch, the following problem arised: linker cannot find IoCreateSymbolicLink within ntoskrnl.lib. I am using MSVC .net and w2k DDK, running on a wxp pro machine and was unable to generate an executable with 'build' and dirs/sources/makefile files, so I created a makefile project with Visual Studio and wrote a very simple makefile and invoked it with "BuildCommand Line: NMake test.mak" in project properties: -- test.mak LINK_OPTS = /driver:WDM /out:test.sys /entry:testmain LINK_LIBS = hal.lib ntoskrnl.lib ntdll.lib wdm.lib .obj.sys: link $(LINK_OPTS) $(LINK_LIBS) $*.obj test.sys : test.obj test.obj : test.cpp -- END testdrv.mak Everything was compiling and linking fine until I tried to use one of the IoXxx functions in test.cpp. The linker refuses to find the functions in any .lib provided with w2k DDK (as far as I can tell, IoCreateSymbolicLink is both in wdm.lib and ntoskrnl.lib). The following 'link test' code compiles fine and linker gives the following error: test.obj : error LNK2019: unresolved external symbol __imp__IoWriteErrorLogEntry referenced in function _testmain while it compiles and links perfectly if the call to IoWriteErrorLogEntry is removed from the code. --test.cpp #define _X86_ extern "C" { #include <ntddk.h> } extern "C" NTSTATUS DriverMain (PDRIVER_OBJECT DrvObj, PUNICODE_STRING RegPath) { KeInitializeSpinLock (NULL); RtlCopyUnicodeString (NULL, NULL); IoCreateSymbolicLink (NULL, NULL); return STATUS_SUCCESS; } -- END test.cpp The linker (and compiler) used are the one shipped with Visual Studio, but the problem remains exactly the same if using compiler and linker of w2k DDK. I have tried everything I could think trying to solve the problem, but now I am stuck. Any hint on how to solve it? Thanks in advance Tag: Ndis Miniport Driver with WPP Tag: 69539
  - 6
    - Link error using KsDispatchSpecificProperty How can I use the KsDispatchSpecificProperty: when I use this function, I got link error: mydriver.obj : error LNK2019: unresolved external symbol __imp__KsDispatchSpecificProperty@8 referenced in function _MyIoCtrlCompleteRoutine@12 I have add the ks.lib in the source file: TARGETLIB=$(BASEDIR)\lib\*\$(DDKBUILDENV)\KS.lib Tag: Ndis Miniport Driver with WPP Tag: 69537
  - 7
    - (mike han)(When removal a usb device from pc, what does the windows send to usbdevice? Dear Sir: I have a problem, I developed a usb disk, but I don't know when user safely remove the usb disk from PC, What command the windows will send to the usb device? I study the common UFI command, But I don't find a command related with it, Please help me, thank you very much. Best Regards Mike Han Tag: Ndis Miniport Driver with WPP Tag: 69525
  - 8
    - Who is watching the store! After loading my MSI file on a bunch of computers, my systems and drivers were all working just fine except for one computer - drat. I hooked up windbg to that computer and discovered that it was doing some strange stuff, and when I thought I had identified a possilbe problem I blew away the driver and replaced it only to discover that I'd made an error in this analysis. So 1st I loaded in a copy of the original driver by hand and things came alive! Then I reloaded from my msi file and things were still alive! Conclusion: during the installation of the msi file, there was some corruption of my file. HERE IS WHERE IT GET's INTERESTING: Experiment: Take an driver from c:\windows\system32\drivers and randomly edit the file with a binary editor and do not update any checksums along the way!. Then try to load it. In my case, I edited some text strings in the file, and I did not change the file length. It loads just fine. Did I hallucinate this? I thought a checksum would be calculated over the entire file. Surely the system would be sensitive to corruption from bad drivers as such. What about Security implications? -- Gak - Finecats Tag: Ndis Miniport Driver with WPP Tag: 69515
  - 9
    - RtlRetrieveUshort - bug? Here's a good interview question... Find a bug in RtlRetrieveUshort/Ulong macros in ntddk.h (DDK 3790.1830 / wnet) For x86 RtlRetrieveUshort, RtlRetrieveUlong are defined as: #define RtlRetrieveUshort(DEST_ADDRESS,SRC_ADDRESS) \ if ((ULONG_PTR)SRC_ADDRESS & SHORT_MASK) { \ ((PUCHAR) DEST_ADDRESS)[0] = ((PUCHAR) SRC_ADDRESS)[0]; \ ((PUCHAR) DEST_ADDRESS)[1] = ((PUCHAR) SRC_ADDRESS)[1]; \ } \ else { \ *((PUSHORT) DEST_ADDRESS) = *((PUSHORT) SRC_ADDRESS); \ } \ Answer: SRC_ADDRESS must be enclosed in braces, or evil will happen. How to repro: #include <ntddk.h> void foo( void ) { UCHAR x[] = { 1,2,3,4,5,6,7,8,9,0 }; PUCHAR p = &x[1]; USHORT y; RtlRetrieveUshort( &y, p + 6 ); // fails RtlRetrieveUshort( &y, p + 1 ); // works } Same with RtlRetrieveUlong. Regards, --PA Tag: Ndis Miniport Driver with WPP Tag: 69505
  - 10
    - Drive letter not visible in Explorer Hello all, I'm trying to write a pseudo-disk driver for Windows XP. All went fine until I tried to mount it. Here's the problem: No metter which way I try to assign the drive letter for my disk -- either through creating a symbolic link or by notifying the Mount Manager with the IOCTL_MOUNTMGR_VOLUME_ARRIVAL_NOTIFICATION -- the letter isn't shown in the Explorer's file tree. The link is there -- it can be seen with WinObj or any similar tool, but Explorer keeps ignoring it. Can somebody please give me or point to any ideas, hints or guidelines on how to properly add a _pseudo_ disk drive into the system? Tag: Ndis Miniport Driver with WPP Tag: 69503
  - 11
    - Error: Digital signature did not verify I have developed an NDIS IM driver. I sign it using Authenticode tools (signtool) with a Verisign code signing ID. It has installed correctly under 2003 Server and x64 Editions (XP and Server). I recently made some changes to the driver. I used the same exact .inf's and procedure to sign the .cat file, yet when I attempt to install on an x64 Server machine I get "The digital signature of the object did not verify". The code returned from HrInstallNetComponent is 0x80096010. If I simply replace the new driver (.sys) file with the previous .sys file it installs correctly. It appears that during the installation process the digital verification of the .cat file works incorrectly for the new .sys file. Note that if I use "signtool verify /pa /v driver.sys" the signature is correct. I suspect that Authenticode is signing the driver correctly, however the driver installation is incorrectly verifying the driver. Has anyone seen this or have any ideas? Thanks. Dan Tag: Ndis Miniport Driver with WPP Tag: 69502
  - 12
    - Is it possible to write a user-mode NDIS miniport driver Tag: Ndis Miniport Driver with WPP Tag: 69499
  - 13
    - Making IOCTL calls between 2 avstream drivers. I want to make an IOCTL call between 2 avstream drivers that support property sets. I am using IoGetDeviceInterfaces to get the interfaces and then I do a IoGetDeviceObjectPointer to get the device object. Following that when I need to make the IOCTL, I use IoBuildDeviceIoControlRequest to set the IRP and then I am trying to use IoCallDriver but it returns back with an error. Here is how I am setting the StackLocation... What I need to send is 1>KSPROPERTY and 2>ULONG(which contains data) pIrp = IoBuildDeviceIoControlRequest( ulIoctl, pFilter->pDevObject, pData, ulpData, pcbData, ulcbData, TRUE, NULL, &IoStatusBlock); //ulpdata points to a KSPROPERTY structure...pcbdata is size of //KSPROPERTY... pcbdata points to a ULONG, ulcbdata is SIZE of ULONG. if (pIrp != NULL) { PIO_STACK_LOCATION pNextStackLocation; pNextStackLocation = IoGetNextIrpStackLocation(pIrp); if (pNextStackLocation) { pNextStackLocation->FileObject = pFilter->pFiObject; pNextStackLocation->MajorFunction = IRP_MJ_DEVICE_CONTROL; pNextStackLocation->Parameters.DeviceIoControl.IoControlCode = IOCTL_KS_PROPERTY; IoStatusBlock.Status = STATUS_SUCCESS; ntStatus = IoCallDriver( pFilter->pDevObject, pIrp); Is there anything wrong in what I am doing ? Do I need to set additional parameters in PIO_STACK_LOCATION ? as to what data needs to go through ( like size of KSPROPERTY or ULONG) ? Thanks. Tag: Ndis Miniport Driver with WPP Tag: 69498
  - 14
    - PDO FireObject of Firefly example Hi, Greetings. In the firefly example, the Fileobject handle of PDO was acquired using ZwOpenFile() and ObReferenceObjectByHandle() for each Set Feature, and was released immediately after every Set Feature. But if I save the Fileobject handle in my device extension during the first Set Feature and use it for all subsequent Set Feature calls, after which Dereference it during my Remove Device, the mouse seems not to respond to any physical movement. The Service_CallBack() routine in Firefly is never triggered. Anyone can enlighten me is it compulsory that the FileObject handle must be released immediately after every set feature, and the reason behind it if it is true? Thanks in advance. Regards, Angela Tag: Ndis Miniport Driver with WPP Tag: 69439
  - 15
    - SCSI Processor Device Driver We have a legacy driver for NT to communicate with a piece of custom hardware. This hardware doesn't seem to fall into any of Microsoft's existing classes (at least I don't think so, but you've probably heard that line before). It attaches via a SCSI-2 interface, and meets the minimum requirements under SCSI-2 as a 'Processor' device. It allows the computer to interface with a large amount of individual I/O points used in a full-scope control room simulator (app. 1500 analog outputs, 7500 digital outputs, 4500 digital inputs, and 300 analog inputs, all scanned at 20 Hz). Our legacy driver, (originally written for NT 3.51) has served us pretty well through the various OS upgrades. I developed a new '.inf' file a few years back to provide client-side installation on Windows 2000. The same .inf and .sys files work under Windows XP (pro & home). But they do *not* seem to work on Windows 2003 Standard edition. Why not?? The OS complains about error starting the driver yet it works under XP and 2000. Anyway, I'm trying to write a new driver using the latest DDK and WDM models (I wrote the original as well). Or should I wait for WDF? But I can't find nearly the amount of information on SCSI device drivers that I had back in the NT days. Most new things are USB & 1394 it seems. I do have the SCSI specs down pat and work quite closely with the device firmware programmer, so I have that going for me (as well as a SCSI bus analyzer etc...) But searching for a good text on the subject of SCSI drivers under WDM hasn't been successful (have "Programming the Microsoft WIndows Driver Model" and "The Windows 2000 Device Driver Book", but they barely acknowledge that SCSI exists). I've started by using a storage/class sample from the DDK. But since 'SCSI Processor' devices support a lot fewer features than either CDROM, disk drives, or tape, there's a lot of code that needs to be thrown away. And cutting out code without breaking things is a bit tricky. Anyone have a better starting point for a simple SCSI device that still fits the WDM model? Also, since this device is external, and has it's own power, can I just reply success to all the power management requests (the device doesn't have any sort of power-down mode)? Sorry for the long ramble, but this is a small outfit and I feel lost in the wilderness a bit. I get to do the low-level drivers because I'm the one that works with the hardware folks and understand bit-bashing. Mike Fochtman Tag: Ndis Miniport Driver with WPP Tag: 69428
  - 16
    - Network bindings -> MoveBefore - error Hello, I look for a way to change the network binding programmaticaly- my problem seems to be the same, as jim2005's in the thread: "How to programmatically set binding order of NDIS miniport adapter on install?". So, I took a look at BindView example in WinDDK and what I do is: I acquire a write lock using INetCfgLock->AcquireWriteLock I enumarate all the components INetCfgClass->EnumComponents, and I search for the component I want to put on the top of the list. Then I enumarate all the binding paths for the component using: INetCfgComponentBindings->EnumBindingPaths For each of the binding path I try to call INetCfgComponentBindings->MoveBefore with the second argument = NULL. However, it gives me an error: -2147180508 And this is where I stuck :-( As I'm not very experienced with C++ programming (I come from the .NET world) I have no clue where I should go next. Can anyone give me any suggestion what may be the cause for the error? Has anyone ever manage to make a good use of MoveBefore (or MoveAfter) and would share a snippet of code? I'll be very grateful - thanks in advance. Marcin Pytel -- Tag: Ndis Miniport Driver with WPP Tag: 69425
  - 17
    - Bidirectional communication to USB printer Hi there, I'm trying to receive status information of an Epson printer (connected by USB) on Windows XP, which is not supplied by some Windows APIs. According to the Epson programming guide it is possible to query the information via ESC sequences. Sending these ESC sequences seem to work by using the "WritePrinter" function. Unfortunately the corresponding "ReadPrinter" function does not return any useful data. Neither the "ExtEscape" function with the PASSTHROUGH option nor the COM object "IBidiRequest" worked. Any suggestions how to establish a bidirectional connection to the printer using Windows XP to send ESC sequences and receive the responses from the printer? Something like ReadFile() and WriteFile() would be fine, but I don't know how to get a handle fot them. Thanks for help. Markus Tag: Ndis Miniport Driver with WPP Tag: 69422
  - 18
    - Porting Win9x driver to right-to-left Windows problem I have been writing monolithic printer driver for Windows9x for our specific fax device. The driver should support right-to-left (RTL) languages. The driver is was properly debugged and tested under left-to-right (LTR) Windows, but there are some problems when itâ??s running under Windows 9x RTL. Problem 1: When driver is installed using itâ??s inf-file, the warning message appears: â??The printer driver you are using doesnâ??t print in your local language. By installing this printer driver you may cause Windows to fail. Contact the printer manufacturer for the proper printer driver.â?? Problem 2 If some document, containing both LTR and RTL strings is printed, the LTR text only appears in the printer output. The printer driver simply redirects all the calls to DIBENG.DLL and when each page is completed, it stories the image of the page to file. Using UNIDRV is not possible. What should be done for the printer driver to support RTL? Thank you for your help, Alexey. Tag: Ndis Miniport Driver with WPP Tag: 69421
  - 19
    - Compiler version not supported by Windows DDK Hi When i compile my program, using the ndis.h and ntddk.h on VC6, i get the error message "Compiler version not supported by Windows DDK". I'm not writing a driver, but a program that use a driver (therfore, i think, compiling with the build program of the DDK is not the right solution). Is there another solution to that situation? Thanks, D Tag: Ndis Miniport Driver with WPP Tag: 69418
  - 20
    - StartDocPort and DOC_INFO_1 Hi I'm writing a port monitor. It's a kind of a redirector port and I have to tell him where to redirect the data to. This is done using a GUID. So I have to give him a GUID. I thought about doing this in the pOutputFile of the DOC_INFO_1/2 struct. Since this is a "caller supplied pointer", it should work. But the MSDN also says: pOutputFile: ... To print to a printer, set this to NULL. ... now, I want to print to a "printer", but I still don't want to set this to NULL... does someone know if this is OK, or should I try to find an other solution? Does Windows redirect the job to somewhere else, if I don't pass NULL in this parameter? thanks MR Tag: Ndis Miniport Driver with WPP Tag: 69417
  - 21
    - NdisMIndicateReceivePacket from ProtocolReceive problem I'm extending the passthru example to create an IM-driver that redirects sent/received packets. Everything works well when using NDIS 5.1 and the ProtocolReceivePacket but I run into problems using NDIS 4.0 and ProtocolReceive. In the ProtocolReceive I get the original packet with NdisGetReceivedPacket which works (for now I ignore drivers that don't support this call but will later on take care of the LookAheadBuffer etc). Once I get the packet I do the same thing as when using ProtocolReceivePacket - allocate a packet, allocate a buffer, copy data between packets with NdisCopyFromPacketToPacket (NdisCopyFromPacketToPacketSafe when doing NDIS 5.1), change the destinationport and update the checksum, NDIS_SET_ORIGINAL_PACKET, NDIS_SET_PACKET_HEADER_SIZE, set flags, set status and then indicate the packet up with NdisMIndicateReceivePacket. The problem is that the packet never gets to the upper layer when ProtocolReceive is used, but everything is working great when ProtocolReceivePacket is used. I've read something about that you need to supply a buffer that is atleast the lookahead length but I guess this doesn't apply when using NdisMIndicateReceivePacket with a complete NDIS_PACKET where the NDIS_BUFFER holds the entire packet? Any suggestions of why I get this behaviour? Do you think it would work better if I used the NdisMEthIndicateReceive instead of the NdisMIndicateReceivePacket? It would be nice to be able to use the same code for both PtReceive and PtReceivePacket - that is using the NdisMIndicateReceivePacket. I would really appreciate your help. Magnus Hedbeck (my email is not valid, reply in newsgroup) Tag: Ndis Miniport Driver with WPP Tag: 69416
  - 22
    - Configuring Win2K USB Mass Storage Driver for "Quick Removal" Hello Experts, I have created a USB Mass Storage device with a PDIUSBD12 target controller. I have successfully written the target side driver and am able to do all kinds of disk operation on it. I now have a requirement of selectively preventing disk operations as below: a) Prevent users from creating any directories on the disk b) Prevent users from formatting the disk c) Prevent users from storing any file on the disk whose name is NOT "MyFile.bin" I have been able to do all the above successfully in Windows XP because when ever the user performs a disk operation, XP first writes data to the "root directory" sectors and then to the rest of them. So, whenever I get a request for any disk operation that needs to write to the "root directory" sectors, I first do a validation on the root directory related data and if it does not meet the above constraints, I stall the operation and return a "Write Protect" status in the the following request sense command. All this works perfectly well in XP. However in Windows 2000, the sequence of disk operation is different. The root directory is NOT written to first. Due to this reason, I am not able to do such a validation on the same. This difference in behaviour in Win 2K is because the mass storage driver is configured for "Better performance" than "Quick Removal". In Win 2K there is no option to change this seeting (unlike Win XP). Is there a registry tweak to change this setting? Thanks. Tag: Ndis Miniport Driver with WPP Tag: 69415
  - 23
    - USB Imaging Device Driver Hi, We are using an OmniVision imaging board, that uses the 3620 chip, which is bridged by a Cypress board. I am fairly new to device drivers and not sure what i need to do to implement a device driver that will treat this board as an imaging board. I need to be able to use DirectX to stream video and capture images off the USB device, which the supplied Cpress device drivers do not support. From what i understand at the moment, the driver is made of a collection of system drivers and a custom driver. The firware for the USB device does not fully implement the Imaging specification, so i suspect that the cutom device driver will mimic that the board is an imaging device. I have implemented the inf file, which includes and uses the DirectX support: [CyUsb.NT] Include=ks.inf, kscaptur.inf, ksfilter.inf Needs=KS.Registration,KSCAPTUR.Registration.NT Any help would be most appreciated. Many Thanks, -- Bruce Philp Software Engineer Astron Clinica Ltd Tag: Ndis Miniport Driver with WPP Tag: 69413
  - 24
    - A sniffer, fast and dirty... I need to count certain packets sent thru a netcard during usual network activity (internet, mail...). The counting can be done in kernel mode, no need to pass data to usermode. The card can be any usual 10/100 ethernet, connected either to LAN or DSL modem (PPPoE). What of the following is less intrusive to the system and easier to do? a. IM filter based on Passthru b. Protocol driver & set the packet filter to ALL_LOCAL Ah and this will be just a fast and dirty internal tool - not for production :) Thanks for any advice, --PA Tag: Ndis Miniport Driver with WPP Tag: 69406
  - 25
    - ISO Busters I have been trying to convert an ISO file downloaded from microsoft (VS2005 Beta 2 Provessional version) using ISOBuster. But everytime I click on a file to extract it comes up with "Could not open file, file might be protected or in use". I definitely do not have it used anywhere else, so I'm not sure why it thinks it's protected. Has anyone else had this issue and found the cure? Thanks, Sarah Tag: Ndis Miniport Driver with WPP Tag: 69404
- Next
  - 1
    - Bug Check In NDIS Intermediate driver. DRIVER_CORRUPTED_EXPOOL (c5) and BAD_POOL_CALLER (c2) All, Thanks a lot in advance, if someone can help me out with these bugs it would be great help. I am having really hard time tracing these two bug checks in my NDIS intermediate driver. As they are random bug checks, they happen once a while so i am not sure what is the problem. Both the bug check are coming at the same location. When i try to free the memory in my driver. Attached is the memory dump of both the bug checks. Bad_POOL_CALLER comes when my NDISReturnPacket handler is called by NDIS. When i receive back the the packet then i try to free the VM, which i have allocated while indicating the NDIS packet upward. Driver_CORRUPT_EXPOOL is coming when my NDISSendComplete is called and i am trying to free the VM which i have allocated while sending the NDIS packet. In the memory dump it shows i tried to free location 00000001. I am not sure if is memory 0000001 if valid memory, which i am suppose to free. Here is the code which i am using to free (FltCleanPacket) my packet memory and below that is the code for creating the new packet (FltCopyPacketBuffers). I am using the same code at both the locations. When i reviewd my code, then i found out i must use NdisBufferVirtualAddressSafe, instead of NdisBufferVirtualAddress functions. I am not sure if this is the problem or its something else. Thanks a lot in advance. VOID FltCleanPacket(IN PNDIS_PACKET Packet){ PNDIS_BUFFER pNDISBuffer = NULL; PUCHAR pPacketBuff = NULL; //Here we have to free all the buffer and memory.. // Packet this is my packet i have to work on Packet NdisUnchainBufferAtBack(Packet,&pNDISBuffer); ////Get the VM from the Buffer// pPacketBuff = NdisBufferVirtualAddress(pNDISBuffer); //// Call free on this VM// NdisFreeMemory(pPacketBuff,0,0); //// Free the Buffer// NdisFreeBuffer(pNDISBuffer); return;} VOID FltCopyPacketBuffers(IN PADAPT pAdapt,IN PNDIS_PACKET Packet,IN PNDIS_PACKET MyPacket) { PNDIS_BUFFER CurrentBuffer; UINT nBufferCount, TotalPacketLength; UINT BytesCopied = 0; PUCHAR pPacketBuff = NULL; NDIS_STATUS Status = 0; PNDIS_BUFFER NewBuffer; if( !Packet || !MyPacket ) return; NdisQueryPacket( (PNDIS_PACKET )Packet, (PUINT )NULL, // Physical Buffer Count (PUINT )&nBufferCount, // Buffer Count &CurrentBuffer, // First Buffer &TotalPacketLength // TotalPacketLength ); __try{ do{ ////We have the Total Packet length, we should allocate the Tagged Memory// Status = NdisAllocateMemoryWithTag(&pPacketBuff,TotalPacketLength,'piSN'); if(Status != NDIS_STATUS_SUCCESS) {break;} ////Here we shuld allocate the Buffer and chain it to the packet// NdisAllocateBuffer(&Status,&NewBuffer,pAdapt->BufferPoolHandle,pPacketBuff,TotalPacketLength ); if(Status != NDIS_STATUS_SUCCESS) __leave; // Leave __try and eventually return... ////Chain that buffer in the packet// NdisChainBufferAtFront(MyPacket,NewBuffer); }while(FALSE); ////We should use the Ndis Copy to copy the whole packet..// NdisCopyFromPacketToPacketSafe(MyPacket,0,TotalPacketLength,Packet,0,&BytesCopied,NormalPagePriority); }//__try __finally { }//__finally } begin 666 BAD_POOL_CALLER.txt M,3H@:V0^("%A;F%L>7IE("UV#0HJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ#0HJ(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" J M#0HJ(" @(" @(" @(" @(" @(" @(" @(" @0G5G8VAE8VL@06YA;'ES:7,@ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" J#0HJ(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" J#0HJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ#0H-"D)!1%]03T],7T-!3$Q%4B H8S(I#0I4 M:&4@8W5R<F5N="!T:')E860@:7,@;6%K:6YG(&$@8F%D('!O;VP@<F5Q=65S M="X@(%1Y<&EC86QL>2!T:&ES(&ES(&%T(&$@8F%D($E244P@;&5V96P@;W(@ M9&]U8FQE(&9R965I;F<@=&AE('-A;64@86QL;V-A=&EO;BP@971C+@T*07)G M=6UE;G1S.@T*07)G,3H@,# P,# P,#<L($%T=&5M<'0@=&\@9G)E92!P;V]L M('=H:6-H('=A<R!A;')E861Y(&9R965D#0I!<F<R.B P,# P,3$U,RP@*')E M<V5R=F5D*0T*07)G,SH@,# P,# P,# L($UE;6]R>2!C;VYT96YT<R!O9B!T M:&4@<&]O;"!B;&]C:PT*07)G-#H@.#DX.6(P,&$L($%D9')E<W,@;V8@=&AE M(&)L;V-K(&]F('!O;VP@8F5I;F<@9&5A;&QO8V%T960-"@T*1&5B=6=G:6YG M($1E=&%I;',Z#0HM+2TM+2TM+2TM+2TM+2TM+2T-"@T*#0I"54=#2$5#2U]3 M5%(Z(" P>&,R7S<-"@T*1$5&055,5%]"54-+151?240Z("!$4DE615)?1D%5 M3%0-"@T*0U524D5.5%])4E%,.B @,@T*#0I,05-47T-/3E123TQ?5%)!3E-& M15(Z("!F<F]M(#@P-38X860P('1O(#@P-30S86,Y#0H-"E-404-+7U1%6%0Z M(" -"F(Y-#4U.6(T(#@P-38X860P(# P,# P,&,R(# P,# P,# W(# P,# Q M,34S(&YT(4ME0G5G0VAE8VM%>"LP>#$Y#0IB.30U-6$Q-"!F-S(T-F4X." X M.3@Y8C P82 P,# P,# P,"!B.30U-6$T,"!N="%%>$9R9650;V]L5VET:%1A M9RLP>#4Q- T*8CDT-35A,C0@9C<U-V-B.60@.#DX.6(P,&$@,# P,# P,# @ M,# P,# P,# @3D1)4R%.9&ES1G)E94UE;6]R>2LP>#,Y#0I705).24Y'.B!3 M=&%C:R!U;G=I;F0@:6YF;W)M871I;VX@;F]T(&%V86EL86)L92X@1F]L;&]W M:6YG(&9R86UE<R!M87D@8F4@=W)O;F<N#0IB.30U-6$T,"!F-S4W.&4Q-" X M.3<R9F8Q," X.3<S9#4V," X.3<R9F8S,"!.4TE01DQ4*S!X-6(Y9 T*8CDT M-35A-3@@9C<R-C R8C$@.#DW,S-B,C @.#DW,F9F,3 @8CDT-35C.3@@3E-) M4$9,5"LP>#%E,30-"F(Y-#4U83<T(# P-#4U8C$X(# P,# P,# P(# P,# P M,# P(&)A8C$Q-C%F($Y$25,A3F1I<U)E='5R;E!A8VME=',K,'AD80T*8CDT M-35A.3@@8F%B,3$X-CD@.#AE,V,S,3@@.#DU-C$P,C @,# P,# P,# @=V-M M*S!X-35B,3@-"C@Y.61B860P(#@Y.61A,3,P(#@Y.61D.#0X(#@Y-S,S8C(P M(# P-64P,#5C(&%F9"%!9F1&87-T0V]N;F5C=&EO;E)E8V5I=F4K,'@R9# - M"F(Y-#4U8S4X(#@P-3@U9F0T(#@X93(Y-C X(# P,# P,# Q(# Y8V)B.#(P M(#!X.#DY9&$Q,S -"F(Y-#4U9# P(#@P-3@V,3(X(# P,# P-68P(# P,# P M-65C(# P,# P,# P(&YT(4EO<%AX>$-O;G1R;VQ&:6QE*S!X,C4U#0IB.30U M-60S-" X,#1D9F0R-" P,# P,#5F," P,# P,#5E8R P,# P,# P,"!N="%. M=$1E=FEC94EO0V]N=')O;$9I;&4K,'@R. T*8CDT-35D,S0@-V9F93 S,#0@ M,# P,# U9C @,# P,# U96,@,# P,# P,# @;G0A2VE3>7-T96U397)V:6-E M*S!X9# -"C Y8V)B-V4P(#<W9C0R-F-B(#<Q8C(Q.#$W(# P,# P-68P(# P M,# P-65C(%-H87)E9%5S97)$871A(5-Y<W1E;4-A;&Q3='5B*S!X- T*,#EC M8F(W930@-S%B,C$X,3<@,# P,# U9C @,# P,# U96,@,# P,# P,# @;G1D M;&PA3G1$979I8V5);T-O;G1R;VQ&:6QE*S!X8PT*,#EC8F(X-S0@-S%C,&9D M9C$@,# P,# U9C @,#EC8F(X86,@,# P,# P,#$@;7-W<V]C:R%74U!296-V M*S!X,6%F#0HP.6-B8CAB8R P,#8U.60R-2 P,# P,#5F," P.6-B8CDP," P M,# P,# S,"!74S)?,S(A<F5C=BLP>#@Q#0HP,# P,# P," P,# P,# P," P M,# P,# P," P,# P,# P," P,# P,# P,"!W8VTK,'@R-3ED,C4-"@T*#0I& M3TQ,3U=54%])4#H@#0I.4TE01DQ4*S5B.60-"F8W-3=C8CED(#AB-&1F8R @ M(" @(" @(" @;6]V(" @("!E8W@L6V5B<"TP>#1=#0H-"E-934)/3%]35$%# M2U])3D1%6#H@(#,-"@T*1D],3$]755!?3D%-13H@($UA8VAI;F5/=VYE<@T* M#0I364U"3TQ?3D%-13H@($Y325!&3%0K-6(Y9 T*#0I-3T153$5?3D%-13H@ M($Y325!&3%0-"@T*24U!1T5?3D%-13H@($Y325!&3%0N<WES#0H-"D1%0E5' M7T9,4E])34%'15]424U%4U1!35 Z(" T,S!A-V8V. T*#0I35$%#2U]#3TU- M04Y$.B @:V(-"@T*0E5#2T547TE$.B @,'AC,E\W7TY325!&3%0K-6(Y9 T* E#0I&;VQL;W=U<#H@36%C:&EN94]W;F5R#0HM+2TM+2TM+2T-"@`` ` end begin 666 DRIVER_CORRUPTED_EXPOOL.txt M,CH@:V0^("%A;F%L>7IE("UV#0HJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ#0HJ(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" J M#0HJ(" @(" @(" @(" @(" @(" @(" @(" @0G5G8VAE8VL@06YA;'ES:7,@ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" J#0HJ(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" J#0HJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ#0H-"D12259%4E]#3U)255!4141?15A03T], M("AC-2D-"D%N(&%T=&5M<'0@=V%S(&UA9&4@=&\@86-C97-S(&$@<&%G96%B M;&4@*&]R(&-O;7!L971E;'D@:6YV86QI9"D@861D<F5S<R!A="!A;@T*:6YT M97)R=7!T(')E<75E<W0@;&5V96P@*$E244PI('1H870@:7,@=&]O(&AI9V@N M("!4:&ES(&ES#0IC875S960@8GD@9')I=F5R<R!T:&%T(&AA=F4@8V]R<G5P M=&5D('1H92!S>7-T96T@<&]O;"X@(%)U;B!T:&4@9')I=F5R#0IV97)I9FEE M<B!A9V%I;G-T(&%N>2!N97<@*&]R('-U<W!E8W0I(&1R:79E<G,L(&%N9"!I M9B!T:&%T(&1O97-N)W0@='5R;B!U< T*=&AE(&-U;'!R:70L('1H96X@=7-E M(&=F;&%G<R!T;R!E;F%B;&4@<W!E8VEA;"!P;V]L+@T*07)G=6UE;G1S.@T* M07)G,3H@,# P,# P,#$L(&UE;6]R>2!R969E<F5N8V5D#0I!<F<R.B P,# P M,# P,BP@25)13 T*07)G,SH@,# P,# P,# L('9A;'5E(# @/2!R96%D(&]P M97)A=&EO;BP@,2 ]('=R:71E(&]P97)A=&EO;@T*07)G-#H@.# U-C<T-&8L M(&%D9')E<W,@=VAI8V@@<F5F97)E;F-E9"!M96UO<GD-"@T*1&5B=6=G:6YG M($1E=&%I;',Z#0HM+2TM+2TM+2TM+2TM+2TM+2T-"@T*#0I$149!54Q47T)5 M0TM%5%])1#H@($12259%4E]&055,5 T*#0I"54=#2$5#2U]35%(Z(" P>$,U M#0H-"D-54E)%3E1?25)13#H@(#(-"@T*3$%35%]#3TY44D],7U1204Y31D52 M.B @9G)O;2!F-S(T-F4X."!T;R X,#4V-S0T9@T*#0I44D%07T9204U%.B @ M9C<X8C)A8C @+2T@*"YT<F%P(&9F9F9F9F9F9C<X8C)A8C I#0I%<G)#;V1E M(#T@,# P,# P,# -"F5A>#TP,# P,#$R82!E8G@].# U.#,S-S@@96-X/3 P M,# P,# P(&5D>#TP,# P,# P,"!E<VD].#AE,V,P9C@@961I/3 P,# P,# Q M#0IE:7 ].# U-C<T-&8@97-P/68W.&(R8C(T(&5B<#UF-SAB,F(V."!I;W!L M/3 @(" @(" @("!N=B!U<"!E:2!P;"!N>B!N82!P92!N8PT*8W,],# P." @ M<W,],# Q," @9',],# R,R @97,],# R,R @9G,],# S," @9W,],# P," @ M(" @(" @(" @("!E9FP],# P,3 R,#(-"FYT(45X1G)E95!O;VQ7:71H5&%G M*S!X-#-F.@T*.# U-C<T-&8@.# S9C S(" @(" @(" @("!C;7 @(" @(&)Y M=&4@<'1R(%ME9&E=+#!X,R @(" @(&1S.C P,C,Z,# P,# P,#$]/S\-"E)E M<V5T=&EN9R!D969A=6QT('-C;W!E#0H-"E-404-+7U1%6%0Z(" -"F8W.&(R M8C8X(&8W,C0V93@X(#@X93-C,3 P(# P,# P,# P(&8W.&(R8CDT(&YT(45X M1G)E95!O;VQ7:71H5&%G*S!X-#-F#0IF-SAB,F(W."!F-S4Y8V(Y9" X.&4S M8S$P," P,# P,# P," P,# P,# P,"!.1$E3(4YD:7-&<F5E365M;W)Y*S!X M,SD-"E=!4DY)3D<Z(%-T86-K('5N=VEN9"!I;F9O<FUA=&EO;B!N;W0@879A M:6QA8FQE+B!&;VQL;W=I;F<@9G)A;65S(&UA>2!B92!W<F]N9RX-"F8W.&(R M8CDT(&8W-3EA-S8V(#@X938S860X(#@X938S8C$P(#@X9&5F,#@X($Y325!& M3%0K,'@U8CED#0IF-SAB,F)B,"!F-S(V,# V92 X.3<T.#1F," X.&4V,V%D M." P,# P,# P,"!.4TE01DQ4*S!X,S<V-@T*9C<X8C)B9#0@9C<P,V,Y-V0@ M.#EA-3$Q,S @.#AE-C-A9#@@,# P,# P,# @3D1)4R%N9&ES35-E;F1#;VUP M;&5T95@K,'@V90T*9C<X8C)B9C@@9C<P,V-A,60@.#DW-&%A-3 @,# W,S<V M-3@@.#DW-&$W.3 @:6%N<W=X<"LP>#0Y-V0-"F8W.&(R8S$P(&8W,#,X9#EE M(&8W.&(R8S(X(# P,# P,# U(#@Y-S,W-C4X(&EA;G-W>' K,'@T83%D#0IF M-SAB,F,S."!F-S(V,# V92 X.3<T83 P." X.3<S-S8U." P,# P,# P,"!I M86YS=WAP*S!X9#EE#0IF-SAB,F,U8R!F-S$Q,#AD9" X.6$V,#$S," X.3<S M-S8U." P,# P,# P,"!.1$E3(6YD:7--4V5N9$-O;7!L971E6"LP>#9E#0IF M-SAB,F,W-"!F-S$Q,&5C92!F-SAB,F,Y-" X.3<S-S8U." P,# P,# P,"!E M,3 P,#,R-2LP>#AD9 T*9C<X8C)C.&,@9C<Q,35C,#(@.#EA-3-B,C@@.#DW M,S<V-3@@,# P,# P,# @93$P,# S,C4K,'AE8V4-"F8W.&(R8V(P(&8W,3$U M,S$X(#@Y.6(X,&8P(#@Y-S,W-C4X(&8W.&(R8V0T(&4Q,# P,S(U*S!X-6,P M,@T*9C<X8C)C9&,@9C<Q,3 T9C0@,# Y8C@P9C @9C<R-C4P,C4@.#EA-3-B M,C@@93$P,# S,C4K,'@U,S$X#0IF-SAB,F0U," X,#1E-C%F-R P,# P,# P M," P,# P,# P92 P,# P,# P,"!E,3 P,#,R-2LP>#1F- T*#0H-"D9/3$Q/ M5U507TE0.B -"DY325!&3%0K-6(Y9 T*9C<U.6-B.60@,# P," @(" @(" @ M(" @("!A9&0@(" @(%ME87A=+&%L#0H-"E-934)/3%]35$%#2U])3D1%6#H@ M(#(-"@T*1D],3$]755!?3D%-13H@($UA8VAI;F5/=VYE<@T*#0I364U"3TQ? M3D%-13H@($Y325!&3%0K-6(Y9 T*#0I-3T153$5?3D%-13H@($Y325!&3%0- M"@T*24U!1T5?3D%-13H@($Y325!&3%0N<WES#0H-"D1%0E5'7T9,4E])34%' M15]424U%4U1!35 Z("!F9F9F9F9F90T*#0I35$%#2U]#3TU-04Y$.B @+G1R M87 @9F9F9F9F9F9F-SAB,F%B," [(&MB#0H-"D)50TM%5%])1#H@(#!X0S5? H3E-)4$9,5"LU8CED#0H-"D9O;&QO=W5P.B!-86-H:6YE3W=N97(-"@`` ` end Tag: Ndis Miniport Driver with WPP Tag: 69400
  - 2
    - How to programmatically set binding order of NDIS miniport adapter on install? I have an NDIS 5 miniport adapter (virtual) which is causing users some trouble because it always installs at the top of the adapter bindings order, knocking off whatever adapter was previously at the top, and wreaking havoc with previously established default bindings. Is it possible to make a change in the .inf file to tell Windows to use a lower binding position for the new adapter? I know that this can be fixed manually by going to Control Panel -> Network Connections -> Advanced -> Advanced Settings -> Adapters and Bindings, and manually changing the ordering. The problem is that this is too complicated a step to expect users to be able to do manually. Is there a way to programmatically tell Windows: "Install this adapter at the bottom of the adapter bindings list, rather than the top"? Thanks, James Tag: Ndis Miniport Driver with WPP Tag: 69395
  - 3
    - 1394 Max Isoch packet size in Windows 2000 1) I am NOT able to send 4096 bytes isoch packet in Windows 2000. I can do it in Windows XP SP1. Is this known bug? 2) When I am receiving packet with Isoch header, does 8 bytes header size included in isoch packet size. I think to receive 4096 byte packet with header, I need to have each receive packet (4096+8) bytes Thanks, Raj Tag: Ndis Miniport Driver with WPP Tag: 69394
  - 4
    - windbg firewire connection xp64 Anyone else having problems with the 1394 debug port on XP64 systems? This was rock solid on my 32bit test system and now it hangs consistently in the early boot load phase of OS initialization. Windbg connects and then the big stall. I'd hate to have to go back to a serial port. The test system is a brand new dell dual proc xeon. TI 1394 chip set. Plugging in an add-on 1394 card is not a problem if that is what it takes. Tag: Ndis Miniport Driver with WPP Tag: 69388
  - 5
    - EngWritePrinter and DrvEnablePDEV please help me out with one problem in EngWritePrinter, when i was trying to call this function it returns an error with error code of 6 (ERROR_INVALID_HANDLE). As DDK says i should use a DrvEnablePDEV's last parameter (which i save in PDEV structure), but an error still remains. i am writing to you cause noone could help me. And one more problem in MS Word, when i open a print window (ctrl+p) and choose my printer, it says the i don't have enough memory. I am using WinXp sp2, and i wrote graphics dll and interface dll. I build the driver with checked version and with free version (in DDK) Tag: Ndis Miniport Driver with WPP Tag: 69375
  - 6
    - EngWritePrinter error!!! please help me out with one problem in EngWritePrinter, when i was trying to call this function it returned an error with error code of 6 (ERROR_INVALID_HANDLE). As DDK says i should use a DrvEnablePDEV's last parameter (which i save in PDEV structure), but an error still remains. i am writing to you cause noone could help me. And one more problem in MS Word, when i open a print window (ctrl+p) and choose my printer, it says the i don't have enough memory. I am using WinXp sp2, and i wrote graphics dll and interface dll. I build the driver with checked version and with free version (in DDK) Tag: Ndis Miniport Driver with WPP Tag: 69372
  - 7
    - laptops that support S1 Hi all, for WHQL testing PCCards we need laptops that support S1 state in addition to S3. We have some Dell D600s that do, but they are getting a little old and flakey. Does anyone know of a current laptop that does support S1? Thanks in advance. Tag: Ndis Miniport Driver with WPP Tag: 69370
  - 8
    - How to use 4th parallel port on WinXP??? Hi, I have 4 physical parallel ports on the board, and I have set "LPT4:" on the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Ports. But I can just use random 3 of 4 parallel ports. The combo box "LPT Port Number:" of the page tab "Port Settings" on the device manager can only be chosen from LPT1 to LPT3. How can I do to use all 4 parallel ports??? By the way, I use the same parallel port driver, i.e. parport.sys, and the .inf file is also the same, msport.inf, except allocate some required resource, such as I/O ports and IRQ, for each parallel port. Thanks all... Tag: Ndis Miniport Driver with WPP Tag: 69369
  - 9
    - selsusp driver can't standby from C3 state. Hi selsusp driver is ddk sample driver of DDK\3780.1830. I connected between selsusp driver and EzUsb chip. The PC loaded selsusp driver could not go to standby state. Instead of going standby state, PC said below message. The driver for the 'selSusp.sys test driver' device is preventing the machine from entering stanby.please all applications and try again. IF the problem persists, you may need to update this driver. What should I do to prevent this message and to go to standby mode ? Please tel me some comment or document about it. Tag: Ndis Miniport Driver with WPP Tag: 69367
  - 10
    - How I can get the size of physical memory .. .. installed in the PC from kernel level (2k, XP, ...)? Values like 'small', 'medium' and 'large' doesn't help, I need the number of bytes! Thanks in advance, Stefan Tag: Ndis Miniport Driver with WPP Tag: 69364
  - 11
    - Driver installation problems I have tried this question earlier with little luck, so here goes again... What is the difference between Add Hardware Wizard and devcon install? My ISA non-pnp driver installs correctly with the wizard. The memory range resource is assigned ok, but it has a IRQ resource conflict. That is resolved at next reboot, due to the IRQ is reserved for legacy ISA devices in BIOS. But when I try the same thing with devcon install I only get the IRQ resource conflict. The memory range resource is not assigned at all, it only shows a questionmark in the resources tab in the device manager. After reboot it is exactly the same. Another difference is that when I look at the "Device Instance ID" in the device manager it reports "ROOT\UNKNOWN\0000" after install with wizard and "ROOT\CAN\0000" after devcon install. CAN is my own device class. I can also see in SetupApi.log that devcon install performs more steps, including DIF_SELECTBESTCOMPATDRV. Please help me, I need an functional installation utility for my driver. /GÃ¶ran Tag: Ndis Miniport Driver with WPP Tag: 69362
  - 12
    - How to pause or resume a new print job on print server? Hi, I need to write an app to take control of the printing process to enforce some security policy. My app running on network printer server needs to be actived as soon as a new print job comes in. It checks the ip address where the new job is from and blocks some special users. Perhaps, it is a choice to develop a custom print processor. But it is too difficult for me that I am not clear about DDK. Can I call OpenPrintProcessor and ControlPrintProcessor for the default processor: WinPrint? How to trap a new print job? Any ideas or code samples? Thank you very much in advance. Tag: Ndis Miniport Driver with WPP Tag: 69357
  - 13
    - NEC DVD RW ND 3520A Nero problems I constantly get an error while burning anything on this writter. No matter if it is Image, DVD, CD, ... I'm not sure is it the drivers, or something else. The OS is WinXP Pro with SP2. Nero is UltraEdition 6. Tag: Ndis Miniport Driver with WPP Tag: 69353
  - 14
    - Special USB Device handling Hi All, Is it possible to configure PNP manager under either Win2k or WinXP such that if a USB device with specific vendor ID and product ID is plugged in, the device manager will install a special pre-defined driver? I know it's probably impossible or very unlikely to do what I want. Any response is greatly appreciated. Best regards, George Tag: Ndis Miniport Driver with WPP Tag: 69339
  - 15
    - Question about MiniportSendPackets It has been discussed before. But still can't find the answer on this news group. The DDK said, MiniportSendPackets can transfer some number of packets, specified as an array of packet pointers, over the network. VOID MiniportSendPackets( IN NDIS_HANDLE MiniportAdapterContext, IN PPNDIS_PACKET PacketArray, IN UINT NumberOfPackets ); We develop two kinds of NDIS driver, one is PCI/CardBus network driver and the other one is USB network driver. On the PCI/CardBus network driver the MiniportSendPackets can have some number of packets. But on USB network driver the MiniportSendPackets always get one number of packets. Of course OID_GEN_MAXIMUM_SEND_PACKETS response more than one. Is this a limitation on USB network driver (NDIS-WDM) why MiniportSendPackets always get one number of packets to send? Because I can't find the answer? Anybody has some idea on that? There is a simple way to see NumberOfPackets can have more than one number of packets or not by ping your device from the other side of machine with packet size large than 1500. For example, ping DUT -l 1800. Tag: Ndis Miniport Driver with WPP Tag: 69337
  - 16
    - HELP! HCT crash with bug check code 0xFC Hi Sir, I have encountered a big problem in HCT testing. We have a USB camera device that is passed WHQL in 32bit XP. Now I am porting it to WinXP x64 platform. After porting, I use it on WinXP x64 OS very well. I can preview by both AMCap and GraphEdit. But now the problem comes, when I want to take this driver to go testing HCT 12.1.01 test kit, It crashes. The HCT is crashed at selecting device step, not any testing step! I have check the crash dump for seeking my driver's fault. But I don't see any thing happening from my driver codes. The bug check code is 0xFC, that is a DEP error. I got no idea about what's going on. I also try to set TRAP in my code to look last code executing in my code. it just the SRB_NOTIFY_IDLE_STATE, but I don't support this SRB. I just simply complete it with STATUS_NOT_IMPLEMENTED. Please help me to solve this problem, I appreciate your kindness. The information I got from crash dump is below. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc) An attempt was made to execute non-executable memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffffa8000a1dbc0, Virtual address for the attempted execute. Arg2: aef0000014f49163, PTE contents. Arg3: fffffadfeefda890, (reserved) Arg4: 0000000000000001, (reserved) Debugging Details: ------------------ DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xFC CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800010b7bbd to fffff80001041910 LOCK_ADDRESS: fffff800011a04e0 -- (!locks fffff800011a04e0) Resource @ nt!IopDeviceTreeLock (0xfffff800011a04e0) Shared 1 owning threads Threads: fffffadff325d470-01<*> 1 total locks, 1 locks currently held FAULTING_THREAD: fffffadff325d470 PNP_TRIAGE: Lock address : 0xfffff800011a04e0 Thread Count : 1 Thread address: 0xfffffadff325d470 Thread wait : 0x2a283 TRAP_FRAME: fffffadfeefda890 -- (.trap fffffadfeefda890) NOTE: The trap frame does not contain all registers. Some register values may be zeroed. rax=fffffa8000a1dbc0 rbx=fffffadff35a6a00 rcx=fffffa8000a1dbc0 rdx=fffffadfeefdaa78 rsi=fffffadff35a6c80 rdi=fffffadff26e9000 rip=fffffa8000a1dbc0 rsp=fffffadfeefdaa28 rbp=fffffadff3300b20 r8=0000000000000000 r9=0000000000000000 r10=fffff80001174180 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc fffffa80`00a1dbc0 48004a00 add [rdx],cl ds:6a00:aa78=?? Resetting default scope STACK_TEXT: fffffadf`eefda7b8 fffff800`010b7bbd : 00000000`000000fc fffffa80`00a1dbc0 aef00000`14f49163 fffffadf`eefda890 : nt!KeBugCheckEx fffffadf`eefda7c0 fffff800`01040559 : 00000001`f306fc01 fffffadf`eefda898 fffffadf`eefda800 fffffadf`f0867502 : nt!MmAccessFault+0x4e1 fffffadf`eefda890 fffffa80`00a1dbc0 : fffff800`01369d2f fffffa80`0298c660 fffffa80`0298c660 00000000`00000000 : nt!KiPageFault+0x119 fffffadf`eefdaa28 fffff800`01369d2f : fffffa80`0298c660 fffffa80`0298c660 00000000`00000000 fffffadf`f3386b30 : 0xfffffa80`00a1dbc0 fffffadf`eefdaa30 fffff800`0130f237 : 00000000`00000000 fffffadf`eefdabd8 00000000`00000000 fffffa80`009a4800 : nt!PpCriticalGetDeviceLocationStrings+0x263 fffffadf`eefdab40 fffff800`0128d449 : fffffadf`f325d470 00000000`00000000 00000000`00000001 00000000`00000001 : nt!PiControlGetPropertyData+0x379 fffffadf`eefdabd0 fffff800`01041422 : fffffadf`f325d470 00000000`00b7f2d0 00000000`00000000 fffffadf`f325d470 : nt!NtPlugPlayControl+0x1d2 fffffadf`eefdac70 00000000`78ef1eca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 00000000`00b7f278 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78ef1eca STACK_COMMAND: .thread fffffadff325d470 ; kb FOLLOWUP_IP: nt!KiPageFault+119 fffff800`01040559 85c0 test eax,eax SYMBOL_STACK_INDEX: 2 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: nt!KiPageFault+119 MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 42436096 FAILURE_BUCKET_ID: X64_0xFC_nt!KiPageFault+119 BUCKET_ID: X64_0xFC_nt!KiPageFault+119 Followup: MachineOwner --------- Tag: Ndis Miniport Driver with WPP Tag: 69324
  - 17
    - how can i view old posts? hi all i would like to review old posts to this newsgroup. how can i do this? tnx assaf Tag: Ndis Miniport Driver with WPP Tag: 69312
  - 18
    - JOB: looking for a Display Mirror Driver developer hi i am looking for a Display Mirror Driver developer. i am willing to pay for such a job. i need to capture all activities on the desktop, save them into a data stream and be able to display them from the data stream. i am willing to work in phases. if you are or you know anyone who can develop such a driver, please help me contact him/her. any and all help in helping me recruit such a develper is most appreciated. assaf assafwo@hotmail.com Tag: Ndis Miniport Driver with WPP Tag: 69299
  - 19
    - Specifying a resource for mf.sys Is there a way of specifying a resource override for mf.sys to use for a PCMCIA card that is compliant with the PCMCIA Multifunction standard. I am having problems getting the mf.sys to take any notice of a top level inf file for the card. It seems to go straight into installing via mf.inf. I need to specify an overide to the defualt parameters and this isn't working in the child function inf files. Paul Harrison Tag: Ndis Miniport Driver with WPP Tag: 69258
  - 20
    - Encryption filter driver Hi I'm writning filter driver which encrypts/decrypts files on the fly. I took sources of filemon from sysinternals as a starting point and added encryption functionality. Works fine, but I have two problems: 1) When the application uses file - memory mapping, I cannot capture any read/write request. I found that data is accessed directly in cache manager, but I still don't know how to solve this problem. "File System Internals" by Rajeev Nagar didn't help me :) 2) When I map a network drive, \\server\folder\file.txt to x: I can capture requests to the x:\file.txt , but I need to capture \\server\folder without using network drive mapping mechanism. I didn't find anything interesting in IFS kit samples, but maybe I missed something ? Does anyone know any useful sample source code, or can explain me how to solve theese two problems? It must work on W2k and later. I found that XP has for example callback mechanism that can be used to solve my first problem, but working only on XP is not enough :( Thanks a lot. Pawel Buchaniec Tag: Ndis Miniport Driver with WPP Tag: 69245
  - 21
    - The priority of routing table in Windows? Dear all, If multiple NICs set different gateways as the default routing, how does tcpip.sys choose the interface to send packet if the destination IP is outsides? For example, the routing table is: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 20 0.0.0.0 0.0.0.0 192.169.1.1 192.169.1.101 20 Can I control the Windows to send packet always through the specified interface, such as 192.168.1.101, even through I reset other interfaces. Thanks! -Liang Tag: Ndis Miniport Driver with WPP Tag: 69230
  - 22
    - Portmon results in STATUS_INVALID_DEVICE_REQUEST Hello all, I'm trying to get some serial communications to work with an Usb-rs232 converter. The problem I started with is that I cant read (I'm getting timeouts) from the converter from my code. It does work when I read from a 'real' rs232 port, and it also works with Hyperterminal in both directions. To solve this I've tried to connect the portmon utility to the port. But when I first start the portmon utility and then try to get the PDO thru the following code (below, mostly copied from toastmon) I get an STATUS_INVALID_DEVICE_REQUEST (C0000010) from the call to IoCallDriver. This happens both on the 'real' rs232 and also on the usb convertor one. any suggestions/help on this? Regards Sander static NTSTATUS getTargetDevicePdo ( PDEVICE_OBJECT devObj, PFILE_OBJECT fileObj, PDEVICE_OBJECT* pdo ) { KEVENT event; NTSTATUS status; PIRP irp; IO_STATUS_BLOCK ioStatusBlock; KeInitializeEvent( &event, NotificationEvent, FALSE ); irp = IoBuildSynchronousFsdRequest ( IRP_MJ_PNP, devObj, NULL, 0, NULL, &event, &ioStatusBlock ); status = STATUS_INSUFFICIENT_RESOURCES; { PIO_STACK_LOCATION irpStack; irpStack = IoGetNextIrpStackLocation( irp ); irpStack->MinorFunction = IRP_MN_QUERY_DEVICE_RELATIONS; irpStack->Parameters.QueryDeviceRelations.Type = TargetDeviceRelation; irpStack->FileObject=fileObj; irp->IoStatus.Status = STATUS_NOT_SUPPORTED; status = IoCallDriver( devObj, irp ); if (status == STATUS_PENDING) { KeWaitForSingleObject( &event, Executive, KernelMode, FALSE, NULL ); status = ioStatusBlock.Status; } // Here status==STATUS_INVALID_DEVICE_REQUEST. if (NT_SUCCESS( status)) { PDEVICE_RELATIONS deviceRelations; deviceRelations = (PDEVICE_RELATIONS)ioStatusBlock.Information; ASSERT(deviceRelations); *pdo= deviceRelations->Objects[0]; ExFreePool(deviceRelations); } } return status; } Tag: Ndis Miniport Driver with WPP Tag: 69214
  - 23
    - Monitoring 1394 communication Hi, Which of the tools, including in DDK, should i use to monitoring 1394/firewire communication ?? Thank you in advance. BR Peter Tag: Ndis Miniport Driver with WPP Tag: 69205
  - 24
    - How to bind passthru to NDIS USB driver Following on from earlier, and pestering Thomas, I'd like to throw this one in the ring... I'm trying to load the passthru intermediate driver (and Thomas's variants thereof) and bind it to a USB data-link cable device. These cables link two PCs, providing ethernet connection between them, over USB. The passthru intermediate driver binds to the NIC and the modem port (NDISWAN), but not to the USB devices (two connected). The USB devices appear in the Network Connections window as 'Local Area Connection's . Their device name is given as 'USB Virtual Network Adapter #n'. They transmit IP and act like an ethernet connection over an ethernet NIC. In addition to that, they can automatically provide an IP address, to each connected PC -ie contain a DHCP server each end. The class in the INF file for the USB devices is 'net'. I'm using Thomas's passthru sample INFs unmodified (though I've tried a few changes!) So my question is... How do I get a passthru sample driver to bind to the USB devices? What changes do I need to make to the INF file? (I'm not using a notify object.) Tag: Ndis Miniport Driver with WPP Tag: 69198
  - 25
    - AVStream Device - Isochronous or Bulk Hi, I am new to developing applications for AVStream-based devices and currently I'm trying to display video over a usb device. I understand that we can use MS's usbvideo.sys for this purpose but how do we know if we are transferring the data over the isochronous or the bulk endpt and is there a way to choose either one? Thanks. Tag: Ndis Miniport Driver with WPP Tag: 69197

Hi,
I am trying to get WPP Trace functionality added to a NDIS miniport driver
written for Windows 2000 in C++? Does any one have any samples? Since my code
was not compiliing I tried putting the WPP macros in a .C file. Then I called
these function from the C++ code. The code compiles but I don't see any
messages. I know I have the traceview configured properly. In addition, when
I try to check if WPP is activated using WPP_LEVEL_ENABLED macro, it returns
false. Any ideas?

I call WPP_SYSCONTROL first in driver entry then WPP_INIT_TRACE in my
initialize function. I use the PDEVICE_OBJECT returned from
NdisMRegisterDevice function.

Shreyash

Top

Re: Ndis Miniport Driver with WPP by Eliyas

Eliyas
Sun Sep 11 21:57:24 CDT 2005

Event tracing on Windows 2000 is not as straight forward as it's on XP and
later OSes. If you go thru the toaster/feature2 function driver, you will
reallize that you have to jump thru few hoops to get the tracing. To list
few: you have to use a device object to init tracing as opposed to
DriverObject; initialization has to happen in the context of start device as
opposed to DriverEntry; have to handle WMI irps to enable/disable tracing
events. Now doing all this in a NDIS miniport driver is not easy, especially
handling WMI irps unless you override the dispatch routines set by NDIS -
not a good thing to do.

I tried out tracing in one of my NDIS miniport drivers and got it to work on
XP. The steps to implement tracing in a NDIS miniport driver is no different
from a WDM driver when it comes to XP and later OSes.

> I call WPP_SYSCONTROL first in driver entry then WPP_INIT_TRACE in my
> initialize function. I use the PDEVICE_OBJECT returned from
> NdisMRegisterDevice function.
>

I don't have access to DDK now but I think WPP_SYSCONTROL sets it own
routine for handling sys-control irps. Now after calling this macro, if you
call NDIS to register your miniport, it's going to override what ever is set
in the DriverObject's dispatch handler with it's own handler. May be that
the tracing is not working in your case.
--
--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/driver/default.mspx
http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx

Top