The Very High Layer and friends

[Thomas S. Strinnhed]

Thank you, makes sense.

But how do I solve it? Can't really figure out from your reply if
the problem lies in python15.dll or elsewhere. Can it be "tracked"
in runtime?

Regards
 -- Thomas S. Strinnhed, thstr at serop.abb.se

Gordon McMillan wrote:
> 
> The most likely cause is mismatching c runtime libs. The stock
> python15.dll uses "Multithreaded DLL". You're using the right kind of
> FILE, but you've opened it in one c runtime lib, and the other ends
> up with a bad pointer.
> 
> - Gordon