I virtualized Greenshot 1.2.8.12 using Cameyo 3.0.1394 in Nov 2015, it's been working perfectly in my Windows 7 Professional x64 with SP1 (VM on ESXi 5.5 Update 3b).
Unfortunately when I install Microsoft's Feb 2016 patches, all my applications virtualizedby Cameyo start either crashing or throwing out error messages. For instance, Greenshot crashes when I try to launch it, it mentions the crash is due to C:\Windows\System32\KernelBase.dll and I observe KB3126587 and KB3126593 do updated a few kernel dll files. The crash/error is gone as soon as I uninstall both KB3126587 and KB3126593.
I have tried to update the package with dragging it and also via the command line but I can't get the application to work anymore. I've tried to create a complete new package with the software but get some automation error. Somebody who no longer works here created the original package and it seems like I'm missing something.
You provided two packages that show Cameyo Engine version of 3.1.1427. Do either of these packages work for you? If yes, please advise which one. If no, please provide the original package that worked before updating.
So here is the version that used to work before the Windows Updates broke. It will work on a Windows 7 machine if I unin stall about 7 different updates. Then you will actually get the login box correctly.
-1023 S1009: [Microsoft][ODBC Microsoft Access Driver] '(unknown)' isn't a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
I know that the software does have an ODBC connection that it uses. I tried to edit the new package but I don't know what I'm looking for. It's probably listed in the working package.
As for the working one I am not certain what that was captured from. It was done prior to me. As for the second one we are trying to get working that was a clean install. And yes if I perform the install I can get it working. But we wanted to use cameyo because it requires alot of configuration and replacing of the odbcjt32.dll file on the local machines.