>>BTW, I used your example of detecting whether or not DCOM was loaded as the basis for a function. I'm going to use this as part of a post setup executable, that'll install it if it isn't. So I need to thank you for that.
>
>Please do - I've been working on a generic fix as a post-setup executable off and on myself, and I'd recommend that you write yourself a RunOnce key to run anything needed after you install DCOM. Install DCOM silently, without allowing any user intervention, and force a reboot after it completes, relying on the RunOnce to start your 'post' Post-Setup' executable.
>
Hi Ed,

Thanks for the suggestion, I think that's how I'll approach it. The only changes I made (beyond those that simply reflect my coding standards) were to define NO_ERROR as zero, and to insert a call to the .CloseKey method. Other than that, nothing. As my Dad would say, "It took off a flew like a big bird".:-) Thanks again.