CTL3D32.DLL

Had some problems recently and had to reformat my laptop.When I went to
reinstall both Dolphin versions 3 and 2, I got a message about the file
CTL3D32.DLL being the wrong version, in that it was only intended for winNT,
whereas I'm using win98. I continued with both installations, which seemed
to be succesful however this was not the case as I cannot access the CHB,
instead receiving an error about SmallInteger does not understand
readstream.

I seem to recall this problem occured for other user about the time of the
v3 release but unfortunatley I lost my newsgroup backups during my recent
problems.

So can someone tell me what the solution was.

thanks
spooky

Spooky,

> Had some problems recently and had to reformat my laptop.When I went to
> reinstall both Dolphin versions 3 and 2, I got a message about the file
> CTL3D32.DLL being the wrong version, in that it was only intended for
winNT,
Don't worry about the CTL3D32 error, you can safely ignore it. In fact it's
nothing to do with Dolphin at all but is brought up when the Wise installer
(that we used to package Dolphin 2.1 and 3) tries to do something with
CTL3D32. The other error you are getting is something different. You'll have
to post more details (like a walkback trace and what you were doing at the
time) if you need more help with this.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com

---
Visit the Dolphin Smalltalk WikiWeb
http://www.object-arts.com/wiki/html/Dolphin/FrontPage.htm
---

"Andy Bower" <[hidden email]> wrote in message
news:960d1b$is5js$[hidden email]...

>
> Don't worry about the CTL3D32 error, you can safely ignore it. In fact
it's
> nothing to do with Dolphin at all but is brought up when the Wise
installer
> (that we used to package Dolphin 2.1 and 3) tries to do something with
> CTL3D32. The other error you are getting is something different. You'll
have
> to post more details (like a walkback trace and what you were doing at the
> time) if you need more help with this.
>

thanks Andy, before I got your message I had searched the web and found the
correct .dll file. I uninstalled both versions, installed the new .dll file
and reinstalled both versions, this went fine and after installation they
were both working fine until I installed my backup images.

Now v2.1 was still giving me the same error message. But v3 seemed to be
okay. I uninstalled 2.1 again and reinstalled again and this time when I
installed my image it worked okay. So I seem to have them both installed and
working fine. I'll need to play about a bit more to make totally sure.

I have one small query left. I had it noted that I had version 3.06, before
all my problems. On installation the About screen told me I had v3.05, I
tried to do a live update and it told me I could install pl1 and pl2 but it
wouldn't let me, saying I already had them installed. I then installed my
backup image and now it tells me I'm at v3.05 pl5. Asking for a live update
from this level tells me there are no updates available. I could have sworn
I was at v3.06. Any comments? I can't find anything about v3 on the OA site
now.

thanks

Scott,

> I have one small query left. I had it noted that I had version 3.06,
before
> all my problems. On installation the About screen told me I had v3.05, I
> tried to do a live update and it told me I could install pl1 and pl2 but
it
> wouldn't let me, saying I already had them installed. I then installed my
> backup image and now it tells me I'm at v3.05 pl5. Asking for a live
update
> from this level tells me there are no updates available. I could have
sworn
> I was at v3.06. Any comments? I can't find anything about v3 on the OA
site
> now.

There was a problem in version 3 where the version of the plug-in (if you
have it installed) could interfere with the version displayed by the
development system. If you are using the plug-in then make sure you install
this first followed by the development system. Also check the version that
the setup program displays during installation to make sure you really have
got the 3.06 installer.

This problem is fixed in v4.0 BTW :-)

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com

---
Visit the Dolphin Smalltalk WikiWeb
http://www.object-arts.com/wiki/html/Dolphin/FrontPage.htm
---

"Andy Bower" <[hidden email]> wrote in message
news:961368$j1b69$[hidden email]...

> There was a problem in version 3 where the version of the plug-in (if you
> have it installed) could interfere with the version displayed by the
> development system. If you are using the plug-in then make sure you
install
> this first followed by the development system. Also check the version that
> the setup program displays during installation to make sure you really
have
> got the 3.06 installer.

sorted,  thanks, I did have the plugin installed, so I
uninstalled/reinstalled again and I'm now back to v3.06 pl5.

>
> This problem is fixed in v4.0 BTW :-)
>

had a feeling you might say that ;o)  To be honest I was a bit confused by
the pricing when it first came out, although having looked again I see there
are upgrader prices which I understand better this time. My last message to
the old Dolphin newsgroup was over a year ago at which stage I was just
about to go and do a Java course, so I haven't been playing with Dolphin at
all since then. So I did the Java (yuk!!) and now I'm coming back to
Dolphin. At the moment I can't justify the upgrade to the wife as I don't
use it that much but we'll see what happens. Shame you couldn't get the OU
to adopt it, you would develop a lot of interest if that happened. It is a
distant goal of mine to tutor on the OU M206 Smalltalk course so if I ever
do I'll put in a good word.

regards
spooky
www.spookySpace.co.uk

(got confused as to who I was in the last message, but I'm okay again now
;o)

"Andy Bower" <[hidden email]> wrote in message
news:960d1b$is5js$[hidden email]...
> Spooky,
>
> > Had some problems recently and had to reformat my laptop.When I went to
> > reinstall both Dolphin versions 3 and 2, I got a message about the file
> > CTL3D32.DLL being the wrong version, in that it was only intended for
> winNT,
> > whereas I'm using win98. I continued with both installations, which
seemed
> > to be succesful however this was not the case as I cannot access the
CHB,
> > instead receiving an error about SmallInteger does not understand
> > readstream.
> >
> > I seem to recall this problem occured for other user about the time of
the
> > v3 release but unfortunatley I lost my newsgroup backups during my
recent
> > problems.
> >
> > So can someone tell me what the solution was.
>
> Don't worry about the CTL3D32 error, you can safely ignore it. In fact
it's
> nothing to do with Dolphin at all but is brought up when the Wise
installer
> (that we used to package Dolphin 2.1 and 3) tries to do something with
> CTL3D32. The other error you are getting is something different. You'll
have
> to post more details (like a walkback trace and what you were doing at the
> time) if you need more help with this.

Version 3 Dolphin.exe, DolphinCR993.dll, DolphinDR993.dll, and
DolphinVM993.dll do not show any references to CTL3D32.dll in Dependency
Walker. Why is it installed?

John Keenan

John,

> Version 3 Dolphin.exe, DolphinCR993.dll, DolphinDR993.dll, and
> DolphinVM993.dll do not show any references to CTL3D32.dll in Dependency
> Walker. Why is it installed?

The Dolphin VM is not an abstraction layer.  Most of Dolphin's external
interfacing is done in the image and is invisible to the MS dependency tool.
CTL3D32.dll is used for the GUI; see CommCtrlLibrary for details.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Bill Schwab"  wrote:
> The Dolphin VM is not an abstraction layer.  Most of Dolphin's external
> interfacing is done in the image and is invisible to the MS dependency
tool.
> CTL3D32.dll is used for the GUI; see CommCtrlLibrary for details.

CommCtrLibrary is for COMCTL32.dll. I do not see any references to
Ctl3d32.dll from Dolphin and an still curious why is is installed.

John Keenan

John,

> > The Dolphin VM is not an abstraction layer.  Most of Dolphin's external
> > interfacing is done in the image and is invisible to the MS dependency
> tool.
> > CTL3D32.dll is used for the GUI; see CommCtrlLibrary for details.
>
> CommCtrLibrary is for COMCTL32.dll. I do not see any references to
> Ctl3d32.dll from Dolphin and an still curious why is is installed.

I stand corrected; but, the image uses COMCTL32.dll and it depends on
CTL3D32.dll - at least I *think* it does :)  So, it looks like CTL3D32.dll
is installed because it is required by a DLL that the image uses.  Do you
agree?

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Bill Schwab"  wrote:
> I stand corrected; but, the image uses COMCTL32.dll
> and it depends on CTL3D32.dll - at least I *think* it
> does :)  So, it looks like CTL3D32.dll is installed
> because it is required by a DLL that the image uses.
> Do you agree?

No. A clean install of Windows NT 4.0 with its latest service pack, IE 5.5
and its latest service pack, and critical updates results in a system with
no ctl3d32.dll. Furtheremore, as a result of a non-Dolphin related problem I
removed *all* copies of ctl3d32.dll from my desktop system (different
machine but same Window's software as mentioned above) several months ago
and verified there are no references to ctl3d32.dll in the registry. I have
not experienced any problems as a result of this action (including Dolphin).
On an NT 4.0 system I am quite sure ctl3d32.dll is simply not needed and in
fact some grief can be avoided by not having it installed.

John Keenan

John,

> No. A clean install of Windows NT 4.0 with its latest service pack, IE 5.5
> and its latest service pack, and critical updates results in a system with
> no ctl3d32.dll. Furtheremore, as a result of a non-Dolphin related problem
I
> removed *all* copies of ctl3d32.dll from my desktop system (different
> machine but same Window's software as mentioned above) several months ago
> and verified there are no references to ctl3d32.dll in the registry.

The registry is not the only place such references can occur though.  On my
Win9x box at work, the dependency is among DLLs independent of COM or other
users of the registry; it's a plain old linker issue.


> I have
> not experienced any problems as a result of this action (including
Dolphin).
> On an NT 4.0 system I am quite sure ctl3d32.dll is simply not needed and
in
> fact some grief can be avoided by not having it installed.

If it's truly not used on NT (at whatever patch level), I doubt that it's
the problem.  I would sooner suspect that the product involved in the
non-Dolphin problem did something wrong.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]