strel

1. I'd put the extra updates after. 2. If you do that you'll not be able to load SATA/SCSI drivers with F6 at the beggining of the setup. 3. Up to you, you should know how annoying could be or how practical. I have it dissabled. 4. As long as you don't remove anything you need to do this, and you make room for your needs, I don't think so. 5. As long as your software uses registry to stablish paths, I don't think corruption would be a problem.

Try setup.exe /? or /help. If you can get the to the .msi file maybe you can apply this guide you said. I don't know.

Try to unzip the .exe, the .msi is probably built-in. Could be a switch for .exe to extract it.

Now that you have the admin install use a compressor to make a self-extracting packet containing the admin install. This sel-extracting installer should run the embedded admin install with something like: msifile.msi /qn norestart /qn means completely silent, /qb means progress bar with cancel button, /passive means progress bar without cancel button (but this one cannot be used with windows installer versions previous to 3.0, so don't use it for win2k). Extra options vary upon your needings, see windows installer options in the link I dropped in my previous post. If you want the extraction process to be silent too I recommend you use 7-zip SFX modified module, that lets you hide the unzipping progress bar, for building the self-extracting packet, and 7-zip for compressing it. Here you'll find a tutorial on how to do it with the modified or the original SFX module. If you use the modified SFX module you don't need msistub.exe because the modified module makes its work. Dialog section modification in poing 8 of the tutorial only applies to 7-zip SFX original module.

As far as I know AVG would generate false positives on every .exe embedded on a file that has been compressed with UPX as the .exe embedded in this file. That kind of contact with AVG is suggested in the link you provide but should be done by an AVG license holder as stated in the contact link therein. All the info AVG needs is in this forum, so up to you.

I don't know how your office installer works, but try setup.exe /? to see if there's swithches for silent or passive installing. And there's a specific office forum, you can try there. Your last KB929399 entry is not necessary. Xable's packs probably don't appear because they are built this way. .cat files are catalog files, and you rarely will need it for installing online anything, just to avoid some security dialog boxes. As long as you're using nLite, you can remove them with option for it.

EDIT: OK, now that it's confirmed, I've got to tell you DON'T WORRY, those error messages only mean the unused 3.5 SP# installer locale files (very small size, and related only to 3.5 SP# install process messages, not to 3.5 SP# framework at all) are not being removed from installer including 3.5 SP#. This is a new feature of the latests script versions not working properly, but it's not a real problem for the installer. 2 egd Check again, the langpack for 3.5 SP1 should be in the ARPrograms list, but not inmmediately after the .NET group.

I think yes, help says %SOURCE% is CD/DVD drive letter I suppose is in the format x:\ I don't get what are you meaining with "copy only", it will run from source media.

I almost have no experience with RAIDs but I think you need need the same controller to mount the RAID, or at least one compatible, in case it exists.

Something like: msiexec /a msifile.msi TARGETDIR=pathofyourchoice See ms installer command line reference and properties reference to not get lost.

Check SNMsynth.cmd is last modified 16-03-2009 19:29. Are you using this version? If not, download again.

I have no idea how MSFN codec pack 5.0 works, but you can try using gspot program to identify the encoding of the streams of the video. Once identified check if the coded pack supports what you need and if you are missing something. If it's not supported look for the codec directly from its source web or another codec pack or so. You can try too video lan client player, it has its own filters embedded and open many formats without worrying about the codecs installed. Keep an eye too to ffdshow directshow filters Qué tengas suerte pibe.

I'm not getting your results and I'm pretty sure you're missing the version, check you're using SNMsynth.cmd last modified 16-03-2009 19:29.

You're not using the latest version 20090316b, isn't it?

You are mixing 2 different install methods, GUIRunOnce and RunOnceEx. start.cmd is built as if it is going be used with RunOnceEx method, but is triggered with GUIRunOnce method. That's why it executes on second logon, because start.cmd only imports keys to registry for next logon execution (as with RunOnceEx method) but instead of being executed from cmdlines.txt during GUI Setup, it's being executed on first logon, importing keys to registry to be executed on second logon. And start.cmd is not installing your software because you're using "regedit /s installcommand /f" as your install command and not just "installcommand".

A lot of thx for your fixes. I hadn't read your post until now, sorry. I'll review all this for the next version. And: - Yes, /passive don't show cancel button, at least for win installer 4.5. - .NET 2.0 requires win installer 3.x - The .ini file OS setting is only to define the target OS version for the installers bypassing default target that is host OS version from which they are built; so even if you change .ini file OS version setting and bypass in-script OS version checking, you cannot build installers for vista or 7 but from this versions for win2K/XP/2K3 x86. - There's interest in having a script that cover all needs, at least mine.

2 Brazillian language users for .NET 2.0 SP# Until I release a new version, to fix KB829019 showing in win/ms update, open a console and type this command: I fixed a typo error sorry. REG ADD "HKLM\SOFTWARE\Microsoft\DevDiv\URT\Servicing\1.1\RED\1046" /V Install /T REG_DWORD /D 00000001 /F 2 hipo_loco Have you copied the installers to ..\i386\SVCPACK folder?

No, the script handle .NET and its updates, this is a windows update, it's only mentioned for completeness. But if you pretend to build an unattended windows set integrate it as you used to do; and if you're using the installers on a installed windows, then simply let update system do its job.

Those are not last versions so you're going to see KB951847 as a high priority update (including in this case 3.5 SP1 redistributable (2.0 SP2+3.0 SP2+3.5 SP1)+ hotfixes + langpacks for these versions). KB951847 fix is not applied for these versions, it's only applied if you build updated installers.

Are different SP# steps of the same #.# versions. Are incompatible.

You're are taking as a fact something that is not real. This supposedly needed restarts doesn't take place when you installed .NET normally with ms original files, and doesn't happen with this installers. For your serenity, this method uses administrative install technique, that is something ms implements in its installer technollogy, .msi files, that is kind of a preinstall. This method is not inventing the wheel. About hotfixes, with this script are not showed as installed, i.e not listed in Add Remove Programs, but are identified by MBSA and win/ms update system as installed. But as you can reach the building script code and/or installing script code, you can remove this feature in one of them manually to your liking. And SNMsynth.cmd is not used to install but to start the SMNsynth installer(s)/add-on(s) building process.

Use HFSVCPACK folder for switchless installers.

I'm almost sure is not possible at this moment. I don't have x64 machine to adapt it, but It's probably I can have access to one soon.

Sorry, should have tested it, there were syntax bugs. Fixed now.

Sorry, should have tested it, there were syntax bugs. Fixed now.