Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


IOCTL Function code conflict in Windows 7

Nguyen_The_HungNguyen_The_Hung Member Posts: 12
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

Comments

  • Mark_RoddyMark_Roddy Member - All Emails Posts: 4,335
    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: showlists.cfm?list=ntdev>
    >
    > MONTHLY seminars on crash dump analysis, WDF, Windows internals and
    > software drivers!
    > Details at
    >
    > To unsubscribe, visit the List Server section of OSR Online at <
    > http://www.osronline.com/page.cfm?name=ListServer&gt;
    >
  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,499
    What do you mean by conflict? It fails to reach the driver? What is the error code?

    Bent from my phone

    ________________________________
    From: [email protected] on behalf of [email protected]
    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:

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

    To unsubscribe, visit the List Server section of OSR Online at
    d
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,450
    [email protected] 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, [email protected]
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA