Leaderboard

I think there are some people in this forum who wonder how nLite slipstream updates. (such as these people) Personally I don't use nLite much. I prefer slipstreaming the updates myself rather than using such tool (just because I cannot trust the latter). However I did some experiments with nLite and I can share what I found here. My OS is Windows XP Professional SP3 (x86). I only tried the "Hotfixes, Add-ons and Update Packs" feature, which I'm interested in the most. Then I use Process Monitor and file difference tools to track nLite's actions. Here is the result - how nLite slipstream (regular) Windows XP updates. (Please note that there might be errors in the info below.) 1. Extracting the update contents nLite extracts all update packages by running this command with each package: "windowsxp-kbXXXXXX-x86-enu.exe" -q /X:"%CDPath%\hottemp" (Assume %CDPath% is the path to your Windows installation CD files, and your Windows XP is English version.) Then, nLite will check whether it is possible to use steps 2 to 4 below to integrate the update. In a few cases, nLite will say it cannot and asks user if he wants to use the regular integration methods. The "regular integration methods" provided by nLite is actually running this command: "windowsxp-kbXXXXXX-x86-enu.exe" -q /integrate:"%CDPath%" 2. Extracting the cabinets For some updates, it is necessary to extract the cabinets. nLite first tests them using 7-zip: 7z.exe t I386\%cab_file_to_extract%.cab Then they are extracted internally. nLite seems to invoke functions in the library called cabinet.dll. Extracted contents of DRIVER.CAB is stored in "%CDPath%\drivertmp". Extracted contents of SP3.CAB is stored in "%CDPath%\sp3tmp". 3. Replacing patched files nLite picks the files of the SP3QFE branch only. GDR branches are generally ignored. For each patched files, nLite looks up the files of the same name in I386 folder or the temp folders in previous step, extract it and compare the versions. nLite gives a warning when the version of CD files is newer than the patch, and asks user whether to replace the files. 4. Creating the registry patch file - nLite.inf The registry changes in each update can be found in the [Product.Add.Reg] section of the "update_SP3QFE.inf" file. nLite reads this and stores the registry entries in nLite.inf. (Unfortunately this causes a bug, see this thread.) nLite.inf is meant to be installed at the same time when Windows installs optional components. nLite.inf and nHelper.exe are compressed and copied to the CD. (NLITE.IN_ and NHELPER.EX_) 5. Updating INF files These files are changed by nLite (in chronological order): HIVECLS.INF (Only optimizes the file. No entries are added or removed.) HIVEUSD.INF (Only optimizes the file. No entries are added or removed.) SVCPACK.INF (Adds the catalog files to be installed.) NLITE.INF SYSOC.INF (Adds this entry, then optimizes.) [Components] nLite = ocgen.dll,OcEntry,nLite.inf,HIDE,7 6. Compressing cabinets DRIVER.CAB and SP3.CAB are re-compressed by nLite. (This takes a REALLY long time on my computer.) 7. Updating INF files again FONT.INF (Only optimizes the file. No entries are added or removed.) HIVESYS.INF (Only optimizes the file. No entries are added or removed.) INTL.INF (Only optimizes the file. No entries are added or removed.) WBEMOC.INF (Two entries are commented out by nLite, I don't know the reason.) [WBEM.CopyMOFs] ;napclientprov.mof ;napclientschema.mof TXTSETUP.SIF - nLite did three things here. First, in [FileFlags] section, some additional file flags are added. Second nLite adds these two entries in the [sourceDisksFiles] section: [SourceDisksFiles] nhelper.exe = 1,,,,,,,2,0,0 nlite.inf = 1,,,,,,,20,0,0 Third, the TXTSETUP.SIF file is opimized. DOSNET.INF (Adds these entries, then optimizes.) [Files] d1,nhelper.exe d1,nlite.inf [OptionalSrcDirs] svcpack HIVEDEF.INF (Only optimizes the file. No entries are added or removed.) HIVESFT.INF (Adds this entry, then optimizes.) [AddReg] HKLM,"SOFTWARE\Microsoft\Driver Signing","Policy",0x00000001,0 SVCPACK\HFINT.DAT (Only updates that are done using "regular integration methods" will have entries here.) 8. nLite deletes the file "nl_proc.log" in I386 folder. "nl_proc.log" is a temporary file that is used to indicate an unfinished nLite session. ----

upload the ETl file

Yes, you got it right , and that adapter should be fine (the PL2303 should use the "lower" TTL level) . BTW this is explained in read-me-first: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ points #6 and #10 which you really should READ FIRST (ALL of it). BUT, for the record, it is not particularly "difficult" to find which wire is what on a CA-42. The FGA #6 deals with it: http://www.msfn.org/board/topic/147532-fga-for-the-seagate-720011-drives/ jaclaz

Thanks for the report. I see no reason to still call it Beta. WinNTSetup 3.5 Final added support for WimBootfixed mounted ISO files on Windows 8 was not unmounted on exitfixed EditionID was not detected on self made WIM filesfixed missing English fallback on not translated stringsadded combo box to select bcdboot firmware optionadded new cmdline switch: -bcd:{ALL|BIOS|UEFI} to specific bcdboot firmware option

Windows 8 Release Preview theme with blue close button without glowing.

Mimo doesn't seem to update his list for two months. Should I give a quick summary of what's changed? March 2014 April 2014 March 2014 KB2935092 | hotfix | timezone | 42048 | replaces KB2904266 (cumulative time zone update) (OBSOLETE:) KB2925418 | MS14-012 | IE | 42219 42207 | replaces KB2909921 in MS14-010 KB2929961 | MS14-013 | qedit.dll | 42113 | replaces KB2845187 in MS13-056 KB2930275 | MS14-015 | win32k.sys | 42101 | replaces KB2893984 in MS13-101 KB931125 | optional | rootsupd.exe (March 2014) | 42092 | WGA Validation Required KB2934207 | "high-priority" | EOS notification | ENU direct download | Nagware. Better hide this update rather than install it. April 2014 KB2936068 | MS14-018 | IE | 42431 42436 | replaces KB2925418 in MS14-012 KB2922229 | MS14-019 | kernel32.dll | 42329 | replaces KB2758857 in MS12-081 (Office 2003:) KB2878303 | MS14-017 | WINWORD | 42408 | replaces KB2863866 in MS14-001 (Office 2003:) KB2878299 | MS14-020 | MSPUB | 42403 | replaces KB2810047 in MS13-042 May 2014 out-of-band security bulletin KB2964358 | MS14-021 | mshtml.dll (IE) | 42591 42588 | None MSRT and Flash Player omitted here.

Hallo JFX, Thanks for the new version and I just like to confirm that Beta 4 is doing fine. Wimboot option is working OK and I can use UEFI Secure booting from MBR FAT32 USB-Stick used as Boot Drive.

The queer thing is that what are actually "real" improvements are too intelligent to be marketed. Example, the newish WOF: http://reboot.pro/topic/18345-wimlib-with-imagex-implementation/?p=183343 which might be (or become) a feature of incredible utility, was never AFAIK ever (or scarcely) mentioned. I believe (and this is consistent with MS history) there are two sides of the company, the developers (that very often are quite good at writing software, but, understandably know very little about communication) and the designers/marketers (that know nothing about anything and just give people what they think people may want to hear). The link between the two, which is - or should be - the management, is what lately has failed, and failed big (IMHO). Now we have reached "pure folly" with the stupid decision that update 1 is compulsory to have future updates. Even if, on the outcry of all the serious IT people they managed to enlarge the "window" from 1 month to almost 4: http://arstechnica.com/information-technology/2014/04/why-the-windows-8-1-update-probably-means-no-more-service-packs-for-windows/ this timeline still does not meet the expectations (and actual needs) of companies where security and uptime is crucial (please read as all those that are in a field where "big money" is). Given the issues that (historically) each and every "major" critical update has introduced in MS OS's the idea of the "new" model of "continuous updates" must be for IT professional a terrible nightmare. The "one size fits for all", that I criticized also in the good ol' times when the user OS (Windows ME) was merged with the professional OS (Windows 2000) to create the Windows XP, had some sense (though forcing upon "home" users features and complexities of the "professional" world), but now forcing upon "professional" users features (and vulnerabilities) to have a "same" OS that can be appealing to the home user is suicidal. jaclaz