Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: "Unable to determine startup path: GetShortPathNameW failed. The specified game file might be missing." ?


Member

Status: Offline
Posts: 18
Date:
"Unable to determine startup path: GetShortPathNameW failed. The specified game file might be missing." ?
Permalink   
 


I have several cameyo apps (games) that, to my knowledge, have been working just fine. But today, I tried to play them, and several of them don't work. Now, I am able to launch the setup menu of these games, but when I actually try to run the exe of the game itself, it gives me the following error message:

HOsT5Vl.png

Here's a copy of one of the cameyo files if any investigation is necessary: https://drive.google.com/open?id=1yKlrFnXH82AqzbdoHhRRQTcqz8JaqIjX

I'm running Win 10, 64-bit. I made these cameyo packages on a clean VM, running either XP or 7. From what I remember, I tested them after and then they just sat on my computer for the past few months, and now they won't launch. Is it possible that a Windows 10 update did something which is messing things up?

Also, I have other cameyo packages which do still work fine (other games). However, the only ones I seem to be having trouble with are these games which were made with a program called "Adventure Game Studio"

 

Edit: I'm pretty sure I used XP to make this package, so that means that "Program Files" is actually "Common Programs" on XP. When I go to the VOS folder and try to run the exe from there, it gives me the following error message:

4ceXjKq.png

So is it possible that my computer is interpreting the %Common Programs% variable to look at Program Files or something, and since it's obviously not there, it has a problem? Or am I way off base here..



-- Edited by lukeman3000 on Wednesday 15th of August 2018 02:50:28 PM



-- Edited by lukeman3000 on Wednesday 15th of August 2018 02:50:51 PM

__________________


Guru

Status: Offline
Posts: 883
Date:
Permalink   
 

Some packages that were created with older Cameyo builds have issues with Win10 1803.  Download the latest Cameyo Packager.  Documentation here for upgrading packages.
lukeman3000 wrote:

Is it possible that a Windows 10 update did something which is messing things up?


 



__________________


Member

Status: Offline
Posts: 18
Date:
Permalink   
 

mule wrote:
Some packages that were created with older Cameyo builds have issues with Win10 1803.  Download the latest Cameyo Packager.  Documentation here for upgrading packages.
lukeman3000 wrote:

Is it possible that a Windows 10 update did something which is messing things up?


 


 Thanks! I'll give this a try.



__________________


Member

Status: Offline
Posts: 18
Date:
Permalink   
 

Well, dragging and dropping the latest cameyo packager worked on at least one of my packages, however, when I tried to use it with another one, I received this error:

SeCxpkG.png

This particular package does have a .dat file, as well, so I'm not sure if that makes a difference or not. Before this error message appears, Windows pops up a little blue box that says something about how this app can't run on this PC:

BZ84a3K.png

Also, I got a false positive from Windows defender (anti virus) during the process (after I dragged and dropped). I went into defender settings and clicked "allow", and it didn't notify me of the issue in subsequent attempts, but the previous error messages did persist. Interestingly, none of things occurred the first time I dragged and dropped the new packager, and it completed without a hitch. The first time I used it, there was no .dat file for that package.



-- Edited by lukeman3000 on Thursday 16th of August 2018 08:19:47 PM



-- Edited by lukeman3000 on Thursday 16th of August 2018 08:22:59 PM

__________________


Guru

Status: Offline
Posts: 883
Date:
Permalink   
 

Try this: add exe extension to your dat, drag Cameyo to the former dat file, which now has an exe extension, and rename the newly created .new.exe back to dat.

E.g.

  1. you have bigpackage.cameyo.exe and bigpackage.cameyo.dat
  2. Rename bigpackage.cameyo.dat to bigpackage.cameyo.dat.exe
  3. Drag Cameyo.exe to bigpackage.cameyo.dat.exe.  Bigpackage.cameyo.dat.new.exe should be created. 
  4. Rename bigpackage.cameyo.dat.new.exe to bigpackage.cameyo.dat.  Bigpackage.cameyo.exe should now work with bigpackage.cameyo.dat.


__________________
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