Mailing List Archive

On Sun, 18 Apr 1999 01:33:46 GMT, hj_ka@my-dejanews.com <hj_ka@my-dejanews.com> wrote:
>I don't know whether this is also related: when I installed
>win32all-124.exe, I got a few warnings:
>
>"Registration of the (AXScript/Python Interpreter/Python Dictionary)
>failed. Installation will continue, but this server will require
>manual registration before it will function."

I had the same warnung and also cannot run the win32 extentions.
(import win32com.client e.g. fails for me.)

Mark Hammond suggested to update some DLLs and it might
very well be a problem related to old DLL version.
(I didn't manage for some reasons to update my DLLs here on my
Windows95 system, so I finally gave up. Any Windows Hacker with
experience in this speak up and offer help! ;-) )

Mark said, that the following dll and their versions might
be relevant:

ole32.dll
oleaut32.dll
msvcrt.dll

The following are used, but should be fine:
pywintypes15.dll
python15.dll
kernel32.dll
user32.dll

You can check the version number in the explorer im C:windows/system
with properties.

Maybe an upgrade package including these .DLLs from support.microsoft.com
can help.


Please report back, If you found a solution...

Bernhard

In article <slrn7hio0v.vlp.bernhard@alpha1.csd.uwm.edu>,
bernhard@alpha1.csd.uwm.edu (Bernhard Reiter) wrote:
>
> Mark said, that the following dll and their versions might
> be relevant:
>
> ole32.dll
> oleaut32.dll
> msvcrt.dll

No luck. I downloaded some more recent versions of ole32.dll
and oleaut32.dll from http://solo.abac.com/dllarchive/, (their
msvcrt.dll is older, from VC5 instead of VC6). I also tried
those DLLs from my Windows 98 System folder. I tried many
combinations. Here is the list of the versions:

msvcrt.dll:
5.00.7303 (solo.abac.com)
5.00.7128 (my Windows 98)
6.00.8267.0 (my Windows NT)

ole32.dll:
4.71.1120 (solo.abac.com)
4.71.1719 (my Windows 98)
4.00 (my Windows NT)

oleaut32.dll:
2.20.4122 (solo.abac.com)
2.20.4122 (my Windows 98)
2.20.4118 (my Windows NT)

I tried many combinations of the DLLs inside the
C:\Winnt\system32 folder. But they didn't help, and
matter of fact, they broke something else and I got
more error messages from the operating system.

NT has had persistent problem with the Pythonwin
extensions. This is not the first time. I have
never been able to run Pythonwin or use its
extensions modules (e.g: win32api, win32ui) on NT,
and we have quite a few NT machines here.

The current real status is: PYTHONWIN DOES NOT
RUN ON NT. At least not on modern NT versions
(our msvcrt.dll is dated 9/23/98, this should be
considered fairly recent.)

I am willing to track down the problem a bit more.
But help is needed from Mark or other people. I am
lost at this moment.

regards,

Hung Jung

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

On Sun, 18 Apr 1999 20:50:45 GMT, hj_ka@my-dejanews.com <hj_ka@my-dejanews.com> wrote:
>In article <slrn7hio0v.vlp.bernhard@alpha1.csd.uwm.edu>,
> bernhard@alpha1.csd.uwm.edu (Bernhard Reiter) wrote:

>> Mark said, that the following dll and their versions might
>> be relevant:

>No luck. I downloaded some more recent versions of ole32.dll
>and oleaut32.dll from http://solo.abac.com/dllarchive/, (their
>msvcrt.dll is older, from VC5 instead of VC6). I also tried
>those DLLs from my Windows 98 System folder. I tried many
>combinations.

Sad to hear.
As we both got that problem with unregistered services
when installing, I think somebody has to find out what that means.

I certainly do not know much about this in Windows.

Bernhard

Hung Jung writes:

> No luck. I downloaded some more recent versions of ole32.dll
> and oleaut32.dll from http://solo.abac.com/dllarchive/, (their
> msvcrt.dll is older, from VC5 instead of VC6). I also tried
> those DLLs from my Windows 98 System folder. I tried many
> combinations. Here is the list of the versions:
>
> msvcrt.dll:
> 5.00.7303 (solo.abac.com)
> 5.00.7128 (my Windows 98)
> 6.00.8267.0 (my Windows NT)
>
> ole32.dll:
> 4.71.1120 (solo.abac.com)
> 4.71.1719 (my Windows 98)
> 4.00 (my Windows NT)
>
> oleaut32.dll:
> 2.20.4122 (solo.abac.com)
> 2.20.4122 (my Windows 98)
> 2.20.4118 (my Windows NT)

...
> NT has had persistent problem with the Pythonwin
> extensions. This is not the first time. I have
> never been able to run Pythonwin or use its
> extensions modules (e.g: win32api, win32ui) on NT,
> and we have quite a few NT machines here.
>
> The current real status is: PYTHONWIN DOES NOT
> RUN ON NT. At least not on modern NT versions
> (our msvcrt.dll is dated 9/23/98, this should be
> considered fairly recent.)

While I'm still on 1.5b2 and build 123 of Mark's stuff, I've had no
problem on NT SP3 and 4. My versions:

msvcrt.dll v 5.00.7303
ole32.dll v 4.00
oleaut32.dll v 2.30.4265

I have (some time ago) had problems with the "not registered"
messages on install, but they went away when I de-installed the
extensions, de-installed Python then reinstalled Python and the
extensions.

(However, to get IE 4 to install, I had to de-install almost
everything network related...)

Just to make sure you haven't overlooked anything basic, you do
realize that you have to have administrative priveleges to install
the extensions?

In a direct reply, I'll attach a copy of the HKLM\Software\Python
portion of my registry.

- Gordon

Gordon McMillan wrote in message <1287633267-17041836@hypernet.com>...
> msvcrt.dll v 5.00.7303
> ole32.dll v 4.00
> oleaut32.dll v 2.30.4265

Mine for NT are identical, except msvcrt, where Gordon's is MSVC 5 and mine
is MSVC6. Build 124 will install MSVC6 DLLs, and Gordon stated he isnt
there yet.

For Windows 98, I have:
ole32.dll 4.71.26.12
oleaut32.dll 2.30.4261


What I know is:
* Anyone who sees during installation something like "The COM object could
not be registered" will have some problem once installed. This problem can
be boiled down to:
- "import pythoncom" fails - COM wont work, but most other things will.
- "import pywintypes" fails - almost every other "import win32*" statement
will also fail. Almost nothing installed will work correctly.

My anecdotal evidence so far is:
* Many people who encounter this error do so because old versions of
pythoncom15.dll and pywintypes15.dll are still hanging around. I dont
understand why the installer is doing this to me :-(
* Almost all the rest are solved by installing the OLE update referenced at
my pages, or installing IE4.
* Bernhard is the only other case. He seemed to have 1 machine where
ole32.dll was version 2, and whatever he did, the DLL could not be upgraded,
deleted or removed. We both gave up there.

No one else has given me any information to believe there is more to it than
that. If people have problems that can't be explained by the above, then I
really want to hear from them.

Ive attempted to put all this into a new "Installation Problems" document,
linked from the downloads page. The address is
http://starship.python.net/crew/mhammond/bigpond/InstallationProblems.html
for any constructuve (or otherwise :-) comments...

Mark.

From: "Mark Hammond" <MHammond@skippinet.com.au>
Subject: Re: NT: win32api and win32ui import error
Organization: Telstra Big Pond Cable - Sydney Site 1

Gordon McMillan wrote in message <1287633267-17041836@hypernet.com>...
> msvcrt.dll v 5.00.7303
> ole32.dll v 4.00
> oleaut32.dll v 2.30.4265

Mine for NT are identical, except msvcrt, where Gordon's is MSVC 5 and mine
is MSVC6. Build 124 will install MSVC6 DLLs, and Gordon stated he isnt
there yet.

For Windows 98, I have:
ole32.dll 4.71.26.12
oleaut32.dll 2.30.4261


What I know is:
* Anyone who sees during installation something like "The COM object could
not be registered" will have some problem once installed. This problem can
be boiled down to:
- "import pythoncom" fails - COM wont work, but most other things will.
- "import pywintypes" fails - almost every other "import win32*" statement
will also fail. Almost nothing installed will work correctly.

My anecdotal evidence so far is:
* Many people who encounter this error do so because old versions of
pythoncom15.dll and pywintypes15.dll are still hanging around. I dont
understand why the installer is doing this to me :-(
* Almost all the rest are solved by installing the OLE update referenced at
my pages, or installing IE4.
* Bernhard is the only other case. He seemed to have 1 machine where
ole32.dll was version 2, and whatever he did, the DLL could not be upgraded,
deleted or removed. We both gave up there.

No one else has given me any information to believe there is more to it than
that. If people have problems that can't be explained by the above, then I
really want to hear from them.

Ive attempted to put all this into a new "Installation Problems" document,
linked from the downloads page. The address is
http://starship.python.net/crew/mhammond/bigpond/InstallationProblems.html
for any constructuve (or otherwise :-) comments...

Mark.



--
|Fidonet: UUCP 2:500/3.1
|Internet: UUCP@p1.f3.n500.z2.hccfido.hcc.nl
|
| Standard disclaimer: The views of this user are strictly his own.