[Richie] > It's possibly that it was an all-users installation but I > copied the DLL into C:\Python24 for some reason
[Martin] > Ah, ok. I could not have thought of *that*. That also explains it: the > upgrading simply did not manage to remove/replace your copy of > python24.dll. > > It's easy to see the effect, then: Windows looks for python24.dll first > in the directory of python.exe (where no DLL should have been found), > and would only fallback to system32 then (which it didn't in your case). Yes, that's what's happened. I've copied the new python24.dll into C:\python24, and everything now thinks it's 2.4.1c1. Sorry about that. (I wish I could remember why I'd copied the DLL, but I can't. I'd like to think there was a good reason. 8-) -- Richie Hindle [EMAIL PROTECTED] -- http://mail.python.org/mailman/listinfo/python-list