creating new package to Speccy - problem with installation

[jakub.mrvc@gmail.com]

Hi,
i'm trying to create new package to Speecy

i have a problem in the installation process, where i see that .exe is going to be unpacked but then it only wait, nothing more happened,

i tryied only simple .bat with path to .exe and it took few seconds but then installation process continued very well

so, now i know that there is no problem with the code but with installation process, maybe i must put them some more options or what

i also found the procedure how to log install process but it doesn't work for me i only get something like this

=== Verbose logging started: 30. 12. 2015 12:12:30 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (80:9C) [12:12:30:098]: Font created. Charset: Req=238, Ret=238, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (80:9C) [12:12:30:098]: Font created. Charset: Req=238, Ret=238, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (80:24) [12:12:30:107]: Resetting cached policy values
MSI (c) (80:24) [12:12:30:107]: Machine policy value 'Debug' is 0
MSI (c) (80:24) [12:12:30:107]: ******* RunEngine:
******* Product: C:\Users\jakub.moravec\Desktop\Dokumenty\OPSI\Speecy\spsetup129.exe
******* Action:
******* CommandLine: **********
MSI (c) (80:24) [12:12:30:107]: Note: 1: 2203 2: C:\Users\jakub.moravec\Desktop\Dokumenty\OPSI\Speecy\spsetup129.exe 3: -2147286960
MSI (c) (80:24) [12:12:30:107]: MainEngineThread is returning 1620
=== Verbose logging stopped: 30. 12. 2015 12:12:30 ===


i would be thankful for any advice
Jacob

[SisterOfMercy]

Uhh, you mean Speccy.

Well, the installer is a bit of a dirty little bugger, and includes an offer for google spyware (chrome). Just open the installer with 7zip, and copy the Speccy.exe and Speccy64.exe files.
Use these files in your package, and copy them to the installation directory. Simple!

[jakub.mrvc@gmail.com]

Hi, thank you for your advice and sorry for my bad english

but i have another problem because i'm newbie in writing .ins scripts i don't know how to use copy command

could you tell me? or is there some good manual for this .ins scripts?

Thank You

[holgerv]

but i have another problem because i'm newbie in writing .ins scripts i don't know how to use copy command

http://download.uib.de/opsi_stable/doc/ ... inst-files

or is there some good manual for this .ins scripts?

http://download.uib.de/opsi_stable/doc/ ... anual.html

Good luck!

[jakub.mrvc@gmail.com]

but i have another problem because i'm newbie in writing .ins scripts i don't know how to use copy command

http://download.uib.de/opsi_stable/doc/ ... inst-files

or is there some good manual for this .ins scripts?

http://download.uib.de/opsi_stable/doc/ ... anual.html

Good luck!

Thank you for the links, i triyed to use the copy command in my script :
copy -sV "%ScriptPath%\Speccy.exe" "C:\Program Files\Speccy"

but it show the error :
Syntax Error in Section: Actions (Command in line 39 origin: \\10.197.90.28\opsi_workbench\speccy\CLIENT_DATA\setup.ins line: 40): copy -> undefined

Don't know where i'm doing mistake this time

[n.wenselowski]

Hi,

you need to put this command into a files-section and then call the section in the main section.


- Niko

[jakub.mrvc@gmail.com]

Hi,

you need to put this command into a files-section and then call the section in the main section.


- Niko

Thank you very much

i create and call section :
[Files_Copying]
copy -sV "%ScriptPath%\Speccy.exe" "C:\Program Files\Speccy"

and for deleting i create section :
[Files_Deleting]
del "C:\Program Files\Speccy" /s /q

and now it works thank you once more for help

Jacob

[SisterOfMercy]

Code: Alles auswählen

[Files_Copying]
copy -sV "%ScriptPath%\Speccy.exe" "C:\Program Files\Speccy"

Code: Alles auswählen

[Files_Deleting]
del "C:\Program Files\Speccy" /s /q

Better look at the documentation again:
–s -> We recursive into subdirectories.
–V -> Version checking
"A newer version of a windows library file is not overwritten by an older one (according primarily to the internal version counting of the file). If there are any doubts regarding the priority of the files a warning is added to the log file."
This is not a windows library so I don't think that is needed.

The delete command does not use dos-style parameters.
del -sf "C:\Program Files\Speccy\"

And look at the templates for hints about $InstallDir32$ and $InstallDir64"

Code: Alles auswählen

[Actions]
DefVar $InstallDir32$
DefVar $InstallDir64$

Set $InstallDir32$      = "%ProgramFiles32Dir%\Speccy"
Set $InstallDir64$      = "%ProgramFiles64Dir%\Speccy"

Code: Alles auswählen

[Files_install_32]
copy "%ScriptPath%\Speccy.exe" "$InstallDir32$"

[Files_install_64]
copy "%ScriptPath%\Speccy64.exe" "$InstallDir64$"

[Files_uninstall_32]
del -sf "$InstallDir32$\"

[Files_uninstall_64]
del -sf "$InstallDir64$\"