Ted,
I did not realize these were not PowerBuilder dlls, so I see where this creates some issues, especially as to ownership of issues that occur from those dlls.
I took a look at that link you provded, and it appears it was specifically relating to paths for those dlls, etc. So I went into my path, and made sure that MKS was at the end, and rebooted to ensure path was set.
I also ran both versions again with the process monitor ensuring that those dlls were being pulled from their own directories, and have verified that they are.
As for encryption, I would entertain this as a possibility if 9 were exhbiiting the same behavior, but it's not. And that encryption would be handled by MKS's SCC dll, would it not?
This all now begs the question... who takes ownership of the issues that arise from use of those dlls? Does SAP have the source code to these files, or are they redistributing them from some trusted source? Who is ultimately accountable and responsible when issues like these arise? How far does this rabbit hole go??
--Brian