> Actually, looking at the code, the only thing init_mac_world() > does for Carbon MacPython is call InitCursor(). Could this > really be the problem? Not for MacCvs, but we are Carbon only. It could be a bigger problem on Classic to call InitGraf twice. It is right MacCvs initializes Python very early, so probably the multiple calls to InitCursor do not matter. Alex.