The function "Remove all virtual data upon exit" works well at most times, but sometimes it doesn't work.
I am using WinXP SP3. I has been facing this problem since I was using WinXP SP2.
Still I didn't encounter this problem in other computer.
When I launch the app, normally the "data" folder, which is in %AppData%/VOS or under the same diectory, will be locked by the app process. Still when I leave the app, opening the taskmgr, the app process "(Name).cameyo.exe" is still running and the "data" folder is still locked.
Then the "data" folder can't be deleted or moved. If it is in a removable drive, the drive can't be ejected.
Also, the problem mostly exists in file converters or large applications. I don't know if it affacts the result.
Here is the software that having problem when leaving.
You can always use custom event with taskkill in a batch file to close the applications that stall..
By the Way any program that lingers on your system is always a cause of consern simply put if the program doesn't shut down what else is it doing on your system?
I don't know either. What is the syntax in the custom event? For example, when I make 3RVX Portable, these will happen: 1. double-click in the windows explorer 2. In the taskmgr, 3RVX.cameyo.exe starts 3. Then after a very short time 3RVX.exe starts 4. Also in a very short time 3RVX.cameyo.exe killed automatically 5. Then the application, 3RVX launched. 6. Close the application 7. 3RVX.exe killed, but no 3RVX.exe appeared. The process "conime.exe" locked the data folder.
Another one is the Free YouTube to MP3 Converter: 1. double-click in the windows explorer 2. The process "Free YouTube to MP3 Converter.cameyo.exe" starts 3. FreeYouTubeToMP3Converter.exe starts 4. The second "Free YouTube to MP3 Converter.cameyo.exe starts, but in a short time it stops 5. The application launched. In the taskmgr there are two process, Free YouTube to MP3 Converter.cameyo.exe and FreeYouTubeToMP3Converter.exe. 6. Close the application 7. The process "Free YouTube To MP3 Converter.cameyo.exe" didn't stop and locked the data folder.
The final one is the Freemake Video Converter. It is similar as the Free YouTube MP3 Converter, but only one Freemake Video Converter.cameyo.exe will start and won't stop.
Sorry. The problem still exists. Can someone give me some help? I found that some of the applications work will. The process "appname.cameyo.exe" will start first, and then"appname.exe" starts while "appname.cameyo.exe" stops. This is the normal situation. However, for some applications, the process "appname.cameyo.exe" still remain after the main process starts, and it keeps running with 0% CPU usage. When I close the application, normally "appname.exe" will stop and then "appname.cameyo.exe" appears to finish the further action. However, the first "appname.cameyo.exe" won't end, and after I close the application, "appname.exe" stops and nothing will happen next. The process "appname.cameyo.exe" will lock the data file, which make the USB getting stuck and can't be ejected. Here is the information about my computer (by Speccy)
Operating System Microsoft Windows XP Home Edition 32-bit SP3 CPU Intel Pentium E2180 @ 2.00GHz 36 °C Conroe 65nm Technology RAM 2.00 GB Dual-Channel DDR2 @ 333MHz (5-5-5-15) Motherboard Gigabyte Technology Co., Ltd. 945GCM-S2L (Socket 775) Graphics JT166x1-2 (1024x768@60Hz) Intel 82945G Express Chipset Family Hard Drives 233GB Seagate ST3250820A (PATA) 36 °C Optical Drives ATAPI DVD A DH20A3S Audio Realtek High Definition Audio
Please help. This problem exists in some important app that makes me need to install the app instead of making it portable. Thanks for all of you.
Have you tried the -Stop parameter (appname.cameyo.exe -Stop from command line)? That should end all child processes and allow you to eject the USB drive.
It is ok to use the -Stop parameter, but the problem is that when I move the app to another computer, the shortcut will be invalid. So I perfer to use another method to cure the problem. Still I can't find the problem...
A future version of Cameyo will have the option of terminating specific processes that remain after the application is closed. For now, the -Stop parameter is probably the simplest workaround.
