reading ndis data through WMI

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
    - Windows XP (SP 2) and USB 2 problem Hello I have just installed a 4 port USB 2 card in my computer. The problem is that when I connected my digital camera, there was a message telling me that the connection would be faster if I had USB 2 Another telltale sign that sth is wrong is that films played on my external drive block (presumably cos the info can't arrive quicly enough) So why doesn't XP recognise a USB 2 card? Anyway, I tried to download a USB 2 driver for Windows and found the Intel Desktop Driver for XP However, on a manual install, XP refuses saying that a more suitable driver is already installed. In system, this drivers seems to be a Microsoft Driver version 5. 1 2600 released 01 June 2002 Is this a USB 2 driver? Hope sm out there can help me. Thanks in advance Dave Neve Tag: reading ndis data through WMI Tag: 98308
  - 2
    - IWiaItemExtras::Escape and VendorReadData? Greetings, I am trying to work with WIA, and I have found the IWiaItemExtras::Escape function. Which can be used to interact with vendor specific commands. But while I use the command I can get the 1st letter specified from the command, but how do I get the acutal data from VendorReadData? It always has 1 byte of data, and I am not sure where to get the output buffer. For example: PTP_VENDOR_DATA_OUT* pDataOut; HRESULT hr = spExtraProps->Escape(ESCAPE_PTP_VENDOR_COMMAND, (BYTE *) pDataIn, dwDataInSize, (BYTE *) pDataOut, dwDataOutSize, &dwActualDataOutSize); When I access the "pData->VendorReadData" it is always the byte[1] size, so I am not sure how to get the actual data. Thanks for any suggestions! Tag: reading ndis data through WMI Tag: 98306
  - 3
    - Get PID/VID from symbolic name? Hello, I would like to retrieve the PID and VID of a mass storage device from its symbolic name. Symbolic name comes from the IoRegisterPlugPlayNotification API indicating the GUID of a disk interface. I guess that there is som eway to find this, but I did not find one. Thanks, Roger Tag: reading ndis data through WMI Tag: 98302
  - 4
    - HID mini port over i8042prt PS2 stack? I'd like to report my PS2 interface device to system as a HID class device. That means I'd like to ask i8042prt to be my port driver, I know there is a moufilter sample in the DDK, well it report itself as a mouse class instead of HID class, and it is a upper filter for the i8042prt. Is it possible to create a HID driver which talked to i8042prt and report itself as a HID class device? Any hint would be apprecited. -chueh888 Tag: reading ndis data through WMI Tag: 98293
  - 5
    - How to hide system error messages. Hi, I am writing a file system minifilter driver. When I fail the create file operation from preoperation callback routine, a windows error message pops up saying "file is not a valid win32 application". and it restricts file from opening successfully. But I want that no popup should be displayed on successfully blocking a file. How can I hide this system popup? Can anybody help me? Thanks in advance. - Vikas sangani Tag: reading ndis data through WMI Tag: 98286
  - 6
    - Sharing handles between user and kernel mode in X64 I found a lot of problems working with handle. I am trying to duplicate a thread handle from user mode that is created in kernel mode. It is not working. Where do I get information about this? -- Sincerely, Maruf Maniruzzaman, Software Engineer, KAZ Software Limited, Dhaka, Bangladesh. http://www.kaz.com.bd http://www.kuashaonline.com Tag: reading ndis data through WMI Tag: 98285
  - 7
    - Why and how is the module name of ntoskrnl.exe displayed as "nt" rather than "ntoskrnl"? Hi experts, I find a weird problem with the WinDBG command 'lm n t': kd> lm n t start end module name 7c920000 7c9b4000 ntdll ntdll.dll Tue Aug 17 07:38:36 2004 (4121457C) 804d8000 806ec600 nt ntoskrnl.exe Wed Aug 04 14:19:48 2004 (41108004) 806ed000 80700d80 hal halacpi.dll Wed Aug 04 13:59:04 2004 (41107B28) bf800000 bf9c0200 win32k win32k.sys Wed Aug 04 14:17:30 2004 (41107F7A) bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 14:00:51 2004 (41107B93) ..... All of the module names except 'nt' are their image name without extention. Why? I also wonder how the debugger determines the module name of a given kernel module? Any help will be highly appreciated. Thanks in advance. Tag: reading ndis data through WMI Tag: 98282
  - 8
    - binplace doesn't seem to instantiate post build I have enabled binplace from setenv and specified a location as directed in the documentation. However, it does not seem to work. can someone confirm the steps needed to make this fire correctly? paul. Tag: reading ndis data through WMI Tag: 98279
  - 9
    - another bda question 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. Tag: reading ndis data through WMI Tag: 98275
  - 10
    - 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: reading ndis data through WMI Tag: 98274
  - 11
    - 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: reading ndis data through WMI Tag: 98261
  - 12
    - 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: reading ndis data through WMI Tag: 98259
  - 13
    - 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: reading ndis data through WMI Tag: 98248
  - 14
    - 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: reading ndis data through WMI Tag: 98242
  - 15
    - 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: reading ndis data through WMI Tag: 98240
  - 16
    - 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: reading ndis data through WMI Tag: 98238
  - 17
    - 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: reading ndis data through WMI Tag: 98223
  - 18
    - 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: reading ndis data through WMI Tag: 98217
  - 19
    - 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: reading ndis data through WMI Tag: 98204
  - 20
    - 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: reading ndis data through WMI Tag: 98201
  - 21
    - 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: reading ndis data through WMI Tag: 98198
  - 22
    - 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: reading ndis data through WMI Tag: 98188
  - 23
    - 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: reading ndis data through WMI Tag: 98185
  - 24
    - 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: reading ndis data through WMI Tag: 98184
  - 25
    - 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: reading ndis data through WMI Tag: 98183
- Next
  - 1
    - 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: reading ndis data through WMI Tag: 98182
  - 2
    - 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: reading ndis data through WMI Tag: 98179
  - 3
    - 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: reading ndis data through WMI Tag: 98175
  - 4
    - 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: reading ndis data through WMI Tag: 98174
  - 5
    - 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: reading ndis data through WMI Tag: 98172
  - 6
    - 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: reading ndis data through WMI Tag: 98170
  - 7
    - 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: reading ndis data through WMI Tag: 98161
  - 8
    - 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: reading ndis data through WMI Tag: 98157
  - 9
    - 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: reading ndis data through WMI Tag: 98156
  - 10
    - 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: reading ndis data through WMI Tag: 98155
  - 11
    - 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: reading ndis data through WMI Tag: 98153
  - 12
    - 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: reading ndis data through WMI Tag: 98143
  - 13
    - 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: reading ndis data through WMI Tag: 98142
  - 14
    - 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: reading ndis data through WMI Tag: 98141
  - 15
    - 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: reading ndis data through WMI Tag: 98132
  - 16
    - 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: reading ndis data through WMI Tag: 98129
  - 17
    - 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: reading ndis data through WMI Tag: 98127
  - 18
    - 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: reading ndis data through WMI Tag: 98126
  - 19
    - 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: reading ndis data through WMI Tag: 98125
  - 20
    - 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: reading ndis data through WMI Tag: 98122
  - 21
    - 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: reading ndis data through WMI Tag: 98121
  - 22
    - 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: reading ndis data through WMI Tag: 98117
  - 23
    - 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: reading ndis data through WMI Tag: 98114
  - 24
    - 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: reading ndis data through WMI Tag: 98106
  - 25
    - 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: reading ndis data through WMI Tag: 98105

Hi ,

Does anybody know how to get the "Interrupt Moderation" of the network
adapter using WMI method.
DDK doc says that , user can use GUID_NDIS_GEN_INTERRUPT_MODERATION
method to obtain the information. Is any sample code , how to do it ?

Thanks

Top