Why Driver Entry called two times in the Mux Sample

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
    - MiniDriver in vista??? Hi! I am new to device driver technology and working on porting the existing device drivers for xp to vista. I have gone thru lot of RnD and able to port many of the example code. I am having a problem in installing the minidriver sample code which is shipped with vista in location "\WinDDK\6000\src\print\mini\mdw\canon10v". After building it for vista environment, when i try to install it with the help of inf file, i got error message "Printer driver was not installed. Operation could not be completed". Any having idea regarding the same. Or if any change in build procedure so that i can successfully install minidriver on Vista Machine. others components provided in print folders can be installed successfully. I am only facing problem in installing minidriver. Please reply. thanks in advance for kind effort. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95609
  - 2
    - About IoConnectInterrupt parameter Hi, The 9th parameter of IoConnectInterrupt() is: IN BOOLEAN ShareVector And in DDK, it is explained as: Specifies whether the interrupt vector is sharable Does that mean that if I specify ShareVector as TRUE, I can connect more than one ISRs to that vector? thanks for any help. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95607
  - 3
    - tiff multipage printer hi, i know it is a frequently asked question, but still without an answer. how should i change the bitmap sample that comes with the ddk to make it print tiff multipage, should i change the imageprocessing function or the filtergraphcs and how to do so any sample any link any word is appreciated thanks Tag: Why Driver Entry called two times in the Mux Sample Tag: 95606
  - 4
    - Driver Signing what steps do i follow in order to get my driver(s) signed? what certificates do i puchase? i've read thru numerous documents but they seem circular, incomplete, and incorrect. is here a simple list of steps that i missed somewhere? Tag: Why Driver Entry called two times in the Mux Sample Tag: 95601
  - 5
    - Mirror driver and Terminal Services/FUS From the DDK documentation: "Fast User Switching works by allowing multiple virtual display drivers to run at the same time. (Each virtual display driver is associated with a particular PDEV.)" Is this true for mirror drivers as well? Could one install a mirror driver and then, while more than one user is logged in, capture those users' screens? (assuming things like memory mapping etc. are properly implemented in the mirror driver) And another question just out of curiosity, how is this implemented for drivers that actually control real hardware? Would the driver have to share its video memory amongst those sessions or is only the glass/physical terminal be able to use the video hardware? Thanks in advance Tag: Why Driver Entry called two times in the Mux Sample Tag: 95592
  - 6
    - Serial Device Enumeration Problem (VCP) Hi Experts, I am writing a virtual Serial/COM port driver using WDF. Everything working fine with my driver except Enumeration of Serial Devices which are attached to my Virtual COM port. I built the same driver for both WindowsXP SP2 and Windows Vista Ultimate. Its enumerating the the attached devices in WindowsXP SP2, But Its not enumerating the attached Serial device in Windows Vista Ultimate. I am loading the Serenum as upper filter to my driver which im specifying in INf file. One thing I observed is that, In WindowsXP during the driverloading process I am getting IRP_MJ_CREATE (SerialWdmDeviceFileCreate() callback) and attached devices are enumerated in that sequence. But In case of windows Vista, during driver loading process I haven't seen any EvtDeviceFileCreate() callback called, hence there is no attached device enumeratiion. Is this the expected result? Also with !devstack command i could able to see serenum as upper filter device object in XP, where as in Vista the command did not show serenum as upper filter device object. Regards, Nancy Tag: Why Driver Entry called two times in the Mux Sample Tag: 95581
  - 7
    - [WIA] Use of usbscan.sys Hello, In order to use a scanner on Windows (XP, 2003 and Vista for instance), I have to create a minidriver (based on the wiascanr sample). This DLL will use a kernel-mode driver provided by Microsoft and called usbscan.sys. I found the header file usbscan.h but do you have documentation on how to use usbscan?!? Thank you! Tag: Why Driver Entry called two times in the Mux Sample Tag: 95579
  - 8
    - For PDO: How to forward request to next lower driver stack automatically in KMDF? Dear all: For filter drivers, KMDF automatically forwards the request to the default I/O target (the next lower driver). How to do this in PDO? Is there any option to do this? I write two drivers: one for a bus driver to enumerate child device, and another is for child device. I want to forward all child device FDO request to bus driver FDO. So I need the function mentioned in subject. Thanks. Casper Tag: Why Driver Entry called two times in the Mux Sample Tag: 95577
  - 9
    - Execution Sequence of default drivers in WinCE 5.0 Hi all, I had a doubt on how to set the execution sequence for the Windows CE 5.0 default drivers. Actually i'm using MIPSII BSP for my project. Whether there is any settings to be done to registry file/Binary Image Build(.bib) file. please reply me back as earlier as possible as now i was struck with my project. regards, S. Pradeep Kumar Tag: Why Driver Entry called two times in the Mux Sample Tag: 95576
  - 10
    - driver type for sending packets ??? Dear Expert, I want to write a simple driver which would be able to send set of packets over the network at highest speed. Please suggest me which type of driver should be writen i.e. IM driver, Protocol driver, TDI driver or filter driver? Waiting for your reply. -- With regards thanks Anand Choubey Tag: Why Driver Entry called two times in the Mux Sample Tag: 95575
  - 11
    - Linking error with DDK function... Hi Everyone, I am trying to use "DrvQueryJobAttributes" in VC++ .net 2005. But it is giving me following error: Error 1 error LNK2019: unresolved external symbol _DrvQueryJobAttributes referenced in function __catch$_main$0 main.obj Error 2 fatal error LNK1120: 1 unresolved externals D:\VC\PrintProcessor\Debug\PrintProcessor.exe 1 Can anyone help me to resolve above error. (I've DDK within my system). Regards, Chirag. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95569
  - 12
    - How to support USB IAD on Win98/ME/2000? I would write UVC driver for Win98/ME/2000. UVC device uses IAD to declare video interface collection. That is, multiple interfaces may be grouped for one device function. Currently, usb composite parent driver usbccgp.sys supports IAD on XP SP2 or later For Win98/ME/2000, IAD is not supported. How should I write my UVC driver on Win98/ME/2000? Do I need to write another parent driver such as usbccgp.sys to handle IAD and create PDO for each device function? or I just use my camera driver and issue the request to different interface in the same driver? If I need to handle function like usbccgp.sys, what does it do? Is any reference code fot this? Best Regards Jack Huang Tag: Why Driver Entry called two times in the Mux Sample Tag: 95568
  - 13
    - Regarding Driver Build Hi, can we use a windows server 2003 x64 build for windows xp 32 bit machine. I know that windows server 2003 x64 build can be used for windows xp x64 version. Basically I am thinking of using the same binary (windows server 2003 x64 build for both the machine) 1.windows xp 32 bit processor 2.windows 64 bit processor x64 build version of windows. Right now I am using windows xp build for 32 bit processor (windows 32) Thanks in Advance Tag: Why Driver Entry called two times in the Mux Sample Tag: 95567
  - 14
    - Can not install Ergonomic Keyboard driver Recently purchased MS Natural Ergonomic 4000 keyboard. Driver installation gets started then aborts due to not enough disk resource. I have GBs! Have cleared out all temp files, but can not determine where .exe is trying to execute from. No quota's established, and have tried downloading device driver from the net with the same result. Any thoughts or has anyone struck the incident before and solved it? J Tag: Why Driver Entry called two times in the Mux Sample Tag: 95554
  - 15
    - MS Certification Practice Exams FREE Demonstration Exams Goto: www.wswexams.com Tag: Why Driver Entry called two times in the Mux Sample Tag: 95551
  - 16
    - Errors in the Printer Driver when building Hi Guys! Good day! I am currently developing a printer driver based on the samples provided in the WDK. I was able to build and integrate a TIFF library so that my output will be in TIFF rather than in Bitmap. My problem now is that I am trying to put a custom property sheet in the printer driver but i am getting these errors (see error snippet). I have already included the required headers for the property sheet (see header snippet) but I am still getting these errors. I am building the code using the Windows XP checked Build Environment provided in the WDK. Any ideas? Thank you! ********Error snippet*********** errors in directory c:\winddk\3790~1.183\src\print\oemdll\redmapprinter c:\winddk\3790.1830\src\print\oemdll\redmapprinter\oemui.h(39) : error C2061: sy ntax error : identifier 'POEMCUIPPARAM' c:\winddk\3790.1830\src\print\oemdll\redmapprinter\oemui.h(40) : error C2061: sy ntax error : identifier 'IPrintOemDriverUI' Compiling - enable.cpp for i386 Compiling - generating code... for i386 Building Library - c:\winddk\3790~1.183\src\print\oemdll\i386\redmapprinter.lib for i386 LIB : error LNK1181: cannot open input file 'objchk_wxp_x86\i386\devmode.obj' BUILD: Compile errors: not linking c:\winddk\3790~1.183\src\print\oemdll\redmapp rinter directory BUILD: Done 8 files compiled - 1 Warning - 2 Errors 1 library built - 1 Error C:\WINDDK\3790~1.183\src\print\oemdll\RedmapPrinter> ******Header Snippet******* #include <STDDEF.H> #include <STDLIB.H> #include <OBJBASE.H> #include <STDARG.H> #include <STDIO.H> #include <WINDEF.H> #include <WINERROR.H> #include <WINBASE.H> #include <WINGDI.H> #include <WINDDI.H> #include <WINSPOOL.H> #include <TCHAR.H> #include <EXCPT.H> #include <ASSERT.H> #include <PRSHT.H> #include "COMPSTUI.H" #include <WINDDIUI.H> #include <PRINTOEM.H> #include <PRCOMOEM.H> Tag: Why Driver Entry called two times in the Mux Sample Tag: 95550
  - 17
    - AddPort fails when others are logged on Here's the situation. I'm running XP and I've got two users with admin privileges, call them A and B. 0. Boot system. 1. Log on user A. 2. Switch user (but don't log off A) to user B. 3. Run the printer driver installer which was provided (with source code) from a third party. Result: The call to AddPort() fails with Windows Error 50 (ERROR_NOT_SUPPORTED). The call which fails is: AddPort(NULL, NULL, lpMonitorName) One wrinkle is that it appears to depend on who first logged on. For example, if I add the following step 2.5, the error does not occur: 2.5. Switch user (but don't log off B) back to user A. Another wrinkle is that I have a unicode-based version of the installer which has the same problem but returns a different error code: 5 (ERROR_ACCESS_DENIED). The third party claims that this is a limitation of the AddPort call, and that the question should be addressed to Microsoft. But wouldn't that imply that, in general, if an admin user is logged on, it's not possible for any subsequent admin user to log on and install a printer driver? I wouldn't expect that behavior. Thanks for any explanations or clarifications. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95548
  - 18
    - Use Printer Offline In the spooler Window for a printer (any port connection) you can see the online/offline status of the printer. Especially when using USB or TCP/IP I noticed Windows is also setting "Use Printer Offline" which is also a setting in the Printer menue and is a sticking state (at least sometimes). I have three problems. 1. Can I programmatically change this on or off? 2. Why is this state sometimes changing and sometimes not? 3. When I am connecting to a print server via a Language Monitor / Port Monitor for the print server it happens all the time that on reboot the "Use Printer Offline" is sticky and can't be reset. You have to attach the print server manually in the Port setup again to fix this problem. What do I have to do to fix this? I hope someone wil get me some answers on these questions. Thanks in advance. -- \Manfred Tag: Why Driver Entry called two times in the Mux Sample Tag: 95537
  - 19
    - Developing for multi core CPUs Hi, i wondered wether it is possible to determine on which CPU a driver is loaded on a multi core system. The intention behind this is that i want to have a whole CPU on my own to get highest performance and avoid interfering with the rest of the system. Regards Max Tag: Why Driver Entry called two times in the Mux Sample Tag: 95521
  - 20
    - USB Device Interface Hi, I'm writing NT Service that listens device notifications. I am subscribing on DEV_BROADCAST_DEVICEINTERFACE notifications. After USB (flash drive or HDD) is connected, I get DBT_DEVICEARRIVAL notification. The notification contains the string \\?\Description{GUID}. I find the same string in the registry HKLM\CONFIG\...\DeviceClasses\... But I cannot know how to get its drive letter? Any help would be appreciated. Ilia Tag: Why Driver Entry called two times in the Mux Sample Tag: 95520
  - 21
    - Windows Logo Program Requirements (V. 2.2) Hello, I have to study how to obtain Windows XP x86 Logo and Windows Server 2003 x86 Logo. For a Windows Vista Logo, I would look at the Windows Logo Program 3.0 for which there is a nice Excel file. I looked at the Windows Logo Program 2.2 but I didn't find such an Excel file :( If somebody can tell me where I can find it, it would be great! Thank you!! Tag: Why Driver Entry called two times in the Mux Sample Tag: 95518
  - 22
    - How to comunicate with Filter Driver Hi all, I have made a filter driver, I have implemented all MJ functions, but now I have a problem. I want to read / write from my monitor application to my filter driver for get some data, but how can I recognize inside my filter driver if IRP_MJ_DEVICE_CONTROL, IRP_MJ_READ, IRP_MJ_WRITE is comming from my monitor application or is external and so the IRP must be passed to the next node? Best Regards. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95517
  - 23
    - ATAPort It was rumor floating around that MS planned to re-introduce the ATAPort on this WinHECâ?¦did it happen? Tag: Why Driver Entry called two times in the Mux Sample Tag: 95516
  - 24
    - Crash Dump Analysis Hello All, i have posted a query regarding the crash few days ago. Yakub suggested me to do !wdfdevicequeues for seeing if there are any pending requests. I did the following for the serial driver. i opened the hyper terminal and here is the output for above command. kd> !wdfdevicequeues 0x7d569a48 Dumping queues of WDFDEVICE 0x7d569a48 ===================================== Number of queues: 4 ---------------------------------- Queue: 1 (!wdfqueue 0x7d5259e0) Parallel, Power-managed, PowerOn, Can accept, Can dispatch, ExecutionLevelDispatch, SynchronizationScopeDevice Number of driver owned requests: 2 !WDFREQUEST 0x7d52e510 !IRP 0x82817b48 !WDFREQUEST 0x7d83c180 !IRP 0x822bd490 Number of waiting requests: 0 Number of driver owned cancelable requests: 2 !WDFREQUEST 0x7d52e510 !IRP 0x82817b48 !WDFREQUEST 0x7d83c180 !IRP 0x822bd490 EvtIoRead: (0xaad056a0) usbservista!SerialEvtIoRead EvtIoWrite: (0xaad05940) usbservista!SerialEvtIoWrite EvtIoDeviceControl: (0xaacffab0) usbservista! SerialEvtIoDeviceControl EvtIoInternalDeviceControl: (0xaad00010) usbservista! SerialEvtIoInternalDeviceControl EvtIoCanceledOnQueue: (0xaacfef80) usbservista! SerialEvtCanceledOnQueue ---------------------------------- Queue: 2 (!wdfqueue 0x7d5247f8) Manual, Power-managed, PowerOn, Can accept, Can dispatch, ExecutionLevelDispatch, SynchronizationScopeDevice Number of driver owned requests: 0 Number of waiting requests: 0 EvtIoCanceledOnQueue: (0xaacfef80) usbservista! SerialEvtCanceledOnQueue ---------------------------------- Queue: 3 (!wdfqueue 0x7d5237f8) Manual, Power-managed, PowerOn, Can accept, Can dispatch, ExecutionLevelDispatch, SynchronizationScopeDevice Number of driver owned requests: 0 Number of waiting requests: 0 EvtIoCanceledOnQueue: (0xaacfef80) usbservista! SerialEvtCanceledOnQueue ---------------------------------- Queue: 4 (!wdfqueue 0x7d522a88) Manual, Power-managed, PowerOn, Can accept, Can dispatch, ExecutionLevelDispatch, SynchronizationScopeDevice Number of driver owned requests: 0 Number of waiting requests: 0 EvtIoCanceledOnQueue: (0xaacfef80) usbservista! SerialEvtCanceledOnQueue I closed the hypterminal then i get the following output for the above command. kd> !wdfdevicequeues 0x7d569a48 Dumping queues of WDFDEVICE 0x7d569a48 ===================================== Number of queues: 4 ---------------------------------- Queue: 1 (!wdfqueue 0x7d5259e0) Parallel, Power-managed, PowerOn, Can accept, Can dispatch, ExecutionLevelDispatch, SynchronizationScopeDevice Number of driver owned requests: 0 Number of waiting requests: 0 Number of driver owned cancelable requests: 1 !WDFREQUEST 0x00000034 !IRP 0x82817b48 Failed to get a pointer @ 0xfffffff4: invalid address, or memory is paged out? c0000005 Exception in D:\WINDDK\6000\bin\x86\wdfkd.wdfdevicequeues debugger extension. PC: 7c812a5b VA: 00000000 R/W: 1003f Parameter: 00000000 im not able to figure out what is going wrong. Can any one help me in analyzing the problem. Thank You. Regards, uba Tag: Why Driver Entry called two times in the Mux Sample Tag: 95515
  - 25
    - chkinf bug: No )'s in the path so no DirectX in the path Hi, Running chkinf gives me: \Utilities\Bin\x86 was unexpected at this time. This is part of a DirectX install which adds the following to the path: C:\Program Files\Microsoft DirectX SDK (April 2007)\Utilities\Bin\x86 I'm guessing the problem is this "for" line (about line 27): for %%I in (%PATH%) do ( if exist %%~fsI\chkinf.bat ( set PLibPath=-I%%I goto runit ) The "if" may become a problem too. I worked around the problem by modifying the path variable to not have that directory in the path. I did this by: 1. Typing "echo %path%" 2. Copying the path to notepad 3. Deleting the problematic directory 4. Coping the new text for the path variable 5. typing "path=" followed by pasting the new list of directories I'm not sure, but it appears another work around is to add the chkinf directory to the beginning of the path variable. I'm not sure where to report this issue, and my quick check doesn't show any documentation on this issue. I hope this is the appropriate way to get this fixed or at least documented. If not, please advise me. Thanks, Drew Daniels Tag: Why Driver Entry called two times in the Mux Sample Tag: 95514
- Next
  - 1
    - USB communication hangs Hello NG, I am currently testing our self-developed USB device driver. It works fine on most machines. However on a few machines it seems as if a reading operation which has been passed down the stack does not return. Meaning the completion routine is never called and therefore the IRP is never completed. As my application is performing synchronous IO-operation on the device my application hangs up and can be ended only by killing it through the task manager. I found this strange driver behaviour by implementing several debug traces in a checked version of the driver and watching that traces with debug view. Debugging the driver with WinDBG also did not bring anything new. Here a short code snippet how I pass down the IRP to the lower driver: //*************************************************************************************************************************************** pNextStack=IoGetNextIrpStackLocation(pIrp); pNextStack->MajorFunction=IRP_MJ_INTERNAL_DEVICE_CONTROL; pNextStack->Parameters.Others.Argument1=(PVOID)pUrb; pNextStack->Parameters.DeviceIoControl.IoControlCode=IOCTL_INTERNAL_USB_SUBMIT_URB; IoSetCompletionRoutine(pIrp, ReadCompletion, pReadContext, TRUE, TRUE, TRUE); IoMarkIrpPending(pIrp); ntStatus=IoCallDriver(pDeviceInfo->pNextDeviceObject, pIrp); return STATUS_PENDING; //*************************************************************************************************************************************** What can be the reason for not getting the IRP completed? Any ideas? Thanks in advance Benji Tag: Why Driver Entry called two times in the Mux Sample Tag: 95512
  - 2
    - Disabling Devices by calling Setupapi.dll, or Converting Devcon to C# Hello group, My C# app needs to disable and re-enable devices. I did some research and found that I could do exactly what I wanted by using Devcon from the DDK. Devcon disable =net @ROOT\POSNATMP\0001 Now, the next challenge is getting this to work in my app. Devcon comes with its C++ source. I see that the function makes SetupDi* calls to the Setupapi.dll library. I am not quite sure how to do this in C#. I followed Vladimir Afanasyev articles and got a little closer. I can enumerate the devices and properties. Afanasyev mentions, in the user comments, that you can disable devices as well but does not provide sample code. This means I am much closer but still not quite able to toggle the device drivers. In sum, I am looking for the answer to one of three questions. 1) Does the .Net Framework 2 provide a way to disable/enable devices? 2) If it does not, what is the best way to convert Devcon C++ sample to a C# app? 3) Alternatively, what could I add to Vladimir Afanasyev's code to disable/enable devices? Thanks in advance, J Wolfgang Goerlich Related Links: Microsoft Article 311272, The DevCon command-line utility functions as an alternative to Device Manager http://support.microsoft.com/kb/311272 .NET - Diving into System Programming - Part 1, 2, 3 By Vladimir Afanasyev http://www.codeproject.com/cs/system/divingsysprog1.asp http://www.codeproject.com/cs/system/divingsysprog2.asp http://www.codeproject.com/cs/system/divingsysprog2.asp Tag: Why Driver Entry called two times in the Mux Sample Tag: 95502
  - 3
    - Why is IoStatus.Information is so sensitive? In a completion routine for a (pending) IRP for writing numBytes (coming via DeviceIoControl), I am setting the IoStatus block before calling IoCompleteRequest(): irp->IoStatus.Status = STATUS_SUCCESS; irp->IoStatus.Information = numBytes; IoCompleteRequest(irp, IO_NO_INCREMENT); The strange thing is that if I set irp->IoStatus.Information to the actual numBytes that were written (several hundreds), the driver doesn't like it... Strange things happen like access violation etc. But... if I set irp->IoStatus.Information to a hard coded value of 4, all is well. Why? Isn't irp->IoStatus.Information supposed to actually relay back (to the caller of DeviceIoControl) any number desired? (in this case the number of bytes actually written, just like file I/O for example. I tried to find some documentation about the *purpose* and *intended use* of IoStatus.Information but all I could find is: "This is set to a request-dependent value. For example, on successful completion of a transfer request, this is set to the number of bytes transferred. If a transfer request is completed with another STATUS_XXX, this member is set to zero." Now... I *am* returning STATUS_SUCCESS, so what's wrong with returning a number greater than 4? Thanks, Don Tag: Why Driver Entry called two times in the Mux Sample Tag: 95485
  - 4
    - mirror driver and service in multiple sessions Hi all, I developed a mirror driver that is able to map its framebuffer into a usermode process' context. (The usermode app does this by calling ExtEscape on the mirror driver). This is all working fine but what i really want is a seperate service .exe and be able to map a specific session's mirror driver framebuffer into that service app. Obviously the problem here is that the server .exe and the session the mirror driver is in are probably different. I was thinking about using some kind of intermediate/broker process in every session but I'd really like to avoid ending up mapping the mirror driver's framebuffer into this intermediate/broker process and then somehow send it to the service app. So in other words: i want to be able to call a particular mirror driver's DrvEscape function so that it can map the framebuffer into the calling process (my service in this case). Thanks in advance! Tag: Why Driver Entry called two times in the Mux Sample Tag: 95474
  - 5
    - New to driver development Hi, We are developing a USB thermal printer driver. We were able to install our printer using the sample codes from the DDK but how do we issue commands when we do the actual printing? I mean how do we issue the ESC sequences that are sent to the printer? Where do we write the code for this purpose? Regards, Samir Tag: Why Driver Entry called two times in the Mux Sample Tag: 95470
  - 6
    - Pagefile and FSCTL_QUERY_RETRIEVAL_POINTERS Is FSCTL_QUERY_RETRIEVAL_POINTERS just for the first pagefile on the boot volume or does it also work for additional pagefiles? I am trying to interpret the following comment by Tony Mason: "That is why FSCTL_QUERY_RETRIEVAL_POINTERS only works on the boot drive's paging file (the dump driver needs the blocks to dump it)." http://www.osronline.com/showThread.cfm?link=40066. Regards, George. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95458
  - 7
    - Virtual network adapter ? Hello, I'm willing to write a virtual network adapter, which won't be connected to any real hardware, but will be "driven" by a running application: packet sent to this adapter shall be read by this application, and the app sometimes send packets to the adapter which are to be dispatched on whoever read on the specified port. The problem being, I'm new to driver developpement. Thus I have a couple of questions: 1 - I've installed the latest windows DDK, is ti correct ? I've seen another framework, but it seems to be vista only out of the box, right ? 2 - I'm looking at the "netvmini" sample provided by microsoft, since it also create a virtual network adapter, again, am I correct ? I'm a little lost between all teh different NDIS drivers types. 3 - What is the best way to make my driver and the running application communicate ? Ioctl control, shared memory, ... ? And what function in the driver should I look at on msdn for receiving/sending packet ? (aka: where in the driver should I put my logic for reading packets from the application, and sending the received packet to the application). Thanks for any answer -- Lepidosteus / Vianney Devreese mail: lepidosteus at gmail dot com url: http://lepidosteus.com Tag: Why Driver Entry called two times in the Mux Sample Tag: 95452
  - 8
    - Create a virtual network adapter ? Hello, I need to create a driver for a virtual network adapter, the prupose being to allow softwares to communicate on it asif it was a real connection, while in fact it is controlled by a running application (packets sent to it are read by this application, and the same application sometimes needs to send packets "trough" this interface to answer). I'm new to driver coding, so I have some questions: 1 - I'm using the latest Windows DDK to develop this, is it correct ? (I've seen another framework for vista drivers, but I guess it isn't backward compatible out of the box ?) 2 - to do this, I'm studying the "netvmini" sample provided by microsoft, since it creates a virtual adapter that, well, do nothing. Am I correct ? (I'm a little lost between the different kind of NDIS drivers) 3 - How to make it write and read its packet to an application ? What I would like to know is both the best way to share data between them (shared memory ? ioctl control ?), and the two "base" fonction I should look at for sending/receiving packets (I've found no how to, so all I can do is study the api for this function). Thanks a lot for any anwser -- Lepidosteus / Vianney Devreese mail: lepidosteus at gmail dot com Tag: Why Driver Entry called two times in the Mux Sample Tag: 95451
  - 9
    - WDK 6000 build env error "error '-f' is not recognized as an internal or external command" First thanks a lot to Doron Holan & Eliyas Yakub for your help. I'm moved into WDK 6000 with KMDF 1.5 ,then the Common buffer allocation works well ,if failed ,I can see the yellow "!" in my device manager.But there is a small problem between my building progress.Followwing is the error log: ************************************* errors in directory l:\work\file4drvtest\kerneldrv\src l:\work\file4drvtest\kerneldrv\src\generating code... : error '-f' is not recognized as an internal or external command, ************************************* And my build command window log: *********************************** L:\Work\File4DrvTest\KernelDrv\Src>build -ceg BUILD: Compile and Link for x86 BUILD: Loading e:\winddk\6000\build.dat... BUILD: Computing Include file dependencies: BUILD: Start time: Sat Jun 02 15:22:57 2007 BUILD: Examining l:\work\file4drvtest\kerneldrv\src directory for files to compi le. l:\work\file4drvtest\kerneldrv\src - 7 source files (4,550 lines) BUILD: Saving e:\winddk\6000\build.dat... BUILD: Compiling l:\work\file4drvtest\kerneldrv\src directory _NT_TARGET_VERSION SET TO WINXP Precompiling - precomp.h Compiling - adxdev.rc Compiling - adxdev.c Compiling - init.c Compiling - isrdpc.c Compiling - read.c Compiling - write.c Compiling - generating code... Compiling - generating code... errors in directory l:\work\file4drvtest\kerneldrv\src l:\work\file4drvtest\kerneldrv\src\generating code... : error '-f' is not recogn ized as an internal or external command, BUILD: Linking l:\work\file4drvtest\kerneldrv\src directory _NT_TARGET_VERSION SET TO WINXP Linking Executable - objfre_wxp_x86\i386\adx16xx.sys BUILD: Finish time: Sat Jun 02 15:23:00 2007 BUILD: Done 11 files compiled - 1 Error - 4550 LPS 1 executable built ************************************ And the followwing is my "sources" file context: ************************************ TARGETNAME=Adx16xx TARGETTYPE=DRIVER KMDF_VERSION=1 INF_NAME=Adx16xx MISCFILES=$(OBJ_PATH)\$(O)\$(INF_NAME).inf NTTARGETFILES= TARGETLIBS=$(TARGETLIBS) \ $(DDK_LIB_PATH)\ntstrsafe.lib PRECOMPILED_INCLUDE=precomp.h PRECOMPILED_PCH=precomp.pch PRECOMPILED_OBJ=precomp.obj #C_DEFINES = $(C_DEFINES) -DASSOC_WRITE_REQUEST_WITH_DMA_TRANSACTION=1 SOURCES= AdxDev.rc \ AdxDev.c \ Init.c \ IsrDpc.c \ Read.c \ Write.c # # Generate WPP tracing code # $(SOURCES) -- run software preprocessor on files listed in SOURCES # -km -- use kernel mode # -func -- define function we'll use for tracing # This would map all TraceEvents calls to # DoTraceMessage. # RUN_WPP= $(SOURCES) \ -km \ -func:TraceEvents(LEVEL,FLAGS,MSG,...) \ -gen:{km-WdfDefault.tpl}*.tmh ***************************************** Can you give some suggestions to aviod the error? Thanks ! Tag: Why Driver Entry called two times in the Mux Sample Tag: 95449
  - 10
    - Oemui and Oemuni...what's the difference? Hi, I am currently working on trying to convert an oemuni image printing driver to a user-mode driver instead of a kernel-mode driver for use in Windows Vista. First question, is there any reason an oemuni driver cannot be implemented as a user-mode driver? I've found these two resources on conversion ([url]http://www.unixwiz.net/techtips/win32-pdriver-ktou.html[/url] and [url]http://msdn2.microsoft.com/en-us/library/ms801104.aspx[/url]) and have tried converting along those guidelines, but am still unable to compile my driver in user mode with the ddk. Second question, is there a major difference/what is the difference between oemuni drivers and oemui drivers? I was considering porting the oemuni driver to oemui, since oemui is already compiled under user mode, but I'm not sure if that's even possible. Again, just for reference, I am working on a print driver that saves the printed document as a sequenced image file (which has been tested in Windows XP) and am trying to port it to a user-mode driver for use in Windows Vista (since vista does not allow kernel-mode drivers). Any replies/references/etc are appreciated. Thanks for taking the time to read this thread! Nuvious P.S. I am working for a company that produces this software as a FREERWARE utility, so I am unable to post any code due to legal restrictions. Again, any help is appreciated. -- Nuvious ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ Tag: Why Driver Entry called two times in the Mux Sample Tag: 95443
  - 11
    - storport requests queue Hi I am developing a storport mini-port driver for Vista and I got a strange problem â?? the storport queues not more than 20 requests against my mini-port driver; I generated different workloads and under heavy load I can see that my mini-driver has 20 outstanding requests practically all the time during the test Any idea how this limitation gets imposed? TIA Andrew Tag: Why Driver Entry called two times in the Mux Sample Tag: 95439
  - 12
    - How to get debug prints in WinDbg from Vista I'm trying to debug my property page provider application on 32bit variant of Vista Ultimate by using WinDbg with a serial connection to try and capture the snapshots being sent by the "OutputDebugString" calls, but nothing comes out to the command window! The same application works just fine under Windows XP, Server 2003, and Windows 2000. I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls only to learn that the former returns a FALSE to the local variable receiving the value when the breakpoint is hit on the latter call. What isn't clear is why the debug connection is established and control is passed to the debugger, yet "IsDebuggerPresent" returns a false and "OutputDebugString" calls are not routed through the connection? I've tried setting the "Debug Print File" as defined in http://www.osronline.com/article.cfm?article=295, but to no avail. Is there another trick to getting debug print statements out of Vista to WinDbg that I'm missing? Tag: Why Driver Entry called two times in the Mux Sample Tag: 95434
  - 13
    - Property sheets in Printer Preferences I have a problem with a property page in the printer preferences. I am setting a handle to my current printer in the creation of the property page. Page.lParam = (long)((OEMUIPSPARAM*)(pPSUIInfo->lParamInit))->hPrinter; When I open this page I save this printer handle in case WM_INITDIALOG: // OpenPrinter hPrinter = (HANDLE)((PROPSHEETPAGE *)lParam)->lParam; VERBOSE(PRNTEXT("Printer handle [%x]\n"), hPrinter); UserData.hPrinter = hPrinter; PUserData1 = &UserData; SetLastError(0); if ((PUserData = (CBMYUSERDATA*)SetWindowLong(hDlg,GWL_USERDATA,(DWORD)PUserData1)) == 0) { dwError = GetLastError(); } Now when I get into the case case WM_NOTIFY: it works to retrieve this printer handle and work with it, but when I press a button on the dialog it goes into case WM_COMMAND: and my handle is false! What am I doing wrong here? I need the access to the printer handle to use GetPrinterData and SetPrinterData. Any help appreciated. Thanks, -- \Manfred Tag: Why Driver Entry called two times in the Mux Sample Tag: 95430
  - 14
    - kernel memory hog There is a certain well know virus/spyware protection company, (not mcaffe, not symantec) that uses a gigantic chunk (around 78 MB ) of paged memory in the kernel and NEVER relinquishes it. If this stuff is installed on a computer, my software , which uses a substantial chunk of paged memory from time to time will simply not function. So far I've not gotten anyone's attention beyond the 1st line of technical support The unnamed company is much bigger than me, what can be done????? I'd hate to think about forcing my driver to load early, grabbing what it needs before this hog gets it snout in the trough ....That would result in 2 hogs with the expected results ... blah blah. -- Gak - Finecats Tag: Why Driver Entry called two times in the Mux Sample Tag: 95427
  - 15
    - strange things about NET_BUFFER_LIST hi everybody I write a miniport driver under Vista base on the sample rtlnwifi, and I crypt the out data. What I do like this: 1, get the NET_BUFFER from NET_BUFFER_LIST 2, get the MDL from this NET_BUFFER 3, get the data address of the MDL 4, so I copy all the data of the NET_BUFFER_LIST to a buffer use this method, and I crypt the data within the buffer(size of data not changed) 5, at last I copy the data back to NET_BUUFER_LIST, send it out through the NIC on the other PC which has Vista on it, I decrypt the data. The problem is: I share a fold, and copy some files in it, such as 123.txt or aaa.bmp, from PC1 to PC2, PC2 can get the file correctly, but the strange thing is that the files on PC1 are changed, even the fold is read only! aaa.bmp can not be recognized as BMP file, and the content of 123.txt which should be "123" also can not be recognized. It seems that when I crypt the data and copy it back to NBL, I also change the content of the file(or the content in memory, because after I reboot, the files are be OK). But I think that the NBL which my miniport get from the protocol driver should can be modified, it should not changed the content of any file or other things. Sorry for my poor English. -- Arthur Tu best regards Tag: Why Driver Entry called two times in the Mux Sample Tag: 95417
  - 16
    - Does devcon.exe work at all? I am trying to use devcon.exe to ease the pain of repetitively re- installing a device driver under development for test & debug purposes. The device driver I am developing is based on MSVA (i.e. has no real hardware). When I attemp invoking it like this: devcon.exe update msvad.inf I get the error message: "devcon.exe: Invalid use of update." It seems that it also requires hwid as the second parameter? So I typed: devcon.exe hwids * but all I get is: "No matching devices found." What could be not matching in the wild card * ????????? What does devcon.exe do? Does it work at all? Or am I so sleepless and tired that I can't even get a clue how to use a simple tool like this? Thanks, Don P.S. If there is another way to re-install a driver (specified by .inf and a path to the actual location of the .sys driver file) without the annoying required mouse clicking on the update driver wizard, I would appreciate describing it here. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95415
  - 17
    - Spooler does not inform the Port Monitor about errors I have compiled the XPSDrv demo targeting Windows Vista and run it on Windows XP. It fails printing some documents causing the applicaitons to hang when some standard print ports are used. I'm writing a custom print monitor grounding on the DDK example. Both the redmon and my monitor receive a premature EndDoc -- after a single 22-byte write is made. The following error is recorded in the System Event Log: " The document Microsoft Word - XPSDrv_Config-1.doc owned by valentin failed to print on printer XPSDrv Sample Driver. Data type: RAW. Size of the spool file in bytes: 405633. Number of bytes printed: 65577. Total number of pages in the document: 11. Number of pages printed: 0. Client machine: \\MERCURY. Win32 error code returned by the print processor: 2147549183 (0x8000ffff). " The same problem is observed when using RedMon -- it starts your application and delivers only 22 first bytes to it. There is no way to inform the application about failure since the monitor is not aware of it itself. I was trying getting error flag from job status retreived via GetJob in the EndDoc of my monitor -- The status is PRINTING for normally finished jobs and is additionally SPOOLING for the troublesome jobs. But but no error observed. Furthermore, I have also noticed that XPSDrv does not notify the printqueue. I have a monitor application, which logs all the activity in a printer's queue but it is silent on the XPS sample driver regardless of whether the job is printed sucessfully or fails. But that is another story. I'm sure that 1) XPSDrv must be repaired; and 2) threads must fail fast. The latter means that you should stop a task once one of it steps (which likely is a preconditioin for the subsequent stages) fails. I see no reason to invoke further processing from the monitor when printing fails and the output is incomplete, therefore. Thanks Tag: Why Driver Entry called two times in the Mux Sample Tag: 95414
  - 18
    - Device Setup Class Question Dear All, We're developing a scientific instrument which communicates via USB to transfer experimental procedures from the PC and stored results to the PC. Can anyone advise on what Device Setup Class this should go into? I can't see one but creating a custom setup class seems a like a big step for this one product (all the others are major groups of devices) We are using the Jungo system to do the comms, so we don't have a separate driver as such, just an inf file to tell Windows to use the Jungo driver when our instrument is connected. The instrument uses interrupt-mode transfers only. Thanks for your help. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95412
  - 19
    - Is there a MS approved general purpose USB driver ? Hello MS team and group members, I'm searching for a general purpose USB driver approved (aka signed ) by MS that is available in Vista and/or XP and allows simple raw transfers to/from device endpoints, mainly bulk and control transfers but iso will be a nice addition. Is there such a beast included with ddk/sdk or I have to do it the hard way ? Best regards, Mircea CIocan Tag: Why Driver Entry called two times in the Mux Sample Tag: 95410
  - 20
    - composite device behavior of UVC device on Win98/ME/2000/XP? I found UVC device would be a multi-interface USB device. For example, interface 0 is for video control interface and interface 1 is for video stream interface. As I konw, multi-interface device will display composite device first, and then find driver for each interface. However, it seems that XP SP2 only query driver for interface 0 of UVC device after display composite device. It doesn't query driver for interface 1 of UVC device. If I plug in UVC device on WinME, it will query driver for interface 0 and 1 of UVC device after display composite device. If I plug in UVC device onWin2000, it doesn't display composite device. Why doesn't Win2000 find composite device first for UVC device? I think the behavior difference is a serious problem for developing UVC driver on these OS. For example, do I need to write different driver for each interface of UVC device on WinME? Do I need to handle multi-interface in one driver on Win2000? Best Regards Jack Huang Tag: Why Driver Entry called two times in the Mux Sample Tag: 95400
  - 21
    - What's the best way to develop UVC driver for Win98/ME/2000? Our device follows UVC spec. Microsoft provides standard driver usbvideo.sys for UVC device on Win XP SP2 or later I would develop the UVC driver for older OS such as Win98/ME/2000. USB Camera driver can be developed based on AVStream or USBCamd model. As I know, usbvideo.sys is a AVStream driver. AVStream driver needs new DirectX is insatalled. I am not sure whether this would be a issue for users of legacy OS. We already have developed the camera driver based on USBCAMD model for other PCam devices. I hope we can develop UVC driver based on our current driver. But I don't know whether any driver architecture limitation exists on USBCAMD model. Could anyone give me a suggestion? Best Regards Jack Huang Tag: Why Driver Entry called two times in the Mux Sample Tag: 95399
  - 22
    - Debugging for beginners I have just started to learn Video Capture device development. I have built and installed the testcap sample that comes with the DDK. It have tested it using AMCap and I can see the pretty test pattern (thanks Microsoft). My next step is to understand how the driver works. To do this, I would like to step-by-step the driver through a debugger. However, I am unsure how to attach the debugger to the driver - I knew when I was working with a WIA device I had to debug the WIA service. Does WDM work similarly? Or should I be attaching to AMCap? Is it possible to debug the driver on the same machine as it is running on - or do I need two computers connected by a cable? Any guidance on the simplest approach would be much appreciated. Tag: Why Driver Entry called two times in the Mux Sample Tag: 95389
  - 23
    - Software Publishing Certificate Certificate Authority You document KMCS_Walkthrough.doc says to purchase a â??Software Publisher Certificate from a commercial CA.â?? And â??For a list of SPC CAs, see â??Resourcesâ?? at the end of this paper.â?? There is no list of CAs in the Resources at the end of the paper. Later on your document says to go to http://www.microsoft.com/whdc/winlogo/drvsign/crosscert.mspx â??This Web page includes: â?¢ A list of Root Authority cross-certificates. â?¢ A list of CAs that provide SPCs for kernel-mode code signing.â?? But again there is no list of CAs, but I will assume that the companies in the Cross-Certificate List are included in the CA list. I then picked VeriSign to investigate purchasing a â??Software Publisher Certificateâ??. But I cannot find this certificate available from this source. Why is this so hard? Please, tell me specifically what â??certificateâ?? or whatever to purchase in order to sign kernel mode drivers. On one of the examples in the document it says, â??Issued by: VeriSign Class 3 Code Signingâ??. So I went to VeriSign but the only information I could find says that this is for object signing for Internet Explorer, etc. Why is this so hard? Does VeriSign sell what I need or do I have to look elsewhere? Where should I look and what should I buy? The only mention of Digital Signing and Microsoft talks about Microsoft Authenticode to sign .exe, .cab, .dll, and .ocx. But, I want to sign a kernel mode driver. Is this the certificate or is there some other certificate? Why is this so hard? Also is there an updated document and web page that has correct information? Tag: Why Driver Entry called two times in the Mux Sample Tag: 95388
  - 24
    - How to share a common file in 2 different inf set? Hi, Based on the INF copyfiles directive describe in the link below, it seems that for files that is shared between 2 different inf driver sets, there is no way to ensure that the latest version of the file gets retain in the system since the COPYFLG_OVERWRITE_OLDER_ONLY flag is ignored by digitally signed sets. http://msdn2.microsoft.com/en-us/library/ms794560.aspx Does anyone knows of any way to safely share a common file between 2 different inf driver set, such that one can always ensure that the newest version of the file always gets retained by the system, no matter what the order of installation was? Or is it not possible to share a common file between 2 inf driver set that is digitally signed? Thanks KS Tag: Why Driver Entry called two times in the Mux Sample Tag: 95382
  - 25
    - RSS on windows Vista and IM driver Hi , I am working on IM driver. My IM driver creates ARP requests,If the underlying miniport driver (this IM driver bound to) supports receive side scaling , what additional steps IM driver should take before sending the packet and after receiving the packet ? Thanks Tag: Why Driver Entry called two times in the Mux Sample Tag: 95381

Hi all,

It looks like the driver entry for the Mux Sample is called two times.
Could anyone let me know why is this.

This is the DebugPrint log

00000308
3.90667701 ----------------------------------------------------------
Inside Driver Entry:::
00000309 3.90668583 ........................Registry is jj??\REGISTRY
\MACHINE\SYSTEM\ControlSet001\Services\MUXMP
00000310 3.90669179 .....................The driver object address
DriverObj 88256A48
00000311 3.90670681 ................................... about to
return from driver entry+++
00000312 3.90701342 MUX-IM:
00000313 3.90701771 ==> MPUnload: DriverObj 88256A48
00000314 3.90704489 MUX-IM:
00000315 3.90704775 <== MPUnload
00000316
4.53355837 ----------------------------------------------------------
Inside Driver Entry:::
00000317 4.53356695 ........................Registry is jj<?\REGISTRY
\MACHINE\SYSTEM\ControlSet001\Services\MUXMP
00000318 4.53357267 .....................The driver object address
DriverObj 88256A48
00000319 4.53358698 ................................... about to
return from driver entry+++

Also why is the Unload called only once. This unload is the one
registered using the NdisMRegisterUnloadHandler(NdisWrapperHandle,
MPUnload);

Regards,
NHKR

Top

Re: Why Driver Entry called two times in the Mux Sample by Tim

Tim
Thu Jun 07 02:40:40 CDT 2007

narsha@gmail.com wrote:
>
>It looks like the driver entry for the Mux Sample is called two times.
>Could anyone let me know why is this.
>...
>Also why is the Unload called only once. This unload is the one
>registered using the NdisMRegisterUnloadHandler(NdisWrapperHandle,
>MPUnload);

I can't answer why (how did you launch this?), but why is this a concern?
It is loaded, it is unloaded, it is loaded again. If your driver cannot
handle this, it is hopelessly broken.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

Top