Tweet
If I were to write a Virtual Drive detector, I would check the the registry of the drive controller. If the controller doesn't use ANY I/O ports or ANY assigned IRQs, the controller is a virtual device, and so does the drive it controls.
While the registry data is only accessible by administrators, most Windows XP users are still using an Administrator group. Even when creating a new user via the User Accounts control panel, the default group is Administrator. And I bet most user ignore this and be an Administrator anyway.
System-only registry data can easily be modified by Administrators and SysInternals-style hidden registry method is already available for public.
My suggestion is, provide a virtually assigned I/O port(s) AND virtually assigned IRQ. Add a virtually used hardware memory (eg. BIOS) also helps. Read-locking the above registry data is impossible and useless since the data is required by the system itself.
Hope that helps and hope it get virtually real.
While the registry data is only accessible by administrators, most Windows XP users are still using an Administrator group. Even when creating a new user via the User Accounts control panel, the default group is Administrator. And I bet most user ignore this and be an Administrator anyway.
System-only registry data can easily be modified by Administrators and SysInternals-style hidden registry method is already available for public.
My suggestion is, provide a virtually assigned I/O port(s) AND virtually assigned IRQ. Add a virtually used hardware memory (eg. BIOS) also helps. Read-locking the above registry data is impossible and useless since the data is required by the system itself.
Hope that helps and hope it get virtually real.
Comment