This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
The Microsoft Hardware Newsletter provides manufacturers and developers the latest technical details for how to succeed with the Windows platform. Stay up to date on beta and final product releases, and specifications for new technologies. Register now, if you're not already receiving the Microsoft Hardware Newsletter.
|
Top Stories
|
|
|
Implementing DMA Support in Windows Drivers
Using direct memory access (DMA) for data transfers to or from a device has many advantages, including higher speed transfers and lower overall system CPU usage. Writing a driver that supports DMA is slightly more complicated than writing a driver for a programmed I/O type of device.
|
A new paper on the WHDC website describes the basic concepts and terminology used in writing DMA drivers for Microsoft® Windows® operating systems. It also describes the details about implementing DMA in a device that driver writers should know before they begin to write the driver. The paper includes details and example code that use both Windows Driver Model (WDM) and Windows Driver Foundation (WDF).
Download and read "DMA Support in Windows Drivers"
Buffer overruns in kernel-mode drivers increase the risk of faults and memory pool corruption that can crash the system, and they create security holes that an attacker could exploit. Read about how to eliminate potential buffer overruns in your driver by using the kernel-mode safe string functions instead of the standard string manipulation functions.
Read the complete driver tip with sample code on the WHDC website.
Top
News for Kernel-Mode Developers
|
|
All kernel-mode drivers must be migrated to (or developed in) 64-bit native mode. MSDN has recorded a webcast by Nar Ganapathy, of the Microsoft WDF team, that explains the migration steps and potential pitfalls, guiding you through a smooth transition to native 64-bit.
MSDN Webcast Drivers for 64-bit Systems
|
Top
Bus and Device-Class Tips and News
|
|
In previous versions of Microsoft Windows, a floppy disk provided by a vendor for storage controller drivers could contain drivers for only one processor architecture. In response to vendor requests to support driver installation for both x86 and x64 architectures, a single floppy disk can contain drivers for multiple architectures, as long as they are in different directories, using the names specified in this article.
To allow drivers for different processor architectures on the same floppy disk, the drivers and Txtsetup.oem for each architecture must reside in separate directories. The directory names are:
x86: \i386
x64: \amd64
Intel Itanium: \ia64
To maintain compatibility with previous Windows versions, if the processor architecture directory is not present, the loader will search the root directory of the disk for the appropriate files. For example, if the floppy has no \i386 directory, the 32-bit driver files can be located in the root directory as they always have been.
The use of standard directory names makes it apparent which processor architecture a particular driver binary is intended for, while allowing the vendor to include multiple versions of the same file name on a single floppy disk. We strongly encourage vendors who provide driver files for multiple processor architectures on a single floppy disk to use the appropriate names for the directories.
|
|
|
In future versions of the Windows operating systems, Microsoft plans to discontinue support for IP over 1394 (that is, TCP/IP over IEEE 1394). Currently, this capability is supported in Microsoft Windows Server 2003, Windows XP, Windows 2000, and Windows Me. Microsoft has not identified any customer dependency on this capability. If you are an IHV or OEM who has a business dependency on this capability, please provide feedback to netdd@microsoft.com.
Top
|
Kits, Tools, Services, and Programs
|
|
DiFX tools simplify installation of driver packages and eliminate most end-user manual steps for installing a driver.
Download DiFX Tools V 1.1
|
Security and Reliability
|
|
MSDN provides advice to help you to improve the security of your developer workstation. It also helps you to avoid common problems that you are likely to encounter when you secure your workstation. Finally, it provides advice on how to identify problems caused by overly restrictive security settings and how to revert those settings when necessary.
|
|
|
|
 December 9, 2004
|
|