"Legacy" NDIS 5.x IM Driver On 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
    - WDM (PnP) Driver - Installation problem Hallo! I have now managed to write an correct INF - File for installing wdm(pnp) - driver. First, I thought it is the best to write a dummy-driver for a hardwar device which exists, but doesn't do anything on the hardware. It shoul only load, save the given Info from the PnP Manager and keep them unti the driver is unloaded. So I wrote these functions, compiled and linked successfully. Then tried to install the driver using the Hardware-Manager. But exactly here occurs the error: The HW-Manager copies the driver sys file and then the compute restarts. But it's not a normal restart. It's like pressing the rese button on the PC. My Idea is the following: When I handle all PnP stuff, the drive should be installed correctly. Could this be so, or is it possibl another error - Markus0 ----------------------------------------------------------------------- Posted via http://www.codecomments.co ----------------------------------------------------------------------- Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78323
  - 2
    - IOCTL_SCSI_PASS_THROUGH_DIRECT - WRITE BUFFER Problems Hi Everybody, I am still having trouble with the IOCTL_SCSI_PASS_THROUGH_DIRECT sending the WRITE BUFFER command (op code 0x3B) to an ATAPI device, similar to a CDROM. The command works fine in UDMA mode, but when I try to run in PIO mode, the data payload is not sent correctly. I just sends the CDB[] array. I'm using Win 2000 and XP professional. READ BUFFER works fine in all cases. Any suggestions for a fix, or where to look? Thanks in advance. Garet Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78311
  - 3
    - Serialization of ProtocolReceivePacket Hi, I am new to writing device drivers and in the process of developing a filter intermediate driver. I have 3 NIC on my system. If i am getting the data on all the 3 NICs, Will the Ndis serialze the protocolReceive or is it the IM developer responsibility?. My understanding is that:- The miniport does not send any new packet to upperlayer protocol unless the ProtocolReceive/ProtocolReceivePacket returns. Is it right? What about the multiprocessor Systems? Thanks in Advance. Gaurav Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78304
  - 4
    - on the fly encryption Hi, I am new to writing device drivers and in the process of developing an on the fly encryption program - somewhat similar to truecrypt / pgpdisk / crosscrypt using KMDF. Starting from the RamDisk sample I have supported the necessary IOCTL's to register it with the mount manager and to allow formattting as well as chkdsk. It has also been made into a single file system ala filedisk. Encryption routines which work in the kernel mode have also been implemented. However, on adding the cryptographic routines to the EvtIoRead/Write functions my virtual disk no longer works correctly - formatting is not completed. My psuedocode is as follows: Write Function - 1. Retrieve the buffer to read from. 2. Encrypt the data in it. 3. Write the file to disk using ZwWriteFile Read Function 1. Retrieve the buffer to write in. 2. Read the data from file using ZwReadFile 3. Decrypt the data By removing the encrypt/decrypt state the system works properly. Am I doing something conceptually wrong or is it an implementation flaw? Or is what I want to do possible only using file system filter drivers? I would prefer to avoid these if possible. Any suggestions and help would be welcome. Thanks. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78293
  - 5
    - How to get print spooler to release/close open device(Parallel0) To be able to query local attached printers for information, I need to force/convince the print spooler to release the ports (parport), which it has opened. As the spooler (or language monitor) needs to monitor the printer for unsolicited status messages, it makes sence that the spooler opens the port(s) and keeps it open. But, now, when another applications tries to open the port (\Device\Parallel0), access is denied. So how do I get the print spooler to release/close the device, so that I can use it? I know this is possible, as I can see Lexmark is doing this from their "lexbces.exe" service. I have used Portmon to monitor all requests sendt to the device, and always before "lexbces.exe" tries to open the device, the print spooler magically closes the device. I don't know if this is a undocumented feature provided by MS to help their chums at Lexmark ;), or if Lexmark uses some tricks and hacks to do this - but I also would realy like to know, how this magic works. Kind Regards, Christoph Lindemann Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78292
  - 6
    - weird errors when compiling bulkusb I have installed xp_sp1_ddk on my computer(my os is w2k sp4), and I'm trying to compile the ddk sample program "bulkusb" using the "W2K checked build environment". Unfortunately I got 621 errors, and all of them were syntax errors about "(", ")" and ";", to list some of them: ====================================================== bulkpwr.h(147) : error C2143: syntax error : missing ')' before 'identifier' bulkpwr.h(147) : error C2061: syntax error : identifier 'DeviceExtension' bulkpwr.h(147) : error C2059: syntax error : '' bulkpwr.h(148) : error C2059: syntax error : ')' bulkdev.h(67) : error C2146: syntax error : missing ')' before identifier 'Devic eExtension' ======================================================== However, when I built the program using "winxp checked build environment", I successfully got the right "bulkusb.sys" file. Since it is the sample program of ddk, it is not likely to have sytax errors, and I have rightly set the environment variable using "setenv D:\WINDDK\2600.1106 chk W2K", I have been so frustrated by the errors. What might be the problems? Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78285
  - 7
    - NdisAllocateBufferPool I m writing a Ndis miniport driver. I m allocating a buffer pool by calling NdisAllocateBufferPool. It returns status as NDIS_STATUS_SUCCESS, but the bufferpool handle is 0. I m able to allocate buffers from this bufferpool. why NdisAllocateBufferPool is returning bufferpool as 0. Thanks in advance. hiremath_vi Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78281
  - 8
    - Error of allocating non-paged pool ? Some times my driver cannot allocate 460Kbyte's non-paged pool . and the system's main memory was 256MByte. when I see the nonpagepool using WinDBG was following !vm .... NonPagedPool Usage : about 10MB .... NonPagedPool Max : about 100MB also I checked using (kd> dd mmmaximumnonpagedpoolinbytes l1 ) I could think the reason would be external external fragmentation, However the gap between usage and current is too large(almost 1/10) Anyone know, athe problem and the way to solve that problem. ? Thanks Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78271
  - 9
    - A device driver GOOD book ? Hi, Can you recomend some books that are treating virtual printer drivers especially ? Radu. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78259
  - 10
    - Silent Install Hi! I've written a driver that contains a "virtual bus" and a "virtual serial port". The bus allows installation, uninstallation and enumeration of virtual serial ports. Everything is contained within the same driver. When a new virtual serial port is installed, I want the installation to proceed without user intervention, except for accepting that an unsigned driver is being installed. However, as it is now, the user must locate the appropriate inf when the port is installed. This is not good. Can I make windows automatically find the inf-file? I've tried putting the inf pretty much everywhere (\windows, \windows\system32, \windows\system32\drivers) but it still isn't found. I set the hardware/device/compatible ID of the physical devices enumerated by the bus to "myBus\myDevice" and I have a corresponding field in the inf: [DeviceList] %DESCRIPTION%=DriverInstall,myBus\myDevice Thanks in advance, Nille Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78258
  - 11
    - Finding a magic in conventionnal memory Hi One of my driver (boot driver) is supposed to find a "magic" in conventional memory.This Magic as been set previously to the actual boot of Windows (even before the MBR has been loaded). I know that the Magic resides between 512KB and 640KB. The memory area in which this magic is located has previosuly been protected from writings (by using a modified Int 15/AX=E820h section) I am currently using MmMapIoSpace(PhysAddr, Size, MmNonCached); This works OK with the free build of Windows XP (sp2, 32bits) but with the checked build (sp2 32bits) I have an error. I am not currently on the computer that runs the debugger so I cannot currently be more precise, but I hope that the experts in this group will have an answer to my question (and if I need to give more detailsn I will have to be very cautious because we have strong non disclosure agreements with the customer). I know that one other developer that worked on this driver had to tune the Memory Mapping functions in order for Driver Verifier to accept the way we do the mapping. He is the one that decided to use MmMapIoSpace. The customer that we develop the driver for is requiring that it to be able to run on the checked build of Windows XP and that it can pass Driver Verifier on the free build. So here is my question: What is the "correct" way to map some "low" memory in order to find a magic and read the memory that is located after this magic? The "correct" way in this context means a way that is acceptable to checked buold and driver verifier Thanks in advance Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78257
  - 12
    - USB Clarification I've read everything I could find under "USB language monitor" in this newgroup.. I've also read the XP DDK. I will first describe what I want to do, and then place my thoughts on what I've gathered here in the newgroup. I would greatly appreciate any clarifications or corrections to this information: I want my language monitor to work on both USB and LPT printers without modication. I've noticed others have wanted to, but I have slightly differing symptoms. (1) in one case, my monitor is called and opens USB001, but never gets a reply on xxxReadPort(...); (2) I'm listed as a monitor for a USB printer, but it never initializes the monitor. What I've learned: USBMON.DLL is the * PORT * monitor for USB printers. LOCALMON.DLL is the * LPT * monitor for LPT printers. In order to install oneself as a language monitor there are two registry keys (with some values) that need to be modified: (1) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3\<Printer Name>\Monitor This value must be set to the KEY name under the following registry tree: (2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors For instance, to install myMonitor.dll, I would create a key under (2) called "MyMonitor". The value in this key is "Driver" and its data value is "myMonitor.dll". Next I choose a printer from (1) and change the "Monitor" value to contain this data, "MyMonitor". ------------------------------------- InitializePrintMonitor is deprecated in favour of the new InitializePrintMonitor2 (and newer methods). From what I've read, it doesn't matter which you use, as long as you write it correctly. There is no special requirement for using the newer xxxMonitor2 functions for USB language monitors. ------------------------------------ >From the DDK, the reference to a driver only using the ReadPort, WritePort, and IOCTL_PAR_QUERY_DEVICE_ID interfaces is in relation to an actual printer driver, NOT for the language monitor that sits between. ---------------------------------- The design of the spooler architecture, specifically language monitors, does not care about the port monitor involved. Thus I write a properly spec'd language monitor and it doesn't give a hoot about which port monitor is in place. ---------------------------------- LOCALMON.DLL implements GetPrinterDataFromPort USBMON.DLL implements GetPrinterDataFromPort ---------------------------------- As an example (which should work) -- ASSUMPTIONS: There are no other print jobs pending, conflicting, or currently printing. The user calls win32 API GetPrinterData on a USB connected printer. The language monitor gets called which in turn calls xxxWritePort to request the data. A moment later (or via another means) calls xxxReadPort(...) to obtain the response. All is well. ---------------------------------- Have I got all this information correct? If you reply and have additional information that is more correct, or explains things more thoroughtly than the DDK, please provide a link. Ciao RDB Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78251
  - 13
    - Getting an 0x000000A3 stop code during HCT 12.1 driver verificatio I am writing a device driver for a hardware device which is running on a system which has Windows XP tablet edition. There is ACPI (ASL) code embedded into the system BIOS ROM and a device driver that registers a callback by doing the following: status = devExt->AcpiInterface.RegisterForDeviceNotifications( devExt->LowerDevObj, EventHandlerFunction, devExt ); The device driver appears to be behaving properly during normal operations, but when I am running through the driver verifier tests, I get a blue screen with the following stop code when the test first reboots the machine: ACPI_DRIVER_INTERNAL 0x000000A3 ( 0x00000002, 0x00090147, 0x86CE6488, 0x86CE6540 ) Where can I find the documentation for that stop code? Specifically, what would cause it, and possibly what the parameters mean. I have looked at a couple of DDKs in order to try and determine what the parameters mean to no avail, I've searched the newsgroups for the meaning of the A3, I've googled for it, I visited most of the WHDC site. Can anyone help me find this documentation? Thanks, M. Lopez Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78249
  - 14
    - WDF WMI problem Hi, I have created a WMI instance using WdfWmiInstanceCreate and 'Register' is set TRUE in the instanceConfig. When i use the WMICodeCreator tool to browse the WMI namespace, i can't see my class. My code is based on the FireFly example. Should this tool show my new class? Where else can i view WMI classes? Where do i look to debug this? Thanks Laurence Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78247
  - 15
    - UNIDRV Grayscale Vector vs. DIB Conversion UNIDRV is doing differnt GrayScale conversions for Vector and Bitmap Objects. In grayscale printmodes, GDI renders these differently Vector objects use Gray = (R+G+B)/3 Bitmap objects use ? Likely an NTSC luminance weighting, i.e., Gray = 0.3 * R + 0.59 * G + 0.11 * B How Do I get UNIDRV to do a GrayScale conversion Like NTSC luminance weighting for all objects? Here the current GPD Settings for ColorMode: *%==================================================================== *% ColorMode Feature *%==================================================================== *Feature: ColorMode { *rcNameID: =COLOR_PRINTING_MODE_DISPLAY *DefaultOption: Color24 *Option: Mono1 { *rcNameID: =IDC_MONO_RADIO *DevNumOfPlanes: 0 *DevBPP: 0 *DrvBPP: 8 *RasterMode: DIRECT *IPCallbackID: 1 *Color? : FALSE *Command: CmdSendBlockData { *Cmd: "" } *Command: CmdSelect { *Order: DOC_SETUP.10 *Cmd: ="" } } *Option: Color24 { *rcNameID: =IDC_COLOR_RADIO *DevNumOfPlanes: 0 *DevBPP: 0 *DrvBPP: 24 *RasterMode: DIRECT *IPCallbackID: 2 *Color? : TRUE *Command: CmdSendBlockData { *Cmd: "" } *Command: CmdSelect { *Order: DOC_SETUP.10 *Cmd: ="" } } } Thank you, Guy Light Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78246
  - 16
    - Word Text Squished Randomly to column 1. Word 2003 and Word SP1 or Word SP2... is squishing text randomly when printer is selected. Is this a Word bug that has yet to be fixed or is there something the printer driver needs to do in order to help out Word? How do I get Word to be well behaved when Printer is selected. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78244
  - 17
    - KMDF Notification Hi. I want my driver to notify a user mode thread when an event happens. For WDM, the preferred method (Oney) seemed to be creating a shared event and pass this to the driver with a DeviceIOControl. In the driver you would use ObReferenceObjectByHandle to get to the event. Is this still the preferred way under WDF? Is it better to create a DeviceIOControl that waits for the event (either directly or through an overlapped call)? Or is WMI and WdfWmiInstanceFireEvent the way to go? I have tried the DeviceIOControl call that waits for the event but that stops other DeviceIOControl calls getting to the driver. This is with SynchronisationScope set to None. Any advice appreciated. Thanks. Laurence. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78243
  - 18
    - RtlUnicodeStringToInteger is either mis documented or buggy Code: RtlInitUnicodeString(&str, buf); RtlUnicodeStringToInteger(&str, 16, &val1); WinDbg watch: str : struct _UNICODE_STRING "123" val1 : 0x123 I dont know about anyone else but I was expecting 0x7B. Ie, that it works the same as atoi. Anyone got any views on this? Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78242
  - 19
    - Using compression from kernel mode... hi I am developing a kernel mode driver in which I need to compress/decompress huge amount of data.Now all the available compression libraries seem to contain the usage C run time libraries,making it very unsuitable for use in windows kernel mode. Is there any compression decompression library for windows kernel mode environment? Rgds Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78239
  - 20
    - Printer driver for Epson LQ-2070 This driver is included in Windows XP. Is it included in my Windows XP Home edition Version 2002 CD? If it is, how do I check that it has been loaded on my computer? If it is not, how do I obtain a copy?Epson does not make an Epson 2070 driver for XP. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78238
  - 21
    - How to produce the race condition by DDK.3790? There are so much dualcore/hyperthreading platforms. Does the DDK can build out the real multi-treading supported driver? I maintain the vga driver. In WinXP, the vga driver own 2 parts, miniport and display. I made 2 tests, the 1st can overlap display/miniport function; the other can't. I don't know why the 2nd test can't produce the race condition. case 1) This can make it. T1: The pc-cam call directdraw function repeatly. T2: The miniport interrupt function check this interrupt belong to repeatly? case 2) I confused this. T1: One AP fired IRP to the IRP handle of miniport function. It's fireing repeatly. T2: The dvd player use directdraw function play the video file. Why the case 2 can't produce the race condition?? Does the ddk3790 support multi-threading? Or I got the mistake. The display and miniport part never overlap, they are sequential except the isolation level is high. -william Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78236
  - 22
    - ZwCreateFile causes UNEXPECTED_KERNEL_MODE_TRAP when PC starts with Ndis WDM device inserted Hi all If I boot the PC with the Ndis WDM device inserted, I get the following BSOD when ZwCreateFile is called from MiniportInitialise. When the device is inserted after the PC has booted there is no problem. Here is the code. RtlInitUnicodeString(&ObjectName, L"\\SystemRoot\\system32\\drivers\\GTNDIS.cfg"); InitializeObjectAttributes(&ObjectAttributes, &ObjectName, OBJ_CASE_INSENSITIVE, NULL, NULL); Status = ZwCreateFile( &hfile, FILE_READ_DATA | SYNCHRONIZE | DELETE, &ObjectAttributes, &IoStatusBlock, NULL, FILE_ATTRIBUTE_NORMAL, 0, FILE_OPEN, FILE_DELETE_ON_CLOSE | FILE_SYNCHRONOUS_IO_NONALERT, NULL, 0); Here is the trace: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80042000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 28) eax=89d162b0 ebx=89d162b0 ecx=00000001 edx=00000000 esi=89cb2100 edi=bad01700 eip=ba626b0f esp=bad01000 ebp=bad01004 iopl=0 nv up ei pl zr na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 Ntfs!NtfsMcbLookupArrayIndex+0xc: ba626b0f 56 push esi Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from ba626a50 to ba626b0f STACK_TEXT: bad01004 ba626a50 89d162b0 00000006 00000000 Ntfs!NtfsMcbLookupArrayIndex+0xc bad01030 ba626bbb 89d162b0 00000006 00000000 Ntfs!NtfsLookupNtfsMcbEntry+0x23 bad0113c ba62707c bad01700 89d16218 00000006 Ntfs!NtfsLookupAllocation+0x5b bad0130c ba626cf6 bad01700 8ac64e70 89d16218 Ntfs!NtfsPrepareBuffers+0x270 bad014f4 ba62803b bad01700 8ac64e70 89d16218 Ntfs!NtfsNonCachedIo+0x20e bad016f0 ba627c97 bad01700 8ac64e70 0110070a Ntfs!NtfsCommonWrite+0x1824 bad01864 804eddf9 89cb2020 8ac64e70 806d02e8 Ntfs!NtfsFsdWrite+0xf3 bad01874 8064b5a8 8ac64e70 89d1a040 89d15530 nt!IopfCallDriver+0x31 bad01898 ba6ca3ca 89d15478 89d15400 bad018dc nt!IovCallDriver+0xa0 bad018a8 804eddf9 89d15478 8ac64e70 806d02e8 sr!SrWrite+0xaa bad018b8 8064b5a8 89cb0a28 00003000 89d15478 nt!IopfCallDriver+0x31 bad018dc 804ef0d5 e17af8f8 00001000 e1507658 nt!IovCallDriver+0xa0 bad018f0 ba647e86 89cb0a08 89da6428 bad01994 nt!IoSynchronousPageWrite+0xaf bad019bc ba647f50 e1507658 e17af8f8 e1507658 Ntfs!LfsFlushLfcb+0x429 bad019e0 ba64da1f e1507658 e17af8f8 e157a230 Ntfs!LfsFlushLbcb+0x81 bad01a08 ba646a8e e1507658 0993b51c 00000000 Ntfs!LfsFlushToLsnPriv+0xf3 bad01a48 ba658341 e157a230 0993b51c 00000000 Ntfs!LfsFlushToLsn+0x8e bad01a7c ba650110 899e7a98 e1650be0 e1650ca8 Ntfs!NtfsCommitCurrentTransaction+0x215 bad01a90 ba65169f 899e7a98 899e7a98 e1650ca8 Ntfs!NtfsCheckpointCurrentTransaction+0x21 bad01b64 ba650e2f 899e7a98 89b9e608 8abaee90 Ntfs!NtfsSetEndOfFileInfo+0x5ea bad01bd4 ba629ad8 899e7a98 8abaee90 89cb2020 Ntfs!NtfsCommonSetInformation+0x477 bad01c3c 804eddf9 89cb2020 8abaee90 806d02e8 Ntfs!NtfsFsdSetInformation+0xa3 bad01c4c 8064b5a8 8abaefd8 8abaeea0 8abaee90 nt!IopfCallDriver+0x31 bad01c70 8056f689 bad01d38 bad01dc4 8056f11a nt!IovCallDriver+0xa0 bad01d1c 8053c808 8000034c bad01e50 bad01e20 nt!NtSetInformationFile+0x56f bad01d1c 804fe405 8000034c bad01e50 bad01e20 nt!KiFastCallEntry+0xf8 bad01da8 ba6ce1e4 8000034c bad01e50 bad01e20 nt!ZwSetInformationFile+0x11 bad01e5c ba6ce502 80000310 89cb2020 e1760c08 sr!SrCopyStream+0x22e bad01fd8 ba6ce87b 89d15530 89c16f90 e1750754 sr!SrBackupFile+0x2b0 bad02040 ba6d05a9 89d15530 00010010 89c16f90 sr!SrBackupFileAndLog+0x4b bad02068 ba6d12c8 89d15530 00010010 89c16f90 sr!SrHandleFileChange+0x59 bad020b4 ba6cfa22 89d15530 00010010 89c16f90 sr!SrHandleEvent+0x194 bad02118 804eddf9 00000000 00000001 806d02e8 sr!SrCreate+0x2fc bad02128 8064b5a8 89e8ce80 89e8ce70 89c16f90 nt!IopfCallDriver+0x31 bad0214c 805773bc 89d128e8 89cc819c bad022f4 nt!IovCallDriver+0xa0 bad0222c 805b365e 89d12900 00000000 89cc80f8 nt!IopParseDevice+0xa58 bad022b4 805afb3f 00000000 bad022f4 00000040 nt!ObpLookupObjectName+0x56a bad02308 8056a133 00000000 00000000 d0245400 nt!ObOpenObjectByName+0xeb bad02384 8056aaaa bad03408 00110001 bad033e8 nt!IopCreateFile+0x407 bad023e0 8056d17c bad03408 00110001 bad033e8 nt!IoCreateFile+0x8e bad02420 8053c808 bad03408 00110001 bad033e8 nt!NtCreateFile+0x30 bad02420 804fd569 bad03408 00110001 bad033e8 nt!KiFastCallEntry+0xf8 bad024c4 a9d23c57 bad03408 00110001 bad033e8 nt!ZwCreateFile+0x11 bad0340c a9d24ffc 899b2000 899cfad0 ba5fad0c Gtm51Irp!ReadRegistryParamsFromFileFunc+0x61 [c:\work\driver\source\projects\cobra\gtndisirp\readparams.c @ 2392] bad035f0 a9d1e967 899b2000 bad038ec 00000000 Gtm51Irp!ParseRegistryParameters+0x1de [c:\work\driver\source\projects\cobra\gtndisirp\readparams.c @ 119] bad03710 ba603dea bad0374c bad03754 ba5ff200 Gtm51Irp!GPRSZCSInitialize+0x4c5 [c:\work\driver\source\projects\cobra\gtndisirp\main.c @ 493] bad038c8 ba6039cc 89b92950 bad038ec bad03994 NDIS!ndisMInitializeAdapter+0x3b7 bad0399c ba6038ba 89b92950 00000000 89cc3be8 NDIS!ndisInitializeAdapter+0xb9 bad039d0 ba604d99 899cf9d0 89b5e040 8ac5cd00 NDIS!ndisPnPStartDevice+0xd6 bad03a00 804eddf9 899cf9d0 8ac5cdb8 806d02e8 NDIS!ndisPnPDispatch+0x306 FOLLOWUP_IP: Gtm51Irp!ReadRegistryParamsFromFileFunc+61 [c:\work\driver\source\projects\cobra\gtndisirp\readparams.c @ 2392] a9d23c57 85c0 test eax,eax SYMBOL_STACK_INDEX: 2b FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: Gtm51Irp!ReadRegistryParamsFromFileFunc+61 MODULE_NAME: Gtm51Irp IMAGE_NAME: Gtm51Irp.sys DEBUG_FLR_IMAGE_TIMESTAMP: 443b655c STACK_COMMAND: .tss 28 ; kb FAILURE_BUCKET_ID: 0x7f_8_Gtm51Irp!ReadRegistryParamsFromFileFunc+61 BUCKET_ID: 0x7f_8_Gtm51Irp!ReadRegistryParamsFromFileFunc+61 Followup: MachineOwner --------- Is this expected? If so, is there a way of waiting untill the system is sufficiently up to support this call? Thanks in advence for any input on this. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78228
  - 23
    - USB controlling Hi, I want to disable/enable the USB ports. So, that no one can can access that device connected with that port. I tried the CreateFile method with no SHARE rights & read/write access ... but it was not useful. Again, i found usbioctl.h header file with WINDDK there we have a flag defines like IOCTL_INTERNAL_USB_ENABLE_PORT, IOCTL_USB_HCD_DISABLE_PORT and IOCTL_USB_HCD_ENABLE_PORT but i don't know how to use it. Can any one show me a light ?? Thanks in anticipation. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78226
  - 24
    - Interrupt handling in Vista Beta2 Hi All, I am developing NDIS6.0 network driver on Windows Vista Beta2. I get a crash as soon as my interrupt handler(DpcForIsr) is returned. On the other hand if in MPIsr, if i dont claim any interrupts i.e when interrupt handler(DpcForIsr) is not called at all, everything is fine. On Vista Beta1, this doesnt happen. Is anything newly added regarding interrupt management in Vista Beta2(5308 build). Thanks, Chiranjeevi. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78221
  - 25
    - How to support Motion JPEG format in driver ? Does intelcam.sys support Motion JPG format(ex:FCC_FORMAT_MJPG)? I can't find enough information in document. MJPG option is showed in Amcap but can not preview with MJPG format. KS_DATARANGE_VIDEO structure below Thanks for any help or hint. -SL ============================================================= KS_DATARANGE_VIDEO StreamFormat_VGA_MJPG = { // KSDATARANGE { sizeof (KS_DATARANGE_VIDEO), 0, // Flags D_X * D_Y * 2, // SampleSize 0, // Reserved // MEDIATYPE_Video STATIC_KSDATAFORMAT_TYPE_VIDEO, // MEDIASUBTYPE_MJPG, 0x47504A4D, 0x0000, 0x0010, 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71, STATIC_KSDATAFORMAT_SPECIFIER_VIDEOINFO }, TRUE, // BOOL, bFixedSizeSamples (all samples same size?) TRUE, // BOOL, bTemporalCompression (all I frames?) KS_VIDEOSTREAM_CAPTURE, // StreamDescriptionFlags 0, // MemoryAllocationFlags (KS_VIDEO_ALLOC_*) // _KS_VIDEO_STREAM_CONFIG_CAPS { STATIC_KSDATAFORMAT_SPECIFIER_VIDEOINFO, KS_AnalogVideo_None, // VideoStandard D_X, D_Y, // InputSize, (the inherent size of the incoming signal // with every digitized pixel unique) D_X, D_Y, // MinCroppingSize, smallest rcSrc cropping rect allowed D_X, D_Y, // MaxCroppingSize, largest rcSrc cropping rect allowed 1, // CropGranularityX, granularity of cropping size 1, // CropGranularityY 1, // CropAlignX, alignment of cropping rect 1, // CropAlignY; D_X, D_Y, // MinOutputSize, smallest bitmap stream can produce D_X, D_Y, // MaxOutputSize, largest bitmap stream can produce 1, // OutputGranularityX, granularity of output bitmap size 1, // OutputGranularityY; 0, // StretchTapsX 0, // StretchTapsY 0, // ShrinkTapsX 0, // ShrinkTapsY 333333, // MinFrameInterval, 100 nS units => 30 fps 2000000, // MaxFrameInterval, 100 nS units => 5 fps 16* 5 * D_X * D_Y, // MinBitsPerSecond; 16* 30 * D_X * D_Y // MaxBitsPerSecond; }, // KS_VIDEOINFOHEADER (default format) { 0,0,0,0, // RECT rcSource; 0,0,0,0, // RECT rcTarget; D_X * D_Y * 16 * 30, // DWORD dwBitRate; 0L, // DWORD dwBitErrorRate; 333333, // REFERENCE_TIME AvgTimePerFrame; sizeof (KS_BITMAPINFOHEADER), // DWORD biSize; D_X, // LONG biWidth; D_Y, // LONG biHeight; 1, // WORD biPlanes; 16, // WORD biBitCount; FCC_FORMAT_MJPG, // DWORD biCompression; D_X * D_Y * 2, // DWORD biSizeImage; 0, // LONG biXPelsPerMeter; 0, // LONG biYPelsPerMeter; 0, // DWORD biClrUsed; 0 // DWORD biClrImportant; } }; Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78216
- Next
  - 1
    - SmartCard Reader Driver Hi, I'm trying to modify the PSCR sample DDK to make a virtual PCSC driver. I removed all HW dependencies from PSCR. Now I see the Smart Card Resource Manager opening a handle to my driver, but one of the last IRPs gets cancelled due to an invalid code forwarded to SmartcardDeviceControl. I am receiving it from Resource Manager after QUERY_DEVICE_RELATIONS... Any ideea how to troubleshoot this? Is there a better place to ask Smart Card specific questions? For details please see the log bellow: SMCLIB!PscrCreateClose: Open PSCR!PscrPnPDeviceControl: Exit c00000bb PSCR!PscrPnPDeviceControl: Enter PSCR!PscrPnPDeviceControl: Default 7 PSCR!PscrPnPDeviceControl: Exit c00000bb SMCLIB!PscrDeviceIoControl: --------- 860aa448 SMCLIB!PscrDeviceIoControl: IRP - 860aa448 Major - 0x0 Minor - 0x0 SMCLIB!PscrDeviceIoControl: SmartcardDeviceControl - status : 0 SMCLIB!PscrDeviceIoControl: --------- 860aa448 SMCLIB!PscrDeviceIoControl: IRP - 860aa448 Major - 0x310008 Minor - 0x60150 SMCLIB!PscrDeviceIoControl: SmartcardDeviceControl - status : 0 SMCLIB!PscrDeviceIoControl: --------- 860aa448 SMCLIB!PscrDeviceIoControl: IRP - 860aa448 Major - 0x310008 Minor - 0x10100 SMCLIB!PscrDeviceIoControl: SmartcardDeviceControl - status : 0 SMCLIB!PscrDeviceIoControl: --------- 860aa448 SMCLIB!PscrDeviceIoControl: IRP - 860aa448 Major - 0x310008 Minor - 0x10101 SMCLIB!PscrDeviceIoControl: SmartcardDeviceControl - status : 0 PSCR!PscrPnPDeviceControl: Enter PSCR!PscrPnPDeviceControl: Default 7 PSCR!PscrPnPDeviceControl: Exit 0 SMCLIB!PscrDeviceIoControl: --------- 8645db28 SMCLIB!PscrDeviceIoControl: IRP - 8645db28 Major - 0x310008 Minor - 0x7fff0001 PSCR!CBCardTracking: Enter PSCR!CBCardTracking: Exit SMCLIB!PscrDeviceIoControl: SmartcardDeviceControl - status : 103 SMCLIB!PscrDeviceIoControl: --------- 863ece00 SMCLIB!PscrDeviceIoControl: IRP - 863ece00 Major - 0x310028 Minor - 0x7fff0001 SMCLIB!PscrDeviceIoControl: SmartcardDeviceControl - status : 0 PSCR!PscrCancel: Enter PSCR!PscrCancel: Completing wait for Irp = 8645db28 PSCR!PscrCancel: Exit SMCLIB!PscrCleanup: Enter SMCLIB!PscrCleanup: Completing IRP 863ece00 SMCLIB!PscrCleanup: Exit SMCLIB!PscrCreateClose: Close IRP 2 Many thanks in advance for any comment.... Mircea Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78209
  - 2
    - SDBUS.SYS on WinCE vs XPSP2 I'm having a little trouble with SDBUS.SYS on XP SP2. I have an SDIO device which works great on WINCE 5.0. However, when I use the same device on an Windows XP SP2 desktop, the device stops responding. I traced the SD bus and found that after SDBUS reads the CIS on function 0 and 1 and FBR on function 1, it then issues a CMD5, which hangs the device. Under CE, this CMD5 is missing and subsequently allows the device to continue operate. I have the feeling that the WINCE version of SDBUS is newer than the one on XP. Is there an update to the XP version of SDBUS.SYS which can help me avoid this problem? Thanks, ((&-> Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78204
  - 3
    - MiniRdr and NAMED_PIPE RDBSS call my CreateVNetRoot for NAMED_PIPE even if I do not support it, after returing STATUS_NOT_SUPPORTED it asks the same to LanmanRedirector. It happens playing a file with wmplayer. wmplayer start playing the file but the user interface start responding only after a lot of call to Lanman hav been returned... I need the RDBSS to ask me for NAMED_PIPE once thanks ale Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78203
  - 4
    - NdisOpenConfigurationEx fails on Windows Vista Beta2(5308 build) Hi Everyone, I am developing an NDIS6.0 network driver for Vista Beta2. I try to use NdisOpenConfigurationEx function to get a configuration handle that allows access to configuration parameters in the registry. I supply the NdisHandle parameter obtained in MPInitialize call back function. NdisOpenConfigurationEx fails with status code c000000d(STATUS_INVALID_PARAMETER). This works fine on Beta1. Could any one throw some light on it. Thanks in Advance. Chiranjeevi. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78199
  - 5
    - Filter driver on Tablet PC or Embedded XP I have a filter driver that sits above the UDF filesystem to interecept reads. The filter is part of a secure video product. Does anyone know if a filter driver will work on the Tablet PC and/or Embedded XP OSes? Everything reads like they will work on these platforms. How about Windows CE? Doesn't look like it will. Is there a similiar mechanism on windows CE or will I have to re-engineer to figure out how I can solve the problem? Thanks in advance! -- Still trying to build a perpetual motion machine Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78192
  - 6
    - Problem of receiving TCP packets on Virtual adapter Hi, I am porting IM driver on WM5.0. I have created a virtual miniport with lower metric value so that upper layer application bind with that VA. So all the packets (TCP/UDP) are coming to that VA with IP and MAC of that VA. The IM then spoof the IP and MAC and put the original miniport IP and MAC and send the packet to the original miniport(TNETWLN1). When original miniport receive the packet IM change the IP and MAC of original to the VA and indicate to the upper layer protocol. This works fine in case of UDP packets but TCP packets are not accepted by TCP/IP stack. I check the MAC, IP, Port and CheckSum of TCP packet after spoofing it back. I also checked the MP binding it is fine too. Here what can be the problem. Somebody has find this kind of problem ever. Any kind of help is appreciated. Thanks Rajat Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78190
  - 7
    - How to change the resource requirement of device in driver? Hi, How to change the resource requirement of device in driver? I am writing a Miniport driver. After the card inserted, the ResourceRequirementList can be read in HLM/SYSTEM/CurrentControlSet/ENUM/PCI/VEN... from Registry. REG_RESOURCE_REQUIREMENTS_LIST is shown as below, Alternative... Resou... Descrip.. Device.. 1 1 1 Memory 1 2 1 Memory 1 3 1 Memory 1 4 1 Intererupt The third memory is not need, and I want to move it. As the DDK said, I/O manager gives a chance to change the resource requirement. When FDO gets IRP_MN_FILTER_RESOURCE_REQUIREMENTS of IRP_MJ_PnP. I did this successfully, however, for doing this, I add the AddDevice routine and IRP_MJ_PnP dispatch routine, as a result, The MiniportInitialize function is not called. Who can give me some suggestion? Thanks! Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78187
  - 8
    - how the vmware windows virtual machine connect the usb device from the host machine ? When you run VMware on a Windows XP host, and a WindowsXP virtual machine runs in the VMware, now you plugin a new usb device to the host, the found new device wizard of the host machine will say that the host found a new device named VMware USB Device whose Hardware ID is USB\Vid_0E0F&Pid_0001. Then the host will load the VMware USB Device driver, which is a USB client driver. And the VMware virtual machine will detect the real usb device type and install the correct device USB client driver. When you unplug the usb device from the virtual machine, the host machine will replace the VMware USB Device driver with the correct device driver. I want to know how the whole process happens. Why the host pnp manager load the VMware usb client driver other than the correct device driver when detecting any usb device with the running of VMware? And how it replaces the VMware usb client driver with the correct device driver when you unplug the usb device from the virtual machine? The process likes a magic to me. I want to know how. The more detailed, the better. Thank you all! Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78186
  - 9
    - Incorrect INF - Installer File ? Thanks for the info. Sorry that my answer is so late, but I post things @codecomments.org, which is not very stable -- Markus09 ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78184
  - 10
    - [Q] Acquiring the same spinlock when it was previously acquired I'm seeing something strange in an NDIS miniport which uses a single spinlock. For example, in the driver's MPSendPackets() function: 1. The spinlock is acquired before calling processing the packets in the packet array. 2. MPSendPackets() calls SendPacket() to send each packet in the packet array. 3. SendPacket itself acquired the same spinlock, processes the send request and then releases the spinlock. 4. After all packets in the packet array have been processed, MPSendPackets() releases the spinlock. So, this driver is nesting spinlock aquires/releases while the same spinlock has previously been acquired. I would have throught this would have resulted in a deadlock, which doesn't happen. Is there a reference count maintained each time a spinlock is acquired, such that it is only released when the count becomes 0? I didn't see any mention of this in the DDK docs, but that seems to be what is happening. Thanks! Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78175
  - 11
    - Accessing PCI device behind a non-transparent bridge. I have some questions on accessing a PCI device behind a non-transparent bridge. I have a PCI bridge that originates a PCI like bus on its secondary device. This bridge connects to the host through the PCI slot(32-bit 33Mhz). The bridge, though, is a non-transparent bridge. This secondary bus allows regular PCI devices to be plugged into the bus. I have a PCI device that sits on the secondary bus. I have a driver for this device that works if the PCI device is plugged into the host's PCI bus. I am thinking that the same driver does not work when the PCI device is plugged to the secondary bus. In particular, since the bridge terminates all memory transactions on the secondary bus (including MSI and interrupt transactions) and does not forward to the primary interface, the driver as it is will not work. SO I have the following solution. Write a bus driver that talks to the bridge through the host PCI interface. This bus driver enumerates the PCI-like bus on the secondary side , will detect my device and initialize it. So far so good. The device I/F is such that its DMA ranges are programmed using configuration accesses. This is where the driver model breaks down. Even if my bus driver takes the config accesses and forwards them to the secondary side as configuration accesses on the secondary side, because the driver programs the ranges as host ranges which cannot be reached from the secondary side. THis means I cannot reuse the driver. Ideally, I want to be able to have the same driver binary in both PCI and secondary bus case. In the secondary bridge case, I want to be able to allocate shadow ranges on the host side that get filled in when the PCI device does DMA (or copied from) on the secondary side. I have another related question. Windows claims to run on architectures with non-transparent bridges(such as from Intel or DEC). If a PCI-to-PCI bridge is nontransparent can Windows reuse the same driver as in the traditional PCI case?. If so, how is this done especially if the secondary side cannot access the host memory ranges. Thank you, RK Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78167
  - 12
    - Bluescreen 0x0000007E Hi! I'm having some problems handling BusRelations. I keep getting a bluescreen (0x0000007E) as soon as I return something to the PnP manager. First, I create a device in an IOCTL: status = IoCreateDevice(..., &myChildDevice); ... myChildDevice->Flags &= ~DO_DEVICE_INITIALIZING; pExt->BusInfo.AChildDevice = myChildDevice; IoInvalidateDeviceRelations(pExt->Pdo, BusRelations); And then I handle the IRP_MN_QUERY_DEVICE_RELATIONS/BusRelations IRP: PDEVICE_RELATIONS pDeviceRelations = (PDEVICE_RELATIONS)pIrp->IoStatus.Information; if(pDeviceRelations) { ExFreePool(pDeviceRelations); } pDeviceRelations = (...)ExAllocatePool(PagedPool, sizeof(DEVICE_RELATIONS)); ... pDeviceRelations->Count = 1; pDeviceRelations->Objects[0] = pExt->BusInfo.AChildDevice; pIrp->IoStatus.Status = STATUS_SUCCESS; pIrp->IoStatus.Information = (ULONG_PTR)pDeviceRelations; In a nutshell, this is all that I do. If I comment out the last row, there's no bluescreen. Any ideas? Oh, and there are some blanks above. When done I pass the IRP through the stack, I always check that memory is allocated properly, I always check status codes etc. Thanks in advance, Nille Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78165
  - 13
    - Why is the HCT preventing my driver from unloading? The problem: I've developed a USB WDM driver that doesn't fall in any device category, so I'm trying testing it with the "universal" test suite. As soon as I select it in the HCT "Test Selection Wizard" window, and I click on ok, the driver will not unload any more. What's happening: knowing that this kind of problems are caused by leaky references to the device or driver object, I did my homework following the directions provided by Eliyas ("Debugging a Failed Driver Unload" in the WinDbg online help), looking for a mismatching ObReferenceObject/ObDereferenceObject couple in my driver. I indeed found one, but it's not in my driver: it's in kitdevis.sys, that appears to be part of the HCT distribution. It seems that for some reason, between two calls to my IRP_MN_QUERY_CAPABILITIES handler, kitdevis.sys increments the reference counter of my device obejct, and after that it never decrements it. A thing to mention is that I'm borrowing the PNP handling code from Walter Oney's WDM book, without any modification. Another thing to mention is that I never experienced any problem in unloading the driver, in months of developing and testing. It only happens when I click "ok" in the Test Selection Wizard. Now, I know I must be doing something very stupid, because it's impossible that the HCT suite has such a macroscopic problem, but I've no idea what. Does anybody know what could cause this behavior? Thanks in advance! Loris Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78164
  - 14
    - Saving Device Parms to the registry Is there any recommended maximum size of data that can be saved to the registry rather than saving to separte on disk file. For instance for my device to work I might need 6K bytes of radio PHY parameter data to program into the card. Is it OK to save that much data to a single Binary Value under my parameter key in the registry? How about in multiple Binary Values? thanks tom Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78144
  - 15
    - Programmatically power up or down a particular device [on a hotplug bus] Is there any documented way to programmatically change the power state of a device (i.e. power off or power on) from usermode? (I'm not particularly knowledgeable about programmatically controlling power management...) In particular, I'm looking to be able to power on or power off an arbitrary USB or 1394 device (i.e. not a device I wrote the driver for). For example, I might have an externally powered USB or 1394 device that is attached to a battery backup system that is separate from the battery backup system the computer is on. I can determine whether the battery backup system that the external device is on is low on power or not, but I need a way to gracefully shutdown the appropriate device before an impending power loss. Because the computer itself is on a different battery system (say for the sake of argument that it is a higher capacity battery system), I don't want (or need) to shut down the computer entirely, just the affected devices. Assume for the moment that I have control over any applications that might be using said devices and can make sure that they relinquish usage before I try to shutdown the device. One option I see is to request a graceful device removal (e.g. CM_Request_Device_Eject_Ex), since the devices are going to be on a hotpluggable bus, but this seems suboptimal for what I'm looking for. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78143
  - 16
    - Q) NDIS_STATUS_PENDING for a MiniportSetInformation and NdisMSetInformationComplete. Dear all, I'm developing NDIS miniport driver for Win2K and WinXP. If a Miniport D/D return NDIS_STATUS_PENDING for a MiniportSetInformation, it will need to return the final status for the NdisMSetInformationComplete. However, the NdisMSetInformationComplete does not have NDIS_OID or Informationbuffer that was from MiniportSetInformation. So, I think it is impossible to identify what the paired MiniportSetInformation is if there were multiple MiniportSetInformations with NDIS_STATUS_PENDING. Q) Between returning NDIS_STATUS_PENDING for a MiniportSetInformation and NdisMSetInformationComplete, is it guaranteed not to issue another MiniportSetInformation from the Window operating system? This can apply to MiniportQueryInformation/NdisMQueryInformationComplete as well. Have a nice weekend. Thank you. // Daum Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78138
  - 17
    - drivers location on x64 Hi Where are installed drivers stored on the Windows x64? The service key ImagePath still points to the system32\drivres directory, but you cannot find drivers there. TIA Andrew Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78137
  - 18
    - bug found only in signed printer driver, how to debug? I recently got my printer driver signed. After getting signed, our QA group found a bug. When I (and then they) tried to reproduce it, we found it only happens with the signed version. The unsigned version does not have the problem (it's a spooler crash when doing a test print as part of the install; test prints after install and normal application prints work fine). So I'm wondering how to debug this. I can't very well submit a debug version of the driver to be signed (cause then it will be part of windows update and all our customers will get this debug driver). And debugging the non-debug, signed, version of the driver is less than productive. Any ideas? Thanks, ScottR -- Scott Robins Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78136
  - 19
    - UpdateDriverForPlugAndPlayDevices does not remove all devices. Hi, I have a device driver that has many virtual devices that have been added through PnP via the AddDevice DriverObject Function call via the PnP system. I can have up to 255 of these devices for this driver. When I have created a new version of this driver, I update it with the system call, "UpdateDriverForPlugAndPlayDevices()". I was hoping that this call would force a call to my driver to "REMOVE_DEVICE" one at a time until there are no devices. At this time the PnP system would call my unload routine. Then when the PnP system calls the AddDevice routine the new driver would be loaded. It does work this way if I only have one or two devices on the driver. However, If I have more devices than this, then the PnP system sends the "REMOVE_DEVICE" IOCTL for a few of them, then calls the AddDevice for the devices that were just removed. Then it repeats this until all of the devices have been removed and re-added. Consequently, the number of devices never reaches zero and the unload routine is never called. At the end of the driver update, a reboot is required, because the previous version of the driver is still the running driver. My question is this: Is there anyway to tell UpdateDriversForPlugAndPlayDevices to remove all the devices before adding them back? Thanks in advance, -David G Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78134
  - 20
    - standby and hibernation How much will the typical laptop tax the battery if it goes to standby instead of hibernation. Is it significant? Will the standby mode still secure? I mean can someone get details of my computer or write a file (if I dont have antivirus/firewall, for example). I think hibernate is safest in this respect? thanks, Raj Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78126
  - 21
    - System hang Hi all, got a nasty system hang issue that I have about run out of ideas on: We only get the hang on an Asus A6000 U, we havent seen it on any other laptop, and, in fact, the driver for this device has been WHQLed in various versions for the last 6 months or so. The device is a PCCard device with an FPGA interface (It is also made by us). We are using WinDbg on a 1394 cable to debug. The hang happens with release drivers, and debug drivers that have no DbgPrinting. With a lot of DbgPrinting, the laptop doesnt hang. With just one DbgPrint at the very start of the Isr, wew do get tha hang, but WinDbg does not show a continuous trace, so this is not an unhandled interrupt as the ISr is not getting called. We cannot break into the hung laptop using Ctrl+Break. We can also not generate a user crash via the RightCtrl + Scroll Lock x 2 technique. Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78125
  - 22
    - Context for Temporary files in case of MSWORD Hi All, I am writing a file system driver for logging purpose. In it, i need to save the context of all the intermediate files formed in case of MS Officce Document. For example in case of MS Word alot many temporasry files with name as ~wr*****.tmp are formed. Now i need to save the refernce that all these files are formed by this particular word document that i have created. So my question is, alothugh some of these files are renamed inbetween (so not a problem to save referce to original file for them), but for all others, i m not able to relate it with the original document. Please help me in this. Regards, Shreshth Luthra Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78121
  - 23
    - Bluetooth DDI [Getting Interface via IRP_MN_QUERY_INTERFACE] Does anyone has any chance working on Bluetooth DDI so far? STATUS_NOT_SUPPORT (0xc00000bb) returned by IoCallDriver when I pass down IRP_MN_QUERY_INTERFACE irp to lower driver stack PDO (which is BTHPORT). The driver is enumerated by BTHPORT all right, *I assumed*. One way or another, I may get STATUS_INVALID_DEVICE_REQUEST with various attempt to send IRP_MN_QUERY_INTERFACE. Doron suggested that I might have the interface structure not well formed. I'm not sure what may the interface structure I need to form. I don't think I'm doing anything different to query interface. Has anyone had any success with getting Interface, or working on anything else, with Bluetooth DDI? Much Appreciated. ========== DEFINE_GUID(GUID_BTHDDI_SERVER_INTERFACE, 0x2caf6042, 0x3468, 0x4e46, 0xbf, 0xd6, 0x86, 0xd4, 0xbe, 0xf0, 0xb, 0x71); PINTERFACE Interface; irpStack->MinorFunction = IRP_MN_QUERY_INTERFACE; irpStack->Parameters.QueryInterface.InterfaceType = (LPGUID) &GUID_BTHDDI_SERVER_INTERFACE; irpStack->Parameters.QueryInterface.Size = sizeof(INTERFACE); irpStack->Parameters.QueryInterface.Version = 1; irpStack->Parameters.QueryInterface.Interface = (PINTERFACE) Interface; irpStack->Parameters.QueryInterface.InterfaceSpecificData = NULL; ========== Thanks RichardMAN Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78118
  - 24
    - How to write a ADC ,I2C,SPI driver in wince5.0 ? hi, We are planning to develop the following drivers for windowsCE5.0: 1,driver for built in ADC 2,driver for I2C to drive i2c DAC ie MAX5841 3,driver to support serial flash for the density of 4mb using SPI(AT25F4096) The drivers are for the samsungs s3sc2410 RISC microprocessor.i searched in platformbuilder help and there seems to be no sample code for these drivers? Since i am new to wince i am totally lost...can anyone please tell me if there is some sample driver available which i am missing out or if someone has worked on these drivers please let me know how to develop them or where to find some tutorial for this..... Thankyou Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78111
  - 25
    - STOP WZCSVC Hi! I use NDISUIO to look for the SSID avaiable and setting them, but I must stop WZCSVC and I don't know how to do it. Can you illustrate me how to do it? Thanks Giulio Tag: "Legacy" NDIS 5.x IM Driver On Vista Tag: 78097

Can someone tell me what kind(s) of performance degradations I can expect if
I run an NDIS 5.x IM driver (based on passthru) under Vista? Also, will I
need to do anything to the .inf files in order for this to work under Vista?

Thanks!

Top

Re: "Legacy" NDIS 5.x IM Driver On Vista by Alireza

Alireza
Thu Apr 13 03:01:11 CDT 2006

In Vista most (almost all) Gig adapters are going to be NDIS 6. TCPIP is
also an NDIS 6 protocol. If a legacy IM driver is installed, we have to
translate NDIS_PACKETs to NET_BUFFERs on both xmit and receive path. I don't
have any exact number for the performance impact but if your IM driver is an
IM filter driver, you can compare the performance of sample lightweight
filter driver with old passthrough IM filter driver and measure the
difference. if your driver is an IM mux driver, you can do the same with
sample MUX driver.

-thanks, ali

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Knotta Clue" <ImInSoquel@nospam.nospam> wrote in message
news:%23yJBHVqXGHA.4484@TK2MSFTNGP02.phx.gbl...
> Can someone tell me what kind(s) of performance degradations I can expect
> if I run an NDIS 5.x IM driver (based on passthru) under Vista? Also, will
> I need to do anything to the .inf files in order for this to work under
> Vista?
>
> Thanks!
>

Top

Re: "Legacy" NDIS 5.x IM Driver On Vista by Stephan

Stephan
Thu Apr 13 03:07:22 CDT 2006

Knotta Clue wrote:
> Can someone tell me what kind(s) of performance degradations I can expect if
> I run an NDIS 5.x IM driver (based on passthru) under Vista? Also, will I
> need to do anything to the .inf files in order for this to work under Vista?

>From the "Driver Compatibility for Windows Vista" document
(http://www.microsoft.com/whdc/driver/WDK/DrvCompat_Vista.mspx):

- NDIS 5.x and earlier drivers must go through a translation layer.
Windows Vista supports NDIS 6.0. NDIS 5.x and earlier drivers run in
Windows Vista, but they do so by translation to NDIS 6.0. The
translation layer can significantly reduce driver performance.

Solution: To avoid the translation penalty, port NDIS 5.x drivers to
NDIS 6.0.

For more information, see the white paper titled "Porting Miniport
Drivers to NDIS 6.0." In the WDK documentation, see also
"Introduction to NDIS 6.0" and "Porting NDIS 5.x Drivers to NDIS
6.0."

- NDIS 4.0 and 5.x intermediate filter drivers install and run in
Windows Vista, but they are deprecated.

Solution: Rewrite intermediate filter drivers as NDIS 6.0 filter
drivers.

For more information, see the WDK documentation, "NDIS 6.0 Filter
Drivers."

HTH, Stephan

Top