So it looked like setup.exe is just a small launcher application which does not really do the installation and terminates itself before installation finished or even really started. This was an indication for setup.exe already terminated although the installation has not been done at all. I could see on execution of the batch file from within a command prompt window with user account control disabled (full granted administrative permissions without prompt) the dialog window to choose language for installation and at the same time in command prompt window the line: Exit code is: 0 So I created a batch file in directory containing setup.exe with the following two lines: Exit code is: %ERRORLEVEL% This was the first indication that something is wrong with setup.exe executed by the SFX module according to SFX script commands inside archive comment file with content: The comment below contains SFX script commands It took me a while to find out what really happens on running the SFX archive songkong-windows64.exe.įirst I detected that the temporary directory %TEMP%\RarSFX0 remains although it should be deleted by the SFX module at beginning of the SFX archive after installation finished without or with really installing the application. Why could this be? Could there be some restriction with files called install.jar? Now I use to submit each new version to Norton whitelist, but that option has gone. I found for one user that disabling Norton AntiVirus allowed installation. So we have this folder structure:īut for users having a problem it only extracts JVM64: Volume in drive C has no label.ĭirectory of C:\Users\gcdr\AppData\Local\Tempĭirectory of C:\Users\gcdr\AppData\Local\Temp\RarSFX0 When I run the self-extracting archive it self-extracts correctly. zip file that users have to extract themselves works fine. There is a only a problem with self-extracting version, a regular. What could be causing this problem? Is it related to a Windows updates? Unable to access jarfile C:\Users\Ray\AppData\Local\Temp\RarSFX0\install.jar It works, for me and most customers, but recently a few customers have reported errors like this: I have a Java application, the Izpack installer is wrapped with launch4j64bit and then bundled as a self-extracting ZIP, created with WinRAR 5.20 using a method as described in an answer on How do I make a self extract and running installer?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |