Windows VISTA Driver Development Kit.

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 IRP_MN_QUERY_POWER Hi all, if I faile a IRP_MN_QUERY_POWER request (device or system) by completing the IRP with STATUS_UNSUCCESSFUL I expect that the system does not enter the requested sleep state. This was true for Windows 2000/XP. On Vista this error code is ignored and the system enters S3 or S4 without any request or warning. Is this a bug or a new system behavior? The bahavior is different than discribed in the WDK documentation. Thanks Guenter Tag: Windows VISTA Driver Development Kit. Tag: 90023
 - 2
 - strange problem in windows xp I am using ECP parallel port in xp .And using port access device driver to acccess parllel port extended rigsetres directly . I am reading ECP fifo in polled mode programm works well on win98 full time it aslso worls on xp but stops after some working 5 or 10 miutes I am unable to resolve problem .When i restarts program again it begin to work pleas help me in this regard. Tag: Windows VISTA Driver Development Kit. Tag: 90022
 - 3
 - Bluetooth HID Currently the Wii Remote is a very hot topic because it works as a HID Bluetooth device. Unfortunately it does not work completely with the HID API and the Windows Bluetooth stack. I use my HID test programs developed for USB devices and with some of them it is possible to BSOD the XP Bluetooth stack. This is probably the uppermost HID driver not checking the parameters. I have seen that problem with an older Logitech mouse driver. I do not own a Wii Remote yet so i do not know much yet. Where do i get information about the problems of the Bluetooth stack? Tag: Windows VISTA Driver Development Kit. Tag: 90021
 - 4
 - Can not map the video memory into mapped file in mirror driver The problem have been resolved by doing as follow: 1. Delete the source code in DrvCreateDeviceBitmap, and just return NULL. 2. Delete the source code in DrvDeleteDeviceBitmap, and do nothing in it. 3. For other Drv* functions, call appropriate Eng* functions and return their value. For example, in DrvText Out, it will just call EngTextOut and return its value. Now the new problem is: 1. If the mirror driver's width/height/bitcount are different from primary driver's, it will still got black image. -- jarvisbao ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: Windows VISTA Driver Development Kit. Tag: 90013
 - 5
 - NDIS 5.0 in Vista ? Hi Experts: I have a question on NDIS version usable under Windows Vista: We have been using an NDIS miniport driver writing using NDIS 5.0. Will this work under Windows Vista? If not, what should I do to make it work in Vista with minimum change? For example, should I port the driver code to NDIS 5.1 (which is supported by Vista as I read from the web)? If I port the code to NDIS 6.0, will the driver still work under older Windows platforms like Windows 2000 and XP? Thanks for your advises ! Polaris Tag: Windows VISTA Driver Development Kit. Tag: 90007
 - 6
 - OID_GEN_SUPPORTED_GUID Query Failure I am querying a NDIS miniport driver for OID_GEN_SUPPORTED_GUID and it returns status 0xC00000BB (STATUS_NOT_SUPPORTED). The driver supports this OID. I see that the query function is not being called in my NDIS driver. Is there any reason why this OID could be blocked/not passed on to the NDIS miniport driver by any other IM/protocol driver? I tried quering using RawEther and WinPCAP with the same result. Thanks, ..Ram Tag: Windows VISTA Driver Development Kit. Tag: 90006
 - 7
 - DDK sample bug reporting What's the proper way to report a potential bug in a DDK sample? Tag: Windows VISTA Driver Development Kit. Tag: 90005
 - 8
 - iostream Hi, I'm using the winddk (6000) to not only develop a WDF driver, but also a console app that tests out my driver (using IOCTLs). When I include <iostream> in the console app, the ddk compiler can't find it. I did find it in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and "new" constructs, but I can't seem to include <iostream> for stl::cout and the like. Here is my sources file for the app ============================================================== TARGETNAME=rmgr TARGETTYPE=PROGRAM UMTYPE=console UMENTRY=main USE_MSVCRT=1 !if defined(DDKBUILDENV) C_DEFINES = $(C_DEFINES) -DDDKBUILD=1 !endif TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \ $(SDK_LIB_PATH)\user32.lib \ INCLUDES=$(INCLUDES);$(DDK_INC_PATH); SOURCES= \ rmgr.cpp RUN_WPP= $(SOURCES) #-func:printf(MSG,...) ========================================================= thanks in advance for help, cm Tag: Windows VISTA Driver Development Kit. Tag: 89988
 - 9
 - DIFx 2.1: Vista 64-bit signed driver install problem (CM_PROB_DRIVER_FAILED_LOAD) Hi! Windows Vista 64-bit build 6000: I´ve got a signed 64-bit driver package for a PCI device. A pure .inf installation works without any problems. The device will be installed properly. But the device installation fails using DIFx 2.1 on a clean system (device has not been installed before). I´ve created a MSI installer using the DIFxAPP 2.1 merge module. The MSI installation log file reports no DIFx error message but the setupapi.dev.log file reports: !!! dvi: Device not started: Device has problem: 0x27: CM_PROB_DRIVER_FAILED_LOAD. And Vista prompts with a "Program Compatibility Assistant - Windows requires a digitally signed driver" dialog. The MSI installation works only if the device has been installed through a pure .inf installation before at least. Looks like that the .cat file will not be copied into the CatRoot directory?!? I will check that out. And I will try the same scenario using DPInst.exe instead of the MSI installer, but I assume that will produce the same problem. Maybe I am doing something wrong. I hope that anyone of the DIFx team can help. Thanks! -Nick Tag: Windows VISTA Driver Development Kit. Tag: 89972
 - 10
 - NDIS6 - state machine and USB questions Hi everyone, 1. I am writing an NDIS6 virtual miniport driver and I am confused by the miniport and NDIS behaviour when I am disabling the device (through device manager). What happens is that Ndis calls MiniportPause, than it calls MiniportRestart and after that it calls MiniportPause again and finally it calls MiniportHalt. This confuses me since from what I understood from the state machine documented at WDK the sequence should be: a call to MiniportPause followed by a call to MiniportHalt - no call to MiniportRestart in the middle Is the sequence I see in my miniport indicates a problem on it or is it the normal sequence when disabling a device? 2. In the future I would like to turn the mninipot into NDIS + KMDF driver using USB. I would like to use the ContiniousReader mechanism. In NdisEdge sample it is written shortly about how to convert the sample to a USB but it is very general. So I looked at the WDK and at the osrusbfx2 sample and I saw that when using it on a KMDF driver one should do some actions on the following KMDF callbacks: EvtDeviceD0Entry (MiniportRestart ?) EvtDeviceD0Exit (MiniportPause ?) EvtDevicePrepareHardware (MiniportInitializeEx ?) EvtDeviceReleaseHardware (MiniportHaltEx ?) Writing an NDIS+KMDF miniport I don't have these callbacks what are the NDIS callbacks that complies to the these KMDF callbacks (I wrote my assumptions in parenthesis) ? Thanks Miki Tag: Windows VISTA Driver Development Kit. Tag: 89965
 - 11
 - How to find LowerDeviceObject in DDK MSVAD Audio Sample?? I use MSVAD to develop my own usb audio stream driver. When I want to CallUSBD, I must have LowerDeviceObject to pass down the IRP. How to find the LowerDeviceObject?? Tag: Windows VISTA Driver Development Kit. Tag: 89955
 - 12
 - [AVStream]: Device is not connected Hi all, I can use GraphEdit to build a graph for my video capture driver filter - an AVStream minidriver. And VMR grants the connection between pins. But when I "Run" the graph, an error message appears: "Device is not connected. Return code: 0x8007048f". In fact, if the real device is connected, the filter will not be inserted into the graph. It's strange! Does anyone meet this problem before? Thanks for your help Tag: Windows VISTA Driver Development Kit. Tag: 89950
 - 13
 - SetupDiRemoveDevice questions? Hi, I want to remove 10 SATA disk running in AHCI mode without rebooting. At the moment I eject each disk with SetupDiRemoveDevice one by one. It takes about 3 seconds for each disk, for 10 disk about 30 seconds. Everything is working fine. If I eject each disk in its own thread, all 10 disks still needs 30 seconds to eject. It seems its not possible to eject more than one disk simultaneously. Is there a solution to eject all the disk at the same time? Many thanks in advance, Chris Tag: Windows VISTA Driver Development Kit. Tag: 89949
 - 14
 - Can not map the video memory into mapped file in mirror driver Note: I copied the sample from Microsoft DDK and just added few code to map the video memory to a file. -- jarvisbao ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: Windows VISTA Driver Development Kit. Tag: 89946
 - 15
 - Can not map the video memory into mapped file in mirror driver I am writing a mirror driver to share the video memory with user-mode applications, here is my idea: 1. In DrvEnablePDEV, create a mapped file (such as c:\mirror.dat) for video memory by function EngMapFile, and store the mapped memory in the point pVideoMemory of PPDEV. The map will be unmapped and the file will be deleted in DrvDisablePDEV 2. In DrvEnableSurface, modify the surface with EngModifySurface. The source code for DrvEnableSurface looks like: HSURF DrvEnableSurface( DHPDEV dhpdev) { PPDEV ppdev; HSURF hsurf; SIZEL sizl; ULONG ulBitmapType; FLONG flHooks; ULONG mirrorsize; MIRRSURF *mirrsurf; DHSURF dhsurf; LONG lDelta=0; // Create engine bitmap around frame buffer. ppdev = (PPDEV) dhpdev; DISPDBG((0,"DISP DrvEnableSurface:(%d,%d,%d)\n",ppdev->cxScreen,ppdev->cyScreen,ppdev->ulBitCount)); ppdev->ptlOrg.x = 0; ppdev->ptlOrg.y = 0; sizl.cx = ppdev->cxScreen; sizl.cy = ppdev->cyScreen; if (ppdev->ulBitCount == 16) { ulBitmapType = BMF_16BPP; flHooks = HOOKS_BMF16BPP; lDelta = ALIGNEDWIDTH(2 * sizl.cx); } else if (ppdev->ulBitCount == 24) { ulBitmapType = BMF_24BPP; flHooks = HOOKS_BMF24BPP; lDelta = ALIGNEDWIDTH(3 * sizl.cx); } else if(ppdev->ulBitCount==32) { ulBitmapType = BMF_32BPP; flHooks = HOOKS_BMF32BPP; lDelta = ALIGNEDWIDTH(4 * sizl.cx); } else return FALSE; flHooks |= flGlobalHooks; mirrorsize = (ULONG)(sizeof(MIRRSURF) + lDelta * sizl.cy); DISPDBG((0,"DISP DrvEnableSurface: MirrorSize:%d,lDelta:%d,pVideoMemory:%lx",mirrorsize,lDelta, ppdev->pVideoMemory)); mirrsurf = (MIRRSURF *) EngAllocMem(FL_ZERO_MEMORY, mirrorsize, 0x4D495252); if (!mirrsurf) { RIP("DISP DrvEnableSurface failed EngAllocMem\n"); return(FALSE); } dhsurf = (DHSURF) mirrsurf; hsurf = EngCreateDeviceSurface(dhsurf, sizl, ulBitmapType); if (hsurf == (HSURF) 0) { DISPDBG((0,"DISP DrvEnableSurface failed EngCreateDeviceSurface\n")); return(FALSE); } if (!EngAssociateSurface(hsurf, ppdev->hdevEng, flHooks)) { DISPDBG((0,"DISP DrvEnableSurface failed EngAssociateSurface\n")); EngDeleteSurface(hsurf); return(FALSE); } if(!EngModifySurface(hsurf, ppdev->hdevEng, flHooks, 0, (DHSURF)dhsurf, ppdev->pVideoMemory, lDelta, NULL)) { DISPDBG((0,"DISP DrvEnableSurface failed EngModifySurface\n")); EngDeleteSurface(hsurf); return(FALSE); } ppdev->hsurfEng = (HSURF) hsurf; ppdev->pvTmpBuffer = (PVOID) dhsurf; mirrsurf->cx = ppdev->cxScreen; mirrsurf->cy = ppdev->cyScreen; mirrsurf->lDelta = ppdev->lDeltaScreen; mirrsurf->ulBitCount = ppdev->ulBitCount; mirrsurf->bIsScreen = TRUE; return(hsurf); } The mapped file will always be filled with Zero, so the image from the mapped file will be black. Can any one tell me what's wrong with the source code? Thanks in advance Jarvis Bao -- jarvisbao ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: Windows VISTA Driver Development Kit. Tag: 89945
 - 16
 - unable to open Tdi Connection Context on Windows Vista Hi All, Here I have a problem with TDI in Windows Vista, In My TDI Client Driver , Code to open the Transport Address executed successfully in Vista. But I am facing a problem while opening a TdiConnectionContext File object on Vista. I am creating a UNICODE_STRING data structure from a unicode string L"\\Device\\Tcp" and then creating an OBJECT_ATTRIBUTES data structure TdiDriverNameAttributes from a UNICODE_STRING. Then I initialize the Extended Attributes data structure members as follows. RtlCopyMemory(&ExtendedAttributesInformation->EaName, TdiConnectionContext, TDI_CONNECTION_CONTEXT_LENGTH); ExtendedAttributesInformation->EaNameLength = (sizeof (TdiConnectionContext) - 1) ExtendedAttributesInformation->EaValueLength = (sizeof (TdiConnectionContext) - 1). My call to ZwCreateFile completes with STATUS_INVALID_PARAMETER. ZwCreateFile(&hConnection, FILE_READ_EA | FILE_WRITE_EA, &TdiDriverNameAttributes, &IoStatusBlock, NULL, FILE_ATTRIBUTE_NORMAL, 0, FILE_OPEN_IF, 0, ExtendedAttributesInformation, EASize ); May I know the reason for failure? The same code is working fine on 2K & XP OS. Only on vista I came across this behavior. Thanks. Tag: Windows VISTA Driver Development Kit. Tag: 89944
 - 17
 - setup class/interface class GUID dilemma Our old WDM driver uses the same GUID for its setup class and for its interface class. I have written a new WDF driver and am in a quandary over what to do about the GUIDs. Our application requires that the interface class GUID remain the same. That implies that I should change the setup class GUID. If I do, do I need to change the ClassName too? What will happen when users update from the old driver to the new driver if the drivers have a different setup class GUID and ClassName? Tag: Windows VISTA Driver Development Kit. Tag: 89943
 - 18
 - Passing down IOCTLs I'm trying to figure out how IOCTLs make it all the way down to a PDO if they need to (for example through a disk class FDO down to a disk PDO, although I'm not sure there are other examples). For the subset of IOCTLs not supported by a generic FDO, is it conventional to use IoSkipCurrentIrpStackLocation and IoCallDriver in the dispatch routines for IRP_MJ_DEVICE_CONTROL and IRP_MJ_INTERNAL_DEVICE_CONTROL? I figure if the PDO doesn't recognize the requests it will just fail them anyway. The "DispatchDeviceControl in Higher-Level Drivers" section of the DDK docs seem to imply copying the current stack location to the next and installing a completion routine, but I don't see why this would be necessary if the FDO doesn't support the IOCTL and therefore doesn't need to do any post-processing on it. IoSkipCurrentIrpStackLocation seems more appropriate in that case. Tag: Windows VISTA Driver Development Kit. Tag: 89927
 - 19
 - Kmdf I have the old WDK (no wdf is included). Is it already too late to download the KMDF's release >= 1.1 separately ? It seems that the KMDF1.5 only comes with the latest WDK. Tag: Windows VISTA Driver Development Kit. Tag: 89923
 - 20
 - CreateFile faiedl with correct SymbolicLink Hi, dears! I added call to IoRegisterDeviceInterface() in AddDevice() for keyboard filter driver and it returned successfully with correct SymbolicLink ( checked in the registry ) like \\?\ACPI#PNP0303#4&4b018eb&0#{b4ee1d31-cbf8-400d-8d63-f99c500dbe76} but fail in HANDLE h = CreateFile(SymbolicLink, GENERIC_READ|GENERIC_WRITE, FILE_SHARE_READ|FILE_SHARE_WRITE, NULL,OPEN_EXISTING,NULL,NULL); for that ( I change '?' to '.' and so forth without success ) with error 2 ( ERROR_FILE_NOT_FOUND ). Is possible to open keyboard filter driver at all and send custom IOCTLs ? TIA Arkady Tag: Windows VISTA Driver Development Kit. Tag: 89922
 - 21
 - String to GUID in C++ only This seems to exist in .Net but I would like to do it in C++ only (no MFC, .net, ATL...) Do you have any snippet of code doing this ? GUID StringToGUID(const String myGuidAsAString) { //??? } Any help would be much appreciated, Mathieu LEMAIRE Tag: Windows VISTA Driver Development Kit. Tag: 89917
 - 22
 - netvmini DHCP off, setting IP statically Hi everbody, Does anybody know if it is possible to change netvmini sample driver from DDK so that DHCP is off when installing the driver? If that is possible how can I set the IP statically? If is not possible, can I set DHCP off for my driver from a user application? How? I have looked IpHelpApi but Tag: Windows VISTA Driver Development Kit. Tag: 89915
 - 23
 - Ndis Driver problem hello, i am writting a network driver,and facing problem in ICMP resolve. can anybody tell me how to form a proper packet in receive path.? it is a miniport - ndis driver. first i am creating a packet, NdisAllocateBuffer(); NdisAllocatePacket(); I copied the ICMP packet of 98 bytes,, then set the status of the packet to NDIS_SET_PACKET_STATUS( packet,,_SUCCESS) then attached the packet at front, and then send it to upper layer ,,, NdisMIndicateReceive(); Am i missing something? if yes then tell me how to resolve it,? thanks,, from Hitesh Tag: Windows VISTA Driver Development Kit. Tag: 89910
 - 24
 - Ndis Driver problem hello, i am writting a network driver,and facing problem in ICMP resolve. can anybody tell me how to form a proper packet in receive path.? it is a miniport - ndis driver. first i am creating a packet, NdisAllocateBuffer(); NdisAllocatePacket(); I copied the ICMP packet of 98 bytes,, then set the status of the packet to NDIS_SET_PACKET_STATUS( packet,,_SUCCESS) then attached the packet at front, and then send it to upper layer ,,, NdisMIndicateReceive(); Am i missing something? if yes then tell me how to resolve it,? thanks,, from Hitesh Tag: Windows VISTA Driver Development Kit. Tag: 89909
 - 25
 - How to find LowerDeviceObject in DDK MSVAD Audio Sample?? I use MSVAD to develop my own usb audio stream driver. When I want to CallUSBD, I must have LowerDeviceObject to pass down the IRP. How to find the LowerDeviceObject?? -- duoman ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: Windows VISTA Driver Development Kit. Tag: 89907
- Next
 - 1
 - ieee1394 driver resume blue screen Hello I am using a driver for IEEE1394 DCAM-compliant cameras (sources can be downloaded from here http://www.cs.cmu.edu/~iwan/1394/downloads/index.html) When hibernating with this driver loaded, I get a blue screen at resume, with a NO_MORE_IRP_STACK_LOCATIONS message and a stop code of 0x00000035 The power management part of the driver is taken from the ieee1394 samples from the DDK, but apparently there is more to be done to make it work... Does anyone has an idea of how to solve this ? Or at least is there a way to prevent system hibernation if this driver is loaded ? Thanks in advance Nicolas Tag: Windows VISTA Driver Development Kit. Tag: 89906
 - 2
 - WINDOWS VISTA, WINDOWS XP ( X64 ) PRO CORP SP2, OFFICE 2007, PROJECT 2007, PUBLISHER 2007, HACKING LESSONS 1-17, other 2006/December/20 new programs WINDOWS VISTA, WINDOWS XP ( X64 ) PRO CORP SP2, OFFICE 2007, PROJECT 2007, PUBLISHER 2007, HACKING LESSONS 1-17, other 2006/December/20 new programs ------------------------------------------------------------------------ PC new programs 2006-Dec-17 Nr=5262 MICROSOFT VISUAL STUDIO 2005 TEAM EDITION FOR DATABASE PROFESSIONALS (DEVELOPERS KIT) 1DVD Nr=5260 MICROSOFT OUTLOOK 2007 (E-MAIL CLIENT) Nr=5258 MICROSOFT VISUAL STUDIO 2005 TEAM TEST LOAD AGENT (TEST) Nr=5257 MICROSOFT EXPRESSION WEB 2007 Nr=5256 MS PRESS MICROSOFT SQL SERVER 2005 ADMINISTRATORS COMPANION (BOOKWARE) PC new programs Nr=5251 MICROSOFT OFFICE ACCOUNTING PROFESSIONAL 2007 (ACCOUNTING) Nr=5249 MICROSOFT HOST INTEGRATION SERVER 2006 (BUSINESS) Nr=5244 MS PRESS MICROSOFT SQL SERVER 2005 ADMINISTRATORS COMPANION (BOOKWARE) Nr=5239 M.O.D.L.2273BL DISTANCE LEARNING MANAGING AND MAINTAINING A MICROSOFT WINDOWS SERVER 2003 ENVIRONMENT 1DVD Nr=5231 MICROSOFT WINDOWS XP PROFESSIONAL CORPORATE SP2 INTEGRATED NOVEMBER 2006 MULTI IMAGE (OPERATING SYSTEM) Nr=5230 MICROSOFT WINDOWS XP X64 PROFESSIONAL CORPORATE SP2 RC INTEGRATED MULTI IMAGE (OPERATING SYSTEM) Nr=5235 MICROSOFT WINDOWS VISTA ENTERPRISE 32BIT VLM (OPERATING SYSTEM) 1DVD Nr=5198 MICROSOFT WINDOWS VISTA FINAL (OPERATING SYSTEM) 1DVD Nr=5197 MICROSOFT WINDOWS VISTA DRIVER KIT RTM (DEVELOPMENT KIT) 1DVD Nr=5227 MICROSOFT OFFICE 2007 ENTERPRISE UG VL (OFFICE-SOLUTION) 1DVD Access 2007 Enterprise 2007 Excel 2007 Groove 2007 InfoPath 2007 OneNote 2007 Outlook 2007 PowerPoint 2007 Professional Plus 2007 Project Professional 2007 Project Standard 2007 Publisher 2007 SharePoint Designer 2007 Standard 2007 Visio Professional 2007 Visio Standard 2007 Word 2007 Nr=5225 MICROSOFT PROJECT PROFESSIONAL & STANDARD EDITION 2007 (PROJECT MANAGEMENT) Nr=5224 MICROSOFT PUBLISHER 2007 (D.T.P) Nr=5223 MICROSOFT SHAREPOINT DESIGNER 2007 Nr=5222 MICROSOFT VISIO PROFESSIONAL & STANDARD EDITION 2007 (BUSINESS TOOLS) =============================================================== please send e-mail astra35@freemail.gr, loa210@mail.gr, loa210@mailbox.gr Tag: Windows VISTA Driver Development Kit. Tag: 89899
 - 3
 - Emulate USB Modem device Hi, We have a requirement to emulate a USB modem device in order to test PDA functionality which is a host. I assume we would need to emulate a communication class device. We also need to send data back to host based on packets received from host. This would include call setup AT command responses and data packets after the connection is established. Does anybody know if this possible? Thanks, Jim Tag: Windows VISTA Driver Development Kit. Tag: 89890
 - 4
 - BSOD BAD_POOL_HEADER Hi, I am writing a usb bus driver (wdm driver) , once I install my driver I am getting blue screens at very random times, sometime in the middle of transactions and sometime even after my driver got unloaded. But all the BSODs shows the same bug check code (0x19). I have installed the driver in Windows XP sp2. Any suggestions will be appreciated. Thanks. =============================================================== BugCheck 19, {20, fb286cd0, fb286ce0, a0202e0} Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+2c1 ) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: 81bf3100 Nonpaged pool DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from 805360bf to 804e2a52 STACK_TEXT: aa7bb79c 805360bf 00000003 aa7bbaf8 00000000 nt!RtlpBreakWithStatusInstruction aa7bb7e8 80536b96 00000003 813c2214 81bf3100 nt!KiBugCheckDebugBreak+0x19 aa7bbbc8 805371aa 00000019 00000020 81bf3100 nt!KeBugCheck2+0x574 aa7bbbe8 80550fc5 00000019 00000020 81bf3100 nt!KeBugCheckEx+0x1b aa7bbc38 8058c38c 81bf3108 00000000 00000000 nt!ExFreePoolWithTag+0x2c1 aa7bbc6c 8056c78f 813c2020 00000000 813c2008 nt!PspProcessDelete+0x7a aa7bbc88 804e1957 813c2020 00000000 813c208c nt!ObpRemoveObjectRoutine+0xdf aa7bbca0 80573b43 00000000 8140fa68 aa7bbccc nt!ObfDereferenceObject+0x4c aa7bbcb0 8056c78f 813c2020 00000000 8140fa68 nt!PspThreadDelete+0xd2 aa7bbccc 804e1957 8140fa80 00000000 000000d4 nt!ObpRemoveObjectRoutine+0xdf aa7bbce4 8056ea9e fd235ba0 e230a310 fd235580 nt!ObfDereferenceObject+0x4c aa7bbcfc 8056e9bc e230a310 8140fa80 000000d4 nt!ObpCloseHandleTableEntry+0x155 aa7bbd44 8056ea06 000000d4 00000001 00000000 nt!ObpCloseHandle+0x87 aa7bbd58 804dd99f 000000d4 0012f80c 7c90eb94 nt!NtClose+0x1d aa7bbd58 7c90eb94 000000d4 0012f80c 7c90eb94 nt!KiFastCallEntry+0xfc 0012f7fc 7c90d592 7c809bbb 000000d4 0012fb44 ntdll!KiFastSystemCallRet 0012f800 7c809bbb 000000d4 0012fb44 0041385d ntdll!ZwClose+0xc 0012f80c 0041385d 000000d4 004115a5 00143d78 kernel32!CloseHandle+0x51 Tag: Windows VISTA Driver Development Kit. Tag: 89886
 - 5
 - Remove locks IRP-by-IRP Okay, despite earlier doubts I suppose I can believe the file-based IRPs cannot be concurrent with IRP_MN_REMOVE_DEVICE, but I still have questions about the earliest OS version where this applies and about exactly which IRPs are file-based. Assuming Windows 2000 or later, here's what I interpret for every IRP major code, but I have questions about some cases, and some are not even documented (just found in the .h file so maybe don't matter?) IRP_MJ_CREATE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_READ - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_WRITE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_DEVICE_CONTROL - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_INTERNAL_DEVICE_CONTROL (IRP_MJ_SCSI) - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_FLUSH_BUFFERS - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_CLEANUP - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_CLOSE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_QUERY_INFORMATION - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_SET_INFORMATION - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_PNP IRP_MN_CANCEL_REMOVE_DEVICE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MN_CANCEL_STOP_DEVICE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MN_QUERY_REMOVE_DEVICE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MN_QUERY_STOP_DEVICE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MN_START_DEVICE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MN_STOP_DEVICE - cannot be concurrent with IRP_MN_REMOVE_DEVICE IRP_MN_SURPRISE_REMOVAL - cannot be concurrent with IRP_MN_REMOVE_DEVICE <other IRP_MJ_PNP minor IRPs> - can be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_SYSTEM_CONTROL - can be concurrent with IRP_MN_REMOVE_DEVICE, but IoWMIRegistrationControl(..., WMIREG_ACTION_DEREGISTER) can be used in place of a remove lock IRP_MJ_POWER - can be concurrent with IRP_MN_REMOVE_DEVICE IRP_MJ_SHUTDOWN - ? IRP_MJ_CREATE_NAMED_PIPE - ? IRP_MJ_QUERY_EA - ? IRP_MJ_SET_EA - ? IRP_MJ_QUERY_VOLUME_INFORMATION - ? IRP_MJ_SET_VOLUME_INFORMATION - ? IRP_MJ_DIRECTORY_CONTROL - ? IRP_MJ_FILE_SYSTEM_CONTROL - ? IRP_MJ_LOCK_CONTROL - ? IRP_MJ_CREATE_MAILSLOT - ? IRP_MJ_QUERY_SECURITY - ? IRP_MJ_SET_SECURITY - ? IRP_MJ_DEVICE_CHANGE - ? IRP_MJ_QUERY_QUOTA - ? IRP_MJ_SET_QUOTA - ? Are any cases different in Windows 98 or Me? Tag: Windows VISTA Driver Development Kit. Tag: 89883
 - 6
 - MiniSpy source? I have downloaded the WDK 6000 from MSDN (I have a premium account) and cannot find the source MiniSpy. I'm looking for the source code to some sample MiniFilter driver. I have never developed a file system filter (either legacy or with the File System Manager archecture) and experience has taught me to find sample code before leaping into something new. Anyone know why this sample code appears to be missing? Know where I can get it? Is there better/newer MiniFilter source available? Anyone? Anyone? Bueller?? Bueller?? Tag: Windows VISTA Driver Development Kit. Tag: 89882
 - 7
 - What does "arp entry addition failed: 5" mean? I see the following mesg for the error of above type: Error Message: The ARP entry addition failed: parameter User Action: Check the command-line format for the Address Resolution Protocol (ARP) command. When adding an entry to the table, the Internet Protocol (IP) address must be entered in a dotted decimal format; the associated media access control (MAC) address must be entered in a 6-digit hexadecimal format with digits separated by hyphens. But in my case, I get this error only sometimes for the same syntax and arguments and for the same card and not always. The command I use: arp -s <remote IP> <remote mac> Looks like device/driver bindings got screwed up or something. If I disable my device and then reenable, the exact same command works. The above text on microsoft site does not provide any useful information on what the value "5" in error mesg means? Does anyone have info on what this error no means? Regds, Tag: Windows VISTA Driver Development Kit. Tag: 89879
 - 8
 - Which is the first NDIS routine registered by miniport with NDIS that needs to be called when network device is disabled? This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C72391.85217160 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Which is the first NDIS routine registered by miniport with NDIS that = needs to be called when network device is disabled? When I try to disable the ethernet device, the device manager hangs and = device disable never seems to get disabled. I see lots of incoming traffic and packets getting indicated from my = driver to NDIS. \windows\inf\setuapi.app.log has the log enclosed below. Wondering why disable is not going through.. Looking at my device = context I dont have any pendings sends to be completed. Neither is my pause routine getting called. Nor is Ndis close routine = getting called. Any what the problem could be? Regds, >>> [DIF_PROPERTYCHANGE - = {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&00] >>> Section start 2006/12/19 00:28:50.234 cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc dvi: Using exported function 'NetClassInstaller' in module = 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer =3D=3D NetCfgx.dll,NetClassInstaller dvi: Using exported function 'NciDeviceInstall' in module = 'C:\Windows\system32\nci.dll'. dvi: CoInstaller 1 =3D=3D nci.dll,NciDeviceInstall dvi: Using exported function 'WlanDeviceClassCoInstaller' in module = 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 2 =3D=3D wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'FDCoInstaller' in module = 'C:\Windows\system32\fdco1ins.dll'. dvi: CoInstaller 3 =3D=3D fdco1ins.dll,FDCoInstaller dvi: CoInstaller 1: Enter 00:28:50.265 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 00:28:50.281 dvi: CoInstaller 2: Exit dvi: CoInstaller 3: Enter 00:28:50.281 dvi: CoInstaller 3: Exit dvi: Class installer: Enter 00:28:50.281 dvi: Class installer: Exit dvi: Default installer: Enter 00:28:50.281 dvi: {Change State} dvi: Device Instance =3D = '{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&00'. dvi: {DICS_DISABLE, DICS_FLAG_GLOBAL} dvi: Using exported function 'NetClassInstaller' in = module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer =3D=3D NetCfgx.dll,NetClassInstaller dvi: Using exported function 'NciDeviceInstall' in module = 'C:\Windows\system32\nci.dll'. dvi: CoInstaller 1 =3D=3D nci.dll,NciDeviceInstall dvi: Using exported function 'WlanDeviceClassCoInstaller' = in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 2 =3D=3D = wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'FDCoInstaller' in module = 'C:\Windows\system32\fdco1ins.dll'. dvi: CoInstaller 3 =3D=3D fdco1ins.dll,FDCoInstaller dvi: CoInstaller 1: Enter 13:34:36.234 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 13:34:36.234 dvi: CoInstaller 2: Exit dvi: CoInstaller 3: Enter 13:34:36.234 dvi: CoInstaller 3: Exit dvi: Class installer: Enter 13:34:36.234 dvi: Class installer: Exit dvi: Default installer: Enter 13:34:36.234 dvi: {Change State} dvi: Device Instance =3D = '{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&00'. dvi: {DICS_DISABLE, DICS_FLAG_GLOBAL} dvi: Using exported function = 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer =3D=3D = NetCfgx.dll,NetClassInstaller dvi: Using exported function 'NciDeviceInstall' = in module 'C:\Windows\system32\nci.dll'. dvi: CoInstaller 1 =3D=3D = nci.dll,NciDeviceInstall dvi: Using exported function = 'WlanDeviceClassCoInstaller' in module = 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 2 =3D=3D = wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'FDCoInstaller' in = module 'C:\Windows\system32\fdco1ins.dll'. dvi: CoInstaller 3 =3D=3D = fdco1ins.dll,FDCoInstaller dvi: CoInstaller 1: Enter 14:00:13.609 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 14:00:13.625 dvi: CoInstaller 2: Exit dvi: CoInstaller 3: Enter 14:00:13.625 dvi: CoInstaller 3: Exit dvi: Class installer: Enter 14:00:13.625 dvi: Class installer: Exit dvi: Default installer: Enter 14:00:13.625 dvi: {Change State} dvi: Device Instance =3D = '{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&00'. dvi: {DICS_DISABLE, DICS_FLAG_GLOBAL} <ins> >>> [DIF_PROPERTYCHANGE - = {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&00] >>> Section start 2006/12/19 13:34:36.187 cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc <ins> >>> [DIF_PROPERTYCHANGE - = {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&00] >>> Section start 2006/12/19 14:00:13.578 cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc <ins> ------=_NextPart_000_0026_01C72391.85217160 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.3020" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV> Which is the first NDIS routine registered by = miniport with=20 NDIS that needs to be called when network device is disabled? When I try to disable the ethernet device, the = device=20 manager hangs and device disable never seems to get disabled.  I see lots of incoming traffic and packets = getting=20 indicated from my driver to NDIS. \windows\inf\setuapi.app.log has the log enclosed=20 below. Wondering why disable is not going through.. = Looking at my=20 device context I dont have any pendings sends to be = completed.  Neither is my pause routine getting called. = Nor is=20 Ndis close routine getting called. Any what the problem could = be?   Regds,   >>>  [DIF_PROPERTYCHANGE -=20 {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&= amp;00] >>> =20 Section start 2006/12/19 00:28:50.234       = cmd:=20 "C:\Windows\system32\mmc.exe"=20 C:\Windows\system32\devmgmt.msc      dvi: Using = exported=20 function 'NetClassInstaller' in module=20 'C:\Windows\system32\NetCfgx.dll'.      dvi: = Class=20 installer =3D=3D = NetCfgx.dll,NetClassInstaller      dvi:=20 Using exported function 'NciDeviceInstall' in module=20 'C:\Windows\system32\nci.dll'.      dvi: = CoInstaller 1 =3D=3D=20 nci.dll,NciDeviceInstall      dvi: Using exported = function 'WlanDeviceClassCoInstaller' in module=20 'C:\Windows\system32\wlaninst.dll'.      dvi: = CoInstaller=20 2 =3D=3D = wlaninst.dll,WlanDeviceClassCoInstaller      dvi: = Using exported function 'FDCoInstaller' in module=20 'C:\Windows\system32\fdco1ins.dll'.      dvi: = CoInstaller=20 3 =3D=3D fdco1ins.dll,FDCoInstaller      dvi: = CoInstaller 1:=20 Enter 00:28:50.265      dvi: CoInstaller 1:=20 Exit      dvi: CoInstaller 2: Enter=20 00:28:50.281      dvi: CoInstaller 2:=20 Exit      dvi: CoInstaller 3: Enter=20 00:28:50.281      dvi: CoInstaller 3:=20 Exit      dvi: Class installer: Enter=20 00:28:50.281      dvi: Class installer:=20 Exit      dvi: Default installer: Enter=20 00:28:50.281      = dvi:     =20 {Change State}     =20 dvi:           Device = Instance=20 =3D=20 '{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0= &00'.     =20 dvi:           = {DICS_DISABLE,=20 DICS_FLAG_GLOBAL}     =20 dvi:           Using = exported=20 function 'NetClassInstaller' in module=20 'C:\Windows\system32\NetCfgx.dll'.     =20 dvi:           Class = installer=20 =3D=3D NetCfgx.dll,NetClassInstaller     =20 dvi:           Using = exported=20 function 'NciDeviceInstall' in module=20 'C:\Windows\system32\nci.dll'.     =20 dvi:           = CoInstaller 1=20 =3D=3D nci.dll,NciDeviceInstall     =20 dvi:           Using = exported=20 function 'WlanDeviceClassCoInstaller' in module=20 'C:\Windows\system32\wlaninst.dll'.     =20 dvi:           = CoInstaller 2=20 =3D=3D = wlaninst.dll,WlanDeviceClassCoInstaller     =20 dvi:           Using = exported=20 function 'FDCoInstaller' in module=20 'C:\Windows\system32\fdco1ins.dll'.     =20 dvi:           = CoInstaller 3=20 =3D=3D fdco1ins.dll,FDCoInstaller     =20 dvi:           = CoInstaller 1:=20 Enter 13:34:36.234     =20 dvi:           = CoInstaller 1:=20 Exit     =20 dvi:           = CoInstaller 2:=20 Enter 13:34:36.234     =20 dvi:           = CoInstaller 2:=20 Exit     =20 dvi:           = CoInstaller 3:=20 Enter 13:34:36.234     =20 dvi:           = CoInstaller 3:=20 Exit     =20 dvi:           Class=20 installer: Enter 13:34:36.234     =20 dvi:           Class=20 installer: Exit     =20 dvi:           Default = installer: Enter 13:34:36.234     =20 dvi:           &nb= sp;   =20 {Change State}     =20 dvi:           &nb= sp;        =20 Device Instance =3D=20 '{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0= &00'.     =20 dvi:           &nb= sp;        =20 {DICS_DISABLE, DICS_FLAG_GLOBAL}     =20 dvi:           &nb= sp;        =20 Using exported function 'NetClassInstaller' in module=20 'C:\Windows\system32\NetCfgx.dll'.     =20 dvi:           &nb= sp;        =20 Class installer =3D=3D = NetCfgx.dll,NetClassInstaller     =20 dvi:           &nb= sp;        =20 Using exported function 'NciDeviceInstall' in module=20 'C:\Windows\system32\nci.dll'.     =20 dvi:           &nb= sp;        =20 CoInstaller 1 =3D=3D = nci.dll,NciDeviceInstall     =20 dvi:           &nb= sp;        =20 Using exported function 'WlanDeviceClassCoInstaller' in module=20 'C:\Windows\system32\wlaninst.dll'.     =20 dvi:           &nb= sp;        =20 CoInstaller 2 =3D=3D=20 wlaninst.dll,WlanDeviceClassCoInstaller     =20 dvi:           &nb= sp;        =20 Using exported function 'FDCoInstaller' in module=20 'C:\Windows\system32\fdco1ins.dll'.     =20 dvi:           &nb= sp;        =20 CoInstaller 3 =3D=3D = fdco1ins.dll,FDCoInstaller     =20 dvi:           &nb= sp;        =20 CoInstaller 1: Enter 14:00:13.609     =20 dvi:           &nb= sp;        =20 CoInstaller 1: Exit     =20 dvi:           &nb= sp;        =20 CoInstaller 2: Enter 14:00:13.625     =20 dvi:           &nb= sp;        =20 CoInstaller 2: Exit     =20 dvi:           &nb= sp;        =20 CoInstaller 3: Enter 14:00:13.625     =20 dvi:           &nb= sp;        =20 CoInstaller 3: Exit     =20 dvi:           &nb= sp;        =20 Class installer: Enter 14:00:13.625     =20 dvi:           &nb= sp;        =20 Class installer: Exit     =20 dvi:           &nb= sp;        =20 Default installer: Enter 14:00:13.625     =20 dvi:           &nb= sp;           &nbs= p; =20 {Change State}     =20 dvi:           &nb= sp;           &nbs= p;      =20 Device Instance =3D=20 '{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0= &00'.     =20 dvi:           &nb= sp;           &nbs= p;      =20 {DICS_DISABLE, DICS_FLAG_GLOBAL} <ins> >>>  [DIF_PROPERTYCHANGE -=20 {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&= amp;00] >>> =20 Section start 2006/12/19 13:34:36.187       = cmd:=20 "C:\Windows\system32\mmc.exe" = C:\Windows\system32\devmgmt.msc <ins> >>>  [DIF_PROPERTYCHANGE -=20 {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0373\4&55C493A&0&= amp;00] >>> =20 Section start 2006/12/19 14:00:13.578       = cmd:=20 "C:\Windows\system32\mmc.exe"=20 C:\Windows\system32\devmgmt.msc <ins></DIV></BODY></H= TML> ------=_NextPart_000_0026_01C72391.85217160-- Tag: Windows VISTA Driver Development Kit. Tag: 89873
 - 9
 - APCs Dear all, Do all APCs run at APC_LEVEL Irql? For example, user APCs that start at ntdll!KiUserDispatchApc. I always thought that they did but !pcr is reporting an IRQL of 0. Many thanks, Carl Tag: Windows VISTA Driver Development Kit. Tag: 89872
 - 10
 - Using i.MX21 with a monochrome display Hello, I'm using i.MX21 on the ADS eval board from freescale. I try to drive a monochrome display. The BSP is delivered to support a sharp display and I've modified initialisation code for LCD in OAL but as soon as I configure the monochrome mode (clear TFT and COLOR bits of LPCR register) the FLM and LP signal are stopped ? any clue, any experience in this domain ... If you have already a configuration that works for a monochrome display it could help. Any advises are welcome thanks in advance Nyrbyk Tag: Windows VISTA Driver Development Kit. Tag: 89864
 - 11
 - USB device descriptor I'm not an expert of device drivers programming on Windows so I hope my question is not stupid for you. What I'm trying to do is reading the USB descriptor of an USB hard disk (or an USB key) in order to read the product id and the serial number of the device. The problem is that I can't even read the USB descritpor. The code is this: USB_DEVICE_DESCRIPTOR data; USBSCAN_GET_DESCRIPTOR descriptor; DWORD length; BOOL ret; descriptor.DescriptorType=USB_DEVICE_DESCRIPTOR_TYPE; ret=DeviceIoControl(hPhysicalDriveIOCTL,IOCTL_GET_USB_DESCRIPTOR , &descriptor,sizeof(descriptor),&data,sizeof(data), &length,NULL); hPhysicalDriveIOCTL is an handle that I get from a CreateFile call on the device I want to get the descriptor from. I tried GetLastError() and I received the error message "The request is not supported". What do you think it could be? Thanks a lot for your help Cold Tag: Windows VISTA Driver Development Kit. Tag: 89862
 - 12
 - what happens when WM_DEVMODECHANGE message is broadcasted Hi.. Whenever printer settings are changed, i am passing this message. SendMessageTimeout (HWND_BROADCAST, WM_DEVMODECHANGE, 0L, (LPARAM) pszPrinterName, SMTO_NORMAL, 1000, NULL) So that applications will come to know the change in devmode. But the new changes are not reflected in opened applications. Can somebody tell me what happens when WM_DEVMODECHANGE message is broadcasted?? and why the change is not reflected in opened application?? Thanks in Advance. Tag: Windows VISTA Driver Development Kit. Tag: 89861
 - 13
 - Create DDK projects in Visual Studio *easily*! Hi, wanted to introduce you to my Visual Studio project creation wizard: DDKWizard. It is based on the two DDKBUILD flavors of OSR and allows you to customize many aspects of the driver project. For example you can tell DDKWizard to create a project using C++ or C source files. You can optionally create PREfast configurations, 64bit configurations (either IA-64 and/or x64). There are 3 predefined project types. "Driver" creates a generic legacy driver (i.e. includes ntddk.h, could be easily changed to WDM, though). "Native App" creates a native application such as are smss.exe, autochk.exe and so on. "Empty Driver" allows you to migrate an existing project into a Visual Studio project. DDKWizard creates one project per DDK you choose from the listbox. The solution configurations will automatically include only the project which is relevant for the current configuration. The configurations (both project and solution configurations) are named after the DDKBUILD configuration, e.g. "WLHNET checked" (i.e. Windows Vista DDK for .NET Server checked build) or "WNET checked (PREfast)" (i.e. WNET DDK checked PREfast build). Download and information about the wizard at: http://ddkwizard.assarbad.net/ Yes it's free, yes it's OpenSource - no, your created projects are not affected by any particular license, they are yours. Yes, it will be free in future, yes I will continue to maintain it ;) Give it a try. If you don't want to install before looking into the documentation, have a look at the manual first: http://ddkwizard.assarbad.net/downloads/ddkwiz_manual.pdf It supports the DDKs supported by DDKBUILD (from OSR) and is compatible with Visual Studio 2002, 2003 and 2005 (tested only with one VS installation per test-system, yet). Best regards, Oliver PS: If you like it, spread the word! Tag: Windows VISTA Driver Development Kit. Tag: 89857
 - 14
 - How important is IoStatus.Information? I've seen five different ways of handling IoStatus.Information in the DDK docs, but one of them doesn't make sense to me: On success IoStatus.Information is set to a count to indicate how much work was performed, which on error implies it should be 0. On success IoStatus.Information is set to the address of some data structure allocated by the driver, which on error implies it should be NULL. On success IoStatus.Information is set to the address of some data structure allocated by another driver, which on error implies it should be left alone. On success or error, IoStatus.Information is irrelevant (not mentioned in the description of the IRP). On success, IoStatus.Information is 0. The last case makes no sense to me. If IoStatus.Information is only set on success, then on error it would either be some indeterminate value or the initial value from the originator, but the originator could just as easily check IoStatus.Status, so IoStatus.Information is irrelevant. Does any code actually depend on IoStatus.Information to be 0 on success, or were the doc authors just having fun pasting "On success, a driver sets Irp->IoStatus.Information to zero." over and over? Tag: Windows VISTA Driver Development Kit. Tag: 89847
 - 15
 - usb filter driver - constant serial number Hi, i am new to whole driver develompent so i would like some pointers. I'm trying to make my UBS printers (same vendorid and productid, different serial number) to be detected as one ie. my idea is to set serial number to constant value. Something like IgnoreHWSerNumXXXXXXXX registry key but that method is not good enough for me because when i plug printer into another usb port, windows detects it as new device. So, I would like to know it this possible and how. Thanks in advance. Tag: Windows VISTA Driver Development Kit. Tag: 89827
 - 16
 - parport.sys driver installation from user-land application i am working on ddk parport sample. after make, i get the parport.sys. now, i want to replace the system32\driver\parport.sys with this new one, in order to set breakpoint in windbg. i can net stop parport, then i want to overwrite the old parport.sys with the new parport.sys together with the pdb file . is it ok? TIA Tag: Windows VISTA Driver Development Kit. Tag: 89826
 - 17
 - Kernel Direct-x Hi, Can i use direct x in kernel mode device like doing direct drawing to the video card??? Where can i find some examples? Thanks Tag: Windows VISTA Driver Development Kit. Tag: 89819
 - 18
 - Can IRP_MN_REMOVE_DEVICE race with IRP_MN_QUERY_DEVICE_RELATIONS? Is it possible for IRP_MN_QUERY_DEVICE_RELATIONS to race with IRP_MN_REMOVE_DEVICE? I get the impression from "Multiprocessor Considerations for Kernel-Mode Drivers" that it is. (If not then what documentation should I be reading that says they are serialized?) If so, then is this possible: - bus driver's FDO receives IRP_MN_QUERY_DEVICE_RELATIONS (BusRelations) and reports child - child receives IRP_MN_START_DEVICE - PnP manager sends IRP_MN_REMOVE_DEVICE, still thinking child has been reported present - bus driver calls IoInvalidateDeviceRelations - bus driver's FDO receives IRP_MN_QUERY_DEVICE_RELATIONS (BusRelations) and does not report child - child receives IRP_MN_REMOVE_DEVICE and since it was not reported calls IoDeleteDevice on itself - PnP manager sends IRP_MN_REMOVE_DEVICE, now realizing child was not reported present - child receives IRP_MN_REMOVE_DEVICE, even though IoDeleteDevice has already been called ? I think the documentation alludes to the possibility of receiving IRP_MN_REMOVE_DEVICE even after IoDeleteDevice, but the explanation is shady. Tag: Windows VISTA Driver Development Kit. Tag: 89795
 - 19
 - History of remove locks I don't want to discuss again when exactly remove locks are necessary. The question I still have trouble answering is why they were ever invented, why they were ever necessary even for one single IRP. It seems kind of roundabout for reference counting to always protect a device object yet not always block what is basically a device object's destructor (IRP_MN_REMOVE_DEVICE). If the OS can protect a device from being removed in the middle of certain IRPs, then why not for all IRPs? Is there some historical reason? Was it a Windows 9x philosophy? Was safe object retention not as popular on such a consumer platform? Was it awkward to merge Windows 9x plug and play into the NT stream when Windows 2000 was created? (not that I know what the NT driver model looked like) Tag: Windows VISTA Driver Development Kit. Tag: 89792
 - 20
 - SRB_INITIALIZE_DEVICE Hello, I have two USB attached, DirectShow cameras that when booting up, only one of the cameras is successfully enumerated. The other camera will usually show up as an "Unknown Device" (VID_0000&PID_0000) or sometimes not at all in the device manager (as if I didn't even have it plugged in). After the reboot, unplugging and plugging back in the problem camera then allows it to be successfully enumerated. After using SoftICE to poke around to see what my driver is doing on a reboot, I see that only one of the cameras is getting the SRB_INITIALIZE_DEVICE and enumerating just fine. This is behind a native UHCI, Intel USB2.0 controller and a Dell system running XPPro, SP2. DirectX9.0C has been installed, as well as all other updates. It seems as if both cameras are successfully enumerated when behind a USB1.1 hub, so I'm not sure if this is timing related or not. Suggestions? What would cause the class driver to not send another SRB_INITIALIZE device and consequently get the descriptors, etc? Am I going to have to put a USB analyzer on it to determine or? If you need more information, just let me know. Any help, suggestions, tips, links to read up on would help. Thanks in adv. Tag: Windows VISTA Driver Development Kit. Tag: 89788
 - 21
 - METHOD_OUT_DIRECT and ISR I am updating/writing a driver that collects a large amount of data (4MB) from an ISA card. Here is the way I want it to work: In my Dispatch routine I handle a START_SAMPLING IOCTL, which is METHOD_OUT_DIRECT. I read in some settings from the input buffer and store what I need in my device extension. It is the output buffer (at Irp->MdlAddress) that I need help with. I translate this address using MmGetSystemAddressForMdlSafe(Irp->MdlAddress,NormalPagePriority), as I should. But now I need help. After my dispatch routine finishes, the user mode code will start a timer on the ISA card, which triggers interrupts to my driver. I have an ISR that runs once for each interrupt, and reads one data point each time... which it should append to the buffer. The interrupts keep occuring until the ISR sees that it has collected the all the data, and turns off the interrupts. So what my ISR needs to do is access and write to that output buffer that was given to the driver back in the dispatch routine? But how? I gather that in my dispatch routine I need to do something like.. lock the buffer and/or mark the irp as pending and/or queue the irp, etc. Then in my ISR I might need to do more of the same. Can someone tell me what I need to do to use this METHOD_OUT_DIRECT buffer in my ISR? Buzz Tag: Windows VISTA Driver Development Kit. Tag: 89784
 - 22
 - IoAttachDevice oddities I'm curious to understand a couple things about IoAttachDevice. Why does IoAttachDevice (not IoAttachDeviceToDeviceStack) require the AttachedDevice out parameter to point to a global memory location? Why can't it be on the stack? The stack will be around until IoAttachDevice returns, and why would IoAttachDevice have to access the pointer after that? I also wonder, why does IoAttachDevice open a file on the target device and then perform the attach _before_ it closes the file object instead of after? (so that the source device being attached on top receives spurious IRP_MJ_CLEANUP and IRP_MJ_CLOSE IRPs that have no matching IRP_MJ_CREATE) Was this an accident or is there some architectural reason for it? (which I'd like to understand if there is) Tag: Windows VISTA Driver Development Kit. Tag: 89783
 - 23
 - METHOD_OUT_DIRECT and ISR I am updating/writing a driver that collects a large amount of data (4MB) from an ISA card. Here is the way I want it to work: In my Dispatch routine I handle a START_SAMPLING IOCTL, which is METHOD_OUT_DIRECT. I read in some settings from the input buffer and store what I need in my device extension. It is the output buffer (at Irp->MdlAddress) that I need help with. I translate this address using MmGetSystemAddressForMdlSafe(Irp->MdlAddress,NormalPagePriority), as I should. But now I need help. After my dispatch routine finishes, the user mode code will start a timer on the ISA card, which triggers interrupts to my driver. I have an ISR that runs once for each interrupt, and reads one data point each time... which it should append to the buffer. The interrupts keep occuring until the ISR sees that it has collected the all the data, and turns off the interrupts. So what my ISR needs to do is access and write to that output buffer that was given to the driver back in the dispatch routine? But how? I gather that in my dispatch routine I need to do something like.. lock the buffer and/or mark the irp as pending and/or queue the irp, etc. Then in my ISR I might need to do more of the same. Can someone tell me what I need to do to use this METHOD_OUT_DIRECT buffer in my ISR? Buzz Tag: Windows VISTA Driver Development Kit. Tag: 89780
 - 24
 - METHOD_OUT_DIRECT and ISR I am updating/writing a driver that collects a large amount of data (4MB) from an ISA card. Here is the way I want it to work: In my Dispatch routine I handle a START_SAMPLING IOCTL, which is METHOD_OUT_DIRECT. I read in some settings from the input buffer and store what I need in my device extension. It is the output buffer (at Irp->MdlAddress) that I need help with. I translate this address using MmGetSystemAddressForMdlSafe(Irp->MdlAddress,NormalPagePriority), as I should. But now I need help. After my dispatch routine finishes, the user mode code will start a timer on the ISA card, which triggers interrupts to my driver. I have an ISR that runs once for each interrupt, and reads one data point each time... which it should append to the buffer. The interrupts keep occuring until the ISR sees that it has collected the all the data, and turns off the interrupts. So what my ISR needs to do is access and write to that output buffer that was given to the driver back in the dispatch routine? But how? I gather that in my dispatch routine I need to do something like.. lock the buffer and/or mark the irp as pending and/or queue the irp, etc. Then in my ISR I might need to do more of the same. Can someone tell me what I need to do to use this METHOD_OUT_DIRECT buffer in my ISR? Buzz Tag: Windows VISTA Driver Development Kit. Tag: 89779
 - 25
 - METHOD_OUT_DIRECT and ISR I am updating/writing a driver that collects a large amount of data (4MB) from an ISA card. Here is the way I want it to work: In my Dispatch routine I handle a START_SAMPLING IOCTL, which is METHOD_OUT_DIRECT. I read in some settings from the input buffer and store what I need in my device extension. It is the output buffer (at Irp->MdlAddress) that I need help with. I translate this address using MmGetSystemAddressForMdlSafe(Irp->MdlAddress,NormalPagePriority), as I should. But now I need help. After my dispatch routine finishes, the user mode code will start a timer on the ISA card, which triggers interrupts to my driver. I have an ISR that runs once for each interrupt, and reads one data point each time... which it should append to the buffer. The interrupts keep occuring until the ISR sees that it has collected the all the data, and turns off the interrupts. So what my ISR needs to do is access and write to that output buffer that was given to the driver back in the dispatch routine? But how? I gather that in my dispatch routine I need to do something like.. lock the buffer and/or mark the irp as pending and/or queue the irp, etc. Then in my ISR I might need to do more of the same. Can someone tell me what I need to do to use this METHOD_OUT_DIRECT buffer in my ISR? Buzz Tag: Windows VISTA Driver Development Kit. Tag: 89775

Hi friends,

I would like to know the site address to download the "Windows VISTA Driver
development Kit".

Thanks,
Shankar B.

Top

Re: Windows VISTA Driver Development Kit. by Don

Don
Fri Dec 22 07:27:23 CST 2006

Follow the directions given here
http://www.microsoft.com/whdc/devtools/wdk/betawdk.mspx

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

"Shankar9483" <Shankar9483@discussions.microsoft.com> wrote in message
news:DA908C44-EEDC-49DC-9107-ECA060506019@microsoft.com...
> Hi friends,
>
> I would like to know the site address to download the "Windows VISTA
> Driver
> development Kit".
>
> Thanks,
> Shankar B.
>

Top

Re: Windows VISTA Driver Development Kit. by Shankar9483

Shankar9483
Sat Dec 23 02:50:01 CST 2006

Hi,

Thanks for your info. I would like to know the new features which are
supported by Windows VISTA in Dot Matrix Printer Driver side? And where can I
download a sample Dot Matrix Printer driver for VISTA?

Thanks,
Shankar B.

"Don Burn" wrote:

> Follow the directions given here
> http://www.microsoft.com/whdc/devtools/wdk/betawdk.mspx
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>
> "Shankar9483" <Shankar9483@discussions.microsoft.com> wrote in message
> news:DA908C44-EEDC-49DC-9107-ECA060506019@microsoft.com...
> > Hi friends,
> >
> > I would like to know the site address to download the "Windows VISTA
> > Driver
> > development Kit".
> >
> > Thanks,
> > Shankar B.
> >
>
>
>

Top

Re: Windows VISTA Driver Development Kit. by Tim

Tim
Sun Dec 24 18:54:49 CST 2006

Shankar9483 <Shankar9483@discussions.microsoft.com> wrote:
>
>Thanks for your info. I would like to know the new features which are
>supported by Windows VISTA in Dot Matrix Printer Driver side?

Nothing. What were you expecting? There hasn't been a new feature in a
dot matrix printer in ten years.

>And where can I
>download a sample Dot Matrix Printer driver for VISTA?

There are samples in the DDK.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

Top