DDK 3790 question

[dave]

Hello:

I have a driver for W2K and Windows XP.
I used "DDK 2000" to build W2K driver and
"DDK 2600" to build XP driver.

I'm wondering if "DDK 3790" build the driver both for W2K and XP ?

To check it I built some simple driver using "DDK 3790" and
this driver works OK both on W2K and XP.

I'm not sure if this is true for other drivers ?

Thank you,
dave

[Mark Roddy]

Yes. The latest ddks support w2k/xp/w2k3 builds (and for the WDK 'vista'
builds as well.) However you should use the latest ddk and target the
oldest platform. So if you are building a driver that must run on
w2k/xp/w2k3 then you should choose the w2k build option in the w2k3 ddk.

[Don Burn]

Yes, you should only be using the latest DDK 3790.1830 or "Windows Server
2003 SP1 DDK" for all builds. This works for all drivers back to 2000 and
has the latest tools, samples, libraries and documentation.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"dave" <da...@discussions.microsoft.com> wrote in message
news:39017053-1C2A-4620...@microsoft.com...

[r_ko...@mailcity.com]

How can we use 3790 for WDK Vista? Do I need to update my 3790 for
Vista build window? But then I would think they will change version
number. I am little confused.

[Maxim S. Shatskih]

> I'm wondering if "DDK 3790" build the driver both for W2K and XP ?

It contains 2 build envs - w2k-compatible and the new XP-only. The new build
env allows you to use the new XP's features not in w2k. The w2k-compatible
build env is for all other work :)

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
ma...@storagecraft.com
http://www.storagecraft.com

[Mark Roddy]

Well you can't use an older ddk for a newer os, obviously. Starting with
the XP ddk release the ddk is self-contained: it has all the required
build tools, and it supports build targets for all supported OS release.
To build vista OS targets you obviously need the Vista ddk, which is now
named the WDK. It is beta so you have to get into the beta program.

[dave]

The "DDK 3790" has build environment ONLY for "Windows Server 2003" !

Is this the one that builds for W2K and XP platforms ?

thank you,
dave

[Don Burn]

Wrong, 3790 has build environment for 2000, XP and 2003. You probably did
not install all of them. Even this is out of date get 3790.1830

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"dave" <da...@discussions.microsoft.com> wrote in message

news:5AFBFE69-39B0-483A...@microsoft.com...

[Pavel A.]

Well, I hoped to try the WDK for XP drivers as well
(of course, non-production... ) but the release notes say that
it can't build NDIS5.x drivers (yet?)
So much for backward XP compatibility.

--PA

[dave]

For drivers in W2K we using
L"\\DosDevices\SomeName"

For drivers in XP we using
L"\\CLOBAL??\\SomeName"

When I'm using "DDK 3790" W2K environment to build
driver both for W2K and XP how the above difference will be taken care of ?

thank you,

dave

[Don Burn]

Why are you deviating from the standard of \\DosDevices\ ? This is never a
good idea. Especially, since assuming that you second line was GLOBAL the
results will be the same.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"dave" <da...@discussions.microsoft.com> wrote in message

news:DA004FB5-5402-47CC...@microsoft.com...

[dave]

"Don Burn" wrote:

This driver creates additional device objects on request of
user-mode application.

And then another application connects to them.

When I'm using L"\\DosDevices\SomeName" these objects are
visible to application ONLY on W2K platform.

On XP these objects are invisible not only to application but also
to "WinObj.exe" v2.15

When I'm using L"\\CLOBAL??\\SomeName" these objects became
visible both to my application and to "WinObj.exe" v2.15.

thank you,
dave

[Maxim S. Shatskih]

For me, \??\ works fine on XP. It is mapped to \Sessions\0\Api-something
like-this\DosDevices or such.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
ma...@storagecraft.com
http://www.storagecraft.com

"dave" <da...@discussions.microsoft.com> wrote in message
news:3CE2571F-FA42-41B1...@microsoft.com...

[Pavel A.]

"Maxim S. Shatskih" wrote:
> For me, \??\ works fine on XP. It is mapped to \Sessions\0\Api-something
> like-this\DosDevices or such.

A lot of things changed since win2000.
On my XP SP1 Pro, "\DosDevices" is a symlink pointing to "\??"
However there is no "\??" - instead, there is "\GLOBAL??" which is a folder
full of symlinks.
Folder \Sessions\0\DosDevices contains many subfolders each containig
"Global" link that points to \Global?? ...

--PA

[Mark Roddy]

thats odd.

[dave]

Driver creates device objects when systems loads and
also after by request from user-mode appl.

When using "\DosDevices\ " objects created at boot time are visible to
appl both on XP and W2K.

When using "\DosDevices\ " objects created by request from
user-mode appl time are visible only on W2K.

To make them visible on XP i have to use "\Global??"

[Arkady Frenkel]

Pavel , JFYI , now that described in
http://www.amazon.com/exec/obidos/tg/detail/-/0735619174/ref=ase_ccomput-20/103-2267461-7252603?v=glance&s=books
p143 section : Object Names
Arkady

"Pavel A." <pav...@NOwritemeNO.com> wrote in message
news:8F40F062-6C86-429A...@microsoft.com...

[Maxim S. Shatskih]

Creating a symlink from the kmode IoCreateSymbolicLink with the name of
\??\MyLinkName results in a session-local symlink object.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
ma...@storagecraft.com
http://www.storagecraft.com

"Pavel A." <pav...@NOwritemeNO.com> wrote in message
news:8F40F062-6C86-429A...@microsoft.com...

[dave]

I found the answer to my questions in "DDK 3790":

Start: "Paste from "DDK 3790":

Here is sample code for creating a global symbolic link that works on
Windows 98/Me as well as Windows 2000 and later operating systems.:

UNICODE_STRING deviceName; // already initialized.
UNICODE_STRING symbolicLinkName; // initializing below.

if (IoIsWdmVersionAvailable(1, 0x10)) {
// We're on Windows 2000 or later, so we use \DosDevices\Global.

RtlInitUnicodeString(&symbolicLinkName,
L"\\DosDevices\\Global\\SymbolicLinkName");

} else {
// Windows 98/Me. We just use DosDevices.

RtlInitUnicodeString(&symbolicLinkName,
L"\\DosDevices\\SymbolicLinkName");
}

IoCreateSymbolicLink(&symbolicLinkName, &deviceName);

End: "Paste from "DDK 3790":

Thank you, dave

[HRcrestron]

[HRcrestron]

I have a job available using WDK develpment. Would you like to hear more?

[HRcrestron]

I am in an HR dept and looking for a software develper for a new project
using WDK develpment. Would you be interested in hearing more?

"Pavel A." wrote:

> "dave" wrote:
> > The "DDK 3790" has build environment ONLY for "Windows Server 2003" !
>

> Please re-install it.
> Select custom install, then select the environments you need.
>
> --PA
>

[chris.a...@gmail.com]

On Apr 7, 9:44 am, HRcrestron <HRcrest...@discussions.microsoft.com>
wrote:

> I am in an HR dept and looking for a software develper for a new project
> using WDK develpment. Would you be interested in hearing more?

Why are you asking this question in a reply to a thread about an
outdated version of the DDK?

[Tim Roberts]

chris.a...@gmail.com wrote:

Because he is a clueless spammer who has not taken the time to understand
simple Usenet etiquette before making this kind of request.
--
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.