My guess is that the difference is 7.
WrUserRequest seems to be mostly associated with the termserver side of
things while UserRequest is from the more traditional OS components.
Given the large number of wait reasons, and the rather non-existent
documentation for what these values mean and how they are used, it would
be nice if the DDK elaborated on what this parameter is actually used
for, which values are legal, and provided some guidelines other than the
cryptic admonition to just use Executive or UserRequest.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of phil brewer
Sent: Wednesday, January 18, 2006 5:44 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] UserRequest and WrUserRequest difference
I’ve seen the posting saying that the wait reason is a “debug
helper” but does anybody know the difference between:
UserRequest and WrUserRequest?
Is it that the prefix “Wr” indicates a call from a particular
Microsoft “package/wrapper”?
Many Thanks
Phil
from previous posting:
typedef enum _KWAIT_REASON {
Executive,
FreePage,
PageIn,
PoolAllocation,
DelayExecution,
Suspended,
UserRequest,
WrExecutive,
WrFreePage,
WrPageIn,
WrPoolAllocation,
WrDelayExecution,
WrSuspended,
WrUserRequest,
WrEventPair,
WrQueue,
WrLpcReceive,
WrLpcReply,
WrVirtualMemory,
WrPageOut,
WrRendezvous,
Spare2,
Spare3,
Spare4,
Spare5,
Spare6,
WrKernel,
MaximumWaitReason
} KWAIT_REASON;
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com