Hi ned

I do not understand what really happen because the KCP 0084 and 0085 
have been split exactly for this reason.
Apparently these are old files.
I still do not understand why the system is perfectly working when I 
load the KCP changesets from the KCP page.
Because it worked with all the images I tried during the last three 
weeks.

> OK, these two change sets should be used instead of updates
> 5304KCP85MoveToChangeSet and 5306KCP88FixChangeSet respectively.
>
> If you're interested, here's my notes on what was happening:
>
> Loading KCP84 switches the change set to KCP84 from what it had been.
>
> That is, after I load the single file, I end up with:
>
> ChangeSet current a ChangeSet named 5302KCP84ChangeSetCurrent
> Smalltalk changes a ChangeSet named New Changes
>
> So I manually did:
>
> ChangeSet current: Smalltalk changes
>
> Then:
>
> File in KCP-0085-MoveToChangeSet.3.cs (the original, 59442 byte one)
>
> Get a deprecated warning at the end of this load because the (old)
>
> ChangeSorter class>>newChangesFromStream:named:
> (which is still in context) calls Smalltalk newChanges:.
>
> which is now deprecated.
>
> BUT... this is really because the end didn't complete, since it hit a
> Deprecated warning in the middle!

But normally here you proceed and it should work.

I hope everything is ok now. I would like really to understand why the 
system did not
crash on me :(

Stef

>
> So I had to break up the change set into 2 pieces...
>
> -- 
> Ned Konz
> http://bike-nomad.com
> GPG key ID: BEEA7EFE
> <KCP0085b-nk.2.cs><KCP0085a-nk.2.cs>