[Vm-dev] behavior issues with windows vm?
John M McIntosh
johnmci at smalltalkconsulting.com
Mon Jun 29 17:24:11 UTC 2009
Ok to solve this I added to
who := Processor activeProcess.
(Delay forMilliseconds: 500) wait. who suspend.
messageStrm := WriteStream on: (String new: 1500).
who suspendedContext errorReportOn: messageStrm.
Clipboard default primitiveClipboardText: messageStrm contents.
who resume ]
forkAt: Processor lowIOPriority.
This showed that yes if you delete the class DosFileDirectory class,
why Window's won't love you...
On 19-Jun-09, at 1:28 AM, Andreas Raab wrote:
> My suspicion would be that this is because you saved the image on
> Mac/Unix thus the ActiveDirectoryClass is set to UnixFileDir and
> consequently fails on Windows. If you'd save the image on Windows it
> will likely show the same behavior on Mac/Unix. I still fail to see
> what this has to do with the Windows VM - file and directory
> operations *will* fail if unless you call FileDirectory>>startUp.
> - Andreas
John M. McIntosh <johnmci at smalltalkconsulting.com> Twitter:
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
More information about the Vm-dev