Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Cameyo error when capturing an install to a flash drive


Veteran Member

Status: Offline
Posts: 40
Date:
Cameyo error when capturing an install to a flash drive
Permalink   
 


I tried to capture two installations to E: (a USB flash drive). Both installations went OK and the programs ran well. The Cameyo captures, however, showed an Error=2 message which I have not seen before (copy of one attached). Can Cameyo capture installations to a USB flash drive?



Attachments
__________________


Guru

Status: Offline
Posts: 876
Date:
Permalink   
 

Please upload your package to a file-hosting site and provide the url for downloading.  WeTransfer is a good option that does not require the uploader or downloader to jump through hoops; just send to yourself and post the url.



__________________


Veteran Member

Status: Offline
Posts: 40
Date:
Permalink   
 

I am doing a We transfer now, and I will PM the link to you when it is ready. Meanwhile, here is more about the process. I installed another program to E: (a USB flash drive) while taking a Cameyo capture. The installed program worked well, and also the Cameyo capture worked well. I then uninstalled the program and tried the Cameyo capture again, but now it gives the same error message as previously shown. Uninstalling the program from the flash drive makes the Cameyo capture no longer work.

I also did another program to the flash drive the same way, and I got the same results. The program and the Cameyo capture worked well until I uninstalled the program, and then the Cameyo capture would not work and gave the error message.



__________________


Guru

Status: Offline
Posts: 876
Date:
Permalink   
 

I looked at your package and found it includes nothing that was written to your E drive.  I checked with a developer and it turns out that Packager checks only fixed drives.  It makes sense because best practice is to perform captures on a clean virtual machine.  

Your package includes extraneous data from programs running in the background.  By using a clean VM, you eliminate these kinds of superfluous data that can sometimes interfere with the functioning of a package.  

Please consider using Online Packager.



__________________


Veteran Member

Status: Offline
Posts: 40
Date:
Permalink   
 

Sorry to reopen an old thread, but I have a recurring problem with some captures. Following the advice above, I install programs to capture to a fixed (but removable) drive assigned letter G:. After I uninstall the program from G: and then remove the fixed drive from my computer, most captures (stored in E:) work well. A few however, will run only if there is a G: drive in my computer. That G: can be a blank USB flash stick, and the filename.Cameyo.exe will run well and it writes nothing I can see to the G: USB flash stick. But if there is no G:, the filename.Cameyo.exe will only start to load and then stop mid process. The folder Cameyo creates contains only one mention of G_, as a folder name under Prog (screenshot below).

G mentioned only once.jpg

 

 

I tried changing the name of that folder to E_ and not removing the folder Cameyo creates when I exit, but when I try to start filename.Cameyo.exe again I get an error (screenshot below).

Error if no G in computer.jpg

 

It looks like for a few captures, filename.Cameyo.exe will not run unless the computer has a drive assigned with the same letter that the original program was installed to. Does a user have the ability to modify a filename.Cameyo.exe after the capture to point it to drive C: or E: or F: instead of G:?  Thanks!

 



Attachments
__________________


Guru

Status: Offline
Posts: 876
Date:
Permalink   
 

Please make one of these problematic packages available for us to take a look at, e.g. Stepok Picture Enlarger.cameyo.exe

To edit the location of an executable, you would have to know the software well enough to also edit any necessary references, e.g. registry, ini files, etc; otherwise, the software might not function properly.  In most cases, it would be better to build a new package.



__________________


Guru

Status: Offline
Posts: 876
Date:
Permalink   
 

That some packages work with no G: drive present and others do not work suggests that it depends on the way the application itself is written.  We recommend the following:

  1. use a clean virtual machine and install somewhere on C to build packages
  2. use Online Packager if you do not want to use your own VM

With the package you provided, I found that even changing CD-ROM Drive Letter in Disk Management to G was enough to get the package to run.  Using Subst command was another workaround.

 



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard