editbin on x64 driver

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
    - virtual com driver Hi all, I am new to driver development. i need to perform a task where in, i need to divert the SPOOL data of the complete system( i.e., all the print tasks of the systems) to USB port to which printer is connected. Tag: editbin on x64 driver Tag: 85195
  - 2
    - About Chelsio Communications Chelsio Technical Overview Chelsio Communications is the market and technology leader for 10 Gigabit Ethernet adapters. Chelsio's board-level products employ the company's unique ICs that process compute-intensive communications protocols at 10Gbps rates. Unburdened of this communications-processing overhead, host servers and storage systems that use Chelsio adapters dramatically increase both applications performance, and communications bandwidth. =E2=96=BA Chelsio products accelerate network performance in enterprise data centers, high performance cluster computing (HPCC), enterprise-wide data storage systems, and post-production shops for digital film and video. Chelsio is a privately-held subsystems company in Sunnyvale, California. The technology we work are: TCP Offload Engine (TOE) 10-Gbit/s iSCSI SAN RDMA (InfiniBand) =E2=96=BA Chelsio=E2=80=99s flagship board-level protocol engine is the wor= ld=E2=80=99s best performing 10GbE adapter. =E2=96=BA It employs Chelsio=E2=80=99s unique Terminator ASIC that processes TCP=E2=80=9DIP, iSCSI, and other upper-layer protocols =E2=80=93 unburdenin= g the host-system=E2=80=99s CPU of these tasks. =E2=96=BA Unlike competitive solutions that tax the host-system CPU to process these protocols, Chelsio=E2=80=99s TCP Offload Engine (TOE) technology dramatically increase the host-system=E2=80=99s CPU performance, as well as it=E2=80=99s network bandwidth. =E2=96=BA To learn more about TOE: http://www.chelsio.com/solutions/pdf/Chelsio_TOE_Value_Prop.pdf http://www.dell.com/downloads/global/power/1q04-her.pdf =E2=96=BA Here is the link to iSCSI documents: http://www.snia.org/tech_activities/ip_storage/iSCSI_Technical_whitepaper.P= DF =E2=96=BA RDMA and InfiniBand documents are available here: http://www.infinibandta.org/home www.intel.com/technology/infiniband/=20 Regards=20 Kurian Tag: editbin on x64 driver Tag: 85194
  - 3
    - unresolved external symbol _MEDIASUBTYPE_RGB32 Hi All, I am writinga media (Camera streaming) driver. The driver works fine on WinXP but I can't build it for Win2000. It encounters this error, unresolved external symbol _MEDIASUBTYPE_RGB32. I was unable to find the lib which exports this symbol. Using the XP driver on WIn2000 leads to the crash of System.I know strmiids.lib exports this symbol in WinXP DDK. Has someone encountered this problem earlier? How to overcome it? Please help Tag: editbin on x64 driver Tag: 85193
  - 4
    - Windows Device Driver Developer--Chelsio Communications Dear All, we have a requirement of Windows Device Driver Developer for Chelsio Communications (www.chelsio.com). So if anybody looking out for a chage then kindly please forward your cv to kurian.thomas@in.ness.com or call me@9845775441. Please find the details below Technical architect/ lead - Windows - NDIS/Chimney/iSCSI - 1 L, 1 D Responsibilities: The Windows Driver Developer will play a technical leadership role in Chelsio's effort to develop a set of device drivers for the Windows OS family. Responsibilities include full design and implementation of one or more drivers, including the NDIS 1G/10G Ethernet drivers, and the drivers for both the TCP Chimney and the RDMA Chimney standard and or iSCSI. The position will be involved in all phases of the development process, including: requirement analysis, developing and writing of design specifications and test plans, coding, testing, performance evaluation, and troubleshooting. The ideal candidate will have experience developing at least one NDIS driver, must have delivered a Windows SW product into production, and must have the ability to quickly analyze complex problems, propose efficient solutions, articulate his/her thoughts clearly and concisely, and be able to follow through with the implementation and testing. Requirements: 6-10 years of experience in developing Windows device drivers and excellent knowledge of C/C++ and the Windows OS family (Windows NT and Windows NT server in particular). Knowledge of and experience with the TCP/IP protocol and socket programming, L2 and L3 Internet protocols, and device driver performance tuning are a must. A basic understanding of the TCP Chimney and RDMA Chimney standards and understanding of SAN, FC and/or iSCSI technologies are desirable. Familiarity with the RDMAC protocol suite highly desirable, and knowledge of Linux and Linux device driver development is preferred but not an absolute must. Excellent verbal and written communication skills are required. Regards Kurian Tag: editbin on x64 driver Tag: 85178
  - 5
    - SCardControl output buffer size While sending an control code using SCardControl if we mention the output buffer size less than 108 the value is automatically set to 108 by the resource manager. If we mention any value above 108 it is not altered. Is there any reason behind this ? Tag: editbin on x64 driver Tag: 85176
  - 6
    - fyi: WDM to KMDF Porting Guide http://www.microsoft.com/whdc/driver/wdf/WDF_Port.mspx -Eliyas Tag: editbin on x64 driver Tag: 85173
  - 7
    - MS UVC driver question Hi all, Have a question for the UVC uncompressed format support issue? According to the UVC spec, the NV12 are supportted, but when my HW output the YUV420 format data, amcap reports failure to connect the graph, event in the GraphEdit, there is no proper filter to transform this format for redering. If output YUY2 format, there is no such issue. Anyone knows if MS UVC driver support NV12 format? Best regards. Tag: editbin on x64 driver Tag: 85166
  - 8
    - Can I get the driver's INF file path from its Device ID? Hi all, Does anyone know if I can get the path to a device driver's INF file in the driver store by just knowing its Device ID? I've been poking around in the SetupDi API and am not sure if I'm seeing something usualable for this. Thanks, -MH Tag: editbin on x64 driver Tag: 85162
  - 9
    - network redirector Can anybody help me as i m going to implement Network redirctor for NFS_client(Windows) n NFS_Server(Linux) as for now plz help if U have any example of it...is the Undocumented DOS(BOOK) will be really useful in this context Can anybody tell me how to go for it.... how RDBSS will come in this whole context......will it come whn the data is going to filter driver of I/O Manger Tag: editbin on x64 driver Tag: 85146
  - 10
    - Obtaining Driver handle in Vista using CreateFile() Folks, I am having trouble obtaining a handle to a WDF driver using CreateFile(DosDeviceName, other parameters) in Vista. My driver is a software only driver and with some help from Chkinf was able to muck around with my inf file to get the driver successfully install (I make this statement based on the fact that the setupact.log in the windows folder doesn't have any errors related to this particular driver listed and there are no bangs or questions marks next to my driver in Device Manager). Initially the chkinf complained about not recognizing the GUID and I had to use the class Name 'System' and the associated GUID to make chkinf happy and eventually Vista happy. Therefore my driver ended up under the 'System Devices' tree. Now when I try to open a handle to this driver using the Symbolic link name I am failing. Before this my driver was under the class name 'Test Tools' with some other GUID and WinXP 32 and 64 bit didn't have any problems with it. Has anyone seen this before and point me towards the solution. Thanks! Ram Driver Developer Tag: editbin on x64 driver Tag: 85142
  - 11
    - HID in a composite device configuration Should HID polling by IN command be blocked by MSC polling IN command more than 10 seconds if these 2 devices are in a composite device configuration? What could we be doing that would irritate Windows in such a way that it would be causing this to hang? We are currently compliant with HID v. 1.0 Draft #4 Compliance http://www.microsoft.com/whdc/archive/hid4.mspx. Our implementation of this compliance uses endpoint 2 which we also use for the IN command instead of end point zero. Tag: editbin on x64 driver Tag: 85138
  - 12
    - problem code 31 when I install NDIS 6 I transfer NDIS 5 to NDIS 6 of miniport driver for my company NIC. I met a problem when I install NDIS driver in Vista. The message showed in device manager is "Window was able to sucessfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 31" I dump the message in WinDbg and found NDIS didn't call Driver InitializeHandlerEx. I checked the status form NdisMRegisterMiniportDriver was sucess. I don't know why NDIS didn't call InitializeHandlerEx. My Vista version is beta #2, Build 5472 Tag: editbin on x64 driver Tag: 85133
  - 13
    - Protocol driver under Windows Vista RC1 Hello, I'm actually testing an application under windows vista RC1. This application uses a protocol driver bound to all ethernet adapters. One of the the application job is to analyse packets coming from ethernet adapters. To do this, i set the adapter filter options ( OID_GEN_CURRENT_PACKET_FILTER) to: NDIS_PACKET_TYPE_DIRECTED + NDIS_PACKET_TYPE_BROADCAST+ NDIS_PACKET_TYPE_ALL_LOCAL . This works well under Windows XP, then i tested under Windows Vista Beta 2, it was fine too. But the tests under the last windows vista failed : i canot receive paquets from the local adapters , only the paquets from other computers are received by the application ( and so by the protocol driver). Are there some specification changes in this new version ? Thanks in advance, Jose Tag: editbin on x64 driver Tag: 85130
  - 14
    - Need to install usbser.sys on my debug target Hi all, I need to install usbser.sys on my debug driver target. The usbser.sys file is distributed with SP2 and my target which is Windows 2003 Server (dbg build) is not allowed to be connected to the internet for 'patching' (only connected to my host by TP and debug cable). The usbser.sys file I can copy from my development computer (debug host) but I don't have the *.inf file for usbser.sys. Anyone that knows how I should design the inf file for usbser.sys or is there one available somewere. Thanks in advance, Lars-Åke Berg Tag: editbin on x64 driver Tag: 85122
  - 15
    - infiniband driver problem we have bought MHES14-XTC modeled InfiniHost III LX infiniband device... www.mellanox.com provides a driver called WinIB we have donwloaded it and installed it... Installation is successful but after restart windows says that unable to load driver... code 31 here is a part from ReadMe of the driver; here it says ur dr IB HCA must be one of the following but our card is not one of the them. I am not able to learn firmware version of the card... And also we use 32bit windows on x64 architecture... I installed 32bit driver Which is the main problem 32-64 ? or Device not supported? -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 3. HW and SW Requirements: ========================== 1) One of the following InfiniBand HCA (Host Channel Adapter) Cards installed on the system: - MHX-CExxx-T Cougar (previously MTPB23108) - MHXL-CFxxx-T Cougar Cub (previously MTLP23108) - MHEL-CFxxx-T Lion Cub (previously MTLP25208) *** Important Note: *** Your HCA card must have a firmware version: - 3.3.2 or later for an MHX-CExxx-T or MHXL-CFxxx-T - 4.6.2 or later for an MHEL-CFxxx-T For FW update: a. Download the latest firmware from http://www.mellanox.com/products/firmware.html b. Use the flint tool of WinMFT (Windows Mellanox Firmware Tools) package (separate MSI package). For further assistance, please contact your local FAE. 2) Windows XP SP2 (x86, x64) Windows Server 2003 SP1 (x86, x64) Windows Server 2003 CCS beta-1 Edition (x64) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Tag: editbin on x64 driver Tag: 85113
  - 16
    - Command 53 for SDIO Wi-Fi card Hi, I am currently working on writing a SDIO Wi-fi device driver on WinE 5.0. When I send CMD53 to the card I always get a Write CRC error. What might be the issue? There are a lot of CMD52 before this CMD53 which run successfully but once CMD53 is sent to the card I get an error. One more thing, when I send CMD53 how will the data be written to the SDIO card? How does the Bus Driver send us the data to be written in this case? Also the specs say that the data from the Dat[x] lines will be written to the card in this case. But who will put the data on the DAT[x] lines for the card? Also the spec says that the data from the DAT[x] lines will be written to the card. Who will put this data on the DAT[x] lines for the card in this case? Regards, Varun Tag: editbin on x64 driver Tag: 85112
  - 17
    - Virtual Driver Hello All, I want to write a Virtual COM driver which collects all the COM data and sent it through USB. I want to select this port in "Ports" tab which would installed from Add Printer. Can anyone let me how to start developing the driver. Is there any sample available to start with? Thanks and Regards, James Tag: editbin on x64 driver Tag: 85108
  - 18
    - wifi sample driver code Hi I am new in miniport driver. Is Anywhere sample source code for wifi card available ? I read in msdn different type of NICs e.g. Bus-master DMA NICs and Nonbusmaster DMA NICs . For knowning type of NIC and other details, Should I contact with card manufacturer? Please shom some way. -- With regards thanks Anand Choubey Tag: editbin on x64 driver Tag: 85107
  - 19
    - kbfiltr question How do I get the DeviceID (which keyboard) from inside the kbfiltr driver? I am connecting multiple keyboard devices (USB barcode scanners), and installing a kbfiltr driver to intercept the input, which works great. Now I want to be able to tell which keyboard each keystroke is coming from. I get a UnitID from InputDataStart but this number changes every time I plug and unplug the usb keyboard (this number also resets on reboot). I need something more like the InstanceID that is unique for identical devices (same make/model device) and does not change when you plug and unplug it. NOTE: I understand the Instance ID changes if you plug the keyboard into a different USB port, I am not worried about this case, but plugging and unplugging from the SAME port does not change the InstanceID. I am an experienced c# programmer, but am very new to C and device drivers. I have read through ~90% of the DDK, but am still unsure how to move forward. Any help would be appreciated. -Steven (Louis) Tag: editbin on x64 driver Tag: 85106
  - 20
    - Logical bug in NTFS - modification date is not set when stream is deleted It seems that somehow the interest in NTFS related questions is low. But I have further observations that I would like to share with you. In NTFS every file can have streams. Lets take the stream "\005SummaryInformation" which is used to save the Summary Information visible in the properties of a file. If you add this stream by entering a comment in the properties the modification date of the file changes. Every further modification to the summary stream will change the modification date too. But if you simply delete the associated stream with DeleteFile the modification date is not changed to reflect this operation: DeleteFileW(L"c:\\file.txt:\005SummaryInformation"); This is a logical NTFS bug for me. Best regards, Holger Tag: editbin on x64 driver Tag: 85104
  - 21
    - How to dynamically load a filter driver? I've written a filter driver for disk volumes. However, to enable it towork, I have to reboot the system. Is there any way to load the driver without rebooting? And I am using AddDevice routine. I first dried to install the driver, it is OK. Then I added it to one volume's device key as UpperFilters. When restarting the volume device, I found that the DriverEntry routine is called and executed successfully. But after leaving DriverEntry routine, there is something wrong and Unload routine is executed. At last, the drive did not get loaded. However, if I reboot the system just after installing the driver, all is OK. What's the difference between starting by system at boot time and starting by IO manager at run time? I'm quite puzzled. Tag: editbin on x64 driver Tag: 85101
  - 22
    - IoFreeWorkItem and return function. Hi all, I am new to device driver development and need an advice. I issue a callback using this IoQueueWorkItem funciton. In my callback function, I have following code: void callback_function(....) { ... if (status) { IoFreeWorkItem(...); return; } .... IoFreeWorkItem; } For the above simple IoFreeWorkItem, do I need to have a return in the if statement? Thanks. HS Phuah Tag: editbin on x64 driver Tag: 85088
  - 23
    - how to exclusively hold an U audio channel. We are using our own USB audio device named "USB audio device" for specific application. But if a skype call or a IM call or others could mix audio signal and send to that device and make things wrong. How can we exclusively own that device. Do we have to do this at device level? The best is at application level we can do some things. Thanks in advance! Tag: editbin on x64 driver Tag: 85086
  - 24
    - Installing a lower filter driver Hello, I am wondering if there is an easy way to install a lower filter driver. I would like to implement the functionality myself. I looked through the source code of DevCon in the windows DDK, but I was a bit confused about the concept of MSG's that the code uses. I would like to be able to install the Lower Filter driver as well as delete it. Also, I am wondering if using a .inf file is required? Someone mentioned to me that it is required so that the OS knows where to hook it up in the device stack. I have the binary, and I would prefer not to use the inf, but if I have no choice, than i guess it's okay. A while back, I had to install an upper filter driver, and that was relatively easy. I just used the service control manager and called OpenService, CreateService etc. Is there something similar to this? Thank you in advance for your help. Tag: editbin on x64 driver Tag: 85085
  - 25
    - XP x64 deadlock issue with KiInterruptDispatch This issue is probably related to a prior microsoft.public.development.device.drivers post "64-bit system hang in KiInterruptDispatch", and it looks to be fixed in Windows Vista x64 (tested with RC1). I would like to know where I can find the hotfix for my customers. Thank you! The issue: On Windows XP for 32-bit x86 (halmacpi,ntkrnlmp), KiInterruptDispatch raises the IRQL to "SynchronizeIrql" (from IoConnectInterrupt) before acquiring the SpinLock (ActualLock) and calling the ServiceRoutine. However on Windows XP x64, KiInterruptDispatch seems to be raising IRQL to "Irql" instead of "SynchronizeIrql" (from IoConnectInterrupt). Why is this a problem? Let us imagine that I have a device (AT-DIO-32F) with multiple interrupts assigned, "X" and "Y". Lucky us, interrupt "X" is not used by any other devices in the system and is assigned IRQL 5. Interrupt "Y", however, _is_ shared with other devices in the system and is assigned IRQL 10. I create 1 spinlock to protect access to device registers and variables from within the interrupt service routine for this device. Next a call is made to IoConnectInterrupt() for each assigned interrupt, where the SynchronizeIrql is set to 10 and the same ServiceRoutine and SpinLock are used for both calls. The problematic scenario: Interrupt "X" fires. KiInterruptDispatch on raises IRQL to 5 (not 10) and grabs the shared spinlock. During the ServiceRoutine, interrupt "Y" fires. Because "Y" is at IRQL 10, and the current IRQL is 5, it preempts the current execution. Because "Y" is a shared interrupt, KiChainedDispatch is called. KiChainedDispatch walks the list of _KINTERRUPT objects at IRQL "Irql", raises the IRQL to "SynchronizeIrql" temporarily if it is higher than the current IRQL, grabs their SpinLock, and calls their ServiceRoutines. When it encounters the SpinLock (ActualLock) for my device, there is a problem because this CPU is already holding the spinlock at the lower IRQL, so the system hangs. Stack: nt!KiScanInterruptObjectList+0x72 (trying to grab my spinlock, again) nt!KiChainedDispatch+0xd7 MyDriver!MyServiceRoutine+MyOffset nt!KiInterruptDispatch+0x138 (holding my spinlock at Irql, not SynchronizeIrql) On Windows XP x86, things have run great for years. Also, Vista x86 and x64 (RC1) both seem to operate fine, though my testing there hasn't been comprehensive -- just a quick test followed by some WinDBG disassembly to confirm that it is fixed. I have not evaluated Server 2003. I hope that saves the rest of you a man day or two. -- Jeremiah National Instruments -- http://www.ni.com "stack smasher" djajadi tribute. Tag: editbin on x64 driver Tag: 85083
- Next
  - 1
    - maximum driver handles per process? Is there a limit to the number of driver handles (one per thread) I can open from a given process? I'm using Win2k, WinXP, Win03. I remember seeing a KB article about a crash in Win2k that occures if you open too many handles to a driver. (Anyone got a source on that?) I have a project currently being tested on Win03 that causes some strange crashes. When running with five open handles it works just fine. If I bump that up to 10, the entire system goes unstable. I just want to know for sure that it is (a beast of a) bug in my code. Tag: editbin on x64 driver Tag: 85077
  - 2
    - maximum driver handles per process? Is there a limit to the number of driver handles (one per thread) I can open from a given process? I'm using Win2k, WinXP, Win03. I remember seeing a KB article about a crash in Win2k that occures if you open too many handles to a driver. (Anyone got a source on that?) I have a project currently being tested on Win03 that causes some strange crashes. When running with five open handles it works just fine. If I bump that up to 10, the entire system goes unstable. I just want to know for sure that it is (a beast of a) bug in my code. Tag: editbin on x64 driver Tag: 85076
  - 3
    - AVStream pin custom interface Hello, All. Please help me to find a way to implement custom COM interface for AVStream filter's pin. I want use this interface in my application to control some features of filter's pin. In steaming minidrivers architecture there was a way to cause ksproxy to load a COM server when my pin was created. It was performed declaring "HKR,PinFactory\0\Interfaces\...." in the driver's INF file. Does there is possibility to implement something similar in AVStream? Andrey Tag: editbin on x64 driver Tag: 85069
  - 4
    - CopyFiles section [iAlmCoInst.CopyFiles] iAlmCoIn_v4299.dll,iAlmCoIn.dll,,0x00000010 I have the following CopyFiles directive in an INF file. Can someone tell me if the line in question is renaming the file to be copied? Is iAlmCoIn.dll being renamed to iAlmCoIn_v4299.dll when it is being copied onto the target machine? Thanks for your consideration, JW Tag: editbin on x64 driver Tag: 85068
  - 5
    - SD card driver development in WinCE Hi, I am developing SD card driver for the ARM926EJS processor in winCE 5.0 here i am developing the client driver as a block driver. can i consider this as an ATA type driver? whether I have to develop the host controller driver and the bus driver or not? thanks, seshu Tag: editbin on x64 driver Tag: 85056
  - 6
    - BusRelations and IoAttachDeviceToDeviceStack Do PDO's created upon IRP_MN_QUERY_DEVICE_RELATIONS with BusRelations requests need to be attached to the underlying FDO using IoAttachDeviceToDeviceStack? Or is the underlying FDO meant to be the top of its stack? thanks. Tag: editbin on x64 driver Tag: 85049
  - 7
    - Problems with uninstalling drivers in Vista Hi, I have also the same problem as Venkat, who wrote on May 27 2006. Environment: Vista Ultimate Pre-RC1, build 5536, August 2006. Background: I'm trying to uninstall a pnp network unsigned driver stack using DifxApp 2.01 and have following error: DIFXAPP: ERROR - Unable to retrieve the driver store handle corresponding to componentId '{84BE9411-41F9-44DA-840C-F42DD8EA25E1}' DIFXAPP: UninstallDriverPackages failed with error 0x643 Install happens fine. I can install/uninstall the same software to Windows XP Professional/Home, to Windows 64 bit and to Windows 2000 and everything happens just fine. Venkat: Do you already have some workaround or really solution for this problem? I read from somewhere that I should use DifxApp 2.10 for installing or uninstalling drivers in Vista. Is this true? Tag: editbin on x64 driver Tag: 85038
  - 8
    - USB2.0 descriptor issue for the full speed Hi all, I want to prepare a USB2.0 webcam driver which is planed to pass WHQL. Although it works well, but it fails USB CV test items about device qualifier and other speed descriptor. Now I have a question for the full speed descriptor and high spees descriptor. How to provide the full speed configure descriptor ? It is declared in the seperate descriptors or in the device qualifier decriptors and other speed descriptors? Does the high speed device qualifier and other speed descriptor need be declared in the full speed USB descriptor? Thanks in advance! Lily Tag: editbin on x64 driver Tag: 85032
  - 9
    - Which is the best way for KM-UM interaction Hi all, In my project i am trying to measure performance of a PCIe Core. For that, in the driver the 8kb Core RAM is written and read through DMA. The data is written from appln to driver continuously and then DMA is done and the same data is read back in the application. Could you pls suggest which is best way for interaction and synchronisation betn appln and driver. Presently I am trying with shared mem using zwcreatesection and createfilemapping of 8kb. Can i also use IOCTLs or other routines. And how do i synchronise as appln should wait writing, till driver does dma to read and write to the core, and then appln read should happen, then again write and so on. Tag: editbin on x64 driver Tag: 85030
  - 10
    - Getting Kernel Shared section object name in Appln Hi , I need to allocate memory in kernel mode , fill it and then user mode application has to read from it. I have created a named section object in kernel space with the name "\\device\\sharedmemory" using ZwCreateSection function. But the problem is when I use the function "CreateFileMapping", with "\\device\\sharedmemory" as its last argument, in user mode application , it fails to open the section object already created in the kernel mode. If I give different name than "\\device\\sharedmemory" in ZwCreateSection in kernel mode driver, then ZwCreateSection function fails. I am not able to figure out the problem . How to access the kernel mode memory from user mode. Please help. Thanking You Tag: editbin on x64 driver Tag: 85029
  - 11
    - Device Instace ID Is the device instance ID extracted from the firmware of the device? I see that it often matches the HWID but not always. I don't see a specific INF directive that corresponds to the device ID so I'm wondering if that comes directly from the device hardware itself. JW Tag: editbin on x64 driver Tag: 85022
  - 12
    - Including <ntstrsafe.h> won't work with DRIVER_TYPE=WDM When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't find <ntstrsafe.h> any more. I suspect DRIVER_TYPE mess with the include directories so my question is : Should I manually add the missing include path or simply drop the DRIVER_TYPE option ? What is its purpose anyway ? Thanks for your time. Tag: editbin on x64 driver Tag: 85019
  - 13
    - Where did drvindex.inf go in Vista? Looking at Vista Beta 2. I can't find drvindex.inf in the inf folder. Nor can I find Driver Cache\i386\ Where did they go? (I need them to extract the UniDrv core files if they aren't already on the system). Colin Tag: editbin on x64 driver Tag: 85017
  - 14
    - sys file protector/encryptor PE encryptors are well known. Each driver can be easily reversed using for instnace IDA. Are there any windows driver file protectors? Matt Tag: editbin on x64 driver Tag: 85015
  - 15
    - obtaining CPU usage Hello! Is it possible to obtain CPU usage by DDK API? Any suggestions how can I do so in driver mode? Thanks, Matt Tag: editbin on x64 driver Tag: 85009
  - 16
    - Probelms with Vista RC1 Check Build Install I'm installing Vista RC1 checked on a dual-boot system. I've previously installed the free build of RC1 on this machine and everything went well. However, installing the checked built results in a frozen system. I've rebooted and gone back to the XP partition, formatted the Vista partition and tried to install the checked build twice now and the same thing happens. Does anyone know what is happening? Thanks! Tag: editbin on x64 driver Tag: 84979
  - 17
    - Debugging NWF In Vista I'm running into a problem with my NWF driver under Vista RC1 (build 5600). This driver is for an 11n chipset and I see the following happen when the driver associates with an 11n AP: 1. The STA associates and gets an IP address. 2. If I start a ping to the gateway, the STA sends out an ARP request and the gateway sends back an ARP response. The driver then indicates the ARP response to NDIS, but the NBF is rejected for some reason. I don't see this behavior when the STA associates with an 802.11 b/g AP. I'm trying to install the checked build of 5600, but that's not going smoothly. All the same, is there any way to enable debug trace options in the NWF system so that I can get feedback on what may be happening? Also, has anyone else seen this kind of problem before? Thanks! Tag: editbin on x64 driver Tag: 84978
  - 18
    - Proper notification/handling of KS format changes. Greetings, I have discovered a dangling pointer bug in my USB camera's UM proxy filter aggregated com object which has now raised in my mind a design question. The aggregated COM object (I'll call it the extension) provides an interface for setting various custom camera parameters to the associated Stream Class driver I have written. This interface is used by all property pages I provide for the camera and also by some custom applications we produce. Many of the parameters can change the format of the image stream. In order to be as friendly as possible, I have attempted to have the extension rebuild the filter graph when any of the format changing parameters is modified. The thinking here was that the extension, as the central object that sends IOCtrls to the KM driver, is in the best position to know which of the many parameters actually impact the image format and thus can reduce the number of times the graph needs to be rebuilt (and also reduce the amount of knowledge the caller must possess). The implementation was to derive my extension from IDistributorNotify in addition to my custom interface. In theory, this will let the extension know (via the NotifyGraphChange method) when the associated filter is added/removed from a graph, has its pins connected/unconnected, and when any other change to the graph happens. Thus in my NotifyGraphChange method, I call m_baseFilter->QueryFilterInfo(&fInf) on the camera's proxy filter and save the fInf.pGraph pointer (if it exists). Then when any relevant parameter is changed, say the X Dimension of the image, I can get the IGraphConfig from the graph and do a Reconnect. I am using the rather brute force method of Reconnect as it is my general understanding (and experience) that renegotiating a format after the initial pin connection is either not supported or completely broken depending on whether you are a Stream Class/AVStream driver and perhaps upon the Windows version. The trouble with this implementation seems to be that while NotifyGraphChange gets called in many of the listed instances, it does not get called when the filter is removed from the graph. Thus depending on the specifics of the graph manipulation, I sometimes end up with a call through an invalid m_graph pointer to Nowheresville with predictable results. While I am sure I can tiptoe around this issue by being a bit more clever (and correct for that matter) in my NotifyGraphChange analysis (for example I have observed that it is always called correctly on pin connect/disconnect and thus I could force my m_graph parameter to NULL then) I am wondering if I am really going about this in the right way. Perhaps the trouble is an abuse of IDistributorNotify. It occurred to me for example that there may be some completely different interface I have not stumbled across yet that sorts this. Or perhaps there is something that could be used from kernel mode that would be more robust (I thought there might be some standard EVENT that would do the trick for example). Is there a preferred technique for notifying a filter graph that the format has changed and the graph must be rebuilt? Or am I already on the right track? Best regards, Tom Udale Tag: editbin on x64 driver Tag: 84977
  - 19
    - any sample code for kernel file map ? I would like to use ZwCreateSecion() to map a large file in kernel, and access it as a mapped file. Anyone has sample code to demonstrate the process and parameters in each call ? Thanks -Gary Tag: editbin on x64 driver Tag: 84975
  - 20
    - SATA 1.0a? We have a legacy SATA tape drive that only supports SATA 1.0a. We heard there might be issues with Longhorn server if controller supports AHCI. Will Standard IDE mode (supports SATA 1.0a) still be supported for these controllers? Tag: editbin on x64 driver Tag: 84972
  - 21
    - srbExtension and PTE depletion Hi All, I'm chasing a driver bug and though you might be able to help me out. I have an LSI SCSI driver which allocates enough memory in the srbExtension to fit a whole filesystem cluster. With WinXPSP2 (SP1 doesn't do this), if I drag a folder with many (100,000) 128KB files onto a volume managed by this driver, the kernel loses Page Table Entries as the copy progresses. I can track this loss in perfmon by watching the Memory->Free System Page Table Entries counter. Lost PTEs are never recovered, and when the kernel gets down to about 4000, it's game over, and the OS throws an "Insufficient Resources Exist to Complete the Requested Service" dialog. I have a similar Adaptec driver which only allocates 4 bytes in the srbExtension, and it does not trigger PTE loss. Large NTFS cluster sizes exacerbate the behavior. I recently tested a Core 2 Duo laptop, and its internal SATA driver, as well as an eSATA ExpressCard both exhibit this behaviour, so it appears that drivers provoking this bug are becoming more widespread. Has anyone developing SCSI drivers seen this issue, or has anyone at MS filed a bug? If so, when can I hope for a fix? Thanks, David Tag: editbin on x64 driver Tag: 84953
  - 22
    - USB suspend issues I'm using the microchip custom firmware with my USB device and I'm having problems with the the computer constantly trying to suspend the device. It makes the device respond slowly and sporadically. When I uncheck the box "Allow the computer to turn this device off to save power" in the Power Management tab of the device in the device manager, the device works much better. Is there any way in the device descriptor or inf file to tell the computer it shouldn't be trying to shut this device down constantly? Or do I need to make a WMI call as part of the driver install to uncheck that check box? Any help is appreciated. Thanks, Clint Tag: editbin on x64 driver Tag: 84951
  - 23
    - PNP stop/remove and the current IRP When a device is either stopped or removed, shouldn't the current IRP for which there was I/O in progress be completed before finishing the stop/remove PNP request? When I look at the WDM book examples, I see the device's IRP queue being either stalled or aborted, but I'm unsure about the way the I/O in progress is handled. Both stop and remove look like they either wait for the current I/O to finish or cause the device hardware to abort it, but shouldn't they also complete the IRP associated with that I/O? (either with success in the stop/wait case or error in the remove/abort case) Tag: editbin on x64 driver Tag: 84950
  - 24
    - NdisQueryBufferSafe returns zero buffer length when NdisQueryPacket says there is more data MiniportSendPacket()... NdisQueryPacket says the total length is 142 say and the packet has 3 buffers. Buffer 1 is 14 length Buffer 2 is 20 length Buffer 3 is 0 length So the Ethernet and IP header are there, the payload is missing. The Packet type is ESP. A Nortel VPN client on the PC. If DNE is run on the PC, the third buffer has the correct length of 108. Any ideas on this? Tag: editbin on x64 driver Tag: 84939
  - 25
    - microsoft CCID & extended APDU I am currently writing firmware for a smartcard reader that should conform to the CCID USB protocol. The idea is that it should work with the Microsoft generic CCID driver usbccid.sys. Everything work as it should when sending & receiving short APDU's (256 bytes + 10 bytes CCID header). Sending extended APDUs to the reader (pc_to_rdr_xfr block) also works with sizes up to 0xffff (as specified in ISO7816). However when attempting to receive extended APDUs from the reader I get the following error: TransferFlags OUT, SHORT_TRANSFER_OK TransferBufferLength 269 bytes status: URB Status USBD_STATUS_BUFFER_OVERRUN TransferFlags IN, SHORT_TRANSFER_OK TransferBufferLength 256 bytes As far as I can see the driver doesn't allocate enough size in the receive buffer and the reader attempts to send more data than 256. Does anyone know the status of the Microsoft CCID driver and / or what can be done in order to use the extended APDU's in rdr_to_pc_xfr blocks ? The current CCID descriptor that we are using and the card ATR is as follows: static CCID_Desc CCID_desc[1] = { 0x36, 0x21, // Length, Type=CCID 0x01, 0x10, // CCID spec release number 0, // Max slot index 0x01, // 3V, 5V supported 0x02, 0x00, 0x00, 0x00, // dwProtocols = T=1 0xa0, 0x0f, 0x00, 0x00, // default clock frequency = 4000 kHz 0x4c, 0x1d, 0x00, 0x00, // max clock frequency = 7500 kHz 0x00, // no manual clock selection 0x01, 0x2a, 0x00, 0x00, // default data rate = 10.75 kbps 0x10, 0xb1, 0x03, 0x00, // max data rate = 241.9 kbps 0x00, // no manual speed setting 0xfe, 0x00, 0x00, 0x00, // max IFSD 0x00, 0x00, 0x00, 0x00, // dwSynchProtocols, not supported 0x00, 0x00, 0x00, 0x00, // dwMechanical, no special characteristics 0xba, 0x00, 0x04, 0x00, // dwFeautures - APDU level, automatic TA & freq settings 9a, 0x12, // dwMaxCCIDMessageLength 0x00, // 0x01, // 0x00, // 0x00, 0x00, // bClassGetResponse, bClassEnvelope 0x00, 0x00, // wLcdLayout = no LCD 0x00, // bPinSupport = No PIN 0x01, // bMaxCCIDBusySlots = 1 }; Card ATR uchar fakeATR[] = { 0x3b, // TS 0xb5, // T0 0x11, // TA1 0x00, // TB1 0x81, // TD1 0x31, // TD2 0x46, // TA3 0x15, // TB3 0x56, 0x20, 0x31, 0x2e, 0x30, //T1-T5 = "V 1.0" 0x1e}; // TCK Tag: editbin on x64 driver Tag: 84925

Moin,

I tried to re-calculate the driver image checksum with "editbin.exe /release
mydriver.sys" but get the "warning: LNK4048 invalid format file; ignored".
The DDK 3790 states that the file format of a x64 driver is PE32+.
Is there a version of editbin available which can handle this format ?

Best regards,
Stefan

Top

Re: editbin on x64 driver by David

David
Wed Sep 13 11:15:49 CDT 2006

Did you try the editbin.exe from Visual Studio 2005 in the correct
directory?

"Stefan de Buhr" <stefan@sdb-consulting.de_nospam> wrote in message
news:%23gCDUzy1GHA.4976@TK2MSFTNGP02.phx.gbl...
> Moin,
>
> I tried to re-calculate the driver image checksum with "editbin.exe
> /release mydriver.sys" but get the "warning: LNK4048 invalid format file;
> ignored".
> The DDK 3790 states that the file format of a x64 driver is PE32+.
> Is there a version of editbin available which can handle this format ?
>
> Best regards,
> Stefan
>

Top

Re: editbin on x64 driver by Stefan

Stefan
Thu Sep 14 07:17:45 CDT 2006

I copied editbin into an extra directory where I had an old mspdb41.dll.
editbin obviously used that old DLL and could of course not interpret PE32+.
Then I copied the newer mspdb80.dll and it worked.

-Stefan

"David J. Craig" <Dave@yoshimuni.com> wrote in message
news:OW%23rh$01GHA.3644@TK2MSFTNGP03.phx.gbl...
> Did you try the editbin.exe from Visual Studio 2005 in the correct
> directory?
>
> "Stefan de Buhr" <stefan@sdb-consulting.de_nospam> wrote in message
> news:%23gCDUzy1GHA.4976@TK2MSFTNGP02.phx.gbl...
>> Moin,
>>
>> I tried to re-calculate the driver image checksum with "editbin.exe
>> /release mydriver.sys" but get the "warning: LNK4048 invalid format
>> file; ignored".
>> The DDK 3790 states that the file format of a x64 driver is PE32+.
>> Is there a version of editbin available which can handle this format ?
>>
>> Best regards,
>> Stefan
>>
>
>

Top