Dear Robert, I removed the maps *.lcd: no solution. I cleaned my registry: no solution I restarted my computer: no solution ..... I became angry and I saved all disk*.* files, I installed Sage for Windows again and replaced the new disk*.* files with the old files
Guess what: problem solved! Maybe something for FAQ if people experience a SIGSEGV ERROR. Thanks for all your support. Roland On 3 dec, 05:45, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Dec 1, 2009, at 9:24 PM, dimpase wrote: > > > well, you probably just need to remove some stale locks. > > That is, somewhere on the VM, there is a place where files indicating > > "busy" status > > of a particular volume, so-called locks, are stored. On Windows hosts, > > they have .lck extensions. > > So you need to remove the one that is > > causing you the trouble. However, a VM reboot should have taken care > > of it. > > (YMMV: It has been ages since I worked with VMware, so I might sound > > vague on this) > > In other words, are there any .lck files sitting around your virtual > disks that you should delete, like a D:\Program Files\Sage\sage- > vmware-4.1\disk.vmdk.lck? . That alone might solve the problem. > > - Robert -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
