[Guide] Assembling & Integrating a Win 7 AIO Update Pack

[RP]

This is an unofficial guide I've put together for integrating an AIO update pack for your Win7 x86 or x64 install using Onepiece’s WINNT 6.x True Integrator. It’ll allow you to easily integrate hotfixes and component addons for an integration comparable to the best of the XP update packs such as OnePiece’s. The guide lists in one place all of the components you’ll need, and shows step-by-step how to do the integration in clean, easy-to-follow fashion.

Disclaimer: Emphasis on the unofficial. No guarantees on individual results, and I encourage self-troubleshooting and finding your own shortcuts to improve on these methods. If anyone wants to officially adopt, adapt, update, or clean up this guide, feel free to use at will.


PART 1: TOOLS YOU'LL NEED
¦ OnePiece’s WINNT 6.x True Integrator
Download: http://www.ryanvm.net/forum/viewtopic.php?t=8450

¦ Windows 7 host (out-of-box install) or Vista host with WAIK installed
WAIK download: http://www.microsoft.com/download/en/de ... en&id=5753
NOTE 1: WINNT Integrator will not work on an XP host, but does work in a Win7 virtual machine hosted on XP.
NOTE 2: I believe if integrating an x64 install you need to be running on an x64 host. Running x64 in a VM and doing integration there is a workaround if your're on an x86 host.

¦ SoLoR's update pack
Link: http://updates.mihgroup.eu.org/. Alt site with just the raw files: http://hotfix.chris123nt.com/.
Official issues/discussion forum link: http://forums.mydigitallife.info/thread ... repository

¦ OnePiece's WINNT True Integrator addons
(see individual items and d/l links in Part 2.)

¦ Various switchless installers as other component addons
(see individual items and d/l links in Part 2.)

¦ 7Zip or equivalent archiver capable of extracting Windows Update .MSU files
7Zip download: http://www.7-zip.org/

¦ CabPack or equivalent CAB file creator (MAKECAB.EXE, etc.)
CabPack download: http://www.softpedia.com/get/File-manag ... Pack.shtml

¦ ImgBurn or equivalent ISO maker/burner (Nero, etc.)
ImgBurn download: http://www.imgburn.com/

¦ Windows 7 USB/DVD Download Tool or comparable utility for making ISO’s bootable (e.g. ISOBuster)
WUDT download: http://wudt.codeplex.com/


PART 2: COLLECTING THE UPDATE FILES
1. Create these empty folders and subfolders on your hard drive:

Code: Select all

..\Win7\Mount
..\Win7\ISO
..\Win7\IntegratorCABS
..\Win7\SetupCABS
..\Win7\Addons
..\Win7\Temp
..\Win7\Temp\Extracted

NOTE: You can name these whatever you want or use alternate means of organizing. Just make sure things go in the right place.

2. Get SoLoR's pack. On the main site the very first link, "KB000000" is the hotfix rollup available in x86 or x64 flavors. Rest of the page lists the contents (all KB's also available for individual download). When you download the hotfix rollup .7z archive (x86 or x64 as needed). Extract the archive into your Temp\Extracted folder.
NOTE 1: SoLoR posts individual updates immediately as MS releases them, while the hotfix rollup is updated monthly. If you want the most current possible hotfixes, check the changelog at the top for date stamps newer than the monthly rollup, then download the individual newer KB's.
NOTE 2: If SoLoR’s changelog shows any removed KB's since the last monthly rollup, delete those .MSU's by KB number from the extracted archive. Note that some of these KB's may reside in the pack's subfolders "IIS", "MSMQ", "NFS", etc. Easiest method is to do a search in Explorer from the parent hotfix folder for “KB*.msu” to pull up every hotfix file in the entire pack.

3a. Navigate to the extracted "Integrate to installation media" subfolder. Move these CAB's into your SetupCABS folder. These hotfixes not applicable in the Integrator since they're for the bootable pre-Setup (the Integrator only touches the main OS image).

3b. Navigate to the other extracted hotfix subfolders. Move all of these .MSU's in with the main hotfixes, then delete the empty subfolders.

4. Get SoLoR's additional update components. You'll want to use the alt download site with the raw files for easier navigation, since these optional KB's are not in the main pack and the main site's layout is not crystal clear at explaining that. Navigate on the alt site's directory tree to the /Windows.7/Additions/ folder. Download the following .MSU updates (x86 or x64 as needed) and save to the same place as all your other hotfix .MSU’s:

¦ Internet Explorer 9 (mandatory).
NOTE: SoLoR no longer includes IE8 updates in the pack.

¦ Windows Help (legacy .CHM help file viewer...strongly recommended)

¦ Windows Identity Foundation + Hotfixes (recommended)

¦ Windows File Management API (recommended...get just the .MSU's)
NOTE: Can be turned off as optional Windows Feature in the Integrator or on a running system via Control Panel > Programs and Features > Turn Windows features on or off.

¦ Microsoft Virtual PC + Hotfixes (optional but recommended...get just the .MSU's)
NOTE: Can be turned off as optional Windows Feature in the Integrator or on a running system via Control Panel > Programs and Features > Turn Windows features on or off.

¦ Microsoft Agent (optional; get if you need backward compatibility)

¦ Windows Activation Technologies (optional...get only if you want more draconian than usual Product Activation enforcement)

¦ Browser Ballot (optional...get only if you absolutely need the browser choice startup screen)

NOTE: Do not download System Update Readiness Tool for integration. Not applicable in Integrator. It's not a hotfix but a cleanup tool to run as-needed on a running system to fix potential corruption in the Windows Update installed updates repository. Recommend downloading separately and running periodically as an application on a running system after several rounds of new Windows Updates to keep WU running smoothly.

5. Download the following OnePiece True Addons to your Addons folder:

¦ Onepiece's DirectX End-user Runtime Update True Addon
Download: http://www.ryanvm.net/forum/viewtopic.php?t=6531

¦ Onepiece's Adobe Flash Player ActiveX True Addon
Download: http://www.ryanvm.net/forum/viewtopic.php?t=8378

¦ Onepiece's Microsoft Silverlight 4.0 for Windows True Addon
Download: http://www.ryanvm.net/forum/viewtopic.php?t=6777

¦ **x86 INTEGRATIONS ONLY** Onepiece's .NET Framework 4.0 True Addon
Download: http://www.ryanvm.net/forum/viewtopic.php?t=8317
CAUTION!: Omit in favor of ricktendo's .NET switchless for x64 installs (see below).

6. **AS NEEDED** Download these switchless installers to your Temp folder:

¦ **x64 INTEGRATIONS ONLY** ricktendo's .NET Framework 4 Full switchless installer. Follow instructions in Part 3 for assembling the switchless installer into an Integrator addon.
Download: http://www.wincert.net/forum/index.php? ... 3-13-2012/
CAUTION!: Omit in favor of OnePiece's .NET True Addon for x86 installs.
NOTE: Switchless installer contains both Client and Extended versions, is platform-neutral with both x86 and x64 .NET builds, and offers different installer options. See download link for details.


PART 3: ASSEMBLING THE UPDATE PACK
1a. Use 7Zip, etc. to extract all .MSU's files (extract all in the same Temp\Extracted folder). Click "Yes to All" when asked to overwrite duplicate files.

1b. In Explorer click sort by file type in Temp\Extracted, then select and move all extracted CAB files (and just the CAB's) to your IntegratorCABS folder.
NOTE: If you want to save the source .MSU’s, delete all of the .TXT and .XML files remaining in Temp\Extracted until you’re left with just the .MSU’s.

1c. In IntegratorCABS, delete “WSUSSCAN.cab”. Not applicable in the Integrator; this is just a Windows Update stub file not needed for integration.

2. **AS NEEDED** Use the following steps to pack your switchless installers into addons for the Integrator:

2a. Create subfolders in your Temp folder for each switchless installer, titling each "DotNet4_addon", etc. (or however you want to name them). Addon folder names must include the word “addon”; the Integrator requires it.

2b. Create a "SVCPACK" subfolder in each addon folder, and place your switchless installer EXE in here. The Integrator requires the SVCPACK subfolder to launch switchlesses.

2c. Create entries.ini files named "dotnet4_entries.ini", etc. (or however you want to name them) in each addon’s parent folder. Filenames must contain word “_entries” (must precede “entries” with underscore); the Integrator requires it.

3. Using Notepad populate each entries.ini as follows, customizing the fields for each addon:

Code: Select all

[general]
title = .NET 4.0  ;<-- required
description = .NET Framework switchless installer  ;<-- required
version = 4.0  ;<-- required
builddate = 03/13/2012  ;<-- required
company = Microsoft Corporation  ;<-- optional
copyright = Microsoft Corporation  ;<-- optional
website = http://www.wincert.net/forum/index.php?/topic/9154-slim-net-framework-4-full-x86x64-3-13-2012/  ;<-- optional
customizedby = ricktendo64  ;<-- optional
lastupdatetime = 03/13/2012  ;<--optional
language = neutal  ;<--optional
releasetype = SVCPACK Addon  ;<-- mandatory (addon type)
processorarchitecture = x86  ;<-- optional. "x86" for x86-only platforms; "x64" for x64-only platforms; omit if platform-neutral.

[AddProgram]
dotNetFx40_Full_x86_x64_SlimSetup.exe  ;<-- switchless EXE

NOTE 1: [AddProgram] syntax: Spaces and arguments OK if calling options to the switchless installer; no need for parentheses. If your addon requires running more than one EXE in the SVCPACK subfolder, simply add the other filename(s) on the next line, etc.; the EXE’s will execute in sequence by line.
NOTE 2: These are the minimum entries.ini fields required for the Integrator to work with switchlesses. Optional fields can be safely omitted, but it’s always good practice to give proper attribution for somebody else's switchless work and to the program copyright holder in your entries.ini.
NOTE 3: This syntax will work for ANY off-the-shelf switchless that can run at the SVCPACK stage of Setup, so template this entries.ini format for any other switchlesses you want to install.

4a. Use CabPack, etc. to pack each addon folder into its own CAB file. Name each CAB the same title as the addon folder ("DotNet4_addon.cab", etc.). Set your CAB maker to include the full SVCPACK folder tree in the CAB (e.g. in CabPack check the “Recurse Subdirectories” option).

4b. Put the finished addon CAB's into your Addons folder.

4c. Delete the entire Temp folder because we’re now done with it (unless you want to keep the unpacked addon and hotfix files).


PART 4: INTEGRATING THE UPDATE PACK
1. Extract your Windows 7 ISO file into the ISO folder.
NOTE: 7Zip can natively extract ISO’s.

2. Open the Integrator and select the "install.wim" image file from the “sources” subfolder of your extracted ISO. Select your Mount folder. When the Integrator finishes working select the Windows edition(s) you want to customize, then click “Mount”.
NOTE 1: For full instructions on using the Integrator, see the Integrator download link at the top.
NOTE 2: At each screen on the Integrator you may click “Apply” to apply settings and integrate hotfixes/addons incrementally. Or you can apply all changes at once by cycling through all screens and clicking “Start” at the end.
NOTE 3: You can exit and return to the Integrator at any time without needing to re-mount the image. When re-launching the program, simply re-select your Mount folder.
NOTE 4: To unmount an image at any time cycle back to the first screen and click “Unmount”. Or select “Discard” on the first screen’s drop-down menu, cycle through all of the screens, and select “Start” at the end.
NOTE 5: Make sure Windows Explorer is not open and navigated to the drive with your Mount or ISO folders while unmounting, or else Integrator may pop an error message about an incomplete unmount. The error does not affect your finished image, but it does leave mount residue to clean up. You’ll need to re-start the Integrator afterwards and click “Cleanup-Wim” to clean up incomplete unmounts.

3a. **OPTIONAL** After mounting, click “Next” to the Feature listing for packages screen to enable/disable any OS features (see Integrator instructions).

3b. Click “Next” to the Packages listing screen. Click “Browse” and navigate to your IntegratorCABS folder. Select all of the hotfix files.
NOTE: A handful of the hotfixes may pop dialogs that say the update is for an older or newer OS version. Disregard these messages and click OK each time; all of SoLoR’s hotfixes are fully applicable.

4a. **OPTIONAL** Click “Next” to the Driver packages listing screen to integrate any INF-based device drivers (see Integrator instructions).

4b. **OPTIONAL** Click “Next” to the Local Settings screen to set Language/Timezone or apply a DISM unattended.xml file (see Integrator instructions).

4c. Click “Next” to the Optional Components listing screen. Click "Browse" and navigate to your Addons folder. Select all of the addon CAB's you want to apply.

5. Apply your integration and exit by hitting "Start" on the last screen. When finished, your ISO folder will be updated with your fully-integrated image.

6a. Navigate to your SetupCABS folder and unpack all CAB files.

6b. The unpacked CAB’s will have individual files to manually copy to your ISO folders. Based on the current (March 2012) SoLoR hotfixes, copy the individual files as follows:

¦ KB2023591 hotfix --> Files: loadstate.exe; migapp.xml; migcore.dll; scanstate.exe --> ..\support\migwiz\
¦ KB2495879 hotfix --> Files: wdstptc.dll --> ..\sources\
¦ KB2521168 hotfix --> Files: uxlibres.dll.mui --> ..\sources\en-us\
NOTE 1: Use the same method for any future hotfixes SoLoR includes in the pack's "Integrate to installation media" subfolder. Replacement files and destination folders will vary with new or updated hotfixes. To find out which folders on the ISO the replacement hotfix files go in navigate in Explorer to your ISO’s parent folder, search for each matching filename from SetupCABS, and move/replace accordingly.
NOTE 2: You can do the SetupCABS copying before running the Integrator if preferred. Integrator doesn’t touch these files, only the mounted “install.wim” image.


PART 5: ISO CREATION
1. Open up ImgBurn, etc. and make a new ISO file from your finished ISO folder.

2. Use Windows 7 USB/DVD Download Tool to burn your ISO to DVD or format a bootable Windows Setup USB thumb drive. WUDT adds the bootloader to your newly-packed (and non-bootable) ISO.
NOTE: If you have a utility such as ISOBuster that can extract the bootloader directly from your original Windows 7 ISO you can skip this step and make your new integrated ISO bootable directly in ImgBurn, etc. The bootloader is a hidden file called “Microsoft Corporation.img”, and ImgBurn's "Advanced options" tab (or equivalent function on Nero, etc.) can include it when making your finished ISO.

3. Test your integrated installation in a VM or scratch partition before deploying.


APPENDIX: FUTURE IMPROVEMENTS TO THE GUIDE???
Potential additional resources needed to streamline and better automate AIO update pack creation. . .
¦ Automated batch files for extracting and collecting the .MSU's into one folder and save the manual steps.
¦ Automated batch files for patching the SetupCAB's, to save the manual file searching and replacing on the ISO.
¦ Update key XP Addons and switchless installers on the forums with WINNT True Integrator syntax. It is possible (see thread here to make dual-mode XP/RVM Integrator and Win7/WINNT True Integrator addons using a single entries.ini file. Most of OnePiece’s True Addons for WINNT True Integrator will also work on XP in RVMI using this method. Switchlesses are particularly easy to adapt. Would be beneficial to inventory the switchlesses and addons on the forums most applicable to a Win7 AIO integration and upgrade them to work with WINNT True Integrator.
¦ True Addons for other needed Win7 components, such as .NET 4 x64, Microsoft Update, and other useful extras similar--but Win7-appropriate--to what OnePiece includes in his XP update pack.
¦ Any suggested improvements to this guide. I will infrequently update it for major changes, but don’t intend to keep it up-to-the-moment current. If anyone wants to take over responsibility and upgrade the guide, feel free to use any and all of the text and info within.


GUIDE CHANGELOG
¦ 1.3, 3/22/2012: Updated .NET switchless instructions and d/l URL, fixed minor inaccuracies.
¦ 1.2, 8/27/2011: Updated SoLoR update pack d/l instructions, reflecting recent site navigation changes.
¦ 1.1, 6/19/2011: General cleanup for clarity, formatting, fixed inaccuracies, newfound info. Updated to new WINNT True Integrator name. Improved folder structure in Part 2, #1. Expanded directions and notes as needed. Updated d/l links, added new component addon d/l's.
¦ 1.0, 4/21/2011

[OnePiece Alb]

Hi RP, sorry for my English, Great job, SoLoR's Update Pack, and really the best Update Pack, Yes can be done a windows 7 update pack, for a zero Microsoft Update after the installation of Windows 7, as always 90% and the work of the SoLoR's, but then you can add additional update as optional component, so everything is perfect , from the Update Pack is not there anything you install, and after you remove it, so that each user can choose configurations that already like, example, Microsoft Update, DirectX post-SP3 and many other components that are in Windows XP Update Pack, are just OK for Windows 7, need only review a bit to remove the offline mod (Silverlight True AddOn, and already ok for Windows 7), I actually do not have the time or even MU, directx and other addons for Windows 7, If I find time i will see do OnePiece_DirectX_AddOn_v1.8.0_For_WinXP_Post SP3_INTL-compatible for Windows 7, so even the OnePiece_Microsoft_Update_v7.4.7600.226_FULL_AddOn_ENU

not there any update or program, we can not integrate true mod on Windows 7, we hold integrate them better that in Windows XP


Ciao.

[=[FEAR]=JIGSAW]

WoW RP ... Guide looks good.
I only did a quick browse through & I assume this guide is for a Win7 SP1 Source ?
Does Rt7Lite do a perfect integration of SP1 yet ?
I will need a lot of time to work through this guide properly

Only problem now is, I need some time to make time.

[OnePiece Alb]

for integration of SP1

http://www.ryanvm.net/forum/viewtopic.p ... 324#113324
however, those who want to try it, can do everything from a file. cmd (Microsoft since April 24 2008, explained how to do it ) http://support.microsoft.com/kb/951035/en

in Wincert ricktendo64 has done much guides (based on what Microsoft recommand to do), I recommend using those to integrate SP1

Ciao.

[RP]

Yes...RT7 does an SP1 integrate with the Beta v2.6 build (which is exactly 100% the same as the active 1.7 build except for that extra ability to slipstream SP1). From what I've read the program does a trace bit of hack sleight-of-hand to integrate so it's not as official-official a way to do it as the manual methods. But I've never seen one single comment about it causing any issues and it's so easy to do. Only the most paranoid-orthodox sticklers are likely to prefer the manual method over RT7's one-click integration.

We'll have to see if the upcoming RT7 v3.0, which is supposed to be rewritten guts-out, changes to a fully orthodox SP1 integration method. The method used in the current build was added to the program long ago while SP1 was still in beta so a little bit of a hack was necessary while they were still chasing a moving target with the SP1 pre-releases.


I think both RT7 and DXIntegrator are essential tools to have for overlapping but slightly different specialties. Almost exactly the same way nLite and RVMI are. I hope later releases of RT7 similarly gets synced up someday with baseline addon compatibility with DXIntegrator similar to how nLite is a 90%+ subset of RVMI functionality. That would really boost the addon and update pack ecosystem in a big way.

[RP]

*(post deleted...addon moved to separate thread)

[RP]

(EDIT, 6/24/11: Moved Fonts addon template to separate thread.)

[RP]

*(EDIT, 6/24/11: Moved CPL addon guide to its own thread.)

[RP]

*(post deleted...addons moved to separate thread)

[ChiefZeke]

SoLar updates at GeekSmack - registration has been terminated.

Have any idea for new/updated link?

[=[FEAR]=JIGSAW]

SoLar updates at GeekSmack - registration has been terminated.

Have any idea for new/updated link?

Up to 17th of April 2011 "SoLoR" Hotfix folder compressed:

x86

x64

[bphlpt]

And, of course, you can find his other goodies by going to the root - http://hotfix.chris123nt.com/ and looking around.

Cheers and Regards

[adric]

What is the advantage of going through the trouble of creating a switchless installer addon such as DirectX Runtimes and adding it to the wim with DXIntegrator when you can simply run

CMD /C start /wait %systemdrive%\Install\directx_Jun2010_redist.exe /Q

from the SetupComplete.cmd which Win7 will run after it finishes setup prior to finalizing the installation?

It is much easier to run the switchless installers from there than to package and integrate them in the image to be run later during install or am I missing something?

Al

[OnePiece Alb]

What is the advantage of going through the trouble of creating a switchless installer addon such as DirectX Runtimes and adding it to the wim with DXIntegrator when you can simply run

CMD /C start /wait %systemdrive%\Install\directx_Jun2010_redist.exe /Q

from the SetupComplete.cmd which Win7 will run after it finishes setup prior to finalizing the installation?

It is much easier to run the switchless installers from there than to package and integrate them in the image to be run later during install or am I missing something?

Al

SetupComplete.cmd not start with the Admin Rights, DXIntegrator always run everything with admin rights, with DXintegrator, not necessarily keep disable UAC to install svcpack AddOn

[ricktendo64]

What is the advantage of going through the trouble of creating a switchless installer addon such as DirectX Runtimes and adding it to the wim with DXIntegrator when you can simply run

CMD /C start /wait %systemdrive%\Install\directx_Jun2010_redist.exe /Q

from the SetupComplete.cmd which Win7 will run after it finishes setup prior to finalizing the installation?

It is much easier to run the switchless installers from there than to package and integrate them in the image to be run later during install or am I missing something?

Al

The problem is your switches, directx /q only extracts it it does not run the setup inside

Code: Select all

directx_Jun2010_redist.exe /t:"%temp%" /q
pushd "%temp%"
start /wait DXSETUP.exe /silent
popd

But dont use that during setupcomplete.cmd because %temp% may not yet be created, use a different temp extraction dir

BTW the best thing for programs is to preinstall them and capture the image

[adric]

Okay, I decided to try and see if I could integrate Yumeyao's DirectX Runtimes with DXIntegrator, but
I'm having problems getting it to work. I replaced the entries_dxrt32.ini with the code mentioned in RP's
first post, but when I select the DirectX package, DXintegrator throws a very quick message with the
following:

An error occurred trying to open DirectXRuntimes-201006-Addon-32.cab

The normal log doesn't list this error and there is barely enough time to read it. The original cab gave the
same error when I tried that. What am I doing wrong?

Edit: I found this in the other log:

• DPX Started DPX phase: Resume and Download Job
  2011-05-08 12:56:45, Info DPX Started DPX phase: Apply Deltas Provided In File
  2011-05-08 12:56:45, Info DPX Ended DPX phase: Apply Deltas Provided In File
  2011-05-08 12:56:45, Info DPX Started DPX phase: Apply Deltas Provided In File
  2011-05-08 12:56:45, Info DPX File could not be expanded, Source=update.mum, Target=(null), status=0x80070002
  2011-05-08 12:56:45, Info DPX ProvideRequestedDataByFile failed, Response file Name: \\?\Z:\$DXi\Addons\DirectX\DirectXRuntimes-201006-Addon-32.cab
  2011-05-08 12:56:45, Info DPX Ended DPX phase: Apply Deltas Provided In File
  2011-05-08 12:56:45, Info DPX DpxException hr=0x80070002 code=0x020102
  2011-05-08 12:56:45, Info DPX Ended DPX phase: Resume and Download Job
  2011-05-08 12:56:45, Info DPX DpxException hr=0x80070002 code=0x020217
  2011-05-08 12:56:45, Info CBS Failed to extract file update.mum from cabinet \\?\Z:\$DXi\Addons\DirectX\DirectXRuntimes-201006-Addon-32.cab [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
  2011-05-08 12:56:45, Info CBS Failed to extract package manifest from cabinet [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
  2011-05-08 12:56:45, Info CBS Failed to initialize internal package [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
  2011-05-08 12:56:45, Error CBS Failed to create internal package [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Al

[OnePiece Alb]

OnePiece DirectX Jun2010 x86 & x64 True AddOn INTL
Update (May 06 2011)
Update (May 06 2011)
Update (May 06 2011)
Update (May 06 2011)
Update (May 06 2011)
Update (May 06 2011)
Update (May 06 2011)
Hash MD5 2D4D034D7214573DAEC7BAA5344177CA
Filesize: 75.1 MB (78762321 bytes)

Ciao.

[adric]

Same error message with this addon too. I figured that I was doing something wrong and sure enough - user error.
I was trying to add the addon in the Packages listing section instead of the Optional Components listing section.
Duh ...

Your addon looks like a better solution than doing it with a switchless installer.
I looked at Onepiece's Windows 7 32/64 Addons, but did not see this one there.
Did you simply build it from scratch that quickly?

Al

[OnePiece Alb]

An error might have happened during encrypt the script during the build of the exe, will check now, thanks for reporting

Anyway if you find problems, put the state in "IGNORE-CHECK"

Ciao.

EDIT
already checked, I see no problems there (be sure to use the last version http://www.ryanvm.net/forum/viewtopic.php?t=8450)

[RP]

FYI, guys...I'm working on these True Addons, and will post in the separate addon threads I've made if knock-on-wood they work properly:

-- All Tasks/"God Mode" CPL, registered as a CPL (i.e. so you can switch views from inside Control Panel). There's a way to do this purely in the registry without having to manually create a "God Mode" folder somewhere.
-- VC++ v7 runtimes (from Yumeyao's Mixed Addon...for 2K5/2K8/2010 you'd use the same switchless installers copied over from Yumeyao's addon or N0ak's x64 addon).
-- Sysinternals Process Explorer + register it as replacement Task Manager (x86 or x64 versions).

No timetable on when these get posted, other than I'm hoping to start trickling them in as they're finished and tested.


*(EDIT, 6/23/2011: Completed addons deleted from above "to-do" list. See separate addon thread for the finished ones).

[solace]

4a. Pack the switchless addon folders into CAB files. Name each CAB the same title as your addon folder..."DirectXRuntimes_addon.cab", "DotNet4_addon.cab", etc. Make sure your CAB maker program is set to pack the SVCPACK subfolder into the CAB.

4b. Put the finished switchless addon CAB's into your Addons folder and delete your Temp folder (unless you want to keep the unpacked addon files).

just a quick addition to these great instructions, when making your .cab pack with CabPack, be sure to tick the checkbox that says recurse subdirectories before clicking on OK to making the cab, otherwise the cab files created are missing the entries.ini files you have custom made for the cab file. cheers

[adric]

Hi, does anyone know the command line syntax for dism to show the optional components listing?

I integrated OnePiece DirectX Jun2010 x86 & x64 True AddOn INTL and
I'm trying to figure out the dism command to list it. /Get-Packages or
/Get-Features doesn't list the DirectX component from what I can tell.

I see it listed in the DX Integrator GUI, so I assume there is a dism command to list the
component, but I'm having a senior moment right now.

Thanks, Al

[ChiefZeke]

Did you try DISM /? - that usually results in the options that can be used.

[adric]

Did you try DISM /? - that usually results in the options that can be used.

Yes, I did (the senior moment was not that bad ). I tried all the parms I thought made sense. Maybe Fabio knows what I need to specify.

Al

[nonno fabio]

Addon integration is performed by DXWNT6xTI, not by DISM, so there isn't a command to list them directly from DISM.

DISM can only list features with
/Get-Features
/Get-FeatureInfo
/Enable-Feature
/Disable-Feature
commands

[RP]

Updated the guide. See first post.

[RP]

Updates: Upgraded my test addons and moved them (along with other addon postings) to a separate thread...cleaned up the posts above where they were listed. Also updated the syntax for the Fonts installation template and CPL template and moved them to their own thread.

[solace]

just another note;

when making the cab addon you must specify what processor architecture to be used in the following line;

"processorarchitecture = XXX ;<-- optional. "x86" for x86-only platforms; "x64" for x64-only platforms; omit if platform-neutral."

It cannot be left blank.. otherwise DXInteg doesn't accept it. Cheers

[bphlpt]

The ENTIRE LINE is optional, but I believe if you include the label then you must supply a value.

Cheers and Regards

[solace]

Hi again,

Sorry but it seems following the instructions to create the self made SVCPACK installers this time around was quite frustrating.

Initially, I was having difficulty trying to get self made installers to pass the checks that DXIntegrator put in place and mucking around with the processor architecture setting made it work, however when deploying the Win7 install, it would get stuck at the "completing installation" phase. Removing my self made addons fixed the issue.

I used the previous version of the guide (notepad entries.ini values) to create SVCPACK installers that worked fine... I really dont know what I am doing wrong here.. Here is a sample of what I put in one of them

Code: Select all

[general]
title = Java Runtime Environment  ;<-- required
description = user_hidden's Java Runtime Environment 6.0 Update 26  ;<-- required
version = June 2011  ;<-- required
builddate = 06/08/2011  ;<-- required
company = Java  ;<-- optional
copyright = Java  ;<-- optional
website = http://www.ryanvm.net/forum/viewtopic.php?t=8420&highlight=java  ;<-- optional
customizedby = RP  ;<-- optional
lastupdatetime = 07/02/2011  ;<--optional
language = neutral  ;<--optional
releasetype = SVCPACK Addon  ;<-- mandatory (addon type)
processorarchitecture = x86  ;<-- optional. "x86" for x86-only platforms; "x64" for x64-only platforms; omit if platform-neutral.

[AddProgram]
java6u26.exe  ;<-- switchless EXE

I also used a NET4 installer from here
http://forums.mydigitallife.info/thread ... post454113

and vmanda's Flash AIO
http://www.ryanvm.net/forum/viewtopic.php?t=6785

All with similar entries.ini files, except for the java which carries the processor architecture set to x86

Any ideas? I do recall the previous entries.ini template had several other lines such as "installpackagename" and "Strings" etc Cheers...

[nonno fabio]

Your .exe file should exit when done. There's no timeout in DXWNTI to kill a paused process. You could try again using Java.exe from Kels or U_H (read about their switches before).

Anyway, for svcpack addons the most important section is [SetupAddOnToRun] ([AddProgram] is needed only to keep addon compatibility with Nlite/RVMi).

So valid section are:

Code: Select all

[SetupAddOnToRun] x32 e x64

if mounted image = x86, looking
SetupAddOnToRun.ntx86.6.1
SetupAddOnToRun.ntx86
SetupAddOnToRun.nt.6.1
SetupAddOnToRun.nt
SetupAddOnToRun.6.1
SetupAddOnToRun

if mounted image = x64, looking
SetupAddOnToRun.ntamd64.6.1
SetupAddOnToRun.ntamd64
SetupAddOnToRun.nt.6.1
SetupAddOnToRun.nt
SetupAddOnToRun.6.1
SetupAddOnToRun 

If you're searching for addons, in this forum you can find everything (legal) you want . About NetFX4 you can try this: http://www.ryanvm.net/forum/viewtopic.php?t=8317

[solace]

Thanks nono for the swift reply.

I think I have tracked down the problem to be NET4 installer from the MDL forum I used. It was the only switchless installer to fail halfway through installation in Windows. That must have been causing the problem. Cheers

[RP]

Thanks nono for the swift reply.

I think I have tracked down the problem to be NET4 installer from the MDL forum I used. It was the only switchless installer to fail halfway through installation in Windows. That must have been causing the problem. Cheers

Some switchlesses are more temperamental in Win7 than XP at SVCPACK stage because of the enhanced security and need for admin permissions. But that's totally an architectural thing with the OS, and it's only a stubborn very small minority of installers that get spiked by the tougher security. Runtimes and such tend to be a little harder than regular apps, but it's completely varied program-to-program. Requires a dry run test to make sure it works...can't rely completely on assumptions like you could with many XP switchlesses when making SVCPACK addons.

[nonno fabio]

Unlike others tools which run installers in Runonceex mode, DXWNT6.x True Integrator acts like in Windows XP at T14, hence "True" in its name, and everything is executed with admin permissions. So if the installer need to be run in Win7 with admin privilege, this shouldn't cause any problem when integrated with DXWNTI

[bina]

A couple of questions:

1- Does Solar's pack include Windows 7 post-SP1 updates only, or it contains ALL updates ever released for W7? The thing is I have W7 SP1 and don't want to update the already updated Windows distribution...

2- It's not specifically a question about Onepiece's integrator tool, RT7Lite, DISM, or any other official or unofficial tool with integration functionality BUT do these tools consider the order of installation of hotfixes/updates same as done by automatic update from MS website? In other terms, does the order of install matter anyhow?

[RP]

A couple of questions:

1- Does Solar's pack include Windows 7 post-SP1 updates only, or it contains ALL updates ever released for W7? The thing is I have W7 SP1 and don't want to update the already updated Windows distribution...

2- It's not specifically a question about Onepiece's integrator tool, RT7Lite, DISM, or any other official or unofficial tool with integration functionality BUT do these tools consider the order of installation of hotfixes/updates same as done by automatic update from MS website? In other terms, does the order of install matter anyhow?

1. SoLoR's pack is post-SP1 only. WAIK in Win7, which Onepiece and RT7 utilize, is safeguarded from patching obsolete or redundant hotfixes.

2. Order of integration of updates doesn't really matter in Win7 because MS's revamped sysadmin guts are a lot more robust at managing hotfix dependencies than the XP slipstreaming methods. Certain addons can still have some of the similar order-of-install quirks, but officially-sanctioned MS updates don't matter. SoLoR's pack also gets rigorous enough testing that he flags and separates out any problem hotfixes known to break things.

[RP]

Updated guide to reflect changes in SoLoR's download site navigation. See first post.

[bina]

3b. Navigate to the other extracted hotfix subfolders. Move all of these .MSU's in with the main hotfixes, then delete the empty subfolders.

Do you mean the following subfolders (except "Integrate to installation media")?:

IIS
LDR placeholders
MSMQ
NFS
Not integratable to Offline image
SNMP

4. Get SoLoR's additional update components. You'll want to use the alt download site with the raw files for easier navigation, since these optional KB's are not in the main pack and the main site's layout is not crystal clear at explaining that. Navigate on the alt site's directory tree to the /Windows.7/Additions/ folder. Download the following .MSU updates (x86 or x64 as needed) and save to the same place as all your other hotfix .MSU’s:

■ Internet Explorer 9 (mandatory).
NOTE: SoLoR no longer includes IE8 updates in the pack.

This particular folder includes both the installer for IE9 (Windows6.1-KB982861-x64.msu) and hotfix inside "Hotfixes" folder (IE9-Windows6.1-KB2559049-x64.msu). So, am I right in understanding that I need to move ALL (installer + hotfix) files inside "Windows 7/Additions/KB982861.Internet.Explorer.9.0" folder into "Temp/Extracted" folder?

Btw, the same applies to "Windows Identity Foundation" and "Windows Virtual PC".

[Knowone]

Thanks! Great work collecting links and info to what is needed for a good seven package.

[Registered55]

you said that

"NOTE 1: Not sure if these will work on an XP host, but if so also install WAIK"

WinNT6.x_True_Integrator will not load run on XP, so you may want to make it clear that vista/7even host is essential.

[bphlpt]

nono fabio and onepiece have both already said that WinNT6.x_True_Integrator will not run on XP, even though WAIK can be installed on XP. If anyone has figured out a way to have WinNT6.x_True_Integrator run correctly on XP I'm sure there are people who would be interested.

Cheers and Regards

[walibie]

Thanks! Great work

[RP]

Minor updates. See original post.

[kurmud]

the guide needs updating.

For example, solor's files are now gone, and the new packs available from that thread don't contain any subfolders. Also, it's not clear whether things like the additional components are included in that pack.

Plus, what happened to this forum?! Did everyone move somewhere else or something?

[ykchanaed]

As Solor 's site is down, can I just just put all the necessary raw .msu files and let NTIntegrator to do the job?

[spawn]

i always find these goodies when they die

[Siginet]

I have some hosting available if anyone wants to upload the files needed from this thread. Just PM me.

[RP]

Sorry...I don't check this one enough to notice just how out-of-date it's gotten.

I'll give it a go on updating the first post for McRip's update pack, which is now the best-of-the-best of the Win7 update packs. Plus update the other info.

[ricktendo64]

KUC is the best

[bphlpt]

And of course the goal is to end up with an install that McRip, KUC, and WU/MU all agree is clean and all say that nothing is needed, and the install logs all show that no errors occurred.

Cheers and Regards