[Pharo-project] Errors after force quit on Windows
My image hung waiting on data from a socket, so I aborted via "End Task" in Windows 7. When I restarted it, I got "CannotDeleteFileException: Could not delete the old version of file Z:\Pharo-2.0-one-click.app\Contents\Resources\stdout" Then, when I went to save the image, it was complaining about the changes file: MultiByteFileStream(Object)>>primitiveFailed: MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primSize: MultiByteFileStream(StandardFileStream)>>size MultiByteFileStream(StandardFileStream)>>setToEnd ChangesLog>>assureStartupStampLogged Any ideas? Thanks, Sean -- View this message in context: http://forum.world.st/Errors-after-force-quit-on-Windows-tp4658575.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Sean P. DeNigris wrote
My image hung waiting on data from a socket...
A little more info... The image resided on a mapped network drive. When I tried to open it on my Mac, it worked fine, and when I copied it to C:\, it worked fine in Windows. The weird thing is that I successfully saved it a few times before it stopped working. -- View this message in context: http://forum.world.st/Errors-after-force-quit-on-Windows-tp4658575p4658576.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On 8 December 2012 22:12, Sean P. DeNigris <sean@clipperadams.com> wrote:
My image hung waiting on data from a socket, so I aborted via "End Task" in Windows 7. When I restarted it, I got "CannotDeleteFileException: Could not delete the old version of file Z:\Pharo-2.0-one-click.app\Contents\Resources\stdout"
Then, when I went to save the image, it was complaining about the changes file: MultiByteFileStream(Object)>>primitiveFailed: MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primSize: MultiByteFileStream(StandardFileStream)>>size MultiByteFileStream(StandardFileStream)>>setToEnd ChangesLog>>assureStartupStampLogged
Any ideas?
A well known windows issue that systems keeps lock on a file, when application which has ownership on it was terminated abruptly :) there are tools to find an offending process which keeps the file(s) locked. Also, unlike unix systems, an r/w permission to open single file can acquire only one process at a time.
Thanks, Sean
-- Best regards, Igor Stasenko.
participants (2)
-
Igor Stasenko -
Sean P. DeNigris