Dolphin 4.01.3 Maintenance Release

Folks,

We've released a 4.01.3 Live Update patch to fix some problems in the
current release. You can read about the fixes at:

http://www.object-arts.com/Lib/Update/Dolphin/4.01/Object%20Arts%20Edition/P
L3.htm

The update can be installed, as usual, using the Live Update icon in the
System Folder. During installation you will be prompted with a message box
asking if you want to recompile methods that reference the
ERROR_NO_MORE_FILES constant. You should answer Yes to this prompt. Once
installed into your image, the update should announce itself as 4.01.3 in
the Dolphin splash screen.

IMPORTANT NOTE: Some of the fixes in this update (#179, #247, #248 and #257)
are to the Dolphin VM and Compiler DLLs and therefore cannot easily be
upgraded using Live Update. If you think you need these fixes then you must
download the full product from our downloads page and re-install (make sure
you save your current work as packages first). The current download is at
4.01.3 so does need Live Update to be run to bring it up to date.

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,

> IMPORTANT NOTE: Some of the fixes in this update (#179, #247, #248 and
#257)
> are to the Dolphin VM and Compiler DLLs and therefore cannot easily be
> upgraded using Live Update. If you think you need these fixes then you
must
> download the full product from our downloads page and re-install (make
sure
> you save your current work as packages first). The current download is at
> 4.01.3 so does need Live Update to be run to bring it up to date.

Is saving packages a precaution, or are you saying that that image has to be
rebuilt to use the new VM and compiler?

The description (257): "Floating point exceptions sometimes not raised
immediately" raises a question.  A little while ago, I was having some
problems with what might have been explained as recursive errors leading to
a meltdown, and I suspected floating point math was involved.  Any possible
connection?  The app in question got a LOT happier when I made the most
recent round of changes to avoid finalization of GDI objects, so the crashes
could simply have been due to instability in low resource conditions.
Still, your summary of the fixed bug has me wondering.

Thanks for the patches!

Have a good one,

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

"Andy Bower" <[hidden email]> schrieb im Newsbeitrag
news:9g55ti$7d6lr$[hidden email]...
> Folks,
>
> We've released a 4.01.3 Live Update patch to fix some problems in the
> current release. You can read about the fixes at:
>
>
http://www.object-arts.com/Lib/Update/Dolphin/4.01/Object%20Arts%20Edition/P
> L3.htm
>
> The update can be installed, as usual, using the Live Update icon in the
> System Folder. During installation you will be prompted with a message box
> asking if you want to recompile methods that reference the
> ERROR_NO_MORE_FILES constant. You should answer Yes to this prompt. Once
> installed into your image, the update should announce itself as 4.01.3 in
> the Dolphin splash screen.

Howdy Andy,

I applied the patch and it seems that it *is* applied, but the splash screen
continues to announce itself as 4.01.2  !?

Ingo

Ingo,

> I applied the patch and it seems that it *is* applied, but the splash
screen
> continues to announce itself as 4.01.2  !?

Sorry, our mistake, we forgot to get the patch to update the image patch
level. If you try a Live Update again now you should find that the patch
will "take" okay.

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
---

Bill,

> > IMPORTANT NOTE: Some of the fixes in this update (#179, #247, #248 and
> #257)
> > are to the Dolphin VM and Compiler DLLs and therefore cannot easily be
> > upgraded using Live Update. If you think you need these fixes then you
> must
> > download the full product from our downloads page and re-install (make
> sure
> > you save your current work as packages first). The current download is
at
> > 4.01.3 so does need Live Update to be run to bring it up to date.
>
> Is saving packages a precaution, or are you saying that that image has to
be
> rebuilt to use the new VM and compiler?

You only need to save your packages if you are using the Default.img since
this would be overwritten by a fresh install. If you want to continue to use
a differently named image (e.g. Bill.Img) then you can do so without
rebuilding it but you will need to run Live Update as well as installing the
new version. Does this make sense?

> The description (257): "Floating point exceptions sometimes not raised
> immediately" raises a question.  A little while ago, I was having some
> problems with what might have been explained as recursive errors leading
to
> a meltdown, and I suspected floating point math was involved.  Any
possible
> connection?  The app in question got a LOT happier when I made the most
> recent round of changes to avoid finalization of GDI objects, so the
crashes
> could simply have been due to instability in low resource conditions.
> Still, your summary of the fixed bug has me wondering.

I doubt this will fix the problem you saw. The fix is a result of the report
in the recent NG thread entitled "Assignment of Overflow" started on 5th
June.

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,

> > Is saving packages a precaution, or are you saying that that image has
to
> > be rebuilt to use the new VM and compiler?
>
> You only need to save your packages if you are using the Default.img since
> this would be overwritten by a fresh install. If you want to continue to
use
> a differently named image (e.g. Bill.Img) then you can do so without
> rebuilding it but you will need to run Live Update as well as installing
the
> new version. Does this make sense?

I think so.  I save to Dolphin.img, and in a well-removed directory, so that
should be ok.  Paraphrasing what I think you've said is that I should
LiveUpdate my image, and then install to refresh the DLLs.  At that point, I
should have all of the fixes.  Fair?  The default image will get clobbered,
but, that's not going to bother me - as you point out, it might bother other
users.

Have a good one,

Bill

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

Object Arts,

Thanks for the great support.

Keith Alcock


Andy Bower wrote: