winddi.h

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
    - vista checked HAL/NT files download ? Any way other than being an MSDN subscriber to download VISTA checked files ( only ) ? NOT full version Tag: winddi.h Tag: 105725
  - 2
    - Selecting Best Compatible Driver (Windows XP) We have a driver package that is installed by when our software is installed. It is installed in to the Driver Store using the DriverPackagePreinstall function. The drivers are for a USB communication adapter for an industrial network. Because it is a custom driver class it canâ??t be tested by Microsoftâ?? hardware lab. All the files are digitally signed and the catalog file is signed as well. In most cases the driver install fine when the USB adapter is plugged into the system. We recently found a problem with a system that was taking 10 minutes to search for the driver. We looked at the setupapi.log file and found that the system was scanning a DVD we happened to have in the drive. The DVD happened to have a lot of files as well as 270 INF files on it. I did some research and found that only the path specified in the HKLM\Software\Microsoft\Windows\CurrentVersion DevicePath is supposed to be searched. The only path specified was %SystemRoot%\INF. Our INF file was in the Windows\INF directory and that was the INF file that was used after the search. My question is why does the DVD get searched when it isnâ??t specified in the search path? Is there a way to stop it (this doesnâ??t happen on Vista systems). Also, the setupapi.log file gives many warnings indicating that the driver isnâ??t signed when all files and the catalog file are correctly signed. Is this a bug that will be fixed or is the fact that the file is signed not detected for some reason? See part of the setupapi.log file below. Thanks, -- Brian [SetupAPI Log] OS Version = 5.1.2600 Service Pack 2 Platform ID = 2 (NT) Service Pack = 2.0 Suite = 0x0100 Product Type = 1 Architecture = x86 [2008/05/08 12:22:13 620.3 Driver Install] #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #-198 Command line processed: C:\WINDOWS\system32\services.exe #I022 Found "USB\Vid_5854&Pid_9005&Rev_0001" in C:\WINDOWS\inf\oem4.inf; Device: "Schneider Electric USB Controller"; Driver: "Schneider Electric USB Controller"; Provider: "Cyberlogic Technologies, Inc."; Mfg: "Schneider Automation, Inc."; Section name: "TSXCUSBMBP_Install". #I087 Driver node not trusted, rank changed from 0x00000000 to 0x00008000. #I023 Actual install section: [TSXCUSBMBP_Install.NT]. Rank: 0x00008000. Effective driver date: 03/28/2008. #I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1". #-147 Loading class installer module for "USB Device". #E358 An unsigned or incorrectly signed file "C:\WINDOWS\system32\MbxCi.dll" for driver "USB Device" blocked (server install). Error 0x800b0110: The certificate is not valid for the requested usage. Windows could not load the installer for MODICON_MBX. Contact your hardware vendor for assistance. Error 0x800b0110: The certificate is not valid for the requested usage. [2008/05/08 12:22:15 1596.2] #-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{65BD9C5E-9D98-4A4E-A54E-3BD028DDE1D6} #I060 Set selected driver. #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #I022 Found "USB\Vid_5854&Pid_9005&Rev_0001" in C:\WINDOWS\inf\oem4.inf; Device: "Schneider Electric USB Controller"; Driver: "Schneider Electric USB Controller"; Provider: "Cyberlogic Technologies, Inc."; Mfg: "Schneider Automation, Inc."; Section name: "TSXCUSBMBP_Install". #I087 Driver node not trusted, rank changed from 0x00000000 to 0x00008000. #I023 Actual install section: [TSXCUSBMBP_Install.NT]. Rank: 0x00008000. Effective driver date: 03/28/2008. #-147 Loading class installer module for "USB Device". #E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\MbxCi.dll" for driver "USB Device" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage. #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #I063 Selected driver installs from section [TSXCUSBMBP_Install] in "c:\windows\inf\oem4.inf". #I320 Class GUID of device remains: {01F5ED20-0BCB-11D4-A02A-00E0290C8B76}. #I060 Set selected driver. #I058 Selected best compatible driver. #I060 Set selected driver. #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #I022 Found "USB\Vid_5854&Pid_9005&Rev_0001" in C:\WINDOWS\inf\oem4.inf; Device: "Schneider Electric USB Controller"; Driver: "Schneider Electric USB Controller"; Provider: "Cyberlogic Technologies, Inc."; Mfg: "Schneider Automation, Inc."; Section name: "TSXCUSBMBP_Install". #I087 Driver node not trusted, rank changed from 0x00000000 to 0x00008000. #I023 Actual install section: [TSXCUSBMBP_Install.NT]. Rank: 0x00008000. Effective driver date: 03/28/2008. #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #-019 Searching for hardware ID(s): usb\vid_5854&pid_9005&rev_0001,usb\vid_5854&pid_9005 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff Tag: winddi.h Tag: 105724
  - 3
    - Creating a hidden local port in Vista Hi, I'm trying to create a hidden local port, similar to XPSPort: used by Microsoft's XPS Document Writer. The print driver I am working on/with creates it's own named local port upon install. This has been fine for Windows 2000 and XP, but in Vista, creating a local port has the unfortunate (and annoying) side effect of also creating a file of the same name in the user's My Documents folder. We orignally got around this by using a port name of NUL. The problem with this is multiple copies of the printer all use the same port and print jobs between the printers will block on the port name ( only one print job running per port name) and you cannot easily do parallel printing. I was able to create a local port that was "hidden" using XcvData and appending a colon (:) to the end of the port name, similar to how Microsoft has named the port associated with their XPS Document Writer. With the : on the name, the driver cannot use the port, it throws an error 123 - "The filename, directory name, or volume label syntax is incorrect." every time I print. I'm assuming that this is from the : on the port name. Is this even possible? How does Microsoft's XPS driver do this? Thanks. Geekgrrl. Tag: winddi.h Tag: 105711
  - 4
    - names of debug registers MASM - ml64.exe reports error: ".\HWBkpts.asm(66) : error A2006: undefined symbol : kdr0" on this line: mov rax, kdr0 What is right name for debug register kdr0 in MASM ? Peter Tag: winddi.h Tag: 105707
  - 5
    - Create a webcam driver and draw into it ? Hello, I would like to create a virtual webcam and to be able to draw into it, using some kind of API. I want to be able to use this virtual webcam into any software that uses it... Such things softwares like webcammax do. Is it possible ? Tag: winddi.h Tag: 105701
  - 6
    - User Mode Driver Hi What is the major difference between user mode driver and application dll , is that user mode driver call Win32 API about device and hardware ? Can user mode driver read/write IO and set DMA channel ? What is the difference between traditional user mode driver and new UMDF ? Thank for your teaching . Tag: winddi.h Tag: 105692
  - 7
    - Differentiate between Control Panel and Apllication - Printer Hi, I want to differentiate the Printer Driver UI is open from Control Panel or Apllication. Is there any API / approch to do this?. Inside the UI code, based on Printer Driver UI is opened from Control Panel or Apllication I have to write a logic. Regards, Sangeeth Tag: winddi.h Tag: 105687
  - 8
    - Where can I find the stardand IDE Contorller spec for Windows XP? Hi. If we want to design a PCI-IDE Card, we shall know the stardand IDE Host adapter spec, in order to support a generic device driver. Where can I find the stardand IDE Contorller spec for Windows XP? Does Microsoft define a rule let hardware vendors following it? -- Sincerely Yours, Tag: winddi.h Tag: 105684
  - 9
    - Does Windows XP , Windows 2000 and Vista has the same registry In my driver, i need to check the registry information in \\Registry\ \Machine\\System\\CurrentControlSet\\Control\\Class\\{4D36E96A- E325-11CE-BFC1-08002BE10318}\\0000\\settings". And i want to know does all the OS has the same position to same these information? thanks. Tag: winddi.h Tag: 105682
  - 10
    - MiniportHalt() function Hi, What sort of things would cause a miniport's Halt function ( MiniportHalt() ) to NOT get caused? I have a deserialized miniport leveraged from the DDK example netvmini. I have even gutted OUT MPHalt() just to set a breakpoint to verify the function is getting called (along with debug statements), and it is not happening. The uninstall/disable window in the Device Manager (which I am using to issue the MPHalt) hangs indefinitely. I can move the window around, but it stays in a "not responding" state. Any ideas? Should I be looking for a spin lock (doubtful due to responsive behavior of window), or is there an acknowledge which must be passed up first to NDIS, etc? I'm sort of fishing for ideas to look into. Thanks, Jan Tag: winddi.h Tag: 105676
  - 11
    - Poblem to install x64 driver from 32-bit code Hi, On WXP 64 installation of x64 driver from 32-bit utility fails with error 0x4a020 . This utility uses setupapi.lib functions and error code 0x4a020 is result of function: INetCfgClassSetup* -> Install(...) Is possible to install x64 driver from 32-bit app on Windows 64, or what do you recommend ? Peter Tag: winddi.h Tag: 105671
  - 12
    - Accessing files on FAT32 partition at boot time Is it possible to access files on a FAT32 parition during boot time from a PnP driver? ZwCreateFile() is returning STATUS_UNRECOGNIZED_VOLUME. I tried playing around with dependencies and load order, but that didn't seem to do anything. If I re-start the driver after the system has fully booted, I am able to open the file. Tag: winddi.h Tag: 105670
  - 13
    - Updated kernel symbols for Windows XP SP3 Yesterday I updated my target machine to Windows XP SP3. However, after that I found out that the kernel symbols available from Microsoft's symbol server do not match SP3 kernel components. Does anyone know when updated symbols (corresponding to Windows XP SP3) will be available on the symbol server? The sooner the better. Thanks, -Indu Tag: winddi.h Tag: 105669
  - 14
    - Where to install device drivers so that USB device finds them when it's first connected I'm creating an installer for an application. This application uses a special type of printer that we'll supply to the client as part of a package with the software. I'd like to install the USB drivers that come with the printer into a location where the printer will find them as soon as it's plugged in - i.e. the client won't have to browse to a directory to select the drivers. Is this possible - and, if so, where should I install the drivers. I guess I'm asking if there's a default USB driver search path that Windows traverses in search of a driver before it gives up and ask the user for help. Does a USB device generally know the *name* of the file it's looking for, if not the location? I'm only interested in XP and Vista. Tag: winddi.h Tag: 105665
  - 15
    - installing DLL file in system32 folder Hi, I am creating setup & deployment project for installing my application & driver for xp-32,64 & vista 32-64. By selecting Target platform as "x86", i am installing the driver for all of the above OS using DPINST DiFX tool based upon the versionNT value. Problem: For 64 bit, i want to add my dll file in system32 folder, i.eSystem(64-bit) Special folder. when i added this folder, i am getting error that above folder is not compatible to 64 bit. Yes, it is true, but any other way to install my dll file in above folder? using inf file, is this can be done? I also understand that, when my msi installer package installed in 64 bit system, it will be copied in programfiles-32 bit folder instead programfiles-64bit folder. 2) I went for above approach is that, a single installer for all OS & all platforms, is there any other way that single installer can install multiple platforms? Thanks, Kota Tag: winddi.h Tag: 105655
  - 16
    - KeWaitForSingleObject never returns please check the below code. I open the device from the application using "\\\\.\\%c:" as the input parameter to createfile. called deviceiocontrol with IOCTL_DISK_GET_DRIVE_LAYOUT ioctl I received this IOCTL in my lower file system filter driver below is the code, if ((pReceivedIrpStack->MajorFunction == IRP_MJ_DEVICE_CONTROL) && (pReceivedIrpStack->Parameters.DeviceIoControl.IoControlCode == IOCTL_DISK_GET_DRIVE_LAYOUT)) { KeInitializeEvent(&Event, NotificationEvent,FALSE); IoSkipCurrentIrpStackLocation(pReceivedIrp); status = IoCallDriver(pFilterDeviceExtension->pPartitionDeviceObject, pReceivedIrp); if (status == STATUS_PENDING) { status = KeWaitForSingleObject(&Event, Suspended, KernelMode, FALSE, NULL); status = pReceivedIrp->IoStatus.Status; } if(!NT_SUCCESS(status)) { debug statement } pReceivedIrp->IoStatus.Status = status; return(status); } problem : The status of IoCallDriver is status_pending and the KeWaitForSingleObject never returns.I am not sure why it doesnt return. can anybody help me. Thanks in advance Tag: winddi.h Tag: 105650
  - 17
    - difference between \\\\.\\%c:" & "\\\\.\\PHYSICALDRIVE%d" In application we call the creafile as follows where pVolumeInfo->Extents[0].DiskNumber is the value obtained from IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS ioctl. swprintf(pathBuff, L"\\\\.\\PHYSICALDRIVE%d", pVolumeInfo->Extents[0].DiskNumber); hDevice = CreateFile( pathBuff, GENERIC_READ|GENERIC_WRITE, FILE_SHARE_READ|FILE_SHARE_WRITE, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL); If we open the device like this the IOCTL doesnt pass thru our filter driver whereas if we open it using "\\\\.\\%c:" in place of "\\\\.\\PHYSICALDRIVE%d"as the input parameter then the IOCTL passes thru our filter driver. If I use "\\\\.\\%c:" the ioctls path is something like below(I havent mentioned all the drivers in the path below) 1.NTFS 2.our filter driver 3.volsnap 4.partmgr But if I use "\\\\.\\PHYSICALDRIVE%d" the ioctl path it shows is 1.\Device\Harddisk2\DR3 I dont see any other driver in the path. can any one explain me the difference between the two calls.I thought that both are opening the same object. I checked the IOCTLs path using IRP Tracker. Thanks in advance Tag: winddi.h Tag: 105642
  - 18
    - WLK 1.2 Print Stress Test Failure Options When use the WLK1.2 to test print driver, after or during PrintDrvStress.exe testing, Test will be failure. The snapshot can refer to http://fleet1.footbig.com/f/00/00/23/0f/m/04/12/0412c29576c708cf0155e8de242169b1-4495.jpg [Some Supplyment] OS is VISTA(sp1) or Server2008 (Both 32 and 64 bit) WLK 1.1 can PASS the testing Thanks for your answer or any support information ! Tag: winddi.h Tag: 105639
  - 19
    - Access Denied openning device in user mode I have a driver that I have installed on two different machines running XP Professional. In the first machine, logging on as power user, I can open the device. In the second, again as a power user, access is denied trying to open the device. Tag: winddi.h Tag: 105638
  - 20
    - =?Utf-8?Q?InstallHinfSection_fails_on_Vist?= Iâ??m using InstallHinfSection to install my filter driver. This works well on XP. On Vista 32 it fails with a â??Copy Errorâ?? when I use an Administrator account. InstallHinfSection obviously requires â??computer administratorâ?? access to copy the driver to the drivers directory. My MSI setup checks for Administrator access and it passes since Iâ??m an administer, however InstallHinfSection eventually fails because it doesnâ??t have the access it requires. How can I get InstallHinfSection to be successful using a standard Administrator account or how can I get the Setup to determine the user has insufficient previledges even when theyâ??re an Administrator? Thanks! Chris Harper Tag: winddi.h Tag: 105620
  - 21
    - DDK version question The MS site has the following DDK available for free download: Windows Server 2003 SP1 DDK [ 236 MB ISO file] Are the WDK6000 and 6001 versions still considered beta? I cannot even find the WDK6000 version for download... Does the 2003 SP1 DDK support Vista? Which one(s) should be used for production level drivers for XP? Which one(s) should be used for production level drivers for Vista? Thanks -decoder Tag: winddi.h Tag: 105614
  - 22
    - Enabling/Disabling NDIS 5.1 Intermediate Miniport ( 1-2 Mux) Hi, I have to to complete the development of a Mux written by a now departed consultant and which is probably 98% right. No experience or training in driver development, so I WILL use the wrong terms in phrasing my questions. This MUX is designed to be bound only to Ethernet NICs. When the NICs are bound to the MUX, all other protocols are unbound from the NICs so that after the user binds whatever protocols he chooses to the MUX, the protocols-originated packets must pass thru the MUX, possibly undergo changes, and then get forwarded to both NICs. When the MUX is Disabled thru the Network Connections, it apparently does enough to convince NDIS that it is disabled and the "Status" field reflects that. When an attempt to "Enable" the MUX, the first thing that happens is that the ProtocolReceive or ProtocolReceivePacket function gets a packet sent up from one of the bound NICs and eventually BSODs in the call to NdisMIndicateReceivePacket. My guess is that the MUX does more than what is required in response to the DISABLE command and frees up too many resources required for the ENABLE command. What does NDIS do or call in the protocol side of the MUX to disable it and what is the minimum required by the MUX to comply? What happens when an IM is Enabled? Since the packet reception is the first and last thing I see with WinDbg, I don't know what ENABLING function, if any, would eventually be called and what it should do. What's the best way to block the receipt of packets until the IM has completed the enable process? THX Wes Tag: winddi.h Tag: 105613
  - 23
    - Problem while performing StretchBlt on HP 1010, HP 1018, HP 1020 and Our application uses Windows GDI library to perform rendering and display of data/output onto the devices such as Screen and Printer. While I am trying to print the data onto a series of printers (HP 1010, HP 1018, HP 1020 and HP 3050) I am facing a typical problem. Explaination ------------------ 1. Appropriate DC for the intended device is created [Printer DC created for a selected printer in this case] 2. The data is displayed onto the identified position onto the DC The details of data (fields) to be displayed and their position onto the DC is calculated before the printing begins. If sufficient space is available for displaying/printing a field (data), then it is displayed directly onto the DC (using TextOut. However at situations, the space available for printing (displaying) a piece of data may not be enough. In such scenario, I display such information onto a temperory (display) DC and then perform StretchBlt(....) onto the printer DC. StretchBlt is capable of performing both Stretch / shrink from source DC to the destination DC. [MSDN: The StretchBlt function copies a bitmap from a source rectangle into a destination rectangle, stretching or compressing the bitmap to fit the dimensions of the destination rectangle, if necessary. The system stretches or compresses (shrinks) the bitmap according to the stretching mode currently set in the destination device context]. In this case: - Data is first displayed / outputted onto tempDC - Then StretchBlt is performed from tempDC to PrinterDC The rectangular area on the destination DC is more than source rectangular area then data is stretched If the rectangular area on the destination DC is less than source rectangular area then data is shrinked StretchBlt(...) allows us to specify the raster operation to use while performing this task as its last parameter. Here I am using SRCAND. When I use SRCAND raster operation the data is displayed in actual font size instead of shrinking. This results on loss of data (as sufficient width/height) is not available to displayed data The same operation works on several other DeskJet/LaserJet (including HP) printers. But it fails on the above mentioned set of printers. If I try to use other raster operation such as SRCCOPY, it is able to shrink the data and display properly. I can't use other operations. I have to use SRCAND (as I would like to retain any data that is already displayed within the rectangular area). I also observed that, if the destination rectangular area is more than source rectangular area: then it is able to stretch and display the data without any loss (even with SRCAND raster operation) Please let me know, if any of you have already encountered such problem and any solution Thanks & Regards, Harish Sohani Tally Solutions Pvt Ltd. Bangalore. Tag: winddi.h Tag: 105609
  - 24
    - Registry question .. Hi Does Windows Vista driver has the same driver key of hardware , class and service ? Another question should Windows service be an user mode or kernel mode driver , or it can be application or driver or others ? Thank you . Tag: winddi.h Tag: 105605
  - 25
    - USB-HID device driver Hi, I wish to develop a usb-hid device driver. I have the following questions: 1) Should it be developed using WDF or WDM? 2) I am referring to the HID standard class. Is it enough as a document to refer all the APIs that can be used for the above purpose? 3) I've downloaded the latest(as on May 06, 2008) DDK from microsoft. Does it have any example codes that mention about USB-HID device driver? Please note that I am referring the following resources: 1) USB Complete -Jan Axelson 2) Making USB Device Drivers Easier Using the HID Class -Stuart Allman 3) Device Class Def for HIDs.pdf I am particularly looking for the example code to do this. Regards, Embedded Boy Tag: winddi.h Tag: 105602
- Next
  - 1
    - Number of IRPS I am writing a virtual disk driver which uses a file as a virtual disk. The disk file can be mounted with a drive letter and normally used. Internally, ZwReadFile and ZwWriteFile in the dispatch routine for IRP_MJ_READ and IRP_MJ_WRITE do the job to write on and read from "disk". As far, everything works fine. In this ,after mounting in explorer window if i make any file copy operation,IRP_MJ_WRITE was called. Also,IRP_MJ_WRITE was called many times after i copied a single file.So my question is, How many IRPs will be sent for file copy operation.How the IRPs are formed by IO manager. How i can trace start and end of copy operation. since,in IRP_MJ_WRITE ,I am writing into a file.Also this file is shared between two driver instances. Looking forward to get reply. Thanks , ND Tag: winddi.h Tag: 105599
  - 2
    - punting back to gdi with EngTextOut not working I am trying to develope a printer driver. When I cannot handle a function I punt back to gdi. It also punts back when succesful so that the mirrorsurface is updated after each call to the driver. I've got punting working for every function except DrvTextOut. EngTextOut returns true, but nothing gets drawn to the mirror surface. According to MSDN "the driver cannot punt to EngTextOut if it has hooked DrvTextOut for a device managed surface.". I have a device managed surface, but I also have an engine managed surface that is used when calling the Eng functions. I wonder if anyone knows: 1. Can I use EngTextOut if I have a device managed surface, even if I am not calling EngTextOut with it. 2. Is there any way to get GDI to draw the text to my mirror surface. Thanks, hwilcox BOOL success = doTextOut(pstro, pfo, pco, prclExtra, prclOpaque, pboFore, pboOpaque, pptlBrushOrg, mix, substMix); if(settings->usingMirrorSurface) { SURFOBJ* mirrorSurf = EngLockSurface(hmirrorSurf); BOOL engRet = EngTextOut(mirrorSurf, pstro, pfo, pco, prclExtra, prclOpaque, pboFore, pboOpaque, pptlBrushOrg, mix); EngUnlockSurface(mirrorSurf); if(engRet && !success) { success = sendRect(&pstro->rclBkGround, pco); } } return success Tag: winddi.h Tag: 105590
  - 3
    - How make .inf file for 'mouser' sample code I read WinDDK\src\input\mouser sample code to include WDK. but this sample code is not included .inf file. If I need inf file, make the .inf file from myself? thank you. Tag: winddi.h Tag: 105588
  - 4
    - How to broadcast messages to all application in co-installer entry I'm writing a co-installer for my driver and I need to broadcast a private message to all running applications in the entry point. I use the BroadcastSystemMessage api as below: DWORD dwRecipients = BSM_APPLICATIONS | BSM_ALLDESKTOPS; BroadcastSystemMessage(BSF_POSTMESSAGE | BSF_IGNORECURRENTTASK, &dwRecipients, g_uBroadcastMsgId, 1, 0); But it seems not working in Vista. How should I do? Any help will be appreciated. Tag: winddi.h Tag: 105587
  - 5
    - Can kernel mode call Win32 API ? Hi Can kernel mode driver call Win32 API function like MessageBox and winsock ? If I want to write a virtual driver use some Win32 API and library , is it possible? Thank you . Tag: winddi.h Tag: 105586
  - 6
    - Test cases for WLAN SDIO interface Hi All, I am working in WLAN driver with SDIO interface. I have some refrence code of WLAN but i dont know how to test this WLAN through SDIO interface.I am very pretty new in this filed and mean to say , need some test plan to make some test cases for this driver interface. I will appreiciate if someone extend his arms. Thnaks Shivmangal Tag: winddi.h Tag: 105571
  - 7
    - Sharing COM1 with WinDbg I have an embedded device running XPe with a single serial port (also no 1394). The COM1 port is normally used by applications for other purposes. However, I would really like to be able to use this for kernel debugging as well. I tried using /crashdebug option in boot.ini so that the COM1 port does not disappear. The problem is that this does not let me debug on demand, only when a bug check occurs. Is there a way to enable on demand debugging without reserving the serial port for exclusive use by the debugger? If not, the other option would be to have WinDbg monitor for specific debug messages coming from the other machine. My understanding is that this used to be possible with a .waitforstr command, but that doesn't seem to be implemented any more. Is there a way to monitor messages from within WinDbg? Thanks! Tag: winddi.h Tag: 105566
  - 8
    - IoCallDriver Bugcheck Hi, I observed a strange behavior with Intelx64 PCs with my virtual COM driver. When I pass an irp to lower driver (using IoCallDriver()) i get an Assertion Failure - code c0000420 exception and when i forcefully continue it i get a bugcheck. I get this exception when i pass the IRP with one of the vendor specific commands. Also, this exception is not happening frequently. It happens for every 3 out of 5 times. I have used an application to test the sequence. By the way this failure is not happening in either Intel x86, AMD x64 or AMD x86 bit machines. In all the PCs i have installed Vista 32-bit OS. I did not see anything pointing in my driver, but i strongly believe that some thing is going wrong in my driver. I have pasted the bugcheck code and wdflog below. Can someone help me find the bug where im going wrong? Here is the bugcheck code: *** Fatal System Error: 0x0000008e (0xC0000420,0x81828671,0x9EF97A3C,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows Vista 6000 x86 compatible target, ptr64 FALSE Loading Kernel Symbols ............................................................................................................................... Loading User Symbols ........................................................................................ Loading unloaded module list ........Unable to enumerate user-mode unloaded modules, Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 8E, {c0000420, 81828671, 9ef97a3c, 0} Probably caused by : kdcom.dll ( kdcom!KdCompPollByte+14 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 818818d0 cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000420, The exception code that was not handled Arg2: 81828671, The address that the exception occurred at Arg3: 9ef97a3c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000420 - <Unable to get error code text> FAULTING_IP: nt!KeUpdateRunTime+248 81828671 cd2c int 2Ch TRAP_FRAME: 9ef97a3c -- (.trap 0xffffffff9ef97a3c) ErrCode = 00000000 eax=763b38b9 ebx=00000000 ecx=818f622c edx=0000009b esi=818f4820 edi=8bd343f0 eip=81828671 esp=9ef97ab0 ebp=9ef97ac8 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202 nt!KeUpdateRunTime+0x248: 81828671 cd2c int 2Ch Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: svchost.exe CURRENT_IRQL: 1c LAST_CONTROL_TRANSFER: from 818d87f7 to 818818d0 STACK_TEXT: 9ef971dc 818d87f7 00000003 9ef9c96c 00000000 nt! RtlpBreakWithStatusInstruction 9ef9722c 818d9264 00000003 9ef97a3c 00000000 nt!KiBugCheckDebugBreak +0x1c 9ef975d8 818d8681 0000008e c0000420 81828671 nt!KeBugCheck2+0x5f4 9ef975fc 8182335e 0000008e c0000420 81828671 nt!KeBugCheckEx+0x1e 9ef979cc 8188d66a 9ef979e8 00000000 9ef97a3c nt!KiDispatchException +0x1a9 9ef97a34 8188d606 9ef97ac8 81828673 badb0d00 nt!CommonDispatchException +0x4a 9ef97a48 804c79ac 804c8020 9ef97a8b 00000000 nt!KiExceptionExit+0x16e 9ef97ac8 818906ad 83347e02 000000d1 9ef97b58 kdcom!KdCompPollByte+0x14 9ef97ac8 81ba4dc0 83347e02 000000d1 9ef97b58 nt!KeUpdateSystemTime +0xed 9ef97b48 806d8533 83347e10 83347eec 9ef97b6c hal! KeAcquireSpinLockRaiseToSynch+0x20 9ef97b58 806e0f8c 9ef97b68 8070cf30 83347eec Wdf01000! FxCallbackSpinLock::Lock+0x7f 9ef97b6c 806e3d13 7ccb81e8 7cf8db90 00000001 Wdf01000! FxIoQueueIoRead::Invoke+0x1e 9ef97b94 806e6598 7cf8db90 83072468 83347e10 Wdf01000! FxIoQueue::DispatchRequestToDriver+0x1dc 9ef97bb0 806e7d2c 83347e00 8070d188 83347e10 Wdf01000! FxIoQueue::DispatchEvents+0x485 9ef97bcc 806e8e67 00000000 83112f40 82f27b58 Wdf01000! FxIoQueue::QueueRequest+0x237 9ef97bf0 806d7d9a 8bd3a920 9ef97c14 81827f83 Wdf01000!FxPkgIo::Dispatch +0x377 9ef97bfc 81827f83 82f27b58 8bd3a920 8bd3a920 Wdf01000! FxDevice::Dispatch+0x7f 9ef97c14 8a42d581 831af0e8 83112e88 831af030 nt!IofCallDriver+0x63 9ef97c28 81827f83 83112e88 00d3a920 82f23030 serenum! Serenum_DispatchPassThrough+0x65 9ef97c40 86338027 9ef97c60 81827f83 82f23030 nt!IofCallDriver+0x63 9ef97c48 81827f83 82f23030 8bd3a920 8bd3a920 RootMdm! RootModemPassThrough+0x21 9ef97c60 892bcb1a 8bd410e8 831af030 00000000 nt!IofCallDriver+0x63 9ef97c74 81827f83 8bd3aab0 8bd3a920 8bd3a920 modem!UniRead+0x4a 9ef97c8c 81988f37 8bd3a920 8bd3aab0 8bd410e8 nt!IofCallDriver+0x63 9ef97cac 81993669 831af030 8bd410e8 00000001 nt! IopSynchronousServiceTail+0x1e0 9ef97d38 8188caaa 831af030 8bd3a920 779ed684 nt!NtReadFile+0x646 9ef97d38 77c30f34 831af030 8bd3a920 779ed684 nt!KiFastCallEntry+0x12a 02e3f1cc 77c30080 779ed71d 00000194 00000000 ntdll!KiFastSystemCallRet 02e3f1d0 779ed71d 00000194 00000000 779ed684 ntdll!ZwReadFile+0xc 02e3f210 6ef09ddf 00000194 03176de4 00000001 kernel32!ReadFileEx+0x72 02e3f698 6ef227ba 00000000 00000000 00780830 unimdmat! ReadCompletionHandler+0x7ca 02e3f6ac 77a06c6d 00780830 02e3a40e 02e3f718 uniplat! AsyncProcessingHandler+0x15 02e3f704 77c30dfd 6ef227a5 00780830 00000000 kernel32!BaseDispatchAPC +0x50 02e3fa5c 6ef22934 000006bc ffffffff 00000001 ntdll!KiUserApcDispatcher +0x25 02e3fa70 77a23833 6ef24020 02e3fabc 77c0a9bd uniplat!UmWorkerThread +0x15 02e3fa7c 77c0a9bd 6ef24020 02e37e4f 00000000 kernel32! BaseThreadInitThunk+0xe 02e3fabc 00000000 6ef2291f 6ef24020 00000000 ntdll!_RtlUserThreadStart +0x23 STACK_COMMAND: kb FOLLOWUP_IP: kdcom!KdCompPollByte+14 804c79ac 0fb7c0 movzx eax,ax SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: kdcom!KdCompPollByte+14 FOLLOWUP_NAME: MachineOwner MODULE_NAME: kdcom IMAGE_NAME: kdcom.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4549bd7c FAILURE_BUCKET_ID: 0x8E_kdcom!KdCompPollByte+14 BUCKET_ID: 0x8E_kdcom!KdCompPollByte+14 Followup: MachineOwner --------- I also captured the WDFLOG as mentioned in http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx. Here is the wdflog. But i could not find any useful information in it. 0: kd> !load C:\Program Files\Debugging Tools for Windows (x86)\winext \wdfkd.dll 0: kd> !D:\WINDDK\6000\bin\x86\wdfkd.wdftmffile D:\WINDDK\6000\tools \tracing\i386\wdf01005.tmf Set TMF file name is : 'D:\WINDDK\6000\tools\tracing \i386\wdf01005.tmf' 0: kd> !D:\WINDDK\6000\bin\x86\wdfkd.wdflogdump usbcom Trace searchpath is: Trace format prefix is: %7!u!: %!FUNC! - TMF file used for formatting IFR log is: D:\WINDDK\6000\tools\tracing \i386\wdf01005.tmf Log at 83343000 Gather log: Please wait, this may take a moment (reading 4032 bytes). % read so far ... 10, 20, 30, 40, 50, 60, 70, 80, 90, 100 There are 106 log entries --- start of log --- 274: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 275: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 276: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 277: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 278: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 279: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 280: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 281: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 282: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 283: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 284: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 285: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 286: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 287: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 288: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 289: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 290: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 291: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 292: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 293: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 294: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 295: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 296: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 297: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 298: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 299: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 300: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 301: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 302: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 303: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 304: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 305: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 306: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 307: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 308: FxFileObject::GetFileObjectFromWdm - The PFILE_OBJECT 0x8BD460D0 in this request (cleanup/close) is different from the one specified in create request 0x833D3700.This is bad! 309: FxFileObject::GetFileObjectFromWdm - Since this is a serial port device, framework is using a workaround to allow this 310: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD2DFE8 requests cancelled 311: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD2DFE8 312: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 313: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 314: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 315: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 316: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD2DFE8 requests cancelled 317: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD2DFE8 318: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 319: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 320: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 321: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 322: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 323: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleStartTimer from FxIdleDecrementIo 324: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleTimerRunning from FxIdleStartTimer 325: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning 326: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer 327: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleCheckIoCount 328: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD2DFE8 requests cancelled 329: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD2DFE8 330: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 331: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 332: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 333: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 334: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 335: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 336: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 337: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 338: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 339: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 340: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 341: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 342: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 343: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 344: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 345: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 346: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 347: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 348: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 349: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 350: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 351: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 352: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 353: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 354: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 355: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 356: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 357: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 358: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 359: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 360: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 361: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 362: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 363: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 364: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 365: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 366: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 367: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 368: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 369: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 370: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 371: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 372: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 373: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 374: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 375: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 376: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 377: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 378: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 379: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo ---- end of log ---- Thanks and Regards, Sushma Tag: winddi.h Tag: 105563
  - 9
    - IRP Tracker I see many entries in Device Selection Menu. In that \Driver\Disk is a entry which gives the entries for all the disk in the system. My doubt is,say for a disk I see entries and I notice that a particular IOCTL IOCTL_DISK_GET_DRIVE_LAYOUT reaches only \Device\Harddisk2\DR3 in my case. what is that DR3 ,what does that mean. what are all the other entries like \Device\Harddisk2\DP(2)0X8004400 - 0XC800000+7 \Device\Harddisk2\DP(1)0X4400 - 0X8000000 + 6 can anybody explain what entry is that. why that particular IOCTL reaches \Device\Harddisk2\DR3 from the application eventhough I have filter drivers between. Thanks in advance. Hope I havent confused Tag: winddi.h Tag: 105562
  - 10
    - Porting WDM to WDF Hello All, I am porting a USB WDM driver to WDF. I have some vendor specific commands thats needs to submitted to lower device. I get a bugcheck 0x7E at WdfIoTargetSendInternalIoctlSynchronously(). Can some one help me if im going wrong anywhere in the below code. Here are the WDM and WDF code snippets. WDM -------- NTSTATUS SubmitUSB() { usUrbSize = (USHORT)sizeof(struct _URB_CONTROL_VENDOR_OR_CLASS_REQUEST); pUrb = (PURB)ExAllocatePoolWithTag(NonPagedPool, usUrbSize, 'BSUD'); if (pUrb == NULL) { DbgPrint(1, ("ExAllocatePool Failed.. No Memory\n")); return STATUS_NO_MEMORY; } UsbBuildVendorRequest(pUrb, URB_FUNCTION_VENDOR_DEVICE, usUrbSize, USBD_TRANSFER_DIRECTION_IN | USBD_SHORT_TRANSFER_OK, 0, ucRequest, usValue, usIndex, pBuffer, NULL, ulTransferLen, NULL); KeWaitForSingleObject( &KeSyncSubmitUrb, Executive, KernelMode, FALSE, NULL ); KeInitializeEvent(&kEvent, NotificationEvent, FALSE); // Build an IRP pIrp = IoBuildDeviceIoControlRequest(IOCTL_INTERNAL_USB_SUBMIT_URB, pdoNext, NULL, 0, NULL, 0, TRUE, &kEvent, &ioStatus); if (pIrp == NULL) { DbgPrint(1, ("IoBuildDeviceIoControlRequest() failed!\n")); status = STATUS_INSUFFICIENT_RESOURCES; } else { PIO_STACK_LOCATION pStack = IoGetNextIrpStackLocation(pIrp); pStack->Parameters.Others.Argument1 = pUrb; IoSetCancelRoutine(pIrp, NULL); // Call the USBD status = IoCallDriver(pdoNext, pIrp); if (status == STATUS_PENDING) { LARGE_INTEGER TimeOut = { (ULONG)(-10000 * 1000), -1 }; while ( status != STATUS_SUCCESS ) { // Wait for completion status = KeWaitForSingleObject(&kEvent, Executive, KernelMode, FALSE, &TimeOut); if ( status != STATUS_SUCCESS ) { DbgPrint(1, ("KeWaitForSingleObject failed\n"); if ( status == STATUS_TIMEOUT ) { IoCancelIrp( pIrp ); } } } status = ioStatus.Status; } } KeSetEvent( &KeSyncSubmitUrb, 0, FALSE ); } WDF Equivalent ----------------------- NTSTATUS SubmitURB() { PURB pUrb = NULL; WDFMEMORY urbMemory; WDF_OBJECT_ATTRIBUTES objectAttribs; WDF_MEMORY_DESCRIPTOR memoryDesc; usUrbSize = (USHORT)sizeof(struct _URB_CONTROL_VENDOR_OR_CLASS_REQUEST); WDF_OBJECT_ATTRIBUTES_INIT(&objectAttribs); objectAttribs.ParentObject = Device; status = WdfMemoryCreate( &objectAttribs, NonPagedPool, POOL_TAG, usUrbSize, &urbMemory, (PVOID*) &pUrb); if (!NT_SUCCESS(status)) { DbgPrint(1, ("Failed to alloc mem for urb\n")); status = STATUS_INSUFFICIENT_RESOURCES; return status; } UsbBuildVendorRequest(pUrb, URB_FUNCTION_VENDOR_DEVICE, usUrbSize, USBD_TRANSFER_DIRECTION_IN | USBD_SHORT_TRANSFER_OK, 0, ucRequest, usValue, usIndex, pBuffer, NULL, ulTransferLen, NULL); WDF_MEMORY_DESCRIPTOR_INIT_HANDLE(&memoryDesc, urbMemory, (USHORT)sizeof(URB)); status = WdfIoTargetSendInternalIoctlSynchronously(WdfDeviceGetIoTarget(Device), NULL, IOCTL_INTERNAL_USB_SUBMIT_URB, &memoryDesc, NULL, NULL, NULL); if (!NT_SUCCESS(status)) { DbgPrint(1, ("WdfIoTargetSendInternalIoctlSynchronously Failed with error 0x%x\n",status)); return status; } } Thank You. Regards, uba Tag: winddi.h Tag: 105561
  - 11
    - IOCTL_DISK_GET_DRIVE_LAYOUT doubt I have a lower filter driver(sits below file system driver) From the application I pass IOCTL_DISK_GET_DRIVE_LAYOUT ioctl. I get error as my partition style is GPT. I am not supporting GPT Partition style for now in my driver.so I wanted to log the error in system logs from the driver if it is GPT. But when I tried to log it I see that the particularIOCTL never reaches my driver. Is it possible that file system driver can return error for this IOCTL. I tried checking with irp tracker .when I select my driver and see for the occurence of the particular IOCTL I am not seeing the IOCTL. when I select the corresponding GPT disk in select disk menu I see the IOCTL that is required. Is it that the IOCTL is returned back with error code by file system driver before even my filter receives it. I also see that the error code is INVALID_DEVICE_REQUEST in IRP Tracker. I believed that disk.sys is responsible for the above IOCTL.so I expected my that IOCTL_DISK_GET_DRIVE_LAYOUT should reach my driver.But I am not sure whether my driver receives the IOCTL. Can anybody help on this. does file system driver have any specific check in it. Tag: winddi.h Tag: 105560
  - 12
    - about URB_FUNCTION_SELECT_INTERFACE I want to change interface setting, and the code as below: PURB urb; USBD_CONFIGURATION_HANDLE hConfig; PUSB_CONFIGURATION_DESCRIPTOR pcd; USBD_INTERFACE_LIST_ENTRY interfaces[4]; PUSB_INTERFACE_DESCRIPTOR pid; PURB pUrbSelIntf = NULL; ... urb = USBD_CreateConfigurationRequestEx(pcd, interfaces); status = SendUrb (Adapter, selurb); hconfig = selurb->UrbSelectConfiguration.ConfigurationHandle; .. pUrbSelIntf = (PURB)ExAllocatePool(NonPagedPool, GET_SELECT_INTERFACE_REQUEST_SIZE(pid->bNumEndpoints)); UsbBuildSelectInterfaceRequest(pUrbSelIntf, GET_SELECT_INTERFACE_REQUEST_SIZE(pid->bNumEndpoints), hconfig, 0, 1); status = SendUrb (Adapter, pUrbSelIntf); but when I submit the pUrbSelIntf, OS bring blue screen. why? How can I do this? Tks! Tag: winddi.h Tag: 105559
  - 13
    - How can I send file or data from WinCE to PC by USB connection ? Hi How can I send file or data from WinCE to PC by USB connection ? Can Activesync service or other way do that , is there any document or sample code ? Thank you . Tag: winddi.h Tag: 105558
  - 14
    - IRQL of HwStorAdapterControl Hi, What is the IRQL HwStorAdapterControl is called at? Thank you, Andrew Tag: winddi.h Tag: 105557
  - 15
    - USB on Windows XP: Composite Devices and Selective Suspend Hi, I have a requirement to Selectively Suspend a Composite Device on Windows XP Does anyone know if the Common Class Generic Parent driver (usbccgp.sys) supports Selective Suspend under Windows XP? Is there a minimum SP (i.e. SP2 or SP3) needed to support this? TIA Pete Tag: winddi.h Tag: 105556
  - 16
    - How to unlock system protected file ? Hi I found serial.sys has been locked by system , so I cannot replace it by my sample code built serial.sys . Is there any way to unlock some built-in generic driver in Windows XP and Vista ? Thank you . Tag: winddi.h Tag: 105555
  - 17
    - about function COM_IOControl in Virtual COM driver hello,everybody! I'm try to create a virtual COM driver. when i applying the function COM_IOControl: DWORD COM_IOControl(DWORD hOpenContext,DWORD dwCode,PBYTE pBufIn,DWORD dwLenIn,PBYTE pBufOut,DWORD dwLenOut,PDWORD pdwActualOut) i've received some values of dwCode parameter,like 0x1B0050 1769552 0x1B0054 1769556 0x1B003C 1769532 0x1B0048 1769544 0x1B0028 1769512 0x1B0044 1769540 but i don't know what these mean. Can you help me ? Thanks! Tag: winddi.h Tag: 105554
  - 18
    - Collate value in Bitmap virtual Printer Driver I am developing a Bitmap virtual printer driver based on Microsoft Universal Printer Driver(Unidrv) Problem is inside driver i am not getting the value of "dmCollate" member of "DEVMODE" I read in MSDN they specify This member is ignored unless the printer driver indicates support for collation by setting the dmFields member to DM_COLLATE. also try after set dmFields to DM_COLLATE but then also i am not getting the value of dmCollate. I tried using PDEVMODEW pDevMode; pDevMode = (PDEVMODEW)pDevObj->pPublicDM; pDevMode->dmFields = DM_COLLATE; But i am not getting the value of "pDevMode->dmCollate" If any one have idea on this topic then please help me. Thanks in advance Tag: winddi.h Tag: 105553
  - 19
    - USB packet ? Hi Does USB has negociate protocol , is there any tool to monitor USB packets ? Where can I find the reference documents ? Thank you . Tag: winddi.h Tag: 105552
  - 20
    - correct forum for Setup & Deployment & driver installation? Hi, Which is the right forum to ask question related to below types? 1) Setup & Deployment 2) Driver installation & uninstallation using DIFx DPINST tools Thanks, Kota Tag: winddi.h Tag: 105544
  - 21
    - Prevent loading of SCSIAdapter in Safe Mode Hi, Is there any way to prevent my driver from being loaded in safe mode? In my INF, I have Class=SCSIAdapter. Thank you, Andrew Tag: winddi.h Tag: 105541
  - 22
    - Filter driver question Hi Can Vista use filter driver , any framework change ? Does MSDN Library tell us much about filter driver ? I have question about ComPort Inf section of msports.inf [ComPort.NT.HW] AddReg=ComPort.NT.HW.AddReg [ComPort.NT.HW.AddReg] HKR,,"UpperFilters",0x00010000,"serenum" What does Inf HW section use for, and where will it create registry key ? Thank you . Tag: winddi.h Tag: 105537
  - 23
    - Visual studio project files for devcon Somebody asked for it, so here it is... Visual Studio 2008 ex. project for the WDK sample program devcon (KB311272). http://w16.easy-share.com/1700307651.html Make a copy of devcon source directory and extract the zip there; the solution file is in vcproj subdir. Enjoy. --PA Tag: winddi.h Tag: 105535
  - 24
    - IoAllocateMdl Failure- returns NULL 30% in Vista64 but not in othe Hi, I observed that IoAllocateMdl is returning NULL around 30% of the times in Vista64 but not that much in other OS. I am allocating the MDL memory for 16MB. System is AMD 64-bit 2GB RAM and for other OS also, i tested in the same PC. Do i have modify any settings in vista64-PC to increase the success rate of IoAllocateMdl? I have read in an article, when system loads heavily & runs lack of system pages, it happens, but i tried with SystemPages 0 to not limit of the pages allocation in regedit, but the response is same. Thanks, Kota. Tag: winddi.h Tag: 105523
  - 25
    - PC Restart required after driver unload and before installing agai Hi, I am working on a WDF PCI device driver, driver supports PNP functionality. Problem: when driver uninstalled, i had to restart the system in xp-32 & xp-64 before driver installing again, where as this is not required in vista-32 bit pc. Driver installation: I am currently using DIFX tools DpInst for installing & uninstalling the driver. I also verified that my driver unmaps the resources before uninstalling the driver using MmUnmapIoSpace to unmap the PCI memory resources. Device doesnt support power managment capability, so driver also not supporting any power managment functionality, instead it just registers the callback & wont do anything inside. Since this problem is existing only in xp, do i have to take any extra care to avoid system restart? and also, after uninstall system doesnt prompt for restart also. Thanks, Prafulla Tag: winddi.h Tag: 105522

I am trying to build a dll which requires winddi.h. I'm guessing that it's
included with WDK CD. After I have installed the build environment, I still
can't find winddi.h needed for my build. I have tried to find it on google
and tried that winddi.h, although I have no luck either. Does the Plaform SDK
need to be installed before I can make use of winddi.h?

Top

Re: winddi.h by Pavel

Pavel
Thu May 08 18:20:29 CDT 2008

"ssylee" <ssylee@discussions.microsoft.com> wrote in message
news:0E5959C8-2750-4501-A960-AE162905F3CA@microsoft.com...
> I am trying to build a dll which requires winddi.h. I'm guessing that it's
> included with WDK CD. After I have installed the build environment, I
> still
> can't find winddi.h needed for my build. I have tried to find it on google
> and tried that winddi.h, although I have no luck either. Does the Plaform
> SDK
> need to be installed before I can make use of winddi.h?

Search again. Winddi.h is in <wdk root>\inc\api

--PA

Top

Re: winddi.h by Tim

Tim
Fri May 09 22:48:41 CDT 2008

ssylee <ssylee@discussions.microsoft.com> wrote:
>
>I am trying to build a dll which requires winddi.h. I'm guessing that it's
>included with WDK CD. After I have installed the build environment, I still
>can't find winddi.h needed for my build. I have tried to find it on google
>and tried that winddi.h, although I have no luck either. Does the Plaform SDK
>need to be installed before I can make use of winddi.h?

What does the DLL do? Winddi.h is the main include file for building
display drivers.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

Top