The new version of CoLib has been released in the new MASM32 Service Pack 2. This Service Pack also includes windows.inc version 1.25, which is by and large it is compatible with CoLib. CoLib 1.1 has some much needed improvements in the original lib (i.e., I found a few bugs). I also added the scripter tut. I'm currently building my current project with windows.inc version 1.25, and only found TWO lines that may cause trouble. If you don't comment out lines 26756 and 26757 of version 1.25, your COM app MUST include a ClassMap. It may be NULL, but the symbol must be defined. This applies to any app that includelib CoLib.lib. It seems these two lines (DllGetClassObject and DllCanUnloadNow proto's) force the linker to add the modules for these procedures even if nothing else references them, and DllGetClassObject needs a ClassMap. That behavior of the linker is quite unexpected from me, and needs further search (it may be bloating all our apps with extraneous lib code). I hope this helps you.
Thanks for heads up Ernie, and the bug fixes! What is the purpose of these lines in bstrRight.asm:
Is a BSTR the same as a UNICODE string? bitRAKE
; check start param mov eax, dwCCount .IF dwCCount > eax ; adjust the count mov dwCCount, eax .ENDIF