Rendering Plugin's EnablePDEV

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
    - Interrupts in PCMCIA device driver Hi, I have been struggling with this problem for some time, so any help from someone who has written a PCMCIA device driver would be greatly appreciated! I have written a working Win2K device driver for a PCI device, and am now writing a device driver for the PCMCIA version of the device (some code included below). My driver does not receive interrupts although the call to IoConnectInterrupt() succeeds. I have gone through the PSCR smartcard device driver code in the DDK samples. I am also familiar with the DisabeISAToPCIRouting registry setting - didn't make a difference in my case. Is there something different one needs to do to receive interrupts in a PCMCIA device driver as compared to a PCI device driver? Thanks! ----------------- Some code from the driver ------------------------ GLOBALS Globals; #ifdef ALLOC_PRAGMA #pragma alloc_text (INIT, DriverEntry) #pragma alloc_text (PAGE, PolarisAddDevice) #pragma alloc_text (PAGE, PolarisCreateClose) #pragma alloc_text (PAGE, PolarisDispatchIoctl) #pragma alloc_text (PAGE, PolarisReadWrite) #pragma alloc_text (PAGE, PolarisDispatchPnp) #pragma alloc_text (PAGE, PolarisUnload) #endif NTSTATUS DriverEntry( IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath ) { // Save the RegistryPath. Globals.RegistryPath.MaximumLength = RegistryPath->Length + sizeof(UNICODE_NULL); Globals.RegistryPath.Length = RegistryPath->Length; Globals.RegistryPath.Buffer = ExAllocatePoolWithTag ( PagedPool, Globals.RegistryPath.MaximumLength, POLARIS_POOL_TAG); if (Globals.RegistryPath.Buffer) { RtlCopyUnicodeString(&Globals.RegistryPath, RegistryPath); } else { PolarisDebugPrint ((0, "Couldn't allocate pool for registry path.")); return STATUS_INSUFFICIENT_RESOURCES; } // Populate the Dispatch routines DriverObject->MajorFunction[IRP_MJ_PNP] = PolarisDispatchPnp; DriverObject->MajorFunction[IRP_MJ_POWER] = PolarisDispatchPower; DriverObject->MajorFunction[IRP_MJ_CREATE] = PolarisCreateClose; DriverObject->MajorFunction[IRP_MJ_CLOSE] = PolarisCreateClose; DriverObject->MajorFunction[IRP_MJ_DEVICE_CONTROL] = PolarisDispatchIoctl; DriverObject->MajorFunction[IRP_MJ_READ] = PolarisReadWrite; DriverObject->MajorFunction[IRP_MJ_WRITE] = PolarisReadWrite; DriverObject->MajorFunction[IRP_MJ_CLEANUP] = PolarisCleanup; // Populate AddDevice/DriverUnload DriverObject->DriverExtension->AddDevice = PolarisAddDevice; DriverObject->DriverUnload = PolarisUnload; return STATUS_SUCCESS; } /* * This routine adds a device to the system */ NTSTATUS PolarisAddDevice( IN PDRIVER_OBJECT DriverObject, IN PDEVICE_OBJECT PhysicalDeviceObject ) { NTSTATUS status = STATUS_SUCCESS; PDEVICE_OBJECT deviceObject = NULL; PPOLARIS_DEVICE_INFO pDeviceInfo = NULL; POWER_STATE powerState; PAGED_CODE(); // Create a device status = IoCreateDevice (DriverObject, sizeof (POLARIS_DEVICE_INFO), NULL, FILE_DEVICE_NETWORK, FILE_DEVICE_SECURE_OPEN, FALSE, &deviceObject); if (!POLARIS_SUCCESS (status)) { return status; } // Initialize the device extension. pDeviceInfo = (PPOLARIS_DEVICE_INFO) deviceObject->DeviceExtension; // Set the initial state of the FDO INITIALIZE_PNP_STATE(pDeviceInfo); // Store the PDO pDeviceInfo->UnderlyingPDO = PhysicalDeviceObject; // Set device power state pDeviceInfo->DevicePowerState = PowerDeviceD0; // Tell lower driver the power state powerState.DeviceState = pDeviceInfo->DevicePowerState; PoSetPowerState ( deviceObject, DevicePowerState, powerState ); // Tell the Plug & Play system that this device will need an interface status = IoRegisterDeviceInterface ( PhysicalDeviceObject, (LPGUID) &GUID_CISCO_AIRO_DEVICE_INTERFACE_CLASS, NULL, &pDeviceInfo->InterfaceName); if (!POLARIS_SUCCESS (status)) { IoDeleteDevice (deviceObject); PolarisDebugPrint ((2, "PolarisAddDevice: returning status: %d\n", status)); return status; } // Attach device to the device stack pDeviceInfo->NextLowerDriver = IoAttachDeviceToDeviceStack( deviceObject, PhysicalDeviceObject); // // Initialize Remove Lock // IoInitializeRemoveLock (&pDeviceInfo->RemoveLock , POLARIS_POOL_TAG, 1, // MaxLockedMinutes 5); // HighWatermark, this parameter is used only on checked build. // Set the flag if the device is not holding a pagefile // crashdump file or hibernate file. // Clear the DO_DEVICE_INITIALIZING flag. // Note: Do not clear this flag until the driver has set the // device power state and the power DO flags. deviceObject->Flags |= DO_BUFFERED_IO; deviceObject->Flags |= DO_POWER_PAGABLE; deviceObject->Flags &= ~DO_DEVICE_INITIALIZING; pDeviceInfo->Self = deviceObject; pDeviceInfo->Removed = FALSE; pDeviceInfo->Started = FALSE; pDeviceInfo->InterruptRegistered = FALSE; pDeviceInfo->RxBufferLen = 32 * PAGE_SIZE; // Hardcoded ? #ifdef BLOCKING_READ pDeviceInfo->ReadEventHandle = NULL; pDeviceInfo->ReadTimeOut.QuadPart = -(10000 * 2000); // 1 second timeout, hardcoded #endif return status; } /* * This routine handles PnP IRPs */ NTSTATUS PolarisDispatchPnp ( IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp ) { PPOLARIS_DEVICE_INFO pDeviceInfo; PIO_STACK_LOCATION stack; PDEVICE_OBJECT attachedPDO; NTSTATUS status = STATUS_SUCCESS; BOOLEAN irpSkipped = FALSE; PolarisDebugPrint((3, "PolarisDispatchPnp called\n")); PAGED_CODE (); pDeviceInfo = (PPOLARIS_DEVICE_INFO) DeviceObject->DeviceExtension; attachedPDO = pDeviceInfo->NextLowerDriver; stack = IoGetCurrentIrpStackLocation (Irp); if (Deleted == GET_CURRENT_PNP_STATE(pDeviceInfo)) { // Since the device is removed, we will not hold any IRPs. // We just fail it. Irp->IoStatus.Status = STATUS_DELETE_PENDING; IoCompleteRequest (Irp, IO_NO_INCREMENT); return STATUS_DELETE_PENDING; } // Acquire the remove lock status = IoAcquireRemoveLock (&pDeviceInfo->RemoveLock, Irp); if (!POLARIS_SUCCESS (status)) { Irp->IoStatus.Status = status; IoCompleteRequest (Irp, IO_NO_INCREMENT); return status; } // Print minor function PolarisDebugPrint((0, "PnP Minor function: %s\n", PnPMinorFunctionString(stack->MinorFunction))); // Process IRP switch (stack->MinorFunction) { case IRP_MN_START_DEVICE: if (!pDeviceInfo->Started) { // We have to call the underlying driver first status = PolarisCallLowerDriver(attachedPDO, Irp); if (status == STATUS_SUCCESS) { // The device is starting. status = PolarisStartDevice(DeviceObject, Irp); if(POLARIS_SUCCESS(status)) { status = IoSetDeviceInterfaceState(&pDeviceInfo->InterfaceName, TRUE); if (!POLARIS_SUCCESS (status)){ PolarisDebugPrint((0, "IoSetDeviceInterfaceState failed: 0x%x\n", status)); Irp->IoStatus.Status = status; IoCompleteRequest (Irp, IO_NO_INCREMENT); // Release the remove lock IoReleaseRemoveLock(&pDeviceInfo->RemoveLock, Irp); return status; } // Set the PnP state to Started SET_NEW_PNP_STATE(pDeviceInfo, Started); pDeviceInfo->Started = TRUE; pDeviceInfo->Removed = FALSE; HardwareEnableInterrupts(pDeviceInfo); } } } break; case IRP_MN_QUERY_REMOVE_DEVICE: status = PolarisCanRemoveDevice(DeviceObject); if(POLARIS_SUCCESS(status)) { SET_NEW_PNP_STATE(pDeviceInfo, RemovePending); status = PolarisCallLowerDriver(attachedPDO, Irp); } break; case IRP_MN_SURPRISE_REMOVAL: // The device has been unexpectedly removed from the machine // and is no longer available for I/O. Stop all access to the device. // Release any resources associated with the device, but leave the // device object attached to the device stack until the PnP Manager // sends a subsequent IRP_MN_REMOVE_DEVICE request. // You should fail any outstanding I/O to the device. You will // not get a remove until all the handles open to the device // have been closed. pDeviceInfo->Removed = TRUE; pDeviceInfo->Started = FALSE; // Release system resources status = PolarisReleaseResources(DeviceObject); if(POLARIS_SUCCESS(status)) { // Set the PnP state to SurpriseRemovePending SET_NEW_PNP_STATE(pDeviceInfo, SurpriseRemovePending); } break; case IRP_MN_REMOVE_DEVICE: // Relinquish all resources here. // Detach and delete the device object so that // your driver can be unloaded. You get remove // either after query_remove or surprise_remove. if(!pDeviceInfo->Removed) { pDeviceInfo->Removed = TRUE; pDeviceInfo->Started = FALSE; // Stop the Adapter HardwareStopAdapter(pDeviceInfo); // Release system resources status = PolarisReleaseResources(DeviceObject); if(POLARIS_SUCCESS(status)) { // Set the PnP state to SurpriseRemovePending SET_NEW_PNP_STATE(pDeviceInfo, RemovePending); } status = PolarisCallLowerDriver(attachedPDO, Irp); } if(POLARIS_SUCCESS(status)) { // Set the PnP state to Deleted SET_NEW_PNP_STATE(pDeviceInfo, Deleted); // Disable the interface IoSetDeviceInterfaceState(&pDeviceInfo->InterfaceName, FALSE); // Remove the device and all references IoDeleteSymbolicLink(&pDeviceInfo->InterfaceName); IoDetachDevice(pDeviceInfo->NextLowerDriver); IoDeleteDevice(DeviceObject); } break; case IRP_MN_QUERY_STOP_DEVICE: status = PolarisCanStopDevice(DeviceObject); if(POLARIS_SUCCESS(status)) { SET_NEW_PNP_STATE(pDeviceInfo, StopPending); status = PolarisCallLowerDriver(attachedPDO, Irp); } break; case IRP_MN_STOP_DEVICE: if(pDeviceInfo->Started) { // Stop the Adapter HardwareStopAdapter(pDeviceInfo); // Release system resources status = PolarisReleaseResources(DeviceObject); if(POLARIS_SUCCESS(status)) { // Mark the device as stopped. IoSetDeviceInterfaceState(&pDeviceInfo->InterfaceName, FALSE); SET_NEW_PNP_STATE(pDeviceInfo, Stopped); } pDeviceInfo->Started = FALSE; status = PolarisCallLowerDriver(attachedPDO, Irp); } break; default: // This is an Irp that is only useful for underlying drivers status = PolarisCallLowerDriver(attachedPDO, Irp); irpSkipped = TRUE; break; } if (irpSkipped == FALSE) { // Don't touch the status field of irps we don't process Irp->IoStatus.Status = status; } PolarisDebugPrint((3, "PolarisDispatchPnp status: 0x%x\n", status)); IoCompleteRequest(Irp, IO_NO_INCREMENT); // Release the remove lock IoReleaseRemoveLock(&pDeviceInfo->RemoveLock, Irp); return status; } NTSTATUS PolarisStartDevice ( IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp ) { PCM_RESOURCE_LIST resourcesTranslated; PCM_RESOURCE_LIST resources; PCM_PARTIAL_RESOURCE_DESCRIPTOR resource; PCM_PARTIAL_RESOURCE_DESCRIPTOR resourceTranslated; PCM_PARTIAL_RESOURCE_LIST partialResourceList; PCM_PARTIAL_RESOURCE_LIST partialResourceListTranslated; PCM_FULL_RESOURCE_DESCRIPTOR fullListTranslated; PIO_STACK_LOCATION stack; PPOLARIS_DEVICE_INFO pDeviceInfo; NTSTATUS status = STATUS_SUCCESS; ULONG index; BOOLEAN foundInterruptResource = FALSE; int count = 0; PAGED_CODE(); // PolarisDebugPrint((3, "PolarisStartDevice called\n")); pDeviceInfo = (PPOLARIS_DEVICE_INFO) DeviceObject->DeviceExtension; stack = IoGetCurrentIrpStackLocation (Irp); // // Do whatever initialization needed when starting the device: // gather information about it, update the registry, etc. // if ((NULL != stack->Parameters.StartDevice.AllocatedResources) && (NULL != stack->Parameters.StartDevice.AllocatedResourcesTranslated)) { // // Set up the resource information that we will use to access the // controller hardware. We always expect only 1 full set of resources. // In that list we expect a DMA channel, an Interrupt vector, and 2 I/O Port // ranges. If we don't see all the required resources we will woof. // resourcesTranslated = stack->Parameters.StartDevice.AllocatedResourcesTranslated; partialResourceListTranslated = &resourcesTranslated->List[0].PartialResourceList; resourceTranslated = &partialResourceListTranslated->PartialDescriptors[0]; resources = stack->Parameters.StartDevice.AllocatedResources; partialResourceList = &resources->List[0].PartialResourceList; resource = &partialResourceList->PartialDescriptors[0]; ASSERT( resourcesTranslated->Count == 1 ); fullListTranslated = &resourcesTranslated->List[0]; // Set up the bus information pDeviceInfo->BusType = fullListTranslated->InterfaceType; pDeviceInfo->BusNumber = fullListTranslated->BusNumber; PolarisDebugPrint((0, "PolarisStartDevice: BusType = %d\n", pDeviceInfo->BusType)); // // Parameters.StartDevice.AllocatedResources points to a // CM_RESOURCE_LIST describing the hardware resources that // the PnP Manager assigned to the device. This list contains // the resources in raw form. Use the raw resources to program // the device. // // Parameters.StartDevice.AllocatedResourcesTranslated points // to a CM_RESOURCE_LIST describing the hardware resources that // the PnP Manager assigned to the device. This list contains // the resources in translated form. Use the translated resources // to connect the interrupt vector, map I/O space, and map memory. // // If it is a PCI card, do 16-bit I/O operations if (pDeviceInfo->BusType == PCIBus) { do8bitIO = 0; } for (index = 0; index < partialResourceList->Count; index++, resource++, resourceTranslated++) { switch (resource->Type) { case CmResourceTypePort: { // use the second port, device dependent condition if (pDeviceInfo->BusType == PCIBus) { if (count == 0 ) { count ++; break; } } switch (resourceTranslated->Type) { case CmResourceTypePort: // PolarisDebugPrint((2, "Resource RAW Port: (%x) Length: (%d)\n", // resource->u.Port.Start.LowPart, resource->u.Port.Length)); // // PolarisDebugPrint((2, // "Resource Translated Port: (%x) Length: (%d)\n", // resourceTranslated->u.Port.Start.LowPart, // resourceTranslated->u.Port.Length)); // Set the base I/O address of the device pDeviceInfo->DeviceBaseIO = (UCHAR *)resourceTranslated->u.Port.Start.u.LowPart; break; case CmResourceTypeMemory: PolarisDebugPrint((2, "Resource Translated Memory: (%x) Length: (%d)\n", resourceTranslated->u.Memory.Start.LowPart, resourceTranslated->u.Memory.Length)); // // Perform memory mapping here. // break; default: // PolarisDebugPrint((0, "PolarisStartDevice: Unhandled resource_type (0x%x)\n", // resourceTranslated->Type)); TRAP (); break; } } break; case CmResourceTypeDma: { DEVICE_DESCRIPTION deviceDesc; PolarisDebugPrint((0, "PolarisStartDevice: DMA - %04x\n", resourceTranslated->u.Dma.Channel) ); // Call PolarisSetupDMA() here if DMA is needed } break; case CmResourceTypeMemory: // PolarisDebugPrint((2, "Resource RAW Memory: (%x) Length: (%d)\n", // resource->u.Memory.Start.LowPart, resource->u.Memory.Length)); // PolarisDebugPrint((2, "Resource Translated Memory: (%x) Length: (%d)\n", // resourceTranslated->u.Memory.Start.LowPart, resourceTranslated->u.Memory.Length)); // Perform memory address mapping with PolarisMapDeviceAddress(). break; case CmResourceTypeInterrupt: // PolarisDebugPrint((0, "PolarisStartDevice: CmResourceTypeInterrupt\n")); if ( resourceTranslated->Flags & CM_RESOURCE_INTERRUPT_LATCHED) { pDeviceInfo->InterruptMode = Latched; } else { pDeviceInfo->InterruptMode = LevelSensitive; } pDeviceInfo->ControllerVector = resourceTranslated->u.Interrupt.Vector; pDeviceInfo->ProcessorMask = resourceTranslated->u.Interrupt.Affinity; pDeviceInfo->ControllerIrql = (KIRQL)resourceTranslated->u.Interrupt.Level; pDeviceInfo->SharableVector = TRUE; pDeviceInfo->SaveFloatState = FALSE; foundInterruptResource = TRUE; break; default: // PolarisDebugPrint((0, "Unhandled resource type (0x%x)\n", resource->Type)); break; } } if (foundInterruptResource == TRUE) { // PolarisDebugPrint((0, "PolarisStartDevice: Connecting Interrupt\n")); // Initialize the spin lock KeInitializeSpinLock(&pDeviceInfo->IntrSpinLock); // Connect the interrupt status = IoConnectInterrupt( &pDeviceInfo->InterruptObject, PolarisISR, pDeviceInfo, &pDeviceInfo->IntrSpinLock, pDeviceInfo->ControllerVector, pDeviceInfo->ControllerIrql, pDeviceInfo->ControllerIrql, pDeviceInfo->InterruptMode, pDeviceInfo->SharableVector, pDeviceInfo->ProcessorMask, pDeviceInfo->SaveFloatState ); if ( POLARIS_SUCCESS(status) ) { pDeviceInfo->InterruptRegistered = TRUE; } else { return status; } } // If successful and got memory/IO space, initialize the H/W if ( POLARIS_SUCCESS(status) && ((pDeviceInfo->DeviceVirtualAddress) || (pDeviceInfo->DeviceBaseIO)) ) { // Initialize the Hardware status = HardwareInitializeAdapter(pDeviceInfo, pDeviceInfo->DeviceBaseIO); if (!POLARIS_SUCCESS(status)) { return STATUS_UNSUCCESSFUL; } } } // PolarisDebugPrint((0, "PolarisStartDevice: returning status: 0x%x\n", status)); return status; } void HardwareEnableInterrupts(PPOLARIS_DEVICE_INFO pDeviceInfo) { airo_info *ai = &(pDeviceInfo->ai); USHORT status; /* Reset the status register */ status = IN4500( ai, EVSTAT ); OUT4500( ai, EVACK, status ); /* Enable the interrupts */ if (!ai->interruptEnabled) { OUT4500( ai, EVINTEN, STATUS_INTS ); ai->interruptEnabled = TRUE; } } Tag: Rendering Plugin's EnablePDEV Tag: 34387
  - 2
    - a question about win2000 ddk PORTIO sample!!!!!! I use win2k DDK to build the PORTIO sample in DDK successfully. But something is wrong when I use the gpdread and gpdwrite to test the driver. I use command line "GpdWrite -b 1 2" to write the number 2 to assigned 'base port address + 1', and then "GpdRead -b 1 "to read out. But the number read out is always 0xFF. I also tested writing a number every 1000 milliseconds and reading every 600 millisecond, but the read-out number kept 0xFF. what does the sample mean? could you tell me why? Softice driver suite(driverworks) contains similar sample, things are same. ____________________________________________________________________________ _________________________ Test OS: win2000 server Develop Environment: win2k ddk, visual studio 6.0 sp5 Tag: Rendering Plugin's EnablePDEV Tag: 34386
  - 3
    - Loading filter driver during OS install I have a upper device filter driver that I need to load during install (ie. Hit F6 for scsi drivers). I was wondering if this has been done (I'm sure it has) and how to do it. I wonder about whether the txtsetup.oem actually loads and parses the inf early in the setup or not, and how you would actually code up the txtsetup.oem. Do you need to need to include a copy of the driver that your filtering (and it's inf) on your driver disk as well, or will this land from the media in time to be present when the filter driver's inf is parsed. -Dan Tag: Rendering Plugin's EnablePDEV Tag: 34383
  - 4
    - Palettes and kernel-streaming driver (USBCAMD2) Hello, I am writing a USB camera mini-driver using USBCAMD2. I have the basic driver working, but need to get the video into the desired format for proper viewing in DirectShow. The video is 8-bit grayscale, and is interlaced (I receive two fields in one "frame" from the camera and interlace them in the CamProcessRawVideoFrameEx () function in my minidriver. They are displayed on the screen using RGB8 (8-bit color.) I would like to know how I can describe (or set somehow) the color palette as a grayscale palette. I've tried converting to RGB24 in the minidriver and replicating the 8-bit pixel value that I receive from the camera in the RGB fields. This works, but is so slow that I'm dropping frames. Any suggestions or hints would be appreciated. Sincerely, Howard M. Harte ======================== Harte Technologies, LLC. (925) 551-0120 (voice) (925) 551-0125 (fax) http://www.hartetechnologies.com/ Tag: Rendering Plugin's EnablePDEV Tag: 34379
  - 5
    - Custom USB Driver Development Hi All I'm a newbie at this, so apologies in advance for any wrong information. I'm trying to write custom usb drivers for one of the usb products. I have win ddk and visual studio installed. Can somone explain me/give me a link on how to approach this problem. I'm quite lost at the moment and need serious help in getting started. pls advice Regards Tag: Rendering Plugin's EnablePDEV Tag: 34376
  - 6
    - USB Driver development Hi All I'm trying to generate custom drivers for one of our usb devices. I have windows DDK and Visual Studio Installed. Has anyone got a link that demonstrates how to proceed in generating custom drivers. I'm a beginner at this and kinda lost. Pls advice Regards Tag: Rendering Plugin's EnablePDEV Tag: 34375
  - 7
    - How to detect Network Cable Unplugged? Hi, For a netwrok card (ie. ethernet), how does windows know if the network cable is unplugged? Does the driver handle any polling routine? The reason I am asking is because I am trying to a virtual network driver which drives the traffic to an application. I need to find some way to determine if that application is running. Thanks, Billy. Tag: Rendering Plugin's EnablePDEV Tag: 34368
  - 8
    - HP deskjet on Windows XP The driver for this printer is included in WinXP and installs okay when plugging in the printers USB cable. My problem is that on the paper size list there is no "custom" size as refered to in the manual. I want to print on 3X5 index cards which is also not on the list. Even if I select a larger card like 4X6 and set margins to reduce it to 3X5 size it prints outside the margins. HP says I will have to wait for them to update the driver. Anyone know of a quicker fix for this??? Tag: Rendering Plugin's EnablePDEV Tag: 34362
  - 9
    - Driver to install a Digital Camera I followed all the instructions and when I connect the camera shows a note saying the driver for this harware is not installed. Then ask me to use the Windows MilleniumEdition disk which I don't have. How or where can I get the disk. I need the answer as fast as you can. Thanks Tag: Rendering Plugin's EnablePDEV Tag: 34361
  - 10
    - How does windows handle PCMCIA Ok, I really need to know how windows 2000/XP handles the insertion of a PCMCIA card. What I have discovered with my card is that occasionally (4-5%) of the time it works (I have found that in this case card enable is activated) and the rest of the time it fails (card enable is not activated). This only occures though within the VideoMiniport drivers. The PnP Functional Driver I wrote does not seem to have this problem. So if anyone can tell me/point me how exactly windows handles insertion or how the Videominiport deals with it, I wolud greatly appreciate it. -- Brian V. Minier Interactive Imaging Systems, Inc www.iisvr.com Tag: Rendering Plugin's EnablePDEV Tag: 34355
  - 11
    - Visual Studio library path size limit I have a project which takes quite a lot of library paths, due to our environment setup. The problem now is that the line in the *.dsp filefor the linker is more than 4Kb long. Is there a limit on how long the line may be? I mean the # ADD LINKER32 <linkeroptions> in the dsp file. When I paste in the project file all the library paths then Visual Studio can compile it, but when I exit the project VC asks me to safe the changes to the project file and when I try to reload the project the line is crippled. Any ideas how to circumvent this size limit? I tried to spread the line over several lines which worked, but as soon as I change something in the settings Visual Studio will rewrite the dsp file and create the long line again. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) Tag: Rendering Plugin's EnablePDEV Tag: 34354
  - 12
    - IoCancelIrp Step 1. We create IRP: IoBuildDeviceIoControlRequest Step 2. We pass IRP to other driver: IoCallDriver Step 3. We want to cancel this IRP: can we call IoCancelIrp ? The IRP can be already deleted by I/O Manager... How long IRP leaves and when we can use pIrp pointer obtained in the step 1? Thanks, Vitaly Kravtsov mailto:VitalyKravtsov@mail.ru Tag: Rendering Plugin's EnablePDEV Tag: 34339
  - 13
    - VideoDriver and PCMCIA Function Configuration Registers Is there a way to access the Function Configuration Registers is a VideoMiniport driver. I can access (somewhat) I/O memory (given to me through VideoPortGetAccessRanges) but nothing comes for the FCR's. Of course, given that the card gets mapped to ISA (determined from the VIDEO_PORT_CONFIG_INFO) I may not need to access the Registers. Also, any one who is famialar with the internal workings of the VideoPort functions, what PCMCIA Configuration Registers are needed for successful operation. Currently we only support a subset of the registers PC-Card requires because we are a CF-Card, could this cause a problem? Thanks in advance, yet again. -- Brian V. Minier Interactive Imaging Systems, Inc www.iisvr.com Tag: Rendering Plugin's EnablePDEV Tag: 34338
  - 14
    - How can I get selected option items from property sheet page? Hi. I am developing a printer driver which prints any document to an image file. I am using Unidrv.dll and Win2000 DDK sample Oemui.dll. There is one more component, rendering plug-in. I added a new property sheet page and a option item using a method in Oemui.dll like below. // source code // HRESULT hrOEMDocumentPropertySheets(PPROPSHEETUI_INFO pPSUIInfo, LPARAM lParam, IPrintOemDriverUI* pOEMHelp) { LONG_PTR lResult; ............ // Do action. switch(pPSUIInfo->Reason) { case PROPSHEETUI_REASON_INIT: { DWORD dwSheets = 0; PCBUSERDATA pUserData; POEMUIPSPARAM pOEMUIParam = (POEMUIPSPARAM) pPSUIInfo->lParamInit; HANDLE hHeap = pOEMUIParam->hOEMHeap; POEMDEV pOEMDev = (POEMDEV) pOEMUIParam->pOEMDM; COMPROPSHEETUI Sheet; DLGPAGE PageProp; // Init property page. memset(&Sheet, 0, sizeof(COMPROPSHEETUI)); Sheet.cbSize = sizeof(COMPROPSHEETUI); Sheet.Flags = CPSUIF_UPDATE_PERMISSION; Sheet.hInstCaller = ghInstance; Sheet.pCallerName = GetStringResource(hHeap, ghInstance, IDS_NAME); Sheet.pHelpFile = NULL; Sheet.pfnCallBack = OEMDocUICallBack; Sheet.pDlgPage = CPSUI_PDLGPAGE_ADVDOCPROP; Sheet.cOptItem = 1; Sheet.IconID = IDI_CPSUI_PRINTER; Sheet.pOptItemName = GetStringResource(hHeap, ghInstance, IDS_SECTION); Sheet.CallerVersion = 0x100; Sheet.OptItemVersion = 0x100; // Init user data. pUserData = (PCBUSERDATA) HeapAlloc(hHeap, HEAP_ZERO_MEMORY, sizeof(CBUSERDATA)); pUserData->hComPropSheet = pPSUIInfo->hComPropSheet; pUserData->pfnComPropSheet = pPSUIInfo->pfnComPropSheet; pUserData->pOEMUIParam = pOEMUIParam; Sheet.UserData = (ULONG_PTR) pUserData; // Create OptItems for page. Sheet.pOptItem = CreateOptItems(hHeap, Sheet.cOptItem); // Initialize OptItems Sheet.pOptItem[0].cbSize = sizeof(OPTITEM); Sheet.pOptItem[0].Level = 1; Sheet.pOptItem[0].Flags = OPTIF_COLLAPSE; Sheet.pOptItem[0].pName = GetStringResource(hHeap, ghInstance, IDS_SECTION); Sheet.pOptItem[0].Sel = pOEMDev->dwDriverData; Sheet.pOptItem[0].pOptType = CreateOptType(hHeap, 3); Sheet.pOptItem[0].pOptType->Type = TVOT_3STATES; Sheet.pOptItem[0].pOptType->pOptParam[0].pData = GetStringResource(hHeap, ghInstance, IDS_TIF); Sheet.pOptItem[0].pOptType->pOptParam[1].pData = GetStringResource(hHeap, ghInstance, IDS_JPG); Sheet.pOptItem[0].pOptType->pOptParam[2].pData = GetStringResource(hHeap, ghInstance, IDS_BMP); Sheet.pOptItem[0].pOptType->pOptParam[0].IconID = IDS_TIF; Sheet.pOptItem[0].pOptType->pOptParam[1].IconID = IDS_JPG; Sheet.pOptItem[0].pOptType->pOptParam[2].IconID = IDS_BMP; Sheet.pOptItem[0].pOptType->Count = 3; // Add property sheets. lResult = pPSUIInfo->pfnComPropSheet(pPSUIInfo->hComPropSheet, CPSFUNC_ADD_PCOMPROPSHEETUI, (LPARAM)&Sheet, (LPARAM)&dwSheets); } break; ............ } pPSUIInfo->Result = lResult; return S_OK; } And it works well. There was a newly added property sheet page in printing dialog. I'd like to let the user select an output file format(bmp, tif, etc.) through the property sheet page(using TVOT_3STATES in above source code) and add some more option items in the same sheet page. The problem is that I don't have any idea how I can get the results of what user selected through the option items in the property sheet page. There are some answers to similar question but not enough to understand how and what. I'd like to use the selected options in rendering plug-in module. Does anyone know the solution to this question? If possible, please show me some sample source codes. Or explain in detail. Thanks in advance. Tag: Rendering Plugin's EnablePDEV Tag: 34333
  - 15
    - Multiple IRP requests from one driver to another Hi All, My driver uses standard serial port driver. It set RTS signal and wait for CTS signal change. 1. Driver send IRP to serial port driver with control code IOCTL_SERIAL_WAIT_ON_MASK and doesn't wait for it. 2. Driver send IRP to serial port driver with control code IOCTL_SERIAL_SET_RTS and wait for it. 3. Driver wait for first IRP through the Event, passed to IoBuildDeviceIoControlRequest. This approach does not work. User mode application is locked and driver can not be unloaded. May be the IoSetCompletionRoutine is solution ? Thanks. VitalyKravtsov mailto:vitalykravtsov@mail.ru Tag: Rendering Plugin's EnablePDEV Tag: 34332
  - 16
    - Protocol driver, don't understand Hi, I try to understand how to write my protocol driver for a WLAN adapter. I read a sample in the PocketPC Platform Builder (Passthru). I don't understand everything, and there's still one thing that I don't get: how should I use this "driver" in my application to retrieve the packets? Can you give me some information to better understand a protocol driver and how to use it in an application. Thank you /Marco Tag: Rendering Plugin's EnablePDEV Tag: 34326
  - 17
    - PrintProcessor Installation problems on Win98SE/Me Hello All, I developed a minidriver and relative Print Processor for our Pos printer product on Win98Se and Me. Then I wrote a .INF file for install the package. The printer is installed correctly, but it doesn't catch my PrintProcessor. All the files (minidriver + printproc.) are copied in C:\WINDOWS\SYSTEM. But when I go to check with 'Regedit', what the installation has written into registry, I can see that no subkeys for my printprocess are been made in: HKLM\System\CurrentControlSet\Control\Print\Environments\Wi ndows 4.0\Print Processors; while the subkey of my printer is present, and into it the field "Print Processor" has "WinPrint" as value. By the way, I started to develop my PrintProcessor from Win98 DDK , modifing the Winprint sample included in src\printers\spooler' subdirectory. And, I took infos for insert printprocess from W98 DDK documentation. Where is my mistake? Somebody have any idea? Please, Help me. Below I inserted my INF file. TIA Giandomenico. [Version] Signature=$CHICAGO$ ver=01.00.03 Class=Printer Provider=%OLIVETTI% LayoutFile=layout.inf,layout1.inf,layout2.inf [SourceDisksNames] 1="PRT100 Res(180x180) PrinterDriver Disk",,0001 [Manufacturer] "OLIVETTI" [OLIVETTI] "PRT100 Res(180x180) Receipt" = PRT100EP.DRV,PRT100 Res (180x180) Receipt "PRT100_180x180 ReduceA4" = PRT100RE.DRV,PRT100_180x180 ReduceA4 ; ; Installer Sections ; [PRT100EP.DRV] CopyFiles=PRT100EP_COPY,UNI DataSection=UNI_DATA,PRT_PROCESS [PRT100RE.DRV] CopyFiles=PRT100RE_COPY,UNI DataSection=UNI_DATA,PRT_PROCESS ; Copy Sections ; [PRT100EP_COPY] PRT100EP.DRV POSPRINT.DLL [PRT100RE_COPY] PRT100Re.DRV POSPRINT.DLL [UNI] UNIDRV.DLL UNIDRV.HLP ICONLIB.DLL ; ; Data Sections ; [UNI_DATA] HelpFile=UNIDRV.HLP DefaultDataType=RAW [PRT_PROCESS] PrintProcessor=%POS_PrintProcess% [DestinationDirs] DefaultDestDir=11 [SourceDiskeFiles] PRT100EP.DRV=1,WIN98 PRT100Re.DRV=1,WIN98 POSPRINT.DLL=1,WIN98 ; ; Localizable Strings ; [Strings] OLIVETTI="OLIVETTI" CLASSNAME="Printer" POS_PrintProcess="POSPrintPROCESS,POSPRINT.DLL" Tag: Rendering Plugin's EnablePDEV Tag: 34324
  - 18
    - How can I get the results from newly added property sheet page? Hi. I am developing a printer driver which prints any document to an image file. I am using Unidrv.dll and Win2000 DDK sample Oemui.dll. There is one more component, rendering plug-in. I added a new property sheet page and a option item using a method in Oemui.dll like below. // source code // HRESULT hrOEMDocumentPropertySheets(PPROPSHEETUI_INFO pPSUIInfo, LPARAM lParam, IPrintOemDriverUI* pOEMHelp) { LONG_PTR lResult; ............ // Do action. switch(pPSUIInfo->Reason) { case PROPSHEETUI_REASON_INIT: { DWORD dwSheets = 0; PCBUSERDATA pUserData; POEMUIPSPARAM pOEMUIParam = (POEMUIPSPARAM) pPSUIInfo->lParamInit; HANDLE hHeap = pOEMUIParam->hOEMHeap; POEMDEV pOEMDev = (POEMDEV) pOEMUIParam->pOEMDM; COMPROPSHEETUI Sheet; DLGPAGE PageProp; // Init property page. memset(&Sheet, 0, sizeof(COMPROPSHEETUI)); Sheet.cbSize = sizeof(COMPROPSHEETUI); Sheet.Flags = CPSUIF_UPDATE_PERMISSION; Sheet.hInstCaller = ghInstance; Sheet.pCallerName = GetStringResource(hHeap, ghInstance, IDS_NAME); Sheet.pHelpFile = NULL; Sheet.pfnCallBack = OEMDocUICallBack; Sheet.pDlgPage = CPSUI_PDLGPAGE_ADVDOCPROP; Sheet.cOptItem = 1; Sheet.IconID = IDI_CPSUI_PRINTER; Sheet.pOptItemName = GetStringResource(hHeap, ghInstance, IDS_SECTION); Sheet.CallerVersion = 0x100; Sheet.OptItemVersion = 0x100; // Init user data. pUserData = (PCBUSERDATA) HeapAlloc(hHeap, HEAP_ZERO_MEMORY, sizeof(CBUSERDATA)); pUserData->hComPropSheet = pPSUIInfo->hComPropSheet; pUserData->pfnComPropSheet = pPSUIInfo->pfnComPropSheet; pUserData->pOEMUIParam = pOEMUIParam; Sheet.UserData = (ULONG_PTR) pUserData; // Create OptItems for page. Sheet.pOptItem = CreateOptItems(hHeap, Sheet.cOptItem); // Initialize OptItems Sheet.pOptItem[0].cbSize = sizeof(OPTITEM); Sheet.pOptItem[0].Level = 1; Sheet.pOptItem[0].Flags = OPTIF_COLLAPSE; Sheet.pOptItem[0].pName = GetStringResource(hHeap, ghInstance, IDS_SECTION); Sheet.pOptItem[0].Sel = pOEMDev->dwDriverData; Sheet.pOptItem[0].pOptType = CreateOptType(hHeap, 3); Sheet.pOptItem[0].pOptType->Type = TVOT_3STATES; Sheet.pOptItem[0].pOptType->pOptParam[0].pData = GetStringResource(hHeap, ghInstance, IDS_TIF); Sheet.pOptItem[0].pOptType->pOptParam[1].pData = GetStringResource(hHeap, ghInstance, IDS_JPG); Sheet.pOptItem[0].pOptType->pOptParam[2].pData = GetStringResource(hHeap, ghInstance, IDS_BMP); Sheet.pOptItem[0].pOptType->pOptParam[0].IconID = IDS_TIF; Sheet.pOptItem[0].pOptType->pOptParam[1].IconID = IDS_JPG; Sheet.pOptItem[0].pOptType->pOptParam[2].IconID = IDS_BMP; Sheet.pOptItem[0].pOptType->Count = 3; // Add property sheets. lResult = pPSUIInfo->pfnComPropSheet(pPSUIInfo->hComPropSheet, CPSFUNC_ADD_PCOMPROPSHEETUI, (LPARAM)&Sheet, (LPARAM)&dwSheets); } break; ............ } pPSUIInfo->Result = lResult; return S_OK; } And it works well. There was a newly added property sheet page in printing dialog. I'd like to let the user select an output file format(bmp, tif, etc.) through the property sheet page(using TVOT_3STATES in above source code) and add some more option items in the same sheet page. The problem is that I don't have any idea how I can get the results of what user selected through the option items in the property sheet page. There are some answers to similar question but not enough to understand how and what. I'd like to use the selected options in rendering plug-in module. Does anyone know the solution to this question? If possible, please show me some sample source codes. Or explain in detail. Thanks in advance. Tag: Rendering Plugin's EnablePDEV Tag: 34322
  - 19
    - linux's hdparm command equivalent in windows ?? Hi, When I issue the hdparm -S command on western digital hard disk, it does not sleep during inactivity. I would like to know : 1. if there is any equivalent command of hdparm in windows. 2. if western digital hard disk does not sleep under windwos too. rgds Shankar Tag: Rendering Plugin's EnablePDEV Tag: 34317
  - 20
    - How to compiling Ndis 5.0 NDIS_WDM sample for Win98se/ windows 2000? Dear sirs, I have build ndis 5.0 driver(NDIS_WDM) running windows 2000 well, how can I porting it to windows 98se/windows me? when I installed with windows 2000 version driver,got a problem as "NDIS.VXD,NTKERN.VXD could not be loaded". How to solve this problem. thanks. lonely Tag: Rendering Plugin's EnablePDEV Tag: 34313
  - 21
    - NDIS_WDM for Windows 2000 and Win98se/Me I'm trying to load my working Windows 2000 NDIS 5.0 driver on Windows ME. I've compiled using the BINARY_COMPATBLE switch, got a problem as "NDIS.VXD, NTKERN.VXD could not be loaded", Why? Tag: Rendering Plugin's EnablePDEV Tag: 34312
  - 22
    - About virtual serial setup problem Hi, I install virtual serial in win2k,it receive IRP_MN_QUERY_DEVICE_RELATIONS and remove last serial port i added ,then new serial port replace it , Does anyone know why it is? Thanks in advance Fzcat Tag: Rendering Plugin's EnablePDEV Tag: 34310
  - 23
    - Scheduled WorkItem takes two mintes to execute Hi, I experience long delays between the time I call NdisScheduleWorkItem to the time the WorkItem is executed. I have an NDIS miniport driver. When windows is shutting down it sends me a managment request to filter all incoming packets. I schedule this request with a work item. It takes windows from 10 seconds to two minute! to execute the workitem. Does anyone know why it takes windows so long? The OS i'm relating to is Win89SE. I have the shutdown patches installed. Thanks in advance, Yoni Baron, Conexant Systems. Tag: Rendering Plugin's EnablePDEV Tag: 34306
  - 24
    - Using system DMA in PCI Device I have a PCI Device and I want to write driver for it. The PCI bridge on the board is not busmaster and i can't use busmaster dma for dma operations. I want to know if i can use Syatem Dma to do Dma operations. and if i can, how may i add Dma Resource to PnP Resource list. Tag: Rendering Plugin's EnablePDEV Tag: 34301
  - 25
    - Does the vender can disable any property page of the printer?? Hello all, There are many property pages in the printer, like the "General", "Sharing", "Ports", "Advanced", and "Color Managment". Can I disable one of them (Ex: disable "Advance" page), or to disable all the radio buttons of one page(Ex: disable all the radio buttons of "Advance" page)? Thanks. Tag: Rendering Plugin's EnablePDEV Tag: 34300
- Next
  - 1
    - 1394 Isoch on Windows 2000 I have developed 1394 driver similar to 1394diag. Isoch operations(no special requirements like TAG or SYNC) works almost. But very few times, I observe the buffers are not transmitted even if they are attached. I see it on analyzer. I stop Isoch and start it. Still Isoch wont transmit. No error in allocating Isoch buffer resources, no error in attaching buffers but simply my Isoch completion callback never called. Attached buffer callback is called and no error is reported. I dont understand what is causing the problem. No error is returned for attach buffers. Finally I found a work around, not really useful :( Unplug the cable and plug again. Allocate Isoch buffer resources and attach buffers and Isoch talk. It works now. So unplugging and plugging is causing something to reset and Isoch transmit works. I am not undertstanding circumstance that causes this problem. But I observe very few times. If I initiate bus reset through software command, no use. Only unplugging and plugging device will help. I have temptation to blame microsoft 1394 bus driver because after attaching the buffer, it is bus driver that transmits the Isoch data. But I couldn't find out the circumstances clearly that are causing the problem nor the way to debug. Any gliches in Isoch operations after every bus reset? Thanks, Raj Tag: Rendering Plugin's EnablePDEV Tag: 34293
  - 2
    - About SetupDiSetDeviceRegistryProperty in win2K i use SetupDiSetDeviceRegistryProperty set SPDRP_HARDWAREID, use \src\general\setup\install is fine,but i copy it to my project , it failed and GetLastError()=87 best regards Fzcat char *inf="d:\\rial.inf"; char *hardid="*rial"; if (!SetupDiGetINFClass(inf,&ClassGUID,ClassName,sizeof(ClassName),0)) { return -1; } DeviceInfoSet = SetupDiGetClassDevs(&ClassGUID, 0, 0, DIGCF_PRESENT ); if (DeviceInfoSet == INVALID_HANDLE_VALUE) { return -1; } // Now create the element. // Use the Class GUID and Name from the INF file. // DeviceInfoData.cbSize = sizeof(SP_DEVINFO_DATA); if (!SetupDiCreateDeviceInfo(DeviceInfoSet, ClassName, &ClassGUID, NULL, 0, DICD_GENERATE_ID , &DeviceInfoData)) { return -1; } // // Add the HardwareID to the Device's HardwareID property. // if(!SetupDiSetDeviceRegistryProperty(DeviceInfoSet, &DeviceInfoData, SPDRP_HARDWAREID, (LPBYTE)hardid, (lstrlen(hardid)+1+1)*sizeof(TCHAR))) { ShowMessage((SetLastError(GetLastError()))); } Tag: Rendering Plugin's EnablePDEV Tag: 34292
  - 3
    - bitmap printer driver and anti aliased fonts? Hi, I wrote a small gpd file to that only outputs raw RGB data to a file. Reading the written data as a raw RGB data with an image manipulation program gives me a correct image of the rendered document. Except the rendering of fonts is very ugly. Is there any possibility to tell unidrv to perform font anti aliasing for me? Thanks Dirk Tag: Rendering Plugin's EnablePDEV Tag: 34290
  - 4
    - pop3 protocol traffic interception / hook Hello masters! I am sorry, if my question is trivial... I can`t find appropriate info in MSDN, DDK and SDK... Does anyone know how to intercept(hook) pop3 protocol traffic? I intend to develop my own universal spam filter, so i need exactly POP3. Is there driver need or winsock is enough? I curious - what personal firewalls use? Please suggest me technique, forum, keywords, url, sample, faq, tutorial, advice.. write me flashinc (commercial at) mail dot ru p.s. win32, visual c++ Tag: Rendering Plugin's EnablePDEV Tag: 34287
  - 5
    - compiling ipdetect sample hi all i am trying to compile ipdetect sample and facing problems. in some previous posting regarding "compilation of ipdetect" , it has been told that "using compiler that comes with new "Windows DDK" and using "Windows ME Build Environment" it is possible to create 16bit ipdetect.exe. But when i try the same configuration, it is asking for c1xx3216.exe which is not present in ddk bin dirs. We don't have MSVC1.52c .. i dont know where to find this file. can anybody help Thanks in advance jyotsna Tag: Rendering Plugin's EnablePDEV Tag: 34286
  - 6
    - sample plotter driver has anybody here ever developed a plotter driver? i'm also developing a plotter driver for a plotter that we're building so i would like to get a basic look at what a plotter driver requires from the os. any suggestions would be very welcome, and also i have the 98 ddk so i'm developing this driver for windows 98. Tag: Rendering Plugin's EnablePDEV Tag: 34284
  - 7
    - pci board driver I am trying to make a driver for a custom pci board. I was wondering if u guys could point me in the right direction (docs, examples, hints) PS: I never used DDK. -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ Tag: Rendering Plugin's EnablePDEV Tag: 34278
  - 8
    - ksproxy INF File Basic Question I have been studying the INF file associated with one of the usbcamd2 examples (the USBINTEL.INF) and creating a commented version such that I can grasp all the details. One bit that is not quite clear yet involves the interfaces. Living as I do in the past and being most comfortable with device objects/symbolic links rather than device interfaces, it took me a while realize what the [.Interfaces] section was actually doing. Now that I realize that AddInterface registers the interface(s) supported by the KM driver (as opposed to, for example a COM interface which gets registered in other ways), I am a bit unclear on what is happening in the subsequent AddReg section. The relevant parts of the INF file are: [Intel.USBDCam.Interfaces] AddInterface=%KSCATEGORY_CAPTURE%,GLOBAL,Intel.USBDCam.Interface AddInterface=%KSCATEGORY_VIDEO%,GLOBAL,Intel.USBDCam.Interface [Intel.USBDCam.Interface] AddReg=Intel.USBDCam.Intf.AddReg [Intel.USBDCam.Intf.AddReg] HKR,,CLSID,,%ProxyVCap.CLSID% HKR,,FriendlyName,,%USB\VID_05D0&PID_FFF4.DeviceDesc% HKR,PageAliases,"{71F96464-78F3-11d0-A18C-00A0C9118956}",1,21,E8,C2,3D, 13,47, d2,11, 0xba, 0x41, 0x0, 0xa0, 0xc9, 0xd, 0x2b, 0x5 HKR,PinFactory\1\Interfaces\{5BB95400-52BB-11d2-BA41-00A0C90D2B05},,, Now for the questions: 1) A question about interfaces. It is now my understanding that, in general, the registry entries specified in [Intel.USBDCam.Intf.AddReg] only have meaning in the context of the interface, for example KSCATEGORY_CAPTURE. In the context of some other interface, for example MY_CUSTOM_INTERFACE, there could be some completely different set of registry settings that could be used as needed. Thus, the fact that KSCATEGORY_CAPTURE and KSCATEGORY_VIDEO can be registered with the same AddReg section indicates that the implementors of those two interfaces chose to require the same registry settings. It does not indicate anything profound about interfaces in general. Is this correct? 2) Regardless of the answer to 1, what is the meaning of the listed entries? CLSID seems to be set to a GUID defined in ksproxy.h for what reason, I do not know. Perhaps to permit multiple implementations of ksproxying? I would have thought this was known by the KSCATEGORY_CAPTURE GUID. FriendlyName is clear. PageAliases is completely unclear. I cannot find any mention of it via google or the directx docs. This appears to be the only inf file it exists in. PinFactory is equally opaque. It exists in several inf files, but with different GUIDs. Is this something I need to understand or can I just close my eyes and "la, la, la....". Regards, Tom Udale PS one last slightly random question. Does an AddReg section always "Device Parameters" subtree or is it specific to the top level inf section? Tag: Rendering Plugin's EnablePDEV Tag: 34274
  - 9
    - Vendor and Product info from a PCI device Hi - I am trying to get vendor and product information from installed pci devices on Win9x up to WinXP. I am successful using the SetupAPI functions on XP and 2000, however, I am kind of stumped on how to go about doing this for Win9x. My first thoughts where to find some type of IOCTL_ command using DeviceIoControl, but not sure which IOCTL_ command or which device paramater handle to pass in to DeviceIoControl.. Can anyone point me in the right direction? Any help is appreciated. Thanks, Bert Tag: Rendering Plugin's EnablePDEV Tag: 34261
  - 10
    - How to make WPA error indication? Not sure if anyone wants to tackle this one, but here goes: In my 802.11 driver I simulate two MIC failures within 30 seconds - to test "countermeasure" feature of WPA. After 2nd failure I make indication of NDIS_802_11_AUTHENTICATION_REQUEST , with Flags = NDIS_802_11_AUTH_REQUEST_PAIRWISE_ERROR. The Funk Odissey client understands this indication, sends EAPOL pairwise error packet, the AP receives it, etc - all as expected. But WZC (update 815485) just ignores my indication. Can anybody tell why? Debug trace of WZC could be of great help here - but Microsoft still won't give out checked build of wscsvc... ----------- code snippet --------------- ... Called at dispatch irql, from some DPC... VOID ReportWpaErr( NDIS_HANDLE mphandle, UINT32 flags, PVOID bssid ) { struct { // Note: I made the following struct from verbal description in MS document. // It is not exactly defined in .h. NDIS_802_11_STATUS_TYPE indtype; NDIS_802_11_AUTHENTICATION_REQUEST ar; } myIndicationData; NdisZeroMemory( &myIndicationData, sizeof(myIndicationData) ); myIndicationData.indtype = Ndis802_11StatusType_Authentication; myIndicationData.ar.Flags = flags; // = NDIS_802_11_AUTH_REQUEST_PAIRWISE_ERROR (0x06) myIndicationData.ar.Length = sizeof(NDIS_802_11_AUTHENTICATION_REQUEST); memcpy( &myIndicationData.ar.Bssid, pdata, sizeof(NDIS_802_11_MAC_ADDRESS) ); NdisMIndicateStatus( mpHandle, NDIS_STATUS_MEDIA_SPECIFIC_INDICATION, &myIndicationData, sizeof(myIndicationData) ); NdisMIndicateStatusComplete( mpHandle ); } --------- end ----------------- Any help will be greatly appreciated. Thanks in advance. -- Pavel Tag: Rendering Plugin's EnablePDEV Tag: 34259
  - 11
    - negotiate paper sizes with printer driver? Hi, for a bitmap printer driver I would like to adjust the paper size to the printed area. Consider e.g. a image drawing program (MsPaint) that wants to print a 600x600 pixel image into a printer driver with 600dpi. Is there a possibility to negotiate a custom paper size of 1x1 inch? As a second example, take the acrobat reader, who has the information about the used paper coded into the pdf. There is an option in the Advanced dialog "Choose Output Tray by PDF paper size". Do I have to support all known paper types, or is there a possibility to negotiate the desired paper size with the application prior to printing? thanks in advance Dirk Tag: Rendering Plugin's EnablePDEV Tag: 34255
  - 12
    - Bitmap Printer Driver (reference implementation)? Hi, I'm in the need to write a printer driver that can write a bitmap file on a W2K od XP system. I searched this newsgroup and found that a few other people where in the same situation. The proposed method seems to build upon the oemuni sample and to hook into the FilterGraphics method. Before I start coding such a driver on my one, I would like to ask, wether there is a reference implementation of such a driver, or wether anybody can provide his source code to the community? BTW.: There is a GPLed print driver in SourceForge called PrintMirror, that writes to a bitmap and EMF file. This is a custom printer driver and not based on the unidrv architecture. Thanks in advance. Dirk Tag: Rendering Plugin's EnablePDEV Tag: 34254
  - 13
    - HID Minidriver for Media Center PC remote Hi, I am trying to develop an HID Minidriver that interfaces to a Media Center PC remote control using the Consumer IR block inside a Super I/O device. This device is on the LPC bus, but the DDK says it's ok to have HID Mindrivers on buses other than USB. In any case, the sample drivers are very helpful, especially the new virtual HID Minidriver in the Windows 2003 DDK. (kudos to Kumar Rajeev & Eliyas Yakub). However, I got stuck when I tried to write a HID_REPORT_DESCRIPTOR for the remote. I studied this Microsoft document: Using the Remote Control Device with Windows http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwmt/html/remote_control.asp I also read the entire DDK section on Interactive Input Devices a few times. And I read most of the USB Device Class Definition for Human Interface Devices (HID) Ver 1.1 along with the USB HID Usage Tables Ver 1.11. I am still confused about how to write a report descriptor that meets the requirements specified in the Microsoft document about "Using the Remote Control Device with Windows". Usage page and ID's are provided for mapping the WM_INPUT messages but the document does not explain what usage page and ID's should be used for the APPCOMMAND_ and VK_ buttons. Would it be just Keyboard? (usage page 0x01 usage ID 0x06). Would Microsoft Media Player see these buttons? Is it correct to map the entire remote using a single report descriptor? Is there some kind of fatal flaw in my approach? Given the limited scope of the Media Center PC remote, would it be possible for Microsoft to publish the report descriptor that meets the requirements of the remote? Thanks in advance for your help. Tag: Rendering Plugin's EnablePDEV Tag: 34250
  - 14
    - Non deterministic register access in HwFindAdapter Now that I'm on the right path with my video miniport driver, Im having some difficulties with the PC-Card. First off, when I wrote a standard miniport I was able to successfully retrieve resources and map them and then turn on the video display. This worked 100% of the time. But that was not the correct method for dealing with a display. So i rewrote it using only the VideoPort functions. I do get the cards resources, just a small register range, and am able to map them. But when I go to enable the card (tried in both HwFindAdapter and HwInitialize) and the device turns on, maybe 5%-10% of the time. I can't explain this. All I'm doing is writting a simple value to one of the mapped registers. And let me point out that under the other method I was getting 100% success so I do not think it is anything dealing with the PC-Card. Any help you can give would be appreciated. -- Brian V. Minier Interactive Imaging Systems, Inc www.iisvr.com Tag: Rendering Plugin's EnablePDEV Tag: 34247
  - 15
    - Sending MMC 4 commands All, I want to send MMC 4 commands to a DVD burner (Plextor 708A, supports +R/RW and -R/RW) for data storage purposes. I've downloaded the DDK and gone through MSDN and a couple of driver development books over the past few days, I nothing has jumped out at me as a way to send the commands. Now, is there some generic SDK class that will allow me to talk to the ATAPI or some other I/O driver to send the commands, or do I have to write a filter driver (or something similar) as a DLL for my application to talk to, or do I have to write a driver specifically for the burner? All helpful suggestions are appreciated. Thanks. Tag: Rendering Plugin's EnablePDEV Tag: 34246
  - 16
    - Signed Drivers for DOS? hi everyone, I'm looking for MS signed drivers for my NIC. are there such drivers? I already have the 'vendor' published drivers, but I'm looking for signed ones from MS, if any. regards, Ali Tag: Rendering Plugin's EnablePDEV Tag: 34245
  - 17
    - Re: Help "Suchrithaa Rajkumar" <suchritharajkumar02@hotmail.com> wrote in message news:... > Hello > > I am developing a test hook display driver that intercepts DDI calls. > During my testing on Windows 2K machine, I have found that it BSOD with > PCAnywhere 10.x display hook driver. As I could not able to find out the > root cause, and to avoid the BSOD, I have decided not to load my hook > display driver during my driver's initialization sequence. > > Following is the code snippet I have written for this purpose: > > DrvEnableDriver() > { > 1) Detect PCAnywhere Installation from registry > 2) If PcAnywhere driver name is from from 1) then return FALSE > 3) Otherwise proceed with my logic..... > } > > After doing this I am not getting BSOD but the machine boots in 16 colors > mode. Could anyone please help me to get rid of this problem? > > Thanks > Suchrithaa > > Tag: Rendering Plugin's EnablePDEV Tag: 34242
  - 18
    - problem: a pci device with no memory IO or port IO addresses?? hi, I am a newbie in device driver development area and also don't have detailed knowledge on pci device internals, design specs etc. in addition, let me tell you that I am not looking for a way to write a device driver (at least for now :) but, I am confused with the my system's pci device configuration and cannot explain this sitution. please find the deails below: the hardware of concern is a PIII module with the popular Intel PIIX4E chipset (82371AB/EB) and running Windows XP as the OS. first let me emphasize that PIIX4E is a multi-function pci device and those are: 1. PCI-ISA bridge 2. IDE Controller 3. USB Controller 4. Power Management Function when I look inside the 'device list' window, all functions BUT the power management function are listed. this was the first confusion point for me. after that, I had tried some utilities, apps (like pci sniffer, windriver) hoping to list all details of my enumerated pci devices. the result was still amazing to me. With all of such utilites I was able to see all the functions of my pci devices including the power management part, but this time I had realized that even though some of the devices are listed with a corresponding memory IO and/or port IO resources, some -like power management device- do not contain any memory IO or port IO resources. my question is -simply- how can this (a pci device with no memory or port IO sapce) be? is this something meaningfull, or am I missing something with pci technology. for instance, is it possible that the system knows this device as a "bridge" (I don't know between what)? from another point of view, when I want to read/write a single register of power management function, which addresses should I use? I think I have to write a device driver to run on XP but which IO should this driver access? I am really stuck due to this problem. your help is really appreciated, thanks in advance. serkan Tag: Rendering Plugin's EnablePDEV Tag: 34241
  - 19
    - Help Hello I am developing a test hook display driver that intercepts DDI calls. During my testing on Windows 2K machine, I have found that it BSOD with PCAnywhere 10.x display hook driver. As I could not able to find out the root cause, and to avoid the BSOD, I have decided not to load my hook display driver during my driver's initialization sequence. Following is the code snippet I have written for this purpose: DrvEnableDriver() { 1) Detect PCAnywhere Installation from registry 2) If PcAnywhere driver name is from from 1) then return FALSE 3) Otherwise proceed with my logic..... } After doing this I am not getting BSOD but the machine boots in 16 colors mode. Could anyone please help me to get rid of this problem? Thanks Suchrithaa Tag: Rendering Plugin's EnablePDEV Tag: 34235
  - 20
    - WLAN protocol capture driver suggestion needed i happened to see some commertial products for wireless lan monitoring like Airopeek, Airmagnet etc.and there is one open source ethereal using winpcap as packet capturing engine. just curious are those commertial products using the same kind of mechanism for packet capturing as winpcap uses. i happened to see a post at a group mentioning that those commertial products are some other driver concept. below is the excerpt from that mail i saw. >>They work around the driver and no-monitor-mode-through-NDIS >>problem by writing their own drivers. Thus, they have to choose which >>cards to support. looking forward to her from you experts. regards, Puneet Tag: Rendering Plugin's EnablePDEV Tag: 34231
  - 21
    - driver doesn't get installed I have to write an USB filter driver. I've made an INF file and setup exe for it, the problem is that I can't start the service after installing it. The INF file is as follows: [Version] Signature="$WINDOWS NT$" Class=USB ClassGUID={36FC9E60-C465-11CF-8056-444553540000} provider=%MSFT% DriverVer=08/05/1999 CatalogFile=dummy.cat [SourceDisksNames] 1="usbfilter Installation Disk",,, [SourceDisksFiles] USBFILTER.sys = 1 USBFILTER.inf = 1 [Manufacturer] %MfgName%=Microsoft [Microsoft] %USB\VID_045E&PID_930A.DeviceDesc%=USBFILTER.Dev, USB\VID_045E&PID_930A ;[PreCopySection] ;HKR,,NoSetupUI,,1 [DestinationDirs] USBFILTER.Files.Ext = 10,System32\Drivers USBFILTER.Files.Inf = 10,INF [USBFILTER.Dev] CopyFiles=USBFILTER.Files.Ext ;, USBFILTER.Files.Inf AddReg=USBFILTER.AddReg COPYINF=USBFILTER.Inf [USBFILTER.Dev.Services] Addservice = USBFILTER2,,USBFILTER.AddService [USBFILTER.AddService] DisplayName = %USBFILTER.SvcDesc% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %10%\System32\Drivers\USBFILTER.sys LoadOrderGroup = Base HKLM,"System\Currentcontrolset\Services\Usbfilter\Parameter s","MaximumTransferSize",0x10001,4096 HKLM,"System\Currentcontrolset\Services\Usbfilter\Parameter s","DebugLevel",0x10001,2 HKLM,"System\Currentcontrolset\services\Usbfilter\Parameter s","UsbfilterEnable",0x10001,1 [USBFILTER.AddReg] ;HKR,,DevLoader,,*ntkern ;HKR,,NTMPDriver,,USBFILTER.sys [USBFILTER.Files.Ext] USBFILTER.sys ;[USBFILTER.Files.Inf] ;USBFILTER.Inf [DefaultInstall] CopyFiles=USBFILTER.Files.Ext ;, USBFILTER.Files.Inf AddReg=USBFILTER.AddReg COPYINF=USBFILTER.Inf [DefaultInstall.AddService] DisplayName = %USBFILTER.SvcDesc% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %10%\System32\Drivers\USBFILTER.sys ;---------------------------------------------------------- -----; [Strings] MSFT="Deutsche Bundesbank" MfgName="Intel" USB\VID_045E&PID_930A.DeviceDesc="USBFILTER.Sys" USBFILTER.SvcDesc="USBFILTER.Sys" Tag: Rendering Plugin's EnablePDEV Tag: 34225
  - 22
    - Plotter driver - UI plugin Hi, Is it possible to implement a UI plug-in or rendering plug-in for a plotter driver for HPGL based plotters? Regards, Janardhanan.R. Tag: Rendering Plugin's EnablePDEV Tag: 34223
  - 23
    - UI customization of Unidrv UI Hi, I'm developing a Unidrv mini driver. Is it possible to completely remove the UI provided GPD and use my own design of UI by using a UI plug-in? i.e I want to remove 'Layout', 'Paper/Quality' pages and use my own property sheets. Thanks, Kiran Tag: Rendering Plugin's EnablePDEV Tag: 34218
  - 24
    - help for capture device Hi, In my quest to understand and to be able to build a non-wdm capture driver, I have some question. I want to get the big picture... I think it goes like this: * UserDriver/App - create a buffer large enough to hold one frame 1. calls read (wich is direct io in driver) - waits for read to complete * Driver - gets the read IRP and the MDL describing the memory from the I/O manager - use dma (scatter gather maybe) to fill this memory - completes request * UserDriver/App - uses buffer to draw frame - go to 1 Is this right or am I missing something ? The I/O manager builds an MDL, but does it lock these pages ? Another thing is since a keep using the same buffer, it recreates the same MDL each time, doesn't this cause an overhead ? And can I get an DmaAdapter for a non-WDM driver ? It seems that IoGetDmaAdapter needs the PDO, I don't have that, can I get it ? Is there another way for non-wdm drivers ? Thanks greetings Tag: Rendering Plugin's EnablePDEV Tag: 34213
  - 25
    - mirror display driver from ddk for win9x ? hi, is there a mirror display driver sample equivalent for windows 95/98/ME ? Tag: Rendering Plugin's EnablePDEV Tag: 34211

Hello,

I am currently developing a common rendering plugin for 5 serial
printers, In EnablePDEV() I tried using the pPrinterName parameter to
differentiate between my 5 printers so that I can insert customized
code for each printer model. My problem is, when I set the port to
FILE: It seems that the value of pPrinterName is always the default
printer(not the currently selected printer), It works fine when set to
other ports like LPT1.

Is this a specification?
Or maybe I'M doing it all wrong, Can anybody tell me how to get the
currently selected printer during or before EnablePDEV timing.

Thanks in advance
-andrew

Top

Re: Rendering Plugin's EnablePDEV by Serguei

Serguei
Sun Oct 26 09:55:08 CST 2003

> Or maybe I'M doing it all wrong, Can anybody tell me how to get the
> currently selected printer during or before EnablePDEV timing.

Use interface provided to you in PublishDriverInterface and read content of
.gpd file associated with each printer. This, of course, implies that each
printer has some common feature in their .gpd file (hide it from UI as well)
and each of them has distinct default option. Alternatively you can use OEM
data section in .gpd.

Top

Re: Rendering Plugin's EnablePDEV by Andrew

Andrew
Mon Oct 27 19:47:45 CST 2003

Thanks for the reply. I'll look into that option-using the
PublishDriverInterface. It seems that the pPrinterName in
the EnablePdev is not being refreshed so currently what I
did was to getteh Handle to the printer from pdevobj and
from there on, retrieved a PRINTER_INFO structure to get
the driver name. It seems to work fine, still have to do
some testing though.

>-----Original Message-----
>> Or maybe I'M doing it all wrong, Can anybody tell me
how to get the
>> currently selected printer during or before EnablePDEV
timing.
>
>Use interface provided to you in PublishDriverInterface
and read content of
>..gpd file associated with each printer. This, of course,
implies that each
>printer has some common feature in their .gpd file (hide
it from UI as well)
>and each of them has distinct default option.
Alternatively you can use OEM
>data section in .gpd.
>
>
>.
>

Top