Directories Created by WUD ?

[bigcheez]

Can someone please explaiin the purpose of each subdirectory created by WUD.

How can the files be used for slipstreaming?

Which files are not for slipstreaming and what is their purpose?

[submix8c]

AFAICR (been a while), it breaks them down the same way WU/MU would (Critical, etc.), hence the FolderNames (?may be wrong). I believe it uses the XML from MS to determine where in MS' File Repository to download the Files directly into the associated folders.

The method of slipstreaming is at your discretion. The list of fixes necessary for your "flavor" of OS is posted multiple places/threads, also sometimes broken down into categories. Sometimes it's a matter of experimentation.

WUD is primarily a method of getting everything "it" knows about in a convenient way. It uses the MS-method that MS' MBSA (search MS for that) uses except it doesn't scan your computer for "what you need", it just downloads all "latest" fixes. Cross-reference any given list against what WUD (all of files) downloads and proceed accordingly.

HTH

[MrJinje]

Yes, that is correct when an Update List follows the XML Schema (see Sticky).

Here is a "traditional" style category list with one OS per list (author steven4554), it has multiple folders for the different "kinds" of updates.

<categories>2

<category id="1">Critical Updates</category>

<category id="2">Important Updates</category>

<category id="3">.NET Framework Updates</category>

<category id="4">Optional Updates</category>

</categories>

But I never really cared what kind of update they were, because I need them all in the same folder when I DISM /ADD-PACKAGE. If you are making your own list, you might want to consider something more like this.

<categories>

<category id="1">Windows 7 Updates - x86</category>

<category id="2">Windows 7 Updates - x64</category>

<category id="3">Other Updates + ISO Images</category>

<category id="4">W2K8-R2 Updates - x64</category>

</categories>

Files can be slipstreamed offline using DISM from the command line.

Files that cannot be slipstreamed in most cases can be integrated in other ways (usually silent switches at setupcomplete.cmd stage). I was thinking to separate those updates into the "other updates" folder. You can tell which files are not for slipstreaming because they are not in (.msu or .cab) format. Any other format cannot be slipstreamed. this means all EXE based updates (like Malicious Software Tool) cannot be integrated but instead need to be installed at some point.

Edited March 9, 2010 by MrJinje

[bigcheez]

Please excuse my ignorance.

I am looking to slipstream 2k.

Can I assume that DISM is not available to do this?

I had planned to use HFSLIP slipstream 2k for starters.

Then I was gonna use nlite for addons and such.

Can you please explain what files I could use to do this?

Here is my take on things so far?

\win\enu & \win\glb & \w2k\enu & \w2k\glb - all files here can be slipstreamed directly

\win\enu\ie6setup - probably needs to be installed after OS (should some hotfixes not be installed until after this?)

\opt & \exclude & \static - I assume these are all just text files used by WUD

\bin - are these updates that can be directly copied?

[bigcheez]

Please excuse my ignorance.

I am looking to slipstream 2k.

Can I assume that DISM is not available to do this?

I had planned to use HFSLIP slipstream 2k for starters.

Then I was gonna use nlite for addons and such.

Can you please explain what files I could use to do this?

Here is my take on things so far?

\win\enu & \win\glb & \w2k\enu & \w2k\glb - all files here can be slipstreamed directly

\win\enu\ie6setup - probably needs to be installed after OS (should some hotfixes not be installed until after this?)

\opt & \exclude & \static - I assume these are all just text files used by WUD

\bin - are these updates that can be directly copied?

? ? ? ? ? ? ?

Is this a stumper for y'all?

Am I going down the wrong path?

? ? ? ? ? ? ?

[MrJinje]

No clue, if you have questions about unattended 2000, HFSLIP, or nlite you might want to stop by those sub-forums.

Wouldn't hurt to take a look at this thread and go through each update one by one to determine if you want to include them. But that sounds like a waste of time time to me. If I was you, I would simply download them all, try to integrate them with nLite and see if I get any errors. What's the worst that could happen, you have to start over again, nlite should know what to do with each file. (or at least warn you it is not supported)

Where'd you download your update list from, is this from jcarles website or somebody elses list ?

Here's another good link

Edited March 17, 2010 by MrJinje

[bigcheez]

Where'd you download your update list from, is this from jcarles website or somebody elses list ?

Here's another good link

The list I was using is directly form the WUD website.

The link you provided does seem like it would be easier to work with.

But to work with that list I would have to open each page linked to and download form there.

The WUD program allows for a batch download of all files.

Is there a better/easier way to download using TommyP's list on the vrock site?

[submix8c]

1 - Use VORCK as the "list" (maybe another, e.g. MSFN, for comparison?)

2 - Collect the files from the WUD download (or manually via any given "list")

3 - Compare WUD to VORK (or "other") for discrepancies (if any)

4 - Try it (the slipstream + test install)

5 - Go to MS for scan (note - may be necessary to install ALL from ADD/Remove)

There have been, in the past as in the present, conflicting reports of the "complete" list and where to obtain "it", so I suggest you just try it yourself.