"CreateCompatibleDC ()" may have a bug on XP x64

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
    - problem with NdisReturnPackets ( ) Hello, All! I get BSOD on vmware 5.0 and some other networc cards. It does not happen on other vmware versions and physical NICs. The problem appears when I try to send previously queued packed. The same(?) packets are sent before BSOD using the same functions, pools, etc without problems. On Windows 2000 Pro, mydriver rises D2 bugcheck somewhere in ethFilterDprIndicateReceivePacket (instead of D1 one in XPsp2 system, see below). Does anybody know why this may happen? According to http://pcausa.com/support/KB05050101.htm I use separate pools for send and receive packets. Also, I tried to zero Packet->MacReserved field. No luck. Any thoughts about this would be greatly appreciated. Best regards, Serge. ############################################################################ ######### *** Fatal System Error: 0x000000d1 (0x00000008,0x00000002,0x00000000,0xF9889848) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE Loading Kernel Symbols ................................................................... Loading unloaded module list ... Loading User Symbols **************************************************************************** *** * * * Bugcheck Analysis * * * **************************************************************************** *** Use !analyze -v to get detailed debugging information. BugCheck D1, {8, 2, 0, f9889848} Probably caused by : mydriver.sys ( mydriver!MPReturnPacket+73 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 804e3b25 cc int 3 kd> !analyze -v **************************************************************************** *** * * * Bugcheck Analysis * * * **************************************************************************** *** DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000008, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: f9889848, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 00000008 CURRENT_IRQL: 2 FAULTING_IP: NDIS!NdisReturnPackets+48 f9889848 8b7308 mov esi,[ebx+0x8] DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from f975f58f to f9889848 TRAP_FRAME: f9f028ec -- (.trap fffffffff9f028ec) ErrCode = 00000000 eax=ffffffff ebx=00000000 ecx=00000002 edx=00000002 esi=81664518 edi=81669f30 eip=f9889848 esp=f9f02960 ebp=f9f02978 iopl=0 nv up ei pl zr na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 NDIS!NdisReturnPackets+0x48: f9889848 8b7308 mov esi,[ebx+0x8] Resetting default scope STACK_TEXT: f9f02978 f975f58f f9f02998 00000001 817b1f30 NDIS!NdisReturnPackets+0x48 f9f029b4 f988987f 815ba3a0 817b1f30 81558280 mydriver!MPReturnPacket+0x73 [C:\Work\Driver\NDIS\miniport.c @ 598] f9f029dc f9755061 f9f02a00 00000001 817b1f78 NDIS!NdisReturnPackets+0xe9 f9f029f4 f9896d09 815ac140 817b1f30 f975ab40 psched!MpReturnPacket+0x3b f9f02a48 f975501d 00029d70 81685be0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x56d f9f02a5c f97551b4 81558280 81685be0 00000001 psched!PsFlushReceiveQueue+0x15 f9f02a80 f97555f9 815ac148 00000000 81558280 psched!PsEnqueueReceivePacket+0xda f9f02a98 f9896d40 815ac140 00000000 816b1120 psched!ClReceiveComplete+0x13 f9f02ae8 f9761fb4 00029d70 f9f02b08 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 f9f02c60 f976ab31 815ba3a0 817b1f30 00000001 mydriver!PtReceivePacketEx+0x119 [C:\Work\Driver\NDIS\protocol.c @ 745] f9f02ca0 f976ae93 815ba3a0 817b1f30 00000002 mydriver!Queue_Packet_ExecuteEx+0x85 [C:\Work\Driver\NDIS\queue_packet.c @ 239] f9f02cd8 f976b453 815ba3a0 81027720 00000000 mydriver!Queue_Packet_Execute_Item+0xef [C:\Work\Driver\NDIS\queue_packet.c @ 270] f9f02d30 f976b6fa 815ba3a0 81027720 00000000 mydriver!Queue_Packet_Execute+0x7b [C:\Work\Driver\NDIS\queue_packet.c @ 331] f9f02d74 f976bdd5 815ba3a0 00000000 816b1120 mydriver!Queue_Packet_Manage+0xa6 [C:\Work\Driver\NDIS\queue_packet.c @ 396] f9f02dac 8057dfed 815ba3a0 00000000 00000000 mydriver!Queue_Packet_Thread+0xa5 [C:\Work\Driver\NDIS\queue_packet.c @ 505] f9f02ddc 804fa477 f976bd30 815ba3a0 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: mydriver!MPReturnPacket+73 [C:\Work\Driver\NDIS\miniport.c @ 598] f975f58f eb0d jmp mydriver!MPReturnPacket+0x82 (f975f59e) SYMBOL_STACK_INDEX: 1 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: mydriver!MPReturnPacket+73 MODULE_NAME: mydriver IMAGE_NAME: mydriver.sys DEBUG_FLR_IMAGE_TIMESTAMP: 42695faa STACK_COMMAND: .trap fffffffff9f028ec ; kb BUCKET_ID: 0xD1_mydriver!MPReturnPacket+73 Followup: MachineOwner --------- ############################################################################ ######### kd> !ndiskd.pkt 0x81669f30 4 NDIS_PACKET at 81669f30 NDIS_BUFFER at 81606120 Next 00000000 Size 20 MdlFlags c Process 00000000 MappedSystemVa 814d3000 Start VA 814d3000 ByteCount 5ea ByteOffset 0 MacReserved[]: 00000000 00000000 00000000 00000000 0. TcpIpChecksumPacketInfo = 00000000 1. IpSecPacketInfo = 00000000 2. TcpLargeSendPacketInfo = 00000000 3. ClassificationHandlePacketInfo = 00000000 4. NdisReserved = 0000000e 5. ScatterGatherListPacketInfo = 00000000 6. Ieee8021QInfo = 00000000 7. OriginalPacketInfo = 00000103 8. PacketCancelId = 00000000 9. OriginalNetBufferList = 00000000 10. CachedNetBufferList = 00000000 11. MaxPerPacketInfo = 00000000 Packet.Private PhysicalCount 00000000 Total Length 00000000 Head 00000000 Tail 00000000 Pool 00000000 Count 00000000 Flags 00000000 ValidCounts 00 NdisPacketFlags 00000000 NdisPacketOobOffset 0000 Private.Flags : 00000000 Private.NdisPacketFlags: 80 fPACKET_ALLOCATED_BY_NDIS, ############################################################################ ######### kd> !ndiskd.pkt 0x81669f30 5 NDIS_PACKET at 81669f30 MDL = 81606120 StartVa ffffffff814d3000, ByteCount 0x5ea, ByteOffset 0x0, NB MdlOffset 0x0 814d3000: 00 0c 29 5e 75 ca 00 50 56 c0 00 01 08 06 00 01 814d3010: 08 00 06 04 00 02 00 50 56 c0 00 01 0a 01 00 01 814d3020: 00 0c 29 5e 75 ca 0a 01 00 07 00 00 00 00 00 00 814d3030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [zeros skipped] 814d35c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 814d35d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 814d35e0: 00 00 00 00 00 00 00 00 00 00 Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62331
  - 2
    - Device driver programmers in SLC ? I am new to device drivers. Are there any device driver developers in the Salt Lake City, Utah area that I may be able to chatt with? Thanks, John Long john@thelongs.us Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62330
  - 3
    - SetPort (printer driver language monitor) Hi all, I wish the SDK explained the SetPort function better. I'm not really sure what it does other than change the "Status" messages column in the "Printers and Faxes" dialog box. Does it do anything else? I've discovered if I use PORT_STATUS_TYPE_ERROR for dwSeverity that it does seem to hang up the spooler, and I can't seem to clear it later. Thats ok, because I found that PORT_STATUS_TYPE_WARNING is ok for my use. My real question is that I would like to use the pszStatus member of PORT_INFO_3 to display my own messages up there, but it doesn't seem to do anything. The SDK says that if the predefined messages available for dwStatus aren't enough that you can define your own with pszStatus. So, this is what I do: PORT_INFO_3 pi3; pi3.dwStatus = 0; // set to zero because none of these messages apply. pi3.pszStatus = TEXT("My Printer Message"); pi3.dwSeverity = PORT_STATUS_TYPE_WARNING; SetPort(NULL,pPortName,3,LPBYTE(&pi3)); Does anybody have any ideas? Thanks! Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62328
  - 4
    - try/except does not catch all exceptions...? I am trying to use __try/__except to catch crashes that may occur in my driver. It works great for NULL pointer access, but not for a plain bad memory access. If the driver accesses 0xfefefefe (just as a test!), I see a crash in WinDbg, instead of my exception handler getting launched. The crash is below. How do I catch it (and other exceptions) ? PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fefefefe, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: b94ca75d, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) / Hannes. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62321
  - 5
    - INF model section decoration 64-bit Windows2003 AMD64 Hi, I am trying to install 64bit printer driver thru. HW1st on beta version of 64-bit Windows2003 build 3790 v.1433 installed on AMD64 machine. Getting an error "can not Install hardware unable to detect device ID". In printer INF file, I have described the decorated model section for windows2003 in following way. [MANUFACTURER] %ABC%=Models,NTamd64.5.2 // Here 5 is MajorOSversion and 2 is MinorOSVersion [Models.NTamd64.5.2] I have also tried with following model section [Models.NTamd64] Still giving the same error "can not Install hardware" on 64-bit Windows2003. Same model decoration is working fine on 64-bit WindowsXP. When I turnoff the undecorated models check by setting registry variable DisableDecoratedModelsRequirement to 1 then 64-bit printer driver gets installed on 64-bit windows 2003. So, I think problem is with model decoratation for 64-bit windows2003. Can anyone tell me what should be the model decoration for 64-bit Windows2003. thanks in advance regards manoj Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62315
  - 6
    - Ndis - DHCP Hi All, I am making use of netvmini sample(Virtual miniport driver). I have modified the code in such a way that i can change the cable status using control codes which will trigger a NDIS_MEDIA_STATUS_CONNECT and NDIS_MEDIA_STATUS_DISCONNECT in driver. It is working fine. But sometimes though adapter is configured to use static IP, on receiving CONNECT control code which will trigger NDIS_MEDIA_STATUS_CONNECT, the status in the network connections window says "Acquiring network address" . The ip address displayed is 0.0.0.0 but soon after the status becomes connected and it chages back to static IP which i configured . What i observed is this happens with LAN as well as WLAN in my machine when they are configured with static IP. When i unplug and plug network cable of LAN adapter, the same event happens sometimes which results in erratic behavior of sockets. Could anyone let me know how can i fix this?Would be of great help if u could let me know what all are the events happens at "Acquiring network address". Thanks, Senthil Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62309
  - 7
    - Disk class filter driver for back-up mechanism Hi All, I am trying to develop a backup tool. To give the maximum performance, my plan is to write only modified blocks/sectors of source disk into target disk since it was last backed up. How I can collect block/sector information from data write request packet. Can a disk class upper filter solve this problem. Your ideas are welcome regards John Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62308
  - 8
    - Will XP/2k load my driver(oemxx.inf) prior to system-supplied keyboard.inf (HID_DEVICE)? I have a HID DEVICE with 2 function on it - keyboard and mouse compisited chip. I only use the keyboard function and my driver is simply a keyboard filter. When I plug DEVICE into system without my filter driver, system treat it as a HID_KEYBOARD and HID_MOUSE. the question is: 1. If I have a valid .cat file, after perform SetupCopyOEMInf, will XP/2000 load my driver(oemxx.inf) prior to system-supplied keyboard.inf (HID_DEVICE)? ( as I know before have .cat file - won't!) I am very worry about the 'Rank' (to match an best .inf) will larger than keyboard.inf, that's mean my filter driver will never been chosen. Here 's my attachment information, thanks for your comments. Assume the pid/vid is: vid = 1234 pid = 5678 The HardwareId (retrieve from actual devnode): HID\Vid_1234&Pid_5678&Rev_0100&MI_00 HID\Vid_1234&Pid_5678&MI_00 HID_DEVICE_SYSTEM_KEYBOARD (I think it's create by HIDClass) HID_DEVICE_UP:0001_U:0006 HID_DEVICE The .Inf file (simply kbfiltr version): //-------------------------------------------------------------------------------------------- ; Hid device filtr.inf ; ; Installation inf for the Device that needs filtering adapter. ; [Version] Signature="$Windows NT$" Provider=%DDK_Ex% ClassGUID={4D36E96B-E325-11CE-BFC1-08002BE10318} Class=Keyboard ;CatalogFile=Flagfiltr.cat - I am trying to obtain one from WHQL... DriverVer=01/01/2005, 1.0.0.0 [DestinationDirs] DefaultDestDir = 12 [ControlFlags] ExcludeFromSelect = HID\Vid_1234&Pid_5678&Rev_0100&MI_00 ExcludeFromSelect = HID\Vid_1234&Pid_5678&MI_00 ; Driver information ; [Manufacturer] %DDK_Ex% = DDK_Ex.Mfg [DDK_Ex.Mfg] "TEST_1" = Flagfiltr, HID\Vid_1234&Pid_5678&Rev_0100&MI_00 "TEST_2" = Flagfiltr, HID\Vid_1234&Pid_5678&MI_00 ; ; General installation section ; [Flagfiltr.NT] ; perform port related actions from keyboard.inf Include=keyboard.inf Needs= ; Copy the driver over CopyFiles=Flagfiltr.CopyFiles.NT ; ; File sections ; [Flagfiltr.CopyFiles.NT] Flagfiltr.sys ; ; Service Installation ; [Flagfiltr.NT.Services] AddService = Flagfiltr, , Flagfiltr_Service_Inst ; Install the port driver and mouclass from keyboard.inf Include=keyboard.inf Needs= [Flagfiltr_Service_Inst] DisplayName = %Flagfiltr.SvcDesc% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 0 ; SERVICE_ERROR_IGNORE LoadOrderGroup = Keyboard Port ServiceBinary = %12%\Flagfiltr.sys [Flagfiltr.NT.HW] ; Add the device upper filter AddReg = Flagfiltr.NT.HW.AddReg ; run the directives need by the port driver Include=keyboard.inf Needs= [Flagfiltr.NT.HW.AddReg] HKR,,"UpperFilters",0x00010000,"Flagfiltr" ; ; Source file information ; ; use [SourceDisksNames.x86] for x86 only installs ; use [SourceDisksNames.alpha] for alpha only installs [SourceDisksNames] 1 = %DiskId1%,,, [SourceDisksFiles] Flagfiltr.sys = 1,, [Strings] ; ; Non-Localizable Strings ; REG_SZ = 0x00000000 REG_MULTI_SZ = 0x00010000 REG_EXPAND_SZ = 0x00020000 REG_BINARY = 0x00000001 REG_DWORD = 0x00010001 SERVICEROOT = "System\CurrentControlSet\Services" ; ; Localizable Strings ; DiskId1 = "TEST" DDK_Ex = "TEST" Flagfiltr.SvcDesc= "TEST" Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62306
  - 9
    - Link between setup classes and interface classes. Dear All, I would like to communicate directly with USB and parallel local printers using CreateFile, WriteFile and ReadFile functions from the Windows API. To retrieve local printers connected to a PC, I used the setupapi with the printer setup class as follow : SetupDiGetClassDevs(&GUID_DEVCLASS_PRINTER, 0, 0, DIGCF_PRESENT); Then I could enumerate the printers using SetupDiEnumDeviceInfo (). To communicate with the printers using CreateFile, WriteFile and ReadFile functions, I figured out I had to retrieve the "symbolic name" of the printers using SetupDiGetDeviceInterfaceDetail (). How can I get the device interfaces of the printers I retrieved using SetupDiEnumDeviceInfo () ? What is the link between setup class and interface class ? Best regards, Guillaume. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62304
  - 10
    - How to completely remove AVSSAMP from windows ? first, i run script to see avssamp device in device manager applet set devmgr_show_nonpresent_devices=1 cd\%SystemRoot%\System32 start devmgmt.msc then i success use uninstall. now it'is removed. but after the few minutes, window find again this device and asks me about how to install in, like: Found new MEDIA... Why it asks me again and again ? Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62302
  - 11
    - Get service pack name from a driver? Hi, From within a driver, I want to get the string name of the service pack, e.g. "Service Pack 1, v.1247" The function PsGetVersion() is supposed to do the trick, but I can't get a string out of it, neither from within DriverEntry, nor any other point in my driver. (I do get other version info from PsGetVersion() though, but not the SP name.) Is there any other way to get the service pack name string from within a driver? Thanks, / Hannes. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62291
  - 12
    - Application can't be killed while on a synchronous read I wrote a driver that is not allowing a console application which is blocked on a synchronous ReadFile() to be killed (ctrl-C or taskmanager). Nor can I remove the driver with out rebooting the system. What am I doing wrong -- details below. I have created a pure software driver that reads and writes from an internal buffer. If data is available the read IRP it will complete immedately, else it will PEND. A Device I/O Control is used to indicate that data is available, and if a read IRP is pending will complete it. I have tested with a TestRead.exe that syncrhonously reads the device and a TestRelease program that writes and sends the IOCTL_RELEASE_READ. Things work fine with the test program interaction, immediately reading or blocking until data is availalbe. HOWEVER, when I run the TestRead and it blocks I can not Ctrl-C the program or use the TaskManager to kill the program. Why is this? I understood that the I/O Manager was support to clean all the synchronous calls/Reads and allow exit of the program, but this is not happening. What am I missing? Below are what I believe to be the critical pieces: NTSTATUS DispatchRead (IN PDEVICE_OBJECT pDevObj, IN PIRP pIrp) { NTSTATUS status = STATUS_SUCCESS; [ declarations ...] PDEVICE_EXTENSION pDevExt = (PDEVICE_EXTENSION) pDevObj->DeviceExtension; if (pDevExt->bDataReady) { [fill read buffer ...] // Now complete the IRP pIrp->IoStatus.Status = status; pIrp->IoStatus.Information = nBytes; // bytes xfered IoCompleteRequest( pIrp, IO_NO_INCREMENT ); return status; } else { pDevExt->pIrpPendingRead = pIrp; // save pointer to IRP status = STATUS_PENDING; IoMarkIrpPending(pIrp); pIrp->IoStatus.Status = status; pIrp->IoStatus.Information = 0; // bytes xfered return status; } } NTSTATUS DispatchIoControl(IN PDEVICE_OBJECT pDevObj, IN PIRP pIrp ) { PIO_STACK_LOCATION pIrpStack = IoGetCurrentIrpStackLocation( pIrp ); PDEVICE_EXTENSION pDevExt = (PDEVICE_EXTENSION) pDevObj->DeviceExtension; // Release read is send when data is available if (pIrpStack->Parameters.DeviceIoControl.IoControlCode == IOCTL_RELEASE_READ ) { if (pDevExt->pIrpPendingRead == NULL) { pDevExt->bDataReady = TRUE } else { // The stack location contains the user buffer info PIO_STACK_LOCATION pPendingIrpStack = IoGetCurrentIrpStackLocation( pDevExt->pIrpPendingRead ); [decls and read Irp buffer copy stuff ...] // Complete Pending Read IRP pDevExt->pIrpPendingRead->IoStatus.Information = nBytes; pDevExt->pIrpPendingRead->IoStatus.Status = STATUS_SUCCESS; IoCompleteRequest( pDevExt->pIrpPendingRead, IO_NO_INCREMENT ); pDevExt->pIrpPendingRead = NULL; // "remove from queue of one" } // Complete Device IO Irp pIrp->IoStatus.Information = pDevExt->bSetPendingRead; pIrp->IoStatus.Status = STATUS_SUCCESS; IoCompleteRequest( pIrp, IO_NO_INCREMENT ); return STATUS_SUCCESS; } else { [ not implemented completion of IRP ...] return status; } } Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62284
  - 13
    - question on USB pipe flags Hello. My device is USB composite (1.1), and the interface I am working on is for ASIO (audio) streaming. I have two questions for USB pipe flags: a) What do USBD_PF_ENABLE_RT_THREAD_ACCESS and USBD_PF_MAP_ADD_TRANSFERS actually do? The DDK says that the former is enables optimization for streaming transfers while the latter enables "fast isochronous mode". Can anyone shed light on what these actually do? b) Since I have a composite device, I use URB_FUNCTION_SELECT_INTERFACE instead of URB_FUNCTION_SELECT_CONFIGURATION to allocate bandwidth and receive my pipes. However, the DDK implies that the aforementioned flags (see above) work for URB_FUNCTION_SELECT_CONFIGURATION. Does this mean that they are inaccessible to me, as I am forced to use these flags in my URB_FUNCTION_SELECT_INTERFACE request? thanks, Philip Lukidis Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62281
  - 14
    - *InputDataConsumed always = 0 (moufiltr) Hi everyone, I found that in MouFilter_ServiceCallback the input data always contain one packet (InputDataStart + 1 = InputDataEnd) but *InputDataConsumed always = 0 (I don't know if this parameter is used by any other driver, eg. mouclass). Can anyone explain this? Thanks in advance. Liang Fu Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62280
  - 15
    - DrvTextOut Font Outlines Hi, I am trying to write a printer driver that saves the output data in vector format in a file. When dealing with TrueType fonts the gdi calls the DrvTextOut function but with bitmap glyphs. I want to get outlines of the characters instead. I have set the following for the various related paramters: DrvDeviceCapabilities: DC_TRUETYPE - returns 0 DEVMODE: dmTTOption = DMTT_DOWNLOAD_OUTLINE DEVINFO: flGraphicsCaps = GCAPS_ALTERNATEFILL | GCAPS_HORIZSTRIKE | GCAPS_VERTSTRIKE | GCAPS_VECTORFONT | GCAPS_FONT_RASTERIZER | GCAPS_GEOMETRICWIDE | GCAPS_HALFTONE | GCAPS_OPAQUERECT GCAPS_GRAY16; GDIINFO: ulTechnology = DT_RASPRINTER; Is there some specific setting that forces the GDI to always send font outlines or is it just not possible in some cases? Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62278
  - 16
    - Audio Delay From Audio Capture Source Filter Dear All: I designed a AVstream driver with video and audio streams. Then, using the graphedit to play and capture it. The audio stream is offered from Audio Capture Source (qcap.dll). The video stream is offered from Video Capture Source filter's capture pin. However, the audio sound has a serious dealy (about 1 ~ 2 sec) to video in previewing. But, its captured avi file is AV-Sync well. This is my driver's bug? I had tried other video devices (USB2.0 Video Grabber). Their preview and capture are AV-Sync both. The USB device is a standard USB Audio Class device. It uses Microsoft's USBAUDIO.sys driver. Why cannot MS's driver cause the preview delay? Best Regards, H.P. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62277
  - 17
    - Does WinDBG follow into SEH finally{}? Hello, when I debug my driver and something went wrong, I can't see (with WinDBG) that the code inside finally{} is executed. AFAIK the code inside finally is _always_ executed, so I assume that WinDBG isn't following. Is this true? Thank you for your efforts! -- phren Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62268
  - 18
    - Audio formats supported by UsbAudio.sys? Is there a listing somewhere with the formats supported by UsbAudio.sys in Windows 2000 and XP? Leo Havmøller. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62267
  - 19
    - MUX driver Virtual Interfaces appear as Network Cable Unplugged hi all, I was creating Virtual Adapters following the MUX Sample. I am using INetCfg interfaces to Install (INetCfgClass->Install) function using my own application instead of using the notify objects as in sample. The problem is that network interfaces do appear in the Network Connection Interfaces but they all appear as Unplugged, but with the sample when i create the new virtual adapter they all are normal and are connected. I am not able to understand the problem. Is the binding to the lower adapter not happening properly ?? Can somebody explain ? Thanks in advance. Regards Tarun Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62265
  - 20
    - How to use DbgPrompt in drivers? Dear All, Recently I read the article "Try This -- Interactive Driver Testing" (The NT Inside, Vol 11). It introduces a minimal driver skeleton. I tried to build the code, but encountered a compiler error. The code uses the function "DbgPrompt". But there is no declaration of DbgPrompt in any *.h files in Win DDK (2600). And there is no information about this function in DDK's help. I have noted that the function is exported by ntoskrnl.lib. So I added "TARGETLIBS=$(DDK_LIB_PATH)\ntoskrnl.lib" in "source" file. But I still need to know the declaration of the function "DbgPrompt". Can anyone tell me about this or how to use "DbgPrompt" in drivers. Thanks in advance. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62264
  - 21
    - STATUS_REPARSE across network share Hello Everybody, I have a filter driver that uses STATUS_REPARSE to redirect file opens in its IRP_MJ_CREATE routine as documented in this list and many other places (http://support.microsoft.com/default.aspx?scid=kb;en-us;319447). The actual files reside on a network share (e.g. reparsed to \device\mup\server\share). This technique works well for IO requests originating from the local system however if the request comes across the network (e.g. via SRV) it fails with 'access denied'. This is obviuosly becasue the access request is in the context of the system. My question is this: is it possible to make this work using impersonation or delegation, or do I need an etirely different approach to the problem? Thanks in advance for any help or advice, zengfeng. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62260
  - 22
    - Get temperature values from the cpu/motherboard How can I get temperature values from the CPU and motherboard of a machine? I've try querying WMI (using IWbem_ methods with win32_temperatureprobe), which hasn't worked - it says the temperature sensors don't exist. Is there some other way I can get this data? Note: project also requires getting CPU usage info, which I've already done through WMI, so a WMI solution to getting the temperature values is preferable, but not necessary. Thanks! Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62254
  - 23
    - WDM capture driver and MPEG-2 video. I am trying to configure the capture Pin format on the WDM capture driver to support MPEG2_Video. We already have the stuff working for a Program stream, but we want to try out something using Mpeg2_Video for testing purposes. I have tried something as I have shown below, but somehow the capture spin of the driver doesnt connect to any downstream decoder filter when I set for MPEG2_Video format. Is there something that I could be doing wrong ? Here is the way I am configuring the KS_DATARANGE_MPEG2_VIDEO required in this case. Any help is appreciated. static KS_DATARANGE_MPEG2_VIDEO Mpeg2Stream = { //KSDATARANGE { sizeof(KS_DATARANGE_MPEG2_VIDEO) + sizeof(SequenceHeader) - 1, 0, 0, 0, STATIC_KSDATAFORMAT_TYPE_VIDEO, STATIC_KSDATAFORMAT_SUBTYPE_MPEG2_VIDEO, STATIC_KSDATAFORMAT_SPECIFIER_MPEG2_VIDEO }, TRUE, 0, 0, 0, // _KS_VIDEO_STREAM_CONFIG_CAPS { STATIC_KSDATAFORMAT_SPECIFIER_MPEG2_VIDEO, // GUID KS_AnalogVideo_None, // 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 8, // CropGranularityX, granularity of cropping size 1, // CropGranularityY 8, // CropAlignX, alignment of cropping rect 1, // CropAlignY; 160, 120, // MinOutputSize, smallest bitmap stream can produce 720, 480, // MaxOutputSize, largest bitmap stream can produce 8, // 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 * 3 * 30 * 160 * 120, // MinBitsPerSecond; 8 * 3 * 30 * 720 * 480 // MaxBitsPerSecond; }, //KS_MPEGVIDEOINFO2 { //KS_VIDEOINFOHEADER2 { 0, 0, 720, 480, 0, 0, 0, 0, 0x003d0900, 0, 0x0000000000051763, 0, 0, 4, 3, 0, 0, { sizeof (KS_BITMAPINFOHEADER), // DWORD biSize; 0x000002d0, 0x000001e0, 0, 0, 0, 0, 0x000007d0, 0x0000cf27, 0, 0 } }, 0x0006f498, 1, KS_MPEG2Profile_Main, KS_MPEG2Level_Main, 0, (DWORD)SequenceHeader } }; the SequenceHeader is the sequence Header array that is supposed to be passed. Thanks. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62242
  - 24
    - If a file system filter driver is installed using DIFxAPP, does it show up in Device Manager? Previously, with our manual method of installing a file system filter driver, I could go into Device Manager, right click on the top tree entry, select "Show Hidden Devices" and a "Non Plug and Play Devices" entry would magically appear. Our device driver would be there. From that I can stop/start and set the start type. I've just gotten a device install working with DIFxApp, and it doesn't seem to be available there. Is this the way it is supposed to be? How do I change the start type to manual (for instance), without going into regedit? Thanks, Bob Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62239
  - 25
    - Uninstalling a file system filter driver with DIFxApp When uninstalling a filter driver with DIFxApp, I notice that it doesn't remove the actual .sys file from c:\windows\system32\drivers. This is a violation of the Certified for Windows test. In looking through the DIFxApp.doc supplied by MS, there is a section that describes the uninstall steps, and by George, it doesn't mention deleting the installed files. From the DIFxApp.doc whitepaper: · Removes the driver package from the Driver Store. (Bob: I'm assuming this doesn't mean remove the actual driver file. This has to do with the .inf and .cat, right?) · Updates the association between the service, the driver, and applications. For more information, see "Associating Services, Driver Packages, and Applications" later in this paper. · Deletes the corresponding entry for the driver package in Add or Remove Programs. (Bob: actually no add/remove entry was created) Is it okay to leave these files there, or is there a way to get them deleted? Thanks! Bob Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62238
- Next
  - 1
    - DIFxApp available for amd64 CPU? The version 1.1 SDK I found contains only ia64 and x86 code. For AMD64, can I use the x86 DLL's? Thanks, Bob Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62237
  - 2
    - DIFxApp is failing - saying drivers are unsigned when they are! I've gone through hell to get this far: Using Installshield X, ran their "Device Driver Wizard" hand-fiddled the tables so they compile correctly got a valid code signing Certificate from Verisign created a catalog pointing to the .inf and .sys files SIGNED the damn catalog file when I run setup, I get the following: DIFXAPP: InstallDriverPackages DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 1.1. DIFXAPP: 'CustomActionData' property 'UI Level' is 5. DIFXAPP: 'CustomActionData' property 'componentId' is {33C87C1F-F8A4-4834-9F3D-A9026D067632}. DIFXAPP: 'CustomActionData' property 'componentPath' is C:\Program Files\FBN product\driver\. DIFXAPP: 'CustomActionData' property 'flags' is 0x3. DIFXAPP: 'CustomActionData' property 'installState' is 2. DIFXAPP: 'CustomActionData' property 'ProductName' is Product. DIFXAPP: 'CustomActionData' property 'ManufacturerName' is FBN Industries. DIFXAPP: Analyzing driver package "C:\Program Files\FBN product\driver\driver.inf". DIFXAPP: Driver package 'C:\Program Files\FBN product\driver\driver.inf' is unsigned. Error code 0x800B0100. DIFXAPP: ERROR 0x800B0100 encountered while adding driver package C:\Program Files\FBN product\driver\driver.inf to the driver store DIFXAPP: InstallDriverPackages failed with error 0x800B0100 Action ended 14:26:21: InstallFinalize. Return value 3. As far as I can tell, the thing is signed (using 'signcode.exe'). If I use chktrust: > chktrust -v driver.cat It displays the certificate. Any ideas???? Thanks for any guidance. Bob Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62235
  - 3
    - create a opentype or truetype "file" from FONTOBJ Hi I have to send the font related to a FONTOBJ to an other computer. So I have to get the whole "font file" ... but, since it doesn't have to be a file always (embedded fonts etc.), I don't want to use the functions that return the filenames to find the data. So I'd like to build the file using functions like FONTOBJ_pjOpenTypeTablePointer and FONTOBJ_cGetAllGlyphHandles and FONTOBJ_cGetGlyphs ... I think this should be possible (at least for truetype and opentype)... but my problem is, that I don't understand how to handle those tables. What tables are required? How is a opentype/truetype font structured? ... can someone explain me this? ... and could this work, what I'd like to do? thanks MR Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62232
  - 4
    - Use of RtlCheckRegistryKey in WDM driver? My WDM driver needs to know if a particular registry key exists The following code fails with a 3C status even when the reg path exists UNICODE_STRING uszTemp; OBJECT_ATTRIBUTES ObjAttrs; KEY_VALUE_PARTIAL_INFORMATION valueInfo; UNICODE_STRING uszName; RtlInitUnicodeString(&uszTemp,"\\Registry\\Machine\\SOFTWARE\\xxx"); InitializeObjectAttributes(&ObjAttrs, &uszTemp, OBJ_KERNEL_HANDLE|OBJ_CASE_INSENSITIVE, NULL, NULL); RtlFillMemory(&valueInfo, sizeof(KEY_VALUE_PARTIAL_INFORMATION), 0x0); RtlInitUnicodeString(&uszName, L"yyy"); status = ZwOpenKey(&KeyHandle, KEY_READ, &ObjAttrs); By contrast, RtlCheckRegistryKey(RTL_REGISTRY_ABSOLUTE,L"\\Registry\\Machine\\SOFTWARE\\xxx\\yyy") returns STATUS_SUCCESS However RtlCheckRegistryKey only exists in ntddk.h. and does not exists in wdm.h This strongly hints that RtlCheckRegistryKey should NOT be used in a wdm driver. What do other people do? Is there a wdm.h compatible alternative to RtlCheckRegistryKey or a way of making ZwOpenKey work? Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62221
  - 5
    - Please : Need help about Port monitor Hello, Sorry, because I have already ask this question but I really need help on this topic. I made my own port monitor, and all works fine except at the starting of the spooler : all my printers which are connected to the ports managed by my port monitor, stay offline in the printer folder. I'm obliged to click manually on the menu "Use printer online" to start printing. Why does the print spooler indicates this state ? Do I forget anything in my port monitor ? I see that the print spooler can call SetPort or GetPort to retrieve information from Ports. Is there a relationship between this function and the behaviour that I can see. Thanks in advance for your replies. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62218
  - 6
    - AttachedToDeviceObject unloaded? Hi All. I'm making my first steps in the File System Drivers programming world, so this question might not be very intelligent or challenging. I've followed the SFilter sample from IFS Kit in order to build my driver. In the sample, I've noticed the use of IoAttachDeviceToDeviceStack (or IoAttachDeviceToDeviceStackSafe). This function, if I understand correctly, is supposed to return the actual device that is directly "below" mine in the device stack. This device can be different from the device I was initially trying to hook, if other devices were already layered on top of it. Let's say I initialize the AttachedToDeviceObject member of my device's extension with the value returned from IoAttachDeviceToDeviceStack, like I understood I should. I Later pass my AttachedToDeviceObject value to IoCreateFileSpecifyDeviceObjectHint . What I couldn't figure out, is what happens if the device pointed to by AttachedToDeviceObject, which is the one that was between me and my target device when I hooked, gets unloaded. Does my AttachedToDeviceObject value reference uninitialized memory, and is therefore likely to cause a blue screen? As I have failed to find a way to discover the next device in stack dynamically, how can I overcome this hazard? Someone on osronline explained to me that the filter driver that is under mine should take care of that if it's unloaded, but I couldn't understand how is it supposed to change the pointer in my extension (AttachedToDeviceObject)? any help would be greatly appreciated. thanks. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62210
  - 7
    - BulkUSB driver unstable on Laptop w/XP Hello, I am still a relative noob in the world of device drivers. I have had some success in the past but recently I have developed a problem that I can't find my way through. When I started I followed the Oney recommendations and selected a sample driver to start from. In this case I started with the sample BulkUSB driver source from the DDK. I adjusted the necessary block/buffer sizes to meet my device requirements and added IOCTL ID macros until I was able to do everything I needed. I compiled it and installed on Win2k. [and the crowd went wild] More recently I have replaced my development machine (the win2k laptop) with a new a new XP laptop. I am now paying for the relative ease with which I acquired my working DD. When I plug my device in to this laptop I frequently but not always get the BSOD! Before I enabled legacy support in the laptop firmware I got the BSOD whenever the device was attached...even on reboot. I am more prone to distrust my driver's completeness than any sort of odd hardware incompatibilities but really I don't have a basis for that either. I am at a loss where to go from here. I am certain that before too long someone who has one of our devices will hit this situation. I want to solve it before that. I have rebuilt the driver in the XP build environment of the DDK. That initially appeared to help but then the BSOD started re-appearing. I can provide much more information but I don't know what is relevant and what is not. This is a simple bulkUSB device. It has 2 endpoints (1 out, 1 in). When I don't get the BSOD everything works pretty much the way I want it to. Hopefully someone here has a tip that might nudge me in the right direction. TIA, Kevin Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62205
  - 8
    - problem with virtual audio driver Hi everybody, I built the DDK samples related to virtual audio drivers (MSVAD). When I install it and use it, the virtual audio driver is supposed to write to wave files (and store them in C:\ by default) what we would normally hear (all the played sounds). But it only works the first time. The first played sound is well recorded (until the end of the buffer) but then, only empty ("corrupted" according to winamp...) wave files (44 bytes) are generated. Any idea to solve this problem ? Best regards, Giuseppe Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62203
  - 9
    - Enumerating drivers Hi, how can I programmatically (in any .net language) receive a list of all network drivers bound to a network adapter? (I need to check if some specific driver is bound to the adapter - and then possibly (de)activate this one). is this possible? Thanks Peter Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62193
  - 10
    - About USB bulktransfer error... Hi, all: I wrote a usb client device driver for wireless modem on WinCE.NET 4.2. And my driver have passed the usb enumeration process sucessfully. When executing IssueBulkTransfer() to write data to wireless modem, then wait_timeout occurred. Could someone tell me why? Thanks!! -Kemin The log msg are as following: 4294896994 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write wait for CritSec 50b40. 4294896995 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write Got CritSec 50b40. 4294896996 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write wait for CritSec 50c14. 4294896997 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write got CritSec 50c14. 4294896997 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write released CritSec: 50c14. 4294896998 PID:63c7872a TID:2387cfb2 0x8386db70: DoPutBytes wait for CritSec 50c14. 4294896999 PID:63c7872a TID:2387cfb2 0x8386db70: DoPutBytes got CritSec 50c14. 4294897000 PID:63c7872a TID:2387cfb2 0x8386db70: TxRead = 0, TxLength = 3, TxBytesAvail = 3. 4294897000 PID:63c7872a TID:2387cfb2 0x8386db70: About to copy 3 bytes 4294897001 PID:63c7872a TID:2387cfb2 0x8386db70: +SerTxIntr 0x4FEC0 4294897002 PID:63c7872a TID:2387cfb2 0x8386db70: >USBCDC_Write(0xe018854, 3) 4294897002 PID:63c7872a TID:2387cfb2 0x8386db70: USBCDC_Write timeout due in 606 msec 4294897003 PID:63c7872a TID:2387cfb2 0x8386db70: +USBD:IssueBulkTransfer, pipe:50730, dwFlags:0x0, Bufsize: 3 vBuf:0xE018854, pBuf:0x0 4294897005 PID:63c7872a TID:2387cfb2 +CHcd::IssueTransfer - address = 66, pipe = 5, dwFlags = 0x0, lpvControlHeader = 0x0, lpvBuffer = 0xe018854, dwBufferSize = 3 4294897007 PID:63c7872a TID:2387cfb2 +CHub(Root tier 0)::IssueTransfer, address = 66, pipe = 5 4294897008 PID:63c7872a TID:2387cfb2 +CHub(External tier 1)::IssueTransfer, address = 66, pipe = 5 4294897010 PID:63c7872a TID:2387cfb2 +CFunction(tier 2)::IssueTransfer 4294897011 PID:63c7872a TID:2387cfb2 +CPipe(Bulk)::IssueTransfer, address = 66 4294897012 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897012 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897013 PID:63c7872a TID:2387cfb2 +CBulkPipe::GetNumTDsNeeded 4294897014 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897015 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897015 PID:63c7872a TID:2387cfb2 -CBulkPipe::GetNumTDsNeeded, returning 1 4294897016 PID:63c7872a TID:2387cfb2 +CBulkPipe::AddTransfer 4294897017 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897018 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897019 PID:63c7872a TID:2387cfb2 CBulkPipe::AddTransfer dwFlags(0x0), packetsize=0x40 4294897019 PID:63c7872a TID:2387cfb2 -CBulkPipe::AddTransfer, returning success 4294897020 PID:63c7872a TID:2387cfb2 +CBulkPipe::ScheduleTransfer 4294897021 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897022 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897023 PID:63c7872a TID:2387cfb2 +CPipe::AddToBusyPipeList - new pipe(Bulk) 0x50780, pri 0 4294897024 PID:63c7872a TID:2387cfb2 -CPipe::AddToBusyPipeList - new pipe(Bulk) 0x50780, pri 0, returning BOOL 1 4294897026 PID:63c7872a TID:2387cfb2 +CUHCIFrame::HandleReclamationLoadChange - Add Reclamation Transfer 4294897026 PID:63c7872a TID:2387cfb2 -CUHCIFrame::HandleReclamationLoadChange - Add Reclamation Transfer 4294897030 PID:63c7872a TID:2387cfb2 -CBulkPipe::ScheduleTransfer, returning HCD_REQUEST_STATUS 1 4294897031 PID:63c7872a TID:2387cfb2 -CPipe(Bulk)::IssueTransfer - address = 66, returing HCD_REQUEST_STATUS 1 4294897033 PID:63c7872a TID:2387cfb2 -CFunction(tier 2)::IssueTransfer - returing HCD_REQUEST_STATUS 1 4294897035 PID:63c7872a TID:2387cfb2 -CHub(External tier 1)::IssueTransfer address = 66, pipe = 5, returing HCD_REQUEST_STATUS 1 4294897035 PID:63c7872a TID:2387cfb2 -CHub(Root tier 0)::IssueTransfer address = 66, pipe = 5, returing HCD_REQUEST_STATUS 1 4294897037 PID:63c7872a TID:2387cfb2 -CHcd::IssueTransfer - returing BOOL 1 4294897038 PID:63c7872a TID:2387cfb2 0x8386db70: -USBD:IssueBulkTransfer, pTransfer:0x520E0 4294897646 PID:63c7872a TID:2387cfb2 0x8386db70: OUT:WAIT_TIMEOUT on hT:0x520e0 Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62190
  - 11
    - About capture stream data in bda Hi, I wrote two bda filters (tuner/demod, and capture), but now, I puzzled where could I capture the stream from device. First, I thought that it should be in tuner/demod filter. So I reviewed the generictuner, the sample with ddk, but I failed to find any usefull information whithin it. And I reviewed the capturesample too, it seemed that the routine Process dealt with the stream data, but I don't know where the stream came from. Could you give me some instructions? Any comments are welcome! Advance thanks! William Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62189
  - 12
    - 802.11 channel How do I get the 802.11 channel of the AP that my adapter is assocaited with? Thanks Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62164
  - 13
    - Is it 802.11a, 802.11b, or 802.11g? If DDK says: typedef enum _NDIS_802_11_NETWORK_TYPE { Ndis802_11FH, Ndis802_11DS, Ndis802_11OFDM5, Ndis802_11OFDM24, Ndis802_11NetworkTypeMax } NDIS_802_11_NETWORK_TYPE, *PNDIS_802_11_NETWORK_TYPE; Is this true: 802.11b = Ndis802_11FH or Ndis802_11DS 802.11a = Ndis802_11OFDM5 802.11g = Ndis802_11OFDM24 Thanks Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62163
  - 14
    - About using IoCompleteRequest and iostatus block's Status Field. Respected sir, I want to know as to, when I use the IoCompleteRequest Function in the DispatchPnp Routine/Function, and that, when I also set the IoStatus block's Status Field to STATUS_ PENDING (pending because I want to make use of pending irp in the driver's system thread to process pnp irp_mn_xxx minor codes), my driver don't seem to work ? I want to set the IRP Pending Status in the Status Field of IoStatus Block, in order to make further use of the IRP, which I already been marked as STATUS_PENDING, in my driver's System Thread to further process IRP_MJ_XXX AND ITS MINOR CODES like irp_mn_start_xxx etc. At the same time, I may also like to know as to, how can I allocate IRP, when my driver is running the system thread ? Which Function should I use (minor pnp codes like irp_mn_xxx ) to pass down the io_resource_requirements_list to make sure that pnp manager and OS must know the resources available thereof. How can I set the IRP in pending state and also how can I make use of this PENDING IRP in the driver's system thread in order to process IRP_MJ_XXX AND IRP_MN_XXX both, major and minor codes respectively ? How can I make sure that, the default resource descriptors, which are already been setted up by the driver will not overwritten i.e. to protect already stored default resource information and at the same time to store additional resource descriptors to IO_RESOURCE_REQUIREMENTS_LIST, so that, PNP MANAGER AND OS will know about the additional resource info., that I provided with. As it is also crucially needed in my case. regards, sudhanshu Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62158
  - 15
    - Memory Mapped Files Reading and Cache Problem Hello Gurus I am writing a File System filter driver having Encrypt/Decrypt. I am using filemon as an example code. In order to solve the memory mapped file issue i have created a new structure of FCB. In that FCB i had specified the structure of FSRTL_COMMON_FCB_HEADER , SECTION_OBJECT_POINTERS and ERESOURCE for MainResource and PagingResource. After creating this I initialize the FSRTL_COMMON_FCB_HEADER to my fileobject->FsContext and fileobject->SectionObjectPointer to my new SectionObjectPointer. My new SectionObjectPOinter has all the 2 members namely the Data,Image set to NULL. I also initialize the MainResource and PagingResource using ExInitializeResourceLite. I do this in my IRP_MJ_CREATE and when i recv a IRP_MJ_CLEANUP i traverse my list for my SectionObjectPOinter and then delete the corresponding FSRTL_COMMON_FCB_HEADER that i had allocated. Actually i keep both the sectionobjectpointer and COmmonFCBHeader in a Link list from which i traverse and delete it. I actually got this by referring some of the posts in this forum. But i know i am missing something because it does not work yet. If i create a rich text document and then edit it and type in some new contents and then open it again i get the garbled text i mean the encyrpted text. the same thing happens for bmp files as well. When i click it again i get the IRP_MJ_READ with CACHE set.Hence my ReadWrite Handler does not decyrpt it as its from the Cache. But still it displays as Encrypted. Any Hints on where i can be going wrong is greatly appreciated. Thanks and Best Regards Shal. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62157
  - 16
    - Errors with USB Bulk requests When our USB function driver is used in a loop or for a long transfer of data (MBs) on a Bulk endpoint, after a short period of time the I/O status (IRP) returns a failure but the URB status is successful. This is after hundreds of successful requests. The IRP errors have been STATUS_IO_DEVICE_ERROR or STATUS_IO_TIMEOUT. The URB status is USBD_STATUS_SUCCESS in either case. In what conditions would the Windows USB stack return these errors and the URB be successful? Second question, when testing for IRP error codes from a IOCTL_INTERNAL_USB_SUBMIT_URB request, which I/O status should be tested? IO_STATUS_BLOCK ioStatus = { 0, 0 }; PIRP irp = IoBuildDeviceIoControlRequest(...., &ioStatus); // Boilerplate code... ntStatus = IoCallDriver(pdx->lowerDeviceObject, irp); if (ntStatus == STATUS_PENDING) // Wait on event At this point is io.Status.Status == irp->IoStatus.Status ???? If not, which is the proper method?? Thanks, SteveB, MCSD Welch Allyn, Inc. Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62147
  - 17
    - network interface name I wanted to get the network interface name which gets stored under hklm\system\currentcontrolset\control\network\connection\name, during the initialization of my miniport driver. the read fails during the initialization and when i disable/enable the interface, I am able to get the registry key. So when does ndis update this registry entry? thanks sophia Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62144
  - 18
    - Error : INVALID_PIPE_HANDLE on Interrupt pipe 0x81 (USB) Hi, I had developed a minidriver in DDK for a USB keyboard controller which supported polling for interrupt pipe on 0x81 and a vendor request - write operations. It was working fine. The development was done on Cypress FX2 kit. Now I'm trying to use the same driver for USBN9603. But here am facing a prob. The enumeartion part is correct. Am able to do many transactions, like reading device desc, config desc, resetting the pipe etc, on the control endpoint. However if am starting any transaction on the pipe 0x81(Interrupt), the IRP is returning with the following error, ALWAYS : IRP error code : 0xc0000008 URB error : 0x80000300 The pipe handle is got from the 0x81 pipe's USBD_PIPE_INFORMATION structure only, while parsing the configuration descriptor. What could be wrong? I would appreciate any help on this matter. One more point is, the same driver has been working properly for another board based on Cypress FX2 board. Expecting help... Thanks Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62143
  - 19
    - FileObject's DeviceObject to whose DeviceObject does the FileObject for the file C:\abc.txt belongs. is it the FSD? i want to know this becasue C: is a symbolic link created by disk driver. ...Mani Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62142
  - 20
    - debugging laptop i want to debug my driver on laptop. it does not have COM1 port. how to proceed. ...Mani Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62141
  - 21
    - HID minidriver crash on reading endp Hi List, I developing a HID minidriver for a non-HID USB device. My problems beguns with "IOCTL_HID_READ_REPORT" HID request ! First, I get infinite loop that consume 99% cpu due to "ping-pong" IRPs, so in DriverEntry I set HID_MINIDRIVER_REGISTRATION.DevicesArePolled to TRUE ! The I add calls to read device's interrupt endpoint data, but now driver crash :o( Sometime I able to get an USB status error code : 0x80000600 (invalid pipe handle). This handle is the one I get after a call to USBD_CreateConfigurationRequestEx() + IoCallDriver() The problem is that source code is the same as samples I get from differents sources. So, does the HID request is donen a a specific IRQL ? Does I miss something ? Thaks for help. Benoit Here the source code : NTSTATUS IoctlReadReport(PDEVICE_OBJECT yFdo, PIRP yIrp, PIO_STATUS_BLOCK yStatus) { PIO_STACK_LOCATION pwIrpStack; ULONG ulOutBufferLen; PVOID pcBufferOutPtr; PDEVICE_EXTENSION pwPDX; // Get all IOCTL info pwIrpStack = IoGetCurrentIrpStackLocation(yIrp); ulOutBufferLen = pwIrpStack->Parameters.DeviceIoControl.OutputBufferLength; pcBufferOutPtr = yIrp->UserBuffer; pwPDX = GET_PDX(yFdo); // Get repôrt descriptor if (ulOutBufferLen >= sizeof (IR_REPORT)) { PURB pwUrbPtr = NULL; pwUrbPtr = ExAllocatePool(NonPagedPool, sizeof (struct _URB_BULK_OR_INTERRUPT_TRANSFER)); if (pwUrbPtr != NULL) { // Read report from Device UsbBuildInterruptOrBulkTransferRequest( pwUrbPtr, sizeof (struct _URB_BULK_OR_INTERRUPT_TRANSFER), &pwPDX->InteruptEndpHdl, &pwPDX->HidReport, NULL, sizeof (pwPDX->HidReport), USBD_TRANSFER_DIRECTION_IN | USBD_SHORT_TRANSFER_OK, NULL); yStatus->Status = UrbSendCompletion(yFdo, pwUrbPtr); if (NT_SUCCESS(yStatus->Status)) { // Send report to HIDClass RtlCopyMemory(pcBufferOutPtr, &pwPDX->HidReport, sizeof (pwPDX->HidReport)); yStatus->Information = sizeof (IR_REPORT); } else { yStatus->Information = 0; } // Clean ExFreePool(pwUrbPtr); } else { yStatus->Information = 0; yStatus->Status = STATUS_INSUFFICIENT_RESOURCES; } } else { yStatus->Information = 0; yStatus->Status = STATUS_BUFFER_TOO_SMALL; } return yStatus->Status; } NTSTATUS UrbSendCompletion(IN PDEVICE_OBJECT yFdo, IN PURB yUrb) { NTSTATUS ntStatus = STATUS_SUCCESS; PIRP pIrp; KEVENT hEvent; IO_STATUS_BLOCK wIoStatus; PIO_STACK_LOCATION pwNextStack; DbgLogTrace(("ModRc: +UrbSend\n")); /* issue a synchronous request (see notes above) */ KeInitializeEvent(&hEvent, NotificationEvent, FALSE); pIrp = IoBuildDeviceIoControlRequest(IOCTL_INTERNAL_USB_SUBMIT_URB, GET_NEXT_DO(yFdo), NULL, 0, NULL, 0, TRUE, /* INTERNAL */ &hEvent, &wIoStatus); /* Set up the URB ptr to pass to the USB driver stack */ pwNextStack = IoGetNextIrpStackLocation(pIrp); pwNextStack->Parameters.Others.Argument1 = yUrb; IoSetCompletionRoutine( pIrp, (PIO_COMPLETION_ROUTINE)IrpCompletionRoutine, (PVOID) &hEvent, TRUE, TRUE, TRUE); ntStatus = IoCallDriver(GET_NEXT_DO(yFdo), pIrp); if (ntStatus == STATUS_PENDING) ntStatus = KeWaitForSingleObject(&hEvent, Executive, KernelMode, FALSE, NULL); else ntStatus = wIoStatus.Status; if (NT_SUCCESS(ntStatus) && !USBD_SUCCESS(yUrb->UrbHeader.Status)) { DbgLogTrace(("ModRc: > USB Request status : 0x%08X\n", yUrb->UrbHeader.Status)); ntStatus = STATUS_UNSUCCESSFUL; } DbgLogTrace(("ModRc: -UrbSend(0x%08X)\n", ntStatus)); return ntStatus; } NTSTATUS IrpCompletionRoutine(IN PDEVICE_OBJECT yFdo, IN PIRP yIrp, IN PVOID yContext) { PKEVENT phEvent = (PKEVENT)yContext; KeSetEvent(phEvent, IO_NO_INCREMENT, FALSE); return STATUS_MORE_PROCESSING_REQUIRED; } Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62140
  - 22
    - Is there any way to suspend/resume a process from kernel mode? . Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62139
  - 23
    - Virtual display driver I want to write a virtual display driver that paints the screen of one color when it loads. To test it I have also to write an application that loads and unloads the driver. What are the methods that I have to implement? Could anybody show me the way or a sample to develop this driver? Jordi Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62138
  - 24
    - NDIS miniport driver Hi all, I've following problem. I need low level access to NIC, so I want to create own NDIS miniport driver. Questions are: - is it possible to have two NDIS miniports running for one card in one time (one which drives card, sends packets and so on = manages normal traffic ... and second one which is responsible for running my own NIC's commands sequence and nothing else)? - I suppose that driver responsible for normal traffic should be "suspended" during working time of the second one. Is that true? Thanks for your time ... Michal Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62136
  - 25
    - problem building vfw now, I downloaded the VFWDK and I tried to build me some sample code but the thing does not work. I don't know the build line for a makefile project. anyone with help? Tag: "CreateCompatibleDC ()" may have a bug on XP x64 Tag: 62135

OS: Windows XP x64
Application: 32-bit application (i.e. Word)
Priner Driver: 64-bit printer driver
DDK version: 3790.1433

"CreateCompatibleDC (NULL);" returns NULL inside our 64-bit printer driver
when our driver is called by a 32-bit application. And "GetLastError()"
returns
0 after that.

Is that a known issue? If so, when can we expect to get the new OS or
DDK version with the fix?

Thanks,

SL

Top