identify kernel os with an extension.

Hi all,

Is there an easy way to identify the OS of the target being debugged
with a windbg ext??

I have an extension that I wrote that loads the correct driver based on
the OS on the target, but I don’t know how to identify the target. Right
now I set it manually myself (another extension function), but I would
rather find it with some function.

I had a previous code that called Ioctl(IG_GET_KERNEL_VERSION,… but I
can’t make heads or tails of the undocumented output (at least I don’t
know what would identify the OS)

Thanks

SG

You can read nt!NtMajorVersion, nt!NtMinorVersion and nt!NtBuildNumber in
your extension. Is that sufficient? Converting the value in nt!NtBuildNumber
to build# requires some work though.


Calvin Guan, Windows DDK MVP
Software Engineer, NT Driver
ATI Technologies Inc. www.ati.com

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-205710-
xxxxx@lists.osr.com] On Behalf Of Steve Goddyn
Sent: April 5, 2005 1:03 PM
To: Kernel Debugging Interest List
Subject: [windbg] identify kernel os with an extension.

Hi all,

Is there an easy way to identify the OS of the target being debugged
with a windbg ext??

I have an extension that I wrote that loads the correct driver based on
the OS on the target, but I don’t know how to identify the target. Right
now I set it manually myself (another extension function), but I would
rather find it with some function.

I had a previous code that called Ioctl(IG_GET_KERNEL_VERSION,… but I
can’t make heads or tails of the undocumented output (at least I don’t
know what would identify the OS)

Thanks

SG


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