KB Articles for Microsoft Windows Device Driver Kit

• Q29519: How to Write a Driver for a Custom Hardware Device
• Q31985: Adjusting Mouse Acceleration Within a Driver
• Q65928: FIX: COMM.DRV Locks Up with Full Duplex Communications
• Q63937: VDS.exe Demonstrates DMA in Windows 3.0
• Q63974: IOCtl Calls in Protected-Mode Microsoft Windows
• Q67165: AllocCStoDSAlias Function Not Documented & Not Supported
• Q67590: VWFD.exe VxD Helps MS-DOS Application Query Screen State
• Q67845: Calling a DLL Written for Windows from a TSR for MS-DOS
• Q68068: Development Environment Required to Use Windows DDK
• Q68250: VFINTD.exe Capturing Global Interrupts in Enhanced Mode
• Q68975: I/O Device Serialization and Virtualization
• Q69292: PRB: Video Driver GP-Faults When Handling Large Bitmaps
• Q71224: SetKBD.exe Dynamically Loads Keyboard DLL
• Q73333: PRB: WDEB386 Does Not Find Driver Symbol Files
• Q72379: Tips on Using WDEB386
• Q72637: Sharing IRQs with the Windows 3.0 Communications Driver
• Q72814: Windows 3.0 Does Not Support Auto-Initialize DMA
• Q72899: SAMPLE: VPostD.exe Calls PostMessage from a Virtual Device (VxD)
• Q74471: Using Selectors from _Allocate_LDT_Selector Service
• Q74472: Initializing Virtual Devices and Hooking Interrupts
• Q74516: Binding a TSR to a VxD
• Q74572: How Microsoft Windows Uses an MS-DOS Mouse Driver
• Q74808: How Display Drivers Use Shadow RAM
• Q74810: Calling Windows Functions from a Device Driver
• Q74994: Display Drivers and Background Drawing to Memory Bitmaps
• Q75005: Handling NULL lpDrawMode in a Display Driver
• Q75006: Virtual Communications Driver Functional Structure
• Q75008: Virtual Display Device I/O Trapping
• Q75009: Using Call_Priority_VM_Event
• Q75497: Writing Embedded Applications for Microsoft Windows
• Q75535: PRB: Network Drive Type Reported Incorrectly
• Q75536: Idle Interrupt (INT 28h) Under Windows 3.0
• Q75742: Display Driver Compatibility
• Q75864: Async VMM Services May Be Called by Interrupt Handlers
• Q75940: BUG: VKD_API_Force_Key Can Cause Windows Crash
• Q77403: MsgMode.exe Uses Message Mode Services & VMM w/VxD
• Q77404: PRB: SETUP.EXE Fails to Replace OEM Drivers
• Q77990: Switching Stacks at Interrupt Time
• Q76301: SAMPLE: VFood.exe Contains Basic Virtual Device (VxD) Structure
• Q76473: PRB: No Output from VxD Debug_Out and Trace_Out Macros
• Q76564: Receiving a Physical COM Port from the Windows VCD
• Q76955: BUG: V86MMGR Virtual Device Boundary Condition Fails
• Q78151: Using the Interrupt 2Fh Critical Section Services
• Q78325: Ring Protection Under Windows 3.1
• Q79988: CE_OVERRUN Errors with Serial Communications
• Q79989: DPMI0301.exe Simulates Real Mode Interrupts
• Q83012: Using Auto-Initialize DMA Under Windows
• Q83658: INF: Version Information Resources in VxDs
• Q83726: INT 12h and Windows Enhanced Mode
• Q84000: Obtaining a Virtual Device (VxD) ID Number
• Q84053: How a TSR Can Serialize Access to Its Data
• Q84071: SAMPLE: WNBDemo.exe Uses NetBIOS Under Microsoft Windows
• Q84191: Proton.exe Uses DPMI Host for MS-DOS Protected Mode Apps
• Q91023: Minidriver Dump() and BlockOut() Callbacks
• Q89330: Complete Text PW0563: Display Compatibility Testing
• Q89494: VHotKeyd.exe VxD Hot Keys in Windows 386 Enhanced Mode
• Q89705: INFO: How VMs Can Communicate with VxDs
• Q92407: API Translation Buffers in Enhanced Mode Windows
• Q92532: PRB: Display Monitor Goes Blank After the Logo Display
• Q92533: Implementing Display Driver Device Bitmaps
• Q92648: PRB: Linear Addr Mode Display Driver & MS-DOS Virtual Machines
• Q90563: Using the AdvancedSetUpDialog() Configuration Call
• Q90796: Instanced Data Management in Enhanced Mode Windows
• Q95456: Overview of Printer Font Metrics (PFM) Files
• Q108309: FIX: Posting WM_COMMNOTIFY Messages May Fail
• Q107696: Modifying COMM.DRV to Support up to Nine Ports
• Q107697: BUG: Sharing IRQ with COM1 Causes System to Reboot
• Q120079: PRB: INT 2Fh 1684h May Return ES == 0 and DI != 0
• Q120565: How to Read Text Mode Screen of MS-DOS Session in Windows
• Q121661: How to Use the TrueType Fonts Built into the Printer
• Q123463: BUG: MSODISUP.386 Giving Bad Value for Link Speed Causes Hang
• Q124729: How to Program DMA Transfers in the Protected Mode Windows Env
• Q125635: BUG: Win 3.1 Kernel Debugger 3.10.46 Locks Up on Pentium Sys
• Q126349: PRB: FastDisk BusMaster DMA Disk Devices Crashes When Paging

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.