Update from server blows up.

Dwight Hughes dwighth at ipa.net
Sat Aug 7 02:28:04 UTC 1999

For Windows the latest Squeak VM is dated May 7, 1999:

And from ftp://st.cs.uiuc.edu/pub/Smalltalk/Squeak/2.4/
get Squeak2.4c.changes, Squeak2.4c.image, Squeak3D.dll, and

The 2.4 version release sequence is rather confusing - the original 2.4
(no letter) release thought it was a 2.3 image with no updates, and
would apply the wrong updates (this may be what your problem is - I
think the lower update numbers are from the 2.3 update stream). I forget
what the problem with 2.4a was, but you don't want it either. 2.4b is
fine, but 2.4c requires fewer updates to bring it current. Somewhere
along this path Squeak Central changed the numbering of their updates to
match that of their internal update stream -- originally they used a
different number sequence for externally released updates.

The last update (patch level if you wish) for a 2.4c image is 1209. You
can see this by selecting "help..." from the screen menu and then
selecting "about this system".

BTW, is Squeak Central still looking for an FTP site librarian? I would
be happy to help with getting this mess straightened out.

-- Dwight

David LeBlanc wrote:
> Hi;
> Thanks to all that replied!
> I downloaded a "squeak2.4.zip" from the squeak.org site in the last 2 days.
> This is the one that i'm having trouble updating. There are the usual 4
> files in it, and they are all dated 4/21/99, and the zip is 5,249kb in
> size. I ALSO downloaded a "squeak.exe" size 5,336kb, which has files dated
> 4/21/99 and 5/8/99. The change and image files in that zip are named
> squeak2.4b.changes and squeak2.4b.images. Is that 2.4b for beta or 2.4
> patch b? (I would appreciate it if one is going to have several version of
> files available, that they have the version number in the filename AND that
> patches be numbered (1 ... ) instead of using a letter like "c". That way
> if I found a file called squeak2.4.2 ("a" would be the 2.4 release I
> guess), i'd know I had the latest version/edit/patch.) IS there a way to
> determine the patch level in a running squeak? I would guess that would be
> hard unless you used the highest update # that image has had applied:
> 2.4.580 seems to be what is in the zip, and 2.4.658 would be what I have
> now, but I think the updates run into the 800's.
> After fossicking around in sqeak and on the swiki, I found out about "save
> updates on local disk" and tried that. I also stopped the update on the
> first debug box that came up. It was able to incorporate changes
> 581readNextUpdate-sw.cs through 658clonerfix3-8-tr.cs. "659" choked on a
> missing dictionary key and the debug log is herein included. Hopefully that
> will aid someone in figuring out what I might have done wrong or what is
> needed to fix things.
> All this happens on a Windows NT Workstation 4.0sp4 pentium pro 200mhz box
> w/256mb of memory.
> BTW, 2.4 seems much zippier than 2.3, and i've not even tried jitter yet!
> Please let me know what to do now folks :)
> Sincerely,
> Dave LeBlanc

More information about the Squeak-dev mailing list