Thank you.
So if anybody knows what the _xxx is and what these IOCTLs exactly do …
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)
ts.osr.com
16.01.2004 23:35
Please respond to
“Windows System
Software Devs Interest
List”
> ----------
> From: xxxxx@storagecraft.com[SMTP:xxxxx@storagecraft.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Friday, January 16, 2004 8:26 PM
> To: xxxxx@lists.osr.com
> Subject: Re: [ntdev] Windows Server 2003 control codes for disk
> drivers (Unsigned Mail)
>
> > I have a few too:
> > 4DC010h
> > 4DC004h
>
> These are IOCTL_MOUNTDEV_xxx
>
Yes. It isn’t quite easy to find it because of clever definitions in
mountmgr.h:
#define MOUNTMGRCONTROLTYPE ((ULONG) ‘m’)
#define MOUNTDEVCONTROLTYPE ((ULONG) ‘M’)
‘M’ is 0x4D. When an unkown IOCTL is received, it is useful to search DDK
headers for both hex code of device type and appropriate letter if there is
any. MountMgr isn’t the only example of such device type definition.
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
You already have all necessary info to find it yourself (hint: start with
mountdev.h and mountmgr.h). And AFAIK, these IOCTLs are documented in the
DDK.
Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]
From: xxxxx@utimaco.de[SMTP:xxxxx@utimaco.de]
Reply To: xxxxx@lists.osr.com
Sent: Monday, January 19, 2004 10:11 AM
To: xxxxx@lists.osr.com
Subject: RE: [ntdev] Windows Server 2003 control codes for disk
drivers (U nsigned Mail) (Unsigned Mail)
Thank you.
So if anybody knows what the _xxx is and what these IOCTLs exactly do …
Kind regards
Else
Michal Vodicka
> Software Devs Interest List"
> nospam> cc:
>
> Sent by: Subject: RE: [ntdev]
> Windows Server 2003 control codes for disk drivers (U
> xxxxx@lis nsigned Mail) (Unsigned
> Mail)
> ts.osr.com
>
>
>
>
>
> 16.01.2004 23:35
>
> Please respond to
>
> “Windows System
>
> Software Devs Interest
>
> List”
>
>
>
>
>
>
>
> > ----------
> > From: xxxxx@storagecraft.com[SMTP:xxxxx@storagecraft.com]
> > Reply To: xxxxx@lists.osr.com
> > Sent: Friday, January 16, 2004 8:26 PM
> > To: xxxxx@lists.osr.com
> > Subject: Re: [ntdev] Windows Server 2003 control codes for disk
> > drivers (Unsigned Mail)
> >
> > > I have a few too:
> > > 4DC010h
> > > 4DC004h
> >
> > These are IOCTL_MOUNTDEV_xxx
> >
> Yes. It isn’t quite easy to find it because of clever definitions in
> mountmgr.h:
>
> #define MOUNTMGRCONTROLTYPE ((ULONG) ‘m’)
> #define MOUNTDEVCONTROLTYPE ((ULONG) ‘M’)
>
> ‘M’ is 0x4D. When an unkown IOCTL is received, it is useful to search DDK
> headers for both hex code of device type and appropriate letter if there
> is
> any. MountMgr isn’t the only example of such device type definition.
>
> 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
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: michal.vodicka@st.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Well ‘M’ 0x10 is not documented anywhere as far as I can tell. ‘m’ 0x10 is
documented.
=====================
Mark Roddy
-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Monday, January 19, 2004 2:16 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Windows Server 2003 control codes for
disk drivers (U nsigned Mail) (Unsigned Mail)
You already have all necessary info to find it yourself
(hint: start with mountdev.h and mountmgr.h). And AFAIK,
these IOCTLs are documented in the DDK.
Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]
> ----------
> From: xxxxx@utimaco.de[SMTP:xxxxx@utimaco.de]
> Reply To: xxxxx@lists.osr.com
> Sent: Monday, January 19, 2004 10:11 AM
> To: xxxxx@lists.osr.com
> Subject: RE: [ntdev] Windows Server 2003 control codes for disk
> drivers (U nsigned Mail) (Unsigned Mail)
>
>
> Thank you.
> So if anybody knows what the _xxx is and what these IOCTLs
exactly do …
>
> Kind regards
> Else
>
>
>
>
>
>
> Michal Vodicka
>
> > “Windows System
> > Software Devs Interest List”
> > nospam> cc:
> >
> > Sent by: Subject:
> RE: [ntdev]
> > Windows Server 2003 control codes for disk drivers (U
> > xxxxx@lis nsigned
> Mail) (Unsigned
> > Mail)
> > ts.osr.com
> >
> >
> >
> >
> >
> > 16.01.2004 23:35
> >
> > Please respond to
> >
> > “Windows System
> >
> > Software Devs Interest
> >
> > List”
> >
> >
> >
> >
> >
> >
> >
> > > ----------
> > > From: xxxxx@storagecraft.com[SMTP:xxxxx@storagecraft.com]
> > > Reply To: xxxxx@lists.osr.com
> > > Sent: Friday, January 16, 2004 8:26 PM
> > > To: xxxxx@lists.osr.com
> > > Subject: Re: [ntdev] Windows Server 2003 control
> codes for disk
> > > drivers (Unsigned Mail)
> > >
> > > > I have a few too:
> > > > 4DC010h
> > > > 4DC004h
> > >
> > > These are IOCTL_MOUNTDEV_xxx
> > >
> > Yes. It isn’t quite easy to find it because of clever definitions in
> > mountmgr.h:
> >
> > #define MOUNTMGRCONTROLTYPE ((ULONG) ‘m’) #define
> MOUNTDEVCONTROLTYPE
> > ((ULONG) ‘M’)
> >
> > ‘M’ is 0x4D. When an unkown IOCTL is received, it is useful
> to search
> > DDK headers for both hex code of device type and
> appropriate letter if
> > there is any. MountMgr isn’t the only example of such device type
> > definition.
> >
> > 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
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: michal.vodicka@st.com To
> > unsubscribe send a blank email to xxxxx@lists.osr.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@stratus.com To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
> ----------
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]