HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root ??

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root

What does this do, explain elaborately, and give examples, thanks.

[Maxim S. Shatskih]

This is the root nodes of the Device Manager's tree.

Post by Maxim S. Shatskih
This is the root nodes of the Device Manager's tree.

So why is it full of /legacy/ nodes, what happens if I add
a node there, any ideas? Is this the location of filters ?
What is this guid that is there in all the nodes, i.e.

{8ECC055D-047F-11D1-A537-0000F8753ED1}

Seriously, your response as it stands doesn't make me any the
wiser.

[Don Burn]

Well the first thing is that this is a set of nodes owned by Device Manager
and you shouldn't be modifying it. There are Setup routines that allow you
to access the items that you are allowed to.

If is full of legacy nodes, since legacy drivers are root enumerated in PNP
systems. As far as the GUID's you will note that the value is titled
ClassGuid, so this identifies the class of the driver.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

Post by

Post by Maxim S. Shatskih
This is the root nodes of the Device Manager's tree.

So why is it full of /legacy/ nodes, what happens if I add
a node there, any ideas? Is this the location of filters ?
What is this guid that is there in all the nodes, i.e.
{8ECC055D-047F-11D1-A537-0000F8753ED1}
Seriously, your response as it stands doesn't make me any the
wiser.

Post by Don Burn
Well the first thing is that this is a set of nodes owned by Device Manager
and you shouldn't be modifying it. There are Setup routines that allow you
to access the items that you are allowed to.
If is full of legacy nodes, since legacy drivers are root enumerated in PNP
systems. As far as the GUID's you will note that the value is titled
ClassGuid, so this identifies the class of the driver.

What is this cat and mouse game??

[Don Burn]

No, go read the DDK, there are guid for each class of driver. Why don't you
tell us what you think you are trying to do, and maybe we can help you.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

Post by Maxim S. Shatskih

Post by Don Burn
Well the first thing is that this is a set of nodes owned by Device

Manager

Post by Don Burn
and you shouldn't be modifying it. There are Setup routines that allow

you

Post by Don Burn
to access the items that you are allowed to.
If is full of legacy nodes, since legacy drivers are root enumerated in

PNP

Post by Don Burn
systems. As far as the GUID's you will note that the value is titled
ClassGuid, so this identifies the class of the driver.

What is this cat and mouse game??

Post by Don Burn
No, go read the DDK, there are guid for each class of driver. Why don't you
tell us what you think you are trying to do, and maybe we can help you.

Do you know the sfilter sample from the file system internals book?
Well, I just want to install it to see what happens, I have never done
this before so I need some help as to which registry changes I need
to do. I don't mind if I get a crash because I am going to activate it
with net start, so after a reboot it should all come back to normal.

thanks.

Post by Don Burn
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

[Mark Roddy]

Post by

Post by Don Burn
No, go read the DDK, there are guid for each class of driver. Why don't

you

Post by Don Burn
tell us what you think you are trying to do, and maybe we can help you.

Do you know the sfilter sample from the file system internals book?
Well, I just want to install it to see what happens, I have never done
this before so I need some help as to which registry changes I need
to do. I don't mind if I get a crash because I am going to activate it
with net start, so after a reboot it should all come back to normal.

That is about 8 years old and is unlikely to work. At any rate, the enum
tree is not the right place to look. You are basically asking "how does
device installation work", and I rather doubt anybody is going to take
the time to write the several chapters-worth of information required to
answer that question. Get a book, study the ddk, get back to us with
specific questions that make sense.

Post by
thanks.

Post by Don Burn
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

[Stephan Wolf [MVP]]

Sorry, but the OP's questions make me guess he has no idea what he is
trying to do but rather he is doing his homework for some computer
class.

If these are serious questions please try to explain what you are
trying to do or what you need to understand in a broader context.

That will enable people in this forum to provide you with satisfying
answers.

Stephan
---

Post by Don Burn
No, go read the DDK, there are guid for each class of driver. Why don't you
tell us what you think you are trying to do, and maybe we can help you.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

Post by Maxim S. Shatskih

Post by Don Burn
Well the first thing is that this is a set of nodes owned by Device

Manager

Post by Don Burn
and you shouldn't be modifying it. There are Setup routines that allow

you

Post by Don Burn
to access the items that you are allowed to.
If is full of legacy nodes, since legacy drivers are root enumerated in

PNP

Post by Don Burn
systems. As far as the GUID's you will note that the value is titled
ClassGuid, so this identifies the class of the driver.

What is this cat and mouse game??