If you ever need to look up an ioctl code by number, I wrote a little
tool to extract this information. The whole list from the 6000 WDK is here:
http://www.probo.com/timr/ioctls.html
I used the C pre-processor to help make this list, which means I had to
make some choices. Ioctls that expired prior to Vista are not included.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
just one gnit to pick … you misspelled WDK in the title.
Thanks Tim.
–
The personal opinion of
Gary G. Little
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> If you ever need to look up an ioctl code by number, I wrote a little
> tool to extract this information. The whole list from the 6000 WDK is
> here:
> http://www.probo.com/timr/ioctls.html
>
> I used the C pre-processor to help make this list, which means I had to
> make some choices. Ioctls that expired prior to Vista are not included.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
Hello, Tim,
I am just curious, where did you find FILE_DEVICE_AVIO? I have searched through WDK 6000 as well as the latest PSDK and could not find it. Your list has it as 0x99.
Thanks,
-Stephen Cleary
xxxxx@gmail.com wrote:
Hello, Tim,
I am just curious, where did you find FILE_DEVICE_AVIO? I have searched through WDK 6000 as well as the latest PSDK and could not find it. Your list has it as 0x99.
Well, he said sheepishly, I pulled 0x99 out of thin air because I
couldn’t find a proper definition…
I assume the three ioctls that use it are internal to the kernel and
should have been #ifdef-ed out.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.