Cameyo

seabhcan · Member

Issue with players on some PCs

betaleaf · Senior Member

Hello, can you use Cameyo Tracer and post a log below. It would also help if you sent us the package, either as a post below, or via PM to me or Mule. Mule is the support staff here and I just volunteer support.

www.cameyo.com/downloads/CameyoTracer.exe

seabhcan · Member

Hi Betaleaf,

Thanks for replying. I'll try this and post the results. I'll also upload the problem package and provide a link.

(I'm away from my PC at the moment, but will post this stuff tomorrow)

Thanks.

S

betaleaf · Senior Member

Sorry I gave you the wrong set of instructions. Cameyo Tracer doesn't output logs and is only useful if you know what you are doing. What you need to do is:

1. Run your package with the "-remove" flag. This will put the package in a clean state.
2. Run your package again, this time with the "-troubleshoot" flag. This basically turns on Cameyo Tracer in a log form.
3. Use the package normally until it no longer works normally.
4. Click Reproduce.
5. Upload the log file somewhere it can be shared to us.

I personally use GitHub these days to host files (including my website :D). To do this:

Go to github.com/new and create a repository with any name. For this example, I will assume you named the repository "FileStorage". Click Create Repository.
Next, click on "Releases" (Use your browser's search function (Ctrl+F) and search for "Releases" to find it easily.)
Next, click "Create a new release". If you already published your first release, you won't see this button and instead you need to click "Draft a new release" in the top right.
Set the tag version to any number. I would set this to 1 and increment it by 1 for every new release. The other fields are optional.
Upload any files you wish to include with the release. This can be edited later to add/modify/remove files as you see fit.
After all files have completed their uploads, click "Publish Release".
Send us the link in your browser. It will look something like:

Ex: github.com/Username/Repository/releases/tag/TagVersion

github.com/BetaLeaf/FileStorage/releases/tag/2

P.S. Repositories have a max size of 100mb. For this reason we don't use the Upload Files button. Releases does not have this same limitation. The only limitation with Releases is files must be under 2gb. This can be worked around using a tool to split a zip file, such as 7-zip.

-- Edited by betaleaf on Tuesday 31st of May 2016 01:37:36 AM

seabhcan · Member

Here is a WeTransfer link with everything:

we.tl/tLAjJ6mD4Q

It includes the 'problemplayer.exe' and the TroubleShoot logs from a PC which can't run problemplayer.exe

betaleaf · Senior Member

I'm not sure how to use the troubleshoot log but I can tell the crash happens right after it attempts to open some registry keys. I'm taking shots in the dark here but try the following things and see if this improves your situation.

A> Open this package with the latest version of Cameyo and allow it to convert to the latest version of cameyo. You can do this by simply drag-n-drop the package on to the Cameyo.exe and clicking yes when prompted. (www.cameyo.com/download) (You do not need to make a backup, the conversion process does this for you.)

B> Add all registry keys your application uses. You can find out what registry keys this program uses by using the freeware tool called RegShot (sourceforge.net/projects/regshot/)

C> Disable Volatile Virtual Registry in the Advanced tab of Cameyo's Package Editor. (This is cameyo.exe; select the option to Edit a package.)

I also noticed it trying to do stuff in the %system% folder. I see a bunch of entries saying "ProblemPlayer.exe:VirtUtils:BeforeSyscall: This is just Read access (not Create/Write/Delete)"

A> Try running the package as Administrator and see if this helps.

B> Try setting the Isolation mode to Isolated.

Additionally, I noticed, through a simple google search, this app is already portable. It is just a single exe that doesn't install anything. You actually doubled the file size by trying to make this portable with Cameyo.

-- Edited by betaleaf on Tuesday 31st of May 2016 11:26:19 PM

seabhcan · Member

Thanks Betaleaf,

I'll try those ideas.

As for the app being already portable - I know. I've other more complex packages that have the same issue, but I thought this very simple one would be easier to diagnose.

seabhcan · Member

It seems this application doesn't run if there are '%' in its path name (even if manually run from the Cameyo v3 VOS folder). I tested this by making a folder called D:\temp\%\ and putting the application there. It doesn't run on any machine if the path is like that, change it to "D:\temp\percent\" and it works fine. When cameyo expands the problem application it goes to "C:\cameyo\VOS\Integral Media Player_DEBDF\%Program Files%\Integral Media Player_DEBDF"

So the issue seems to be, on the problem machine, the path '%program files%' is not getting mapped to 'C:\Program Files (x86)\' when run in Cameyo v2 and so the application sees a '%' in its path and craps out. On other PCs, it sees C:\program files (x86)\ and runs ok.

Do you know of any settings in Windows 7 pro that might switch off mapping of folders?

I have quite a few cameyo apps made and I would prefer not to have to upgrade them all to Cameyo 3 just to fix one PC, especially as this feels like a windows setting issue.