As I was saying over in
this thread, I often fix file-opening issues by turning off the "Use DDE" feature for that filetype.
Or, at least, I used to, back in the olden days. Before the dark times. Before Windows XP.
It seems that lately, in Windows XP, most of the filetypes where I used to do that, now don't allow me to do that.
Here's an example:
- I wanted to associate the file type CFG with UltraEdit. I specifically don't want to use DDE for this, I want it to open with a command line parameter.
- I doubleclick on a CFG file and it asks me which application. I pick UltraEdit from the list, and I check the box "Always use this application to open this type of file" or whatever the heck it says.
- I open an explorer window and go to Tools, Folder Options, File Types.
- I Locate the CFG file type, and hit "Advanced"
- I select the "Open" action and hit "Edit".
- The "Use DDE" checkbox is checked, and all the DDE conversation parameters are there below the checkbox.
- I uncheck it. The DDE conversation parameters disappear.
- I hit OK, OK, Close.
- If I now drill back down into the CFG file type, the "Use DDE" checkbox is checked again, and all the DDE conversation parameters are there.
What the heck? Why does it keep forcing DDE to be "on" for this file type?
Incidentally, the Classes tree in the registry for this file type says nothing about DDE. The .CFG extention looks like this:
[HKEY_CLASSES_ROOT\.cfg]
@="ft000004"
And the ft000004 file type looks like this:
[HKEY_CLASSES_ROOT\ft000004]
"EditFlags"=dword:00000000
"BrowserFlags"=dword:00000008
@=""
[HKEY_CLASSES_ROOT\ft000004\shell]
@="open"
[HKEY_CLASSES_ROOT\ft000004\shell\open]
[HKEY_CLASSES_ROOT\ft000004\shell\open\command]
@="\"C:\\Program Files\\Ultra Edit\\UEDIT32.EXE\" \"%1\""
WTF?
I've googled around, searched the MSKB, and I don't see anywhere that even recognizes this as a problem, let alone offers a solution. Maybe I'm using the wrong search terms. Anyway. Anyone have any ideas on this one?