device driver

    Sponsored Links


  • 1. Create asynchronic IRP
    As a result from IoDeviceControl from an application i want to create a new asynchronic IRP using IoAllocateIrp. The input buffer for the new IRP is the same buffer got from the application. newIrp = IoAllocateIrp(DeviceObject->StackSize, FALSE); if(NULL != newIrp ) { NextStack = IoGetNextIrpStackLocation(Irp); NextStack->MajorFunction = IRP_MJ_INTERNAL_DEVICE_CONTROL; NextStack->Parameters.DeviceIoControl.IoControlCode = IOCTL_INTERNAL_I8042_KEYBOARD_WRITE_BUFFER; buf = Irp->AssociatedIrp.SystemBuffer; BufLen = stack->Parameters.DeviceIoControl.InputBufferLength; NextStack->Parameters.DeviceIoControl.Type3InputBuffer = ExAllocatePool(NonPagedPool,BufLen ); RtlCopyMemory( NextStack->Parameters.DeviceIoControl.Type3InputBuffer, Irp->AssociatedIrp.SystemBuffer, BufferLength); ..... } Got blue screen with error 0xCC PAGE_FAULT_IN_NONPAGED_AREA Invalid system memory has been referenced. can you tell me where i get wrong?
  • 2. Windows XP x64 crashdump problem
    I have a SCSI HBA serving as the boot controller in a dual processor hyper-threaded system running WinXP x64 edition. Upon generating a crash via Crash-On-Ctrl-Scroll or the HCT crashdumptest, I have seen proof via WinDbg that the runtime (miniport) driver is still running when the crashdump driver is being loaded. Specifically, I have seen an interrupt generated during crashdump initialization get serviced by the runtime driver. I have also seen the one second timer I have continue to run on the runtime driver. No need to explain what a driver collision like this can do to the hardware. If I disable hyper-threading and one of the processors, the problem goes away. Why isn't crashdump processing disabling the other processors? Thanks Scott
  • 3. hook to DrvGradientFill does not work in my Customed 2k/XP printer driver
    Hello, Every one: I need some help on my current project. According to MSDN's document, graphic drivers can optionally support DrvGradientFill() by setting HOOK_GRADIENTFILL flag when it calls EngAssociateSurface or EngModifySurface. we have a costomed printer driver using a GDI managed surface with standard bitmap format. I was trying to recognize a graphic (vector) object (filled with a Gradient color) by intercepting DrvGradientFill(). Somehow, if I hook up DrvGtadientFIll() in printer driver, and trying to print a Gradient object from MS WORD 2003, GDI just calls DrvFillPath() and DrvStretchblt(), never calls DrvGradientFill(), Any body give me a hint? Thanks in advance, Xiao
  • 4. Display "New hardware" wizard on an orphanded device programmatically
    We have situations where the user selects "cancel" on the new hardware wizard dialogs before the driver is completely installed (apparently they get confused or something.) The driver files have been pre-installed using SetupCopyOEMInf. This is a USB device and if they unplug and re-plug the device in the wizard comes up again and works fine (at least on XP where I'm testing.) Is there a way to do this from a program? I can detect the device on the bus and that it wasn't setup correctly. Now I want to "reinstall" the device to set it up correctly. If I right click in the device manager it displays the new hardware wizard. I want to do this from my application, just cause the new hard found dialog to appear and again and do its normal thing. Any way to do this? Thanx!


Postby RossettoeCioccolato » Thu, 02 Aug 2007 05:52:13 GMT

On what platforms is CmResourceTypeMemoryLarge implemented (kernel or user 
mode)?  I see it in a comment in cfgmgr32.h but I can't find it in the DDK.



Re: CmResourceTypeMemoryLarge

Postby RossettoeCioccolato » Sat, 04 Aug 2007 22:34:12 GMT

Why is there no response?  Is this not a managed newsgroup?

Return to device driver


Who is online

Users browsing this forum: No registered users and 72 guest