G
Guest
When I click Properties of a random shortcut and then click 'Find Target' button nothing happens
R
Ramesh [MVP]
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
D
David Candy
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
R
Ramesh [MVP]
I saw an Internet Download
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
D
David Candy
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
R
Ramesh [MVP]
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
D
David Candy
I have a batch file that echo's %1 then Pauses. I have a regentry c:\idlist.bat %I (that's % eye) applied to AllFileSystemObjects. So I r/c and choose IDLIST and a cmd window opens with the number. It a different number each time a object comes into existance. I choose a file on the desktop as it stays constant till logoff or a crash happens as the Desktop folder is always open.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
R
Ramesh [MVP]
Very well explained, D. (Prof.D) And I didn't know it was in the Desktop.
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
I have a batch file that echo's %1 then Pauses. I have a regentry c:\idlist.bat %I (that's % eye) applied to AllFileSystemObjects. So I r/c and choose IDLIST and a cmd window opens with the number. It a different number each time a object comes into existance. I choose a file on the desktop as it stays constant till logoff or a crash happens as the Desktop folder is always open.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
I have a batch file that echo's %1 then Pauses. I have a regentry c:\idlist.bat %I (that's % eye) applied to AllFileSystemObjects. So I r/c and choose IDLIST and a cmd window opens with the number. It a different number each time a object comes into existance. I choose a file on the desktop as it stays constant till logoff or a crash happens as the Desktop folder is always open.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
D
David Candy
It would have worked elsewhere as long as I had a window open on it.
--
----------------------------------------------------------
And the band played ....
http://www.smh.com.au/articles/2004/05/14/1084289883713.html
Very well explained, D. (Prof.D) And I didn't know it was in the Desktop.
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
I have a batch file that echo's %1 then Pauses. I have a regentry c:\idlist.bat %I (that's % eye) applied to AllFileSystemObjects. So I r/c and choose IDLIST and a cmd window opens with the number. It a different number each time a object comes into existance. I choose a file on the desktop as it stays constant till logoff or a crash happens as the Desktop folder is always open.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
--
----------------------------------------------------------
And the band played ....
http://www.smh.com.au/articles/2004/05/14/1084289883713.html
Very well explained, D. (Prof.D) And I didn't know it was in the Desktop.
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
I have a batch file that echo's %1 then Pauses. I have a regentry c:\idlist.bat %I (that's % eye) applied to AllFileSystemObjects. So I r/c and choose IDLIST and a cmd window opens with the number. It a different number each time a object comes into existance. I choose a file on the desktop as it stays constant till logoff or a crash happens as the Desktop folder is always open.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Thanks again David. You said "explorer /IDLIST,:2888:1608 (which is a PDF file on my system)". I assume this is only a temporary reference/pointer (the IDLIST ## is valid till the container is open.)
Meanwhile, I tried:
I did a search keyword "NIKON" and it showed this folder in the Search Results pane. I opened it and it had this value:
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2164:1920,/S
Second time when I opened the same folder, using the same search keyword, this time the IDLIST ## has changed.
"D:\WINDOWS\Explorer.EXE" /IDLIST,:2032:1920,/S
On both the occasions, I used ProcExp. If this IDLIST ## is just a random number, I'm confusing myself how did you ascertain the IDLIST for a PDF folder/file in ur system
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Things only exist within the namespace when their containers are opened, either by programming or by opening a folder window. Therefore only things on the Desktop exist all the time (ie all the time you are logged in). Things in search don't exist because their containing folder isn't opened (which is why some multi operations don't work in search).
As a container is opened the objects are given ID numbers that last only as long as the container is opened. This is when it exists within the shell's namespace. However most programs don't use the shell's namespace but use traditional file paths.
-- [/QUOTE]
Exactly David, I saw that same dialog, when I removed the (default) value and set it to Null value. For the IDLIST, it's confusing how it works
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
Though very interesting (I found a dialog after I sent my last post) I used
explorer /IDLIST,:2888:1608 (which is a PDF file on my system) to see if the select is essential, disk chattered and no window appeared. When I closed a few other windows I saw an Internet Download dialog for this pdf file.
Therefore I am even more puzzled why the value would be needed for Find Target to work.
--
----------------------------------------------------------
And the band played ....
http://www.livejournal.com/users/aldon/74121.html
Open Registry Editor and navigate to:
HKEY_CLASSES_ROOT\Folder\shell\open\command
What does the (default) value read, in the right-pane?
Try the Folder association fix from here:
http://www.dougknox.com/xp/file_assoc.htm
G
Guest
The Default Value is
%SystemRoot%\Explorer.exe /idlist,%I,%
and I still have this problem
%SystemRoot%\Explorer.exe /idlist,%I,%
and I still have this problem
R
Ramesh [MVP]
Try changing the value to:
%SystemRoot%\Explorer.exe /idlist,%I,%L,%S
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
The Default Value is :
%SystemRoot%\Explorer.exe /idlist,%I,%L
and I still have this problem
%SystemRoot%\Explorer.exe /idlist,%I,%L,%S
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
The Default Value is :
%SystemRoot%\Explorer.exe /idlist,%I,%L
and I still have this problem
D
David Candy
%S is the ShowWindow state. It will be interpreted as 0 if absent which means Hide The Window. Normally it is the previous folder show state that is passed to a new folder. Explorer also saves it in it's settings but will never save anything other than Normal (it will never save maximise - just anticipating questions, however changing %S to 3 will force most explorer windows to Max).
Public Const SW_HIDE = 0
Public Const SW_MAXIMIZE = 3
Public Const SW_MINIMIZE = 6
Public Const SW_RESTORE = 9
Public Const SW_SHOW = 5
Public Const SW_SHOWDEFAULT = 10
Public Const SW_SHOWMAXIMIZED = 3
Public Const SW_SHOWMINIMIZED = 2
Public Const SW_SHOWMINNOACTIVE = 7
Public Const SW_SHOWNA = 8
Public Const SW_SHOWNOACTIVATE = 4
Public Const SW_SHOWNORMAL = 1
--
----------------------------------------------------------
And the band played ....
http://www.smh.com.au/articles/2004/05/14/1084289883713.html
Try changing the value to:
%SystemRoot%\Explorer.exe /idlist,%I,%L,%S
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
The Default Value is :
%SystemRoot%\Explorer.exe /idlist,%I,%L
and I still have this problem
Public Const SW_HIDE = 0
Public Const SW_MAXIMIZE = 3
Public Const SW_MINIMIZE = 6
Public Const SW_RESTORE = 9
Public Const SW_SHOW = 5
Public Const SW_SHOWDEFAULT = 10
Public Const SW_SHOWMAXIMIZED = 3
Public Const SW_SHOWMINIMIZED = 2
Public Const SW_SHOWMINNOACTIVE = 7
Public Const SW_SHOWNA = 8
Public Const SW_SHOWNOACTIVATE = 4
Public Const SW_SHOWNORMAL = 1
--
----------------------------------------------------------
And the band played ....
http://www.smh.com.au/articles/2004/05/14/1084289883713.html
Try changing the value to:
%SystemRoot%\Explorer.exe /idlist,%I,%L,%S
--
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k
---------------------------------------
What You Should Know About the Sasser Worm and It Variants:
http://www.microsoft.com/security/incident/sasser.asp
---------------------------------------
The Default Value is :
%SystemRoot%\Explorer.exe /idlist,%I,%L
and I still have this problem
G
Guest
Didn't worked
D
David Candy
I read your post. Don't put %S there. %S is only valid in the DDE key, which as I explained is the only one being used anyway. And it's 3 not %3 but put in %S (in DDE) which is the state of the previous folder.
G
Guest
I didn't undesrtand where exactly to put this value 3 ?