>I remember looking at FindExecutable() while working on the ShellExecute wrapper not sure why I didn't go ahead and wrap it too or stuff it into the dfwinapi.hlp file, maybe next release. *s*

I think you ought to. Just because a file has a particular extension doesn't mean that the user is running the expected program with it. I think it'd make a good addition.

>It must be looking in the registry because that's where 99.99% of that stuff is stored. But there may be older apps out there that directly write the win.ini without making a registry entry. I guess FindExecutable() may deal with that too by knowing what's in the [Extensions] section. I don't have time to test that right now.

What brought this to mind was some recent playing around with the GetPrinter() API function I've done. I noted that the registry contains a DevMode entry. This, I think, corresponds with the PRINTER_INFO_2 structure which has a DEVMODE structure as one of its members. When I saw that registry entry, it made me think that there probably a number of functions that read and write directly to it, elminating the need to use the registry functions all the time.