|
|
Path: cantaloupe.srv.cs.cmu.edu!das-news.harvard.edu!noc.near.net!howland.reston.ans.net!usc!cs.utexas.edu!uunet!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!kralizec.zeta.org.au!not-for-mail |
|
|
From: [email protected] (Steven Murray) |
|
|
Newsgroups: comp.os.ms-windows.misc |
|
|
Subject: Do we need SDK as well as DDK? |
|
|
Date: 16 May 1993 00:27:47 +1000 |
|
|
Organization: Kralizec Dialup Unix Sydney: +61-2-837-1183 V.32bis |
|
|
Lines: 14 |
|
|
Message-ID: <1[email protected]> |
|
|
NNTP-Posting-Host: kralizec.zeta.org.au |
|
|
Summary: Do We need SDK as well as DDK? |
|
|
Keywords: SDK, windows |
|
|
|
|
|
|
|
|
|
|
|
The Microsoft Windows Device Driver Kit (DDK) documentation (blurb) |
|
|
states that the user must separately acquire the Microsoft Windows |
|
|
Software Development Kit (SDK), which contains the Windows tools |
|
|
to build the drivers. If we are using Borland C++ with Application |
|
|
Frameworks, is this necessary? We also have a copy of the Microsoft |
|
|
Press Programmer |
|
|
with the SDK, and Microsoft Macro Assembler 6.0. Why is the SDK |
|
|
neccessary for development of Virtual Device Drivers? |
|
|
|
|
|
- Steven Murray |
|
|
(posted on behalf of Brian Davies) |
|
|
|
|
|
|
