Windows driver debugging using 1394

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
    - WinUsb_Initialize failing with ERROR_BAD_DEVICE Hi. I've got a driver based on the FX2 sample. When plugging in the hardware, the my driver starts loading and wudfhost is running. I've used the debugger to break into it and see my driver calling IWDFUsbTargetFactory::CreateUsbTargetDevice. That's failing with ERROR_BAD_DEVICE. According to the docs, this would be an error code returned by WinUSB_Initialize. The device name is \\.\UMDFCtrlDev-3e5e32b1-51b0-11dd-813d-0010dc4ece8d from a previous call to IWDFDevice::RetrieveDeviceName. I've even tried taking the FX2 driver source as is and just modifiying the vendor ID and PID to match my hardware, realizing that it would fail later in the process after WinUSB initialized. The result is the same. Any guesses as to what I might have wrong? Thanks, Steve Tag: Windows driver debugging using 1394 Tag: 107690
  - 2
    - Detect if a file is already open. How do I detect if I file is already open? How do I detect the number of File_objects that are referencing a given file context? Thanks Larry Tag: Windows driver debugging using 1394 Tag: 107689
  - 3
    - How to get enumerator's DO (due to possible system bug)? Hi. Is there any way to get the device object of the bus driver whoâ??s created the PDO to which our device is attached? To be precise, I have a legacy PCI device which works more reliably with old applications if itâ??s been assigned legacy I/O addresses (i.e. 12-bit ISA ports below 0x1000). To achieve this, I use the PCI bridge subtractive-decode: add extra resource lists with desired resources to the resource requirements list and then rely on PnP Manager to assign one if available, or just use boot resources in case of a positive-only bridge or if resources arenâ??t available. However, on one particular system, Iâ??ve hit a problem where although the bridge does not support subtractive-decode (based on â??How Windows Identifies and Supports Bridge Typesâ?? section of â??Supporting Subtractive PCI-to-PCI Bridges in Windowsâ??), PnP manager still sends me resources which are only available for a subtractive-decode bridge. This apparently ends up in a crash and possibly is a bug in PnP/PCI driver(?). As a workaround, Iâ??m trying to get the device object of the underlying PCI bridge (which is on a different stack) and use it to read the PCI config space of the bridge and verify if the programming interface (in class code) is 01. How could this be done? Are there any other ways of achieving this? Thanks, DaveH Tag: Windows driver debugging using 1394 Tag: 107683
  - 4
    - ANN: user- and kernel mode unit testing framework cfix 1.1 released I am pleased to announce that a new release of cfix is now available on http://cfix.sourceforge.net/. cfix is an xUnit testing framework for C and (unmanaged) C++. Unlike other frameworks, cfix has been specially tailored for Windows development. In addition to user mode unit tests, cfix 1.1 introduces the ability to author NT kernel mode unit tests. For more information please refer to my blog post at http://jpassing.wordpress.com/?p=73 Tutorials are available on http://cfix.sourceforge.net/doc/TutorialUserVs.html (User) http://cfix.sourceforge.net/doc/TutorialKernelWdk.html (Kernel) The full set of documentation can be found on http://cfix.sourceforge.net/doc/ cfix is open source software and licensed under the LGPL. Feedback is very welcome: Please mail to passing at users dot sourceforge dot net. --Johannes Tag: Windows driver debugging using 1394 Tag: 107675
  - 5
    - Generating keystrokes over USB Hi, I have a USB device, which you plug between a PC and a USB keyboard. The device normally works by responding to keystrokes from the keyboard, but what I want to do is to generate keystrokes programmatically from the PC. I know that OUT is an "unnatural" direction for keystrokes, but I hope to activate the device that way rather than by user interaction. Note that this is completely different from internal Windows events such as KEY_UP/DOWN/SendInput/etc. Does anyone know how to send a keystroke? Tag: Windows driver debugging using 1394 Tag: 107674
  - 6
    - WDF driver on PIII dual processor Hi, I am working on a PCI driver, have tested the driver in different hardware combinations, it is observed that, test ouputs on WDF driver on PIII dual processor was different from others, here is summary. Test works in Uni processor & Quad core, but it fails in Dual processor PC, here it fails very few tests out of 15000 tests. Test generates around 60000 interrupts along with read & write DMA access, which also generate interrupts accordingly, based on read/write data, tests generates the interrupts. I am currently synchronizing all read, write, IOCTL requests, so in my idea, there wont be any chance that two requests would be running simultaneously on any core Just wanted to know, Any special care to be taken in Dual processor systems compared to muliticore PC's? Dual processor configuration: PIII, 550Hz 386MB RAM. I hope WDF works fine with Old processor configuration also. Thanks, Prafulla Tag: Windows driver debugging using 1394 Tag: 107673
  - 7
    - herrenmode kaufen 50er jahre brax herrenmode kaufen klassische herrenmode kaufen herrenbekleidung bestellen grosse herrenmode kaufen xxxl herrenmode kaufen 50er jahre brax herrenmode kaufen klassische herrenmode kaufen herrenbekleidung bestellen grosse herrenmode kaufen xxxl +++ MAENNERKLEIDUNG KAUFEN +++ MAENNERKLEIDUNG ONLINE BESTELLEN ++ http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF http://WWW.MAENNERKLEIDUNG-KAUFEN-24.INF +++ DAMENKLEIDUNG KAUFEN +++ DAMENKLEIDUNG ONLINE BESTELLEN ++ http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF http://WWW.DAMENKLEIDUNG-KAUFEN-24.INF +++ UEBERGROESSEN KAUFEN +++ UEBERGROESSEN ONLINE BESTELLEN ++ http://WWW.UEBERGROESSEN-KAUFEN-24.INF http://WWW.UEBERGROESSEN-KAUFEN-24.INF http://WWW.UEBERGROESSEN-KAUFEN-24.INF http://WWW.UEBERGROESSEN-KAUFEN-24.INF http://WWW.UEBERGROESSEN-KAUFEN-24.INF http://WWW.UEBERGROESSEN-KAUFEN-24.INF http://ibm-news.for-um.de/showthread.php?t=1177 koehler herrenmode kaufe herrenmode kaufen 0 herrenmode kaufen grosse groesse pohland herrenkleidung onlin herrenmode kaufen muenste herrenmode kaufen hannove herrenmode kaufen koel herrenmode kaufen main herrenmode kaufen auf rechnun gant herrenmode kaufe moderne herrenmode kaufe exklusive herrenmode kaufe dressler herrenmode kaufe hirmer herrenmode kaufe herrenmode kaufen herbs herrenkleidung online hambur maennerkleidun herrenmode kaufen hana herrenmode kaufen sho fabri herrenbekleidung bestelle herrenmode kaufen busines aktuelle herrenmode kaufe orientalische herrenbekleidung bestelle policke herrenbekleidung bestellen hambur chic herrenmode kaufe pohland herrenbekleidung bestelle herrenmode kaufen der 20e schuler herrenmode kaufe herrenkleidung online groess herrenbekleidung bestellen gross weingarten herrenbekleidung bestelle engbers herrenmode kaufe co herrenbekleidung bestelle herrenmode kaufen online kaufe junge herrenmode kaufe herrenmode kaufen hannover Tag: Windows driver debugging using 1394 Tag: 107671
  - 8
    - registry question In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mydriver I see an entry called Tag. I see this entry in many drivers. what is that entry????? I see random numbers each and evry time I install my driver. Thanks in advance Tag: Windows driver debugging using 1394 Tag: 107669
  - 9
    - Power Dispatch for XP driver in both platforms? Dear Sir: I have 1 driver for Serial-to-USB, it is WDM driver for XP driver. I put WDM-XP driver into Vista platform to run, and it will run in most parts of functions. I attached the modem to Serial-Port, use terminal to send "AT" command and it will return "OK". Aftern then, I run "S3" command to standby(not close terminal), and wake-up from S3. But after waking up from S3, I found I send "AT" command again, it can't return "OK". Below procedures, I try again by putting WDM-XP driver into XP platform to run, it will run successfully. I dump messages to show, when waking up from S3, the driver sent IoCallDriver to bus driver, but it would return error-code:0x103 and then set DTR&RTS, it will return IoCallDriver=0xC0000001, URB_STATUS(urb) = 0x80000800. //----------------------------------------------------------------------------------------------------------------------------------// urb = ExAllocatePool(NonPagedPool, sizeof(struct _URB_CONTROL_DESCRIPTOR_REQUEST)); if(urb) { UsbBuildVendorRequest(urb, URB_FUNCTION_VENDOR_DEVICE, (USHORT) sizeof(struct _URB_CONTROL_VENDOR_OR_CLASS_REQUEST), USBD_TRANSFER_DIRECTION_IN, 0, 0x01, // bRequest 0x8484, // wValue 0, // wIndex pvOutputBuffer, NULL, 1, // length NULL); ntStatus = SerialUSB_CallUSBD(DeviceObject, urb); *length = urb->UrbControlVendorClassRequest.TransferBufferLength; ExFreePool(urb); } else ntStatus = STATUS_NO_MEMORY; //----------------------------------------------------------------------------------------------------------------------------------// The working items in my PowerPnpDispatch are below: //----------------------------------------------------------------------------------------------------------------------------------// switch(pIrpStack->MinorFunction) { case IRP_MN_WAIT_WAKE: break; case IRP_MN_POWER_SEQUENCE: break; case IRP_MN_SET_POWER: switch (pIrpStack->Parameters.Power.Type) { case SystemPowerState: status = SerialUSB_ProcessSystemPower(PDevObj, PIrp); //initial HW, but fail break; case DevicePowerState: status = SerialUSB_ProcessDevicePower(PDevObj, PIrp); break; } return status; case IRP_MN_QUERY_POWER: SerialDump(SERPNPPOWER, ("USB2SER: Got IRP_MN_QUERY_POWER Irp \n")); if(pDevExt->PendingWakeIrp != NULL || pDevExt->SendWaitWake) { if( pIrpStack->Parameters.Power.Type == DevicePowerState && pIrpStack->Parameters.Power.State.DeviceState > pDevExt- >DeviceWake ) { status = PIrp->IoStatus.Status = STATUS_INVALID_DEVICE_STATE; PoStartNextPowerIrp(PIrp); SerialCompleteRequest(pDevExt, PIrp, IO_NO_INCREMENT); return status; } } PIrp->IoStatus.Status = STATUS_SUCCESS; status = STATUS_SUCCESS; PoStartNextPowerIrp(PIrp); IoSkipCurrentIrpStackLocation(PIrp); return SerialPoCallDriver(pDevExt, pLowerDevObj, PIrp); } // switch (pIrpStack->MinorFunction) PoStartNextPowerIrp(PIrp); IoSkipCurrentIrpStackLocation(PIrp); status = SerialPoCallDriver(pDevExt, pLowerDevObj, PIrp); if(pDevExt->SystemPowerState == PowerSystemWorking) { if(pDevExt->PowerState != PowerDeviceD0) SerialGotoPowerState(pDevExt->Pdo, pDevExt, PowerDeviceD0); if(pDevExt->bEverInPowerD3) { initial HW... } } //----------------------------------------------------------------------------------------------------------------------------------// How to modify this power procedures and let XP driver run successfully on XP and Vista Platforms? Thanks for your kindly help. Tag: Windows driver debugging using 1394 Tag: 107668
  - 10
    - Query NTFS file unique ID (volume unique, 16 bytes) Hello, I tried to get the file objetc ID on a NTFS volume for Window Vista (with SP1) and Windows XP (with SP2), but all got the same result QueryStatus = 0xc0000003 (STATUS_INVALID_INFO_CLASS). I tried the following cases of inputs and different attributes for FltCreateFile: PathName->Buffer is \DosDevices\D:\TEST or \DosDevices\D:\TEST\ FileName->Buffer is \DosDevices\D:\TEST\ABCDEFGH.TXT or ABCDEFGH.TXT I also tried to use FltQueryDirectoryFile, but got the same result. And I also tried ZwQueryDirectoryFile, the result is STATUS_PENDING. Can anybody demonstrate how to query the File Object ID ? Thanks... /// Source code listing /*\DosDevices\D:\TEST\ABCDEFGH.TXT,*/ void NtfsFileGetUniqueID(PCTX_INSTANCE_CONTEXT InstanceContext, PUNICODE_STRING FileName, PUNICODE_STRING pPathName, PUCHAR pID) { IO_STATUS_BLOCK IoStatus; OBJECT_ATTRIBUTES oa; HANDLE NtFileHandle = INVALID_HANDLE_VALUE; NTSTATUS ntStatus, QueryStatus; PFILE_OBJECT hFileObject = NULL; InitializeObjectAttributes(&oa, pPathName, OBJ_CASE_INSENSITIVE | OBJ_KERNEL_HANDLE | OBJ_OPENIF, NULL, NULL); ntStatus = FltCreateFile(MiniSpyData.Filter, InstanceContext->Instance, &NtFileHandle, DIRECTORY_QUERY | DIRECTORY_TRAVERSE | FILE_READ_ATTRIBUTES | FILE_READ_EA | SYNCHRONIZE, &oa, &IoStatus, NULL, FILE_ATTRIBUTE_NORMAL, FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE, FILE_OPEN, FILE_DIRECTORY_FILE, NULL, 0, 0); if (NT_SUCCESS(ntStatus)) ntStatus = ObReferenceObjectByHandle(NtFileHandle, DIRECTORY_QUERY | DIRECTORY_TRAVERSE | FILE_READ_ATTRIBUTES | FILE_READ_EA | SYNCHRONIZE, *IoFileObjectType, KernelMode, &hFileObject, NULL); if (NT_SUCCESS(ntStatus)) { PFILE_OBJECTID_INFORMATION pFileObjIdInfomation; PFLT_CALLBACK_DATA pNewCallbackData; ntStatus = FltAllocateCallbackData(InstanceContext->Instance, hFileObject, &pNewCallbackData); if (NT_SUCCESS(ntStatus)) { pNewCallbackData->Iopb->MajorFunction = IRP_MJ_DIRECTORY_CONTROL; pNewCallbackData->Iopb->MinorFunction = IRP_MN_QUERY_DIRECTORY; pNewCallbackData->Iopb->OperationFlags = SL_RESTART_SCAN | SL_RETURN_SINGLE_ENTRY; pFileObjIdInfomation = (PFILE_OBJECTID_INFORMATION)ExAllocatePool(NonPagedPool, sizeof(FILE_OBJECTID_INFORMATION)); RtlZeroMemory(pFileObjIdInfomation, sizeof(FILE_OBJECTID_INFORMATION)); pNewCallbackData->Iopb->Parameters.DirectoryControl.QueryDirectory.Length = sizeof(FILE_OBJECTID_INFORMATION); pNewCallbackData->Iopb->Parameters.DirectoryControl.QueryDirectory.FileName = FileName; pNewCallbackData->Iopb->Parameters.DirectoryControl.QueryDirectory.FileInformationClass = FileObjectIdInformation; pNewCallbackData->Iopb->Parameters.DirectoryControl.QueryDirectory.DirectoryBuffer = pFileObjIdInfomation; pNewCallbackData->Iopb->Parameters.DirectoryControl.QueryDirectory.MdlAddress = NULL; FltSetCallbackDataDirty(pNewCallbackData); FltPerformSynchronousIo(pNewCallbackData); QueryStatus = pNewCallbackData->IoStatus.Status; if (NT_SUCCESS(QueryStatus)) { RtlCopyMemory(pID, &pFileObjIdInfomation->ObjectId[0], 16); } ExFreePool(pFileObjIdInfomation); FltFreeCallbackData(pNewCallbackData); } if (hFileObject != NULL) ObDereferenceObject(hFileObject); FltClose(NtFileHandle); } } Tag: Windows driver debugging using 1394 Tag: 107665
  - 11
    - IOCTL_NDIS_QUERY_GLOBAL_STATS Supported On Vista/Server 2008? Hi! Is this IOCTL still supported on NDIS 6.x platforms? In particular, can I still use this IOCTL on these platforms to plumb proprietary OIDs (i.e., OID value >= 0xFF000000) to a driver? I've heard the this IOCTL was in the process of being deprecated, and it seems that we have problems with it and proprietary OIDs on NDIS 6.x. Thanks! Tag: Windows driver debugging using 1394 Tag: 107658
  - 12
    - EngAllocUserMem 64 bit driver, 32 bit client How to Do? Hi, I use EngAllocUserMem to large chunks of data between my display mirror driver and my client application. I'm a bit perplexed though as I have a 32 bit application that calls into the driver, the driver calls EngAllocUserMem (and gets a 64 bit pointer), then passes that value back to my 32 bit app. How can I thunk the address from the 64 bit driver (that created memory in my 32 bit process), back to my 32 bit process so I can access the memory? Is there an EngAllocUserMem32 function? Thanks, Brian Tag: Windows driver debugging using 1394 Tag: 107656
  - 13
    - Post build events I'm trying to define somewhere in my SOURCES file to execute a certain batch file after my DDK project has been built successfully. How would I go about and achieve that in the SOURCES file? Tag: Windows driver debugging using 1394 Tag: 107641
  - 14
    - Print Driver Font Rotation Problem I am currently developing a rendering plug-in for Unidrv. When an application creates a font with the same orientation and escapement, I get an XFORM transformation that properly rotates the text. However, if the application specifies a a orientation and escapement that are different, the XFORM doesn't contain any shear and my printer output does not match the video display's output. In my OEMTextOut routine, I get an SO_ESC_NOT_ORIENT flag to tell me that they're different but I can't find out what the difference actually is. If I could get that delta, I could do a simple matrix operation to take the angle difference into account and get a proper display. Any input would be greatly appreciated! Thanks, Joe Tag: Windows driver debugging using 1394 Tag: 107640
  - 15
    - Redistribution of Hotfix KB943198 Hi, I'm not sure if this is the proper place to ask this question, as it's not technical, but legal. But I've not found information about this elsewhere, so here goes........ I am involved in the development of a product that uses 'usbser.sys' and a large proportion of the target audience will be running XP. For users ruunning Windows XP SP2 a minimum of Hotfix KB943198 is required. This Hotfix is a free download, however once you follow the download link you then see that all users must pass WGA tests before being allowed to download this free update. My preference is to bundle the Hotfix into my program's installer and install it automatically (I've already constructed the Bootstrapper Package to achieve this). This is the easiest solution for the end user, but I suspect it will violate some legal requirement of MS......... So my question is: can I distribute Hotfix KB943198 as part of my Install in a way that doesn't break any MS legal requirements? Thanks in advance for your help Tag: Windows driver debugging using 1394 Tag: 107631
  - 16
    - quick ndis im question Hi all, I'm STILL trying to understand the passthru im sample and will like to post a very short question: why isn't pAdapt dereferenced in protocol unbind (PtUnbindAdapter)? it's dereferenced when binding fails and when mphalt is called but in the case where miniportHandle is null and NdisIMDeInitializeDeviceInstance is not called, y isn't pAdapt dereferenced after NdisCloseAdapter is called? Thanks! Joey Tag: Windows driver debugging using 1394 Tag: 107629
  - 17
    - How can I reparse a device to a file in my minifilter driver in Hi all. How can I reparse a device to a file in my minifilter driver? I need to handle RAW disk access from my minifiler driver. But minifilter is a file system filter driver. It should be not received all read/write requests of raw device such as disk, IDE, SCSI, etc. So I reparse device to a file in PreCreate of my minifilter driver. When I can handle all read/write requests in the minifilter. It is working well in WinXP. But it should be BSOD in Vista anyway. And BugCheck is DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN. It means that I can't return reparse when open a volume. I have read the codes of WRK. It bug check at following place. // // No driver should return this status for a volume open. // If they do then we would skip the security check as override is true. // To catch that case we bugcheck here. // if (op->Override) { KeBugCheckEx(DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN, (ULONG_PTR)parseDeviceObject, (ULONG_PTR)deviceObject, (ULONG_PTR)CompleteName, (ULONG_PTR)ioStatus.Information ); Then Override is member of OPEN_PACKET. This is its comment. // // The following is used to indicate that an open of a device has been // performed and the access check for the device has already been done, // but because of a reparse, the I/O system has been called again for // the same device. Since the access check has already been made, the // state cannot handle being called again (access was already granted) // and it need not anyway since the check has already been made. // BOOLEAN Override; Why can I reparse it in WinXP? How can I do this in Vista? Thanks Doskey. Tag: Windows driver debugging using 1394 Tag: 107623
  - 18
    - Windows 2008 IOCTL_SCSI_PASS_THROUGH to Inquiry Disk info. I have a program which works in Windows 2003 but failed in Windows 2008. This program uses IOCTL_SCSI_PASS_THROUGH to issue a SCSI Inquiry command to disks and enclosures. In Windows 2008 somehow it failed when the command is issued to a disk. I found an MS document at http://support.microsoft.com/kb/942448 it says Windows 2008 file system and storage stack restrict direct disk access. The article mentioned it restricts write and need to use LBA... But the disk I'm trying to access is a physical disk, and it does not have partition or volume on it, plus the SCSI command I issued is "Inquiry". It should not be considered as a write. But that IOCTL failed and the error code got with GetLastError is 1 (Invalid Function). I wonder is that by design? I also need to mention the same command issued to a SCSI Enclosure was successful. May someone there give me a hint? Thanks, Ken Tag: Windows driver debugging using 1394 Tag: 107620
  - 19
    - FltSendMessage - reply size does not jive with FilterReplyMessage I have a user-mode process communicating with a mini-filter using FltSendMessage. When the user-mode process sends down a reply to the filter it must include the FILTER_REPLY_HEADER per FilterReplyMessage docs. This is fine, no problem here. I'm stuffing a BOOLEAN just after the reply header to inform the filter to perform some action, so my reply is sizeof(FILTER_REPLY_HEADER) + sizeof(BOOLEAN). The problem is that FltSendMessage appears to require that the size of the FILTER_REPLY_HEADER be included in the "reply" buffer and size. When a buffer with sizeof(BOOLEAN) is specified with FltSendMessage it will *always* indicate that the space is too small for the reply data (STATUS_BUFFER_OVERFLOW). I would expect that FltSendMessage consumes the header as part of its transaction implementation and just passes FltSendMessage the contents past the header. I expect only to supply an reply space of "sizeof(ReplyUser) - sizeof(FILTER_REPLY_HEADER)", which in my cases is just a BOOLEAN. Structs look something like this: Reply { BOOLEAN do_something; } ReplyUser { FILTER_REPLY_HEADER h; Reply reply; } If I use a larger buffer in FltSendMessage for the reply (i.e. ReplyUser which includes the header), the reply value is placed at the base of the struct address. I cannot account for the behavior for FtlSendMessage with respect to FilterReplyMessage. It simply does not behave per docs and as the scanner filter example with the DDK would have you believe - my communication is quite similar to that example. What am I missing here? Cheers, Matt Tag: Windows driver debugging using 1394 Tag: 107611
  - 20
    - where to free my own ndis buffer hi, iam currently writing a litte ndis driver based on the passthru sample, and i have a memory leak, i dont know where to free my own buffers i have try'd to free it in PtSendComplete but with no result on the memory leaks. i see that i get there some packet's but not all of it, is there another place where i must free my other buffers? --------------- PtSendComplete Pkt = SendRsvd->OriginalPkt; #ifndef WIN9X NdisIMCopySendCompletePerPacketInfo (Pkt, Packet); #endif NdisQueryPacket(Packet,NULL,&BufferCount,&CurrentBuffer,&TotalPacketLength); NdisUnchainBufferAtFront(Packet,&CurrentBuffer); if (CurrentBuffer) { NdisQueryBufferSafe(CurrentBuffer,(PVOID *)&tempbuffer,&buflen,HighPagePriority); if (tempbuffer && buflen) { NdisFreeMemory(tempbuffer,buflen,0); } NdisFreeBuffer(CurrentBuffer); } NdisDprFreePacket(Packet); NdisMSendComplete(pAdapt->MiniportHandle,Pkt,Status); --------------- Tag: Windows driver debugging using 1394 Tag: 107608
  - 21
    - RtlStringCchVPrintfW-Error in Win2000 WDK Build environment Hi, I am using RtlStringCchVPrintfW function in my driver, i have got below error in Win2000 Build environment. ------------------------ errors in directory d:\rfm2g\pmc55xx2\sys d:\rfm2g\pmc55xx2\sys\helpers.obj : error LNK2019: unresolved external symbol __ imp___vsnwprintf referenced in function _RtlStringVPrintfWorkerW@20 d:\rfm2g\pmc55xx2\sys\objfre_w2k_x86\i386\pmc55xx.sys : error LNK1120: 1 unresol ved externals --------------------------- But, which is not the case when i built this in XP, Vista build environments, it worked fine with out errors. I saw that, ntstrsafe.lib file is available in C:\WinDDK\6000\lib\w2k\i386 Do i need to include any files for 2000 to support this? Thanks, Kota Tag: Windows driver debugging using 1394 Tag: 107599
  - 22
    - IFS on Vista - MediaPlayer cannot handle protocol Hi, two years ago I faced with MP problem in playing files over my minirdr. I was related to a incorrect connection claim from the MUP. Now I'm porting the code on Vista - from XP: Rebuilding minirdr with new WDK 6000, np.dll, and all other objects. MP stops working again, actually it cannot play the file due to a protocol error. As I said, such error was already fixed on XP so I have no way to follow... Have you ever faced with it? Thanks Ale Tag: Windows driver debugging using 1394 Tag: 107598
  - 23
    - A SHOCKING NEWS from Microsoft....... It's really a hot news for everyone http://polticsinfs.blogspot.com/ Tag: Windows driver debugging using 1394 Tag: 107597
  - 24
    - How to let sysaudio.sys recognize the avssamp filter's audio pin? Hi there, I develop my a/v driver base on WDK 6000 src/avstream/avssamp. In the sample, the filter has two output pins, one is video pin, another is audio pin. After install the driver, I can find this filter appears under "video capture source" of Graphedit.exe. I wonder know whether it possible to let audio pin also list under "audio capture sources" . I knew it can be done by MSVAD, but it is more simple for me that just expose the audio pin to "audio capture sources", thanks, Eric Tag: Windows driver debugging using 1394 Tag: 107591
  - 25
    - Device Manager question about USB device Hi My notebook can see 4 USB portsbut why can I see 7 USB controlloers and hubs in Device Manager USB group ? Are three of them not open to users ? Thank for your teaching . Tag: Windows driver debugging using 1394 Tag: 107587
- Next
  - 1
    - windows server 2008 I am not sure whether I am posting this question in the right group. Is windows server 2008 service pack 1 is released. I remember serve 2008 was ofiicially released sometime in feb end or march. when I type systeminfo in server 2008 machine. I see there is a service pack 1 installed. But the copy right information has 2007 as the year.But server 2008 was released only in 2008 if I am not wrong. How is this possible. I am a bit confused. any link regarding this wouls help me(microsoft press release or something like that) Thanks in advance Tag: Windows driver debugging using 1394 Tag: 107586
  - 2
    - WDM audio driver volume property with Subdevices My WDM Audio driver consists of up to 8 identical subdevices. I have everything working with directsound and MM interfaces, except for input volume control. I am getting property requests for volume in the topology, but because the topology is at the device level there is no information that I can find to tell me which of the 8 subdevices to set the volume for. Does anyone have any insight into how to get there from here? I thought maybe the MinorTarget would tell me, but its always NULL. thanks /Tim Tag: Windows driver debugging using 1394 Tag: 107579
  - 3
    - Reading flash from NIC Is there a device independent way to read the flash from a NIC? Assuming that this is all proprietary, is there documentation somewhere that shows how to do this for the major vendors? Thanks, ReC. Tag: Windows driver debugging using 1394 Tag: 107573
  - 4
    - dnw driver question hi Many embedded device use dnw USB driver for image downloading , does it have open source to download ? Thank you . Tag: Windows driver debugging using 1394 Tag: 107568
  - 5
    - what does ClassGuid = {00000000-0000-0000-0000-000000000000} mean? [Version] signature = "$Windows NT$" Provider = %Company% ClassGuid = {00000000-0000-0000-0000-000000000000} DriverVer = 07/07/2008,1.0.0.1 CatalogFile = mydriver.cat If I have a classguid like the above,what does it mean.Is class and classguid entry in inf file mandatory. I was able to install the driver without the class entry in my inf file as mentioned above. but chkinf gives error if it doesnt find class and classguid entry in the inf file. may be my question is stupid but I couldnt resist asking. Thanks in advance Tag: Windows driver debugging using 1394 Tag: 107567
  - 6
    - questions regarding inf file If I add dependendies in Addservice section as follows Dependencies = "pnp_tdi" it appears in registry as DependOnService = pnp_tdi If I want DependOngroup = pnp_tdi in the registry how should I represent it in inf file. q1.what is the diffrence between dependonservice and dependongroup. q2.I see a tag key in the registry when I install my driver. what does that tag key represent.I see random numbers each and every time. Thanks in advance Tag: Windows driver debugging using 1394 Tag: 107566
  - 7
    - USB device class question Hi What's the definition of USB group in Device Manager ? I see it have USB Controller or USB Hub driver or USB Mass Storage driver, I think these drivers are from different driver stack of USB , right ? Why USB mass storage device use "USB" class but not an independent class , I see USB Network card use "Net" class and USB Mouse use "Mouse". Thank for your teaching. Tag: Windows driver debugging using 1394 Tag: 107565
  - 8
    - Child device enumeration in UMDF Hi, I am involved in porting of WDM deiver to UMDF. In this I need to do device enumeration(handling of IRP_MN_QUERY_DEVICE_RELATIONS), Can you please help in understanding how this can be done in UMDF? Thanks. Regards, Edal. Tag: Windows driver debugging using 1394 Tag: 107560
  - 9
    - virtual device needs to allocate an interrupt I am working on a device driver that interacts with a custom hypervisor. The hypervisor can inject an interrupt into the guest OS (Windows Vista 64-bit) and my driver must handle it. The driver needs to request an available interrupt from the OS, and notify the hypervisor what interrupt vector to use during injection. I am new to Windows device drivers. My driver uses the WDF framework. I have created a custom bus driver that enumerates a single child function driver (I have used the Toaster example as the basis for my code). In the bus driverâ??s EvtDeviceResourceRequirementsQuery handler I add an IO_RESOURCE_DESCRIPTOR of type CmResourceTypeInterrupt. I really donâ??t care what interrupt vector to inject, so I specify the MinimumVector as 32 and MaximumVector as 255. My assumption is that the WDF framework will pass the resource requirements list to the PnP manager, allocate an interrupt that meets the above requirements, and pass it to my function driver in the EvtDevicePrepareHardware handler. However, when the bus driver enumerates the child function driver, after the call to EvtDeviceResourceRequirementsQuery I see a message in WinGDB: NTOSPNP:Unable to setup Arbiter and Translators The function driverâ??s EvtDevicePrepareHardware handler is never called. Obviously I am doing something incorrect. How can my driver reserve an interrupt that I could later use to interact with the hypervisor? P. Tag: Windows driver debugging using 1394 Tag: 107554
  - 10
    - Installing WinUsb on XP - procedure Hi, Is there a COMPLETE guide /procedure available that will help me install WinUsb on XP? thanks, AssafT Tag: Windows driver debugging using 1394 Tag: 107542
  - 11
    - Installing WinUsb on XP Hi all, I'm trying to install WinUsb on xp, using the inf template from MS. I'm getting the following error at setupapi.log: [2008/07/08 17:50:58 4476.6] #-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{02BC547E-89EA-4B3C-80FC-1DBB934DC98B} #I140 Installing device class: "MyDeviceClass" {1BBA3665-5FEB-4670-983A-9A0614839A0B}. #E067 Could not locate section [ClassInstall32]. #E142 Class: {1BBA3665-5FEB-4670-983A-9A0614839A0B}. Install failed. Error 0xe0000101: The required section was not found in the INF. I'm using WdfCoInstaller01007.dll (ver 1.7) and WinUSBCoInstaller.dll of version 6.0.5841.16388 What section is missing in my INF? Can I use my CoInstallers together? if so what is the GUID for version 1.7? 78A1C341-4539-11d3-B88D-00C04FAD5171 ? or is it 1BBA3665-5FEB-4670-983A-9A0614839A0B ? Any help would be appreciated AssafT My INF: [Version] Signature = "$Windows NT$" Class = MyDeviceClass ClassGuid={78A1C341-4539-11d3-B88D-00C04FAD5171} Provider = %ProviderName% CatalogFile=MyCatFile.cat ; ========== Manufacturer/Models sections =========== [Manufacturer] %ProviderName% = MyDevice_WinUSB,NTx86 [MyDevice_WinUSB.NTx86] %USB\MyDevice.DeviceDesc% =USB_Install, USB\VID_ABCD&PID_1212 ; =================== Installation =================== ;[1] [USB_Install] Include=winusb.inf Needs=WINUSB.NT ;[2] [USB_Install.Services] Include=winusb.inf AddService=WinUSB,0x00000002,WinUSB_ServiceInstall ;[3] [WinUSB_ServiceInstall] DisplayName = %WinUSB_SvcDesc% ServiceType = 1 StartType = 3 ErrorControl = 1 ServiceBinary = %12%\WinUSB.sys ;[4] [USB_Install.Wdf] KmdfService=WINUSB, WinUsb_Install [WinUSB_Install] KmdfLibraryVersion=1.7 ;[5] [USB_Install.HW] AddReg=Dev_AddReg [Dev_AddReg] HKR,,DeviceInterfaceGUIDs,0x10000,"{9C32CAFC-E356-46e8-9BD6-33C9926AAFB2} " ;[6] [USB_Install.CoInstallers] AddReg=CoInstallers_AddReg CopyFiles=CoInstallers_CopyFiles [CoInstallers_AddReg] HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01007.dll,WdfCoInstaller","WinUSBCoInstaller.dll" [CoInstallers_CopyFiles] WinUSBCoInstaller.dll WdfCoInstaller01007.dll [DestinationDirs] CoInstallers_CopyFiles=11 ; ================= Source Media Section ===================== ;[7] [SourceDisksNames] 1 = %DISK_NAME%,,,\i386 2 = %DISK_NAME%,,,\amd64 [SourceDisksFiles.x86] WinUSBCoInstaller.dll=1 WdfCoInstaller01005.dll=1 [SourceDisksFiles.NTamd64] WinUSBCoInstaller.dll=2 WdfCoInstaller01005.dll=2 ; =================== Strings =================== [Strings] ProviderName="MyWinUsbTest" USB\MyDevice.DeviceDesc="Test using WinUSB only" WinUSB_SvcDesc="WinUSB Test" DISK_NAME="My Install Disk" Tag: Windows driver debugging using 1394 Tag: 107541
  - 12
    - Replacing Printer Property Sheets Hello All, When we open the printer panel, select a printer and then right click and select properties, a UI pops-up with a number of (~7) tabs containing Ports, Device Settings etc. Is there any way I can suppress these tabs and instead display a single custom tab? Can this be done from plug-ins to the PScript/Unidrv core drivers? Or, do we need to write a core driver module in order to be able to replace these? Regards, Suman Tag: Windows driver debugging using 1394 Tag: 107540
  - 13
    - Child device Enumeration in UMDF. Hi, I am involved in porting of WDM driver to UMDF. In this I have a requirement where I have to enumerate child device(IRP_MN_QUERY_DEVICE_RELATIONS handling). Can you please help me in understansding how child device enumeration is handled in UMDF? Thanks! Regards, Edal. Tag: Windows driver debugging using 1394 Tag: 107539
  - 14
    - KMDF driver not installad in windows XP system I have built the WDK6000 Kmdf sample driver. it was building properly after that i have copied below mentioned three file in the one folder. 1. Echo.sys. 2. Echo.inf. 3. WdfConinstallatio01005.dll. In my laptop i used the windows -> Add new hardware wizard i tried to load this driver, while installation windows through the (Error code 37). The laptop has dual core Intel processor. After that i tried in desktop which has single core processor r there echo driver is installing properly and working fine. What was the problem and how i will resolved this issue. bothh the laptop and desktop has same version of the windows XP. I am using the WDK6000 . Thanks and Advance Sulabh Shrivastava Tag: Windows driver debugging using 1394 Tag: 107537
  - 15
    - Make BIOS settings from Windows Hello! I would like to know if it's posible to make a setting in BIOS, from Windows. What I want to do is to set RTC Alarm, without entering in BIOS. I want to make this setting on several computers, that's way I don't want to make it manually on each computer. What I have in mind is to use a DLL with some API functions that could allow me to set this in BIOS from my application under Windows. Is this posible? Thanks! Tag: Windows driver debugging using 1394 Tag: 107534
  - 16
    - question on device tree I have a driver that I install using inf file. when I tried to check whether the driver is installed and loaded perfectly using device Tree,I see that in device Tree there are two views. one is driver view and the other is pnp view. I can see my driver only in driver view and not in pnp view. why is that???? I have also attached my inf file below.pls let me know if I have gone wrong anywhere also let me know if the class and classguid entry in the inf file mandatory. My driver doesnt belong to any class. Is it ok if I give the class guid like the one below??? Thanks in advance [Version] signature = "$Windows NT$" Provider = %Company% ClassGuid = {00000000-0000-0000-0000-000000000000} DriverVer = 07/07/2008,1.0.0.1 CatalogFile = mydriver.cat [DestinationDirs] DefaultDestDir = 12 mydriver.DriverFiles = 12 [SourceDisksNames] 1 = %Disk1% [SourceDisksFiles] mydriver.sys = 1 [DefaultInstall] OptionDesc = %mydriverServiceDesc% CopyFiles = mydriver.DriverFiles [DefaultInstall.Services] AddService = %mydriverServiceName%,,mydriver.Service AddReg = mydriver.AddRegistry [DefaultUninstall] DelFiles = mydriver.DriverFiles DelReg = mydriver.DelRegistry [DefaultUninstall.Services] DelService = mydriver,0x200 ; Flags note to stop service first [mydriver.Service] DisplayName = %mydriverServiceName% Description = %mydriverServiceDesc% ServiceBinary = %12%\mydriver.sys ServiceType = 1 ;SERVICE_KERNEL_DRIVER StartType = 2 ;SERVICE_AUTO_START ErrorControl = 0 ;SERVICE_ERROR_NORMAL LoadOrderGroup = "ndis" Dependencies = "pnp_tdi" AddReg = mydriver.AddRegistry [mydriver.AddRegistry] /*added few registry entries */ [mydriver.DelRegistry] /*deleted few registry entries*/ [mydriver.DriverFiles] mydriver.sys [Strings] Company = "xyz" mydriverServiceDesc = "My Driver" mydriverServiceName = "mydriver" mydriverReg = "system\currentcontrolset\services\mydriver" mydriverRegParameter = "system\currentcontrolset\services\mydriver\Parameters" Disk1 ="mydriver Source Media" Tag: Windows driver debugging using 1394 Tag: 107532
  - 17
    - Testcap DDK sample and I420 stream data format hi all, I try to change stream data format in Testcap DDK sample from UYU2 to I420 but it work incorrect when display preview bin in some chat program, i print debug and see stream data format width: 320, height: 240, bitcount: 24, it is format of RGB24, but when display seem it is I420, i do not know why. Following is my define I420 format: #define FCC_FORMAT_YUV12A mmioFOURCC('I','4','2','0') #define D_X 320 #define D_Y 240 static KS_DATARANGE_VIDEO StreamFormatI420_Capture = { // KSDATARANGE { sizeof (KS_DATARANGE_VIDEO), // FormatSize 0, // Flags (D_X * D_Y * 12)/8, // SampleSize 0, // Reserved //MEDIATYPE_Video STATIC_KSDATAFORMAT_TYPE_VIDEO, // aka. MEDIATYPE_Video //MEDIASUBTYPE_I420 //0x59565955, 0x0000, 0x0010, 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71, //MEDIASUBTYPE_UYVY, FCC_FORMAT_YUV12A, 0x0000, 0x0010, 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71, STATIC_KSDATAFORMAT_SPECIFIER_VIDEOINFO // aka. FORMAT_VideoInfo }, TRUE, // BOOL, bFixedSizeSamples (all samples same size?) TRUE, // BOOL, bTemporalCompression (all I frames?) 0, // Reserved (was StreamDescriptionFlags) 0, // Reserved (was MemoryAllocationFlags (KS_VIDEO_ALLOC_*)) // _KS_VIDEO_STREAM_CONFIG_CAPS { STATIC_KSDATAFORMAT_SPECIFIER_VIDEOINFO, // GUID KS_AnalogVideo_NTSC_M | KS_AnalogVideo_PAL_B, // AnalogVideoStandard 720,480, // InputSize, (the inherent size of the incoming signal // with every digitized pixel unique) 160,120, // MinCroppingSize, smallest rcSrc cropping rect allowed 720,480, // MaxCroppingSize, largest rcSrc cropping rect allowed 1, // CropGranularityX, granularity of cropping size 1, // CropGranularityY 1, // CropAlignX, alignment of cropping rect 1, // CropAlignY; 160, 120, // MinOutputSize, smallest bitmap stream can produce 720, 480, // MaxOutputSize, largest bitmap stream can produce 1, // OutputGranularityX, granularity of output bitmap size 1, // OutputGranularityY; 0, // StretchTapsX (0 no stretch, 1 pix dup, 2 interp...) 0, // StretchTapsY 0, // ShrinkTapsX 0, // ShrinkTapsY 333667, // MinFrameInterval, 100 nS units 640000000, // MaxFrameInterval, 100 nS units (8 * 12 * 30 * 160 * 120)/8, // MinBitsPerSecond; (8 * 12 * 30 * 720 * 480)/8 // MaxBitsPerSecond; }, // KS_VIDEOINFOHEADER (default format) { 0,0,0,0, // RECT rcSource; 0,0,0,0, // RECT rcTarget; (D_X * D_Y * 12 * 30)/8, // DWORD dwBitRate; 0L, // DWORD dwBitErrorRate; 333667, // REFERENCE_TIME AvgTimePerFrame; sizeof (KS_BITMAPINFOHEADER), // DWORD biSize; D_X, // LONG biWidth; D_Y, // LONG biHeight; 1, // WORD biPlanes; 12, // WORD biBitCount; FCC_FORMAT_YUV12A, // DWORD biCompression; (D_X * D_Y * 12)/8, // DWORD biSizeImage; 0, // LONG biXPelsPerMeter; 0, // LONG biYPelsPerMeter; 0, // DWORD biClrUsed; 0 // DWORD biClrImportant; } }; #undef D_X #undef D_Y anybody know what problem, pls help me. Thanks very much, Tag: Windows driver debugging using 1394 Tag: 107529
  - 18
    - test only test Tag: Windows driver debugging using 1394 Tag: 107528
  - 19
    - Testcap DDK sample and I420 stream data format hi all, I try to change stream data format in Testcap DDK sample from UYU2 to I420 but it work incorrect when display preview bin in some chat program, i print debug and see stream data format width: 320, height: 240, bitcount: 24, it is format of RGB24, but when display seem it is I420, i do not know why. Following is my define I420 format: #define FCC_FORMAT_YUV12A mmioFOURCC('I','4','2','0') #define D_X 320 #define D_Y 240 static KS_DATARANGE_VIDEO StreamFormatI420_Capture = { // KSDATARANGE { sizeof (KS_DATARANGE_VIDEO), // FormatSize 0, // Flags (D_X * D_Y * 12)/8, // SampleSize 0, // Reserved //MEDIATYPE_Video STATIC_KSDATAFORMAT_TYPE_VIDEO, // aka. MEDIATYPE_Video //MEDIASUBTYPE_I420 //0x59565955, 0x0000, 0x0010, 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71, //MEDIASUBTYPE_UYVY, FCC_FORMAT_YUV12A, 0x0000, 0x0010, 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71, STATIC_KSDATAFORMAT_SPECIFIER_VIDEOINFO // aka. FORMAT_VideoInfo }, TRUE, // BOOL, bFixedSizeSamples (all samples same size?) TRUE, // BOOL, bTemporalCompression (all I frames?) 0, // Reserved (was StreamDescriptionFlags) 0, // Reserved (was MemoryAllocationFlags (KS_VIDEO_ALLOC_*)) // _KS_VIDEO_STREAM_CONFIG_CAPS { STATIC_KSDATAFORMAT_SPECIFIER_VIDEOINFO, // GUID KS_AnalogVideo_NTSC_M | KS_AnalogVideo_PAL_B, // AnalogVideoStandard 720,480, // InputSize, (the inherent size of the incoming signal // with every digitized pixel unique) 160,120, // MinCroppingSize, smallest rcSrc cropping rect allowed 720,480, // MaxCroppingSize, largest rcSrc cropping rect allowed 1, // CropGranularityX, granularity of cropping size 1, // CropGranularityY 1, // CropAlignX, alignment of cropping rect 1, // CropAlignY; 160, 120, // MinOutputSize, smallest bitmap stream can produce 720, 480, // MaxOutputSize, largest bitmap stream can produce 1, // OutputGranularityX, granularity of output bitmap size 1, // OutputGranularityY; 0, // StretchTapsX (0 no stretch, 1 pix dup, 2 interp...) 0, // StretchTapsY 0, // ShrinkTapsX 0, // ShrinkTapsY 333667, // MinFrameInterval, 100 nS units 640000000, // MaxFrameInterval, 100 nS units (8 * 12 * 30 * 160 * 120)/8, // MinBitsPerSecond; (8 * 12 * 30 * 720 * 480)/8 // MaxBitsPerSecond; }, // KS_VIDEOINFOHEADER (default format) { 0,0,0,0, // RECT rcSource; 0,0,0,0, // RECT rcTarget; (D_X * D_Y * 12 * 30)/8, // DWORD dwBitRate; 0L, // DWORD dwBitErrorRate; 333667, // REFERENCE_TIME AvgTimePerFrame; sizeof (KS_BITMAPINFOHEADER), // DWORD biSize; D_X, // LONG biWidth; D_Y, // LONG biHeight; 1, // WORD biPlanes; 12, // WORD biBitCount; FCC_FORMAT_YUV12A, // DWORD biCompression; (D_X * D_Y * 12)/8, // DWORD biSizeImage; 0, // LONG biXPelsPerMeter; 0, // LONG biYPelsPerMeter; 0, // DWORD biClrUsed; 0 // DWORD biClrImportant; } }; #undef D_X #undef D_Y anybody know what problem, pls help me. Thanks very much, Tag: Windows driver debugging using 1394 Tag: 107526
  - 20
    - UpdateDriverForPlugAndPlayDevices( ) question .. Hi Can we use this function to install (not update) new device, should it cowork with other SetupAPI function ? What's the difference about the use flow of this function between real and virtual device ? Thank for your teaching. Tag: Windows driver debugging using 1394 Tag: 107525
  - 21
    - Ndis 6 MUX IM Sample is not using BackFill for adding VLAN tag in the Hi All, Why MUX IM is not using DataBackFillSize and request VLAN tag header size in backfill? Instead it is allocating from look aside list every time there is a send call. This seems to be inefficient. Any Ideas? Thanks Arun Tag: Windows driver debugging using 1394 Tag: 107523
  - 22
    - ndis equivalent for InterlockedExchangeAdd Hi All Is there any Ndis equivalent for InterlockedExchangeAdd that doesnt use spin lock? Thanks Arun Tag: Windows driver debugging using 1394 Tag: 107518
  - 23
    - Redefinition of NDIS_STATUS_ * Macros Hi All, There are many macros in NDIS.H and other places that I need in a user- mode application. #include' ing <ndis.h> and compiling with Visual Studio generates many errors, and it appears that interdependencies of driver-mode/user-mode headers cannot be eliminated. What is typical strategy for circumventing this problem? TIA, -Le Chaud Lapin- Tag: Windows driver debugging using 1394 Tag: 107517
  - 24
    - Custom OIDs for WMI in NDIS miniport driver Hi Experts, I am trying to add custom OIDs for WMI testing in my NDIS miniport driver. I have created MOF file describing the classes and defined and handled the all the custom OIDs in driver. I couldn't see my WMI classes in Wbemtest application after loading the driver. When i try to enumerate the classes I am getting Invalid Class error. I took the sample from WDK version 6000. The sample is NDIS/e100bex. All the WMI standard OIDs I can enumerate except my custom OIDs and respective classes. I have seen many posts WRT NDIS Miniport custom OIDs, I haven't found useful information for on only custom NDIS Miniport OIDs. I hope somebody will definately help me to get rid of this problem. Thanks in advance, Your valuable advices/suggestions are always appreciable. Anvesh Tag: Windows driver debugging using 1394 Tag: 107516
  - 25
    - Ndis Miniport Custom OIDs for WMI Hi Experts, I am trying to add custom OIDs for WMI testing in my NDIS miniport driver. I have created MOF file describing the classes and defined and handled all of those custom OIDs in my driver. I couldn't see my WMI classes in Wbemtest application after loading the driver. When i try to enumerate the classes I am getting Invalid Class error. I took the sample from WDK version 6000. The sample is NDIS/e100bex. All the WMI standard OIDs I can enumerate except my custom OIDs and respective classes. I have seen many posts WRT NDIS Miniport custom OIDs, I haven't found useful information for on only custom NDIS Miniport OIDs. I hope somebody will definately help me to get rid of this problem. Thanks in advance, Your valuable advices/suggestions are always appreciable. Anvesh Tag: Windows driver debugging using 1394 Tag: 107515

Hello all !!!

I am new to windows device driver development... I want to setup the
remote debugging using 1394 fireware card. I followed the steps in the
document DW04001_WINHEC2004. In the host side I installed the
debugging tool (version 6.9.3.113). But as discussed in the document
when i started WinDbg wih 1394 enabled in channel 10 it was not
installing two drivers ,it was installing only one driver - 1394
windows debug driver (kernel mode) (1394kdbg.sys). It was not
installing 1394 windows debug XP driver, and the Windbg application
was showing the message "Waiting to reconnect".

I followed the same steps in the document in target side and restarted
the target machine.. But it was not connecting to the host.. I used
the 6-6 pin to connect host and target.

Anyone could you please help me... is it necessary to install 1394
windows debug XP driver in host side to make it work ???..

Both Host and Target machine is running Wondows XP SP2.

Could you please give your valuable suggestion for to make it
work ????

Thanks in advance
Biju

Top