(EV) Message Catalog missing FATAL error mesage

Surrender. Logging calls replaced, message catalog removed.

I moved the registry handling for the event log DLL to the shibd.exe component, pending testing.

The logging calls don't always produce any output because of timing issues with the libraries, but some of the major ones show up.

After discussion, Windows wins, we'll just yank out the dedicated logging code in the modules and send it back through log4shib. The only practical effect should be that shibd service messages don't show up in the log, but that's just more consistent with the rest of the logging on that side anyway.

This is totally mystifying. Same code in all the components, but shibd LogEvent calls are parsed fine while this one is claiming the code's not in the message DLL.

I can't find anything online about decompiling or interrogating the DLL somehow to read the table, that seems like the obvious next step.

I'm going to commit a change to get the Native module codes starting from 300 instead of having them renumber from 0.

I reproduced it locally. It's some kind of issue I caused and didn't notice because I hadn't updated my messages.dll, so weirdly the old messages.dll I was using lines up with what the code's doing, but the new one doesn't. It's these crazy codes it generates and how it reverses all that bitmasking.

Anyway, not installer related, most likely.

I may not have tested the new module's logging, I'll review that before I do a full build and test the installer. The old module's shutdown message was event ID 207, FWIW, and was handled by my registry entries.