Regarding "...a complete Vista registry reference, describing all keys,
values and data supported by the OS itself...".
The Hives and Key titles are "fixed", however values and data differ
depending upon the OS versions, applications installed, user modifications,
functions and so forth on the individdual computer. As an example the method
of OS activation such as "retail" single key", "MAKS Multiple Activation
Keys'" and "KMS (server activation)" will generate different data/values.
The book "Microsoft Windows XP Regisrty Guide" from Microsoft Press by
Jerry Honeycutt is excellent for a basic understanding of Registry
construction. The Vista Resource Guide provides some insight on specfic
settings related to Vista.
-
"johanafm" <spam.me@here.net> wrote in message
news:5063F480-FD17-4896-B3E9-BFBEEF8EAC60@microsoft.com...
>
>
> "Mike Brannigan" wrote:
>
>> "johanafm" <spam.me@here.net> wrote in message
>> news:141EEB42-DC58-4607-9047-84B906F97845@microsoft.com...
>> >I was wondering if anybody knows where to I could get my hands on either
>> >a
>> > complete Vista registry reference, describing all keys, values and data
>> > supported by the OS iself, or at least a partial reference describing
>> > supported keys, values and data that can not be set by other means
>> > through
>> > the user interface. I don't really care how the information is made
>> > available; purchasing it in print, as downloadable electronic document
>> > or
>> > simply getting access to it through a browser is all the same to me.
>> >
>> > Contacting MS support (in sweden) was of no use as the answer was along
>> > the
>> > lines of "that's a tough question. I really have no idea". That seems
>> > rather
>> > strange to me as the developper most certainly should have documented
>> > this,
>> > and in the case that they really wish to keep said information from
>> > their
>> > clients, then that decision should be known to the support staff as
>> > well.
>> > Would MS' US support staff know?
>>
>> There is no all encompassing Registry Guide for the general public,.
>> If you need to know the function of a specific key then the best thing to
>> do
>> is just search for it on Microsoft.com as massive amounts of KB articles,
>> TechNet Articles, whitepapers, resource guides and MSDN references
>> contain
>> specifics about many keys.
>> How to access, read and write to the registry is well document in MSDN.
>> There is no requirement for Microsoft to publically document each and
>> every
>> registry key and value any more the they need give you source code access
>>
>> Is there something in particular you want to do ?
>>
>> --
>>
>> Mike Brannigan
>>
>
> Thanks for the tip on searching on the keys themselves.
>
> Actually, there are several things I'd like to do that I've not managed to
> alter through normal means (although I am aware that I may have missed the
> "normal" way to go about it) that I can think of off the top of my head:
> - Make all folders appear as plain folders, disregarding content
> alltogether
> - When using the keyboard to navigate in explorer, have the directory
> listing appear automatically after a short delay, thus removing the need
> to
> press enter.
> - Remove the possibility of switching between user accounts
> - Use normal login procedure (no account listing, just a dialog for
> user/pwd)
> - Enable the possibility of placing folders and short cuts on the start
> menu
> in a non-alphabetical order (while still inserting new ones in
> alphabetical
> order if possible)
> - Remove the built in search feature in IE7.
> - Have the normal menu bar (edit, view etc) just below the title bar
> instead
> of the search bar in IE7 (appearance as in IE6 in other words)
> - Set the Program Files directory as default for any installation instead
> of
> splitting them between Program Files and Program Files (x86).
> - Not showing directory shortcuts (or virtual folders, whatever the name
> might be in english) in the directory tree when expanding drives.
> - Removing the max simultaneous downloads cap in IE7 if it's still there.
> I've yet not had the oppertunity of testing this.