User talk:Red Wine: Difference between revisions
(Installer for Successional Installations) |
DeathAdderSF (talk | contribs) |
||
Line 1: | Line 1: | ||
== NSIS Quick Setup Script Generator issue == | |||
Hello. Can't seem to reach you via the winamp.com forums, and also can't find any contact info for you, so... | |||
In regard to NSIS Quick Setup Script Generator: | |||
Can a subfolder be chosen for the Start Menu location? | |||
For example: | |||
Instead of installing to a folder called FIGHT it installs to a sub-folder called FIGHT, within a folder called GAMES. | |||
So, START MENU -> GAMES -> FIGHT | |||
When I try to configure the program to do this, I enter the following text in the "Start Menu Folder Name" box: | |||
GAMES\FIGHT | |||
But the program reports: | |||
"Please specify a valid path for the installer." | |||
I have also tried entering: | |||
$STARTMENU\Games\Fight | |||
This too did not work. | |||
Any help appreciated, thanks. | |||
I can be reached at contact@superfighter.com | |||
Revision as of 09:02, 8 September 2013
NSIS Quick Setup Script Generator issue
Hello. Can't seem to reach you via the winamp.com forums, and also can't find any contact info for you, so...
In regard to NSIS Quick Setup Script Generator:
Can a subfolder be chosen for the Start Menu location?
For example:
Instead of installing to a folder called FIGHT it installs to a sub-folder called FIGHT, within a folder called GAMES.
So, START MENU -> GAMES -> FIGHT
When I try to configure the program to do this, I enter the following text in the "Start Menu Folder Name" box:
GAMES\FIGHT
But the program reports:
"Please specify a valid path for the installer."
I have also tried entering: $STARTMENU\Games\Fight
This too did not work.
Any help appreciated, thanks.
I can be reached at contact@superfighter.com
Installer for Successional Installations
I like your example script Installer for Successional Installations. I've made a page on Embedding other installers describing how to install other installers. I am considering updating it to use your technique for successional installs.
I might make the second example script part of a sourceforge project. Perhaps a NSI that will download all the requested installers, generate a NSI that auctually installs them compile the NSI. I would not want to redistribute all the installer files, nor could I, and I don't think a mega installer that installs every app imaginable would be the best of ideas either.