Is your OS XP SP3 x86? If not, please advise OS, Service Pack, and architecture, e.g. Win7 SP1 x64.
Sorry i forgot to specify the OS.
I am trying Cameyo v2.5.1153 in Windows 7 SP1 x64 running in a VMware virtual machine.
I can also try it in XP Sp3 x86 if you think that may help.
Thanks.
Edit:
The app i packaged and tested in windows7 SP1 x64 was tested to run in XP Sp3 X86 and the result is the same - configuration changes are lost after app restart.
-- Edited by lsaca on Sunday 22nd of December 2013 04:08:47 PM
I was able to reproduce on XP but not Win7--that is why I asked if you were using XP.
When you tried the package built by Cameyo-2.5.1153, did you restore your VM to its state before having launched the package created by build 1145? If not, please run your package with -Remove parameter to start over, so to speak, and then relaunch package, make configurations, exit app, wait several seconds, and launch again to see if settings are retained.
The Volatile virtual registry is new to Cameyo 2.5 and affects Win7 and above. In previous versions of Cameyo (and still on XP), the package's registry is extracted to HKCU\Software\VOS\%AppID%. This extraction doesn't occur with Cameyo 2.5 on Win7 and above if the Volatile virtual registry is used. You didn't uncheck this box, did you? Just as I can reproduce loss of the package's registry on XP, I can also duplicate if I uncheck the Volatile virtual registry box and run on Win7.
-- Edited by mule on Sunday 22nd of December 2013 11:58:52 PM
"When you tried the package built by Cameyo-2.5.1153, did you restore your VM to its state before having launched the package created by build 1145?"
Yes. I always restore the VM to a clean OS install snapshot after creating the packaged applications.
"The Volatile virtual registry is new to Cameyo 2.5 and affects Win7 and above. In previous versions of Cameyo (and still on XP), the package's registry is extracted to HKCU\Software\VOS\%AppID%. This extraction doesn't occur with Cameyo 2.5 on Win7 and above if the Volatile virtual registry is used. You didn't uncheck this box, did you?"
I tried all cases. With volatile virtual registry checked and unchecked, in win 7 SP1 x64 and XP SP3 x86 with two different packaged applications.
Always the same result - changed settings are not persistent.
I also tested the packaged applications in a non virtual Win 7 SP1 x64 machine with the same result.
Let me just note that when Volatile Virtual Registry is checked the VirtRegSync.export file is always 4 bytes in length.
When VVR is unchecked the VirtRegSync.export file contains registry settings and i could find by inspecting it's contents that changes
i made to the app settings where saved in the file.
So i guess the problem is when restarting the app those reg settings in the export file are not retrieved.
Can you upload your package to a file-hosting site and provide the url, along with directions of configurations to make that will be stored in the registry, so we can reproduce the problem on our side? or you can use WeTransfer, send to yourself, and post the link. If it is a package that you do not want to make available publicly, you can send me the link via private message.
PM received and you have a reply that includes a link to a package I built, which I would like you to test to see if you lose the skin change.
In regards to disabling "Check if new version is available," I wonder if this is a bug with KMPlayer because when I unchecked it during a regular install and opened the program again, the check was back....
"In regards to disabling "Check if new version is available," I wonder if this is a bug with KMPlayer because when I unchecked it during a regular install and opened the program again, the check was back...."
You are right. Unchecking "Check if new version is available" doesn't work also in a regular install. It is a KMplayer dysfunction.
However you may try changing Options - preferences (F2) - DVD settings - tab General - DVD Auto Resume - change to: Always start playback from the beginning.
This setting works in a regular install but fails in my tests with the packaged app.
Just downloaded your package and tried it out of the box in my virtual win7 SP1 64 system.
I changed the skin to Default.ksf and also the option: DVD Auto Resume - Always start playback from the beginning.
Relaunched your package the skin is back to (Built-in Skin) and the DVD option is back to Resume playback from the last scene.
Don't know if this is the expected behavior but the VirtRegSync.export file is always 4 bytes.
I also tested your package in my real win7 SP1 64 system with the same results.
I can't imagine what is the problem with my system or what i am doing wrong but if you have any idea i will be glad to test and help.
On my Win7 systems, a changed DVD Auto Resume setting is retained after exiting and relaunching.
As a troubleshooting measure, please try my package that you downloaded on your VM in Safe Mode. I'm referring to Win7 Safe Mode, not the package's parameter, -SafeMode. In my reply to your PM, I said I couldn't get your package to keep its settings; however, it does work as it should if I boot into Safe Mode.
Just tested your package in my virtual Win7 SP1 64 running in safe mode.
When launching the package i get twice a win error like this:
"Access violation at address 012956BF in module KMPlayer.exe
Read of address 00000000"
Note that the 1st address varies on each launch.
Closing the win error the package app launches.
After changing the skin, the DVD option and relaunching both changes are persistent.
Interesting that no VirtRegSync.export file exists in Changes dir.
I have also tested two of my cameyo 2.5.1154 packaged KMplayer: one with vvr checked and the other unchecked.
The win error also exists but on both cases the registry changes are persistent when running in safe mode.
That it works (better anyway) on your VM in Safe Mode indicates that a driver is conflicting with your package, and not only the operation of the package but also the creation of it since I was able to reproduce the behavior with the package you uploaded.
What do you have installed on your VM? Please include all programs even if they seem that they shouldn't cause a conflict or install a driver. You can use a program like WinAudit, Save as type Text (Unicode), upload it, and PM me the url.
Thanks for your help and info that pointed me to the conflicting source.
My virtual machine only has 2 non MS addictions. VMtools ans zonealarm antivirus and firewall.
My real machine also runs zonealarm.
After uninstalling zonealarm in my vm the registry changes in cameyo packaged apps are persistent.
It would be important to figure what exactly is conflicting between cameyo and zonealarm as this antivirus firewall app is used by many people.
I will try to do it and would appreciate any help on this.
Thanks, Lsaca, for reporting back. I installed ZoneAlarm Free Antivirus + Firewall v12.0.104 on Win7 x64 but was unable to reproduce the problem, i.e. my package worked as expected, and I was able to create a package that worked as expected.
During installation of ZoneAlarm, I set Application Control to Max Security mode. Are there any other settings that I should change to match your configuration?
Thank you again for your answer.
I think the problem is solved.
I upgraded my zonealarm installation and all is working now.
I apologize for all of this trouble but until now i had no problem with my old zonealarm installation so
for me it wasn't a possible cause. We are always learning !!!
I really don't like windows apps upgradings and installations.
That's why i love packaged apps and cameyo.
Lsaca, "we are always learning" applies to both you and me, and this exchange may help other users in the future. Thank you for going through all the steps I asked and diligently reporting back.
Thanks for supporting Cameyo, including your answers on the forum to other posts. We are a community.