giulia wrote: ↑Tue Dec 31, 2019 11:54 pm
why 32bit ? the program is 64bit (cuetools)
Hi,
After your question I looked at CueTools again and it appears that it's both 32 and 64 bit. Since there is only one executable, CueTools.exe, it looks like the application detects and executes in 32 or 64 bit mode depending on the system. I assumed it was a 32-bit program since I was going by the database entry, it runs on my 32-bit XP system, and I didn't see a separate 64-bit executable. As you know, 32-bit programs also run on 64-bit systems, but not the other way around, so recommending a 32-bit config was a safe bet that it would work regardless of system. The yaPX64.exe launcher is used for launching 64-bit programs that have a separate executable with a different name (e.g., *CueTools64.exe). Anyway, to use the 64-bit yap launcher, you could rename it to the same name as the current yaP launcher, but be sure to revise the current launcher's name first since two files with the same name can't exist in the same folder. However, changing to the 64-bit launcher shouldn't make any difference since whether the application runs in 32 or 64-bit mode isn't determined by yaP anyway.
If curious you may want to play around with things. It may be possible to run both launchers using different names (e.g., CueTools_yaP.exe and *CueTools_yaP64.exe), but I can't confirm that since I'm using a 32-bit system. I know that the 64-bit yaP launcher, yap64.exe, is a 64-bit file because I can't launch it on my system. Something to check is to run the yaP64.exe and see if it generates a separate ini file with a different name than the original ini config file (before it was changed to CueTools_yaP.ini). If so, then it's possible to have a 32-bit launcher and the 64-bit launcher with separate ini config files. Then again, it's more likely that the both launchers are programmed to use the same ini config file, switching to 32 or 64 bit depending on the config file entry and the system itself. If that's the case, there isn't any need to change anything unless one wants to use a 64-bit launcher - just because it's possible.
There's been changes, bug fixes and added features over time for yaP, some of which I wasn't aware of. Below are a couple of noteworthy ones for launching applications:
For apps that include 32 and 64-bit executables, the config file entry would look like the below:
[GENERAL]
Code: Select all
application = App\CueTools.exe :: App\*CueTools64.exe
You could even use relative paths:
Code: Select all
application = App\CueTools.exe :: ..\Some Folder\*CueTools64.exe
On a 64bit OS yaP automatically launches the application set in the second segment (if available)
Also, I wasn't aware that yaP is able to launch programs from an existing location such as from Program Files. That could come in handy when running installed apps on another machine without a trace.
Code: Select all
application = %ProgramFiles%\App.exe :: %ProgramFiles%\AppX64.exe
*CueTools_yaP64.exe doesn't exist, it's used here for example purposes