[squeak-dev] Image not startable after save
lists at fniephaus.com
Sat Jun 6 15:54:10 UTC 2020
On Sat, 6 Jun 2020 at 5:43 pm, Thiede, Christoph <
Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> Thank you, Jakob.
> Well, I have to revoke my previous success message. Restarting my image
> another time and it crashes again on startup ...
> But I have looked up my sources files. They do contain DisplayScreen class
> >> #startUp. And (Smalltalk class classVarNamed: #StartUpList) includes:
> #DisplayScreen. What could be the problem?
Wild guess: there's something wrong with the display form and the Windows
VM crashes before the beDisplay primitive is called with a fresh one. That
could explain why it works on macOS. I could have a look at the raw display
object if you provide an image.
> *Von:* Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im
> Auftrag von Jakob Reschke <forums.jakob at resfarm.de>
> *Gesendet:* Samstag, 6. Juni 2020 17:33:16
> *An:* The general-purpose Squeak developers list
> *Betreff:* Re: [squeak-dev] Image not startable after save
> Am Sa., 6. Juni 2020 um 17:25 Uhr schrieb Thiede, Christoph <
> Christoph.Thiede at student.hpi.uni-potsdam.de>:
>> How did you hit on that?
> That I tried the same copy of the VM from another folder at all is because
> I have the unpacked zips lying around and always copy the current VM that I
> use to a different folder, where the Windows file association looks for it.
> So when I switch VMs, I won't have to tell Windows again how to open these
> .image files...
> I compared the folders with a merge tool (after renaming my Squeak64.exe
> .ini and .manifest back). All the binary files are equal, and
> Monticello/Metacello cache folders, the default image and changes file,
> debug logs, and crash dumps aside, the only meaningful difference left was
> eventually the presence of the sources file.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev