strel

Hi. The logs are there in the same manner original installers left them in the %TEMP% folder, I just renamed and applied maximum verbosity to install logs only, uninstall logs are created automatically in the same folder by the installers, but are not renamed (I'm looking for a simple solution to do it from Add/Remove Programs but I'm not being able to manage msiexec.exe ... /l*v %TEMP%\NETFX##uninstall.log switch to work on the uninstall string). They are there to allow looking for errors in case it happened. I use a ccleaner scheduled task to remove them regularly on idle time. And of course you can use a del command to remove them. About x64 add-on, maybe it's better you extract installers to test it, pay attention to the .mst files, Insted is your friend for doing that. Ask me if you have any questions. EDIT: in fact the way install logs are stored is not exactly as the original one because install logs overwrite previous one for that framework/language, so there would less install .log files stored in the %TEMP% folder.

I'd buy a powerfull mobo in order to upgrade parts later, with the highest FSB frecuency in the range of CPU and memory type you want, and I'd save with rest of the parts except memory and HD quality (not quantity there you can save too), then you'll have later the opportunitty to upgrade the parts while building a great machine and you can sell old parts or keep them for replacement.

Read the guide unattended guide (link above) for install methods, there you'll find how to be able to monitor what's installing. About making silent installers each software is different from another. See Applications forum. You can use too add-ons for that programs applying them to your OS source with nLite or RVM integrator but probably you're not going to monitor what's installing instantly+ with this method.

The script will ask you for it if needed. You'll need NDP35SP1-KB963707-x86.exe in the work folder in case you are building an installer/nLite add-on containing .NET 3.5 SP1 framework, if you allowed it to install .NET Assistant add-on for Firefox therein, through the related setting in the .ini file. KB963707FIX.mst is precisely a fix to get that hotfix correctly applied to the installer, otherwise it generates errors on install (if I recall it correctly).

Not sure why it fails in your first trial. For your second trial, the sfx accept multiple RunPogram entries, try RunProgram="hidcon:%SYSTEMROOT%\REGEDIT /S UPDATE.REG" if you want to hide the console, and don't forget to save the config.txt in UTF-8 mode, otherwise it won't work. Remember that 7zsd.sfx included in the SNMsynth packet is yet compressed with UPX. And finally you got it, nice idea to make an ad-hoc _SNMsynth.cmd, are you having questions about how to do it?

Hi djanz. Suppose it would be similar but I'm sure there would be things to adapt and test. Someone asked me about this time ago, at that time I was thinking in making a 64-bit version of the script, the problem is that I'm not having access to a 64-bit machine, so I'm not doing it. What I can offer is my help to anyone who want to do it. At the moment you have a better option with HJW's .NET x64 installer that includes regular hotfixes, thx to RickSteele for the link. Cheers.

Hi Pleased to read your good news.

But this is only a workaround for installing, if you don't get .mst files are effectively copied over a subfolder of the installers cache folder (%SYSTEMROOT%\Installer\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}), and you remove the folder from wich you are installing .NET, the uninstall process will have access to .mst files, and will not be able to remove the tweaks made by SNMsynth installers so you may have incorrect win/ms update messages. You need to get .mst files copied over that folder, this way all fixes applied will get properly removed on uninstall. I'd try changing the permissions of %SYSTEMROOT%\Installer folder as explained before, to get .mst files copied during install. Or try making it manually, to get the folder name you need the GUID of the installer, you can get it from registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, there you'll see varios GUID named keys, browse through them looking for .NET in DisplayName values, and you'll have folder name. Copy .mst files used by the installer for that framerwork version (in the TRASFORMS= property of the install command of each framework version, inside the install script of SNMsynth installer) to the installer cache subfolder. As you see it's far more easy to fix intaller cache folder permissions.

I didn't know its features, thx; and haven't realized of the "price per seat"

Well, I still think something is obstructing .mst files to get copied over the installer cache folder. If we read the log file, install process first try to look for the .mst files in the installer cache folder, when it don't find them, then it searches them in the installer source folder, but .mst files are not in the installer source folder, they are in the install script folder, I may have to change this for the next version. I think if you give permissions to the installer cache folder or if you manage to put a copy of the .mst files in the DNF20 DNF30 DNF35 folders when the installer uncompress (or if you uncompress the installer and then put a copy of .mst files in folders DNF20 DNF30 and DNF35 manually and then run INSTALL.cmd), you'd solve the problem. About permissions I think this is self explicative. Again tell us about your progress please.

I think jaclaz was referring to hide console apps, not the .vbs

Great you include the log file! After searching around, error code 2203 seems to suggest a problem with permissions that seems to be obstructing .mst to get copied to the installer cache folder, typically %SYSTEMROOT%\Installer and/or to be uncompressed to the %TEMP% folder. To overcome this error try giving full permissions to SYSTEM account on these folders, begin with %TEMP%. You may need to give full permissions on that folders too to current user account. Please tell us about your progress. Is it happening that to any of you using win 2K3?

I think "VisualFXSetting" should be VisualFXSetting and you can find this useful.

No idea if this is possible but maybe renaming workaround the issue, and then renaming again after copy.

I'm thinking of giving a password to the file or using cacls command to set permissions to the file.

I'd check driver inf file to check where this file is supposed has to be in.

Yes and yes.

I only use common sense and noscript add-on for firefox, to avoid every script not comming from the web page I typed in the address bar + the rest of the protections it includes; and maintain my own whitelist of common online "for the web" services like youtube and many others. Never had a malware infection and have no favourite application for malware scanning because I don't use them on my machines. Used ad-aware in the past to scan other people's machines because it was pretty famous at that time, simple to use. Recently I tried briefly HiJackThis to see how it looked, concise, like it.

You say you installed in IDE mode, then you switched to AHCI. There's plenty of info around preventing you from doing this because because it causes problems with the HD. This could be of interest in your case, same chipset: HOWTO: enable AHCI mode after installing Windows.

If you want to spend some bucks, I recently had notice of Universal Imaging Utility. I cannot add any reference about how it works.

This would be of interest: http://www.techspot.com/vb/topic7746.html

No, but I don't think you'd want to change to maximum, you could get unexpected results as minimum size for everything in the screen as well as minimum refresh frequency. What you have to find is whether this utility works when you want it, and if that's the case what you can do is to process the list of available resolutions to find something reasonable. For example look for the maximum resolution available at a specified refresh rate and color depth, or look for the maximum refresh rate for a determined resolution and color depth given that a monitor that support a maximum resolution of XXXXxYYYY should have a screen size of ##' and for this size an optimal resolution should be XXXXxYYYY, less than the maximum... And in case you don't get an utility that works in RunOnce, you can always try to make the script work after logon, for example, copying it in the startup folder and including a line on it to add a value in the RunOnce key in the registry to delete itself in the next reboot.

Try with QRes. Link edited to a download location.

The default option installs the firefox add-on as the original installer do, moreover, for this default option the script makes you apply mandatory KB963707 hotfix, as it contains important fixes for FF add-on like being able to install on firefox > 3.0.*, giving the uninstall button, but more important, removing the .NET user agent that were reporting every webserver about the .NET update condition of your machine. This setting is useful in case you just don't want to install the firefox add-on. 2 simurqq (see above) and everybody In point 1 of your "applies to both scenarios" section there's something incorrect. It's not mandatory to set "DNF_FF_ADDON=YES" it's a choice. As explained in my previous lines.

As long as office update will not be up to date would be a good idea.