search for: winedvm

...n the previous run. On the first instance of run from boot, the program runs correctly, but if it is closed and later re-opened without re-booting the computer, it cannot access its data file because it says it is already in use. I notice that each time the program is run it creates a process 'winedvm.exe' which sleeps when the program is closed, therefore it does not release the data file. To run the program more than once during any work session, any existing instances of winedvm.exe have to first be killed. Is there any way of forcing wine to release the data file when the program is clo...

...les and dll files from the Norton Desktop program that was designed to run without an installer from Win 3.1 . For me this program has worked in all versions of Windows including XP and when running Wine in Ubuntu 10.04 it also worked. Now when I double click the exe I get an error message saying winedvm,exe must close and then the following diagnostic- 0000001c 0 0000001d wineconsole.exe 0000001e 0 0000001...

...ndows Home Premium as this does not have XP compatability mode. I therefore decided to attempt installation via Wine. I have downloaded the latest version of Wine and installed it. I used Wine to install the program with no problems. However, when I try to run the program I get the error message: Winedvm.exe has encountered a serious error and needs to close. We are sorry for the inconvenience. Here is the output from the terminal. Does this make sense to anyone? > tm2383 at tm2383-Aspire-5551:~$ wine /home/tm2383/.wine/drive_c/MolWorld/Mw5/mw5.exe > wine: Unhandled exception 0xc000008d at...

...x exits and wine continues to run the rest of the script with errors for the missing file. If I startup dosbox separately, mount the location and run that fragment of the script, the file is created and exists after the execution completes and dosbox shuts down. In the dosbox integration code for winedvm, I see "mount -z ..." dosbox commands but can't find docs describing what the -z flag does. The wine integration code builds up a dosbox config file executes dosbox then wipes out the file. Is there a workaround, or does anyone have any insight into what's might need to be change...