Capi 2.0 - driver for Vista

TheMSsForum.com: The Microsoft Software Forum

The MSS Forum ‹ Drivers
- Archive
  - Biz
  - MCSE
  - CRM
  - Drivers
  - Framework
  - ADO
  - ASP
  - Compact
  - Forms
  - Dotnet
  - C#
  - VB
  - FontpageGen
  - Excel
  - WorkSheet
  - Exchange
  - Setup
  - Fox
  - Fontpage
  - ASP
  - IIS
  - Entourage
  - Money
  - Messanger
  - PocketPC
  - Powerpoint
  - Project
  - Publisher
  - Excel
  - VB
  - Security
  - Portal
  - Services
  - SQLServerDev
  - SVCS
  - SQLServer
  - VB
  - VC
  - MFC
  - ExcelGen

- Previous
  - 1
    - NDIS IM driver signing Hi When I'm trying to install my NDIS IM driver in WinXp, I get the "Windows logo program message box" with the "continue" and stop installation buttons. I know that for commercial use, drivers need some kind of license, and I've heard of WHQL and Verisign. Can someone please tell me which one of the licenses does NDIS IM need? Is Verisign should be enough? Thanks. Tag: Capi 2.0 - driver for Vista Tag: 94193
  - 2
    - How to modify the soundcard buffer? Hi all, I'm writing a Filter Driver which is attached into sysaudio device. I'm able to catch the IRP_MJ_WRITE and IRP_MJ_READ. Now how to modify the DMA buffer of the sound and then pass it to the lower device? My code snippet NTSTATUS AudioFilter_Write(PDEVICE_OBJECT DeviceObject, PIRP Irp) { NTSTATUS NtStatus = STATUS_BUFFER_TOO_SMALL; PAUDIO_FILTER_EXTENSION pAudioFilterDeviceContext = (PAUDIO_FILTER_EXTENSION)DeviceObject->DeviceExtension; PIO_STACK_LOCATION pIoStackIrp = NULL; PCHAR pReadDataBuffer; DbgPrint("AudioFilter_Write Called \r\n"); pIoStackIrp = IoGetCurrentIrpStackLocation(Irp); pReadDataBuffer = MmGetSystemAddressForMdl(Irp->MdlAddress, NormalPagePriority); AudioFilter_ClearBuffer(pReadDataBuffer, (UINT)MmGetMdlByteCount(Irp->MdlAddress)); IoSkipCurrentIrpStackLocation(Irp); NtStatus = IoCallDriver(pAudioFilterDeviceContext->pNextDeviceInChain, Irp); DbgPrint("AudioFilter_Write Exit 0x%0x \r\n", NtStatus); return NtStatus; } NTSTATUS AudioFilter_ClearBuffer(PUCHAR pString, UINT uiSize) { NTSTATUS NtStatus = STATUS_SUCCESS; UINT uiIndex = 0; PCHAR data = NULL; PAGED_CODE(); DbgPrint("AudioFilter_ClearBuffer...\n"); while (uiIndex < (uiSize - 1)) { if (pString[uiIndex] != 0) pString[uiIndex] >>= 1; DbgPrint("%d ", pString[uiIndex]); uiIndex++; } DbgPrint("\n"); return NtStatus; } Thanks, Hieu Tag: Capi 2.0 - driver for Vista Tag: 94186
  - 3
    - selectively bind a NDIS IM hi. i am currently developing a NDIS IM and i want to bind it to only one specific underlying adapter. the adapter is chosen at the user-level control program (it's okay if this operation requires administrative rights). problem is, at the very moment i install the IM, NDIS binds it to all adapters. i'm currently installing it through INF files. some people told me to try the CreateService() API function, but it doesn't seem to work (apparently it gets created alright, but when i try to start it, StartService() returns 0 (false = failure), and the subsequent GetLastError() gives 0 (no error)). the CreateService() solution seems to be a better one, because i can first start the driver, then tell it which interface to bind to (via IOCtl, for example), and it will register with NDIS only at this moment, refusing all the bindings except the desired one. from out the following two questions, EITHER one might be helpful. Q1: can i not register with NDIS in the driver's DriverEntry() function, and follow the INF installation? Q2: how should i correctly register the IM driver with CreateService()? thanks in advance. -- vv Tag: Capi 2.0 - driver for Vista Tag: 94181
  - 4
    - Safely removing USB stick - problem Running Vista 64 bit Ultimate release. Can't get Vista to properly stop the USB pin drive. When selecting to "Safely Remove Hardware", the correct dialogue windows pops up, I select Stop, confirmation window displays to stop the device, I select OK and the dialogue tells me it' safe to remove the USB pin drive. However the USB pin drive LED is still lit suggesting the device is truely not safe to remove. Anyone else seeing this? I guess the only work around is to shut the system down and remove the pin drive. Hopefully this gets fixed in Service Pack 1. -- RaXeT Tag: Capi 2.0 - driver for Vista Tag: 94175
  - 5
    - Unable to start SCSISCAN.SYS on Vista On Windows XP we install our SCSI scanner with a "stub" INF file that does not load any drivers. The only thing it does it get the scanner into the device manager under Imaging Devices. Then we find it and use SCSI pass through. No STI or WIA. That does not work on Vista. We tried loading SCSISCAN.SYS in our INF file. SCSISCAN.SYS loads but cannot start. Vista successfully sends 12 SCSI inquiry commands to the scanner at startup and when we Scan for Hardware Changes. We never get the New Hardware Found dialog. Should we get a New Hardware Found dialog because Windows gets SCSI Inquiry data from our scanner, even with no INF file installed? Why do we have to load SCSISCAN.SYS in our INF file in Vista but not in XP? Any ideas why SCSISCAN.SYS loads but does not start? Could this be a security/permissions problem? Do we have to write a STI or WIA driver to use SCSI pass through on Vista? Here is our INF file: [Version] Signature = "$CHICAGO$" Class = Image ClassGuid = {6bdd1fc6-810f-11d0-bec7-08002be2092f} Provider = %Xerox% [Manufacturer] %Xerox%=Xerox, NTx86 [Xerox.NTx86] %DI665S% = Xerox.SCSISection, SCSI\ScannerXerox___DocuImage_665S__ [SourceDisksFiles] scsiscan.sys=3426 [DestinationDirs] DefaultDestDir=10,system32\drivers Xerox.SCSI.CopySys32Files=10,system32\drivers [Strings] Xerox="Xerox" DI665S="Xerox DocuImage 665S Scanner" scsiscan.SvcDesc= "SCSI Scanner Driver" [Xerox.SCSISection] CopyFiles=Xerox.SCSI.CopySys32File AddService=scsiscan, 0x00000002, Xerox.ScsiScan.AddService [Xerox.SCSISection.Services] AddService=scsiscan, 0x00000002, Xerox.ScsiScan.AddService [Xerox.SCSI.CopySys32Files] scsiscan.sys [Xerox.ScsiScan.AddService] DisplayName = %scsiscan.SvcDesc% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\scsiscan.sys LoadOrderGroup = Base Tag: Capi 2.0 - driver for Vista Tag: 94170
  - 6
    - Debugging USB device Hello, I'm an embbedded software developer, trying to implement an USB HID keyboard. I've found many HID samples for various microcontrollers, and I'm OK with the basis : I can have my device enumerate properly, claimed by hidclass.sys driver, and available to user-land application. This is almost perfect, but my goal is to make a "standard" keypad to be used as input device in any application, and not a vendor-specific device. Now my problem is, as soon as I claim being to USB HID keypad (and of course provide the appropriate descriptor, as found on the specification and in a few samples), Windows stops my device and marks it as invalid (with error code 10). Note that when I remove the "keyboard" part of the descriptor to keep only the "LED" part (CAPS LOCK, NUM LOCK, SCROLL LOCK), the device is marked OK, and any change in main keyboard status is correctly forwarded to my board. So, my question is, how can I find what's wrong in my keyboard descriptor ? Is it possible to have hidclass.sys providing detailed report on what's going wrong, or is there a analysis software that may help ? Regards, -- johann.d Tag: Capi 2.0 - driver for Vista Tag: 94164
  - 7
    - RegisterDeviceNotification on Vista x64 I have a Win32 Service App, which registers an opened device handle for removed check. This App works fine in XP-x64. but not in Vista-x64. The Vista-x64 send the SERVICE_CONTROL_DEVICEEVENT / DBT_DEVICEREMOVECOMPLETE with the value in the DEV_BROADCAST_HANDLE parameter : dbch_size --> sizeof(DEV_BROADCAST_HANDLE) dbch_devicetype --> DBT_DEVTYP_HANDLE dbch_handle ---> NULL dbch_hdevnotify ---> NULL This makes me to have no way to determent which handle I registered has been removed. Is there anyway to solve this problem? Tag: Capi 2.0 - driver for Vista Tag: 94155
  - 8
    - trying to install a minifilter without INF file Hi, Yes I know I should have an INF file, but that is another story. I'm trying to load my minifilter driver on XP 2003 Server. I'm using SCM to get loaded and this is working , my driver is getting loaded. In the DriverEntry I am failing when I call FltRegisterFilter() I am getting error 0xC0000034. I figure that this must be because of register settings? Can someone tell me exactly what the settings should be for my minifilter? TIA -- Gak - Finecats Tag: Capi 2.0 - driver for Vista Tag: 94154
  - 9
    - .kdfiles with boot start drivers on Vista Anyone been able to use .kdfiles -m in WinDbg with boot start drivers on Vista? After much wailing and gnashing of teeth I am thinking it can't be done. Anyone? I have seen some posts on this but they all either go no where or the people replying didn't read very well. Here is what I have tried. I tried using bcdedit to turn on the boot debugger. Here is my output from WinDbg: Waiting to reconnect... BD: Boot Debugger Initialized Connected to Windows Boot Debugger 6000 x86 compatible target, ptr64 FALSE Kernel Debugger connection established. Symbol search path is: From the kd prompt I set >sxe ld:mydriver.sys and the debugger promptly broke after all of the boot start drivers had been loaded?? The .kdfiles mapping to my driver never kicked. I am connecting WinDbg via NULL modem cable COM1 115200 baud. I also tried loading a checked build of WinLoad.exe...still no love. I can't seem to get the debugger to hook during boot. HELP? Anyone? I have seen several veteran driver devs ask this same question with no real help. If it isn't possible, it would be nice of someone to just say so. In my case this would sure save me a butt-load of time. Thanks. Bill M. Tag: Capi 2.0 - driver for Vista Tag: 94150
  - 10
    - File attributes not preserved on copy Hi, I am working on a filesystem driver. I have a weird problem while copying files from an NTFS volume to my volume. After the file is copied, Windows sends an IRP_MJ_SET_INFORMATION IRP with FileBasicInformation information class. Now the attributes field in the FILE_BASIC_INFORMATION structure is always zero even if the original file had read only, archive and/or hidden attribute set. So the file attributes are not preserved on copy unlike a copy between two NTFS harddisks or to a floppy disk. Is this expected behaviour? Is there anything the filesystem driver needs to do during driver startup or volume mount to ensure that Windows sets the right file attributes on file copy? Any information is greatly appreciated. Thanks, Priya Tag: Capi 2.0 - driver for Vista Tag: 94132
  - 11
    - Printer installation in Vista I try to install printer driver ( oemdll from WDK ) with AddprinterDriver() function. But I get each time the same error : Error 2. How to add printer driver in Vista ? Tag: Capi 2.0 - driver for Vista Tag: 94127
  - 12
    - Problem regarding WHQL WIA Transfer Test Hi, We are currently developing a WIA 2.0 scanner mini driver. We are using Widariverex sample that comes with WDK as our reference. When we are running WHQL WIA Transfer test we are seeing one assertion to fail. "Assertion: {CC5F18FA-0436-4e78-BB83-1881841FFB8D}, Test Case: Basic Single-Item, good-parameter, cancellation-free download. " But we are able to scan and preview properly from MS default UI. While debugging I saw that "drvAcquireItemData" entry point is also returning S_OK. Can you please guide me whether I am missing any thing in the source execution path? I have copied the contesnts of the WHQL log I got after conducting the test for your reference. / *************************************************************************************************************** 4/17/2007 5:13:36.524 PM Assertion: {CC5F18FA-0436-4e78- BB83-1881841FFB8D}, Test Case: Basic Single-Item, good-parameter, cancellation-free download. Message 4/17/2007 5:13:36.524 PM Case 1 Message 4/17/2007 5:13:36.524 PM Transfer Awaiting Start Message 4/17/2007 5:13:36.524 PM Parameters: Message 4/17/2007 5:13:36.524 PM Using Primary device Message 4/17/2007 5:13:36.524 PM Item Download Mode Message 4/17/2007 5:13:36.524 PM unsignedVT = 0x0 Message 4/17/2007 5:13:36.524 PM Selected Format GUID {B96B3CAB-0728-11D3-9D7B-0000F81EF32E} for transfer Message 4/17/2007 5:13:36.524 PM GetNextStream Executing Message 4/17/2007 5:13:36.524 PM Parameters: Message 4/17/2007 5:13:36.524 PM lFlags = 0x0 Message 4/17/2007 5:13:36.524 PM bstrItemName = Flatbed Message 4/17/2007 5:13:36.524 PM bstrFullItemName = 0000\Root\Flatbed Message 4/17/2007 5:13:36.524 PM GetNextStream Action Will Be: Message 4/17/2007 5:13:36.524 PM Run Normally Message 4/17/2007 5:13:36.524 PM TransferCallback Executing Message 4/17/2007 5:13:36.524 PM Parameters: Message 4/17/2007 5:13:36.524 PM lFlags = 0x0 Message 4/17/2007 5:13:36.524 PM lMessage = 0x1 Message 4/17/2007 5:13:36.524 PM lPercentComplete = 0 Message 4/17/2007 5:13:36.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:36.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:36.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:36.524 PM Run Normally Message 4/17/2007 5:13:36.524 PM TransferCallback Executing Message 4/17/2007 5:13:36.524 PM Parameters: Message 4/17/2007 5:13:36.524 PM lFlags = 0x0 Message 4/17/2007 5:13:36.524 PM lMessage = 0x1 Message 4/17/2007 5:13:36.524 PM lPercentComplete = 0 Message 4/17/2007 5:13:36.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:36.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:36.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:36.524 PM Run Normally Message 4/17/2007 5:13:43.524 PM TransferCallback Executing Message 4/17/2007 5:13:43.524 PM Parameters: Message 4/17/2007 5:13:43.524 PM lFlags = 0x0 Message 4/17/2007 5:13:43.524 PM lMessage = 0x1 Message 4/17/2007 5:13:43.524 PM lPercentComplete = 10 Message 4/17/2007 5:13:43.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:43.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:43.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:43.524 PM Run Normally Message 4/17/2007 5:13:44.524 PM TransferCallback Executing Message 4/17/2007 5:13:44.524 PM Parameters: Message 4/17/2007 5:13:44.524 PM lFlags = 0x0 Message 4/17/2007 5:13:44.524 PM lMessage = 0x1 Message 4/17/2007 5:13:44.524 PM lPercentComplete = 20 Message 4/17/2007 5:13:44.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:44.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:44.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:44.524 PM Run Normally Message 4/17/2007 5:13:44.524 PM TransferCallback Executing Message 4/17/2007 5:13:44.524 PM Parameters: Message 4/17/2007 5:13:44.524 PM lFlags = 0x0 Message 4/17/2007 5:13:44.524 PM lMessage = 0x1 Message 4/17/2007 5:13:44.524 PM lPercentComplete = 30 Message 4/17/2007 5:13:44.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:44.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:44.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:44.524 PM Run Normally Message 4/17/2007 5:13:44.524 PM TransferCallback Executing Message 4/17/2007 5:13:44.524 PM Parameters: Message 4/17/2007 5:13:44.524 PM lFlags = 0x0 Message 4/17/2007 5:13:44.524 PM lMessage = 0x1 Message 4/17/2007 5:13:44.524 PM lPercentComplete = 40 Message 4/17/2007 5:13:44.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:44.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:44.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:44.524 PM Run Normally Message 4/17/2007 5:13:45.524 PM TransferCallback Executing Message 4/17/2007 5:13:45.524 PM Parameters: Message 4/17/2007 5:13:45.524 PM lFlags = 0x0 Message 4/17/2007 5:13:45.524 PM lMessage = 0x1 Message 4/17/2007 5:13:45.524 PM lPercentComplete = 50 Message 4/17/2007 5:13:45.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:45.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:45.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:45.524 PM Run Normally Message 4/17/2007 5:13:45.524 PM TransferCallback Executing Message 4/17/2007 5:13:45.524 PM Parameters: Message 4/17/2007 5:13:45.524 PM lFlags = 0x0 Message 4/17/2007 5:13:45.524 PM lMessage = 0x1 Message 4/17/2007 5:13:45.524 PM lPercentComplete = 60 Message 4/17/2007 5:13:45.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:45.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:45.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:45.524 PM Run Normally Message 4/17/2007 5:13:45.524 PM TransferCallback Executing Message 4/17/2007 5:13:45.524 PM Parameters: Message 4/17/2007 5:13:45.524 PM lFlags = 0x0 Message 4/17/2007 5:13:45.524 PM lMessage = 0x1 Message 4/17/2007 5:13:45.524 PM lPercentComplete = 70 Message 4/17/2007 5:13:45.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:45.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:45.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:45.524 PM Run Normally Message 4/17/2007 5:13:46.524 PM TransferCallback Executing Message 4/17/2007 5:13:46.524 PM Parameters: Message 4/17/2007 5:13:46.524 PM lFlags = 0x0 Message 4/17/2007 5:13:46.524 PM lMessage = 0x1 Message 4/17/2007 5:13:46.524 PM lPercentComplete = 80 Message 4/17/2007 5:13:46.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:46.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:46.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:46.524 PM Run Normally Message 4/17/2007 5:13:46.524 PM TransferCallback Executing Message 4/17/2007 5:13:46.524 PM Parameters: Message 4/17/2007 5:13:46.524 PM lFlags = 0x0 Message 4/17/2007 5:13:46.524 PM lMessage = 0x1 Message 4/17/2007 5:13:46.524 PM lPercentComplete = 90 Message 4/17/2007 5:13:46.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:46.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:46.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:46.524 PM Run Normally Message 4/17/2007 5:13:47.524 PM TransferCallback Executing Message 4/17/2007 5:13:47.524 PM Parameters: Message 4/17/2007 5:13:47.524 PM lFlags = 0x0 Message 4/17/2007 5:13:47.524 PM lMessage = 0x1 Message 4/17/2007 5:13:47.524 PM lPercentComplete = 100 Message 4/17/2007 5:13:47.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:47.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:47.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:47.524 PM Run Normally Error 4/17/2007 5:13:47.524 PM Read called on guarded stream File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Relevant Assertion: File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM WIA drivers must use only the following IStream methods during downloads: Write, Seek, SetSize. WIA drivers must use only the following IStream methods during uploads: Read, Seek, Stat. File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Read called on guarded stream File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Relevant Assertion: File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM WIA drivers must use only the following IStream methods during downloads: Write, Seek, SetSize. WIA drivers must use only the following IStream methods during uploads: Read, Seek, Stat. File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Read called on guarded stream File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Relevant Assertion: File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM WIA drivers must use only the following IStream methods during downloads: Write, Seek, SetSize. WIA drivers must use only the following IStream methods during uploads: Read, Seek, Stat. File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Read called on guarded stream File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM Relevant Assertion: File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Error 4/17/2007 5:13:47.524 PM WIA drivers must use only the following IStream methods during downloads: Write, Seek, SetSize. WIA drivers must use only the following IStream methods during uploads: Read, Seek, Stat. File: Line: 0 Error Type: Error Code: 0x0 Error Text: Error 0x00000000 Message 4/17/2007 5:13:47.524 PM TransferCallback Executing Message 4/17/2007 5:13:47.524 PM Parameters: Message 4/17/2007 5:13:47.524 PM lFlags = 0x0 Message 4/17/2007 5:13:47.524 PM lMessage = 0x2 Message 4/17/2007 5:13:47.524 PM lPercentComplete = 0 Message 4/17/2007 5:13:47.524 PM ulTransferredBytes = 0x68CF76 Message 4/17/2007 5:13:47.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:47.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:47.524 PM Run Normally Message 4/17/2007 5:13:47.524 PM TransferCallback Executing Message 4/17/2007 5:13:47.524 PM Parameters: Message 4/17/2007 5:13:47.524 PM lFlags = 0x0 Message 4/17/2007 5:13:47.524 PM lMessage = 0x3 Message 4/17/2007 5:13:47.524 PM lPercentComplete = 0 Message 4/17/2007 5:13:47.524 PM ulTransferredBytes = 0x0 Message 4/17/2007 5:13:47.524 PM hrErrorStatus = 0x0 Message 4/17/2007 5:13:47.524 PM TransferCallback Action Will Be: Message 4/17/2007 5:13:47.524 PM Run Normally End Test 4/17/2007 5:13:47.524 PM Assertion: {CC5F18FA-0436-4e78- BB83-1881841FFB8D}, Test Case: Basic Single-Item, good-parameter, cancellation-free download. Result: Fail Repro: E:\WTT\JobsWorkingDir\Tasks \WTTJobRun6648C66F-90A1-472F-8C83-18476EC8ADB4\WiaTransferTool.exe / *************************************************************************************************************** We are in a critical stage and Your help will be much appreciated. Thanks, Madhu Tag: Capi 2.0 - driver for Vista Tag: 94124
  - 13
    - [OT] OpenProcess shows "Access Denied (5)" on some Processes,.. Hi, can please someone have a look at this: http://groups.google.de/group/microsoft.public.vc.mfc/browse_thread/thread/9a26245c82cd048e/157c9704f05a2860 TIA Best regards Kerem Gümrükcü Tag: Capi 2.0 - driver for Vista Tag: 94123
  - 14
    - Enumerate Child Device Hello All, We are writing a USB-Serial driver using WDF framework. We have completed the USB part i.e handling PnP and Power Management. My problem is i want OS to enumerate a child device probably as Serial device. I want the device manager to show virtual COM port device and USB device. I did the following to achieve this. After the completion of EvtDeviceD0Entry, i have added the following code to enumerate a child device (COM) in EvtDeviceRelationsQuery NTSTATUS EvtDeviceRelationsQuery (IN WDFDEVICE Device, IN DEVICE_RELATION_TYPE RelationType ) { // Initialize UNICODE device name RtlInitUnicodeString(&uniDeviceName, L"\\Device\\SerBus0"); DeviceInit = WdfPdoInitAllocate(Device); // USB device object if (DeviceInit == NULL) { DbgPrint ("WdfControlDeviceInitAllocate failed 0x%x\n", status); status = STATUS_INSUFFICIENT_RESOURCES; } // // Set exclusive to true so that not more than one app can talk to the // control device simultaneously. // WdfDeviceInitSetExclusive(DeviceInit, TRUE); WdfDeviceInitSetDeviceType(DeviceInit, FILE_DEVICE_UNKNOWN); WdfDeviceInitSetCharacteristics(DeviceInit, FILE_DEVICE_SECURE_OPEN, FALSE); // // Assign the device name // status = WdfDeviceInitAssignName(DeviceInit, &uniDeviceName); if (!NT_SUCCESS(status)) { DbgPrint ("WdfDeviceInitAssignName failed 0x%x\n", status); return status; } // // Initialize the attributes // WDF_OBJECT_ATTRIBUTES_INIT_CONTEXT_TYPE (&attributes,DEVICE_CONTEXT); // // Create the control device // status = WdfDeviceCreate(&DeviceInit, &attributes, &serbusdevice); if (!NT_SUCCESS(status)) { DbgPrint (WdfDeviceCreate failed 0x%x\n", status); return status; } status = WdfFdoAddStaticChild(Device, serbusdevice); if (!NT_SUCCESS(status)) { DbgPrint (WdfFdoAddStaticChild failed 0x%x\n", status); return status; } } In EvtDeviceAdd i added the following code after i get the device handle. busInfo.BusTypeGuid = GUID_CLASS_COMPORT; busInfo.LegacyBusType = PNPBus; busInfo.BusNumber = 0; WdfDeviceSetBusInformationForChildren(device, &busInfo); I followed the instructions at the following link. http://msdn2.microsoft.com/en-us/library/aa490110.aspx I dint have any luck in proceeding further. Cany anyone point me if im missing anything, so that windows could enumerate a child device. I want to provide a different INF file for second enumeration. Thank You, Regards, Sushma Tag: Capi 2.0 - driver for Vista Tag: 94121
  - 15
    - Installing Filter driver I am trying to install Filter driver using SetupAPI function as decribed in MSDN. Call SetupInstallFilesFromInfSection for the [upperfilter_inst] section. Call SetupInstallServicesFromInfSection for the [upperfilter_inst.Services] section. Call SetupInstallFromInfSection for the [upperfilter_inst] section, once for each class key it wants to register the upperfilt service for. But I see only registry is getting updated. The actual driver is not get bound to the adapters. How to do that? Tag: Capi 2.0 - driver for Vista Tag: 94120
  - 16
    - MiniportCheckForHangEx vs MiniportCHeckForHang Hi, I am writing an NDIS6 miniport driver. In WDK it is written on MiniportCheckForHangEx do that "If a miniport driver does not complete an OID request within two successive calls to MiniportCheckForHangEx, NDIS can call the driver's MiniportResetEx function." and on MiniportCheckForHang doc that: "If a NIC driver has no MiniportCheckForHang function and NDIS judges the driver unresponsive as, for example, when NDIS holds many pending sends and requests queued to the miniport driver for a time-out interval, NDIS calls the driver's MiniportReset function" 1. If I correctly understand the doc than MiniportCheckForHangEx in contrary to MiniportCheckForHang does not care about pending sends request only pending OIDS. I tested it by pending send requests forever and indeed MiniportReset was not called. Is that the expected behaviour or did I miss something? 2. What is the meaning of "NDIS can call the driver's MiniportResetEx?" are there times that it will not call it ? Thanks Miki Tag: Capi 2.0 - driver for Vista Tag: 94113
  - 17
    - Driver Signing Problem Hallo, For VISTA I have build a signed driver package with a "VeriSign Class 3 Code Signing 2000 CA" ID. Our Rule is using the same package for Windows XP. In Vista the installation is OK but in Windows XP I can see some errors in setupapi.log #E360 An unsigned or incorrectly signed file "c:\windows\inf\oem9.inf" for driver "XXX" will be installed (Policy=Ignore). Error 1168: What is not correct with my signing ? The result: class installer entrys (ICON, name) are not installed in registry and CoInstaller DLL is not running by the installation. When I break this signed package (insert a space into INF file) all is fine. elli Tag: Capi 2.0 - driver for Vista Tag: 94109
  - 18
    - Does anyone use regdmp.exe or objdir.exe? What would be the impact on you if we pulled regdmp.exe and objdir.exe from the WDK? Tag: Capi 2.0 - driver for Vista Tag: 94099
  - 19
    - Can the Media Center source be aquired? We are having a large problem developing a BDA driver. The source of this problem is that the documentation for writing a BDA driver explains what everything does, but not what actually happens in terms of successfully instancing a filter that will be used by Media Center. This makes debugging impossible as very little of our code actually runs before Media Center decides not to acknowledge our device. Is the source code for Media Center available under some license offered by Microsoft? Otherwise, does anyone have a method to successfully diagnose graph building and filter caps problems? Tag: Capi 2.0 - driver for Vista Tag: 94098
  - 20
    - Embedded authenticode signature Hi, I want to sign MyDriver.sys with an authenticode signature appended to the .sys file, just like a normal user mode DLL. The driver is for Server 2003 and Vista, x86 and x64. I realize this will have no effect on the install prompts etc. My question is, will the signature adversely affect the loading of the driver, assuming the checksum is OK? My concern is that the driver loader might be confused by the signature added to the .sys file. Thanks -- Tag: Capi 2.0 - driver for Vista Tag: 94085
  - 21
    - Help writing virtual webcam driver Hi guys, I'm a newcomer the device driver development discipline. I'm short my project requires me to write a virtual webcam driver - the driver should not interact with any real hardware instead the image input is actually coming from e.g. the network.. I really looking for some pointers - that might push me in the right direction.. I've been reading a bit the last two days and this is how far I've come: 1) I would like to use KMDF - (cannot be done in UMDF correct?). 2) It seems I need to develop a "Video Capture Device" using something called AvStream (Currently I'm not really sure what AvStream does). 3) Are there any good DDK samples that might give me a idea of how to continue. I've looked a bit at the AVSHwS and it seems promising. 4) I found that a webcam driver is classified as an UVC (USB video device class) - Is this the protocol I need to implement in my driver? I really hope you can help me, in answering my initial questions.. All ideas, thoughts are more than welcome :) -- // morten Tag: Capi 2.0 - driver for Vista Tag: 94080
  - 22
    - Problems in Vista with WiFi and Ndis (ndisuio.sys) Hello, I need help for Vista OS. I am updating a program to make connections to Wifi Networks so that it works in Vista. This program work with ndisuio.sys driver or any compatible driver based on NDISPROT sample protocol driver. For this case I stop the Wlansvc as I was doing in XP with the wzcsvc. It work without problems and Vista let me control the WiFi device. These drivers work fine in Vista and the devices I have probed work fine with them. I send these OID=B4s for make a connection: OID_802_11_INFRASTRUCTURE_MODE(0x0D010108) OID_802_11_AUTHENTICATION_MODE(0x0D010118) OID_802_11_ADD_KEY(0x0D01011D) (some times, if the mode needs it) OID_802_11_WEP_STATUS(0x0D01011B) OID_802_11_SSID(0x0D010102) OID_GEN_PORT_AUTHENTICATION_PARAMETERS(0x0001020F) They work well and they are shown by the program ndismon(PCAUSA) also when the system connects. The connection(association) with the AP is Ok and I send the neccesary security protocol (802.1X, WPA-PSK, WPA-PEAP) developed in my program and they work fine with the device and the AP. THE PROBLEM: Up to here, everything seems to work fine but the problem is with the TCP/IP and the new interface added in the system Vista. The new interface does not appear in the window "Network and Sharing Center" and the DHCP protocol does not work over it. The new interfce does not obtain IP address and it does not work although the association with the AP and the authorization and authentication with the WiFi device is Ok. I think that more actions are necessary in order to wake up the interface in the system Vista although I have not been able to find information on the matter. Any help about this issue would be very appreciated. Sorry for my bad English. Best regards, Frank Tag: Capi 2.0 - driver for Vista Tag: 94077
  - 23
    - About driver developing Hello, I'm new to driver authoring and want to know some simple question's answers. 1-WinDDK is enough to develop MS-based device drivers? 2-Do i need/have to know programming languages like c++? 3-Is WDK (or called WinDDK) avaible for download? Sorry for these basic questions but i need to know. Best regards... Tag: Capi 2.0 - driver for Vista Tag: 94071
  - 24
    - avstream avssamp example freeze system Hello. Using matlab+simulink (under mex setup VS2005) as a client application for capturing video from DDK sample avssamp totally freeze windows (Vista, XP). The mouse cursor doesn't move, nothing is move at all. At the same time Avssamp is fine when capturing with Amcap, and fine if matlab mex setup is VS2003.NET, also matlab is fine with vs2005 when captureing from webcamera... Tried using avsamp debug version with dbgPrintf+dbgview - i can't see any out message, system is freezed before any message occurs. Tried run with verifier ON, nothing! Could anybody advise how to debug this strange avssamp behaviour? Thank you. -Andrey Tag: Capi 2.0 - driver for Vista Tag: 94066
  - 25
    - SYS File Format Hello All, Where I can find information about the format of SYS file? What is the different from DLL PE file format? Thanks, Ronen Tag: Capi 2.0 - driver for Vista Tag: 94065
- Next
  - 1
    - winusb and WinUsb_ControlTransfer My USB device supports the default control pipe (only) and these requests are made using control transfers. In order to fetch the version from my device, the following vendor specific call is successful: WINUSB_INTERFACE_HANDLE hWinUsbIntf ; UCHAR ucaBuffer[256] ; DWORD dwXeptLen ; : : WINUSB_SETUP_PACKET Wsp = { 0xC3, 0x81, 0x80, 0, 255 } ; BOOL bRC = WinUsb_ControlTransfer ( hWinUsbIntf, Wsp, ucaBuffer, sizeof(ucaBuffer) - 1, &dwXeptLen, NULL ) ; In order to reset the LED on the device, I issue: WINUSB_SETUP_PACKET Wsp = { 0x40, 0x80, 0x40, 0, 1 } ; bRC = WinUsb_ControlTransfer ( hWinUsbIntf, Wsp, ucaBuffer, sizeof(ucaBuffer) - 1, &dwXeptLen, NULL ) ; The vendor specific SetLED fails and the translated GetLastError is "A device attached to the system is not functioning." Shouldn't I be able to write to the device via Winsys as well as read? Tag: Capi 2.0 - driver for Vista Tag: 94064
  - 2
    - KMDF: accessing PCI configuration space results in STATUS_NOT_SUPPORTED I try to access the PCI configuration space of my PCI hardware. I follow the WDK help topic "Accessing PCI Device Configuration Space". As a first step, I try to get a BusInterface, but this fails. I used two different styles (see code below), both result with status = STATUS_NOT_SUPPORTED. I can not see the difference between the PCIDRV example and my own device, so any help is welcome! J. Hoppe, PEAK System Technik GmbH ======= Try #1 (as in example "src/kmdf/pcidrv") : ================ xxxDeviceAdd() { ... ... status = WdfFdoQueryForInterface(Device, &GUID_BUS_INTERFACE_STANDARD, (PINTERFACE) & pDeviceContext->BusInterface, sizeof(BUS_INTERFACE_STANDARD), 1, // Version NULL); //InterfaceSpecificData .... } ======= Try #2 (as in other example / Knowledgebase) ================ // from C:\WinDDK\6000\src\general\pcidrv\sys\hw\nic_init.c NTSTATUS GetPCIBusInterfaceStandard( __in PDEVICE_OBJECT DeviceObject, __out PBUS_INTERFACE_STANDARD BusInterfaceStandard ) /*++ Routine Description: This routine gets the bus interface standard information from the PDO. Arguments: DeviceObject - Device object to query for this information. BusInterface - Supplies a pointer to the retrieved information. Return Value: NT status. --*/ { KEVENT event; NTSTATUS status; PIRP irp; IO_STATUS_BLOCK ioStatusBlock; PIO_STACK_LOCATION irpStack; PDEVICE_OBJECT targetObject; DiagMsg("GetPciBusInterfaceStandard entered."); PAGED_CODE(); KeInitializeEvent( &event, NotificationEvent, FALSE ); targetObject = IoGetAttachedDeviceReference( DeviceObject ); irp = IoBuildSynchronousFsdRequest( IRP_MJ_PNP, targetObject, NULL, 0, NULL, &event, &ioStatusBlock ); if (irp == NULL) { status = STATUS_INSUFFICIENT_RESOURCES; goto End; } irpStack = IoGetNextIrpStackLocation( irp ); irpStack->MinorFunction = IRP_MN_QUERY_INTERFACE; irpStack->Parameters.QueryInterface.InterfaceType = (LPGUID) &GUID_BUS_INTERFACE_STANDARD ; irpStack->Parameters.QueryInterface.Size = sizeof(BUS_INTERFACE_STANDARD); irpStack->Parameters.QueryInterface.Version = 1; irpStack->Parameters.QueryInterface.Interface = (PINTERFACE)BusInterfaceStandard; irpStack->Parameters.QueryInterface.InterfaceSpecificData = NULL; // // Initialize the status to error in case the bus driver does not // set it correctly. irp->IoStatus.Status = STATUS_NOT_SUPPORTED ; status = IoCallDriver( targetObject, irp ); if (status == STATUS_PENDING) { status = KeWaitForSingleObject( &event, Executive, KernelMode, FALSE, NULL); ASSERT(NT_SUCCESS(status)); status = ioStatusBlock.Status; } End: // Done with reference ObDereferenceObject( targetObject ); return status; } xxxDeviceAdd() { ... ... { PDEVICE_OBJECT devobj = WdfDeviceWdmGetDeviceObject(Device) ; status = GetPCIBusInterfaceStandard(devobj, & (pDeviceContext->BusInterface)) ; } .... } =============== end code examples ================= Tag: Capi 2.0 - driver for Vista Tag: 94059
  - 3
    - Debug IEEE 802.1X Does anyone seen this kind of problem before? On what case 802.1x supplicant will create port fail and error code is 13 as below. Good information for debugging 802.1x http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/wlansupp.mspx Environment: Hidden SSID/WPA-PSK [472] 09:22:03:234: Device: \DEVICE\{3AE7D14E-74EC-4F06-B655-20FE661B518C} [472] 09:22:03:234: Description: USB Wireless LAN Card - Packet Scheduler Miniport [472] 09:22:03:234: ElEnumAndOpenInterfaces: Found interface after enumeration \DEVICE\{3AE7D14E-74EC-4F06-B655-20FE661B518C} [472] 09:22:03:234: ElEnumAndOpenInterfaces: Did NOT find PCB already existing for interface [472] 09:22:03:234: ElOpenInterfaceHandle: Opening handle for \DEVICE\{3AE7D14E-74EC-4F06-B655-20FE661B518C} [472] 09:22:03:234: ElOpenInterfaceHandle: Trying to access NDIS Device: \DEVICE\{3AE7D14E-74EC-4F06-B655-20FE661B518C} [472] 09:22:03:234: ElOpenInterfaceHandle: OpenIntfHandle(\DEVICE\{3AE7D14E-74EC-4F06-B655-20FE661B518C}) = 4440 [472] 09:22:03:234: ElOpenInterfaceHandle: BindIoCompletionCallback already done !!! [472] 09:22:03:234: ElOpenInterfaceHandle: Opened handle 00001158 with dwRetCode 0 [472] 09:22:03:234: ElCreatePort: Entered for Handle=(00001158), GUID=({3AE7D14E-74EC-4F06-B655-20FE661B518C}), Name=(USB Wireless LAN Card - Packet Scheduler Miniport), ZCId=(0), UserData=(00000000) Notification=<8> [472] 09:22:03:234: ElCreatePort: No PCB found for {3AE7D14E-74EC-4F06-B655-20FE661B518C} [472] 09:22:03:234: ElGetInterfaceNdisStatistics: pwszDeviceInterfaceName = (\Device\{3AE7D14E-74EC-4F06-B655-20FE661B518C}) [472] 09:22:03:234: ElCreatePort: Ignoring WLAN indications for pZCConnectInfo == NULL ****[472] 09:22:03:234: ElEnumAndOpenInterfaces: Error in CreatePort = 13 <======??? [472] 09:22:03:234: ElCloseInterfaceHandle(0x1158,{3AE7D14E-74EC-4F06-B655-20FE661B518C}) entered [472] 09:22:03:234: ElEnumAndOpenInterfaces: Completed with retcode = 0 [472] 09:22:03:234: ElMediaSenseCallbackWorker: processed, RetCode = 0 Thanks. Tag: Capi 2.0 - driver for Vista Tag: 94058
  - 4
    - WINDOWS CE 5.0 run-time image errors hi all, i am new to this field WIN CE. i'm trying to build CEPC run-time image. But i'm getting errrors like bellow. BUILD: [00:0000001177:PROGC ] Scan \PUBLIC\COMMON\OAK\CSP\X86\GEODE\GXVIDEO\DDRAW\ BUILD: [00:0000001178:ERRORE] CreateDirectory(\) failed. GetLastError=5 (dec). please solve my problem. thanking you. Tag: Capi 2.0 - driver for Vista Tag: 94057
  - 5
    - Vista RTM GDR release Hi, I have seen that the Vista USB driver stack is released in two different versions. The driver stack shipped with the MSDN DVD's is the RTM version: 6.0.6000.16386 (vista_rtm.061101-2205), the version that is now on the market is GDR: 6.0.6000.16400 (vista_gdr.061212-1500). I have done a binary comprision of the driver files. E.g. usbd.sys has only a new data from the compilation and a new version information. But other drivers like usbport.sys differs in more than the version. What is the difference between these versions? Is it required to test kernel mode drivers with both versions? Is RTM the latest beta version? I have got a problem report from a customer. He claims that the driver is not running with GDR that was tested successful with RTM! This problem is still under investigation. Any comments? Thanks Guenter Tag: Capi 2.0 - driver for Vista Tag: 94055
  - 6
    - NDIS6 Miniport not unloaded Hi everyone: I am running an ndis 6 + KMDF Ethernet miniport driver. The miniport controls a USB NIC . I bridged miniport through bridgeMP to another Ethernet NIC. When I am suprisingly remove my device I my MiniportPause is not called and the miniport remains active(checkforhang is keep being called). When I do !stacks 2 ndis I see the following: nt!KiSwapThread+0x36d: nt!KeWaitForSingleObject+0x414 ndis!NdisWaitEvent+0x55 bridge+0xb1d7 bridge+0xb221 bridge+0x1a92 ndis!ndisUnbindProtocol+0x24b ndis!ndisPnPNotifyAllTransports +0x1c8 ndis!ndisCloseMiniportBindings +0x17a ndis!ndisPnPRemoveDevice+0x1ab ndis!ndisPnPDispatch+0x85e nt!IovCallDriver+0x252 nt!IofCallDriver+0x1b nt!ViFilterDispatchPnp+0x120 nt!IovCallDriver+0x252 nt!IofCallDriver+0x1b nt!IopSynchronousCall+0xce nt!IopRemoveDevice+0xd5 nt! PnpSurpriseRemoveLockedDeviceNode+0xbd nt!PnpDeleteLockedDeviceNode +0x1f nt!PnpDeleteLockedDeviceNodes +0x4c nt! PnpProcessQueryRemoveAndEject+0x572 nt!PnpProcessTargetDeviceEvent +0x38 nt!PnpDeviceEventWorker+0x201 nt!ExpWorkerThread+0xfd nt!PspSystemThreadStartup+0x9d nt!KiThreadStartup+0x16 It seems that the bridge is hang on some Event and due to that the miniport is unloaded. Does anyone has any idea how can I further debug it? Thanks Miki Tag: Capi 2.0 - driver for Vista Tag: 94052
  - 7
    - Why WindowsXP does not accept the correct NIC driver? I have a serious problem with my PC. I had to format my disk and reinstall Windows XP (with SP2), but I can not get to in web because Windows thinks that my network card is of Asound, but its of Realtek. I tried doing update driver using the Realtek RTL8139/810X Family PCI Fast Ethernet Card driver on the device manager. I tried uninstalling the driver, and then letting Windows find it again. I tried downloading new driver from the Internet (using another PC). But came out Asound. Windows simply does not let me change the driver. I logged in with Administrator account. I talked with the my ISP service provider, and they also found that the trouble is with my NIC. How can I force Windows use the driver that has on a disk, and not the built-in Asound? ----------- Thanks Sharon Tag: Capi 2.0 - driver for Vista Tag: 94051
  - 8
    - Miniport driver - OID_GEN_SUPPORTED_LIST problem Good morning, I'm developing miniport driver, when I answered OID_GEN_SUPPORTED_LIST query without OID_GEN_LINK_SPEED and OID_GEN_MEDIA_CONNECT_STATUS in the oid list, the adapter connected and setup successfully, when I applied those two oid to the list, the adapter couldn't connect. I hope you will be able to help me, vir0n Tag: Capi 2.0 - driver for Vista Tag: 94050
  - 9
    - Adding More than 3 Printers in Vista, Adding more than 3 LPT's In Hi, Did anyone able to add LPT4 thru LPT9 in windows Vista ? i tried to add LPT4 it says invalid port name till LPT9, but it is accepting LPT10 onwards. Is something wrong in my observation, precisely is my observation valid ??? how to add LPT4 in vista. Note : it has LPT 4, but not LPT4. Thanks and Regards, Neo Tag: Capi 2.0 - driver for Vista Tag: 94049
  - 10
    - Anti-Tampering Verification Hi everyone, I just need to clarify something in DTM regarding this 'Anti-Tampering Verification' that was displayed in DTM when I was preparing my submission package. On the 'Submission Status' window, it shows the following message: Anti-Tampering Verification Verification.wtl File Does Not Exist I search for info on this term on the DTM Help, MSDN and Microsoft website but found none. I don't know what's this message means and whether should it be a cause for concern. I don't want, later on, that because of this I'll have problem with my WHQL submission, as you know it involves some $$$. Anyway, my submission summary shows that my device has pass all the required tests. Anyone knows about this? Thanks! Tag: Capi 2.0 - driver for Vista Tag: 94043
  - 11
    - Could not load Driver dynamically into Vista Kernel... Hi, i have a (simple) 32bit driver that works perfect for Windows 2000 and XP, but i cant load it into a running vista system. Does the driver has to be signed to make it loaddable into vista kernel? If so, how can i sign it with a valid signatur or whatever certificate i have to use,...? TIA Best regards Kerem Gümrükcü Tag: Capi 2.0 - driver for Vista Tag: 94041
  - 12
    - OEMTextOut glyph position problem We are writing a special plotter driver and we are seeing some strange things when we are looking at the GLYPHPOS structures being sent to OEMTextOut call... The glyphs start out their position correctly but at some point we get a negative Y coordinates or the offsets for the Y coordinates restart at low numbers and all text lines are getting mixed. We noticed that it starts happening when Y > 7200 in *PrintableArea: PAIR(7200, 7200) of GPD file We need to support big table sizes 48x48 inches and have to have a good text quality for small fonts so we need to set *DPI: PAIR(1200,1200) *TextDPI: PAIR(1200, 1200) If we set DPI for lower number Windows programs like MS Word, Corel return low quality Text. Setting DPI for low resolution but TextDPI for high resolution doesn't make text better. Are there any limitation on DPI * Y ? Any help would be greatly appreciated. Tag: Capi 2.0 - driver for Vista Tag: 94040
  - 13
    - build utility I'm Building a user mode component modeled on the user component of minispy As I understand this, I need to build this with BUILD tool. The bit that I'm building will be a DLL that will hook up to other stuff... So when I use BUILD and the OSR ddkbuild tool in a very generic way, specifing TARGETNAME=NvDrvComm TARGETTYPE=DYNLINK UMTYPE=windows USE_MSVCRT=1 C_DEFINES=$(C_DEFINES) -DUNICODE -D_UNICODE -DNVDRVCOMM_EXPORTS LINKLIBS=$(SDK_LIB_PATH)\shell32.lib INCLUDES=$(INCLUDES); \ $(IFSKIT_INC_PATH); \ $(DDK_INC_PATH); \ ..\inc TARGETLIBS=$(TARGETLIBS) \ $(IFSKIT_LIB_PATH)\fltLib.lib \ $(IFSKIT_LIB_PATH)\kernel32.lib \ $(IFSKIT_LIB_PATH)\ntdll.lib SOURCES=NvDrvComm.cpp\ NvDrvComm.rc !if "$(DDK_TARGET_OS)"=="WinLH" _NT_TARGET_VERSION=$(_NT_TARGET_VERSION_WINXP) !endif But the build is complaining that it cannot find the DEF file. This creates an error. I built a DEF file by hand and that stopped the BUILD from complaining about the missing def file. BUT this project is on going and if I'm already using the declspec attributes for the things I need to export, why is BUILD complaining about the DEF file? I'd hate to think that I'll need to rewrite the def file everytime I want to add another export!? -- Gak - Finecats Tag: Capi 2.0 - driver for Vista Tag: 94038
  - 14
    - IRP pending at unload on filter driver. Hello, I've made a search about this problem across the newsgroup and the web. I've seen a lot of response and always the same things: "Your routine is attach to an IRP...bla bla bla". But I see nowhere the way to resolve this problem. I add a cleanup routine (Dispatch cleanup) with an IoCancelRoutine and IoComplete function. In my unload function I add an IoDeleteDevice and an IoDetachDevice. What can I add more to avoid a BSOD when I unload my drivers ? Regards, Tag: Capi 2.0 - driver for Vista Tag: 94035
  - 15
    - standard device requests and winusb Given: my USB device attached and detected; WinUSB.sys installed and executing. After obtaining my USB device handle (createfile), I can successfully execute WinUSB_Initialize. I then call WinUsb_ControlTransfer and fetch the status. Next I call WinUsb_ControlTransfer to set a feature (<WINUSB_SETUP_PACKET> RequestType=0, Request=3, Value=1, Index=0, Length=0). The call fails and the GetLastError string="A device attached to the system is not functioning." Note: 1. "Value=1" ==>> DEVICE_REMOTE_WAKEUP 2. This error also occurs when RequestType=1 or 2 Did I set a field incorrectly? Is the sequence of operations incorrect? Thanks dmm Tag: Capi 2.0 - driver for Vista Tag: 94033
  - 16
    - how to disable USB disk cache I am trying to validate the SCSI commands in our USB drive product, and use file copy back and forth to create more traffic. However, I noticed the SCSI read command is passed down to USB device only the first time read. I think there must be some disk cache enabled. but I already set the disk policy as "Optimize for quick removal", which, I believe, is supposed to disable the disk cache. Anyone has idea how to set up the system to allow me to see every read in device ? -Gary Tag: Capi 2.0 - driver for Vista Tag: 94032
  - 17
    - Network Configuration Interface Greetings, I am trying to learn how to configure network using INetCfg APIs. I need to understand how to install the actual adapter and associate TCP/ IP protocol with it. I would like to know exact order of steps needed to configure network. According to MSDN documentation, a network configuration object is created using CoCreateInstance function which is followed my enumerating interfaces and so on. I do not understand the full mechanics of INetCfg APIs. I will appreciate help toward making me understand/learn. Thanks Tag: Capi 2.0 - driver for Vista Tag: 94024
  - 18
    - handling parallel port interrupts Hello, I've got a question about timing incoming IR signals and decoding them in Windows. Here's my story. I've built a device which detects IR signals at 38KhZ and sends interrupts to the parallel port. Then I created (well, I didn't write it entirely, but I edited one I found on the internet) a driver to catch those interrupts and I created a usermode program to interact with the driver. So far so good, everything seemed to work fine. I receive interrupts when I press a button on my remote control or when I just connect a wire between pin 2-9 and 10 of the parallel port. But there's also a problem. For some reason, I receive way too few interrupts when I press a button on my remote control, and the time between the interrupts always is nearly identical. My only guess is that for some reason processing an interrupt hasn't finished yet when the next interrupt arrives and that therefore that interrupt doesn't get handled. That should also explain why the time between logged interrupts is nearly identical; it always takes the same time to complete one interrupt and after that it can handle another. But I don't get why handling the interrupt would take that long. My pc should be fast enough to handle it. Here's my isr and dpc routine and after that the part in DriverEntry where I connect the interrupt to my driver. When an interrupt occurs, first the isr gets called and then the dpcroutine. I hope any of you have an idea why it doesn't handle all interrupts or what the problem is and how it can be fixed. Thanks in advance, Floris van Nee BOOLEAN hwinterfaceIsr(IN PKINTERRUPT Interrupt, IN OUT PVOID Context) { PDEVICE_OBJECT DeviceObject = Context; //KdPrint( ("hwinterface.sys: Interrupt Service Routine\n") ); /* We should check if the interrupt comes from us and return */ IoRequestDpc(DeviceObject, DeviceObject->CurrentIrp, NULL); return TRUE; } VOID hwinterfaceDpcRoutine(IN PKDPC Dpc, PDEVICE_OBJECT DeviceObject, IN PIRP Irp, IN PVOID Context) { PLOCAL_DEVICE_INFO DeviceExtension; PIRP pIrp; pIrp = DeviceObject->CurrentIrp; DeviceExtension = DeviceObject->DeviceExtension; //Get the current 'time' and print it to kernel debug KeQueryTickCount((PLARGE_INTEGER)&TickCount); KdPrint(("Interrupt: %d", TickCount)); return; } DeviceExtension = DeviceObject->DeviceExtension; DeviceExtension->Level = 7; DeviceExtension->Vector = DeviceExtension->Level; MappedVector = HalGetInterruptVector(Isa, 0, DeviceExtension->Level, DeviceExtension->Vector, &Irql, &DeviceExtension->Affinity); if (MappedVector == 0) DbgPrint("hwinterface.sys: HalGetInterruptVector failed\n"); IoInitializeDpcRequest(DeviceObject,hwinterfaceDpcRoutine); KdPrint(("%d", &DeviceExtension->InterruptObject)); status = IoConnectInterrupt(&DeviceExtension->InterruptObject, // InterruptObject hwinterfaceIsr, // ServiceRoutine DeviceObject, // ServiceContext NULL, // SpinLock MappedVector, // Vector Irql, // Irql Irql, // SynchronizeIrql Latched, // InterruptMode FALSE, // ShareVector DeviceExtension->Affinity, // ProcessorEnableMask FALSE); // FloatingSave if (!NT_SUCCESS (status)) DbgPrint("hwinterface.sys: IoConnectInterrupt Failed\n"); Tag: Capi 2.0 - driver for Vista Tag: 94023
  - 19
    - Mailslot and Drivers hi all! i need a little help, i'm trying to communicate with a mailslot created in user mode, but when i try to open the mail slot with ZwOpenFile it fails with 0xC0000043 that means STATUS_SHARING_VIOLATION .... This is the code: //----------------------- ret = ZwOpenFile( &hand, GENERIC_WRITE, &oa, &iosb, 0, FILE_NON_DIRECTORY_FILE); //----------------------- are the flags used right? can someone help me please? ^_^ Thank you anyway and sorry 4 my english :) Tag: Capi 2.0 - driver for Vista Tag: 94020
  - 20
    - About Windows Filtering Platform - Callout Modules API - Kernel Mo Hi all, I am very much new to Windows Filtering Platform and Kernel level Programming.I want to try out Packet Modification feature that is a part of the Callout Module API in WFP . Can I get any sample code for this Callout Module API .And Also want to know is there any structured way of learning this kind of kernel level program. And also want to initiate certain discussion about this WFP ? Some docs related to this WFP convey me that I need to write a driver or hook that will listen for the incoming packets of the NIC and then modify the packet.Can anyone confirm me that whether packet modification is really possible in WFP and If so please provide me with some guidelines.They also say it is alternate for the NDIS Mini port driver developments .? Tag: Capi 2.0 - driver for Vista Tag: 94011
  - 21
    - Regarding createfile Hi All I want to set some permission like(Read only or Read/Write) on USB, CD and i am using createfile. But i am not able to set this kind of permission can i have any clue. with regards RYK Tag: Capi 2.0 - driver for Vista Tag: 94007
  - 22
    - Wrestling with Windows Filtering Platform Is the use of the family "Packet Injection Functions" mandatory for mechanism "Pend-Complete" without modification packet data? Tag: Capi 2.0 - driver for Vista Tag: 94006
  - 23
    - Request delegation in WDF? Hi all, I am still wondering how on earth should the, what the book "Programming the Microsoft Windows Driver Model" calls, delegate action, be handled in WDF for a bus driver? It seems very easy if you read the documentation; just take the request, call WdfDeviceGetIoTarget() on the device that wants to forward the request, send the request and that's about it. But as we learned yesterday it doesn't work. WdfRequestSend() fails every time although we verified that the target is working fine and can receive ioctls created with WdfIoTargetSendInternalIoctlSynchronously(). The same result even if we called WdfRequestFormatRequestUsingCurrentType() before the send command. So it has to do something with the Request object? We tried to create a new request with WdfRequestCreateFromIrp() by taking the original IRP with WdfRequestWdmGetIrp() but it doesn't seem to create a new IRP, instead just copying a pointer to the old one which causes a BSOD for exhausted stack. So finally we got something working by creating a new IRP and poking around with the stack location just as we would in WDM and creating a WDF Request from that IRP - but it seems very odd that we have to work on the WDM side even when we have this beautiful abstraction around it. Now we have a hybrid of WDM inside WDF and completing request correctly seems to be a nightmare - which still doesn't work... So is Request delegation possible in WDF and if so, how? Tag: Capi 2.0 - driver for Vista Tag: 94004
  - 24
    - No way to full-proof DeviceIoControl() ??? I am in the process of developing a WDM device driver which already handles pretty well several IOCTL codes when sent by a user-mode application, using DeviceIoControl(). Now I want to make sure that driver can handle any crazy input that an application programmer may throw at it. For that purpose I placed in the switch case for the pIoStackLocation- >Parameters.DeviceIoControl.IoControlCode a default case that all it does is this: default: { pIRP->IoStatus.Information = 0; ntStatus = STATUS_INVALID_DEVICE_REQUEST; pIRP->IoStatus.Status = ntStatus; IoCompleteRequest(pIRP, IO_NO_INCREMENT); return ntStatus; } This works great (i.e. returns an error with a suitable GetLastError() code) when I test it with an unrecognized IOCTL as follows: int dummy; if ( !DeviceIoControl(hWdm, IOCTL_UNRECOGNIZED, NULL, 0, // input &dummy, sizeof(dummy), // output &BytesReturned, NULL)) but when I pass the output paramter as NULL, too (see below), the system hangs (i.e. only a hard reset would get it out of that state): if ( !DeviceIoControl(hWdm, IOCTL_UNRECOGNIZED, NULL, 0, // input NULL, 0, // output &BytesReturned, NULL)) Notice, the only difference is "NULL, 0" vs. "&dummy, sizeof(dummy)" ... On the WinDbg side, all I can see is the following: Access violation - code c0000005 (!!! second chance !!!) *** ERROR: Symbol file could not be found. Defaulted to export symbols for ks.sys - ks!KsDispatchIrp+0x3b: f82b9f0d ff10 call dword ptr [eax] Which doesn't give me enough information about what's happening in the driver. So, for now, my workaround is to never pass a NULL output buffer pointer to DeviceIoControl() - but is it really impossible to protect a driver against something like this? I thought that (not) handling an unrecognized IOCTL is a no brainer (as described above in the 'default' case). What am I missing? Thanks, Don Tag: Capi 2.0 - driver for Vista Tag: 93993
  - 25
    - Portable Devices device class in Vista My USB MSD device resulted in an device "generic volume" under "Storage volumes" in XP Device Manager. But in Vista that instance does not show up, instead, an instance with my product name shows up under 'Portable Devices" device class in Vista. Can anyone tell me what does this change mean to the same USB drive ? -Gary Tag: Capi 2.0 - driver for Vista Tag: 93992

Is there already a driver for Visa wich is working on a PCI ISDN Card with
Capi ????

Ruud

Re: Capi 2.0 - driver for Vista by Alexander

Alexander
Sun Apr 22 12:38:53 CDT 2007

I'm afraid ISDN is so last century, nobody bothers anymore.

"ruudd" <ruud@doek.tweakdsl.nl> wrote in message
news:413B28B3-A9A8-418F-9947-97EF5224294A@microsoft.com...
> Is there already a driver for Visa wich is working on a PCI ISDN Card with
> Capi ????
>
> Ruud

Top

Re: Capi 2.0 - driver for Vista by Mathias

Mathias
Mon Apr 23 00:19:26 CDT 2007

ruudd wrote:

> Is there already a driver for Visa wich is working on a PCI ISDN Card with Capi ????
>
> Ruud

Yes, I have written this driver. Looks for Billion or OEM Customer from Billion for PCI Card
with Cologne chip set.

elli

Top