R
Robert Paris
How do I search the registry from the command line?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Matthias Tacke
Use Reg.exe. Depending on your OS Version you already have it (XP) orRobert Paris said:How do I search the registry from the command line?
should download it. See this thread for details:
http://groups.google.com/[email protected]
HTH
R
Robert Paris
Is that really the only way to search the registry from the command line?
From Windows 2000 and previous there's never been a built-in command-line
utility?
From Windows 2000 and previous there's never been a built-in command-line
utility?
M
Mark V
In said:Is that really the only way to search the registry from the
command line? From Windows 2000 and previous there's never been a
built-in command-line utility?
Never. That's what the Resource Kit is for. <G>
However the quoted article points to a free download
ttp://download.microsoft.com/download/win2000platform/Tool/SP3/NT5/EN-US/SP3SupportTools.exe
which is the same or updated versions of the tools shipped on the
W2K CD as installable (free) "Support Tools". (almost as "built-in")
IMO many/most ResKit tools should always have been shipped with the OS
and optionally or by default installed with it. But that is my pet
peeve with MS's failure to do so.
T
Torgeir Bakken (MVP)
Mark said:However the quoted article points to a free download
ttp://download.microsoft.com/download/win2000platform/Tool/SP3/NT5/EN-US/SP3SupportTools.exe
which is the same or updated versions of the tools shipped on the
W2K CD as installable (free) "Support Tools". (almost as "built-in")
And the latest version of "Support Tools" is available here:
http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/supporttools.asp
D
David Wang [Msft]
Regarding your pet peeve:
There are a couple of causes that I'm aware of which result in such tools
not being shipped with the OS --
1. Supportability -- yet another codebase to support. Who fixes bugs in it,
and who tests it for regressions (this gets even worse when the tool can run
on multiple OS/SKU/Language/Architecture -- quickly, a huge matrix comes out
of any tiny change).
2. Uniformity -- everything in the OS must meet certain requirements. If it
has UI, it needs a help file. It needs to be localized (which has its own
schedule and costs). Etc
It is QUITE trivial for us to crank out a useful utility. Sometimes, the
ResKit tools are utilities originally intended for the OS but the costs got
too great for the benefit, or the schedule slipped, etc, and the ResKit
becomes a way for these tools to see the light of day without supportability
nor uniformity requirements.
These are all real and significant costs that customers seem to expect for
free... something's gotta give.
But the way I'd like to think of it is that maybe there is a better model
for everyone to be happy with such tools and support; I'd love to hear any
comments/suggestions on it.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
Never. That's what the Resource Kit is for. <G>
However the quoted article points to a free download
ttp://download.microsoft.com/download/win2000platform/Tool/SP3/NT5/EN-US/SP3
SupportTools.exe
which is the same or updated versions of the tools shipped on the
W2K CD as installable (free) "Support Tools". (almost as "built-in")
IMO many/most ResKit tools should always have been shipped with the OS
and optionally or by default installed with it. But that is my pet
peeve with MS's failure to do so.
There are a couple of causes that I'm aware of which result in such tools
not being shipped with the OS --
1. Supportability -- yet another codebase to support. Who fixes bugs in it,
and who tests it for regressions (this gets even worse when the tool can run
on multiple OS/SKU/Language/Architecture -- quickly, a huge matrix comes out
of any tiny change).
2. Uniformity -- everything in the OS must meet certain requirements. If it
has UI, it needs a help file. It needs to be localized (which has its own
schedule and costs). Etc
It is QUITE trivial for us to crank out a useful utility. Sometimes, the
ResKit tools are utilities originally intended for the OS but the costs got
too great for the benefit, or the schedule slipped, etc, and the ResKit
becomes a way for these tools to see the light of day without supportability
nor uniformity requirements.
These are all real and significant costs that customers seem to expect for
free... something's gotta give.
But the way I'd like to think of it is that maybe there is a better model
for everyone to be happy with such tools and support; I'd love to hear any
comments/suggestions on it.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
In said:Is that really the only way to search the registry from the
command line? From Windows 2000 and previous there's never been a
built-in command-line utility?
Never. That's what the Resource Kit is for. <G>
However the quoted article points to a free download
ttp://download.microsoft.com/download/win2000platform/Tool/SP3/NT5/EN-US/SP3
SupportTools.exe
which is the same or updated versions of the tools shipped on the
W2K CD as installable (free) "Support Tools". (almost as "built-in")
IMO many/most ResKit tools should always have been shipped with the OS
and optionally or by default installed with it. But that is my pet
peeve with MS's failure to do so.
M
Mark V
In said:Regarding your pet peeve:
There are a couple of causes that I'm aware of which result in
such tools not being shipped with the OS --
1. Supportability -- yet another codebase to support. Who fixes
bugs in it, and who tests it for regressions (this gets even worse
when the tool can run on multiple OS/SKU/Language/Architecture --
quickly, a huge matrix comes out of any tiny change).
2. Uniformity -- everything in the OS must meet certain
requirements. If it has UI, it needs a help file. It needs to be
localized (which has its own schedule and costs). Etc
It is QUITE trivial for us to crank out a useful utility.
Sometimes, the ResKit tools are utilities originally intended for
the OS but the costs got too great for the benefit, or the
schedule slipped, etc, and the ResKit becomes a way for these
tools to see the light of day without supportability nor
uniformity requirements.
These are all real and significant costs that customers seem to
expect for free... something's gotta give.
But the way I'd like to think of it is that maybe there is a
better model for everyone to be happy with such tools and support;
I'd love to hear any comments/suggestions on it.
Well it's getting better... Support Tools on the CD. Free downloads
(even some ResKit items) etc. I've heard all the arguments and
cannot fault MS in any way that contradicts those valid points.
"wish" that more could be included and supported is all. I hear that
XPP has more tools included than W2k (which has more on CD than NT4,
which... Progress.