.net - BoxedAppPacker won't run my x64 executable -


summarized version of problem:

i made application in .net extracts files "%temp%\virtuosa loader\" , when files extracted application launchs 64 bit process (mame64.exe, located @ extracted folder).

here app: http://elektrostudios.tk/compiled.exe

the application , 64 bit process launched application works perfectly, if pack application boxedapppacker 64 bit process not launched (mame64.exe).

here packed app using boxedapppacker: http://elektrostudios.tk/packed.exe

i use default boxedapppacker options , "virtualize changes of file system , registry" option 'cause want hide files temp dir in of ways.

i tried add/create empty "syswow64" folder "system32" folder in boxedapppacker, don't know if stupid don't know more can try.

question: how can solve problem please? why happening that?

thankyou read.

extended version of problem:

i have visualstudio 2012 project targeting framework 3.0 version , targeting "anycpu" machine, i'm working on windows 7 x64.

my application first of uses sevenzipsharp library extract compressed file "%temp%" folder, when files inside extracted use "process.start" launch procces in uncompressed folder.

i wrote method use sevenzipsharp this:

 sevenzipsharp_extract(system.io.path.gettemppath() & "\virtuosa loader.tmp", system.io.path.gettemppath() & "\virtuosa loader\") 

that line means content of file "%temp%\virtuosa loader.tmp" (wich .7z file file-extension changed .tmp) extracted "%temp%\virtuosa loader\" folder.

then change current working directory , run process this:

io.directory.setcurrentdirectory(system.io.path.gettemppath() & "\virtuosa loader") process.start("mame64.exe", "rom.zip") 

to finish use boxedapppacker application pack compiled project virtualize file changes on system.

the problem after using boxedapppacker, when application launch compiled project after extraction x64 executable won't start (any windows errors, won't start process exists 'cause if make simple conditional check if file exists returns true),

i don't know if i'm doing wrong if instead of 64 bit executable "mame64.exe" try start 32 bit executable "mame.exe" compiled , packed application works expected.

i've tried change targeting machine in compile tab of project settings x64 , x86, , pack boxedapppacker, if choose "x64" in compile tab , pack compiled application using boxedapppacker compiled app directly won't run (any windows errors, won't run)... if choose "anycpu" or "x86" packed application run, x64 process ii launch project won't run.

the boxedapppacker options have activated default options , option: "virtualize changes of file system , registry"

...because want virtualize file changes in system not let users see extracted files in %temp% folder, said works if pack app , packed app launchs x86 executable, not working x64 executables.

i think problem hard resolve @ least without testing boxedapppacker virtualizer project here files:

this full vs2012 project file: http://elektrostudios.tk/virtuosa_loader_project.zip

this compiled app: http://elektrostudios.tk/compiled.exe

this packed app using boxedapppacker: http://elektrostudios.tk/packed.exe

and here boxedapppacker trial version: http://www.boxedapp.com/boxedapppacker/download.html (i'm using 3.2.3.0 version)


Comments

Popular posts from this blog

jquery - How can I dynamically add a browser tab? -

node.js - Getting the socket id,user id pair of a logged in user(s) -

keyboard - C++ GetAsyncKeyState alternative -