RE: Windows Server 2003 control codes for disk drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Ma

NTDEV
1

sorry MOUNTDEV_LINK_CREATED was not the problem, it came here by mistake.
The dbg version of my driver “lets me know” about IOCTLs it does not
recognize
(=outside of DDK). Be assured that before I go to the list I search the
newest DDK and
the Web (IOCTL-Decoder) then, but 704008h (-> disk ) and 4DC010h (->
volume) I did
not find.
I’m so insistent because I think that “newer” IOCTLs (like the XP _EX
stuff) might gradually
replace the older ones, and just try to keep the driver up to date to
support all OSs > NT.

Kind regards
Else

Michal Vodicka

nospam> cc:
Sent by: Subject: RE: [ntdev] Windows Server 2003 control codes for disk drivers (U
xxxxx@lis nsigned Mail) (Unsigned Mail) (Unsigned Mail)
ts.osr.com

19.01.2004 21:25
Please respond to
“Windows System
Software Devs Interest
List”

> ----------
> From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Monday, January 19, 2004 8:50 PM
> To: xxxxx@lists.osr.com
> Subject: RE: [ntdev] Windows Server 2003 control codes for disk
> drivers (U nsigned Mail) (Unsigned Mail)
>
> Well ‘M’ 0x10 is not documented anywhere as far as I can tell. ‘m’ 0x10
is
> documented.
>
Did you shift 0x10 two times to the right? ‘M’ 0x10 is
IOCTL_MOUNTDEV_LINK_CREATED.

Well, original question was for 4DC010h which is strange because above
mentioned is 0x4D0010. All ‘M’ IOCTLs in DDK headers are defined with
FILE_ANY_ACCESS and 0xCxxx is FILE_READ_ACCESS | FILE_WRITE_ACCESS.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

2

> ----------

From: xxxxx@utimaco.de[SMTP:xxxxx@utimaco.de]
Reply To: xxxxx@lists.osr.com
Sent: Tuesday, January 20, 2004 8:51 AM
To: xxxxx@lists.osr.com
Subject: RE: [ntdev] Windows Server 2003 control codes for disk
drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)

sorry MOUNTDEV_LINK_CREATED was not the problem, it came here by mistake.
The dbg version of my driver “lets me know” about IOCTLs it does not
recognize
(=outside of DDK). Be assured that before I go to the list I search the
newest DDK and
the Web (IOCTL-Decoder) then, but 704008h (-> disk ) and 4DC010h (->
volume) I did
not find.
I’m so insistent because I think that “newer” IOCTLs (like the XP _EX
stuff) might gradually
replace the older ones, and just try to keep the driver up to date to
support all OSs > NT.

Well, you’re right, there is something strange. 0x4DC010 has the same device
type and function code as IOCTL_MOUNTDEV_LINK_CREATED and differs in access
flags only. It is unusual; maybe there are two version of this IOCTL or it
was updated in the latest OS version.

I’d try to find who sends this IOCTL, it shouldn’t be so hard (trap IRP and
examine call stack). Also, you can binary search system32\drivers directory
to find modules which contain this value.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

3

IOCTL_MOUNTDEV_LINK_CREATED has different access flags for different OS:
FILE_ANY_ACCESS - for Win2K and WinXP
FILE_READ_ACCESS | FILE_WRITE_ACCESS - for Windows Server 2003

Anybody has an idea about my original question:

  1. How should the disk driver handle IOCTL_VOLUME_IS_CLUSTERED (0x560030)?
  2. What is IOCTL code 0x49400?

Regards,
Gregory

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Wednesday, January 21, 2004 00:43
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Windows Server 2003 control codes for disk drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)

From: xxxxx@utimaco.de[SMTP:xxxxx@utimaco.de]
Reply To: xxxxx@lists.osr.com
Sent: Tuesday, January 20, 2004 8:51 AM
To: xxxxx@lists.osr.com
Subject: RE: [ntdev] Windows Server 2003 control codes for disk
drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)

sorry MOUNTDEV_LINK_CREATED was not the problem, it came here by mistake.
The dbg version of my driver “lets me know” about IOCTLs it does not
recognize
(=outside of DDK). Be assured that before I go to the list I search the
newest DDK and
the Web (IOCTL-Decoder) then, but 704008h (-> disk ) and 4DC010h (->
volume) I did
not find.
I’m so insistent because I think that “newer” IOCTLs (like the XP _EX
stuff) might gradually
replace the older ones, and just try to keep the driver up to date to
support all OSs > NT.

Well, you’re right, there is something strange. 0x4DC010 has the same device
type and function code as IOCTL_MOUNTDEV_LINK_CREATED and differs in access
flags only. It is unusual; maybe there are two version of this IOCTL or it
was updated in the latest OS version.

I’d try to find who sends this IOCTL, it shouldn’t be so hard (trap IRP and
examine call stack). Also, you can binary search system32\drivers directory
to find modules which contain this value.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

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

*** IMPORTANT: Do not open attachments from unrecognized senders ***

******************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to any one or make copies.

******************************************************************************************

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

4

In general if you don’t support an IRP IOCTL you either hand it down
unprocessed to whomever is below you, or if you terminate the stack, you
simply fail it. If you are emulating a physical disk, you are not likely to
have to deal with volume IOCTLs or mountmgr IOCTLS. Instead, use the source
for classpnp/disk in the ddk to guide you about which IOCTLs you do have to
process.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gregory Dardyk
Sent: Wednesday, January 21, 2004 1:35 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Windows Server 2003 control codes for
disk drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)

IOCTL_MOUNTDEV_LINK_CREATED has different access flags for
different OS:
FILE_ANY_ACCESS - for Win2K and WinXP
FILE_READ_ACCESS | FILE_WRITE_ACCESS - for Windows Server 2003

Anybody has an idea about my original question:

  1. How should the disk driver handle
    IOCTL_VOLUME_IS_CLUSTERED (0x560030)?
  2. What is IOCTL code 0x49400?

Regards,
Gregory

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Wednesday, January 21, 2004 00:43
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Windows Server 2003 control codes for
disk drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)

> ----------
> From: xxxxx@utimaco.de[SMTP:xxxxx@utimaco.de]
> Reply To: xxxxx@lists.osr.com
> Sent: Tuesday, January 20, 2004 8:51 AM
> To: xxxxx@lists.osr.com
> Subject: RE: [ntdev] Windows Server 2003 control codes for disk
> drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)
>
>
> sorry MOUNTDEV_LINK_CREATED was not the problem, it came
here by mistake.
> The dbg version of my driver “lets me know” about IOCTLs
it does not
> recognize (=outside of DDK). Be assured that before I go to
the list I
> search the newest DDK and the Web (IOCTL-Decoder) then,
but 704008h
> (-> disk ) and 4DC010h (->
> volume) I did
> not find.
> I’m so insistent because I think that “newer” IOCTLs (like
the XP _EX
> stuff) might gradually
> replace the older ones, and just try to keep the driver up
to date to
> support all OSs > NT.
>
Well, you’re right, there is something strange. 0x4DC010 has
the same device type and function code as
IOCTL_MOUNTDEV_LINK_CREATED and differs in access flags only.
It is unusual; maybe there are two version of this IOCTL or
it was updated in the latest OS version.

I’d try to find who sends this IOCTL, it shouldn’t be so hard
(trap IRP and examine call stack). Also, you can binary
search system32\drivers directory to find modules which
contain this value.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

*** IMPORTANT: Do not open attachments from unrecognized senders ***

**************************************************************
****************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the
system manager or the sender immediately and do not disclose
the contents to any one or make copies.

**************************************************************
****************************

**************************************************************
**********************
This footnote confirms that this email message has been
scanned by PineApp Mail-SeCure for the presence of malicious
code, vandals & computer viruses.
**************************************************************
**********************

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

5

> ----------

From: xxxxx@store-age.com[SMTP:xxxxx@store-age.com]
Reply To: xxxxx@lists.osr.com
Sent: Wednesday, January 21, 2004 7:34 AM
To: xxxxx@lists.osr.com
Subject: RE: [ntdev] Windows Server 2003 control codes for disk
drivers (U nsigned Mail) (Unsigned Mail) (Unsigned Mail)

IOCTL_MOUNTDEV_LINK_CREATED has different access flags for different OS:
FILE_ANY_ACCESS - for Win2K and WinXP
FILE_READ_ACCESS | FILE_WRITE_ACCESS - for Windows Server 2003

Ah, you’re right. I looked to good DDK and bad directory… This is really
great and will help us to make binary compatible drivers. It is
irresponsible to change IOCTL codes this way and don’t make big read
exclamation point to docs, at least.

Anybody has an idea about my original question:

  1. How should the disk driver handle IOCTL_VOLUME_IS_CLUSTERED
    (0x560030)?
  2. What is IOCTL code 0x49400?

As Mark Roddy wrote.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]