IOCTL Function code conflict in Windows 7

Hi All,
I happened to come across a strange situation. I wrote some test driver for Windows 7 and it runt perfectly well. I add a new IOCTL and put the Function code different from other IOCTL ( all function code are in range of 0x9xx). In Windows 7, it seems there is a conflict in IOCTL when i run new IOCTL. When i try to change the Function code, it run seems fine. All these does not happened in Widows 8 or Windows 10. I am plugging the debugger for more information but do anyone have information about this.
Thank you

You might want to provide the source code instead of a description of what
you think the source code is.

Mark Roddy

On Wed, Feb 8, 2017 at 5:11 AM, wrote:

> Hi All,
> I happened to come across a strange situation. I wrote some test driver
> for Windows 7 and it runt perfectly well. I add a new IOCTL and put the
> Function code different from other IOCTL ( all function code are in range
> of 0x9xx). In Windows 7, it seems there is a conflict in IOCTL when i run
> new IOCTL. When i try to change the Function code, it run seems fine. All
> these does not happened in Widows 8 or Windows 10. I am plugging the
> debugger for more information but do anyone have information about this.
> Thank you
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

What do you mean by conflict? It fails to reach the driver? What is the error code?

Bent from my phone


From: xxxxx@lists.osr.com on behalf of xxxxx@yahoo.com.vn
Sent: Wednesday, February 8, 2017 2:11:35 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] IOCTL Function code conflict in Windows 7

Hi All,
I happened to come across a strange situation. I wrote some test driver for Windows 7 and it runt perfectly well. I add a new IOCTL and put the Function code different from other IOCTL ( all function code are in range of 0x9xx). In Windows 7, it seems there is a conflict in IOCTL when i run new IOCTL. When i try to change the Function code, it run seems fine. All these does not happened in Widows 8 or Windows 10. I am plugging the debugger for more information but do anyone have information about this.
Thank you


NTDEV is sponsored by OSR

Visit the list online at: http:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:

To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>

xxxxx@yahoo.com.vn wrote:

I happened to come across a strange situation. I wrote some test driver for Windows 7 and it runt perfectly well. I add a new IOCTL and put the Function code different from other IOCTL ( all function code are in range of 0x9xx). In Windows 7, it seems there is a conflict in IOCTL when i run new IOCTL. When i try to change the Function code, it run seems fine. All these does not happened in Widows 8 or Windows 10. I am plugging the debugger for more information but do anyone have information about this.

And while you’re showing us the source code, be sure to show us the
macro calls you used to create the ioctl codes.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.