I will be sending custom IOCTL to my raw PDO. Obviously, there are already defined ICOTLs … therefore, what code range is it safe to use for customs IOCTLs so I don’t end up using predefined code.
If you are not implementing a Microsoft defined io interface where we defined the ioctl values for your particular class of device, you are free tonuse whatever values you want. In that case you dint have to worry about other ioctl values for other io interfaces.
d
debt from my phone
-----Original Message-----
From: xxxxx@hotmail.com
Sent: Friday, June 10, 2011 7:00 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Custom IOCTL
I will be sending custom IOCTL to my raw PDO. Obviously, there are already defined ICOTLs … therefore, what code range is it safe to use for customs IOCTLs so I don’t end up using predefined code.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
xxxxx@hotmail.com wrote:
I will be sending custom IOCTL to my raw PDO. Obviously, there are already defined ICOTLs … therefore, what code range is it safe to use for customs IOCTLs so I don’t end up using predefined code.
Unless you are filtering a pre-defined device class, there are no
predefined ioctl codes. Some of the bits of the code have a special
meaning (bits 15, 14, 1, 0), but for your own PDO, you can do whatever
you want with the other bits.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.