Yes. If the MITKrb4 module registration is not present, then it will not be loaded.
Note that for the WiX installer, the registration info for the modules are part of the components that declare the module binaries. You will either have to remove or disable the entire component (which is what I think you want to do), or change the component GUID after removing just the registration info. If you are removing the component, don't forget to also remove the localization library (krb4_en_us.dll) and the corresponding debug information file (krb4cred.pdb) which are in different components. On Mon, Mar 31, 2008 at 9:17 AM, Kevin Koch <[EMAIL PROTECTED]> wrote: > Removing the plugin from the plugins page worked. > > Can you confirm that the Krb4Cred Plugin and MITKrb4 Module are the only > registry deletions needed in the installers? > > > Kevin > > -----Original Message----- > From: Jeffrey Altman [mailto:[EMAIL PROTECTED] > > Sent: Sunday, March 30, 2008 10:21 PM > To: [EMAIL PROTECTED] > Subject: Re: NIM plug-in loading question > > Go to the plugins page in NIM and disable it or remove it. > > Kevin Koch wrote: > > A KRB4 provider is probably the problem. By registered, do you mean a > > Krb4Cred entry in > HKLM/Software/MIT/Kerberos/NetIDMgr/PluginManager/Plugins? > > > > The release notes don't mention the HKLM/.../PluginManager/Modules > entries. > > Would I want to delete the MITKrb4 entry as well? > > > > > -----Original Message----- > > From: Jeffrey Altman [mailto:[EMAIL PROTECTED] > > > Sent: Sunday, March 30, 2008 10:32 AM > > To: [EMAIL PROTECTED] > > Cc: kfwdev@mit.edu > > > Subject: Re: NIM plug-in loading question > > > > > > Kevin Koch wrote: > >> Good point. For now, I'll continue trying to get it to work without any > >> KRB4 support. Later I'll turn the compile time condition into a run time > >> condition. > >> > >> With the changes in dynimport.c, NetIdMgr starts but one of the three > >> kmmint_plugin_broker threads calls krb4_cb which leads to an exception in > >> khm_krb4_set_def_tkt_string. Is another NO_KRB4 / No-KRB4-support > > condition > >> needed somewhere? > >> > >> Kevin > > Look at the #ifndef _WIN64 code blocks. It will be one of those. > > > > Although krb4_cb should not be called unless you are loading the krb4 > > provider. Make sure you don't have a krb4 provider registered on your > > system > > > > _______________________________________________ > kfwdev mailing list > kfwdev@mit.edu > http://mailman.mit.edu/mailman/listinfo/kfwdev > > _______________________________________________ kfwdev mailing list kfwdev@mit.edu http://mailman.mit.edu/mailman/listinfo/kfwdev
