[squeak-dev] problems with Windows 7 beta and Squeak-Etoys

Hi all,

yesterday I tried the current Etoys-version on Windows 7 beta and
unfortunately the vm got crashed. Do you have any ideas what I could do
about that?

Thanks,
Rita

--
Rita Freudenberg
FIN-ISG
Otto-von-Guericke-Universität Magdeburg
http://isgwww.cs.uni-magdeburg.de/isg/rita.html

Rita Freudenberg wrote:
> yesterday I tried the current Etoys-version on Windows 7 beta and
> unfortunately the vm got crashed. Do you have any ideas what I could do
> about that?

Send me the crash.dmp (in the vm directory). We've tried running Forums
on Windows 7 with no apparent problems so I'm a little surprised to hear
your report.

Cheers,
   - Andreas

Am 19.03.2009 um 15:47 schrieb Andreas Raab:

> Rita Freudenberg wrote:
>> yesterday I tried the current Etoys-version on Windows 7 beta and  
>> unfortunately the vm got crashed. Do you have any ideas what I  
>> could do about that?
>
> Send me the crash.dmp (in the vm directory). We've tried running  
> Forums on Windows 7 with no apparent problems so I'm a little  
> surprised to hear your report.

I'm sory I can't find a vm directory in the Etoys folder. Where should  
I look?

Rita
>
>
> Cheers,
>  - Andreas
>

Rita Freudenberg wrote:
In the place where the vm (Squeak.exe) lives. There is a file called
crash.dmp that gets written upon a VM crash. The VM will also tell you
where the dump has been written to, so if you can't find it, just have
it crash again and go to the location mentioned in the dialog.

Cheers,
   - Andreas

At Thu, 19 Mar 2009 14:16:08 -0700,
Andreas Raab wrote:
  I'm afraid that it is not as simple as it should be.  The Etoys on
Windows is installed into a normal place (C:\Program Files\Etoys\...)
and that is the location indicated when the VM crashes.  However,the
directory is 1) read-only and 2) such program files and directories
are protected by the OS so that the user process cannot mess with it.

By the mechanism introduced to Vista and Windows 7, such attempt to
write a file is simulated but actually done to a shadow directory.
Qwaq Forums log data, for example, goes to:

  C:\Users\ohshima\AppData\Local\VirtualStore\Program Files\Qwaq Forums

But for some reason, for the Etoys case, you can mess some files in
some ways (like saving the image and the shadow file does get updated)
but crash.dmp doesn't get updated for some reason.

So, Rita, here is what to do:

  - Uninstall Etoys.
  - Install Etoys via EtoysInstaller.exe.
  - When the installer asks you to specify the directory to install,
    specify something other location and make it not under C:\Program Files.
  - Launch Etoys and see if it crashes.  This time, the crash.dmp will
    be there.

-- Yoshiki

Yoshiki Ohshima wrote: Thanks Yoshiki! I did that and then tried to crash the VM again, but did
not succeed yet...
One thing I changed is that I copied the etoys.image file into the same
directory like the etoys.exe, because before I did that, when running
etoys.exe, I got the file browser to select an .image every time.

I will go on next week and try if I can reproduce the crash.

Rita

> -- Yoshiki
>
>  


--
Rita Freudenberg
FIN-ISG
Otto-von-Guericke-Universität Magdeburg
http://isgwww.cs.uni-magdeburg.de/isg/rita.html

At Fri, 20 Mar 2009 16:03:28 +0100,
Rita Freudenberg wrote:
  Oh ok, so it wasn't reliably crashing before.

> One thing I changed is that I copied the etoys.image file into the same
> directory like the etoys.exe, because before I did that, when running
> etoys.exe, I got the file browser to select an .image every time.

  Right.  The application icon in start menu has command line option
so that it can find the image, but if you double click the .exe, it
cannot.  I thought we could have ImageName spec in the .ini file but
it was not folded in.

> I will go on next week and try if I can reproduce the crash.

  Good luck!

-- Yoshiki