Tatsh

I imagine with ResHack or XNR you can modify the resource to get rid of the menu item. You need to use PEChksum and movelatr once you do or else Windows won't recognise it and WFP will replace the DLL back to original. I am going to try this myself later. Will post my results.

I tried to modify the MSI to skip the action of the licensing and the updating but then it does not validate properly. Msiexec finds it as a non-valid package. Tried modifying with Orca. Surprisingly, Orca does show that default action of closing out the license screen or saying 'No' even though no such button exists (again it's a very custom window) automatically sets Ad-Aware into free mode.

I've been trying to do the same thing. For the previous version I was using an AutoIt script that was simply wait for the window and hit Enter, but that did not work with this new version. Discovered today though: Empty all your %TEMP% directories. Run the setup programme like normal, but let it get to the point where you are about to click Next. Do not pass it any switches. Now go into all your %TEMP% directories and find an MSI. Mine was named dfc61.msi. Now you may execute like this: msiexec /i dfc61.msi /qb. The problem is the licensing. The licensing application for Ad-Aware will run immediately after the installation is complete, and what I found was that AutoIt cannot identify any elements of this windows, so only click/mouse functions could possibly skip this part. However, if you kill this programme, AAWLic.exe, then Ad-Aware on first run assumes you clicked 'Use Free'. You will need to use AutoIt a little bit. First, copy the MSI to %SYSTEMROOT%\system32 because that is where msiexec is, unless you want to code in a batch file a way to give the full-path to the MSI to msiexec. In my case, I'm running it like the following (AutoIt code): Run("msiexec /i dfc61.msi /qb"). AutoIt does not tell msiexec that it's running in somewhere else other than system32 and then is able to change the reference of the MSI file. If the MSI file is always at one point, you can change it in the AutoIt code. Essentially, you need to run this part, then wait for the window of the licensing which is handled by AAWLic.exe, give it Alt+F4 to kill it. Updater now runs, but it will automatically close. Then continue as normal. @ECHO OFF REM Copy MSI file to system32 temporarily copy /y "dfc61.msi" "%SYTEMROOT%\system32\dfc61.msi" REM AutoIt executable "ad-aware-free-installer.exe" REM Now remove the MSI file del "%SYTEMROOT%\system32\dfc61.msi" exit You can do more of course, but the main thing is getting past that license screen. Here is the AutoIt code: Run("msiexec /i ad-aware-2008-7.1.0.8.msi /qb") WinWaitActive("Product registration") ; Send the Alt+F4 combination Send("!{F4}") ; Updater now runs, but it closes automatically I usually remove the desktop shortcuts, and the shortcut to Ad-Watch since it does nothing. del "%USERPROFILE%\Desktop\Ad-Aware.lnk" del "%USERPROFILE%\Desktop\Ad-Watch.lnk" del "%USERPROFILE%\Start Menu\Programs\Lavasoft\Ad-Aware\Ad-Watch.lnk" Hope this helps. I've tested this several times on a VM, seems to work pretty good. Yes, the updater sucks in that it has a time out of 10 seconds to wait, but this is negligible to me. I will have this tested on a real machine by tomorrow for sure.

Very light and GPLv2 PDF reader for all Windows: SumatraPDF

I tested my nLite CD (with SFC left enabled) in VirtualBox 1.4.0 and used nLite 1.4 beta to make it. I installed the guest additions (basically drivers) for the virtual PC and upon reboot I immediately get the SFC errors. I turned on File Monitor to see what files get copied but it didn't seem to catch anything interesting (plus it seemed Winlogon did the copying?). I replace the SFC files with ones from a slipstreamed installation that doesn't have SFC (and disable SFC) or I tell the registry to look for other places for the CD. From a slipstreamed installation with disabled SFC, copy the SFC files either off its hard drive or the CD (you will have to expand them). For the installation with SFC you will need to use something like WfpReplace (a command-line app) to replace the files. Google it. I think the most effective way to fix for the moment is to copy the I386 folder to somewhere and edit the registry in these places similar to how I do it: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "ServicePackSourcePath"="C:\\" "SourcePath"="C:\\I386\\" ServicePackSourcePath should be the folder just before the I386 folder as far as I can tell (Original value is the drive letter from which Windows was installed). After once placing the nLite CD in to fix and applying the registry change (and I've done this on numerous PCs), it seems I do not get the WFP message again. I think it finds the spot properly in C: or wherever I place I386. I always copy I386 because I do not want to have get the CD out or mount an ISO or anything like that. So, the best thing to do if you want to keep WFP is to install Windows, install all drivers with no reboots in between, and then reboot and insert your nLite CD (or keep it inserted during reboot) and let it do its thing. After that copy your I386 folder to C: and then apply these changes to the registry. Reboot and make sure things work still. Hope this helps.