>>Hi Mark,
>>
>>Sorry if I didn't understand your question correctly. I wasn't exactly sure what was generating the dialog.
>>
>>I think my friend Ed has you on the right track. In fact, I was about to respond to your last message to him about the error you were getting and the 0xOD and 0x0D business, but he beat me to it.
>>
>>AFAIK, there is no way via an API function to do what you're trying to accomplish. I'm wondering, however, if there isn't a command line switch (such as /s) that will do this in silent mode, similar to REGSVR32. I know that there's are several command line switches.
>
>
>Thanks guys.
>The keybd_event tip works great. In order to get it to work right though I had to replace the 0x0D with 13 ( it didn't like 0x0D either). I also tried the /s switch which someone suggested on deja.com and that allows me to avoid having to answer the prompts at all. Better yet though, it just occured to me that rather than merge the reg file via regedit ( which I admit is a kluge) I could right a little function that you pass a reg filename to and it does a low level file read and merges the registry entries one line at a time using standard registry functions. I was just looking for a way to avoid hard coding a bunch of registry entries. Thanks again.

You're welcome Mark. Sure that wasn't dejavu.com?< bg > I don't know how much of a kludge using REGEDIT.EXE with the /s switch is. If you check your hard drive, I'm sure you'll find a bunch of reg files, and I'd guess that they were added to the registry the way you're doing it.

BTW, the problem with the 0xOD is that the system tries to interpret it as a hexidecimal value, and the "O" character isn't one. However, the compiler doesn't pick that up. It's not until the defined value is accessed in some way that an error is generated.