Re: What is the main difference between the symbolic link and "device object Name".

device interfaces use symbolic links.

by the Win32 API I mean CreateFile. The NT API is the set of system
calls windows supports which the Win32 subsystem (and the posix
subsystem, and the old os-2 subsystem, etc…) are built upon. the NT
API is undocumented but people have determined how to use it and drivers
need to be aware of this.

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mathieu Routhier
Sent: Tuesday, June 17, 2003 1:06 PM
To: NT Developers Interest List
Subject: [ntdev] Re: What is the main difference between the symbolic
link and “device object Name”.

From: Peter Wieland [mailto:xxxxx@windows.microsoft.com]
one point of caution - a user-mode application can try to open your
device if it has a name, regardless of whether you create a symbolic
link in \DosDevices or not.

I think of the case of Device Interfaces where there’s no symbolic link
involved and the device object can be reached from user mode. Or… do
device interfaces use symbolic link internally?

But how can a user-mode application open a device object otherwise?
You’ve mentioned the Win32 API: I guess you were referring to
CreateFile(). What do you mean by NT API? Undocumented functions? I’m
a little bit confused.

Mat


You are currently subscribed to ntdev as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com