another bda question

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
    - Is AttachedDevice an incorrect paramenter name in the function prototype of IoAttachDevice? Hi all, The function prototype of IoAttachDevice is declared as follows in the DDK documentation. /*********************************/ NTSTATUS IoAttachDevice( IN PDEVICE_OBJECT SourceDevice, IN PUNICODE_STRING TargetDevice, OUT PDEVICE_OBJECT *AttachedDevice ); Parameters SourceDevice Pointer to the caller-created device object. TargetDevice Pointer to a buffer containing the name of the device object to which the specified SourceDevice is to be attached. AttachedDevice Pointer to caller-allocated storage for a pointer. On return, contains a pointer to the target device object if the attachment succeeds. /*********************************/ According to the statement above, AttachedDevice should point to a lower device, i.e the target device. However, in English, if an upper device is attached to a lower device, then the upper device, rather than the lower device, should be called "attached device". So, the last paramenter should be named DeviceAttachedTo or something like this. I'm not a native English speaker. I eagerly hope those who speak English can give me some tips. Tag: another bda question Tag: 98274
  - 2
    - Using QueryInterface inside COM Hello I am working on a COM project in which i use Interface Inheritance. The IDL file looks like this, interface IEarthInterface : IUnknown {}; interface IOceanInterface : IEarthInterface {}; interface IPacificInterface : IOceanInterface {}; interface IAntarticInterface : IOceanInterface {}; interface IDataInterface : IUnknown {}; interface IFindInterface : IDataInterface { HRESULT GetOceanTypeInterface(IOceanInterface** pOceanInterface); }; From inside IFindInterface i need to figure out which Ocean is currently attached and then attach or typecast it was IOceanInterface and send it back to client. All i wanted to know is how to get a Interface pointer from inside another Interface. ie, can i call CoCreateInstance or QueryInterface from inside IFindInterface and get the Interface Pointer to IPacificInterface or IAntarticInterface. I been already told that CoCreateInstance will not work in this case. Any idea how to implement this? Thanks in advance. Tag: another bda question Tag: 98261
  - 3
    - Why self signed certificates gives error ? Hi All, While loading a driver on Vista (32 bit) error message pops up "Windows can't verify publisher of this software". Where as our driver is signed. Certification path is : Verisign Class3 Public primary CA Verisign class 3 code signing 2004 CA ABC technology I have copied the certificates from ABC Technology to Trusted Publisher and Verisign Class 3 Code Signing 200CA to Trusted Root Certification Authority under certificate manager. While Checking it under "Device Manager" it shows name of digital signer as "ABC Technology" and under "Driver Detail" tab it shows "Digital Signer : not digitally singed" . Did the verification of driver and catalog using "Signtool utility" SignTool verify /kp /c <(nameofcat).cat> <.inf/.sys> and it shows result "succeed" While checking log under Setupapi.dev.log and it shows errror "Verifying file against specific (valid) catalog failed !(0x800b0109)" "Error (0x800b0109): A certificate chain processed but terminated in root certificate which is not trusted by trust providers" File has not been modified after taking signature. Can I get pointers regarding same that where I m getting wrong ? -- Thanks, Nash Tag: another bda question Tag: 98259
  - 4
    - Getting data from COM Object in Driver Is it possible to reliably use com calls to get data? -- Sincerely, Maruf Maniruzzaman, Software Engineer, KAZ Software Limited, Dhaka, Bangladesh. http://www.kaz.com.bd http://www.kuashaonline.com Tag: another bda question Tag: 98248
  - 5
    - Windows 2000 and BusTypeiScsi Hi all, I am using iSCSI HBA on Windows 2000 SP4 (with Rollup update1). I want to use MPIO feature of iScsi Initiator services but unable to do so. I can login to target and see the Luns in the Device Manager but mpdev does not seem to claim these Luns. According to Microsoft iSCSI Software Initiator User's Guide 2.x, For an HBA to work properly with Microsoft MPIO, HKLM\SYSTEM\CurrentControlSet\Services\hbadevicedriver\Parameters\BusType key should be set to BusTypeiScsi(0x09) so that the Microsoft iSCSI DSM can claim the device. I do see this registry key set but it seems SCSIPORT driver is returning BusTypeScsi for these Luns. The knowledge base article 264203 describes IOCTL_STORAGE_QUERY_PROPERTY can be used to get the adapter and device properties. When used on my system this IOCTL returned bus type as 1(BusTypeScsi) for Adapter and Device. This is a default bustype returned by SCSIPORT. Can some one help me to get iSCSI HBA working with MPIO on Windows 2000? Thanks. Tag: another bda question Tag: 98242
  - 6
    - WPD driver error 10 after reboot Hi all, I am working on a device driver which is based on the WpdWudfSampleDriver (DDK, 6000). Everything is great (driver works as expected and installs/uninstalls, WMP11 recognizes it, etc) until I reboot the PC. After reboot, the driver appears with a yellow exclamation mark icon in the device manager. Properties dialog indicates that "Device cannot start" with error 10. This happens on both Vista 32bit and XP+SP2+WMP11. I tried to compile in different build environments (XP or Vista), also tried the tweaks from WPD team blog about co-installers, nothing helped so far. In addition to that, I realized that even simplest WPD driver example from the DDK (WpdHelloWorldDriver) also works same way (also shows error 10 after PC reboots). Can it be related to the fact that the driver is actually a root-enumerated device (like original WpdWudfSampleDriver) and is not assigned to any USB VID/PID? Or a missing .cat file? missing signature, maybe? I have checked last 10 pages of the newsgroup and did a search, but could not find anything relevant. Did anyone experience same problem? Please, give me some advice on what else I could try/check. Or please, let me know where else I could post this question... thanks and best regards, Sergey Tag: another bda question Tag: 98240
  - 7
    - Driver signing question Hey All, Quick question about driver signing. I hope this is the correct forum for my question. I have a device driver for an external PNP device. I am currently signing it and will be shipping it out in my next software release targeting windows vista. I understand that signatures do expire. I'm uncertain if the signature on my signed drivers expire (they do expire, don't they? Where can I find the expiration date?). Furthermore, what will happen when the drivers expire? The drivers, I assume, will still work with the device after the drivers expire, correct? What happens when a user tries to install my device drivers after they expire? Do they just get a notice that the drivers have expired? Thanks in advance, Matt Tag: another bda question Tag: 98238
  - 8
    - NMI: Parity check / Memory parity error during debugging Hello everyone, I am a newbie to driver development. Currently, I am working on a PCI driver on Windows XP platform. I have a target that runs my driver and a host on which Windbg runs. The problem I have is as follows: I want to make sure that the operations that are carried out by my ISR routine are correct. Thus, I set a breakpoint in the ISR. The routine is called normally and the breakpoint is reached. However, when I want to access fields of one of my volatile structs in the watch window, the target machine bugchecks giving out the "NMI: Parity check / Memory parity error" error. When the breakpoint is removed, the ISR runs normally. I searched the group posts and the web for possible reasons but could not come across anything like this. Many sites say that ISR should not be debugged "the usual way" like I try to do.Am I doing something wrong regarding this issue? What could be other possible reason for this behaviour? Many thanks in advance! Tag: another bda question Tag: 98223
  - 9
    - GeneralAttributes & RegistrationAttributes for IrDA Miniport Driver. Hi, In the Due course of Developement of Miniport IrDA Driver the Registration and General Attributues used are given as follows, can anyone comment on this, if it is correct or not ??? RegistrationAttributes.AttributeFlags = NDIS_MINIPORT_ATTRIBUTES_NDIS_WDM; RegistrationAttributes.InterfaceType = NdisInterfaceInternal; GeneralAttributes.MediaType = NdisMediumIrda; GeneralAttributes.MediaConnectState = MediaConnectStateConnected; GeneralAttributes.MediaDuplexState = MediaDuplexStateHalf; GeneralAttributes.MacOptions = NDIS_MAC_OPTION_COPY_LOOKAHEAD_DATA | NDIS_MAC_OPTION_TRANSFERS_NOT_PEND | NDIS_MAC_OPTION_NO_LOOPBACK; GeneralAttributes.PhysicalMediumType = NdisPhysicalMediumIrda; GeneralAttributes.RecvScaleCapabilities = NULL; GeneralAttributes.AccessType = NET_IF_ACCESS_POINT_TO_POINT; GeneralAttributes.DirectionType = NET_IF_DIRECTION_SENDRECEIVE; GeneralAttributes.ConnectionType = NET_IF_CONNECTION_DEDICATED; GeneralAttributes.IfType = IF_TYPE_OTHER; GeneralAttributes.IfConnectorPresent = TRUE; GeneralAttributes.SupportedStatistics = NDIS_STATISTICS_XMIT_OK_SUPPORTED | NDIS_STATISTICS_RCV_OK_SUPPORTED | NDIS_STATISTICS_XMIT_ERROR_SUPPORTED | NDIS_STATISTICS_RCV_ERROR_SUPPORTED | NDIS_STATISTICS_RCV_CRC_ERROR_SUPPORTED | NDIS_STATISTICS_RCV_NO_BUFFER_SUPPORTED | NDIS_STATISTICS_TRANSMIT_QUEUE_LENGTH_SUPPORTED; Thanks and Regards, Neo Tag: another bda question Tag: 98217
  - 10
    - Personal: Wdm driver ioCalling Wdf driver looking for STATUS_SUCCE if the WDF driver [callee] does WDFCompleteWithInfo(SUCCESS, . .) why does WDM driver [caller] get STATUS_PENDING ? ? ? tom Tag: another bda question Tag: 98204
  - 11
    - Fast I/O Functions not being called I'm developing a file system filter driver - same base functionality as FileSpy, but without all the useless bloat, complication, inefficiency and fluff. I have set up my fast I/O table in Driver Entry ... allocated it, checked and double checked every last field (including size ... it's 0x70), assigned it by DriverObject->FastIoDispatch = fastIoDispatch; I broke into KD and double checked every address. No crashes are occurring, no bugs are occurring. DriverObject exits with its FastIoDispatch field assigned to my very valid table. But no fast I/O functions ever get called. When I open non-Microsoft programs, all the disk I/O passes through my filter driver. The very first line of every fast I/O dispatch is a DbgPrint statement. I even tried DbgBreakPoint and a straight inline assembler _asm int 3. They're never called. The standard dispatch routines are being called just fine. Any program I run that comes from Microsoft leaves my driver dead in the water. There is no activity. All other programs run all disk I/O through my driver - when the disk is hit. I understand the difference; when fast I/O is used and why, but I don't understand why such a simple process is not working. Assuming nothing is wrong with my code, it must be something I'm leaving out (although this process is not difficult; how many things are there to leave out?). So I must be doing something stupid to disable these calls. Conceptually, are there any ideas? Tag: another bda question Tag: 98201
  - 12
    - Enable/Disable iSCSI HBA on Windows 2000 Hi, I have a issue with enable/disable of the iSCSI HBA we are developing. Our HBA is a mass storage adapter and the SCSIPort miniport driver loads during boot. After the OS comes up, we can perform all operations using Microsoft iSCSI Initiator and everything's fine. The problem occurs when I disable the adapter and enable it again from DeviceManager. After this operation, though the driver successfully unloads and reloads, our HBA fails to get listed under iSCSI WMI. iscsicli listinitiators does not report our HBA. Enabling the debugprints for WMI discovery module, I see errors - iscsidsc: Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} has arrived or remove failed iscsidsc: ArrivalTimer 30 for 00080C58 \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} Flags 0x0 iscsidsc: Getting InstanceName for Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} iscsidsc: Error 4201 finding instance name for \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} iscsidsc: Error 4201, try 0 Didn't get InstanceName for Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} This continues until the ArrivaTimer counts down upto 0 and the device never gets added. The same binary which shows this problem on Windows 2000 works fine on Windows 2003. iscsidsc: Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} has arrived or remove failed iscsidsc: ArrivalTimer 30 for 0008DE40 \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} Flags 0x0 iscsidsc: Getting InstanceName for Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} iscsidsc: Error 4201 finding instance name for \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} iscsidsc: Error 4201, try 0 Didn't get InstanceName for Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} iscsidsc: ArrivalTimer 29 for 0008DE40 \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} Flags 0x0 iscsidsc: Getting InstanceName for Interface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} iscsidsc: PnpDeviceInterface \\?\PCI#VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00#4&3b9abcb&0&0008#{2accfe60-c130-11d2-b082-00a0c91efb8b} is for instance name PCI\VEN_xxxx&DEV_xxxx&SUBSYS_xxxxxxxx&REV_00\4&3b9abcb&0&0008_0 What interface name is it missing on Windows 2000?? Any help or suggestions? Regards, Prabal Tag: another bda question Tag: 98198
  - 13
    - macro for sources file What is the general way of setting up path for include files in SOURCES. I cannot use relative path because my workspace is in different drive than the WDK installation. My include directory is C:\winddk\6000\inc\ddk. I want some macro to define WDK directory c:\winddk\6000. I want a macro that will work even if new version come up like c:\winddk\7000. I didnot find anything like ddk-root-dir or base-directory. Tag: another bda question Tag: 98188
  - 14
    - NewB question regarding filter drivers Hello driver developers, I am *VERY* new to driver development. As a matter of fact, I do driver installs mostly and now am beginning to learn about developing drivers. Here is my question: We have a filter driver (class filter driver) that should be applied to all Hard Disk Controllers (HDC). The end result should be that all messages to hard disk and optical media should be intercepted by the filter driver. This used to work fine, until the hardware on the system that I am installing this driver on has changed (OS has changed to Vista as well). Now the system uses SATA with AHCI. I have no problem installing the filter on the hard disk, but the filter does not get applied to the optical media for some odd reason. Is it possible to have a filter driver written for devices connected via SATA? On the side note, I am just wondering what creates the following registry key(s) and writes values under them - is it the driver itself or the PNP manager? HKLM\SYSTEM\CurrentControlSet\Services\<DriverName>\Enum. Thank you so much, Natalia Tag: another bda question Tag: 98185
  - 15
    - 1394 device driver Hi, the sample provided in the \src\kmdf\1394 subfolder missed the implementation for gathering the device informations (t1394_GetConfigurationInformation in 1394api.c). Can someone explain what to do here!? The goal is to have a driver that stores the CSR_offset somewhere (in the DeviceExtension), and that I have a function to Read and Write registers of my device. Later receiving iso-chronous transfer to a file would be fine. additional some pointers fro 1394 device drivers would be fine - thank you in advance, thomas Tag: another bda question Tag: 98184
  - 16
    - how to get the top object in the device object's stack Hi all, device stack is as follows (from up to bottom): 1. upper filter dirver 2. usb video class driver 3. lower fitler driver 4. usbccgp driver I tried to get the top object in the device object's stack in lower fitler driver but failed and the return devExt->TopDevice = 0x00. I will appriciate if you provide some suggestions? //===================================== Below is the code in AddDevice() function. #define DEVICE_NAME L"\\Device\\lowUVCFilter" RtlInitUnicodeString(&deviceName, DEVICE_NAME ); status = IoCreateDevice(Driver, sizeof(USBCAMD_DEVICE_EXTENSION), &deviceName, FILE_DEVICE_UNKNOWN, 0, FALSE, &device ); if (!NT_SUCCESS(status)) { return (status); } RtlZeroMemory(device->DeviceExtension, sizeof(USBCAMD_DEVICE_EXTENSION)); devExt = (PDEVICE_EXTENSION) device->DeviceExtension; devExt->TopOfStack = IoAttachDeviceToDeviceStack(device, PDO); status = IoGetDeviceObjectPointer( &deviceName, FILE_ALL_ACCESS, &FileObject, &devExt->TopDevice ); Tag: another bda question Tag: 98183
  - 17
    - Device drivers will not install with proper INF with correct VID/P We are trying install an x-ray sensor. The drivers install fine on several different Windows XP Pro machines, but on the one where we need to install it, Windows doesn't even recognize the inf as containing information on the device. The XP Pro machine in question is primarily used for software development and has had a ton of drivers installed on it previously. I've tried placing the exact INF into C:\Windows\INF and confirmed that no other INF contains that hardware's VID/PID. I've tried deleting the INFCACHE.1 files in every directory on the computer, so that Windows has to recreate the inf cache, including our INF from C:\Windows\INF. I've confirmed that the new INFCACHE.1 contains our INF's filename. Windows even created the PNF for that INF. I've also checked in the setupapi.log in C:\Windows\, which shows (in verbose mode) that it is searching for the VID/PID through all the INFs in C:\Windows\INF: #-019 Searching for hardware ID(s): usb\vid_0a40&pid_0101&rev_0264,usb\vid_0a40&pid_0101 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff #-019 Searching for hardware ID(s): usb\vid_0a40&pid_0101&rev_0264,usb\vid_0a40&pid_0101 #-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff It mentions our INF in the list of INFs, but it just skips over it. It can't find any supported driver, so it just installs a null driver: #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device. #W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device. #I060 Set selected driver. #-166 Device install function: DIF_INSTALLDEVICE. #I125 Installing NULL driver for "USB\VID_0A40&PID_0101\6&27FE8D50&0&3". #I121 Device install of "USB\VID_0A40&PID_0101\6&27FE8D50&0&3" finished successfully. Throughout all of this, I've repeatedly deleted any references to the VID/PID from the registry, in between each test. We even got on the phone with a developer for the company who makes the sensor/drivers, and went through all their troubleshooting. In the end they had no clue what was wrong. Any ideas? Tag: another bda question Tag: 98182
  - 18
    - WindowsXPe Serial Port (Comport) timing issue Hello all, I have a WindowsXPe system that I am currently working on, where the serial port has a jitter of approximately 50ms. I'd like to be able to get the jitter down to less than 10ms; but I suspect that this may not be possible using WindowsXPe. The delay is not important; only the jitter. The language used is C#. Is there anyone out there that can confirm my suspicions? The function call is " WriteFile(hPort, _tosend, (uint)writeCount, out sent, ptrUWO) ", which as far as I can see it is a funtion in kernel32.dll. My thanks in advance. Tag: another bda question Tag: 98179
  - 19
    - Trouble printing to LPT1 using overlapped I/O when LPT1 is used Here is my situation: 1. When we perform overlapped I/O on the LPT1 device on a computer with a Generic/Text only printer driver installed on LPT1, characters sent to a non-plug-and-play printer attached to that port appear to be getting dropped intermittently. 2. The problem appears to go away if we go into Device Manager and change the â??Filter Resource Methodâ?? setting on the printer port to â??Use any interrupt assigned to the portâ??, but only until the next reboot. After a reboot, if we switch the Filter Resource Method setting back to â??Never use an interruptâ?? then switch it again to â??Use any interrupt assigned to the portâ??, we donâ??t lose characters â?? again until a reboot. 3. If we remove the Generic/Text only printer driver, or map it to a different LPT port, the characters are no longer dropped. If anyone has any advice / ideas, they would be greatly appreciated. Thanks, Todd Tag: another bda question Tag: 98175
  - 20
    - System Memory Hello, I have come across an interesting issue. I boot Windows Server 2003 with /maxmem switch set to 1500 inside boot.ini file. This sets the limit on OS ability to use amount of memory available. So system reports only ~1.5Gig or 1500MB of memory under various tools/ programs. But yesterday, I needed to find out the actual physical memory present in the system. It is 16GB. Since OS sees only 1.5G, it reports 1.5Gig. Is there a way to find out the actual memory size without having to reboot and/or go into BIOS to look at how much memory a system truely has? Thanks for help. Tag: another bda question Tag: 98174
  - 21
    - Retrieve disk partitions (volumes) from Disk DevicePath I have trouble finding a way to retrieve/enumerate the volumes of Disk by using the DevicePath of the disk. The DevicePath is found by enumerating the GUID_DEVINTERFACE_DISK and querying SetupDiGetDeviceInterfaceDetail. Thanks for the help. Tag: another bda question Tag: 98172
  - 22
    - problem in porting 32 bit application in x64... hi... i m using an 32 bit allication to load a driver ...but when i m trying this application in X64,its failing at SetupDiCallClassInstaller(DIF_REGISTERDEVICE, DeviceInfoSet, &DeviceInfoData) with error code e0000235 can any body plz tell me y its happening so???? Regards mani Tag: another bda question Tag: 98170
  - 23
    - Event tracing in display miniport - newbie question I need to implement tracing in a display miniport driver. The msdn page for "WPP Software Tracing" states that WPP tracing is not available for certain types of miniport drivers, and : "To determine whether a particular driver type is supported, add basic WPP macros to the driver, such as WPP_INIT_TRACING and WPP_CLEANUP. If the code does not compile because the types that are used are not defined, ETW and WPP cannot support the driver type." When I did this, I found out that my display miniport driver did not compile with WPP_INIT_TRACING. I wish ETW would have worked for me .. Now that it doesn't, what are the other options for me to trace events of interest to log files? Is there a way to do some kind of printf's ? I really need to get this working as soon as possible. Please help! Tag: another bda question Tag: 98161
  - 24
    - PCI express Power management event with Vista 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 Tag: another bda question Tag: 98157
  - 25
    - 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: another bda question Tag: 98156
- Next
  - 1
    - 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: another bda question Tag: 98155
  - 2
    - 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: another bda question Tag: 98153
  - 3
    - 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: another bda question Tag: 98143
  - 4
    - 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: another bda question Tag: 98142
  - 5
    - 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: another bda question Tag: 98141
  - 6
    - 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: another bda question Tag: 98132
  - 7
    - 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: another bda question Tag: 98129
  - 8
    - 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: another bda question Tag: 98127
  - 9
    - 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: another bda question Tag: 98126
  - 10
    - 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: another bda question Tag: 98125
  - 11
    - 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: another bda question Tag: 98122
  - 12
    - 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: another bda question Tag: 98121
  - 13
    - 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: another bda question Tag: 98117
  - 14
    - 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: another bda question Tag: 98114
  - 15
    - 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: another bda question Tag: 98106
  - 16
    - 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: another bda question Tag: 98105
  - 17
    - 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: another bda question Tag: 98104
  - 18
    - 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: another bda question Tag: 98103
  - 19
    - 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: another bda question Tag: 98099
  - 20
    - 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: another bda question Tag: 98097
  - 21
    - 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: another bda question Tag: 98083
  - 22
    - 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: another bda question Tag: 98082
  - 23
    - 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: another bda question Tag: 98078
  - 24
    - 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: another bda question Tag: 98070
  - 25
    - 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: another bda question Tag: 98059

Hi,

I have implemented KSPROPSETID_BdaTableSection property set on both nodes of
my tuner filter, but the handlers are never get called. Under what
conditions this property is set?

Thanks,
Anatoly.

Top