PCI express Power management event with Vista

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
    - Signed on one OS == What on other OSes? Say I get my driver package signed by WHQL for XP only. How does Server 2003 treat this same driver package, as unsigned, or as having an invalid signature? Tag: PCI express Power management event with Vista Tag: 98156
  - 2
    - Silent Install - Am I ready? Ok, I have my USB (custom setup class) driver pre-installing on XP with a DIFx-based installer completely fine, with no popups during the pre-install. When any of my devices is plugged in for the first time, I get the "Found New Hardware Wizard" and the user has to click through the pages (i.e. "connect to Windows Update? Not this time" and "Install the software automatically"). The driver is found and installed and everything works. My question: Is getting the drivers signed by WHQL the *only* thing I have left between me and a completely silent install (i.e. the user is not presented with anything other than the pop-up balloons in the system tray, and in particular no questions he has to answer or buttons to click)? For instance, is there anything I have to add to the INF (beyond the .cat line) to make it a silent install? Does Windows treat a custom setup class differently than a non-custom class (e.g. does Windows do something silly like not allow a silent install with a custom setup class)? Is there anything I'm forgetting and/or never knew? Tag: PCI express Power management event with Vista Tag: 98155
  - 3
    - Notify Object and DllGetClassObject not calling Hi, I am trying to wrtie a Notify object for IM that can control over Binding paths. While my testing I deployed a notify object dll. After make some modification, I tried to install new DLL. During deployment of new dll, DllGetClassObject is not being called but DllRegisterServer is called. Please suggest me what should I Do? -- With regards thanks Anand Choubey Tag: PCI express Power management event with Vista Tag: 98153
  - 4
    - NDIS_NET_BUFFER_LIST_8021Q_INFO not available The document said: To retrieve or insert 802.1Q information that is associated with a NET_BUFFER_LIST structure, an NDIS driver calls the NET_BUFFER_LIST_INFO macro and specifies the Ieee8021QNetBufferListInfo information type. But I always get NULL data from the NET_BUFFER_LIST OOB data on the TX path. Does anyone can get this Ieee8021QNetBufferListInfo for QOS support? Any idea would be appreciate. Note: Miniport driver is Native WiFi driver. Thanks! Tag: PCI express Power management event with Vista Tag: 98143
  - 5
    - Unclassified Signature: requirements? Hello, I need to certify a driver using the Unclassified Signature. I have some questions: 1- The DTM manual mentions "to obtain a logo for a server requires that the system being used to test the device supports four processors and a minimum of 1 GB of RAM." Does that mean that if a company needs to certify a server needs that configuration or it means if I want my driver to run on Windows 2003 server for instance, I need to run certificaiton for that sistem? 2- I want to certify my driver for Vista 32/64 bit and Windows 2003 32/64 bit. Do I need to run the suite of tests on all the OSs or 32 will also cover 64 bit flavors? 3- I need to purchase a system for the logo testing: can I purchuse a system that supports all the OSs and then run a test suite at a time. Is the DTM able to collect the results sequencially or the logo suite needs to run at the same time on all the OSs that need to be certified? Regards, atony Tag: PCI express Power management event with Vista Tag: 98142
  - 6
    - Where can I find the definitive specification of DbgPrint()? The DDK documentation states DbgPrint() is much like printf which is a standard C library function. However, printf doesn't define such format specifiers as %ws and %wZ. I know how to use these format specifiers, but I can't find any definitive specification for them. Where to find them? Thanks for any comments. Tag: PCI express Power management event with Vista Tag: 98141
  - 7
    - WLK: USB video device with "Plug and Play" code 10 error? We test USB video device logo under Vista32 with WLK testing tool. Meet "plug and Play" with code 10 error. Do you have any idea for this error? Thanks, Tag: PCI express Power management event with Vista Tag: 98132
  - 8
    - Getting the Iso data Hi, Is there an appropriate way to transfer the isochronous data to the application or to read these data from the application. I read about a ring buffer in kernel that the user could access through IOCTL Thanks for any suggestion CYB Tag: PCI express Power management event with Vista Tag: 98129
  - 9
    - USB Mouse driver I need to decode the data from a USB pointing device. Whenever it is plugged in, it is automatically interpretted by the system as a mouse device. How do I go about accessing the data from the mouse from a c++ program?. Ideally, I'd like to treat the device as a normal COM/serial port and just use open()/close()/read() functions to read the data - can I do this?. Thanks in advance, Dave Tag: PCI express Power management event with Vista Tag: 98127
  - 10
    - How to create and register one virtual audio device on Vista? Hello, I want to create and regiter one virtual audio device on Vista, this virtual device will get audio streaming from real audio device, process and distribute the data by following the audio streaming path. I know filter driver of XP and APO of Vista can filter and process the audio streaming. but I really need to register one virtual device, so users can select the virtual device to use special audio effects or select the real device to bypass special audio effects. Driver of SRS audio sandbox can do the job, it's a famous application. How the driver works? Tag: PCI express Power management event with Vista Tag: 98126
  - 11
    - kmdf\1394 sample on VISTA Hi I've tried to install the "C:\WinDDK\6000\src\kmdf\1394\driver\1394vdev" and the "WinDDK\6000\src\kmdf\1394\driver\1394diag" on VISTA, but get the error message: " Update Driver Software - 1394_VIRTUAL_DEVICE Windows encountered a problem installing the driver software for your device Windows found driver software for your device but encountered an error while attempting to install it. 1394 Virtual device The system cannot find the file specified. If you know the manufacturer of your device, you can visit its website and check the support section for driver software. " What is wrong ? I've tried to build the Win XP env. and install on XP. That works fine. Thanks in advance best Eigil Tag: PCI express Power management event with Vista Tag: 98125
  - 12
    - Notify Object and DllGetClassObject Hi, I have written a IM Filter driver. Now I want to bind my IM driver with a perticular physical NIC. I am borrowing notify object source code from MUX sample. I modified IM's INF file too. INF file is: [IMD.ndi.AddReg] HKR, Ndi, ClsID, , {801B6F17-2293-441c-955A-C8B40D69CF8D} ; THIS IS NEW GUID. HKR, Ndi, ComponentDll, , imd.dll HKR, Ndi, FilterClass, , failover HKR, Ndi, FilterDeviceInfId, , ct_imdmp HKR, Ndi, Service, , IMD HKR, Ndi\Interfaces, UpperRange, , noupper HKR, Ndi\Interfaces, LowerRange, , nolower HKR, Ndi\Interfaces, FilterMediaTypes, , "ethernet" ;HKR, Ndi\Interfaces, FilterMediaTypes, , "ethernet, tokenring, fddi, wan" The new same guid is modified in IDL and RGS files. Problem is: Whenever I install IM driver. DllMain, DllRegisterServer methods are called but never DllGetClassObject is called. Why so? my os is XP SP2. Please suggest me how to solve problem. Thanks and With Regards Anand Choubey Tag: PCI express Power management event with Vista Tag: 98122
  - 13
    - KMDF 1.7 for other platforms than Windows Server 2008? Hi, I see that the KDMF web pages states that KMDF 1.7 is only available for Windows Server 2008 and KMDF 1.5 should be used for XP and Vista <http://www.microsoft.com/whdc/driver/wdf/KMDF_pkg.mspx>. When can we expect version 1.7 to replace 1.5? Regards, Johan Paul Tag: PCI express Power management event with Vista Tag: 98121
  - 14
    - Capture the Audio Output? Hi everyone Wondered how can I capture the audio that goes out on the speakers. I dont mind writing a device driver, injecting code etc - just do the job. Any ideas? Any samples out there for anything like that? Thanks for _any_ ideas Lior Tag: PCI express Power management event with Vista Tag: 98117
  - 15
    - Are 2k/XP display drivers restricted to win32k.sys exports? I'm trying to write a display driver using the Windows 2000 model, but it seems that if I call any ntoskrnl.exe functions, GDI refuses to load my driver (and does so with the rather unhelpful statement that "It was written for a previous version of Windows"). Unlike the miniport driver, where the docs explicitly say that only functions exported from videoprt.sys may be called, AFAICT the display driver docs are completely silent on the subject. Has anyone got chapter and verse on this before I commit to working around a problem which may not be what I think it is? TIA. Tag: PCI express Power management event with Vista Tag: 98114
  - 16
    - DTM and IM driver Hi , I am running the DTM tests for my IM (MUX) driver. I found that there are 1. Driver Realibility tests 2. LAN (ethernet) tests In LAN(ethernet) tests , HP SLIPT test for im driver . There is no test for data path testing , as in earlier WHQL tests. Are there any data path testing tests in DTM for IM driver or my setup is wrong ? Tag: PCI express Power management event with Vista Tag: 98106
  - 17
    - wmi and interrupt moderation I want to know from application layer whether underlying NIC supports interrupt moderation or not. I used WMI , msndis_interruptmoderation, but I am not getting the correct result. Is there any way to get this info from user layer or msndis_interruptmoderation is a wrong way ? Thanks Tag: PCI express Power management event with Vista Tag: 98105
  - 18
    - Does a virtaul NDIS driver also need to pass WHQL to get signed? Hi, I have developed a virtual NDIS Miniport driver for windows XP and windows CE. In order to get the driver signed, do I also need to go through the WHQL process? Thanks. Daniel Tag: PCI express Power management event with Vista Tag: 98104
  - 19
    - How to open control object from user app using symbolic link? Hi There, I am having problem opening control device object that I create in driver from the user application. I create a control object and make a symbolic link to it. When I try to open it using CreateFile() it returns invalid handle and GetlastError() returns "file not found" Here is how I create control object: #define K_MOUSE_FILTER_DEVICE_NAME L"\\Device\\MyCompanyMouseSniffer" #define K_MOUSE_CONTROL_DEVICE_NAME L"\\Device\\MyCompanyMouseSnifferIoCtl" NTSTATUS MouseFilter_CreateControlObject(IN WDFDRIVER Driver) { PWDFDEVICE_INIT DeviceInit; UNICODE_STRING DeviceName; WDF_OBJECT_ATTRIBUTES DeviceAttributes; WDF_IO_QUEUE_CONFIG DeviceQueueConfig; WDFQUEUE DeviceQueue; UNICODE_STRING SymbolicLinkName; NTSTATUS status = STATUS_INSUFFICIENT_RESOURCES; if (InstanceNo != 0) return STATUS_SUCCESS; /* Allocate INIT structure. */ DeviceInit = WdfControlDeviceInitAllocate(Driver, &SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_RW_RES_R); if (NULL == DeviceInit) { DebugPrint(("WdfControlDeviceInitAllocate failed\n")); return status; } /* Assign name to the control device. */ RtlInitUnicodeString(&DeviceName, K_MOUSE_FILTER_DEVICE_NAME); status = WdfDeviceInitAssignName(DeviceInit, &DeviceName); if (!NT_SUCCESS(status)) { WdfDeviceInitFree(DeviceInit); DebugPrint(("WdfDeviceInitAssignName failed with status code 0x%x\n", status)); return status; } /* Shutdown notification must be set before WdfDeviceCreate() call. */ WdfControlDeviceInitSetShutdownNotification(DeviceInit, ControlDevice_EvtShutdown, WdfDeviceShutdown); /* Initialize attributes struct. */ WDF_OBJECT_ATTRIBUTES_INIT(&DeviceAttributes); /* Create device. */ status = WdfDeviceCreate(&DeviceInit, &DeviceAttributes, &ControlObject); if (!NT_SUCCESS(status)) { WdfDeviceInitFree(DeviceInit); DebugPrint(("WdfDeviceCreate failed with status code 0x%x\n", status)); return status; } /* Create device queue. */ WDF_IO_QUEUE_CONFIG_INIT_DEFAULT_QUEUE(&DeviceQueueConfig, WdfIoQueueDispatchSequential); DeviceQueueConfig.EvtIoRead = ControlObject_EvtIoRead; // READ ONLY status = WdfIoQueueCreate(ControlObject, &DeviceQueueConfig, WDF_NO_OBJECT_ATTRIBUTES, WDF_NO_HANDLE); if (!NT_SUCCESS(status)) { WdfDeviceInitFree(DeviceInit); DebugPrint(("WdfIoQueueCreate failed with status code 0x%x\n", status)); return status; } /* Create symbolic link so it could be open by CreateFile() from user space. */ RtlInitUnicodeString(&SymbolicLinkName, K_MOUSE_CONTROL_DEVICE_NAME); status = WdfDeviceCreateSymbolicLink(ControlObject, &SymbolicLinkName); if (!NT_SUCCESS(status)) { WdfDeviceInitFree(DeviceInit); DebugPrint(("WdfDeviceCreateSymbolicLink failed with status code 0x%x\n", status)); return status; } /* Done. */ WdfControlFinishInitializing(ControlObject); InstanceNo ++; return status; } It doesn't fail and function return status 0. Here is how I open it from user application: PWCHAR path = L"\\\\.\\MyCompanyMouseSnifferIoCtl"; HANDLE device = CreateFile(path, 0, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL ); I also tried L"\\Device\\MyCompanyMouseSnifferIoCtl"; I can't figure out what I am doing wrong. I appreciate your help. Thank you, Dmitry. Tag: PCI express Power management event with Vista Tag: 98103
  - 20
    - Co-Installer on Vista not called with DIF_INSTALLDEVICE code! Hi All, I have written a device co-installer that changes the com port number that system has assigned to my device. It is working fine with Windows XP. But i have the problem on windows vista. My co-installer is called, but not with DIF_INSTALLDEVICE code. I am getting DIF function codes 0x12 (DIF_PROPERTYCHANGE) and 0xc(DIF_DESTROYPRIVATEDATA) during driver loading. The same codes when i disable and enable the device. I compiled the co-installer using WDK 6000 build environment for vista. Does any change required in coinstaller section in .inf file for Windows vista. Any comments on whats happening are welcome. Thanks in advance, Chiranjeevi. Tag: PCI express Power management event with Vista Tag: 98099
  - 21
    - Reading Ethernet data from NDIS_PACKET Packet I am running WinCE 5.0, and I am trying to trap on a certain IP address. I would like to trap on when a certain GRATUITOUS ARP is sent out to a modem IP address(192.168.xx.xx). I would like to trap on when a the ARP goes out in my NDIS driver send function. NDIS_STATUS aumacSend(IN NDIS_HANDLE MiniportAdapterContext, IN PNDIS_PACKET Packet, IN UINT Flags ). I would like to parse the NDIS packet to read the destination and source addres. In addition I need to read the type to determine the type of message IP, ARP. I tried to using the following code, but I Get an error when trying to read the buffer that I copied the NDIS packet into. I would like to know where can I get I read the ethernet packet? I think that I am at the right place inside the NDIS miniport driver. NDIS_STATUS aumacSend(IN NDIS_HANDLE MiniportAdapterContext, IN PNDIS_PACKET Packet, IN UINT Flags ) { ULONG PacketLength; PUCHAR Buffer; ULONG BufferLength; ULONG TotalLength; UINT BufferCount; BOOL LastBuffer = FALSE; PNDIS_BUFFER NdisBuffer; PAUMAC_ADAPTER Adapter; PUCHAR TargetBuffer; ULONG BufferNumber; ULONG nNumberOfBytesRead = 74; PUCHAR myData; int i = 0; Adapter = (PAUMAC_ADAPTER)(MiniportAdapterContext); DEBUGMSG(ZONE_TX, (L"+Send\r\n")); // // Get information about the packet // NdisQueryPacket(Packet, NULL, &BufferCount, &NdisBuffer, &PacketLength); UTILReadOnPacket( Packet, (PUCHAR )&myData, PacketLength, 0,//Offset From MAC Header &nNumberOfBytesRead ); OutputDebugString(L"Packet Length = "); DBGOut(PacketLength); OutputDebugString(L" \r\n"); for(i=0;i<74;i++) { myData[i] = *(Buffer+i); DBGHexOut(myData[i]); OutputDebugString(L"\r\n "); } ///////////////////////////////////////////////////////////////////////////// //// UTILReadOnPacket // // Purpose // Logical read on the packet data in a NDIS_PACKET. // // Parameters // // Return Value // // Remarks // The purpose of this function is to provide a convenient mechanism to // read packet data from an NDIS_PACKET that may have multiple chained // NDIS_BUFFERs. // VOID UTILReadOnPacket( PNDIS_PACKET Packet, PUCHAR lpBuffer, ULONG nNumberOfBytesToRead, ULONG nOffset, // Byte Offset, Starting With MAC Header PULONG lpNumberOfBytesRead ) { PNDIS_BUFFER CurrentBuffer; UINT nBufferCount, TotalPacketLength; PUCHAR VirtualAddress; UINT CurrentLength, CurrentOffset; UINT AmountToMove; *lpNumberOfBytesRead = 0; if (!nNumberOfBytesToRead) return; // // Query Packet // NdisQueryPacket( (PNDIS_PACKET )Packet, (PUINT )NULL, // Physical Buffer Count (PUINT )&nBufferCount, // Buffer Count &CurrentBuffer, // First Buffer &TotalPacketLength // TotalPacketLength ); // // Query The First Buffer // NdisQueryBuffer( CurrentBuffer, &VirtualAddress, &CurrentLength ); CurrentOffset = 0; while( nOffset || nNumberOfBytesToRead ) { while( !CurrentLength ) { NdisGetNextBuffer( CurrentBuffer, &CurrentBuffer ); // If we've reached the end of the packet. We return with what // we've done so far (which must be shorter than requested). if (!CurrentBuffer) return; NdisQueryBuffer( CurrentBuffer, &VirtualAddress, &CurrentLength ); CurrentOffset = 0; } if( nOffset ) { // Compute how much data to move from this fragment if( CurrentLength > nOffset ) CurrentOffset = nOffset; else CurrentOffset = CurrentLength; nOffset -= CurrentOffset; CurrentLength -= CurrentOffset; } if( nOffset ) { CurrentLength = 0; continue; } if( !CurrentLength ) { continue; } // Compute how much data to move from this fragment if (CurrentLength > nNumberOfBytesToRead) AmountToMove = nNumberOfBytesToRead; else AmountToMove = CurrentLength; // Copy the data. NdisMoveMemory( lpBuffer, &VirtualAddress[ CurrentOffset ], AmountToMove ); // Update destination pointer lpBuffer += AmountToMove; // Update counters *lpNumberOfBytesRead +=AmountToMove; nNumberOfBytesToRead -=AmountToMove; CurrentLength = 0; } } void DBGOut(ULONG dwValue) { TCHAR tcTemp[10]; wsprintf(tcTemp,L"%ld",dwValue); //#ifdef TRACEON OutputDebugString(tcTemp); //#endif } void DBGHexOut(UCHAR dwValue) { TCHAR tcTemp[16]; wsprintf(tcTemp,L"0x%02X",dwValue); //#ifdef TRACEON OutputDebugString(tcTemp); //#endif } Tag: PCI express Power management event with Vista Tag: 98097
  - 22
    - BasepCreateActCtx() tries to open "buggy" path Hello, while debugging a problematic system, I keep getting the following output in WinDBG: SXS: BasepCreateActCtx() NtOpenFile(\??\C:\??\C:\WINDOWS\system32\winlogon.exe) failed Does anyone know what this means? Why does it try to open the "buggy" \??\C:\??\C:\... path? Is there something wrong in the setup? I search on the Web did not show much of value. At http://microsoft-programming.hostweb.com/TopicMessages/microsoft.public.win32.programmer.kernel/2105240/1/Default.aspx, someone asked the same question (without answer), but there wasn't much more available. Thank you for any insight. ;) Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ Tag: PCI express Power management event with Vista Tag: 98083
  - 23
    - Vista 64bit: 1394 ISOCH_ATTACH_BUFFERS fails with STATUS_INVALID PARAMETERS I am porting a 32Bit version of a 1394 (firewire) driver to Vista 64Bit. As reported in my recent newsgroup issue, there is the strange limitation of 1MB buffer size for 1394 isochronous transfers in Vista 64bit. So I tried to transfer data buffers smaller than 1 MB. After successfully allocating 1394 ressources etc.as usual (but <1MB), I tried to attach buffers smaller than 1MB, but the the request REQUEST_ISOCH_ATTACH_BUFFERS fails constantly with STATUS_INVALID PARAMETERS. I traced all the parameters and return values from the preceeding requests and the attach buffer request to be shure nothing went wrong, so I am shure everything is correct. But I'm just perplexed and must conclude, that this is in all probability related to the 1MB limit 1394 stacks misbehaviour. ? Thanks for the support, Christoph Tag: PCI express Power management event with Vista Tag: 98082
  - 24
    - audio filter driver cause system bootstrap hang I change wdk keyboard source code to implemete my audio filter driver, and install it as audio class filter, but when system bootstarp, it hang when login into OS with error message: "Access violation - code c0000005 (!!! second chance !!!) kmixer!GetSystemAddressForMdlWithFailFlag+0xb: aef7770b 668b4606 mov ax,word ptr [esi+6]" call stack as following: #ChildEBP RetAddr Args to Child ChildEBP RetAddr Args to Child af35aaa8 aef7a397 00000000 896ca3ac 8a31a648 kmixer!GetSystemAddressForMdlWithFailFlag+0xb af35aae4 ba6141e8 8a6ae9d8 896ca240 af35ab14 kmixer!PinDispatchWrite+0x87 af35aaf4 804e13d9 8a6ae9d8 896ca240 8a68b698 ks!DispatchWrite+0x1c af35ab04 f79a38e0 00000000 896ca3ac af35ab3c nt!IopfCallDriver+0x31 af35ab14 804e13d9 896ca8b8 896ca240 896ca240 audiofilter!KbFilter_DispatchPassThrough+0xd0 af35ab24 af20b569 00000001 8a31c4d8 896ca240 nt!IopfCallDriver+0x31 af35ab3c ba6141e8 896c8b30 8a685b80 af35ab6c sysaudio!CInstance::DispatchForwardIrp+0x68 af35ab4c 804e13d9 896c8b30 896ca240 8a68b698 ks!DispatchWrite+0x1c af35ab5c f79a38e0 8a3bc5a0 896ca3ac af35ab98 nt!IopfCallDriver+0x31 af35ab6c 804e13d9 896c9b08 896ca240 8a3bc5a0 audiofilter!KbFilter_DispatchPassThrough+0xd0 af35ab7c aefe0dfa 896dc008 897e1000 8a443290 nt!IopfCallDriver+0x31 af35ab98 aefe1108 896fb2b0 00000000 896d4a30 wdmaud!WriteWaveOutPin+0xb2 af35abf4 aefe127d 896dc008 897e1000 8a443290 wdmaud!Dispatch_WaveOutWritePin+0x15d af35ac20 804e13d9 00000000 897e1000 8a68b698 wdmaud!SoundDispatch+0x3d5 af35ac30 f79a38e0 001d811c 896dc0c0 af35ac64 nt!IopfCallDriver+0x31 af35ac40 804e13d9 896c28e8 896dc008 806ff410 audiofilter!KbFilter_DispatchPassThrough+0xd0 af35ac50 8056f50b 896dc0c0 8a69b0b0 896dc008 nt!IopfCallDriver+0x31 af35ac64 80580fb1 896c28e8 896dc008 8a69b0b0 nt!IopSynchronousServiceTail+0x60 af35ad00 8058709e 00000808 000007c4 00000000 nt!IopXxxControlFile+0x5ef af35ad34 804dd99f 00000808 000007c4 00000000 nt!NtDeviceIoControlFile+0x2a My audio filter driver name :"audiofilter". 1: kd> !drvobj audiofilter Driver object (8a68b698) is for: \Driver\audiofilter Driver Extension List: (id , addr) Device Object list: 896dbd10 896ca8b8 896dc478 896d0560 8a676a58 896d4460 896c9b08 896c28e8 8a44ec10 8a453408 8a458700 8a45d6c0 8a463448 8a5a3a10 1: kd> !devstack 896dbd10 !DevObj !DrvObj !DevExt ObjectName > 896dbd10 \Driver\audiofilter 896dbdc8 8a47ea98 \Driver\drmkaud 8a47eb50 896d08c0 \Driver\swenum 896d0978 KSENUM#00000008 !DevNode 8974dee8 : DeviceInst is "SW\{eec12db6-ad9c-4168-8658-b03daef417fe}\{ABD61E00-9350-47e2-A632-4438B90C6641}" ServiceName is "drmkaud" 1: kd> !devstack 896ca8b8 !DevObj !DrvObj !DevExt ObjectName > 896ca8b8 \Driver\audiofilter 896ca970 8a6ae9d8 \Driver\kmixer 8a6aea90 89759b28 \Driver\swenum 89759be0 KSENUM#00000007 !DevNode 896d0d18 : DeviceInst is "SW\{b7eafdc0-a680-11d0-96d8-00aa0051e51d}\{9B365890-165F-11D0-A195-0020AFD156E4}" ServiceName is "kmixer" 1: kd> !devstack 896dc478 !DevObj !DrvObj !DevExt ObjectName > 896dc478 \Driver\audiofilter 896dc530 896caa08 \Driver\DMusic 896caac0 00000078 89762b28 \Driver\swenum 89762be0 KSENUM#00000006 !DevNode 89754008 : DeviceInst is "SW\{8c07dd50-7a8d-11d2-8f8c-00c04fbf8fef}\dmusic" ServiceName is "DMusic" 1: kd> !devstack 896d0560 !DevObj !DrvObj !DevExt ObjectName > 896d0560 \Driver\audiofilter 896d0618 8a3f7d20 \Driver\swmidi 8a3f7dd8 896c8f10 \Driver\swenum 896c8fc8 KSENUM#00000005 !DevNode 8a356a40 : DeviceInst is "SW\{6c1b9f60-c0a9-11d0-96d8-00aa0051e51d}\{9B365890-165F-11D0-A195-0020AFD156E4}" ServiceName is "swmidi" 1: kd> !devstack 8a676a58 !DevObj !DrvObj !DevExt ObjectName > 8a676a58 \Driver\audiofilter 8a676b10 8a3db490 \Driver\aec 8a3db548 8a5e6cb8 \Driver\swenum 8a5e6d70 KSENUM#00000004 !DevNode 8a41f5e8 : DeviceInst is "SW\{4245ff73-1db4-11d2-86e4-98ae20524153}\{9B365890-165F-11D0-A195-0020AFD156E4}" ServiceName is "aec" 1: kd> !devstack 896d4460 !DevObj !DrvObj !DevExt ObjectName > 896d4460 \Driver\audiofilter 896d4518 8a5a6f10 \Driver\splitter 8a5a6fc8 8a4064e8 \Driver\swenum 8a4065a0 KSENUM#00000003 !DevNode 8a6b0590 : DeviceInst is "SW\{2f412ab5-ed3a-4590-ab24-b0ce2aa77d3c}\{9B365890-165F-11D0-A195-0020AFD156E4}" ServiceName is "splitter" 1: kd> !devstack 896c9b08 !DevObj !DrvObj !DevExt ObjectName > 896c9b08 \Driver\audiofilter 896c9bc0 896c8b30 \Driver\sysaudio 896c8be8 sysaudio 896dfe88 \Driver\swenum 896dff40 KSENUM#00000002 !DevNode 8a4202f8 : DeviceInst is "SW\{a7c7a5b0-5af3-11d1-9ced-00a024bf0407}\{9B365890-165F-11D0-A195-0020AFD156E4}" ServiceName is "sysaudio" 1: kd> !devstack 896c28e8 !DevObj !DrvObj !DevExt ObjectName > 896c28e8 \Driver\audiofilter 896c29a0 896dfb38 \Driver\wdmaud 896dfbf0 896d3358 \Driver\swenum 896d3410 KSENUM#00000001 !DevNode 896c3430 : DeviceInst is "SW\{cd171de3-69e5-11d2-b56d-0000f8754380}\{9B365890-165F-11D0-A195-0020AFD156E4}" ServiceName is "wdmaud" 1: kd> !devstack 8a44ec10 !DevObj !DrvObj !DevExt ObjectName > 8a44ec10 \Driver\audiofilter 8a44ecc8 8a44f500 \Driver\audstub 8a44f5b8 8a7954f0 \Driver\PnpManager 8a7955a8 00000039 !DevNode 8a7953a8 : DeviceInst is "Root\MEDIA\MS_MMVID" ServiceName is "audstub" 1: kd> !devstack 8a453408 !DevObj !DrvObj !DevExt ObjectName > 8a453408 \Driver\audiofilter 8a4534c0 8a453938 \Driver\audstub 8a4539f0 8a795730 \Driver\PnpManager 8a7957e8 00000038 !DevNode 8a7955e8 : DeviceInst is "Root\MEDIA\MS_MMVCD" ServiceName is "audstub" 1: kd> !devstack 8a458700 !DevObj !DrvObj !DevExt ObjectName > 8a458700 \Driver\audiofilter 8a4587b8 8a458f10 \Driver\audstub 8a458fc8 8a795970 \Driver\PnpManager 8a795a28 00000037 !DevNode 8a795828 : DeviceInst is "Root\MEDIA\MS_MMMCI" ServiceName is "audstub" 1: kd> !devstack 8a45d6c0 !DevObj !DrvObj !DevExt ObjectName > 8a45d6c0 \Driver\audiofilter 8a45d778 8a45dc88 \Driver\audstub 8a45dd40 8a795bb0 \Driver\PnpManager 8a795c68 00000036 !DevNode 8a795a68 : DeviceInst is "Root\MEDIA\MS_MMDRV" ServiceName is "audstub" 1: kd> !devstack 8a463448 !DevObj !DrvObj !DevExt ObjectName > 8a463448 \Driver\audiofilter 8a463500 8a463a38 \Driver\audstub 8a463af0 8a795df0 \Driver\PnpManager 8a795ea8 00000035 !DevNode 8a795ca8 : DeviceInst is "Root\MEDIA\MS_MMACM" ServiceName is "audstub" 1: kd> !devstack 8a5a3a10 !DevObj !DrvObj !DevExt ObjectName > 8a5a3a10 \Driver\audiofilter 8a5a3ac8 8a5a55c0 \Driver\senfilt 8a5a5678 8a5a2400 \Driver\aeaudio 8a5a24b8 8a689c80 \Driver\smwdm 8a689d38 00000072 8a7e3460 \Driver\PCI 8a7e3518 NTPNP_PCI0008 !DevNode 8a7da3b8 : DeviceInst is "PCI\VEN_8086&DEV_266E&SUBSYS_02D91014&REV_03\3&61aaa01&0&F2" ServiceName is "smwdm" As my source code is very simple, and it does not change IRPs at all, it just print some message in KbFilter_DispatchPassThrough(...) and call lower driver. during system bootstrap , use Windbg, it can display the received IRPs, but when I enter OS user name & password to login. system hangs :( this issue bother me a lot, could anybody give me a hand or give some tips to accomplish such one simple audio filter. By the way: I also try to install the simple filter driver as one device filter driver(lower driver is sysaudio.sys), but it seems system can not find my audio filter driver. I install device filter driver as follows: 1. Run regedit and locate audio class under CurrentControlSet/Class key, then under sysaudio key add "Upperfilters" audiofilter 2. under Service Key, add audiofilter related key, just the same as install it as one class filter driver. Does some install problems with my installation process? NTSTATUS DriverEntry ( IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath ) /*++ Routine Description: Initialize the entry points of the driver. --*/ { ULONG i; UNREFERENCED_PARAMETER (RegistryPath); // // Fill in all the dispatch entry points with the pass through function // and the explicitly fill in the functions we are going to intercept // for (i = 0; i <= IRP_MJ_MAXIMUM_FUNCTION; i++) { DriverObject->MajorFunction[i] = KbFilter_DispatchPassThrough; } DriverObject->MajorFunction [IRP_MJ_CREATE] = DriverObject->MajorFunction [IRP_MJ_CLOSE] = KbFilter_CreateClose; // DriverObject->MajorFunction [IRP_MJ_PNP] = KbFilter_PnP; // DriverObject->MajorFunction [IRP_MJ_POWER] = KbFilter_Power; // DriverObject->MajorFunction [IRP_MJ_INTERNAL_DEVICE_CONTROL] = // KbFilter_InternIoCtl; // // If you are planning on using this function, you must create another // device object to send the requests to. Please see the considerations // comments for KbFilter_DispatchPassThrough for implementation details. // // DriverObject->MajorFunction [IRP_MJ_DEVICE_CONTROL]; DriverObject->DriverUnload = KbFilter_Unload; DriverObject->DriverExtension->AddDevice = KbFilter_AddDevice; return STATUS_SUCCESS; } NTSTATUS KbFilter_DispatchPassThrough( __in PDEVICE_OBJECT DeviceObject, __in PIRP Irp ) /*++ Routine Description: Passes a request on to the lower driver. Considerations: If you are creating another device object (to communicate with user mode via IOCTLs), then this function must act differently based on the intended device object. If the IRP is being sent to the solitary device object, then this function should just complete the IRP (becuase there is no more stack locations below it). If the IRP is being sent to the PnP built stack, then the IRP should be passed down the stack. These changes must also be propagated to all the other IRP_MJ dispatch functions (create, close, cleanup, etc) as well! --*/ { PIO_STACK_LOCATION irpStack = IoGetCurrentIrpStackLocation(Irp); PAGED_CODE(); DbgPrintKbFilter_DispatchPassThrough\n "); if(irpStack->MajorFunction == IRP_MJ_DEVICE_CONTROL){ switch (irpStack->Parameters.DeviceIoControl.IoControlCode) { case IOCTL_KS_READ_STREAM: DbgPrint("IOCTL_KS_READ_STREAM\n"); break; case IOCTL_KS_WRITE_STREAM: DbgPrint("IOCTL_KS_WRITE_STREAM\n"); break; case IOCTL_KS_PROPERTY: DbgPrint("IOCTL_KS_PROPERTY\n"); break; default: // DbgPrint("Not our concerned"); break; } } // // Pass the IRP to the target // IoSkipCurrentIrpStackLocation(Irp); return IoCallDriver(((PDEVICE_EXTENSION) DeviceObject->DeviceExtension)->TopOfStack, Irp); } NTSTATUS KbFilter_AddDevice( __in PDRIVER_OBJECT Driver, __in PDEVICE_OBJECT PDO ) { PDEVICE_EXTENSION devExt; IO_ERROR_LOG_PACKET errorLogEntry; PDEVICE_OBJECT device; NTSTATUS status = STATUS_SUCCESS; PAGED_CODE(); DbgPrint("KbFilter_AddDevice...\n"); status = IoCreateDevice(Driver, sizeof(DEVICE_EXTENSION), NULL, FILE_DEVICE_UNKNOWN, 0, FALSE, &device ); if (!NT_SUCCESS(status)) { return (status); } RtlZeroMemory(device->DeviceExtension, sizeof(DEVICE_EXTENSION)); devExt = (PDEVICE_EXTENSION) device->DeviceExtension; devExt->TopOfStack = IoAttachDeviceToDeviceStack(device, PDO); if (devExt->TopOfStack == NULL) { IoDeleteDevice(device); return STATUS_DEVICE_NOT_CONNECTED; } //IRP_BUFFERED_IO // ASSERT(devExt->TopOfStack); devExt->Self = device; devExt->PDO = PDO; devExt->DeviceState = PowerDeviceD0; devExt->SurpriseRemoved = FALSE; devExt->Removed = FALSE; devExt->Started = FALSE; device->Flags |= (DO_BUFFERED_IO | DO_POWER_PAGABLE); device->Flags &= ~DO_DEVICE_INITIALIZING; return status; } Tag: PCI express Power management event with Vista Tag: 98078
  - 25
    - Invoking BIOS services from a windows driver. I would like to query the system memory map that BIOS hands off to Windows by using the e820 service (int 15h). First of all, is BIOS still resident (always, depends, no) when Windows is running?. If so, is it possible to invoke any int services to access BIOS?. If not, then are there any Windows registry entries that let me find out what the memory map was that BIOS handed off to Windows?. Thanks, Ramakrishna Saripalli Tag: PCI express Power management event with Vista Tag: 98070
- Next
  - 1
    - WHQL signing confusion Hi, I have developed a display driver I would like to have CAT-signed by WHQL. My driver consists of three binaries and a single INF. The installer is an executable, with the binaries and the INF file embedded. When installing, the installer extracts binaries and INF and installs the usual way (class installer etc). The driver loads at boot-time. 1) I have signed the 32bit and 64bit binaries with signtool.exe. Can I just ship my driver as three (six) binaries and an inf-file to WHQL, or do I need to package it in some way (e.g. a CAB-file)?? 2) When/if WHQL accepts and signs my driver, I get a CAT file in return. I reference this file from the inf-file (CatalogFile=...). If I include the CAT file in above mentioned installer, everything should work. .. right? Or do I need to install in some other way?? 3) When I get my driver CAT-signed, and I discover and fix a bug in it, do I need to start all over with WHQL? 4) I'm completely new to driver signing, so any other advice you may have will be greatly appreciated! Thanks and regards, Sebastian Bargmann Tag: PCI express Power management event with Vista Tag: 98059
  - 2
    - SMBus Client driver I have been asked to write a device driver for various SMBus device (Temp/Voltage/etc) on some of our embedded PC's and have found some promising information in the DDK documentation. There appears to be an SMBus Class driver available in the newer OS's which would require me to writ e an SMBus client driver. However, I have not been able to find any reference to this Bus Class driver except in the documentation. Are there DDK samples? The DDK I have installed doesn't have any smbus related header files? Any help would be greatly appreciated. Tag: PCI express Power management event with Vista Tag: 98057
  - 3
    - mass storage driver key name & drive handles. Hi, I have looked at the usbview application in the DDK and know how to get the mass storage driver key name. However, I don't know how to get the drive handles that are exposed by the windows drivers for this particular device. For example. * I can get the driver key name for the mass storages driver in question after enumerating the PCI/USB tree for a particular card reader I am interested in. This works fine. This card reader exposes four luns or four drives. However, how do I figure out the drive letters that are supported by this particular device. PCs in question can have many usb card readers. If anyone has any suggestions, I would apprecaite your help. regards, Yogesh Tag: PCI express Power management event with Vista Tag: 98042
  - 4
    - yet another networking question Hi, I have a tdi kernel client that sends udp multicast and an application that receives it. Note, that it is on the same computer. Everything works fine as long as there is a network connection in the computer. If network cable is disconnected or network connection is disabled, my TdiSendDatagram returns STATUS_HOST_UNREACHABLE. Is there a way to workaround this problem? Is there a built in loopback interface that I can use? Regards, Anatoly. Tag: PCI express Power management event with Vista Tag: 98032
  - 5
    - ComDBOpen in UMDF driver Hi, I would like to obtain a free COM port number within the context of an UMDF driver. However, calling ComDBOpen returns with ERROR_ACCESS_DENIED. Is it possible to open the COM Port Database within an UMDF driver? Must I grant special access right to the LOKAL SERVICE user under which account the driver runs? Regards, Andre Tag: PCI express Power management event with Vista Tag: 98030
  - 6
    - CR3 and Page Directory Table Hi All, I'm somewhat hesitant to post in here because most people only respond with questions that are already answered in the posting. Or they tell me "well give us more info." So here's all the info that's needed. SOMEBODY has to know this.... I'm trying to hook (globally - system-wide) all the file access functions in kernel32.dll. No, I'm not creating spyware - this is for a client in Italy who needs specific file logging; the .DLL I created relies on the host app passing a list of file specs to filter. Any-who ... I have a driver I'm using to set the hook. Problem: ALL, yes ALL, of the documentation currently on the web on how to do this is outdated and stopped working with XP. Every one of 16,248 articles on the web says "CR3 holds the base address of the page directory table." No, it doesn't. Not in any way a driver can use it. I've tried MmMapIoSpace to map the physical address (CR3 & FFFFF000) to a virtual address. This points to a table, but every other dword is 0 or close to 0 - it's NOT a page directory table; these do not have 64 bit entries. Not on a Pentium 4 with 32 bit addressing. I use the widely documented claims of "C30000000" hesitantly because they're unreliable. I read the registry key giveing C3000 as a directory base. I pass this to the driver from the user app ... but then it's hit-or-miss, that page certainly seems to be the page directory table, but a) I don't know how far I can rely on that address in the future, and b) half the time THAT is paged out. When that happens is completely random. I load CR3, disable caching, and reload CR3. Half the time that triggers a page directory table load, half the time not. If I call MmProbeAndLockPages when the directory is already loaded, it double faults claiming "you have to probe before you read this memory." Typical stuff to come out of a team environment. That call double faults the system if the page is already loaded. There is no present bit in CR3 so I can't tell if the directory is loaded. CR3 holds a base of 07100xxx which does nothing for me. I used MmMapIoSpace to convert that physical address to virtual. That gives me the pointer to the every-other-dword-is-zero (or close) table. I have loaded the GDT and looped through its descriptors, looking for any entry where 07100xxx can map into its range. Nothing exists. I'm out of options. Completely, totally out of options. Everything has failed. I am missing something because Windows is making this work and I'm not. I'm doing something very wrong or missing something I need to be doing. Can ANYBODY help????? Tag: PCI express Power management event with Vista Tag: 98019
  - 7
    - can user mode application access the kernel mode buffer ?? hello all, Is it possible for a kernel mode driver to lock down a buffer area in kernel space, mark the buffer as accessable from user mode, then pass the kernel virtual address of the base of this buffer back to the user mode program so the user mode program can directly access the buffer without going through the driver. Tag: PCI express Power management event with Vista Tag: 98010
  - 8
    - kernel allocated memory used by application Hi all how i can send the memory location which is allocated by driver. used by the application. can you tell me methods for this: 1. i want to allocates the memory in driver level. 2. application can use this memory location and fill the data and send to driver. how i can do this step: regards suli Hi Maurice, This is the same sai who reported sometime back delay caused by the pending IOCTL.I am trying to allocate memory in the kernel and map that to the user,to improve the latency caused by the pending IOCTL and the routines to call if we allcote the buffer in the user modeapp. This is what i am trying to do; proc: 1) Allocate the memory in the driver and send that to the user mode application. 2) The user mode application access the pointer and writes some entries of type ULONG. 3) Next The user mode application sends the IOCTL requestiing the driver to read the contents from the shared buffer in the ISR. 4) In the ISR I read the contents from the shared kernel memory and writes to the device register. 5) As the IOCTL request from the user is asynchronous i keep that IRP pending. 6) There is a FIFO on the device that can take only 2048 entries. 7) when i send 2048 for the first time it works excellent. 8) when send few more entries like 5000 it crashes the system. when i send 5000 entries what happens is the driver writes first 2048 entries when it is interrupted and waits for the device to generate another interrupt to write remaining half. 9) when it writes the remaining half it crashes.when i debug it found to be only when access the kernel shared memory during the second half i see the crash. Tag: PCI express Power management event with Vista Tag: 98009
  - 9
    - What are the exact definitions of "arbitrary thread context" and "nonarbitrary thread context"? The DDK documentation explains little on the two terms. I consulted Walter Oney's book, and got some tips. I post my premature understanding here and hope experts to correct my errors or give me some comments. To my understanding, 1) If thread A sends IRP_MJ_CREATE to driver X, and next, sends IRP_MJ_XXX to driver X's corresponding dispatch routine, then, the dispatch routine is being executed in a "nonarbitrary thread context". 2) If thread A sends IRP_MJ_CREATE to driver X, and next, another thread, say thread B, sends IRP_MJ_XXX to driver X's corresponding dispatch routine, then, the dispatch routine is being executed in an "arbitrary thread context". 3) For a given dispatch routine, DDK (or Microsoft) specifies whether it must be called in a "nonarbitrary thread context" or in an "arbitrary thread context" (with some exceptions, see DDK documentation : "Dispatch Routine IRQL and Thread Context") Is my understanding correct? Any comments will be helpful. Thanks. Tag: PCI express Power management event with Vista Tag: 98003
  - 10
    - How to reference a handle from a 32 bit process in a 64 bit driver I want to reference a handle from a 32 bit process using ObReferenceObjectByHandle from a 64 bit driver. How can I do that without changing the 32 bit application? The handle is sent to driver through a IOCTL request. -- Sincerely, Maruf Maniruzzaman, Software Engineer, KAZ Software Limited, Dhaka, Bangladesh. http://www.kaz.com.bd http://www.kuashaonline.com Tag: PCI express Power management event with Vista Tag: 97998
  - 11
    - DEFINE_GUID and it's use in SetupDiEnumDeviceInterfaces Hi, I embed interface guid (it is generated with uuidgen) in my driver with DEFINE_GUID(GUID_DEVINTERFACE_MYDRIVER_FILTER, 0x1d9e9eb0, 0x393a, 0x4345, 0xbb, 0x1d, 0xba, 0xf7, 0x45, 0x68, 0x62, 0xf3); /* 1d9e9eb0-393a-4345-bb1d-baf7456862f3 */ Then I try to find path to that device using info = SetupDiGetClassDevs(guid_from_above, NULL, NULL, DIGCF_PRESENT | DIGCF_DEVICEINTERFACE) Next I call SetupDiEnumDeviceInterfaces(info, NULL, guid_from_above, 0, interfaceData) Which fails (returns false) and LastError() returns ERROR_NO_MORE_ITEMS even if index is 0. When I look into .sys file with hex editor I can't find my guid anywhere. Is it somehow mangled? Could somebody point me what I am doing wrong? I use Vista x86 Checked build env to build driver and it runs on 32-bit Vista box. Thank you, Dmitry. Tag: PCI express Power management event with Vista Tag: 97981
  - 12
    - So what's this about PoRequestPowerIrp? For the time being, I'm still developing WDM drivers, and I have legacy code that issues a wait-wake by calling PoRequestPowerIrp. Prefast fussed at me for having a non-null last argument (the PIRP argument), which the WDK doc says should always be NULL. The pointer in question is in the device extension, and I InterlockedExchangePointer it with NULL when I'm about to cancel it, and I have a completion routine that also InterlockedExchangePointer's it in a way that would work with any other IRP to deal with the obvious race between cancellation and completion. So, is there something special about power IRPs that makes otherwise bulletproof code not work, so that the doc is really correct that the PIRP argument DOES have to be NULL in all cases? And, does anyone besides Prefast actually check, so that drivers will stop working if they break this rule? If the answer to either question is "yes", is there another way for a WDM driver to cancel a wait-wake, which I believe it has to do at various times? -- Walter Oney, Consulting and Training http://www.oneysoft.com Tag: PCI express Power management event with Vista Tag: 97979
  - 13
    - Limiting read/write transfer lengths for a storage device Greetings, I've created a USB mass storage device that implements the commands defined in SBC-2. For this particular device it is desirable that only a single block is read or written at a time. That is, in the READ/WRITE CDBs, the transfer length field should always be set to 1. As I read the spec, the obvious way to do this is with VPD page B0h, but this page doesn't seem to be requested by the driver. A lower storage filter driver implements some device-specific functionality. At the moment my strategy for limiting the transfer length is to intercept READ10 and WRITE10 SRBs, create a new SRB and IRP for each block requested, then complete the original IRP, but this doesn't strike me as the correct solution. I've read that miniport drivers are responsible for limiting DMA request sizes, but that doesn't seem to apply to my problem. If anybody could give me some direction on the correct way to go about this, I would be grateful. I'm new to USB, SCSI and device driver programming, so any corrections to my understanding of the issues is welcome. Regards, Brian Tag: PCI express Power management event with Vista Tag: 97968
  - 14
    - Message signaled Interupt support in 2003 Does anybody know for sure if windows 2003 supports PCI-Express MSI's I was going to use WDF to get MSI support but all the documentation I see only references Vista and later for MSI's. If not I'll have to change the pci core to use legacy ints. Tag: PCI express Power management event with Vista Tag: 97965
  - 15
    - kernel level com port I/O Hi, I'm trying to interface to a usb to serial com port at the driver (kernel mode) level. I need to open it, read, and write from it. I have looked around and haven't found any obvious sample code on how to do this at the kernel level (tons of samples at user mode). I have tried using ZwCreateFile status = ZwCreateFile(&pDeviceToOpen->hLowerDevice, FILE_READ_DATA|FILE_WRITE_DATA, &ObjectAttr, &IoStatusBlock, NULL, 0 ,0, FILE_OPEN, 0, NULL, 0) ; ) after initializing an object based on the device name obtained from the symbolic link returned from the pnp detection of the GUID_DEVINTERFACE_COMPORT interface class. This device name happens to be \Device\USBPDO-6, if it matters. From there I've tried using ZwWriteFile status = ZwWriteFile(pDeviceToOpen->hLowerDevice, 0, NULL, NULL, &IoStatusBlock, &ttt, // PUCHAR buf 1, // ULONG Length NULL, // PLARGE_INTEGER ofStartingOffsetfset NULL); with the handle returned from ZwCreateFile but that returns an invalid parameter error (c000000d). I've also tried using IoGetDeviceObjectPointer and sending IRP_MJ_WRITE down to the device object via IoAllocateIrp and IoCallDriver and their attendant setup paths. Can anyone give me some pointers and what I may be doing wrong here? I've been banging my head on this one trying to see what obvious thing I'm missing. Thanks and Regards, Jess Howe Tag: PCI express Power management event with Vista Tag: 97956
  - 16
    - Ndis filter driver question Hello! I'm programming a ndis filter driver that handles 802.3 media (Ethernet II frames). I am looking for info how ethernet frames are put into buffers. Does every single NET_BUFFER contain one frame? Or does every NET_BUFFER_LIST contain one ethernet frame (fragmented in NET_BUFFERS)? Last there is the option that the frames are not split at all. The documentation has no info on this subject (or I just haven't been able to find any) :( Thank you for your attention! Sh0 Tag: PCI express Power management event with Vista Tag: 97953
  - 17
    - MTP & composite devices in Vista Hi all, Are my preliminary discoveries correct, that if I plug in an MTP capable device into Vista, it will be automatically placed into the WPD device class and Vista will only load the MTP device driver without further caring about the HWID thus not installing additional drivers? If this is correct, can this feature be disabled or prevented from happening by the developer? Thus, how am I able to enumerate additional capabilities of a composite USB device with MTP support in Vista? Regards, Johan Paul Tag: PCI express Power management event with Vista Tag: 97945
  - 18
    - Why is Isochronous DMA MaxBufferSize only 1MB for 1394 on Vista 64bit? I am porting a 32Bit version of a 1394 (firewire) driver to Vista 64Bit. This driver worked for years wonderfully under Windows2000 and WindowsXP. I attach isochronous buffers as big as 6MB. Unfortunately in Vista64 the maximum attachable buffer size is shrinked from formerly 2GB (Vista32/XP) to 1MB. I sent the 1394 request REQUEST_GET_LOCAL_HOST_INFO + GET_HOST_DMA_CAPABILITIES and got HostDMAInformation.MaxDmaBufferSize = 0x100000 (1MB). The same call in WinXP-SP2 returns: MaxDmaBufferSize = 0x80001000 (2GB) - on the same hardware of course. As a result, the 1394 request REQUEST_ISOCH_ALLOCATE_RESOURCES fails when I try to set the nMaxBufferSize bigger than 0x100000. From the hardware point of view, it makes no sense why x64 and x86 return two different values. With the limitation of 1MB, the 32bit driver needs lots of modifications, it is a nightmare. Is this phenomen known? Is there any effort from Microsoft to change the maximum dmaBufferSize back to the -much more convenient- value of 2GB ? Any hint to solve the problem? Thank you in advance, Christoph Tag: PCI express Power management event with Vista Tag: 97943
  - 19
    - one bug in ndis6 for vista I write a miniport6 driver for my NIC for vista. But I find one bug of wakeup in ndis6. Property --> Power Management --> 'Allow this device to wake up the computer', when this option is checked , OS will send OID_PNP_ENABLE_WAKE_UP to ask my miniport driver enable NIC NDIS_PNP_WAKE_UP_MAGIC_PACKET and NDIS_PNP_WAKE_UP_PATTERN_MATCH wakeup at loading time , this is okay. But, when that option is unchecked, the OS will still send OID_PNP_ENABLE_WAKE_UP to ask my miniport driver enable NIC NDIS_PNP_WAKE_UP_PATTERN_MATCH wakeup at loading time. And OS do nothing before entering S3 sleep state. This is not according to WDK specification: OID_PNP_ENABLE_WAKE_UP As a set, the OID_PNP_ENABLE_WAKE_UP OID specifies the wake-up capabilities that a miniport driver should enable in a NIC. As a query, OID_PNP_ENABLE_WAKE_UP obtains the current wake-up capabilities that are enabled for a NIC. This topic documents OID_PNP_ENABLE_WAKE_UP for NDIS 6.0 and later versions. For NDIS 5.x information, see OID_PNP_ENABLE_WAKE_UP (NDIS 5.x). The InformationBuffer member of the NDIS_OID_REQUEST structure contains flags that can be bit-wise ORed together to enable a combination of wake-up events: NDIS_PNP_WAKE_UP_MAGIC_PACKET When set, specifies that the miniport driver should enable a NIC to signal a wake-up event on receipt of a Magic Packet. (A Magic Packet is a packet that contains 16 contiguous copies of the receiving NIC's Ethernet address.) When cleared, specifies that the miniport driver should disable the NIC from signaling such a wake-up event. NDIS_PNP_WAKE_UP_PATTERN_MATCH When set, specifies that the miniport driver should enable a NIC to signal a wake-up event on receipt of a packet that contains a pattern specified by the protocol with OID_PNP_ADD_WAKE_UP_PATTERN. When cleared, specifies that the miniport driver should disable the NIC from signaling such a wake-up event. NDIS_PNP_WAKE_UP_LINK_CHANGE Reserved. NDIS ignores this flag. A protocol driver uses the miniport adapter's wake-up capabilities in NDIS_BIND_PARAMETERS to enable the associated NIC's wake-up capabilities. A protocol driver can also query this OID to determine which wake-up capabilities are enabled for a NIC. NDIS does not immediately enable the wake-up capabilities that a protocol driver specifies. Instead, NDIS keeps tracks of the wake-up capabilities that the protocol driver enabled and, just before the miniport adapter transitions to a low-power state, NDIS sends an OID_PNP_ENABLE_WAKE_UP set request to the miniport driver to enable the appropriate wake-up events. Before the miniport adapter transitions to a low-power state (that is, before NDIS sends the miniport driver an OID_PNP_SET_POWER request), NDIS sends the miniport driver an OID_PNP_ENABLE_WAKE_UP request to enable the appropriate wake-up capabilities. The miniport driver must take the appropriate device-dependent steps to enable or disable wake-up events on the NIC. The miniport driver should clear the wake-up capabilities that NDIS set with OID_PNP_ENABLE_WAKE_UP when the system is resumed. The wake-up capabilities should not be persisted across resumes. If wake-up capabilities are enabled, NDIS explicitly sets OID_PNP_ENABLE_WAKE_UP before the miniport transitions to the low-power state. Any suggestion will be appreciated! Thanks in advance! Tag: PCI express Power management event with Vista Tag: 97942
  - 20
    - Wave Out Mix disabled in Vista Wave Out Mix disabled in Vista. How can I enable this endpoint from my driver installation application? Tag: PCI express Power management event with Vista Tag: 97940
  - 21
    - audio filter driver on Vista VS. XP Key words: filter driver, APO, virtual audio driver On XP, we can implement filter driver to filter audio streaming from or to audio devices. But on Vista, filter driver for audio device is not recommended, so how can I filter audio streaming for real audio device? I know APO(sfx/gfx) can do it, but APO can't meet all of my requirements, I need to implement it by registering a virtual audio device for processing audio data from or to real audio hardware. So the detailed question is how can my virtual audio driver get audio data from audio input device and send audio date to audio output device? waiting for your kindly guidance. Tag: PCI express Power management event with Vista Tag: 97938
  - 22
    - *Not* getting unsigned driver warning on unsigned driver install Hi folks, I'm having what is known as a "high-class problem": I am *not* getting the unsigned driver warning dialog (you know the one, the box telling you that your drivers aren't signed and bad things are going to happen etc etc) when installing unclassified USB drivers that are most assuredly not signed (these drivers don't even have a .cat file yet). This is on both W2K SP4 and XP SP2. The "System Properties/Hardware/Driver Signing/Driver Signing Options" is set to "Warn", and "Make this the system default" is set. The drivers are pre-installed via a DIFx-based application (FWIW this is Jungo WinDriver with customized INFs, and the installer is the wdreg.exe utility bundled with it). On the first plug-in of a device, the behavior is slightly different on 2K vs XP. - On 2K, the device is plugged in, and two â??Found New Hardwareâ?? â??alert boxesâ?? pop up in very quick succession in the center of the screen and disappear. These appear to be the W2K equivalent to the system tray bubbles in XP. The user is never asked to click on anything, and the device is ready for action. - On XP, the device is plugged in, you get some system tray bubbles, then the usual "Found New Hardware Wizard" pops up, and the user has to click through a few Wizard pages before the device is installed. At no time though does the "Warning! Unsigned Driver!" box show up. What's going on here? Does DIFx somehow bypass the warning box? Do other people see this? This is completely new behavior to me and I don't know what to make of it. -- Gary R. Van Sickle Tag: PCI express Power management event with Vista Tag: 97935
  - 23
    - CoNDIS 6.0 - send and receive hang Hello, We are porting a Windows XP CoNDIS miniport (MCM) driver from NDIS 5.x to NDIS 6.0 and are getting a driver hang in the send and receive code. We are porting using guidelines from the following MSDN URL: http://msdn2.microsoft.com/en-us/library/aa503536.aspx Are there any NDIS 6.0 driver samples available for send and receive operations? Any other resources or debugging tips from the experts, which can help us with debugging this driver hang? We suspect this hangs because an IO request is not getting completed, but we are unclear on the usage of the following new NDIS 6.0 APIs: NdisMCoSendNetBufferListsComplete NdisMCoIndicateReceiveNetBufferLists How do we find out which code causes the hang? Thanks in advance, VISTAwarrior Tag: PCI express Power management event with Vista Tag: 97933
  - 24
    - Device Drivers and HAL Greetings, I am interested in understanding some of the terminology and concepts in regards to device drivers. I have done some basic research and some of the things are confusing me. For instance, when I think of a driver, I think of software controlling a hardware. That is, it may contain C and/or assembly language very particular to a piece of hardware. In my understanding a driver was a software which has full ability to access a device, knows about its internal structures, buses, timings and registers etc. I was told about an example that exists called toaster that can be studied to help better understand device drivers and device driver development process for Windows OS. I have not yet looked into toaster. I wanted to read up on theory first and thats where I am really puzzled. What device are we controlling with that toaster driver? Suppose toaster controls CD-ROM device, I have no idea how Samsung makes their CD-ROM drive and how Sony makes theirs. To me a driver is fully aware of the hardware it must be controlling. That is, a driver is hardware dependent. It seems to me that is not the case. How can driver have a hypothetical device? My question is based on the fact, that I am thinking a physical device with chips with internal registers, timing issues, memory, buses etc. What made me write this post is right now I am studying HAL layer of Windows OS. It seems drivers don't access devices directly, they go through HAL. That is another puzzle. HAL can not possibily concieve a device that, say, I make. How would HAL know how to begin to interact with the device? I am sure there are standards that exists to adhere to making,say, PC device that uses PCI. Suppose my device, a card that sits in a PCI slot, has 32MB of memory on it, and of course myraid of chips on it. It is a brand new device that is custom made and adheres to all the PC and PCI hardware standards. How would HAL know how to control and utilize this device if a device driver can not directly access it? Thanks Tag: PCI express Power management event with Vista Tag: 97912
  - 25
    - How can i get Extra BOF's and TAT info in NDIS6.0 Hi, i am developing IrDA miniport driver in Vista using NDIS6.0. The Turnaround Time and Extra BOF's of the other tranceiver is sent by protocol driver from above, through the MediaSpecificInfo as per NDIS5.0. In the sample from DDK for NDIS5.0 is given as, PNDIS_IRDA_PACKET_INFO GetPacketInfo(PNDIS_PACKET packet) { MEDIA_SPECIFIC_INFORMATION *mediaInfo; UINT size; NDIS_GET_PACKET_MEDIA_SPECIFIC_INFO(packet, &mediaInfo, &size); return (PNDIS_IRDA_PACKET_INFO)mediaInfo->ClassInformation; } where as the returned PNDIS_IRDA_PACKET_INFO, which is inturn mediaInfo->ClassInformation has the ExtraBOF and TAT info. Now, i want to get the same ExtraBOF's and TAT info in NDIS6.0. i have coded something like the below, PNDIS_IRDA_PACKET_INFO GetPacketInfo(PNET_BUFFER_LIST pNetBufferList) { NDIS_NET_BUFFER_LIST_MEDIA_SPECIFIC_INFO *mediaInfo; mediaInfo = NET_BUFFER_LIST_INFO(pNetBufferList ,MediaSpecificInformation); return (PNDIS_IRDA_PACKET_INFO)mediaInfo->ClassInformation; } please correct me, if i am wrong. Now, the problem for me here is the MediaSpecificInformation is always NULL. please help me in getting ExtraBOF's and TAT info in NDIS6.0 Thanks and Regards, Neo Tag: PCI express Power management event with Vista Tag: 97909

Hi list,

I'm developing a driver for a PCI express card, but I have an issue
with remote wakeup.

Althought the option "Allow this device to wake the computer" is set,
and the device is still
switched on while the system is sleeping, the device don't wake the
system.

I checked with a protocol analyser, the device send Power Management
Events, but system
don't wake.

The only documents I found on the internet specifies Vista handle PME,
but don't specify how !

Does PME handling need some specific registry entries, as MSI ?
Does someone activate PCI express PME handling ?
Any idea, or hint ?

Thanks
--
Benedict

Top

Re: PCI express Power management event with Vista by Eliyas

Eliyas
Wed Aug 22 22:47:22 CDT 2007

What type of device is this? Are you sending wait-wake irp to the bus?

--
- This posting is provided "AS IS" with no warranties, and confers no
rights.

Top

Re: PCI express Power management event with Vista by Benoit

Benoit
Thu Aug 23 02:15:08 CDT 2007

Hi,

Thanks for reply

> What type of device is this?

This is a TV Tuner device

> Are you sending wait-wake irp to the bus?

Of course.
In fact this driver is based on a PCI driver for the same kind TV
Tuner, and remote wake up work perfectly well with this initial
driver.

I read in microsoft document "CPA070_WH06.ppt" (page 8) : "By default,
Windows Vista starts in PCI compatibility mode. No PCI Express
features assumed or enabled".

So, may be, it is only an activation issue, do you know how to enable
PCI Express features in Vista ?

Regards
--
Benedict

Top

Re: PCI express Power management event with Vista by Harison213

Harison213
Thu Aug 23 03:56:04 CDT 2007

Wake-up mechanism from a driver point of view shouldn't be different and if
the driver used to work on a similar PCI device, it should work on the new
device out of the box.

If you see a PME event has been generated, system should wake-up regardless
of the OS/driver as at this stage all what's happening is in the system
board/hardware context. Check the bus power management capabilities to see if
it supports wakes from required states. Also check/upgrade BIOS and test this
on as many systems as you have available.

In my experience many PCI Express systems today aren't fully compliant with
PCIE spec specially when it comes to power management.

Harison

--
There are 10 kinds of people in the world: those who understand binary, and
those who don''t!

Top