On February 2, 2006 at 12:38, mburwen said...
what is that registry entry?
You might find it easier to use a program designed for managing those registry entries rather than edit the registry entry yourself. A program that seems to be pretty good is "File type association editor" from
[Link: angelfire.com]In that program you would:
1) click on the entry for .pcf (which exists if you previously installed any version of PENG).
2) Click on the Edit button to bring up the "Edit file association" dialog.
3) In the "command verb" box type the name of the command as you want it to appear in the right click menu.
4) Click the browse button next to the "Command line" box and find and select the .exe file you use for unzipping.
5) Type a blank followed by "%1" after the .exe name within the command line box.
6) Click Add, then Close
7) Click Save changes in the main dialog.
If you prefer more complete control, you can create a .reg file with contents such as those listed at the bottom of this post (of course changing all names and paths to fit the way things are installed on your system.
If you have already installed any association for .pcf files you should first do two exports from the registry to start from the associations you already have:
First find and export HKEY_CLASSES_ROOT\.pcf
Th e first keyname below that (which is ProntoEdit NG.ConfigurationFile on my machine) tells you what to export second. So in my case the second export was
HKEY_CLASSES_ROOT\applications\ProntoProEdit NG.exe
Then edit that second exported .reg file to add or change things. If you just want to add or change keys, you can then double click the edited .reg file to merge it back to the registry.
If you need to delete parts of the file association, I find it easiest to edit the .reg file to exactly what I want to end up with, then use the registry editor to delete that whole section, then double click the .reg file to put the new content in. Otherwise the merge of new content with old content may not give you what you expect.
If I want the same associations on a few different computers (as I usually do) I prepare a single .reg file merging both the exports decribed above and use that to install the associations elsewhere.
In the following .reg file example, the first line tells which version of the Registry Editor this .reg is supposed to be compatible with.
The second section gives both the internal and user visible names for the type of file indicated by .pcf
The third section gives the icon for that type of file.
The fourth section gives the default command (used for double click).
The fifth section gives the open command details.
The last section gives the winzip command details.
In any of the quoted strings, you'll notice that each " or \ is preceeded by an extra \
Those extras are part of the text format of a .reg file. They are removed by the registry editor as it merges the content into the registry, but they must be there in order for the .reg file to be read correctly.
Note also that named entities, such as the descriptive file type or the commands themselves have both an internal name and a visible name. The visible name is optional and will match the internal name if omitted. For commands, things can get confusing if the internal names have blanks or are out of alphabetic sequence. For that reason, I often make short simple internal names different from the visible names. So instead of doing winzip the way I did below, I might have done it as:
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell\x1]
@="Open in Winzip"
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell\x1\Command]
@="C:\\Program Files\\WinZip\\WINZIP32.EXE \"%1\""
By doing that I've changed the internal name of this command from "winzip" to "x1" (which may make managing the rightclick menu sequence simpler) and I've changed the visible name from "winzip" to "Open in Winzip".
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.pcf]
@="ProntoProEdit.NG.ConfigurationFile"
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile]
@="ProntoProEdit NG Configuration File Document"
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\DefaultIcon]
@="C:\\ir\\Philips\\ProntoProEdit NG\\ProntoProEdit NGLOC.dll,1"
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell]
@="open"
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell\open]
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell\open\Command]
@="C:\\IR\\Philips\\ProntoProEdit NG\\ProntoProEdit NG.exe %1"
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell\winzip]
[HKEY_CLASSES_ROOT\ProntoProEdit.NG.ConfigurationFile\Shell\winzip\Command]
@="C:\\Program Files\\WinZip\\WINZIP32.EXE \"%1\""
Last edited by johnsfine
on February 2, 2006 13:31.