MHz

As the website server seems to be currently down, a direct download link has been added to the 1st post. Thanks to those, who have been patient.

It is added to your favorites, very good. Glad you have succeeded to get the program. Thank's MAVERICKS CHOICE

I think that you could also have a look at the Wise packages. Some thing like Wise for Windows, maybe a suitable package to look at. It covers everything like Installshield covers, but I find that it is much more user friendly to create msi installers. It is not any cheaper than Installshield, but has the features. Thet also have a studio package.

Nice guide, master_mtz. It is a good starting reference for noobs of AutoIt. Scite4AutoIt3 has all the tools onboard for making AutoIt scripts as easy as possible. As a user may get to know some of the vast amount of inbuilt functions, then AutoItMacroGenerator could be used. This program is made for unattended installs in mind. AutoItMacroGenerator records as well. Some knowledge of the Control*() functions maybe needed to edit the final draft script created by AutoItMacroGenerator. CMenu can create AutoIt scripts for silent installing. The thread is in this forum. Certainly a nice range of tools, to help the user with creating installation scripts.

Sure, you can customize the templates. You are not out of line, as I assumed that users would like to customize the templates, from the very beginning. 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.

Updated to version 1.6. Please see 1st post for information and improved download link. Lots more incrediable features added.

@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.

Any requirements should already be in the script that you made. You should be able to run the compiled executable without a switch.

I totally agree with your 1st statement, but the 2nd is way off. I have built enough systems to know the difference. Here is a Whitepaper on memory and the dual channel concept. Please enjoy the reading. Here is a quote from it.

Yup, I have seen. But, you show good promise, to your deeds. No one knows drivers like Bâshrat the Sneaky. We all cannot be good at everything. But I have seen some growing talent in you with your programming skills. This maybe the direction for you to focus on. You will learn, continue and enjoy.

2 different sizes of ram. pc3200 should not be a problem. It is a dual channel, correct? Most Mobo's that I am aware of, require the same type and size of ram for dual channel to operate. Matched pairs are sold for this reason. I would consider that the Mobo is seeing the 512 Mb ram, but will not allow the 1Gb ram to operate, as to the incorrect balance, between the channels.

I would guess that you have the wiring setup on the wrong polarity. Check the wires going to your reset switch. You may have set the wrong wires to the wrong connections?, or you have the wrong polarity (e.g. + to -, - to +) on the reset switch? Incorrect wiring can easily raise a problem, such as this.

This command will change the attribute of boot.ini Attrib +S +H %SystemDrive%\boot.ini

You may need to run CHKDSK on those at risk drives to sort your problem. If the drives are on your new HDD, then you may have a faulty drive? What are Dynamic disks?

1. At a command prompt, type set. You will now see the environmental variables available to you. 2. Not sure of this. 3. The registry is mostly built from inf files, from the I386 directory. One resource for inf files is here.

Small alteration: @echo off && Mode 60,12 && Color f2 FOR %%i IN ( ".\Update\*.exe" ) DO ( ECHO Installing hotfix %%i start /wait "" "%%i" /O /U /N /Z )

The installer would be trying to make a log file in it's current directory. Use the /f2 switch to set the log file to a writable medium.

Well, you going to be a smartie. or share some.

shellexecute=explorer.exe .\

Just type in a commandbox: sfc /scannowAnd have your windows cd, as you will need it.

If you mean, is folders available for adding files to desktop, from within $OEM$, then yes. Create a $DOCS folder inside $OEM$ folder. Then create within the $DOCS folder, 2 foldors, All Users and Default User. Within those folders, you can create Desktop folders.

Seems like the installer is trying to make a log file? If you silently install form cd, you may need to specify a switch, to make the log file, to write to the HDD, else your installation will fail.

Unpack the thing with winrar. Make a recording of the install with /r. Retrieve the setup.iss file, from the windows folder. Place it with the setup.exe file. Use /s to install silently. Also use /f2"c:\windows\setup.log" for the log file, if you install directly from cd. You can change the log location, if you wish, so long as it is a writable medium. You could even SFX it all up, and use tempmode in winrar, then you may not need to worry for log, as it would be extracted to the HDD.

The installer appears to be created by InstallConstruct. I have looked around the site, with no answers of any switches to pass, to achieve silent install. Tried different switches with no luck. You can unpack the thing with winrar, but it must destroy the parameters of the installer, as it will not even work in gui mode then. Sorry, but no go.

The repair option is removed, when you create an unattended cd.