What build target to use for Windows XP 64?

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
    - DIFx and virtual device drivers... I would like to use DIFx to install some virtual device drivers. Since these are virtual drivers I have to create the device instances manually. Is there a recommended way to do this with DIFx? DIFx appears to require a real device before it will create an instance. Is there a DIFx way to do this or should I use the SetupAPI and create the device? Robert Randall Tag: What build target to use for Windows XP 64? Tag: 91445
  - 2
    - How user mode drivers handle client application crash? Hello, I write a user mode USB driver which serves overlapped ReadFile requests from the client application. There will be exceptions in the driver when the client application crashes(or is closed by the Task Manager). Is there any special requirment for the user mode driver to handle this situation? BTW, I'm a newbie to the driver development. I'm using Vista and WDK. Thanks! zxli Tag: What build target to use for Windows XP 64? Tag: 91438
  - 3
    - Parallel Dispatching in KMDF drivers I have a PCI hardware with two communication channels. (A and B) Only DeviceIoControl() is used to communicate with this hardware, because there are In- and Outdata for each IRP. In NT4.0 driver I use the standard-queue for Type-A IOCTLs and a user-defined-queue for Type-B IOCTLs NTSTATUS MyDeviceControl(...) { ... switch(pIoStack->Parameters.DeviceIoControl.IoControlCode) { case IOCTL_MY_SIMPLE: // read some bits from hardware and complete IRP ... pIrp->IoStatus.Information=... pIrp->IoStatus.Status=... ntStatus=STATUS_SUCCESS; IoCompleteRequest(...) // no queue used break; case IOCTL_TYPE_A: ntStatus=STATUS_PENDING; IoMarkIrpPending(pIrp); IoStartPacket(...) // the default queue break; case IOCTL_TYPE_B: ntStatus=STATUS_PENDING; IoMarkIrpPending(pIrp); MyAlternateStartPacket(...) // my second queue break; ... } ... } -------------- Now I want to port my driver to KMDF. But I can define only one separate queue for Read, for Write and for IoControl. My Problem is, that I need two queues for IoControl like in my NT4.0 driver, because two User-Mode threads are communicating with my hardware (one thread with channel A, the other with channel B) Question 1: Is it possible in KMDF to return the IRP without using a queue (like IOCTL_MY_SIMPLE) Question 2: Can I direct my IRPs into different queues in KMDF? EvtIoDeviceControl is called for all types IOCTLs. (IOCTL_TYPE_A and for IOCTL_TYPE_B) Thanks Jacques Tag: What build target to use for Windows XP 64? Tag: 91437
  - 4
    - Print Monitor Needs to Access Interactive Services I have a print monitor that is installed for a custom Postscript printer driver. This print monitor needs to display a screen asking the user to name a file and select some processing options during the call to LcmStartDocPort. It also invokes a COM object that display several interactive screens to process the file during the call to LcmEndDocPort. The printer driver and monitor installs and runs on OSes Win2K and up. It also installs on Vista, and it will properly interact with the user and process files as designed. However, on Vista the OS intercepts the dialog boxes and displays a dialog titled "Interactive Services Dialog Detection". The message is that "The program [my port monitor] may need information or permission to complete a task." When the user clicks OK, the dialogs are displayed. My questions: 1. How can I properly set permissions (programatically, during the installation) on the port monitor so that it can interact in the user session without the OS intercepting the dialog boxes? 2. Do these permissions need to be applied to the port monitor (a dll) or to the spooler that invokes it? Thanks, Mike Tag: What build target to use for Windows XP 64? Tag: 91436
  - 5
    - How to support DRM in AVStream? Hi, I would like to implement support for DRM content in a AVStream based driver. The DDK only mentioned about how to declare support for a WaveCyclic or WavePCI miniport driver, and nothing about AVStream. Can anyone provide any info? Thanks KS Tag: What build target to use for Windows XP 64? Tag: 91435
  - 6
    - How can I get certification stored in WinXPX64? Which API do I use and it makes me to get certification stored in "WinXPX64"? I tried to use CertOpenSystemStore() and CertEnumCertificatesInStore() APIs. Some certifications stored in local computer, but I sometimes get no certification. I don't know what the reason is. Whether do I need to use other APIs, not these or not? Do these APIs not work completely? Does somebody help me to solve this issue? I need you some suggesstion. Thanks. Tag: What build target to use for Windows XP 64? Tag: 91434
  - 7
    - Strange Monitor behaviour and debug messages on win2k3 Hi there, I have a question, it seems that when I print and exaclty afterwords attempt a XcvDataPort() on the Monitor that has recieved my print data I get error 170 (requested resource is in use). On the debugger it I saw that this module gets loaded "pcl5eres.dll" and someone prints this debug information: "Entering SimpleDocumentPropertiesinside DDPS returning sizeofEntering SimpleDocumentPropertiesEntering SimpleDocumentPropertiesinside DDPS returning sizeofEntering SimpleDocumentPropertiesEntering SimpleDocumentPropertiesinside DDPS returning sizeofEntering " What is it? Does anyone what this data means and why such a think could be happening. Thanks Adam Tag: What build target to use for Windows XP 64? Tag: 91433
  - 8
    - Printer driver problem on Vista I have developed a printer driver that runs on Vista, for some reason when I print a lot of pages (more than 1000); The OS becomes unstable, and some of OS exes become corrupted! For example (task manager)!; And some of the folder security gets changed (you canâ??t access folders that you were allowed to access). And when you restart the OS it will not restart!!! I will have to reinstall VISTA again. Any suggestions of what the problem might be will help? Tag: What build target to use for Windows XP 64? Tag: 91432
  - 9
    - save string functions at IRQL > PASSIVE_LEVEL? I'm porting a big old driver to KMDF. I use some strcat()/strcpy()/sprintf(), often for internal diagnostic messages. They are now deprecated, and the recommended kernel mode replacement RtlStringCch*() functions are bound to PASSIVE_LEVEL. So what is your meaning about the best solution: Leave everything as it is and disable compiler warnings ? Or write my own strcpy_s()/strcat_s()/sprintf_s() ? Tag: What build target to use for Windows XP 64? Tag: 91417
  - 10
    - DIFx: .cab files Hi! Can DIFx handle driver packages with .cab files? like this: mydriverpackage.inf mydriverpackage.cat mydriverpackage.cab (includes all driver files...) -Nick Tag: What build target to use for Windows XP 64? Tag: 91406
  - 11
    - register 32-bit dll in 64bit driver INF Hi, I'm trying to trigger registration of a 32-bit dll during a 64-bit driver installation. The following is an extract of the relevant parts in the INF. [XX_Device.ntamd64] ... CopyFiles=...,xx32.CopyList.ntamd64 ... RegisterDlls=xx.RegisterDlls.ntamd64 [DestinationDirs] ... xx32.CopyList.ntamd64 = 16425 ; %SystemRoot%\SysWOW64 [xx32.CopyList.ntamd64] xx123.dll,,,0x0100 [xx.RegisterDlls.ntamd64] ... 16425,,xx123.dll,1 After the inf installation, my 32-bit dll (xx123.dll) gets copied correctly to the SysWOW64 directory, but it the regsvr of the 32 bit DLL was not successful. Does anyone knows how to trigger the regsvr of the 32-bit dll correctly? Thanks KS Tag: What build target to use for Windows XP 64? Tag: 91396
  - 12
    - Does Longhorn driver work for W2K3 or Vice Versa Hi, I'm porting my driver to Longhorn, it's a boot-loaded driver supporting W2K3 32bit, W2K3 x64 and W2K3 ia64. Now we need to support Longhorn on all 3 platforms. Since for W2K3 support, I've built 6 drivers (free/checked, x86/x64/ia64). If for Longhorn, I build another 6, that'll be a lot. My questions are: 1. If I use WDK to build a driver for Longhorn in WDK Longhorn build enviroment, could that driver run in W2K3 on same platform ? 2. As a boot-loaded driver, to support Longhorn x64, it needs a embedded signature in driver file. If I do so, could this driver run in W2K3 x64 ? Tag: What build target to use for Windows XP 64? Tag: 91390
  - 13
    - DTM: Run WDK File Signature verification Library job task What is this test "Run WDK File Signature verification Library Job task" about?? I have this task running under almost any Job for "Unclassified" category driver and it failed under 4 jobs and succeed for 2 other jobs. Tag: What build target to use for Windows XP 64? Tag: 91388
  - 14
    - DTM client configuration - is Autologon required? I successfully installed all components of DTM. I then decided to run some tests on sound card drivers currently used by computer on which I installed DTM client (this PC is running Windows XP pro if it matters). All these drivers are signed by Microsoft, so I expected that all test should complete successfully. Was my expectation wrong? Because they all failed. Looking at the test errors I see this several times: ================================= Failed to Wait For Autologon Error Code 0 (The operation completed successfully) Resolution Waiting for autologon in session 0 failed. If you have tasks depending on that session to be present then those tasks will fail until someone logs on to the session. ====================================== Does it mean that PC where DTM client is installed should be configured for Autologon? If yes - what user name should I use? I noticed there is DTMLLUAdminUser created by DTM Client installation, but if this has to be used - what is the password for this account? Tag: What build target to use for Windows XP 64? Tag: 91385
  - 15
    - WDK help collection registration Hi, I've installed WDK on one of my computers, and I would like to migrate the WDK documentation to another one, without installing WDK on it. How can I do that? Thanks Tag: What build target to use for Windows XP 64? Tag: 91382
  - 16
    - VISTA Install Windows Drivers (Hardware-First Scenarios) I need to install drivers on VISTA and XP. I will provide a CD containing the drivers. As documented in the SDK and the WHDC site, I have added in my autorun.inf a new directive supported by VISTA, "hardwareid". This is my autorun.inf: [AutoRun] open=setup.exe [DeviceInstall] hardwareid= VID_413C&PID_5128, VID_413C&PID_5128&MI_00, VID_413C&PID_5128&MI_01, VID_413C&PID_5128&MI_02, VID_413C&PID_5128&MI_03, VID_413C&PID_5128&MI_04 DriverPath=\Drivers With VISTA, I am expecting the the "Found New Hardware Wizard" is stopped when I insert the CD containig the drivers, and launch my setup.exe that will preinstall the drivers (using the DIFx DPINST.exe) then give back the hand to the "Found New Hardware Wizard". But this is not the case. What is wrong with my autorun.inf. Olivier Tag: What build target to use for Windows XP 64? Tag: 91379
  - 17
    - NDIS: ProtocolUnbindAdapter() gets called at IRQL DISPATCH_LEVEL on Vista I got a problem, where ProtocolUnbindAdapter() of my IM driver gets called at IRQL DISPATCH_LEVEL on Vista, consequently causing a bugcheck 0x7C with 0x14,0x02,0x00,0x00 parameters when calling NdisWaitEvent() to wait for NdisCloseAdapter() to complete asynchronously. I'd like to know, why this can happen (most likely it's my programming error, but still), if the documentation clearly states that ProtocolUnbindAdapter() is called at PASSIVE_LEVEL IRQL. Also, the Debugging Tools documentation must be updated probably, since it doesn't reflect 0x14 parameter in the 0x7C bugcheck documentation. Additionally, when I specifically enable "DbgPrint buffering" parameter in GFlags utility and reboot the system and it crashes with a full memory dump, WinDbg then displays nothing when issuing ! dbgprint command. The nt!kdprint* buffers are empty for some reason. Thanks. Tag: What build target to use for Windows XP 64? Tag: 91378
  - 18
    - looking for code to detect if Windows firewall is turned on Hi, Please excuse if this is the wrong forum for my question. Does anyone have any code that detects if the Windows XP firewall is running? Hopefully this is code that I could run in VBA (Access)? Thanks, -- Jay Tag: What build target to use for Windows XP 64? Tag: 91377
  - 19
    - help on acpi on driver...thanks. Does device driver or bus driver be able to post a power request packet in able to control the minimum CPU power level on Vista? If this answer is yes,which bus driver or device is? This setting in Vista is on advanced setting of Power options. Thanks for answering. Tag: What build target to use for Windows XP 64? Tag: 91374
  - 20
    - KMDF inconsistent compiling: order of struct { } members differs I'm writing a KMDF-driver with an IoCtl-Interface. For each IOCTL-code I have defined a C-structure which describes the data passed between driver and the application. These structures interpret the data buffer "inBuf" and "outBuf" on both sides of DeviceIoControl(). So I have several "typedef struct { ... } " declarations. These are located in a separate header .h-file, which is included both in the driver sources and the application sources. So it is garanteed that driver and applications use the same buffer-structures. PROBLEM: I have found at least one struct {}, where the compiler changed the field order, when he compiles the driver. Example: typedef struct { DWORD result; DWORD long_value; char string_value[MAX_STRINGPARAMLEN]; } MyRecord ; When I compile the APPLICATION and declare a variable "mybuffer" MyRecord mybuffer ; then the fields have physically those offsets: mybuffer byte 0..3: member ".result" mybuffer byte 4..7: member ".long_value" mybuffer byte 8..11: member ".string_value" = pointer to character-array = address of mybuffer byte 12 mybuffer byte 12 ... space for string This is as it should be: struct fields are allocate in the order they were defined. BUT when I compile the DRIVER, then there are those offsets: MyRecord mybuffer ; mybuffer byte 0..3: member ".result" mybuffer byte 4..7: member ".string_value" = pointer to character-array = address of mybuffer byte 12 mybuffer byte 8..11: member ".long_value" mybuffer byte 12 ... space for string So the order of members is NOT like defined, the members ".long_value" and ".string_value" were exchanged! The consequences are of course catastrophic, since the driver interprets the integer "long_value" as pointer to the character array "string_value" => end of live as we know it. Thanks for reading so far, I hope the problem is clear now. I searched a lot, but found no #pragma settings which could influence the ordering of struct-members. Only struct-aligning can be modified, but this is not my problem. Some more facts: - I use WinDDK 6000 - driver and application are compiled within the same run of the BUILD-utility - its a checked build for x86 and WinXP platform. - build environment is also an x86 machine with WinXP. Tag: What build target to use for Windows XP 64? Tag: 91373
  - 21
    - USB HID Lower Filter Driver issue under VISTA Hi, I have a problem under MS VISTA with a USB HID filter driver (I developped) attached as low filter on the USB common class generic parent driver (usbccgp.sys) for a USB keyboard device with extra keys. The goal of my filter driver is to change the behaviour or inibit some extra keys of the keyboard. The principle of the filter is the following: it change the HID codes output for the requested keys using a remapping table set in the registry (bytes of code to replace/ bytes of replacing code) and comparing incoming codes and replacing if codes are matching the ones for the keys. Inside the filter driver, the codes are catched thru IRP_MJ_INTERNAL_DEVICE_CONTROL IRP, then IOCTL_INTERNAL_USB_SUBMIT_URB control code, then URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER function. This filter driver works fine under Windows XP all version. But, now, under vista the filter is installing and running (i can see this thru debug outputs), but it doesn't filter anything: it doesn't catch anymore the function URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER even if i can see this URB with a sniffer (WDMSniffer). I am not a specialist in driver development and i don't understand what could have changed under Windows Vista comparing to Windows XP ? Does somebody has an idea? Thanks Christian Tag: What build target to use for Windows XP 64? Tag: 91372
  - 22
    - USBOHCI.sys bug. Is it back on Vista? 818e9b90 87b36000 badb0d00 00000000 818e9bec nt!KiTrap0E+0x2ac 818e9c08 883176b4 89ba9144 82f9a1bc 00000004 usbohci! OHCI_SetEndpointState+0x2e 818e9c24 883115fa 89ba8002 82f9a008 00000004 USBPORT! MPf_SetEndpointState+0x45 818e9c50 88317332 36316573 00000007 0000000d USBPORT! USBPORT_iSetGlobalEndpointStateTx+0xb91 818e9c70 8833048f 89ba8028 82f9a008 0000000d USBPORT! USBPORT_iSetGlobalEndpointState+0x18 818e9c84 88330364 89ba8028 82f9a008 00000000 USBPORT! USBPORT_Core_iNukeEndpoint+0x19 818e9cb8 88330520 89ba8028 88330476 818ec820 USBPORT! USBPORT_Core_WalkEndpointList+0x139 818e9cd8 88328fba 89ba8028 818e9d40 818e9d50 USBPORT! USBPORT_Core_NukeAllEndpoints+0x88 818e9ce8 8186b17e 89ba8e5c 89ba8028 82e1a220 USBPORT! USBPORT_SurpriseRemoveDpc+0x1f 818e9d50 81837abe 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147 818e9d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46 We got this bug a lot on 2K surprise removing a PCCard with an OHCI controler on it. Looks like its back on Vista, we are seeing it more frequently. Microsoft guys. any comments? (If you make a statement saying dont surprise remove these cards, that is good enough, we need to convince the customers) Tag: What build target to use for Windows XP 64? Tag: 91368
  - 23
    - Legacy driver class for "Unclassified Signature" program What class should I use for legacy non-pnp software-only driver? According to "Unclassified Signature" requirements, driver must be installed through an INF-file. I tried to use "LegacyDriver" and "Unknown" classes, but chkinf tool reports that these classes are for system use only. Is there the only way is to define own class and write class coinstaller? Thanks for assistance. Tag: What build target to use for Windows XP 64? Tag: 91365
  - 24
    - How to remove default Layer 2 multicast addresses in miniport driv Hello, Upon examining the netvmini sample using OID scope, I found that there are default layer 2 multicast addresses, usually: 01:00:5e:00:00:01 01:00:5e:7f:ff:fa 01:80:c2:00:00:03 After further research, I found that the first two are used for IP multicasting, while the third is used for IEEE 802.1x port authentication. How can I remove these default addresses from the miniport multicast address list? Is it even advisable to do this? Tag: What build target to use for Windows XP 64? Tag: 91363
  - 25
    - DDK info Hi I'm completely new in windows. Please, somebody could you tell me where is possible to download DDK user manuals in pdf format? Thanks. Tag: What build target to use for Windows XP 64? Tag: 91360
- Next
  - 1
    - Devcon sample generating errors... hi... I am trying to compile the devcon source(taken from 2003 DDK) with win2000 DDK checked build.I am getting the errors as follows... d:\ntddk\inc\commctrl.h(28) : error C2146: syntax error : missing ';' before identifier 'HRESULT' d:\ntddk\inc\commctrl.h(28) : fatal error C1004: unexpected end of file found d:\ntddk\inc\commctrl.h(28) : error C2146: syntax error : missing ';' before identifier 'HRESULT' d:\ntddk\inc\commctrl.h(28) : fatal error C1004: unexpected end of file found d:\ntddk\inc\commctrl.h(28) : error C2146: syntax error : missing ';' before identifier 'HRESULT' d:\ntddk\inc\commctrl.h(28) : fatal error C1004: unexpected end of file found Any ideas as to why this is happening? Thanks Regards S Tag: What build target to use for Windows XP 64? Tag: 91354
  - 2
    - High level intermediary driver Hello, Are there any existing driver apps that could "bridge" to audio devices such that audio stream data can be fed to two devices (or more) at the same time? Particularly devices of different colors (hi def audio device and stereo output device or S/PDIF device) When accessed by an application to output audio data, it would appear as an audio device and then redirect and feed the data to multiple audio hardware devices... Thanks, Chris Tag: What build target to use for Windows XP 64? Tag: 91351
  - 3
    - SetupDiXXX functtions Hi all... I am trying to use the SetupDiXXX functions from a WDM driver.I am including the setupapi.h file.After that I include the ntddk.h file (for other declarations used in this driver program).When I am building the driver...I get errors related to various definition and declarations of all the three files included. Is there any clash occuring in those definitions...and how do I solve it... Thanks Regards DC -- Tag: What build target to use for Windows XP 64? Tag: 91349
  - 4
    - Looks like contents msdn server moved to msnd2 server. Few links I had pointing to pages on msdn.microsoft.com seem notto be working now. It seems to have moved to msdn2.microsoft.com. This is for others information who might be facing similar problem. Not sure why this happened and whether this happens regularly.. Tag: What build target to use for Windows XP 64? Tag: 91347
  - 5
    - IOCTL using for notification Hello. I'm trying communication a driver and an application program. So I'm referring to IOCTL. But I think that is very difficult. I want any sample... Could you give any link for samples of PENDING-IOCTL-MEHOD (driver and application program) Please... Tag: What build target to use for Windows XP 64? Tag: 91346
  - 6
    - DTM network LAN Test Environment I got some question in DMT. Q1. In Local machine, Could Test device and Support device set in the sam e PCI Bus? Q2. While NDIS testing, could I change the test item order? Could I just select one subitem to test? Q3. I had already read the DMT's help, But I don't see how to set the subnet of remote machine's message device. My environment: DTM Controller and Studio + 1 NIC IP: 192.168.0.100 Local Machine + Test Device IP: 192.168.0.2 + Support Device IP: 192.168.0.3 + Message Device IP: 192.168.1.2 Remote Machine + Support Device IP: 192.168.0.1 + Message Device IP: 192.168.1.1 am I right? Could you offer the correct environment of the company which had gotten the submission? Q4. Could you offer the PC List which can test DTM Network LAN (Include X86 and X64)? Could you offer the PC List of the company which had gotten the submission? Tag: What build target to use for Windows XP 64? Tag: 91344
  - 7
    - NDIS 6 RSS: mapping between CPU number, MSI message, and queue I am working on an Ethernet miniport driver, and am confused about RSS. Suppose the NIC has 16 MSI-X messages and it supports 16 receive queues. According to the NDIS spec, the NIC should compute the target "CPU" as follows. Target CPU = indirection_table[hash & (table_size - 1)] & (# of receive queues - 1) + base cpu number. Computing this target CPU number is straightforward. But, how should the NIC map this number onto a specific receive queue and also the MSI message to generate an interrupt? The indrection table entries as well as the base CPU number may change over time according to the RSS spec. How does NDIS know that the NIC is interrupting the expected CPU? Tag: What build target to use for Windows XP 64? Tag: 91338
  - 8
    - Performance Counters I have been looking into exporting performance data from the driver I am working on. I am somewhat confused as to what exactly I have to do. I have been reading all the info on MSDN about OpenPerformanceData, CollectPerformanceData, and Performance DLL's. What would I need to do inorder to make the objects I export (WMI) monitorable via perfmon? Tag: What build target to use for Windows XP 64? Tag: 91331
  - 9
    - Accessing IO port Resource Controlled by Motherboard Resource Hi All, I need to access some of the IO ports of my motherboard to turn on some of the on-board LEDs. It looks like these IO port resources are controlled by the "Motherboard Resource" system device. Which is the best way to set/clear bits of this IO registers? Are there any articles available on accessing the resources controlled by the Motherboard Resouece? Thanks in Advance, Boby Tag: What build target to use for Windows XP 64? Tag: 91329
  - 10
    - registry values and limits Is there a recommendation available about the max number of Values to put under a key in the registry ? I think I need about 100 entries? Are there bad consequences to using more than this? Gak - Finecats Tag: What build target to use for Windows XP 64? Tag: 91328
  - 11
    - when is the file system ready? During boot time I'd like to open a file to read some initialization parameters. I have too much data to store in the registry ( I don't know how much is too much, this may be an aesthetic issue), so I am considering storing it in an INI file. How do I know that the file system is ready for business? The info will be in a directory that the user creates. Typically it will be somewhere in C:\program files\...... , but not necessarily. When can I open this file? Gak - Finecats Tag: What build target to use for Windows XP 64? Tag: 91327
  - 12
    - PsLookupThreadByThreadId According to the documentation http://msdn2.microsoft.com/en-au/library/aa489311.aspx PsLookupThreadByThreadId() shall return a referenced pointer to the ETHREAD structure, however the function always returns STATUS_INVALID_PARAMETER, this is in XP SP2 called from a=20 ThreadNotifyCallback registered by PsSetCreateThreadNotifyRoutine(). How can I get a handle to the newly created thread? I need a way to inject a DLL in newly created processes without hooking CreateProcess. =20 Arno Garrels Tag: What build target to use for Windows XP 64? Tag: 91326
  - 13
    - comparing all HW drivers on 2 servers Does anyone know of an easy way to compare the device drivers on 2 systems? I've got several supermicro 6014ptr boxes. one will occasionally freeze up - no network, no video, no kybd, etc. A couple others have frozen up similarly once or twice over the course of a year. I get no msgs in the system logs, the memory tests good (memtest86 for 16+ hrs) so I suspect device drivers. I've considered using MS System Information (winmsd), exporting to a file, then comparing, but I'd like to know if anyone has a better method to recommend. thanks! Bob Tag: What build target to use for Windows XP 64? Tag: 91325
  - 14
    - Stream Class Custom Video Format Problem Greetings, I am trying to create a custom video format for a USB camera driver based on the Stream Class. I currently have support for RGB24 and RGB8 which works fine for just looking at the video stream. However, I need to support some extended information that I believe is best done via a custom format (namely 16 bit monochrome images and some extended timing information). This custom format is consumed by a specific usermode DSHow filter I am also writing. Everything starts off well: the format is negotiated and UM sink filter gets the expected format information. The pins connect and the stream opens (i.e. my camera gets a SRB_OPEN_STREAM and completes successfully). When I transition into run however, I never get any SRB_READ_DATA calls. I can easily still use the RGB24 and RGB8 formats so I know that the support code around the different formats is working. But there is something about this new format that I am missing. I suspect that I was relying on some KS behavior that is no longer present now that I have left the cozy KSDATAFORMAT_SPECIFIER_VIDEOINFO world. To implement my new format, I created two new GUIDs: MEDIASUBTYPE_MYCAM_RAW and KSDATAFORMAT_SPECIFIER_MYCAM_RAW_INFO There is an info structure to hold the format information: typedef struct tagMYCAM_RAW_INFO { // whatever... }MYCAM_RAW_INFO; And a data range and format: typedef struct tagKS_DATARANGE_MYCAM_RAW { KSDATARANGE dataRange; // I include nothing here because there is no "range" to speak of. The camera // only supports whatever its current settings are. } KS_DATARANGE_MYCAM_RAW; typedef struct tagKS_DATAFORMAT_MYCAM_RAW { KSDATAFORMAT dataFormat; MYCAM_RAW_INFO formatInfo; } KS_DATAFORMAT_MYCAM_RAW; The data range is static KS_DATARANGE_MYCAM_RAW StreamDataRange = { // KSDATARANGE dataRange; { sizeof (KS_DATARANGE_MYCAM_RAW), // ULONG FormatSize; 0, // ULONG Flags; [doc: ignored] 0, // ULONG SampleSize; [doc: ignored] 0, // ULONG Reserved; [doc: must be 0] STATICGUIDOF(KSDATAFORMAT_TYPE_VIDEO), // GUID MajorFormat; MEDIATYPE_Video STATICGUIDOF(MEDIASUBTYPE_MYCAM_RAW), STATICGUIDOF(KSDATAFORMAT_SPECIFIER_MYCAM_RAW_INFO) } }; It is possibly that my use of KSDATAFORMAT_TYPE_VIDEO (which I though was required for capture pins) is triggering some assumptions somwhere? Any thoughts would be most appreciated. Best regards, Tom Udale Tag: What build target to use for Windows XP 64? Tag: 91324
  - 15
    - WaveRT/WaveCyclic miniport usage and Vista certification We developed a virtual sound card driver and want it certified by Microsoft. The purpose of the driver is to capture audio stream and then service that we wrote sends it over the local network to networked speakers for playback. So the driver itself doesn't work with any hardware. Our current implementation (we support Windows 2000 and Windows XP 32 bit at this time) uses WaveCyclic miniport. We just started work on supporting Vista and got our driver working under Vista with some minor changes. We are still using WaveCyclic miniport. However, this document http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/DrvCompat_Vista.doc says: ========================== The following list summarizes some key requirements for audio drivers: · Implement Universal Audio Architecture (UAA)-compliant audio devices. · Implement audio drivers _as WaveRT_ miniport drivers. · Implement up-to-date digital rights management (DRM) support. ========================== Does it mean that if our Vista implementation uses WaveCyclic miniport we will not be able to get it certified? Also: who should I address this question to in Microsoft to receive authoritative answer? I emailed to whqldt@microsoft.com but so far haven't received even an acknowledgement that my email has been received. Tag: What build target to use for Windows XP 64? Tag: 91322
  - 16
    - Output sequence for WPP software tracing Moin, I use WPP software tracing in my driver. For each trace line the first item shown is the CPU number in brackets. I'm wondering if there is a output sequence for those trace messages for the same time stamp. I'm currently analyzing a problem within my driver. The driver has a queue of messages with numbers in sequence. For any reason I see the messages fetched in a different order: [3]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=89528008 READ cmd=0x82ff nr=0x4fcf [3]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=89528008 READ cmd=0x82ff nr=0x4fd1 [1]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=89337E68 READ cmd=0x82ff nr=0x4fce [2]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=8987D8F8 READ cmd=0x82ff nr=0x4fd0 I would expect the following order: [1]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=89337E68 READ cmd=0x82ff nr=0x4fce [3]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=89528008 READ cmd=0x82ff nr=0x4fcf [2]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=8987D8F8 READ cmd=0x82ff nr=0x4fd0 [3]08EC.16B0::01/30/2007-13:05:25.839 [driver]CAPI(173): PutMsgToIrpBuffer: IRP=89528008 READ cmd=0x82ff nr=0x4fd1 Is it simply a sequence issue caused by WPP ? Bis gleich ... Stefan Tag: What build target to use for Windows XP 64? Tag: 91320
  - 17
    - NdisRegisterDeviceEx() and CreateFile() security settings. Hi all Ndis 6 and Vista... I am using NdisRegisterDeviceEx() with as SDDL of "D:P(A;;GA;;;SY) (A;;GA;;;BA)(A;;GRGW;;;BU)(A;;GRGW;;;WD)" and it returns STATUS_SUCCESS. With a symboliclinks viewer I can see my device. But, when I try to open it with CreateFile() is using GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, 0, NULL I get the error: 'The request is not supported'. I have tried it with a 0 SDDL too with the same result. I am logged in as Administrator but this needs to work for users too. The old function, NdisRegisterDevice() works on Vista with my Ndis 5.1 driver. Doeas anyone have any ideas? I looked at the netvmini code that ships with the 6000 DDK and dont seed any reason for my code to fail. Thanks in advance for any suggestions on this. Tag: What build target to use for Windows XP 64? Tag: 91317
  - 18
    - Vista 64 bit: HowTo receive origin inf file location? Hi! I need to receive the origin inf file location (path) through my CoInstaller dll when installing a hardware device. I´ve done that in the past using SetupDiGetSelectedDriver and SetupDiGetDriverInfoDetail. Doing it the same way on Vista 64 bit the path points to \Windows\inf. But I need the origin path. Is that somehow possible? Thanks, Nick Tag: What build target to use for Windows XP 64? Tag: 91315
  - 19
    - File System Filter Driver Porting on Vista Hey, I need to port a legacy file system driver onto the vista system. Can some one tell me API's which are not supported by the Vista File System which were supported by the earlier versions of windows so that it can help in porting. If you have some link which has the same information please tell. Thanks for any help. Regards, Aman. Tag: What build target to use for Windows XP 64? Tag: 91310
  - 20
    - newbie for searching a usbaudio.sys lower filter sample code!! Hi! All: I try to write a usbaudio.sys lower filter to get the raw data. I know this is an old question, but I don't know where to get a sample code for this purpose! THX for help! jay Tag: What build target to use for Windows XP 64? Tag: 91307
  - 21
    - hInstance field in PROPSHEETPAGE structure: MSDN doc not correct ( This is maybe not the right place to post this, but I lost almost a whole week because of it, so I hope it will be helpful to someone: The "hInstance" filed in the PROPSHEETPAGE structure must not only be set when you use the "pszIcon, pszTitle, pszHeaderTitle, or pszHeaderSubTitle members" like specified in the MSDN (see below) but also when you specify a resource template in the pszTemplate member (the WIndows CE documentation is apparently correct) Win32 docu: (http://msdn2.microsoft.com/en-us/library/ms652419.aspx) hInstance: Handle to the instance from which to load an icon or string resource. If the pszIcon, pszTitle, pszHeaderTitle, or pszHeaderSubTitle member identifies a resource to load, hInstance must be specified. Windows CE docu: (http://msdn2.microsoft.com/zh-CN/library/aa453562.aspx) hInstance: Handle to the instance from which to load the dialog box template, icon, or title string resource. Tag: What build target to use for Windows XP 64? Tag: 91291
  - 22
    - UpdateDriverForPlugAndPlayDevices fails - Please HELP Hi, I want to install a driver for non-PnP printer. For this I create and register a devnode for my device. Then I try to call UpdateDriverForPlugAndPlayDevices to update the drivers for the PnP devices. I expected to see my printer added but the UpdateDriverForPlugAndPlayDevices failed instead. The driver was installed but the printer was not on the "Printer and Faxes" page. If I add manually "PortName" and its value under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\Printer\0000\Device Parameters" and then call UpdateDriverForPlugAndPlayDevices I have the printer installed. The problem is that the "Device Parameters" key appears after calling UpdateDriverForPlugAndPlayDevices. I cannot create the "Device Parameters" key manually because I am not allowed to. There should be a way to add the PortName parameter somewhere/somehow so that the printer installation to succeed. Are there another settings that I should add in order to get the printer installed correctly? Thanks a lot Tag: What build target to use for Windows XP 64? Tag: 91284
  - 23
    - ACPIView on vista I tried to run the ACPIView tool on vista (RTM). It throwed an error message saying "unable to load driver". What driver is it trying to load? Is it acpiec.sys? or its some other driver? Is there a ACPI Viewer for vista already available? Tag: What build target to use for Windows XP 64? Tag: 91283
  - 24
    - Intel ICH8 chipset doesn't response a DMA ack....(Vista) Folks: I was porting my FIR driver to Vista. My FIR driver work fine on my SIS EV board (both XP and Vista). My Custom used INTEL ICH8 chipset (for mobile). XP worked fine but Vista didn't work. During FIR negotiation, each computer will send/receive 2 bytes data (command and address) and 4 bytes FCS check code. Normally, FIR will send/receive a 6 bytes data (2 bytes data and 4 bytes command). I used LA to monitor DMA cycle and found out Vista didn't response the 5th time DMA ack. The FIR negotiation failed. Then repeated the error. Anyone knew how to monitor DMA operation ? I mean once I start DMA transfer. DMA should move data automatically. How did I know which steps DMA operation was wrong ? There is a strange situation: I installed XP and Vista in the same HD. There is two OS I could choose during booting. If I entered XP then reboot, changed to Vista (without unplug power). My FIR worked fine. If I removed my power core then plug, booting in Vista. The FIR driver failed to connect. Anyone can give me an advice ? Thanks Tag: What build target to use for Windows XP 64? Tag: 91282
  - 25
    - DTM Network LAN Test If test device is giga bit device, all others(Support, Message device) must be giga bit device??? In Local Maching: Test Device and Support Device should be plug in different PCI Bus???? Because HCT 12.1 must set these two card in different PCI Bus. And WDK???? Tag: What build target to use for Windows XP 64? Tag: 91276

What build target should I use for Windows XP 64 in 3790.1830 DDK? What
about WDK 6000?

Re: What build target to use for Windows XP 64? by Gianluca

Gianluca
Thu Feb 01 17:11:43 CST 2007

For DDK 3790.1830 use the Win2003 x64 build target. I'd use the same for
WDK6000.

Ciao
GV

"Nobody" <noone@nowhere.com> wrote in message
news:e8YSzXlRHHA.4060@TK2MSFTNGP03.phx.gbl...
> What build target should I use for Windows XP 64 in 3790.1830 DDK? What
> about WDK 6000?
>
>

Top

Re: What build target to use for Windows XP 64? by Tim

Tim
Fri Feb 02 00:24:10 CST 2007

"Nobody" <noone@nowhere.com> wrote:
>
>What build target should I use for Windows XP 64 in 3790.1830 DDK? What
>about WDK 6000?

Here's a little clue: Microsoft never actually built a 64-bit version of
XP. The product that is marketed as Windows XP 64 is really Windows 2003
Server 64-bit with a new label.

So, in general, pretending you have Win 2003 is a good plan.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

Top