Using WPP in kernel mode drivers that are build using VS/VS2005

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
 - WttLogger with DTM Hi, I am new in here and I'm currently configuring my tests to run with DTM. Unfortunatly, I cannot access the windows.beta.wdk.dtm newsgroup due to access problem :( My question is: Where can I find the WTTLogger.h and .lib ? I need them to use the CWTTLogger class within my tests. Anyone started using DTM yet ? Thank you Sylvain Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84777
 - 2
 - Whats with red x's in DDK Build 1830? I needed to update my DDK to 1830 and notice all of the red x's which mean that these marked features are not available. No audio stuff, most samples are not available, win xp headers, etc.. What am I missing here? I dont recall my 3790 doing this at all. Thanks, Mike Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84776
 - 3
 - 1394B S800 Dear sir, When will the Microsoft Software driver support S800 in 1394B PCI card ? Where can I find the S800 driver for 1394B PCI card ? best regards, David Tang Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84763
 - 4
 - 1394 DDI document Dear sir, (1) where can I find the "1394 DDI document" ? (2) How to enable BOOT UP with "1394 diag mode" ? (I do not want to use UI to start the "1394 diag mode") Best regards, Please, help me!! Thanks, David Tang Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84762
 - 5
 - Newbie Question : PnP & PS2 ? AFAIK there is no PnP support for PS2 interface in Windows kernel , this is because of PS2 hw or not ? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84754
 - 6
 - File System - large file random access Hi, Is it possible to insert data in the middle of a file without affecting other data? I need this to improve system performance. Assume a large database file (100MB). Now I am inserting 10 bytes in the middle of the file(50MB). What the actions will be taken by the file system? I am assume one of the following action will be taken 1) Insert the new 10 bytes at the 50MB offset and move the bottom half of the 50MB data 10 byte below and allocating a new disk block in the end if required. 2) Allocating new disk block in the middle for the 10 byte and just doing the re-linking. Method 2 will be faster because it requires less number of disk accesses for large files. Is there any file system supporting this kind of functionality TIA, Samuel Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84752
 - 7
 - Getting STATUS_TOO_LATE with virtual disk I have a driver that creates a virtual NTFS formatted removable disk drive that is actually just a file on an NTFS formatted hard disk. Each time the system is shutdown, NTFS wants to write data to the virtual disk. Usually, writes succeed but at shutdown calling ZwWriteFile to carry out the write requests results in STATUS_TOO_LATE. Is there a way to resolve this? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84749
 - 8
 - Are VISTA RC1 and WDK RC1 the same ISO file? Hi, I am new here,and I am an engineer for our products driversâ?? WHQL testing. Our drivers had passed HCT testing and got microsoft logo'd driver. However, we need to transfer to DTM testing tool to retest our drivers. So I attend Microsoft connect program, and I can download WDK RC1 from Microsoft connect . And I also heard of VISTA RC1 has released now, Iâ??m wondering that WDK RC1 and VISTA RC1 are the same ISO file? If not, where can I download VISTA RC1? I think I should test our drivers on VISTA platform asap. Can anyone help me out ? Thanks! Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84747
 - 9
 - determine if using 802.1x Anyone know if it is possible to determine programatically if a connection that I am using, used 802.1x to authenticate, when connecting to my switch? --joubert Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84746
 - 10
 - WinCE modifications Serial_class to USBser class Anybody can help to modify my existing serial class to USBser class for USBser.sys support for XP Host, Please help me, who are using Windows Mobile 5.0 or Windows CE 6.0 beta this two platform have full support of USBser.sys. for USB modem class on Win CE device. for refrance please check it out http://groups.google.com/group/microsoft.public.windowsce.embedded.vc/browse_thread/thread/cc1542edb42abc63/4135e4aa3d883c8e?lnk=st&q=&rnum=17&hl=en#4135e4aa3d883c8e I able to connect device by modifying in descriptor but I am still not able to open COM port in Hyperterminal to test...:( in Windows Mobile 5 platform builder WINCE500\public\common\oak\drivers\usbfn\class\serial ---->USBFnDrv.cpp in Windows CE 6 beta may be they have give seprate class as WINCE500\public\common\oak\drivers\usbfn\class\USBser I appreciate who would give me the direction. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84743
 - 11
 - Checking if path is valid. Hello, I am creating a keyboard filter logger as a learning experience. So far, everything is going pretty smooth, and I think i am understanding the basics. I am having one problem though. I allow the user to specify the path of where he or she wants the log file in the registry. With this value, I will be calling NtCreateFile to create the log file and write it etc.. Is there a way to validate the path though? I was thinking about calling NtOpenFile to see if it fails and if it fails, then I could tell if the path that is provided in the registry is broken, but that seems a bit dirty. I was hoping to find a clean way to do it. Also, if I pass in "c:\\log.txt" as opposed to "\\DosDevices\\c:\\log.txt" to NtCreateFile, would it still work properly? or must I pass in the full path. thanks Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84742
 - 12
 - IoRegisterDeviceInterface outside of AddDevice I would like to register a different device interface GUID depending on my PCI Device ID (using the same binary WDM driver). 1. Is it OK to wait until the IRP_MN_START_DEVICE minor function to call IoRegisterDeviceInterface? I don't want to access the device until I know it's started, and I can't select the proper interface to register until I know which device I've got... 2. If it is not OK to register the device interface then, is there a way to get my Hardware ID when I'm in the AddDevice routine? Thanks Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84737
 - 13
 - Extra ObReferenceObject() -- is this why? I think I almost understand what this statement from the WDM book means (in reference to sending an asynchronous IRP to another driver): "The calls to ObReferenceObject and ObDereferenceObject that precede and follow the call to IoCallDriver ... are necessary only when you've used IoGetDeviceObjectPointer to obtain the DeviceObject pointer and when the completion routine (or something it calls) will release the resulting reference to a device or file object." I can only think that this also assumes there's code immediately after IoCallDriver() that accesses the device object (for some reason I can't think of) and may end up running either before or after the completion routine. If there is no code like that then I'd think the reference from IoGetDeviceObjectPointer() and the dereference from the completion routine would pair with each other and be safe. The book's examples are all in this pseudo-code style with missing details, and it doesn't actually show whether code like that would or wouldn't be there. I don't see any similar real examples in the included CD samples. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84733
 - 14
 - Getting a value from the registry. Hello, I am having problems reading a value from the registry... For some reason, the return value is always empty. Would anyone be willing to glance over my code? reg_key is the key reg_path is the path to the registry which is passed in from Driver Entry - Registry Path val is the out value that will store the result. thanks ------------------------------------------------------ NTSTATUS GetRegistryValue( IN UNICODE_STRING reg_key, IN PUNICODE_STRING reg_path, OUT PUNICODE_STRING val ) { NTSTATUS status; HANDLE hkey; OBJECT_ATTRIBUTES obj_attrib_reg; ULONG size = 0; // Opening the registry to query it InitializeObjectAttributes( &obj_attrib_reg, reg_path, (OBJ_KERNEL_HANDLE | OBJ_CASE_INSENSITIVE), NULL, NULL ); status = STATUS_UNSUCCESSFUL; status = ZwOpenKey(&hkey, KEY_READ, &obj_attrib_reg); // If it is successful, it means that we were able to open the registry value and // that there exists a registry key with the name provided above. if( NT_SUCCESS(status)) { status = STATUS_UNSUCCESSFUL; status = ZwQueryValueKey( hkey, &reg_key, KeyValuePartialInformation, NULL, 0, &size); // If we were able to successfully query for the key, then the key is valid. // This does not mean that the value was empty. if( !(status == STATUS_OBJECT_NAME_NOT_FOUND || size == 0 )) { size = min(size, PAGE_SIZE); PKEY_VALUE_PARTIAL_INFORMATION vpip = (PKEY_VALUE_PARTIAL_INFORMATION)ExAllocatePool(PagedPool, size); if( !vpip ) { ZwClose(hkey); return STATUS_UNSUCCESSFUL; } status = STATUS_UNSUCCESSFUL; status = ZwQueryValueKey( hkey, &reg_key, KeyValuePartialInformation, vpip, size, &size); if(!NT_SUCCESS(status)) { ZwClose(hkey); return STATUS_UNSUCCESSFUL; } // Copying my data into the string so that I could use it when I return PCANSI_STRING my_data = (PCANSI_STRING)vpip->Data; RtlAnsiStringToUnicodeString( val, my_data, TRUE); ExFreePool(vpip); } else { ZwClose(hkey); return STATUS_UNSUCCESSFUL; } ZwClose(hkey); } else { return STATUS_UNSUCCESSFUL; } return STATUS_SUCCESS; } Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84731
 - 15
 - Byte array of each page from the printer driver I have implemented a virtual printer driver using sample Microsoft unidrv approch. I want to split the pages so that I can get the byte array of each page individually. After all pages byte array I recieves, I need to call a .Net application which process these pages one by one & send data to our customize application. Thanks, Sahaj Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84730
 - 16
 - DMA abstraction for x64 drivers / performance issues This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C6D0E3.D7A869D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Considering page 9 of the following document :=20 http://www.microsoft.com/whdc/driver/kernel/dma.mspx and dealing with 64-bit adapters used in x64 machines that will have at = least 8GB RAM, featuring the AMD64 IOMMU implementation (as opposed to = bouncing buffers above 4GB), I wonder if opting for DMA abstraction = could tax performance by more than 30% in some cases. Below is Microsoft's rationale :=20 The Windows PHYSICAL_ADDRESS data structure has always been 64 bits. If = you expect an address that can be safely truncated to 32-bits, it is = good programming practice to ASSERT that the high half of the address is = zero. =B7 The bus addressing capability. Driver writers that follow = the Windows DMA model never have to be concerned about the addressing = capability of the bus to which their device is attached. For example, = the driver for a PCI bus device that is capable of 64-bit addressing = does not need to be aware of whether the device is attached to a 64-bit = capable PCI bus. Just as with the amount of physical memory present on = the machine, the addressing capability of the bus is made transparent by = the standard Windows DMA implementation. Bus addressing transparency is maintained for PCI buses with 64 address = lines, as well as for PCI buses that support the dual address cycle = (DAC) mode of 64-bit addressing. =20 The above features apply only to drivers that follow the model based on = the Windows DMA abstraction. Drivers that take shortcuts by not = following the model, often in an unnecessary attempt at performance = optimization, will receive unpredictable levels of support for the = features described above, depending on precisely which parts of the DMA = model they use. Thanks,=20 Christopher ------=_NextPart_000_0017_01C6D0E3.D7A869D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV>Considering page 9 of the following = document :=20 </DIV> <DIV> <A=20 href=3D"http://www.microsoft.com/whdc/driver/kernel/dma.mspx">http://www.microsoft.com/whdc/driver/kernel/dma.mspx</A><= /P> and dealing with 64-bit adapters used in x64 machines that = will have=20 at least 8GB RAM, featuring the AMD64 IOMMU implementation (as = opposed=20 to bouncing buffers above 4GB), I wonder if opting for DMA=20 abstraction could tax performance by more than 30% in some=20 cases. Below is Microsoft's rationale : The Windows <SPAN=20 style=3D"FONT-WEIGHT: normal">PHYSICAL_ADDRESS data = structure has=20 always been 64 bits. If you expect an address that can be safely = truncated to=20 32-bits, it is good programming practice to ASSERT that the high half of = the=20 address is zero. <FONT=20 size=3D2>=B7<SPAN=20 style=3D"FONT: 7pt 'Times New = Roman'">        =20 The bus addressing capability. Driver writers that follow = the=20 Windows DMA model never have to be concerned about the addressing = capability of=20 the bus to which their device is attached. For example, the driver for a = PCI bus=20 device that is capable of 64-bit addressing does not need to be aware of = whether=20 the device is attached to a 64-bit capable PCI bus. Just as with the = amount of=20 physical memory present on the machine, the addressing capability of the = bus is=20 made transparent by the standard Windows DMA = implementation. Bus addressing transparency is maintained for PCI buses with 64 = address=20 lines, as well as for PCI buses that support the dual address cycle = (DAC) mode=20 of 64-bit addressing. <FONT=20 size=3D2> <?xml:namespace prefix =3D o ns =3D=20 "urn:schemas-microsoft-com:office:office" = /><o:p></o:p> The above features apply only to drivers that follow the model = based on=20 the Windows DMA abstraction. Drivers that take shortcuts by not = following the=20 model, often in an unnecessary attempt at performance optimization, will = receive=20 unpredictable levels of support for the features described above, = depending on=20 precisely which parts of the DMA model they use.   Thanks,=20 Christopher  </DIV></BODY></HTML> ------=_NextPart_000_0017_01C6D0E3.D7A869D0-- Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84721
 - 17
 - Computer Crash - Device Driver I own a Gateway 500X puter purchased in June 2003. Recently I have been experiencing complete shutdowns - two days ago 5 times. Here is the message error I received: "You are receiving this message because a device driver installed on your computer caused a stop error message. This error message required a restart of your computer. After the restart your computer should continue to operate normally, however the error may re-occur until the problem is corrected. A stop error occurs when your computer encounters an error from which it cannot recover. This is usually caused by a device driver which encounters an unhandled exception or performs an illegal operation. When the operating system detects this situation it is stopped to prevent future problems, such as data loss or further system instability" When I purchased the 500X a red Drivers CD came with the unit. The question I have is should I reinstall the drivers using this CD and will this correct the problem? Or is there another solution out there? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84720
 - 18
 - Windows 2000 not reloading the driver Hello, Im having a wierd issue in Windows 2000, does not appear in XP. I insert my USB 1.1 device, install the drivers, and drivernetry and adddevice and everything get called and the drivers gets loaded nicely. If i remove the device unload is called. Now begins the strange part. When i reinsert the device, nothing at all happens. Sometimes windows tells me it found a usb device, not recognised and no function driver loaded. Sometimes it just shows me usb device in device manager and nothing is loaded. Here is the even stranger part, if i do the same action, but via a usb hub (unpowered), it works like a charm. Ive been trying to fix this issue several days now, buit im not any closed. What could cause such a strange behavior? Please give me some suggestions! Regards Wilhelm Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84705
 - 19
 - DIFx and virtual devices Hi! I want to install a virtual system device (root\MyBusDevice) for x64 systems. Is that possible using the DIFx tools? Cause I am getting these DIFx logs: DIFXAPP: INFO: Looking for Model Section ... DIFXAPP: INFO: No drivers installed. No devices found that match driver(s) When I use the DevCon sample tool from the DDK it works for x64 systems. I just read that the Vista SDK includes a new version of the DIFx tools -> Version 2.10. I will give it a try. Thanks Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84701
 - 20
 - Help Needed Good Morning to All, I am working on File System Development for an Embedded OS to NandFlash. I need to know about the FAT file system concepts, its working principles, interaction between File System and File system Driver. If you know any books or online resources pls send me. I also have a query : How does the OS able to find the size of the device when formatting? Like floppy and Harddisk. Are these information will be stored in the device itself? Thank you Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84689
 - 21
 - Where do I get Signability Test? Hi, I have tried to download Signability Test tool from the following site: Download WHQL Tests, Procedures and Forms http://www.microsoft.com/whdc/whql/WHQLdwn.mspx Signability Test https://winqual.microsoft.com/com/mercsetup.exe However, the link for the tool seems dead and I could not download it. Does anyone know how to get this tool? Especially, I would like to obtain the newest version (v2.19). (I know it is included in WDK, but I need separated package as well.) Thanks Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84687
 - 22
 - Driver prevent S1 standby but aloow S3 standby ? Hi, Our device driver is a USB port driver sitting below a mouse class driver. I found if I set the BIOS option "Suspend to RAM enabled (S3)".. WinXP is able to go to standby with our deivce attached. While if BIOS option "Suspend to RAM disabled(S1)".. system would claim that our driver prevent the system going to standby.. The following is a bit of debug info... I found our driver return success for Query Power,, but system just set the device to D0..when S1 .. ,, (while it would set device to D3 when S3 Query..) Any hint for that ? Thanks. -chueh8 TSC(IRQL 00): TSCPowerDispatch++. IRP 8273AE48 TSC(IRQL 00): IRP 8273AE48 IRP_MJ_POWER TSC(IRQL 00): IRP_MN_QUERY_POWER TSC(IRQL 00): PowerSystemSleeping1 TSC(IRQL 00): ............Query Power 8273ae48.... TSC(IRQL 00): query system power TSC(IRQL 00): TSCSystemPowerDispatch++. IRP 8273AE48 TSC(IRQL 00): TSCSystemPowerCompletionRoutine++. IRP 8273AE48 STATUS 0 TSC(IRQL 00): KKK1 TSC(IRQL 00): TSCGetDevicePowerState++. PowerSystemSleeping1 TSC(IRQL 00): System State =2 TSC(IRQL 00): DeviceExtension->DeviceCaps.SystemWake =4 TSC(IRQL 00): DeviceExtension->DeviceCaps.DeviceState[SystemState] =3 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD3 =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD2 =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD1 =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD0 =1 TSC(IRQL 00): 333 TSC(IRQL 00): TSCGetDevicePowerState--. PowerDeviceD3 STATUS 0 TSC(IRQL 00): Get Device Power state status=0 TSC(IRQL 00): KKK2 TSC(IRQL 00): TSCDevicePowerCompleteCallback++. IRP 8273AE48 TSC(IRQL 00): TSCDevicePowerCompleteCallback-- TSC(IRQL 00): KKK4 TSC(IRQL 00): TSCSystemPowerCompletionRoutine--. Irp 8273AE48 STATUS 103 TSC(IRQL 00): TSCSystemPowerDispatch--. IRP 8273AE48 TSC(IRQL 00): TSCPowerDispatch--. IRP 8273AE48 STATUS 103 TSC(IRQL 00): TSCPowerDispatch++. IRP 8273A008 TSC(IRQL 00): IRP 8273A008 IRP_MJ_POWER TSC(IRQL 00): IRP_MN_SET_POWER TSC(IRQL 00): PowerSystemWorking TSC(IRQL 00): ............PDO set power 1 .... TSC(IRQL 00): set sys power TSC(IRQL 00): TSCSystemPowerDispatch++. IRP 8273A008 TSC(IRQL 00): TSCSystemPowerCompletionRoutine++. IRP 8273A008 STATUS 0 TSC(IRQL 00): KKK1 TSC(IRQL 00): TSCGetDevicePowerState++. PowerSystemWorking TSC(IRQL 00): System State =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.SystemWake =4 TSC(IRQL 00): DeviceExtension->DeviceCaps.DeviceState[SystemState] =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD3 =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD2 =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD1 =1 TSC(IRQL 00): DeviceExtension->DeviceCaps.WakeFromD0 =1 TSC(IRQL 00): 111 TSC(IRQL 00): TSCGetDevicePowerState--. PowerDeviceD0 STATUS 0 TSC(IRQL 00): Get Device Power state status=0 TSC(IRQL 00): KKK2 TSC(IRQL 00): TSCPowerDispatch++. IRP 82440430 TSC(IRQL 00): IRP 82440430 IRP_MJ_POWER TSC(IRQL 00): IRP_MN_SET_POWER TSC(IRQL 00): PowerDeviceD0 TSC(IRQL 00): ............PDO set power 1 .... TSC(IRQL 00): set device power TSC(IRQL 00): device same power TSC(IRQL 00): device same power 2 TSC(IRQL 00): TSCPowerD0PrepCallback++. IRP 82440430 TSC(IRQL 00): TSCDevicePowerCompleteCallback++. IRP 8273A008 TSC(IRQL 00): TSCDevicePowerCompleteCallback-- TSC(IRQL 00): TSCPowerD0PrepCallback-- TSC(IRQL 00): TSCPowerDispatch--. IRP 82440430 STATUS 103 TSC(IRQL 00): KKK4 TSC(IRQL 00): TSCSystemPowerCompletionRoutine--. Irp 8273A008 STATUS 103 TSC(IRQL 00): TSCSystemPowerDispatch--. IRP 8273A008 TSC(IRQL 00): TSCPowerDispatch--. IRP 8273A008 STATUS 103 Abort: \Driver\Mouclass \Device\PointerClass1 irp (8273ae48) QueryPower-Sleeping1 status c00002d3 Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84683
 - 23
 - Need guidance on Generic USB IO (by using PipeHandles??) I am a Win32 application programmer and a newbie to USB driver development. I am stuck with the changed requirements for my application, please guide me on this. About the Application: 1. The application is intended to give a solution to control most USB devices, mainly printers(Inluding DOT4 printers). 2. The communication with USB devices is implemented as a Win32 User DLL which the Application(Java) will load dynamically and communicate with the USB device. 3. This DLL uses the Connection Address(Port Address) and uses it to fetch the corresponding Symbolic Link(Device Path). The symbolic link is sent to the CreateFile() to obtain the Device Handle, which is finally used for further communication with the USB device using ReadFile()/WriteFile(). 4. The application currently uses only the drivers that are shipped with Windows OS. And no custom drivers are used as of now for USB communication. Current requirement: 1. Now to make the application more generic so that it can control other USB devices apart from USB printers, the idea is to use the "Pipe handle" for data exchange instead of "Device Handle" from the Win32 DLL. Queries: 1. Can we get the handle to a pipe by some means(append the pipe name to the Symbolic link??) for communication? 2. Can we use pipeHandle straight from a Win32 Application that uses existing USB drivers shipped with Windows? 3. Does this requirement(Using PipeName for USB data exchange) need any custom driver or can this be achieved using the USB drivers that are shipped with Windows? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84647
 - 24
 - newbie@KMDF: can not build a signed catalog file for Vista 64. Hello everybody! *** Problem: WDF/KMDF: I can not build a signed catalog file (signtool.exe verify gives errors). I use already the updated signtool.exe (Version 6.0.5440.0). - signtool.exe verify gives an undocumented error - Vista says about my inf-file: "This driver is not digitally signed!" So I think to whole signing process failed *** Background: Because I worked the last years with Compuware Driver:Works, I'm quite new to the driver development process with Microsoft tools. I now have to port a driver to WDF/KMDF and try to get familiar with the driver signing process for Vista. For test of my own build environment, I want to get the WDF-ECHO-example running on Vista on a AMD64x2 machine. For build, I use WindowsXP. *** I list here all steps of my building and signing process: 1) This is how I made a test certificate: CMD>c:\WinDDK\5384\bin\selfsign\Makecert.exe -r -pe -ss PrivateCertStore -n "CN=PEAKTESTCERT" D:\PEAK\PEAKCAN3\testcert.cer ... seems OK. 2) This is how I build ECHO (copied into my own build directory): CMD>call C:\WinDDK\5384\bin\setenv.bat c:\WinDDK\5384\ CHK x86 WLH CMD>cd /d D:\PEAK\PEAKCAN3\CURRENT\ECHO CMD>build -ceZP ... seems OK. Now I have echo.sys and echo.inf. See echo.inf at the end of thsi email! 3) Now I copy the coinstaller DLL in the directory where echo.sys and echo.inf were generated: CMD>copy c:\WinDDK\5384\redist\wdf\x86\WdfCoInstaller01005.dll D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386 4) I stamp ECHO.INF: CMD>c:\WinDDK\5384\bin\x86\stampinf -f ECHO.inf -d 09/04/2006 -v 6.0.9999.0 ... seems OK 5) Now I create an catalog file, I call it "KmdfSamples.inf" I use "makecat.exe" and a *.cdf-File, see below. (This is because SIGNABILITY.EXE does not work at all ...) ----------------- BEGIN pack_sign.cdf -------------------------------- [CatalogHeader] Name=KmdfSamples ResultDir=D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386 [CatalogFiles] <HASH>wdfcoinstaller=D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\WdfCoInstaller01005.dll <HASH>inffile=D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\ECHO.inf <HASH>sysfile=D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\ECHO.sys --------------------- END pack_sign.cdf -------------------------------- CMD>c:\WinDDK\5384\bin\selfsign\makecat.exe -v D:\PEAK\PEAKCAN3\Scripts\execute\pack_sign.cdf opened: D:\PEAK\PEAKCAN3\Scripts\execute\pack_sign.cdf processing: <HASH>wdfcoinstaller processing: <HASH>inffile processing: <HASH>sysfile Succeeded 6) I try to sign my catalog file "KmdfSamples.inf" CMD>c:\WinDDK\5384\bin\selfsign\SignTool.exe sign /v /s PrivateCertStore /n PEAKTESTCERT D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.cat The following certificate was selected: Issued to: PEAKTESTCERT Issued by: PEAKTESTCERT Expires: 01.01.2040 01:59:59 SHA1 hash: 91F8CF9553ED09B76D039A17646416533D9534D0 Done Adding Additional Store Attempting to sign: D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.CAT Successfully signed: D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.CAT Number of files successfully Signed: 1 Number of warnings: 0 Number of errors: 0 ... it seems OK 7) I timestamp the catalog file CMD>c:\WinDDK\5384\bin\selfsign\SignTool.exe timestamp /v /t http://timestamp.verisign.com/scripts/timestamp.dll D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.cat Timestamping: D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.CAT Successfully timestamped: D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.CAT Number of files successfully timestamped: 1 Number of errors: 0 ... it seems OK 8) I verify the catalog file: CMD>c:\WinDDK\5384\bin\selfsign\SignTool.exe verify /v /pa D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.cat Verifying: D:\PEAK\PEAKCAN3\CURRENT\ECHO\sys\OBJCHK_WLH_x86\i386\KmdfSamples.CAT Signing Certificate Chain: Issued to: PEAKTESTCERT Issued by: PEAKTESTCERT Expires: 01.01.2040 01:59:59 SHA1 hash: 91F8CF9553ED09B76D039A17646416533D9534D0 The signature is timestamped: 04.09.2006 10:38:20 Timestamp Verified by: Issued to: Thawte Timestamping CA Issued by: Thawte Timestamping CA Expires: 01.01.2021 01:59:59 SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656 Issued to: VeriSign Time Stamping Services CA Issued by: Thawte Timestamping CA Expires: 04.12.2013 01:59:59 SHA1 hash: F46AC0C6EFBB8C6A14F55F09E2D37DF4C0DE012D Issued to: VeriSign Time Stamping Services Signer Issued by: VeriSign Time Stamping Services CA Expires: 04.12.2008 01:59:59 SHA1 hash: 817E78267300CB0FE5D631357851DB366123A690 Number of files successfully Verified: 0 Number of warnings: 0 Number of errors: 1 *** What is this error??? 9) I try to install on Vista: After I select the echo.inf, there's the message "This driver is not digitally signed!" So I think to whole signing process failed ----------------- BEGIN echo.inf ----------------------- ;/*++ ; ;Copyright (c) 1990-2000 Microsoft Corporation ; ;Module Name: ; ECHO.INF ; ;Abstract: ; INF file for installing the Driver Frameworks ECHO Driver ; ;Author: ; Ravi Gollapudi (RaviG) Oct 2002 ; ;Installation Notes: ; Using Devcon: Type "devcon install ECHO.inf root\ECHO" to install ; ;--*/ [Version] Signature="$WINDOWS NT$" Class=Sample ClassGuid={78A1C341-4539-11d3-B88D-00C04FAD5171} Provider=%MSFT% DriverVer=09/04/2006,6.0.5384.4 CatalogFile=KmdfSamples.cat [DestinationDirs] DefaultDestDir = 12 ; ================= Class section ===================== [ClassInstall32] Addreg=SampleClassReg [SampleClassReg] HKR,,,0,%ClassName% HKR,,Icon,,-5 [SourceDisksNames] 1 = %DiskId1%,,,"" [SourceDisksFiles] ECHO.sys = 1,, ;***************************************** ; ECHO Install Section ;***************************************** [Manufacturer] %StdMfg%=Standard,NTx86 ; Following section is meant for Windows 2000 as it ; cannot parse decorated model sections [Standard] ; ; Hw Id is root\ECHO ; %ECHO.DeviceDesc%=ECHO_Device, root\ECHO ; Decorated model section take precedence over undecorated ; ones on XP and later. [Standard.NTx86] %ECHO.DeviceDesc%=ECHO_Device, root\ECHO [ECHO_Device.NT] CopyFiles=Drivers_Dir [Drivers_Dir] ECHO.sys ;-------------- Service installation [ECHO_Device.NT.Services] AddService = ECHO,%SPSVCINST_ASSOCSERVICE%, ECHO_Service_Inst ; -------------- ECHO driver install sections [ECHO_Service_Inst] DisplayName = %ECHO.SVCDESC% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\ECHO.sys LoadOrderGroup = Extended Base ; ;--- ECHO_Device Coinstaller installation ------ ; [DestinationDirs] ECHO_Device_CoInstaller_CopyFiles = 11 [ECHO_Device.NT.CoInstallers] AddReg=ECHO_Device_CoInstaller_AddReg CopyFiles=ECHO_Device_CoInstaller_CopyFiles [ECHO_Device_CoInstaller_AddReg] HKR,,CoInstallers32,0x00010000, "wdfcoinstaller01005.dll,WdfCoInstaller" [ECHO_Device_CoInstaller_CopyFiles] wdfcoinstaller01005.dll [SourceDisksFiles] wdfcoinstaller01005.dll=1 ; make sure the number matches with SourceDisksNames [ECHO_Device.NT.Wdf] KmdfService = ECHO, ECHO_wdfsect [ECHO_wdfsect] KmdfLibraryVersion = 1.5 [Strings] SPSVCINST_ASSOCSERVICE= 0x00000002 MSFT = "Microsoft" StdMfg = "(Standard system devices)" DiskId1 = "WDF Sample ECHO Installation Disk #1" ECHO.DeviceDesc = "Sample WDF ECHO Driver" ECHO.SVCDESC = "Sample WDF ECHO Service" ClassName = "Sample Device" Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84642
 - 25
 - newbie question Hello all, There 2 versions of symbol package: the retail symbols and the checked symbols. What are the differences between both? What are they used for? Thanks for your answers, Jerome Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84641
- Next
 - 1
 - unirc.h Hi. I'm trying to build a minidriver using some .gpd, and .rc files. But when I typed "build -cZg", it spat out error saying that I have no unirc.h file, which was to be included in pclxl.rc file. I guess the source files I have were originally written for an older version of ddk, than mine. So I commented the unirc.h-line out and have a good looking .dll output. But I'm not sure if I did properly. My ddk is of ver. 3790.1830. When is unirc.h removed from ddk, and what should be included insteaded of unirc.h, if any? Thankx. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84640
 - 2
 - USBD_STATUS_CANCELED inconsistent definitios Hello I cannot reply to the other topic about this issue, so here's a new topic... I noticed that the 3790 DDK defines different values for USBD_STATUS_CANCELED in directory <ddk>\inc\ddk\wxp\ like this: usbdi.h: #define USBD_STATUS_CANCELED ((USBD_STATUS)0x00010000L) usb.h: #define USBD_STATUS_CANCELED ((USBD_STATUS)0xC0010000L) My WinXP SP 2 system returns USBD status 0xC0010000 in the URB when my driver cancels the IRP. I don't know about Win2K or WinVista. My driver sources seem to include the 0x00010000 usbdi.h definition. How to deal with this? I also noticed that the usbstor.sys driver masks out bits 31..28 when it checks for USBD status codes like this (I didn't check other system usb drivers): and eax, 0FFFFFFFh cmp eax, 4 <- Apparently checks for USBD_STATUS_STALL_PID This is happening in the real world. So, do we have to mask out the upper 4 bits of every USBD status code before checking it? Is there an incompatibility issue between Win2K, WinXP and WinVista regarding USBD status codes? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84639
 - 3
 - Memroy mapped files problem in minifiler level Hi, I am writing a filter driver that will encrypt/decrypt the file. The problem i am facing is when some application uses memory mapped files like MS Word or Wordpad to read the file. I cannot intercept the read call for this kind of files, no IRP_MJ_READ for this kinda files. Is there something special i have to do for this kind of memory mapped files. Thanks Lokanadham R Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84634
 - 4
 - Realted with callback interface in Windows drivers Hi All, I am currently working on a layered architecture Windows driver devlopment.My requirement is lower driver must raise a notification to upper layer driver.To do this i think IRP is one of the method... But i wanted to know is there any other way to achieve this , were in upper driver need not register through IRP but still then lower edriver can notify the uppper driver abt the event. Thanks With regards, Jagu Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84631
 - 5
 - InterlockedExchangePointer() while lock held? Is it necessary to do interlocked exchanges while any type of lock is held? The only reason I can think of is to ensure memory ordering, but I got the impression that acquiring and releasing a lock already takes care of that. There's an InterlockedExchangePointer() in a sample in the WDM driver book that accesses a field that looks like it's only ever accessed while a lock is held, and I wondered if the exchange really had to be interlocked in that case or if it was just a lazy way to avoid declaring a temporary variable and typing 3 lines of code. I'm only curious to understand the principle. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84618
 - 6
 - Simple printer driver Hi, I'm a C/C++ developer looking to create a simple printer driver that outputs data to a text file. I'm working with a proprietary database engine that only allows metadata to be exported from its print function. I would like to output the data to a text file, then use WinDiff on it. Are there any examples that show how to create a print driver like this? Thanks in advance. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84610
 - 7
 - Problem loading ndis6 light weight filter sample in WDK. Has anyone out there successfully loaded the ndis6 sample filter driver on a recent Vista build? I tried to load the sample on top of my ndis6 miniport driver on Vista 5520 by following the instructions in the code tour but the installer hung and I have to reboot. Before I spend time in debugging the problem, I want to know if there is any gotcha I should have paid attention to. Being relatively unfamiliar with Ndis IM driver, debugging this issue will be difficult since there is absolutely no os symbol for that build. Tom, Max, Stephan or other folks, have you tried that? Thanks in advance. -- Calvin Guan (DDK MVP) Sr. Staff Engineer NetXtreme NTX Miniport Broadcom Corporation Connecting Everything(r) Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84594
 - 8
 - NDIS miniport reset questions Hi everybody, I have some questions with respect to NDIS miniport reset. - In addition to Check4Hang what are the other options to notify NDIS that we are under a reset process? - What would be the impact of the reset on NDIS with respect to the following: - Will it stop transferring packets/OIDS to the miniport? - Will it notify the protocols drivers? - Is there a limit to the time we are allowed to be in reset process? - How would the protocol drivers (especially TCP/IP) behave, in that case? will they stop sending packets/OIDS to NDIS until they are told that the reset is done? Thanks Miki Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84578
 - 9
 - Need help on MSVAD's CopyFrom function Hi experts out there, I am totally new to virtual audio driver. I need to develop a virtual audio driver that can capture data that receiving from the mic of physical audio device. I was told by someone that I can do it what I want by modifying the function called "CMiniportWaveCyclicStreamMSVAD::CopyFrom( IN PVOID Destination, IN PVOID Source, IN ULONG ByteCount )" at basedma.cpp file. The question is how do I know which sound cards was I mapping to if I got two sound cards in my computers? I have tried to leave the function unmodified and record to see whether I got anything from the virtual audio driver. The result is I got a repeat random noise and I knew I should move something to the "Destination". I tried to move all the data from "Source" to "Destination" and it gave silence(all zeros) data!! I am sure I have done something seriouly not right caused I don't think my virtual audio driver didn't really connect to any "pyhsical" device. I have been tried to search for the solution everywhere I could for more than a month already. Could anyone please tell me what should I do? I have to make it works ASAP! :-( Thank in advance. aze2cool Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84576
 - 10
 - Driver memory footprint/CPU utilization Hi. I'm looking for a way to measure device driver memory footprint and CPU utilization. I did it... kinda. What I did was rather inconvinient and not presice, so I'm looking for a better way to measure there parameters. Memory: The only way to measure driver memory footprint is to measure free memory before and after the driver is loaded. So I booted into safe mode with network, measured free memory using systeminfo, loaded the driver by enabling it's device (using devcon enable) and once again measured the free memory. There are 2 problems here: 1. systeminfo give only MB resolution (can use task manager but would prefer command line tool) 2. there is huge variance between consequtive runs. probably because windows keeps doing some weird stuff in the background Any ideas ? CPU utilization: Well, I used task manager (which is kinda lame) to measure CPU utilization under traffic via my device (forgot to mension that it's wireless network device). Guess it's OK, but if there are other suggestions I would like to hear them. Thanks a lot. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84573
 - 11
 - [KMDF USB] I/O to bulk endpoints on CDC ACM data class interface Ok, so I have a new, bizarre problem that I just can't find any explanation for. I have a new device here that exports the CDC ACM configuration (interface 0 with a 'read' interrupt endpoint, and interface 1 with 'read' and 'write' bulk endpoints). I'm using WDF_USB_DEVICE_SELECT_CONFIG_PARAMS_INIT_MULTIPLE_INTERFACES with arguments 2 (interfaces) and NULL (settingPairs pointer), which doesn't error out and configParams.NumConfiguredInterfaces does show "2" after the call. To make a long story short, I can only read from the interrupt endpoint. When I issue a read or a write to either of the endpoints on the second interface, the completion routine immediately fires and errors out with 0xC000000D -- invalid parameter. I've tried varying the read size, using a continuous reader, etc. -- they all give the same result. Now, here's the crazy part: *I HAD THIS WORKING!!* I could talk to the device (read/write) easily as of Friday afternoon. I didn't touch anything, as far as I know, and it just broke. The only thing that's different is that earlier I was using a laptop on its docking station (that's where the USB port was) and now I'm using a desktop. If I use the laptop without its docking station (that's all I have right now), it still fails as well. So I guess my question is: what could cause this? What causes the USB completion routines (in general, I suppose) to return STATUS_INVALID_PARAMETER? I compared USB monitor logs with my driver versus usbser.sys. They're fairly similar, except I noticed that my log has an additional "Select Interface: Interface Number: 0x1, Alternate Setting: 0x0) in it which the usbser.sys log does not contain. By the way -- If I change the device configuration so that the bulk endpoints are all on one interface, everything works. Any ideas?? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84561
 - 12
 - Problem With NdisRegisterDeviceEx/IOCTL On Vista I'm porting an NDIS miniport driver for a WLAN device from XP to Vista. This driver supported an IOCTL interface for query/set requests from the client application. Following the mux sample driver in the WDK, the driver now calls NdisRegisterDeviceEx() to register the device. Stepping through this in WinDbg, I see the call succeed and return NDIS_STATUS_SUCCESS. However, when the client application calls CreateFile(), the call fails and GetLastError() returns 53 (ERROR_BAD_NETPATH). This was seen on Vista build 5536. Does Vista's NWF framework allow NDIS miniport drivers to export their own IOCTL interface? If not, what should NWF miniport drivers do instead? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84538
 - 13
 - Problem With NdisRegisterDeviceEx/IOCTL On Vista I'm porting an NDIS miniport driver for a WLAN device from XP to Vista. This driver supported an IOCTL interface for query/set requests from the client application. Following the mux sample driver in the WDK, the driver now calls NdisRegisterDeviceEx() to register the device. Stepping through this in WinDbg, I see the call succeed and return NDIS_STATUS_SUCCESS. However, when the client application calls CreateFile(), the call fails and GetLastError() returns 53 (ERROR_BAD_NETPATH). This was seen on Vista build Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84537
 - 14
 - IOCTL_USB_USER_REQUEST I am using a Belkin 4-Port USB 2.0 Tetra Hub in my Windows XP system. I would like to power on/off inidividual ports on this hub. I could see one option could be using "IOCTL_USB_USER_REQUEST" with "USBUSER_OP_SEND_RAW_COMMAND" request. Can anyone provide me any help on how to use IOCTL_USB_USER_REQUEST? Thanks in advance. Kallol Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84525
 - 15
 - Installing a driver as a service Hello, I was wondering if anyone knew of an easy way to install a driver? It's a driver I made and it is just a binary. I don't have any .inf files. Someone suggested earlier that you could do it as a service... When I tried his method though, I get the error message: [SC] StartService FAILED 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. The driver that I am trying to install is just a simple keyboard driver, the one that comes with the Windows DDK. It's called kbfiltr. i first created the service such as: "sc create kbfilter binpath= c:\kbfiltr.sys type= kernel" then I executed: "sc start kbfilter" no luck.. anyone know what I could do? thanks Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84515
 - 16
 - Perf Counters - Processor Queue Length Hi, We've NDIS Intermediate Driver (Filter) and it does load balancing. We've a requirement to do load balancing based on "Processor Queue Length" of System Object. Is there a way to get this value from within Intermediate Driver? I know of one way. Get the counter thru WMI program in user land and push it to Intermediate Driver. Is there any way to get this value from within driver? Like internal IOCTL? Really appreciate any help. Thanks, Best, Srini Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84504
 - 17
 - Will Longhorn Server Support SATA 1.0a? We have a legacy SATA tape drive that only supports SATA 1.0a and were wondering there will be issues. We heard that AHCI will be a requirement for Longhorn Server. Thanks! Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84500
 - 18
 - NDIS Intermediate (passthru) communicates with second driver We have two drivers. One is based on the DDK sample 'passthru', one is based on the DDK sample 'ioctl'. We want the two drivers to communicate with each other. In direction passthru to ioctl it works fine. When we try to call the passthru driver from the ioctl driver, IoCallDriver returns NtStatus 0x00000001L. In DebugView we see that the IoManager calls IRP_MJ_CREATE immediately follwed by a call to IRP_MJ_CLEANUP. The relevant sourcecode: swprintf(Name, L"\\Device\\passthru"); RtlInitUnicodeString( &stringName, Name ); status= IoGetDeviceObjectPointer( &stringName, FILE_ALL_ACCESS, &pfo, &pdo ); KeInitializeEvent(&Event, NotificationEvent, FALSE); pIrpDr= IoBuildDeviceIoControlRequest( IOCTL_INTERDRV_COMM_TEST, pdo, NULL, 0, NULL, 0, FALSE, &Event, &iostatus ); status= IoCallDriver( pdo, pIrpDr ); // >>> RETURNS 0x00000001L status= KeWaitForSingleObject( &Event, Executive, KernelMode, FALSE, &timeout ); Whats wrong with that? Is it possible to talk to passthru at all? We appreciate any help or hint. Thank you, gigefrunk Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84483
 - 19
 - BDA Device - How to expose multiple instances of a filter I am developing a driver for hardware that will have two BDA tuners/demodulators on one card. From the BDA and KS documentation it appears that if the Tuner and demodulator nodes are exposed as two seperate filters then by specifying a unique KSPIN_MEDIUM GUID it will ensure that they only connect together, and by giving each tuner/demod pair a unique KSPIN_MEDIUM ID the connections are made unique. It also seems that this allows the graph build process to establish that there are two of theses filters available. In my driver I intended to expose each tuner/demodulator pair in a single filter with two nodes. So my driver will have two filters that are identical on the two hardware channels. Therefore the input pin must connect to the service provider, and the output pin would connect to the demux (and does the actual stream capture). Is this a valid way of describing the hardware to the system? If it is, I I don't think I can specify any unique medium information to indentify the fact that there are two filters available from the hardware. In this situation how can I ensure that a user space application can build and run two graphs using the two channels available in the hardware? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84480
 - 20
 - Lower Filter Driver Questions Hello, To learn the concepts of device drivers, I created a small key logger that acted as an upper filter driver and attached to the keyboard device drivers. My next project is to expand upon my key logger and make this into a lower filter driver. I am wondering if there resources on creating a lower filter driver, or if there are any huge conceptual differences? Would it just consist of easily rewriting my previous code? Thanks Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84459
 - 21
 - [KMDF USB] Who is responsible for zero-length packet termination of bulk write? First, let me say thanks to everyone who helped with my KMDF <==> USB driver. It is working very well right now from an application standpoint. At the moment, I am trying to understand what I need to get WHQL certification as I am failing many of the 2C tests (reset, address change, etc.) I am in contact with the WHQL support alias but I am getting the impression that no one has tried to certify a driver like this yet -- so there are some questions on both sides. One question I still have: when I complete a USB write whose size is an exact multiple of the endpoint's maximum packet size (i.e. 64, 128, 192 bytes, etc.) the device is behaving as though it doesn't know the write is complete. Does KMDF (or somebody else) automatically send a zero-length packet to the USB device after completing a write of these sizes, or is there something I need to do, or perhaps a flag that needs to be set when configuring the pipe? Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84458
 - 22
 - problem with NDIS miniport driver Hi We are developing NDIS miniport driver for wireless LAN card. OS is windows XP pro SP2 Observation is, OS sends SCAN OID, then SCAN_LIST and adapter returns scanned item. but after that instead of sending valid SSID from this list in set OID_802_11_SSID, NDIS sends Junk SSID. Why does NDIS sends Junk SSID when it has retrieved valid scan list item. Are there any security parameters we need to verify? Note: we dont see same behaviour on Windows XP Pro (Without Service pack) Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84456
 - 23
 - passthru First of all I want to thank everybody who has helped me in this group. I am trying to do packet queuing for send packets in the IM driver. I take the packet that comes into the send packet function and make a linked list by point the miniport_reserved field in the NDIS structure to the next packet. Then I launch a DPC to read the linked list and send the packets. I DO NOT RETURN ANYTHING AFTER THE SendPackets function. In the Dpc , I take the linked list and start sending packets ( code from the send packet function). All this works well, but my throughput is very low 62mb on a gigabit nic. My DPC fires at 100ms. I have tried to reduce the DPC time but that has not helped. Any ideas? Thanks Prashant Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84454
 - 24
 - Windows DDK sample portio I compiled and installed the portio sample driver as well as the two applications gpdwrite and gpdread. When I write data to a port, the program appears to be successful at writing to that port. When I attempt to read the data from that port, I always get back 0xFF...regardless of what I wrote to that port. Regarding the portio sample, is there a feature that is lacking that would enable the data to actually be written to the port? Perhaps a port enable/disable feature? I am running the sample on both a windows 2000 and a windows XP system...both have the same behavior. Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84453
 - 25
 - [KMDF] Removing FDO and let PDO running Hi, I am writing a FDO for the system-enumerated system timer (PIT 8253) aka PDO (denoted *PNP0100). It works fine for now (I can use the IRQ) but the coding process is getting frustrating because I develop in a "one machine environnement" so each time I uninstall my device from the device manager, the system needs to reboot. Can KMDF remove my FDO by simply detaching it from its PDO so I can reinstall the FDO with "Update driver" in device manager or devcon ? I tried this in my EvtDriverAddDevice callback : ... status = WdfDeviceCreate( &DeviceInit, &attributes, &device ); if (!NT_SUCCESS(status)) { return status; } WdfDeviceRemoveRemovalRelationsPhysicalDevice( device, WdfFdoInitWdmGetPhysicalDevice(DeviceInit) ); ... But I get the BSOD 0x0000010d with arguments 0x00000004 0xb8xxxxxx // some address around b 0x00000000 0x85xxxxxx // some address around 8 What's wrong ? Is detaching/reataching at will even possible ? Thanks for your time. Guillaume Tag: Using WPP in kernel mode drivers that are build using VS/VS2005 Tag: 84449

Hello,

I have a kernel mode driver project and use VS2005 to build this
driver. I want to generate logs from this driver and want to use WPP
for that reason.

I am having diffuclty in defining RUN_WPP preprocessor within VS2005
build settings.

If anyone has done similar from VS2005, please part your knoweldge with
me.

Thanks
Brijesh

Top

Re: Using WPP in kernel mode drivers that are build using VS/VS2005 by Don

Don
Wed Sep 06 13:19:02 CDT 2006

Well building a driver that way is really stupid. So I would recomend you
look at ddkbuild so you can use the VS environement but use a way that is
blessed and will allow WPP tracing.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply

<mishra.brijesh@gmail.com> wrote in message
news:1157566495.685406.15550@d34g2000cwd.googlegroups.com...
> Hello,
>
> I have a kernel mode driver project and use VS2005 to build this
> driver. I want to generate logs from this driver and want to use WPP
> for that reason.
>
> I am having diffuclty in defining RUN_WPP preprocessor within VS2005
> build settings.
>
> If anyone has done similar from VS2005, please part your knoweldge with
> me.
>
> Thanks
> Brijesh
>

Top

Re: Using WPP in kernel mode drivers that are build using VS/VS2005 by Maxim

Maxim
Wed Sep 06 13:23:22 CDT 2006

VS2005 builds of the drivers are not supported. Switch to BUILD.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

<mishra.brijesh@gmail.com> wrote in message
news:1157566495.685406.15550@d34g2000cwd.googlegroups.com...
> Hello,
>
> I have a kernel mode driver project and use VS2005 to build this
> driver. I want to generate logs from this driver and want to use WPP
> for that reason.
>
> I am having diffuclty in defining RUN_WPP preprocessor within VS2005
> build settings.
>
> If anyone has done similar from VS2005, please part your knoweldge with
> me.
>
> Thanks
> Brijesh
>

Top

Re: Using WPP in kernel mode drivers that are build using VS/VS200 by HarryGraham

HarryGraham
Thu Sep 07 12:50:03 CDT 2006

"Maxim S. Shatskih" wrote:

> VS2005 builds of the drivers are not supported. Switch to BUILD.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com

You should check out DDKBUILD at hollistech.com, it makes using VS2005 for
driver builds a breeze.

Harry

Top