why diskperf attaches itself with disk.sys

NTDEV
1

Hi

The group for disk is “SCSI class” and for diskperf is “System Bus
Extender”. Still diskperf attaches itself with disk.sys.
Why this is happening.

Thanks
rahul

2

Because it specifies that it is an Upper Filter for “Disk Drivers” with the
lines:

[diskperf.AddReg]
HKLM,
System\CurrentControlSet\Control\Class{4d36e967-e325-11ce-bfc1-08002be10318},
UpperFilters, 0x00010008, diskperf

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

“Rahul Pandey” wrote in message news:xxxxx@ntdev…
Hi

The group for disk is “SCSI class” and for diskperf is “System Bus
Extender”. Still diskperf attaches itself with disk.sys.
Why this is happening.

Thanks
rahul

3

> The group for disk is “SCSI class” and for diskperf is "System Bus

Extender". Still diskperf attaches itself with disk.sys.
Why this is happening.
A group determines the load order only; bus extenders are loaded
very early, that’s it - when disk.sys is loaded, diskperf is already
loaded.
The fact that disperf is going to be a filter above disk.sys has
nothing to do with load groups, it’s established by other means.

Note that VTrace uses the same trick by putting itself not
in “Filters” but in “System Bus Extenders”.

Hope it helps.

Regards,
Alex Shvedov

----- Original Message -----
From: “Rahul Pandey”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, July 12, 2005 3:15 AM
Subject: [ntdev] why diskperf attaches itself with disk.sys

Hi

The group for disk is “SCSI class” and for diskperf is “System Bus
Extender”. Still diskperf attaches itself with disk.sys.
Why this is happening.

Thanks
rahul

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com