reg hack for windows start menu

I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than a
dozen symbols with lower ASCII values. I sometimes find this handy when I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)

R.Wieser wrote:
Bill in Co,

... but since I was so used to the regular logical (ASCII) character
sort order for files, it drove me nuts.

Same here. Could not visually scan a folder (in XP) for a certain file
anymore, as the sought-for one could pop up in unexpected locations.
Drove me (sort of) mad. :-\

But even with that setting a folder seems to be sorted with all
non-alphanumeric symbols infront of alphanumeric ones (try a filename
starting with a "{" or "}" and you'll see what I mean).

Regards,
Rudy Wieser

P.s.
The other two registry entries are not bad either (understatement). :-)


-- Origional message:
Bill in Co schreef in berichtnieuws
...
Thanks again for the correction, and I hope it's not a problem for the
other
Bill that I added those in, as I found them useful. So Bill C, if you
don't
want the added stuff, hopefully you saved the original before adding this
to
the registry and can go back.

Rudy - I think that change in sorting order came stock with XP and later,
but since I was so used to the regular logical (ASCII) character sort
order
for files, it drove me nuts. But now I can't even remember what the
disadvantage of not using logical character sort order was (the way it is
now in Vista and above). Well I found one example using these file
names:

Picture
Picture - Copy
Picture - Copy 2
Picture - Copy 3

which apparently gets sorted "incorrectly" using the newer method in
Windows
7 and later) as follows:

Picture - Copy 2
Picture - Copy 3
Picture - Copy
Picture

"Windows 7 treats blank spaces in file names illogically in alphanumeric
sorts." URL: http://tinyurl.com/ya5bc29e

R.Wieser wrote:
Bill in Co,

"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001

Please do notice that the above three have nothing to do with "recent
documents".

And I definitily like that last one. It resolved a long standing "what
the
heck?" about the sorting order of the files in a folder ...

Regards,
Rudy Wieser


-- Origional mesage
Bill in Co schreef in berichtnieuws
...
Bill Cunningham wrote:
"Bill in Co" wrote in message
...

I'm coming into this thread a bit late, but if you are looking for a
way
to automatically clear the recent documents shortcuts list, here is
the
solution:

Create a text file named "Clear Recent Docs.txt" (for example), and
paste
in the following (using a pure text editor like Notepad), and then
rename
it to "Clear Recent Docs.reg" and double click it to enter it into
ther
registry.

Windows Registry Editor Version 5.00



[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"ClearRecentDocsOnExit"=dword:00000001

I've been using this for quite awhile, as I got tired of seeing that
recent documents list all the time. After rebooting, it automatically
gets
cleared. :-)

Hum...Ok thanks Bill I entered the text into notepad and saved as
"rdoc.reg" and notepad saved a regdit file. I loaded and rebooted
twice
those entries are still there. Everything I've open and it can
sometimes
be
a long list. It is a pain to erase every one.

Bill

I noticed I had updated mine a bit and the complete one was as follows.
If
this doesn't do it, I don't know what else to suggest. Again,this is
for
cleaning out the recents document list (which I found to be annoying)
for
Windows XP. (As always, it's always a good idea to save the original
one).

Windows Registry Editor Version 5.00



[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001
"ClearRecentDocsOnExit"=dword:00000001
"MaxRecentDocs"=dword:00000008

In message , Bill in Co
writes:
I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than a
dozen symbols with lower ASCII values. I sometimes find this handy when I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)
[]
In order:
space ! " # $ % & ' ( ) * + , - . / then 0. You can't use " * or / in
filenames, and normally, you can't _start_ one with a space.

(I too use ! at the beginning of names I want to appear first.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Knowledge isnt elitist - that's rubbish! Why are we embarrassed by the idea
that people know things? It's not a conspiracy against the ignorant. Knowing
things is good!" - Jeremy Paxman, RT 14-20 August 2010

J. P. Gilliver (John) wrote:
In message , Bill in Co
writes:
I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than a
dozen symbols with lower ASCII values. I sometimes find this handy when
I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)
[]
In order:
space ! " # $ % & ' ( ) * + , - . / then 0. You can't use " * or / in
filenames, and normally, you can't _start_ one with a space.

(I too use ! at the beginning of names I want to appear first.)

Yeah, me too. And if you think that's a bit unusual, I create a lot of zero
byte files with very long file names that are notes, instead of actually
creating a real text file and saving the actual note inside it. That way I
can see the "note" at a glance in the directory listings.

I guess the only penalty I'm paying for that is the extra directory entry
bytes required for the longish filename. I read that LFN entries are 32
bytes long, and each LFN directory entry has room for only 13 characters in
the file's name. So if you're creating a 40 character note, that means 4*32
bytes are being used for the LFN directory listing, if I understand this
correctly.

Windows "Long File Name" Specification:
http://www.fandecheng.com/personal/i...lp/lfnspec.htm

Bill in Co,

I believe that's because several alphanumeric symbols have
lower ASCII values than do the letters and numbers, which
all start at 30 hex

:-) "{", which I picked on purpose, has an ASCII value of 0x7B (above any of
the alphanumeric ones)

There are three groups above 0x30 containing non-alphanumeric symbols
(0x3A/6, 0x5B/5 and 0x7B/5). Regardless of that *all* of those
non-alphanumeric symbols are sorted below the "0" symbol ...

I sometimes find this handy when I name files and want to
"flag them" to show up first in the directory listings, to call
my attention to them. :-)

:-) Same here (mostly using "!", as that symbol is an attention-seeker by
itself). But sometimes I have temporary files (output of of some program or
another), which I would like to have stand-out, but way away from the (often
more permanent) "attention seekers". Which is how I came to notice this
unexpected sorting behaviour.

Regards,
Rudy Wieser


-- Origional message:
Bill in Co schreef in berichtnieuws
...
I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than a
dozen symbols with lower ASCII values. I sometimes find this handy when I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)

R.Wieser wrote:
Bill in Co,

... but since I was so used to the regular logical (ASCII) character
sort order for files, it drove me nuts.

Same here. Could not visually scan a folder (in XP) for a certain file
anymore, as the sought-for one could pop up in unexpected locations.
Drove me (sort of) mad. :-\

But even with that setting a folder seems to be sorted with all
non-alphanumeric symbols infront of alphanumeric ones (try a filename
starting with a "{" or "}" and you'll see what I mean).

Regards,
Rudy Wieser

P.s.
The other two registry entries are not bad either (understatement). :-)


-- Origional message:
Bill in Co schreef in berichtnieuws
...
Thanks again for the correction, and I hope it's not a problem for the
other
Bill that I added those in, as I found them useful. So Bill C, if you
don't
want the added stuff, hopefully you saved the original before adding
this
to
the registry and can go back.

Rudy - I think that change in sorting order came stock with XP and
later,
but since I was so used to the regular logical (ASCII) character sort
order
for files, it drove me nuts. But now I can't even remember what the
disadvantage of not using logical character sort order was (the way it
is
now in Vista and above). Well I found one example using these file
names:

Picture
Picture - Copy
Picture - Copy 2
Picture - Copy 3

which apparently gets sorted "incorrectly" using the newer method in
Windows
7 and later) as follows:

Picture - Copy 2
Picture - Copy 3
Picture - Copy
Picture

"Windows 7 treats blank spaces in file names illogically in
alphanumeric
sorts." URL: http://tinyurl.com/ya5bc29e

R.Wieser wrote:
Bill in Co,

"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001

Please do notice that the above three have nothing to do with "recent
documents".

And I definitily like that last one. It resolved a long standing
"what
the
heck?" about the sorting order of the files in a folder ...

Regards,
Rudy Wieser


-- Origional mesage
Bill in Co schreef in berichtnieuws
...
Bill Cunningham wrote:
"Bill in Co" wrote in message
...

I'm coming into this thread a bit late, but if you are looking for
a
way
to automatically clear the recent documents shortcuts list, here is
the
solution:

Create a text file named "Clear Recent Docs.txt" (for example), and
paste
in the following (using a pure text editor like Notepad), and then
rename
it to "Clear Recent Docs.reg" and double click it to enter it into
ther
registry.

Windows Registry Editor Version 5.00




[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"ClearRecentDocsOnExit"=dword:00000001

I've been using this for quite awhile, as I got tired of seeing
that
recent documents list all the time. After rebooting, it
automatically
gets
cleared. :-)

Hum...Ok thanks Bill I entered the text into notepad and saved as
"rdoc.reg" and notepad saved a regdit file. I loaded and rebooted
twice
those entries are still there. Everything I've open and it can
sometimes
be
a long list. It is a pain to erase every one.

Bill

I noticed I had updated mine a bit and the complete one was as
follows.
If
this doesn't do it, I don't know what else to suggest. Again,this is
for
cleaning out the recents document list (which I found to be annoying)
for
Windows XP. (As always, it's always a good idea to save the original
one).

Windows Registry Editor Version 5.00




[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001
"ClearRecentDocsOnExit"=dword:00000001
"MaxRecentDocs"=dword:00000008

In message , Bill in Co
writes:
J. P. Gilliver (John) wrote:
[]
(I too use ! at the beginning of names I want to appear first.)

Yeah, me too. And if you think that's a bit unusual, I create a lot of zero
byte files with very long file names that are notes, instead of actually
creating a real text file and saving the actual note inside it. That way I
can see the "note" at a glance in the directory listings.

Me too. For the same reason.

I guess the only penalty I'm paying for that is the extra directory entry
bytes required for the longish filename. I read that LFN entries are 32
bytes long, and each LFN directory entry has room for only 13 characters in
the file's name. So if you're creating a 40 character note, that means 4*32
bytes are being used for the LFN directory listing, if I understand this
correctly.

(Another penalty - of long names in general - is that the "columns"
format [most often seen in my case in the "file open" and "file save"
dialogue windows) has wide columns, so usually only one visible.)
Compared to video, picture, sound, or even Word files, I don't think we
need worry much about a few extra 128 bytes in directory files these
days!

Windows "Long File Name" Specification:
http://www.fandecheng.com/personal/i...lp/lfnspec.htm


--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"What happens if I press this button?" "I wouldn't ..." (pinggg!) "Oh!" "What
happened?" "A sign lit up, saying `please do not press this button
again'!"(s1f2)

Bill in Co,

I read that LFN entries are 32 bytes long, and each LFN
directory entry has room for only 13 characters in the file's
name.

LFN entries are actually just repurposed standard DOS 8.3 entries. IIRC
the OS detects a standard or an LFN entry by the first character of the
filename (the same way it detects "deleted" 8.3 entries).

Also, that problem only exist for FAT drives, onder, for example, NTFS its
just a single extra char (it uses another file-entry storage mechanism).

Regards,
Rudy Wieser


-- Origional message:
Bill in Co schreef in berichtnieuws
...
J. P. Gilliver (John) wrote:
In message , Bill in Co
writes:
I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than
a
dozen symbols with lower ASCII values. I sometimes find this handy
when
I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)
[]
In order:
space ! " # $ % & ' ( ) * + , - . / then 0. You can't use " * or / in
filenames, and normally, you can't _start_ one with a space.

(I too use ! at the beginning of names I want to appear first.)

Yeah, me too. And if you think that's a bit unusual, I create a lot of
zero
byte files with very long file names that are notes, instead of actually
creating a real text file and saving the actual note inside it. That way
I
can see the "note" at a glance in the directory listings.

I guess the only penalty I'm paying for that is the extra directory entry
bytes required for the longish filename. I read that LFN entries are 32
bytes long, and each LFN directory entry has room for only 13 characters
in
the file's name. So if you're creating a 40 character note, that means
4*32
bytes are being used for the LFN directory listing, if I understand this
correctly.

Windows "Long File Name" Specification:
http://www.fandecheng.com/personal/i...lp/lfnspec.htm

Rudy, I'm not familiar with that slash notation, like 0x3A/6 with the /6
there. So I know 3A hex is a colon in ASCII, but you're evidently talking
about something else, I presume?


R.Wieser wrote:
Bill in Co,

I believe that's because several alphanumeric symbols have
lower ASCII values than do the letters and numbers, which
all start at 30 hex

:-) "{", which I picked on purpose, has an ASCII value of 0x7B (above
any of the alphanumeric ones)

There are three groups above 0x30 containing non-alphanumeric symbols
(0x3A/6, 0x5B/5 and 0x7B/5). Regardless of that *all* of those
non-alphanumeric symbols are sorted below the "0" symbol ...

I sometimes find this handy when I name files and want to
"flag them" to show up first in the directory listings, to call
my attention to them. :-)

:-) Same here (mostly using "!", as that symbol is an attention-seeker by
itself). But sometimes I have temporary files (output of of some program
or
another), which I would like to have stand-out, but way away from the
(often
more permanent) "attention seekers". Which is how I came to notice this
unexpected sorting behaviour.

Regards,
Rudy Wieser


-- Origional message:
Bill in Co schreef in berichtnieuws
...
I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than a
dozen symbols with lower ASCII values. I sometimes find this handy when
I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)

R.Wieser wrote:
Bill in Co,

... but since I was so used to the regular logical (ASCII) character
sort order for files, it drove me nuts.

Same here. Could not visually scan a folder (in XP) for a certain file
anymore, as the sought-for one could pop up in unexpected locations.
Drove me (sort of) mad. :-\

But even with that setting a folder seems to be sorted with all
non-alphanumeric symbols infront of alphanumeric ones (try a filename
starting with a "{" or "}" and you'll see what I mean).

Regards,
Rudy Wieser

P.s.
The other two registry entries are not bad either (understatement). :-)


-- Origional message:
Bill in Co schreef in berichtnieuws
...
Thanks again for the correction, and I hope it's not a problem for the
other
Bill that I added those in, as I found them useful. So Bill C, if you
don't
want the added stuff, hopefully you saved the original before adding
this
to
the registry and can go back.

Rudy - I think that change in sorting order came stock with XP and
later,
but since I was so used to the regular logical (ASCII) character sort
order
for files, it drove me nuts. But now I can't even remember what the
disadvantage of not using logical character sort order was (the way it
is
now in Vista and above). Well I found one example using these file
names:

Picture
Picture - Copy
Picture - Copy 2
Picture - Copy 3

which apparently gets sorted "incorrectly" using the newer method in
Windows
7 and later) as follows:

Picture - Copy 2
Picture - Copy 3
Picture - Copy
Picture

"Windows 7 treats blank spaces in file names illogically in
alphanumeric
sorts." URL: http://tinyurl.com/ya5bc29e

R.Wieser wrote:
Bill in Co,

"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001

Please do notice that the above three have nothing to do with "recent
documents".

And I definitily like that last one. It resolved a long standing
"what
the
heck?" about the sorting order of the files in a folder ...

Regards,
Rudy Wieser


-- Origional mesage
Bill in Co schreef in berichtnieuws
...
Bill Cunningham wrote:
"Bill in Co" wrote in message
...

I'm coming into this thread a bit late, but if you are looking for
a
way
to automatically clear the recent documents shortcuts list, here is
the
solution:

Create a text file named "Clear Recent Docs.txt" (for example), and
paste
in the following (using a pure text editor like Notepad), and then
rename
it to "Clear Recent Docs.reg" and double click it to enter it into
ther
registry.

Windows Registry Editor Version 5.00




[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"ClearRecentDocsOnExit"=dword:00000001

I've been using this for quite awhile, as I got tired of seeing
that
recent documents list all the time. After rebooting, it
automatically
gets
cleared. :-)

Hum...Ok thanks Bill I entered the text into notepad and saved as
"rdoc.reg" and notepad saved a regdit file. I loaded and rebooted
twice
those entries are still there. Everything I've open and it can
sometimes
be
a long list. It is a pain to erase every one.

Bill

I noticed I had updated mine a bit and the complete one was as
follows.
If
this doesn't do it, I don't know what else to suggest. Again,this is
for
cleaning out the recents document list (which I found to be annoying)
for
Windows XP. (As always, it's always a good idea to save the original
one).

Windows Registry Editor Version 5.00




[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001
"ClearRecentDocsOnExit"=dword:00000001
"MaxRecentDocs"=dword:00000008

Bill in Co,

Rudy, I'm not familiar with that slash notation

My apologies. I used it to mark the number of symbols there. I should
maybe have just used 0x3A ... 0x3F, but thought I could "cut a corner" (with
the thought to be able to easily add the number of mis-sorted symbols
together). :-|

Regards,
Rudy Wieser


-- Origional message:
Bill in Co schreef in
berichtnieuws ...
Rudy, I'm not familiar with that slash notation, like 0x3A/6 with the /6
there. So I know 3A hex is a colon in ASCII, but you're evidently talking
about something else, I presume?


R.Wieser wrote:
Bill in Co,

I believe that's because several alphanumeric symbols have
lower ASCII values than do the letters and numbers, which
all start at 30 hex

:-) "{", which I picked on purpose, has an ASCII value of 0x7B (above
any of the alphanumeric ones)

There are three groups above 0x30 containing non-alphanumeric symbols
(0x3A/6, 0x5B/5 and 0x7B/5). Regardless of that *all* of those
non-alphanumeric symbols are sorted below the "0" symbol ...

I sometimes find this handy when I name files and want to
"flag them" to show up first in the directory listings, to call
my attention to them. :-)

:-) Same here (mostly using "!", as that symbol is an attention-seeker
by
itself). But sometimes I have temporary files (output of of some
program
or
another), which I would like to have stand-out, but way away from the
(often
more permanent) "attention seekers". Which is how I came to notice
this
unexpected sorting behaviour.

Regards,
Rudy Wieser


-- Origional message:
Bill in Co schreef in berichtnieuws
...
I believe that's because several alphanumeric symbols have lower ASCII
values than do the letters and numbers, which all start at 30 hex. The
digit "0" has a value of 30 hex or 48 decimal, and there are more than
a
dozen symbols with lower ASCII values. I sometimes find this handy
when
I
name files and want to "flag them" to show up first in the directory
listings, to call my attention to them. :-)

R.Wieser wrote:
Bill in Co,

... but since I was so used to the regular logical (ASCII) character
sort order for files, it drove me nuts.

Same here. Could not visually scan a folder (in XP) for a certain file
anymore, as the sought-for one could pop up in unexpected locations.
Drove me (sort of) mad. :-\

But even with that setting a folder seems to be sorted with all
non-alphanumeric symbols infront of alphanumeric ones (try a filename
starting with a "{" or "}" and you'll see what I mean).

Regards,
Rudy Wieser

P.s.
The other two registry entries are not bad either (understatement).
:-)


-- Origional message:
Bill in Co schreef in berichtnieuws
...
Thanks again for the correction, and I hope it's not a problem for
the
other
Bill that I added those in, as I found them useful. So Bill C, if
you
don't
want the added stuff, hopefully you saved the original before adding
this
to
the registry and can go back.

Rudy - I think that change in sorting order came stock with XP and
later,
but since I was so used to the regular logical (ASCII) character sort
order
for files, it drove me nuts. But now I can't even remember what the
disadvantage of not using logical character sort order was (the way
it
is
now in Vista and above). Well I found one example using these file
names:

Picture
Picture - Copy
Picture - Copy 2
Picture - Copy 3

which apparently gets sorted "incorrectly" using the newer method in
Windows
7 and later) as follows:

Picture - Copy 2
Picture - Copy 3
Picture - Copy
Picture

"Windows 7 treats blank spaces in file names illogically in
alphanumeric
sorts." URL: http://tinyurl.com/ya5bc29e

R.Wieser wrote:
Bill in Co,

"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001

Please do notice that the above three have nothing to do with
"recent
documents".

And I definitily like that last one. It resolved a long standing
"what
the
heck?" about the sorting order of the files in a folder ...

Regards,
Rudy Wieser


-- Origional mesage
Bill in Co schreef in berichtnieuws
...
Bill Cunningham wrote:
"Bill in Co" wrote in message
...

I'm coming into this thread a bit late, but if you are looking
for
a
way
to automatically clear the recent documents shortcuts list, here
is
the
solution:

Create a text file named "Clear Recent Docs.txt" (for example),
and
paste
in the following (using a pure text editor like Notepad), and
then
rename
it to "Clear Recent Docs.reg" and double click it to enter it
into
ther
registry.

Windows Registry Editor Version 5.00





[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"ClearRecentDocsOnExit"=dword:00000001

I've been using this for quite awhile, as I got tired of seeing
that
recent documents list all the time. After rebooting, it
automatically
gets
cleared. :-)

Hum...Ok thanks Bill I entered the text into notepad and saved
as
"rdoc.reg" and notepad saved a regdit file. I loaded and rebooted
twice
those entries are still there. Everything I've open and it can
sometimes
be
a long list. It is a pain to erase every one.

Bill

I noticed I had updated mine a bit and the complete one was as
follows.
If
this doesn't do it, I don't know what else to suggest. Again,this
is
for
cleaning out the recents document list (which I found to be
annoying)
for
Windows XP. (As always, it's always a good idea to save the
original
one).

Windows Registry Editor Version 5.00





[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explor
er]
"NoDriveTypeAutoRun"=dword:00000091
"CDRAutoRun"=hex:00,00,00,00
"NoStrCmpLogical"=dword:00000001
"ClearRecentDocsOnExit"=dword:00000001
"MaxRecentDocs"=dword:00000008