infringer

you will also first need to change your boot sequence to hard drive first after first restart to prevent the usb from booting again.

correct that makes the request implicitly something we are trying to stop by making the installer silent. Anyhow thanks for the heads up in my case it seemed to cause peazip for instance to ask for administrative access. Anyhow thanks I will keep at it figuring all this out but for now its a bit more learning curve time.I know this program win7tookit is a one of a kind program I am just trying to leverage it to my full potential and see exactly what is worth doing and what is not with lash's help I was able to determine the best possible use for drivers is to install the LAN/WLAN drivers as they are most important which is very true while I overlooked this simplistic thing it just made since as video drivers as well as other drivers change with the season it seems. And even if they don't you can slap the rest of the drivers on a flash drive and just pull in all the drivers needed saving you space on your install in the end as well.

Excellent breakdown thanks for your time and the excellent program. Must be an old school coder or trained by them. The professional approach you have with your own albeit free application is astonishing. And quick to boot. I thank you and take care.

No the error was basically missing cd drivers which didn't make since when entering setup ... Well I integrated driver packs to automate stuff obviously and oddly enough while each wim was 20gigs + the final file size of my setup was a whopping 6.x GB for an AIO setup to me this is not all that bad. I don't feel it would be a waste of space if it saves me the time of having to transfer drivers for wireless here and some laptop models are just utterly stupid they have like 10 different wireless adapters for the same model of laptop or 5 different camera drivers. So if I could simplify the process it would be nice but you say then driver integration is not the correct way to go about it instead use the driver pack CD or get the drivers manually. I like this solution for drivers while I have not tested the time it will take on the installation side which would possibly change my view... Does the install take double the amount of time to install windows with the drivers integrated or more? Does the installation of windows with the drivers retain all the drivers on the hard drive even if they are not used? I am really curious being that the developer himself doesn't use the driver integration except for rare occasions I would like to know more specifically what the results are one could estimate what you say as a long time meaning 10mins more or for the next guy it may be an hour more. And as far as the waste of space is it space wasted on the iso vs the target drive it is being installed to? There was a lot of information in that short reply you made while I appreciate the reply the specifics of the answer were left out. I think that integration is really not all that long a couple of days to have nearly every driver possible is a small price to pay and the amount of compression achieved is amazing for anything to process that much faster at this current day and age I would have to say show me. 200+Gigs compressed to 6.x gigs sounds almost impossible. --- So when you say dvd root x:drivers you mean you create a directory in the home directory with your setup.exe called drivers and you just pile them all into there well I have done that with software that everyone would typically use and some non typical stuff that I use as well like SIW and other tools. But this somewhat defeats the purpose of what you are trying to produce with this piece of software which is automation. From your useage it sounds to me like the biggest bummer of all for you is windows updates if I am reading you correctly. The tweaks were a nice addon as well by the way. Silent installers and windows addons are nice too but as soon as you get them on the disc they will surely be updated the next day drivers on the other hand do not get updated as frequently as software anyhow I suppose your method would work equally as well but would take up quite a bit more space being uncompressed.

The only issue I have is figuring how to do this correctly cause I spent about 4 days creating images that were faulty due to the fact the CD DVD drivers are missing this may be related to my own stupidity of selecting the integrate drivers into boot.wim option IDK or selecting enable x64 recovery I don't understand why a perfectly good image would be faulty espicially with all of those drivers integrated from the driver pack there should be no reason to have a missing cd/dvd driver to install windows every friggin driver possible was loaded to this ISO. Could anybody tell me what the underlying issue is here I really do not want to waste another 4 days integrating stuff for it not to work again. I thank you for your time I am running out of it here as I really need to get this working to help a friend out who has been bugging me for the past week to help him reinstall his windows 7 to his new ssd on the laptop and it would be great not to have to sit and wait for updates or find all kinds of drivers but if I have to I guess I have to I just figured this would save me some time in the long run as I plan to upgrade my SSD soon as well... I really appreciate your help guys. This is all done using .65 as the version. I wonder if the updated version will solve this issue or if I am doing something wrong. PS no addons or silent installs were used in the making of this ISO.

yes it takes about 24hours to integrate but you must remember for an AIO image you are compressing 200+Gigs with all of them drivers into a 6.x GB file it is just amazing I am shocked it could be done this soon and I'm running an AMD 1100T with 16GB of ram over clocked to 3.8GHZ per core.

Yes that is the correct source thanks for mentioning that... as I lost where I had copied it from. Anyhow Netopsystems Fead / NOSSO this is a real gem of an installer is giving me a fun time trying to actually get something to unpack it... I would like to see a silent installer of avast without google chrome but it has been 2 days of defeat for that cause. The switches are supposed to be: -nos_ne : no execution -nos_o : specify output directory -nos_nd: specify not to delete any files from the installer You used to be able to install avast without it in early versions up to 6.1 or something of that nature then they changed something IDK...

Introduction The goal of this document is to collect instructions for performing unattended / silent installations of many popular application installers. Such instructions are useful for automating these installations. A quick word on terminology: Strictly speaking, an unattended installation is one which does not require user interaction, and a silent (or quiet) installation is one which does not display any indication of its progress. However, most people use these terms interchangeably. Here, we are interested not only in performing unattended installations, but also in waiting for those installations to finish and suppressing any reboot they might want to perform. This is necessary for reliably installing multiple applications. General information There are several systems which vendors use to create installers for their applications. To make an educated guess about how to run an installer unattended, you need to know which system was used to create it. Sometimes this will be obvious from the installer's splash screen; sometimes you can figure it out by running strings; and sometimes you will have to guess. Of course, you can try running the installer with the /? switch to find out which other switches it supports. But if you really expect this to work, then you have not been using Windows for very long. In my experience, the odds are about 1 in 4 that /? will tell you anything at all, even when there is something to tell. MSI packages Microsoft's own Windows Installer Service is the nominal standard, and if everybody used it, there would be no need for this document. Unfortunately, Microsoft invented it too late. The package files have a .msi extension, and you manipulate them using the msiexec utility. For installation, use the /i and /qb switches. Use the /l* switch to produce a log file. You can provide named options (or "properties") at the end of the command line; which properties are supported depends on the package. For example, this command: msiexec /qb /l* perl-log.txt /i ActivePerl.msi PERL_PATH=Yes PERL_EXT=Yes ...is how you install ActiveState Perl, instructing the MSI package to add Perl.exe to your PATH and to associate .pl files with it. Perhaps the most important common property is the REBOOT property, which you can use to suppress any automatic reboot the MSI package might try to perform. So in general, you want to provide the /i, /qb, and REBOOT=ReallySuppress parameters to msiexec. msiexec can do many other things, like uninstall software or apply patches. Neat, huh? Too bad nobody uses it. InstallShield InstallShield is one of the oldest and most widely used application packaging systems. Installers created by InstallShield recognize the /r, /s, /sms, /f1, and /f2 switches. The installer itself is invariably named setup.exe. To perform a silent installation, you need an InstallShield "answer file", customarily named setup.iss. Some applications ship with such a file, but if yours does not, you can use the graphical installer itself to create one. Here is how it works. Run the installer with the /r ("record") switch. Proceed through the dialogs and complete the installation. This will create a setup.iss file and place it in the C:\WINDOWS directory (yes, really). This file will include all of your responses to the InstallShield dialogs, allowing you to perform unattended installations as if you were giving the same answers again. Simply copy setup.iss to the same directory as the installer executable. Once you have a setup.iss file, run the installer with the /s ("silent") option. This will perform an unattended installation. Unfortunately, the installer will fork a separate process and exit, meaning it will return immediately even if you run it under start /wait. This makes it useless for scripting purposes. Luckily, there is another switch, /sms, which will cause the installer to pause until the installation completes. Hence, for an InstallShield application, you want to provide both the /s and the /sms switches. The /f1filename switch allows you to specify a fully-qualified alternate name for the setup.iss file. Note that there must be no space between the /f1 switch and the file name. This switch works both with /r to create the file and with /s to read it. The /f2filename switch specifies a log file. Once again, there must be no space between the switch and the file name. WARNING: Be careful what characters you use in these file names, because InstallShield silently strips certain non-alphanumerics (like hyphens). Oh, one more thing. The /r and /s switches only work if the release engineer is competent. Many packages have "custom dialogs" which are not supported by setup.iss, which means the dialogs will always appear no matter what you do. For such packages, I suggest asking the vendor to fix their installer. If that does not work, I suggest doing what you can to deprive them of business. PackagefortheWeb InstallShield has a relatively new add-on product called PackagefortheWeb, or PFTW for short. This is basically an InstallShield tree bundled up as a single-file executable. When you run this executable, it extracts a bunch of files to a temporary directory and launches the setup.exe within. The PFTW package recognizes the /s and /a ... switches. The /s switch instructs the PFTW package to run silently, although this does not necessarily mean that the underlying setup.exewill run silently. The /a ... ("add") switch allows you to add switches to the command line of the underlying setup.exe process. You may provide any of the normal InstallShield switches here, including /r, /s, and /sms. Thus, to automate the installation of a PFTW package named foo.exe, you would first perform one installation by hand to create the answer file: foo.exe /a /r /f1c:\temp\foo.iss Then, to install the package completely silently, you would run: start /wait foo.exe /s /a /s /sms /f1c:\temp\foo.iss The first /s is only needed for a completely silent installation. If you leave it off, the PFTW package will show you a status bar as it extracts the InstallShield tree to the temporary directory. InstallShield with MSI Recent versions (7 and above) of InstallShield's tools are able to produce MSI files. Read InstallShield's documentation for full details. These MSI files may be shipped alone or with a setup.exe installer. These installers in turn come in two flavors, called "InstallScript MSI" and "Basic MSI". InstallScript MSI uses the traditional InstallShield switches. Basic MSI is another story. To perform an unattended installation using a Basic MSI installer, you provide the /s /v"..." switches, where ... represents any additional switches you want to pass down to msiexec. These should include the /qb (or /qn) switch to make the installation non-interactive, so a minimal invocation would be: setup.exe /s /v"/qb" Just to make things interesting, any of these mechanisms might be combined with PFTW. For example, we eventually figured out that the IBM Update Connector requires these flags for unattended installation: updcon532.exe /s /a /s /v"/qb" The first /s tells the PFTW installer to extract silently. The /a tells it to provide the remaining switches to the underlying setup.exe. The second /s tells setup.exe to run silently, while the /v"/qb" tells it to pass /qb to msiexec, which causes msiexec to run non-interactively but display a basic interface. Finally, InstallShield has a KnowledgeBase article which is less helpful than you might expect. Are we having fun yet? Wise InstallMaster InstallMaster from Wise Solutions is a competitor to InstallShield. You can usually identify the installers it produces by running "strings" on the executable and grepping for "Wise". InstallMaster installers are supposed to recognize the /s switch to perform a silent installation. And in our experience, they generally do. But there is no way to set options, and the exit status is meaningless. Note: This product has been rebranded the "Wise Installation System". Don't let them confuse you. Inno Setup Inno Setup is an open source competitor in this space. You can usually identify the installers it creates by running "strings" on the executable and grepping for "Inno". The switches for Inno Setup are fully documented in the ISetup.hlp file in the Inno distribution. Here, is an html version. Thanks to Lawrence Mayer for it. In our experience, the /silent switch is usually sufficient for a basic unattended installation. But to be completely sure, we recommend /sp- /silent /norestart. Note that the /verysilent switch may reboot the machine without prompting, which is pretty much the worst of all possible worlds. So if you use /verysilent, be sure to use /norestart as well. Nullsoft Scriptable Install System The Nullsoft Scriptable Install System (NSIS) is another open source installation system. It was created by the WinAmp authors to distribute that application, but it is now a general-purpose system which anyone might use. When an NSIS installer runs, it creates a little window which says verifying installer: N%, where N counts from 0 to 100. So you can recognize these installers by this behavior. (Actually the verification procedure is optional, but most installers have it enabled. As an alternative, you can run "strings" and grep for "NSIS"). NSIS installers recognize /S for silent installation, /NCRC to suppress the CRC (verification) step, and /D=dir to specify the "output directory", which is where the program will be installed. These options are case-sensitive, so be sure to type them in upper case. Incidentally, all /S does is change the installer script's SilentInstall attribute from "normal" to "silent". What effect this has, exactly, depends on the person who wrote the script. If /S does not perform a silent install, consider submitting a bug report to the installer's creator. Ghost installer Ethalone's Ghost installer is just another commercial product, available in free and commercial editions. The free edition is nothing but the compiler, which takes XML files; the commercial edition is the compiler plus a graphical editor and wizard to create these XML files. When a Ghost installer runs, it creates a little graphical window which says "Ghost installer wizard. Setup is preparing the Ghost Installer wizard..." together with a progress bar. Ghost installers recognize -s (case-sensitive) for silent installation, but that works only if the person who created the installer defined a standard installation type (if there are more than one). If you have trouble to get it silent you might try to guess internal variables and pass new values at the command line using -var:MyVar=value. Unfortunately, using "strings" will not help you guessing. See here. Other command line parameters are -r (repair), -c (add/remove), and -u (uninstall). Microsoft hotfixes and older packages Most Microsoft hotfixes respond to the /? switch, but they do not always tell you everything. According to KB article 816915 and KB article 824687, Microsoft is moving towards standardized packaging and naming for hotfixes. But they are not done yet. Modern hotfixes support /passive (formerly /u) for unattended installation, /norestart (formerly /z) to suppress the automatic reboot, and /n to skip backing up files needed for uninstalling the hotfix. Some hotfixes use an old Microsoft packaging technology called "IExpress", whose switches are more-or-less documented in KB article 197147 and an old USENET post. These installers first extract some stuff to a temporary folder and then run a command from inside that folder. They support the /t:path switch to specify the temporary folder name and the /c:command switch to specify the command to run. Specifying just /c suppresses running the command at all, so you can use /c /t:path to extract the hotfix just to look at it. These packages support the /q switch for quiet operation, except sometimes you have to use /q:a instead. They also support the /r:n switch to suppress the reboot. Sometimes these do not work and you have to fiddle with the /c:command switch; see the second "NOTE" in KB article 317244 for an example. Leave it to Microsoft to make systems administration an experimental science. If all else fails... If the application simply has no unattended installation procedure, you can create your own. I prefer to avoid these approaches if at all possible, since they are relatively unreliable and difficult to maintain. Repackaging There are several tools around which can take a snapshot of a machine's state before and after a manual installation, compute the differences between the states, and bundle them up as an "installer". The Wise product line provides good support for this, and Microsoft's free tool provides bad support for it. The problem with this approach is that it fundamentally cannot work reliably. An installer's behavior may depend on the exact initial state of the machine, such as the OS version or the presence/absence of other installed software. So the repackaged installer will almost never do exactly the same thing that a fresh installation would, unless the target machine is completely identical to the original machine. In addition, for every new release of an application, you will need to repackage it again. And there are other disadvantages which even Microsoft recognizes. For these reasons, we think repackaging is a very bad idea and we strongly advise against it. AutoIt AutoIt is a free tool which can simulate key presses and mouse clicks, following a script customarily named with a .aut or a .au3 extension. Most installers have a sufficiently simple and consistent interface that a very short AutoIt script suffices to automate their installation. The AutoIt distribution includes very good documentation. The Unattended distribution includes both versions 2 (AutoIt.exe) and 3 (AutoIt3.exe). These versions differ in their script formats. Currently, all scripts that are shipped with Unattended are written for version 2, but we plan to switch to version 3 in the future and advise to create new scripts only in version 3. AutoIt scripts do have drawbacks. First, you must be careful when upgrading to new releases of an application, since the installer's UI may have changed. More worryingly, AutoIt scripts are theoretically unreliable because they do not let you determine when a sub-process has exited. You can tell when AutoIt itself exits, but that is not the same thing at all. For example, an installer's last window might disappear while the installer was still working. Your master script, waiting only for the AutoIt executable, would then proceed, starting another installation or rebooting the machine. AutoIt provides Run and RunWait primitives, but it does not provide a way to wait for the termination of an application which was invoked by Run. If it did, this race condition could be avoided. In practice, it does not matter much, because most installers do finish their work before destroying their last window. Just make sure your .aut script uses WinWaitClose to wait for that last window to vanish. You should make sure that your script contains a [ADLIB] section to catch surprising reboot requests. If any mods care to add to this and update it please feel free. -infringer-

Yes it isn't all that hard but I found good documentation if you are aware of the package on which switches to use. There is also resource hacker that will tell you what type of setup as well as USSC.exe which will tell you the switches to use. I was using very silent in capitol letters thinking that should do the trick but no you must use all for it to work correctly. I thank you for the help it was actually a couple of days of tinkering and reading all the wrong stuff till I bruteforced every possibility and figured out just what it was that I was doing wrong and the thing I was doing wrong was assuming go figure that one always gets you in the end.

Whats been done? The AVG crapware that they try and make you install has been replaced with the simple hello world cmd line output. The software was repacked and now all you have is peazip. 5.74 MB a9d328919773f1ad3d7a825c432e8d4c

ok so it appears it works it was just the switches I was using were incorrect for the setup type man I will tell you silent installers rule

I am sure Reaper could create a nice guide on how to do this if he has time he seems to be the posting machine when it comes to addons and such I wonder if he'd be up for helping me out is it illegal to contact people here by private msg without first getting their consent first I know this is a foolish but common rule at some forums... It is foolish because if you want to contact someone you first have to contact them in order to contact them a bit trivial the time wasted doing such a thing could be spent on better efforts and the time wasted by the responder replying he could have used to answer the question to begin with lol Anyhow I want to create this setup first for a guy or gal on this forum then I have some setups of my own to work out.

Wow do I feel like a numbskull lol the problem was the syntax err there was 2 periods between exe must have put them there by mistake. OK so I got that part down I got it running. Still need help though with the following when I execute it it still asks me for administrator privlidges to run the installer... Could someone please do a walk through on how to create a proper addon from an exsisting installer I know how to unpack and edit the original installer but the issues I have now are the fricking popups that appear askng me if I want tto do what I already told it to do and disabling UAC is out of the question for me personally there has to be a way to make this bend to my will and work properly wthout running a less secure version of windows.... Someone have time to help me troubleshoot this issue they say there are no switches that will stop this I don't get it I can easily wreak havoc by deleting someones system files on them with an SFX but I cannot install a program kinda strange... Anyways would be nice to know if it is nessacary to get around this during the installation of windows or how others are doing this... Thanks!

I haved tried yummi with less success I would like to just suggest to you to try Sardu. It is basically the same thing but I have had more success with Sardu then I have had with yummi. Could likely just be luck but either way give it a try.

It may be that the OEM disks were released later or sooner then a digital version of the ISO espically being that it is an OEM for system builders in your case. It could be a factory based thing that the date of CD creation is marked for in house reasons or whatever ... The truth is I really do not have an answer that is fully positive but from the standpoint of logic any digital version is going to be the first thing to hit the streets. It takes a while for the physical goods to be produced... Most likely stuff is outsourced to china and is shipped their on a slow boat and comes back on the same slow boat. And it is possible that their were a limited amount of system builder OEM discs and they had to produce a second run of these discs at the date you specified either way all dates aside for it to be a legit windows ISO it must be the original release or SP1 their are no other versions available all dates aside.