Thanks for the update! I'm just having a whole lot of fun w/this utility.
CMenu Context Menu for Installers.
#51
Posted 16 July 2005 - 12:38 AM
Thanks for the update! I'm just having a whole lot of fun w/this utility.
#52
Posted 16 July 2005 - 01:04 AM
NemoNada, on Jul 16 2005, 04:38 PM, said:
Thanks for the update! I'm just having a whole lot of fun w/this utility.
<{POST_SNAPBACK}>
Superb, enjoy it.
#53
Posted 16 July 2005 - 01:40 AM
very Nice Utility Dude, Thats why I like this place soo many timesavers.
#54
Posted 16 July 2005 - 01:50 AM
has anyone ever had this problem: some install app is supposed to have a "/s" switch (according to identify installer). but it just doesn't work. the prompt for user input just keeps popping up.
i tried the nifty silent install tool in Cmenu 1.5, and the prompt still comes up, so i know the install app must have some... "anti-silent" thing going on...
i've been trying to silent this install for so long. i would like to request a "send app creator to hell" feature.
anyways, keep up the good work! i'll keep an eye out for the next version.
#55
Posted 16 July 2005 - 02:06 AM
1boredguy, on Jul 16 2005, 05:50 PM, said:
Take a close look at Identify Installer, when it shows you the switches.
You may see descriptions like this:
(All switches MUST be upper case. No inverted comma's)
Some installers are case sensitive. NSIS likes uppercase only.
1boredguy, on Jul 16 2005, 05:50 PM, said:
1boredguy, on Jul 16 2005, 05:50 PM, said:
Notify the program creator, and complain.
This post has been edited by MHz: 16 July 2005 - 02:07 AM
#56
Posted 16 July 2005 - 02:54 AM
MAVERICKS CHOICE, on Jul 16 2005, 05:40 PM, said:
Thanks and you are so true.
Timesaving is an important concept. The more you save, the more you can commit, to do more. Or spend more precious time with family and friends.
#57
Posted 17 July 2005 - 09:10 AM
I have one more suggestion for your future version. I think you missed the switches for Tarma installers.
#58
Posted 17 July 2005 - 09:31 AM
totoymola, on Jul 18 2005, 01:10 AM, said:
I will look into it. Do you know of a small program that uses it?
#59
Posted 17 July 2005 - 08:49 PM
#60
Posted 29 July 2005 - 06:40 AM
1.) Would you mind to rip Identify Installer out from CMenu?
2.) What about creating database of known switches for setups, that dont support common installation?
#61
Posted 31 July 2005 - 03:28 PM
the rapidshare may still ok but I'm having a little problem:
Quote
Maybe you use a proxy-server. Premium-users are not affected by this ban. Maybe you might want to get a PREMIUM-Account, too.
It is just a one-time fee and you will have access instantly. Please see our big FAQ, if you still have questions.
so any upload to have fun in the next weekend?!
#62
Posted 01 August 2005 - 01:39 AM
Quote
1.) Would you mind to rip Identify Installer out from CMenu?
2.) What about creating database of known switches for setups, that dont support common installation?
@Martin
Interesting requests.
Could you supply a reason for asking for Identify Installer's removal. This request does seem unusual, to what I would expect. Perhaps you may wish to pm your concerns?
The database idea seems interesting, but I would consider too much information to process. My spare time would be used up in adding entries into a database for all the programs that exist.
@Wesmosis
Sorry for the disappointment. A better download link, will be setup.
#63
Posted 01 August 2005 - 01:41 AM
Please see 1st post for information and improved download link.
Lots more incrediable features added.
#65
Posted 01 August 2005 - 07:17 AM
keep this proggy alive
#66
Posted 01 August 2005 - 05:52 PM
I do have one request and it may seem a bit stupid.
Is there anyway you can make it so that you can have the choice to write a simple autoit script such as:
Runwait("setup.exe /silentmode")
Reason I ask, is because I normally write my own AutoIt scripts for silent installs and I usually have something like this:
SplashTextOn('', "Installing NOD32 v2.50.25", 400, 25, -1, -1, 1, '', 14)
adorning the top of it.
To take the concept a step further, the ability to create our own autoit templates would be great (i.e., it would add that SplashTextOn to each of my scripts I generate) Just a couple ideas...
I love the app and if I am at all out of line, then my sincerest apologies.
-redfive
#67
Posted 02 August 2005 - 01:09 AM
This is how CMenu 1.6 does this.
It installs the template files into Program Files\CMenu\Templates. The text files are read by Identify Installer and the au3 files are read, when you create an AutoIt script.
If example Inno Setup is identified, and you want to create a script, then the Inno_Setup.au3 will be read. A file called Common_Functions.au3 will also be read, for any installer. The data will be checked for the strings, Program_name and filename.ext, and will be replaced by, for example NOD32 v2.50.25 and NOD32 v2.50.25.exe. If a recording was made of the installation, then the recorded files could be read. The variables at the top of the script may have the information added to them. The script is then created in the installers directory. That is the script making process.
Now, as Identify Installer reads these files, then if you make change to the files, in the templates folder, the output would be what you have changed them to. If you want no common functions for the scripts, then clear the code from the Common_Functions.au3, so when it is read, nothing is returned. Now you may want to customize the Inno Setup output, so you would open the Inno_Setup.au3, in your editor. Do note the strings mentioned previously, that will help to fill some information in automagically.
A sample of what you may want in the template:
; Script for Program_name
SplashTextOn('', "Program_name", 400, 25, -1, -1, 1, '', 14)
Runwait("filename.ext /silentmode")
SplashOff()
This is your custom template for Inno Setup. When it would be read by Identify Installer, and the known strings are replaced, then the output script would look like:
; Script for NOD32 v2.50.25
SplashTextOn('', "NOD32 v2.50.25", 400, 25, -1, -1, 1, '', 14)
Runwait("NOD32 v2.50.25.exe /silentmode")
SplashOff()
Now, quick and easily, the output script is created to suit your needs.
When customizing, you may want to backup the original templates, in case you want use some information from them? You should definately backup your customized templates, to prevent tragic loss.
End of lessen
If you are like me, and get tired of all the extra comments that display the workings in the script alot, then you may use this script.
If MsgBox(4, 'Comment remover', 'Remove comments, are you sure?') = 7 Then Exit $read_handle = FileOpen($cmdline[1], 0) $write_handle = FileOpen($cmdline[1] & '.temp', 2) If $cmdline[0] = 1 Then _SafeRemoval() ElseIf $cmdline[0] = 2 Then _FullRemoval() EndIf FileClose($read_handle) FileClose($write_handle) Sleep(100) If FileRecycle($cmdline[1]) Then FileMove($cmdline[1] & '.temp', $cmdline[1]) Func _SafeRemoval() While 1 $line = FileReadLine($read_handle) If @error Then ExitLoop $check = StringStripWS($line, 3) If Not (StringLeft($check, 2) = ';~') And _ Not (StringRight($check, 1) = '.') And _ StringLeft($check, 1) = ';' Then ContinueLoop FileWriteLine($write_handle, $line) WEnd EndFunc Func _FullRemoval() While 1 $line = FileReadLine($read_handle) If @error Then ExitLoop $check = StringStripWS($line, 3) If StringLeft($check, 1) = ';' Then ContinueLoop FileWriteLine($write_handle, $line) WEnd EndFunc
Compile it. If you drag'n'drop a script onto this, it will remove comments that do not end with a period (.). You can also add it into your editor to pass the script path to the compiled exe. Or you can pass the script path by commandline to the compiled exe.
If you pass a 2nd switch to it also, which can be anything, it will remove all comments. Not recommended, as when you come back to look at the script latter, you will need to re-interpret what the script code is accomplishing throughout.
The original script is put into the recyle bin, and the replaced by the comment removed version.
I have it setup in the Scite directory, and have added to the user options file:
# 17 Comment Remover command.17.$(file.patterns.au3)=comment_remover.exe "$(FilePath)" command.name.17.$(file.patterns.au3)=Comment Remover command.subsystem.17.$(file.patterns.au3)=1 command.save.before.17.$(file.patterns.au3)=1 command.is.filter.17.$(file.patterns.au3)=1
This will appear in the tools dropdown menu as Comment Remover, and will remove the comments without ending in a period, from the script displayed in the editor.
End of Comment Remover
Good luck.
#69
Posted 02 August 2005 - 05:09 AM
cyberhrc, on Aug 1 2005, 10:49 PM, said:
It is added to your favorites, very good.
Wesmosis, on Aug 1 2005, 11:17 PM, said:
Glad you have succeeded to get the program.
MAVERICKS CHOICE, on Aug 2 2005, 08:33 PM, said:
Thank's MAVERICKS CHOICE
#70
Posted 02 August 2005 - 10:54 PM
- ← Silent uninstallation of Kaspersky Antivirus 2011
- Application Installs
- installing software silenlty with serial key →



Help

Back to top









