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

Home NTFSD

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/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Permissions on PhysicalDisk0

OSR_Community_UserOSR_Community_User Member Posts: 110,217
I'm running Windows 2000. My system was originally installed with the RTM
version. I've 'upgaded' to the definitive release. Both are build 2195.

Ever since the upgrade was done, I can no longer do an
IOCTL_GET_DRIVE_LAYOUT on PhysicalDrive0. I can get geometry, but no layout.
The failure is error code 5 (access denied). winobj shows plenty of
permissions on all the seemingly relevant objects (namely,
\devices\harddisk0\DR0, which is the target of the PhysicalDrive0 link).

Anyone got any hints or clues?

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I think you may need administrator privilages.
    ----- Original Message -----
    From: Benson Margulies
    To: File Systems Developers Interest List
    Sent: Thursday, March 02, 2000 4:26 AM
    Subject: [ntfsd] Permissions on PhysicalDisk0


    I'm running Windows 2000. My system was originally installed with the RTM version. I've 'upgaded' to the definitive release. Both are build 2195.

    Ever since the upgrade was done, I can no longer do an IOCTL_GET_DRIVE_LAYOUT on PhysicalDrive0. I can get geometry, but no layout. The failure is error code 5 (access denied). winobj shows plenty of permissions on all the seemingly relevant objects (namely, \devices\harddisk0\DR0, which is the target of the PhysicalDrive0 link).

    Anyone got any hints or clues?
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

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!
Writing WDF Drivers 24 January 2022 Live, Online
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online