TheTechGuide Forum

General Category => Software => Topic started by: qckslvr on January 31, 2002, 06:40:21 AM

Title: Security Rollup Package
Post by: qckslvr on January 31, 2002, 06:40:21 AM
the 1st w2k srp has just been released...



im wondering if itz possible to like.. slipstream it into the os just like the service packs?



tia!
Title: Security Rollup Package
Post by: Twinkie on January 31, 2002, 05:52:35 PM
I took a few moments to look at the update.exe in it.  Nothing shows up there.  Looks a lot like directx programming to me.  No good way to slipstream.  Anyone disagee?
Title: Security Rollup Package
Post by: Big_Z on January 31, 2002, 07:58:55 PM
Will be trying that soon...but I doubt its possible.
Title: Security Rollup Package
Post by: qckslvr on February 02, 2002, 06:19:21 AM
i hope someone figures out how to go about it...

will the patches in the SRP1 b also included in the upcoming win2k SP3?
Title: Security Rollup Package
Post by: crizp on February 04, 2002, 06:51:40 AM
no possibility of slipstreaming the SRP1 found...

change into the folder

[SRP1ROOT]i386update

( [SRP1ROOT] is the root folder where you have unpacked the SRP1, if you haven\'t you can\'t execute update.exe )

and execute \"update -l\" (this is a lowercase \"L\" not an \"I\")

it shows (on my system)

\"SP2SRP1 - SP3\"

so its either likely that this unofficial SP3 or it will be included in SP3

crizp
Title: Security Rollup Package
Post by: qckslvr on February 13, 2002, 12:46:47 AM
thnx crizp!

was wondering if itz possible coz i saw this artice http://www.winnetmag.com/articles/index.cfm?articleid=23994 (http://\"http://www.winnetmag.com/articles/index.cfm?articleid=23994\")

and m not sure of what he meant by \"If you’re creating new systems, you can put all 22 hotfixes in one slipstream directory and easily install the most recent and secure version of the OS from that directory. \"

tnx again! =)
Title: Security Rollup Package
Post by: Twinkie on February 07, 2002, 12:01:02 PM
A gentleman by the name of Peter sent me an email on this subject.  We have been trying to figure this out as well.  Here are the two emails that relate to this subject:

Make a SVCPACK folder under i386. Copy all hotfixes (and *.cat file you can extract) with a short name into that folder.

You have to use the latest sp3.cat in order for it to work.
Then make a file called svcpack.inf in the i386 folder. Here is the contents in my case:
 

[Version]
Signature=\"$Windows NT$\"
BuildNumber=2195
MajorVersion=5
MinorVersion=0

[SetupData]
CatalogSubDir=\"i386svcpack\"

[ProductCatalogsToInstall]
sp3.cat
exception.cat
dtcsetup.cat

[SetupHotfixesToRun]
Q252795.exe -q -m -z
Q276471.exe -q -m -z
Q282784.exe -q -m -z
Q285156.exe -q -m -z
Q285851.exe -q -m -z
Q296185.exe -q -m -z
Q298012.exe -q -m -z
Q299553.exe -q -m -z
Q299687.exe -q -m -z
Q299796.exe -q -m -z
Q300980.exe -q -m -z
Q301625.exe -q -m -z
Q302755.exe -q -m -z
Q303392.exe -q -m -z
Q308508.exe -q -m -z
Q310510.exe -q -m -z

Then you have to extract all Q*.exe files and substitute all files the they contain (except symbols, hotfix.exe, hotfix.inf,
spmsg.dll) with the same files in the i386 folder, usually *dll and *.exe files.
In the svcpack folder you have to use the sp3.cat with the latest version number.

Then you get a installation CD with all the latest pre SP3 files (it works for me anyway). I think I have all the files that you
can slipstream in the picture above (let me know if there is some file missing)

Please let me me know if this helped any.

A Later email Peter sent to me:

I will try to slipstream the w2kSP2SRP1.exe into the w2kSP2 package and let you know if I succeed. I think I forgot one cruicial information from my earlier mail. The slipstreaming starts with putting svcpack under [OptionalSrcDirs] in the dosnet.inf file, otherwise none of this works.
 
The benefit of slipstreaming also the pre-SP3 hotfixes into the installation is that you can install optional components later without installing the hotfixes again. Another thing is that you can use the -n switch and not create any uninstall directory for the hotfixes which makes your original installation smaller. The uninstall should not be needed in a clean install. Another benefit is of course the time it takes to install, no extra shutdowns.


I also sent an email to the author of the article mentioned above.  I will post any reply that I get.
Title: Security Rollup Package
Post by: fugazi on February 21, 2002, 03:46:35 PM
anymore details/info regarding this twinkie? very interested...not holding my breath though.

-thanks
[email protected]
Title: Security Rollup Package
Post by: Twinkie on February 27, 2002, 07:10:35 PM
No new news, sorry.  The author of the above mentioned article was not all that helpful.  I have yet to hear back from Peter either and have been unable to slipstream unless using his first mentioned process.
Title: Security Rollup Package
Post by: Fjellu on March 06, 2002, 06:32:20 PM
Hi guys

Just signed up. Peter is my name but nickname Fjellu.

I have the package slipstreamed into a booting CD. I have followed the multiOS thread for some time now but I just use the info to make a CD with all the goodies I need for a single install.

OK, so down to business:

1. Use a slipstreamed W2KSP2.
2. Open dosnet.inf and add svcpack to [OptionalSrcDirs]. it should loke like this:
[OptionalSrcDirs]
uniproc
svcpack
3. Create a folder named svcpack under the i386 folder.
4. Put w2kSP2SRP1.exe into the svcpack folder.
5. Change the name to SP2SRP1.exe (8.3 limitation)
6. Unpack w2kSP2SRP1.exe to a temp folder.
7. Copy the catalogs dtcsetup.cat and empty.cat to the svcpack folder.
8. Copy sp3.cat from the update folder of the unpacked w2kSP2SRP1.exe to the svcpack folder.
## The following could be done several ways ##
9. Copy everything from the temp folder where you unpacked w2kSP2SRP1.exe to the i386 folder (including subdirectories)
10. Delete dtcsetup.cat and empty.cat from the i386 folder.
11. Delete the update folder (now subfolder to i386).
12. Delete all duplicate files in the i386 folder, whenever there is a compressed one (this is a bit time consuming). Every *.dl_ and *.ex_ should be deleted. The beginning of the file is the same, for example MAILMSG.DL_ and mailmsg.dll. Always delete the older. (Just ignore if there is no duplicate. These files are supposedly for w2k serv and adv serv)
## Maybe someone invents an easier way ##
13. Create a file called svcpack.inf in the i386 folder with the following contents:
[Version]
Signature=\"$Windows NT$\"
BuildNumber=2195
MajorVersion=5
MinorVersion=0

[SetupData]
CatalogSubDir=\"i386svcpack\"

[ProductCatalogsToInstall]
SP3.CAT
EMPTY.CAT
DTCSETUP.CAT

[SetupHotfixesToRun]
SP2SRP1.EXE -Q -M -Z -N
Q314147.EXE -Q -M -Z -N

15. Yes, you guessed right, I have slipstreamed yet another patch to the package. The \"Unchecked Buffer in SNMP Service Could Enable Arbitrary Code to be Run\" update (don´t you just love Bill Gates)
16. Copy the file Q314147_W2K_SP3_X86_EN.exe to a temp directory.
17. Change the name to Q314147.EXE.
18. Copy the file to the svcpack folder.
19. Unpack Q314147.EXE in a temp folder.
20. Copy evntwin.exe and snmp.exe to the i386 folder and follow the procedure in 12.
21. Copy sp3.cat to the svcpack folder (yeah, you could have skipped 8).
22. Burn and install. Enjoy!

Whenever there is a new update follow the instructions 16-21 above. You don´t have to copy the files hotfix.exe, hotfix.inf, spmsg.dll or the symbols folder. Remember to update the svcpack.inf with the appropriate Q*.EXE. Remeber also that the svcpack folder should always contain the latest sp3.cat. Check the properties of the file and see which one has the latest modified date (the size also tells something).

This works for me. Let me know if you think there are any glitches.

I have tried to incorporate IE6, DirectX, WMPlayer (+patches and hotfixes for them) into a single package. But I cant get the hang of using Cmdlines.txt and [GuiRunOnce]. I asked Twinkie for some instructions in my mail but got none. I have followed all instructions in the multiOS thread and the OEM Usage and MS Extra´s pages at www.tech-hints.com but still need some more info about the details.
Title: Security Rollup Package
Post by: Fjellu on March 09, 2002, 10:28:18 AM
I forgot one instruction. Delete the file svcpack.in_ in the i386 folder.

There is another new critical update posted yesterday that can be streamlined into the i386 the same way mentioned above, Q313829.exe.
Title: Security Rollup Package
Post by: mlongwell on March 20, 2002, 04:36:56 PM
Thanks for the great information.  This worked great for me and will be a great timesaver.

But there is one \"gotcha\" to consider.

It seems like the hotfixe files are not truely \"slipstreamed\".  To test this I installed a server with the CD as outlined above.  I then removed IIS, rebooted, and re-added IIS, pointing it to the same CD I installed with, and then rebooted again.  I then ran qfecheck and it mentioned that the hotfix needed reapplied, pointing to 4 specific files, which were the SP2 version (not the SRP1 version).  It looks like the W2K setup routine is extracting these files from an older CAB file.

I\'m not sure if there is any way around this.  Any ideas?  I will check also.
Title: Security Rollup Package
Post by: Fjellu on March 21, 2002, 10:25:53 AM
Are you absolutely sure that you deleted the compressed sp2 files (*.ex_, *.dl_, etc) when you inserted the srp1 files? If yes, let me know which files you are referring to and I will try to find a solution.

You propably could inject the corresponding srp1 files into the sp2 *.cab files: fp40ext.cab, ims.cab, ins.cab, wms4.cab and xmldso.cab. Do you know any software to do that. I remember that there was a \"CAB File Wiever\" from MS with some OS or a Support Tools Pack but don´r remember which.
Title: Security Rollup Package
Post by: mlongwell on March 22, 2002, 08:41:50 AM
I\'ve think I\'ve found the problem.  The files that get rolled back are:

aqueue.dll
smtpsvc.dll
ntfsdrv.dll
mailmsg.dll

I checked this using qfecheck -v

They seem to be part of the IMS.CAB file.  However, they have different names in the cab file, they are preceded by smtp prefix (i.e. smtp_aqueue.dll).

It looks like when you reinstall certain components (like IIS), the setup program extracts these four files from the IMS.CAB.   I don\'t think that there is a more current version of this CAB file in SRP1 or any other hotfixes.  I will try to repackage the CAB file today and test.

(oh yes I did double check that the original source versions of these files were deleted from the i386 directory).

I also double checked that I had the latest SP3.cat file.  I got ahold of a command line utility catver.exe which will tell you the exact build version of the catalog file.  I can e-mail it to you if you\'re interested.

BTW - any luck on slipstreaming the IE security patch?  I\'m not having any luck (although I did get it to install using cmdlines.txt).

Thanks again for the help!
Title: Security Rollup Package
Post by: mlongwell on March 22, 2002, 08:47:56 AM
Oh, forgot to add:

There seems to be a cab maker utility included as part of XP.  

m:>makecab
Microsoft ® Cabinet Maker - Version 5.1.2600.0
Copyright © Microsoft Corporation. All rights reserved..

MAKECAB [/V[n]] [/D var=value ...] [/L dir] source [destination]
MAKECAB [/V[n]] [/D var=value ...] /F directive_file [...]

  source         File to compress.
  destination    File name to give compressed file.  If omitted, the
                 last character of the source file name is replaced
                 with an underscore (_) and used as the destination.
  /F directives  A file with MakeCAB directives (may be repeated).
  /D var=value   Defines variable with specified value.
  /L dir         Location to place destination (default is current directory).
  /V[n]          Verbosity level (1..3).

I think that the /F refers to a text file that lists the files to be included in the cab file.
Title: Security Rollup Package
Post by: Fjellu on March 22, 2002, 03:15:20 PM
I think you are right. When installing components through Control Panel -> Add/Remove Programs, W2K most likely only install from the i386 folder and is nor checking the svcpack.inf file or svcpack folder. That seems logical. So the \"slipstreaming\" only works on an empty partition.

I think you would get the same problem with the FrontPage extension files in fp40ext.cab.

Please do email me the catver.exe. Maybe it is more reliable than checking the sp3.cat files properties for version. You can however tell much from the size of the file. It is supposed to be incremental, newer ones including all information from the older ones.

The IE slipstreaming is a lot more trickier. I think you need to repackage the cab files inserting the new files. However I don´t think you need to worry about sliptreaming IE. It is unlikely that you would revert back to a previous version of IE. I use IEAK6 to make a package of the install. I include appupd.exe, euroconv.exe, mmssetup.exe and vbs56nen.exe into the package, installing after IE6, and q316059.exe installing after IE6 automatically restarts. When making the IEAK package totally hands-free you get all customizations + 5 other updates with one line in cmdlines.txt.

I also found an interesting little program within IEAK6 called iexpress.exe. With that program you can repackage for instance DX8.1, WMP7 + bonuspack + update into 4 separate selfextracting cab files. You can give the setup parameter \"/install /silent\" to DX8 and \"/Q:A /R:N\" to the 3 WMP *.exe files with iexpress.exe within the package. Using this metod you can save about 2/3 of the diskspace theese files normally occupy which gives you room for more apps on the CD.

This was the latest modification to the boot CD and it seems to work. I am installing (as we speak) the CD with VirtualPC booting from an iso file made with CDRWin and mounted with VirtualCDRom
Title: Security Rollup Package
Post by: Fjellu on March 22, 2002, 03:48:22 PM
I have to check out the makecab program, it could solve the remaining problems.

BTW my Boot CD now contains every piece of update available through \"Windows Update\". Including the first window update installer program you get installed when first visiting the \"Windows Update\" site and the Critical Update Notification and Root Certificates Update. These were made with the WinINSTALL LE included on the w2k CD (updated version from Veritas homepage) into *.msi packages.

The same way I made packages for Acrobat Reader, Winzip, WinAce, WinRar, CDRWin, Winimage, Getright, Quicktime, Schockwave 8.5, the file viewers for word, excel and powerpoint and a few others so far.

Putting all these into the GuiRunOnce section gives you all the programs installed totally hands-free. Just the CD and floppy (with winnnt.sif) in the PC (bootorder CD -> Floppy -> HD), wait for the \"press any key to boot from cd\", check that the winnt.sif is read without errors and you can come back 45 minutes later with all updates, patches and programs already installed.

If you want to save additional space (65MB) you can delete the i386lang folder, if you don´t need arabic, chinese, korean etc.

Heureka! It actually works. Running \"Windows Update\" first time after installing and \"No updates of this type are available at this time.\" under all sections.

Mission accomplished!
Title: Security Rollup Package
Post by: Zudrick on March 27, 2002, 07:37:08 PM
Try This Web Site: http://www.bink.nu/ (http://\"http://www.bink.nu/\")
Title: Security Rollup Package
Post by: cookie on April 25, 2002, 12:51:47 PM
hey folks... been following this discussion for a while, and there\'ve been a number of hotfixes since your original posts.  I\'ve followed the instructions laid out above, and they\'ve worked great.  I\'ve also found a few MS Kb articles that re-iterate what\'s already been said.

I\'d also recommend visiting the M$\'s OEM site, they\'ve got a few utilities and some extra documentation.  I was able to lift a copy of the DirectX distributable, which can silently install DX from cmdlines.txt.

I also wanted to let you know that I was able to re-package the cab files using a utility called \"cabarc\" that comes with the IEAK.  It\'s really ease to use:

cabarc.exe n cabname.cab *.*

-where \"n\" means create a new cab file.

I used WinRAR to extract the cabs (IMS.CAB, FP40EXT.CAB, and SP2.CAB) into their own folders.  I then replaced the original files with new versions, and then used cabarc to repackage them.  For the IMS.cab file, i had to add \"smtp_\" to some of the files.

Drop the new cabs into the i386 folder, burn, install, enjoy.

Now when i uninstall and reinstall IIS, hfnetchk shows that all the files are up to date.
Title: Security Rollup Package
Post by: Fjellu on April 25, 2002, 04:29:14 PM
Thank´s for the info about cabarc.exe. Have to try it.

About DX8. Don´t know if you mean the same file that is downloadable at

http://download.microsoft.com/download/win...S/DX81NTeng.exe (http://\"http://download.microsoft.com/download/win2000pro/Update/8.1/NT5/EN-US/DX81NTeng.exe\")

That file works fine in cmdlines.txt. Just extract the files and run the following from a batch file

dxsetup.exe /install /silent
Title: Security Rollup Package
Post by: Anonymous on April 27, 2002, 08:02:07 AM
where is MS\'s OEM site? is it password-protected?
Title: Security Rollup Package
Post by: Fjellu on June 07, 2002, 02:12:42 AM
oem.microsoft.com
You have to register
Title: Security Rollup Package
Post by: Harjit S. Batra on June 11, 2002, 08:42:42 PM
Quote:
------------------------------------------------------------------------------------------
12. Delete all duplicate files in the i386 folder, whenever there is a compressed one (this is a bit time consuming). Every *.dl_ and *.ex_ should be deleted. The beginning of the file is the same, for example MAILMSG.DL_ and mailmsg.dll. Always delete the older. (Just ignore if there is no duplicate. These files are supposedly for w2k serv and adv serv)
## Maybe someone invents an easier way ##
------------------------------------------------------------------------------------------
Well, assuming you are doing this on a W2K box, open a command prompt at the I386 folder and type this:

for %X in (*.dl_) do if exist %~nX.dll del %X

and then repeat for (ex_ exe) (in_ inf) (sy_ sys) (ce_ cer) (zi_ zip)!

If you are paranoid, you could move instead of deleting!

Also, if you are doing a bunch of hotfixes, after expanding each hotfix, search for and delete the files hotfix.exe, hotfix.inf, spmsg.dll and the symbols folders from all expanded folders. If you have already located the most recent sp3.cat and moved it and other .cat files to I386, then delete those too. NOW you are ready to move all files from the expanded folders to the I386 folder.
Title: Security Rollup Package
Post by: Fjellu on June 12, 2002, 01:52:26 AM
Thanks Harjit! If this really works it will save a lot of time.

Taking this method a bit further you could make a batchfile to automatically delete all duplicate files. I will have to try it out.
Title: Security Rollup Package
Post by: Harjit S. Batra on June 13, 2002, 10:00:49 AM
Anybody know where I can get a copy of the catver.exe file?

Also, any help/instructions on installing the following as part of the INSTALL will be appreciated:
a) Critical Updates Notification
/cool.gif\' class=\'bbc_emoticon\' alt=\'B)\' /> Installer

Thanks!
Title: Security Rollup Package
Post by: Fjellu on June 14, 2002, 05:07:35 AM
MS says the catver is only for internal use. Does this mean it is illegal to distribute it?

You can use Wininstall LE on w2k CD. Take before snapshot. Got to update, install Critical updates, take after snapshot and you have a *.msi package usable for install. the same with Root certificate etc.

If you mean Windows installer, just explode the package and use the approporiate file
Title: Security Rollup Package
Post by: Digitalfox on June 19, 2002, 09:52:06 PM
So does anyone have a full list of directions on how to slip stream the SRP or should i just wait for SP3   send me an e-mail at [email protected] if you have the direction it gets to confusing on here cause it always oh wiat i forgot this.
Title: Security Rollup Package
Post by: Anonymous on June 19, 2002, 10:52:07 PM
Hi,

Well ive been working on my own unattended install for more than a year now... funny only now do I find this forum.  All the info here is really awesome but I havent seen any mention of any WFP issues, which is what are still stumping me.

Particularly, with IE 6 (win2k download only package), when installing (with /Q:A /R:N) in Cmdlines.txt, I get 3 errors in my setuperr.log:

Error: Setup detected that the system file named [e:win2000system32dxmasf.dll] is not signed properly by Microsoft.  This file has been restored to the correct Microsoft version to maintain system stability.
***
Error: Setup detected that the system file named [e:win2000system32msdxm.ocx] is not signed properly by Microsoft.  This file has been restored to the correct Microsoft version to maintain system stability.
***
Error: Setup detected that the system file named [e:win2000system32strmdll.dll] is not signed properly by Microsoft.  This file has been restored to the correct Microsoft version to maintain system stability.
***

Yeah so basically this is windows media player (Except for strmdll).However, I dont get any WFP messages anywhere if I install it after Win2k wetup (e.g. GUiRunOnce), although the same files are present after both methods (Medie Player is still 6.4---1109). Not sure why Microsoft would send me something I didnt need but oh well... I just hate having error messages.

Now that was just asthetics really (cause media player has a later update) but I have a different problem with DX 8.1. Regardless of when I install it, I get 4 WFP messages in my event viewer upon the next boot.

Event Type:   Information
Event Source:   Windows File Protection
Event Category:   None
Event ID:   64002
Date:      6/19/2002
Time:      2:55:26 PM
User:      N/A
Computer:   C201753-A
Description:
File replacement was attempted on the protected system file ksinterf.ax. This file was restored to the original version to maintain system stability. The file version of the system file is 5.0.2134.1.
...
File replacement was attempted on the protected system file ksdata.ax. This file was restored to the original version to maintain system stability. The file version of the system file is 5.0.2134.1.
...
File replacement was attempted on the protected system file ksvpintf.ax. This file was restored to the original version to maintain system stability. The file version of the system file is 5.0.2134.1.
...
File replacement was attempted on the protected system file ksclockf.ax. This file was restored to the original version to maintain system stability. The file version of the system file is 5.0.2165.1.

In this case apparently, I am stuck with older AX files. I believe that they are involved with streaming media, and particularly with filtering and redirecting streams through different devices (e.g. audio streams from the net). I also get the same 4 WFP messages again when I install my sound card (Hercules GTXP).

Has anyone encountered anything of this sort? Any thoughts would be greatly appreciated.

Thanks,
Sean
Title: Security Rollup Package
Post by: Fjellu on June 24, 2002, 07:44:24 AM
Use IEAK6, make a fully unattended install package. Then you only need to run ie6setup in cmdlines.txt or in a batchfile if you prefer. I use that method, it is easier to troubleshoot. Here is my ie6.bat:
@echo off
echo Installing Internet Explorer 6 and some patches
echo.
echo Installing...
echo.
echo Please wait
C:WINAPPSIE6IE6SETUP.EXE
;endfile

When you use IEAK6 you can even integrate som updates and hotfixes directly into that package. I have the following files integrated: appupd.exe, auroconv.exe, jet35sp3.exe, mmsetup.exe, VBRun60sp5.exe, vbs56nen.exe and the hotfix q319182.

After upgrading IE, you could also add WMP7 to your cmdlines.txt.

No ideas about your DX problem, sorry
Title: Security Rollup Package
Post by: Fjellu on June 28, 2002, 06:37:40 AM
My DOS knowledge is not what it should be. With the syntax

for %X in (*.dl_) do if exist %~nX.dll del %X

I cannot get it to work. Is the syntax correct?

I am trying to make a general batchfile for deleting all duplicates after copying every hotfix in chronological order
Title: Security Rollup Package
Post by: c400a on July 02, 2002, 11:13:07 AM
Hi, All

Thanks for the info, I`ve successfuly built a fully patched Win2k install. here`s my contribution to the forum.

You can build a batch file from the temp dir where you extracted the files

run the following command in the i386 folder of the extracted SRP1 files, at the CMD Prompt.

dir /s /b>cleanup.txt

This is what it does:
dir /s (will recurse all sub-dirs) /b (bare format no headers)>output file for listing.txt

your cleanup.txt will be a file list of that dir, using notepad or i prefer metapad replace the last character of the file extensions.

so find .dll replace with .dl_ and so on. Use replace again to add del to the start of each line along with the correct path to your build dir.

Re-save the file as cleanup.bat or whatever and then you can launch it in your patched i386 dir to remove the files, just create lists in each of the Qxxx directories for the post srp1 hotfixes and paste the required entries, in the file to remove the compressed files. I`ll post my listing for the SRP1 dir, as a TXT You`ll need to change the path to the files and rename it to a .bat file.

Any questions PM me or post I`ll try to keep a check.

Anyone fancy collating all this data into a webpage or two I`m willing to write a few pages. As i`ve got all this working, plus i`m loading IE6 using IEAK with all patched DX8.1, Arcrobat 5 reader and a zip tool all silently during installation via unattended scripting and modifiying the install via KIX scripting.

Anyone considered applying these steps to update XP.

All the Best

Ian (C400a)

A bit of DOS is good for the soul
Title: Security Rollup Package
Post by: jiimmy on July 08, 2002, 05:14:42 AM
I posted above about the WFP errors and just registered.

Well, I finally wrote a batch file to do this stuff. I guess I will attach it to this post (if it works) or just post it below in its own post. I didnt know jack about batch files before this so its not perfect, but it works for me.

To see the argument syntax use the /? switch.

Anyways I fixed my prob by using IEAK to make a package that didnt have windows media player.

Also, there is something else someone may find interesting. I used Wininstall LE to repackage the Windows Critical Update Notification and root certificates but the LE is kinda clumsy and very indescriminant so I went about another way. By searching around in files I was able to find the following:

rootsupd.exe ( the roots certificate install ) at:

http://www.download.windowsupdate.com/msdo...D5E13152EBE.exe (http://\"http://www.download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/rootsupd_4BCC89780E381ABF122B2798D411DD5E13152EBE.exe\")

iuctl.cab ( the Windows Update install ) at:

http://v4.windowsupdate.microsoft.com/CAB/...7433.6368287037 (http://\"http://v4.windowsupdate.microsoft.com/CAB/x86/unicode/iuctl.CAB?37433.6368287037\")

The cab file I repackaged with iexpress.exe in IEAK (and if you havent tried it, iexpress is the best thing since sliced cheese)

Now im gonna try to slip in Dx8.1.
Title: Security Rollup Package
Post by: jiimmy on July 08, 2002, 06:25:29 PM
So I guess attaching the file did not work (what a surprise). Here is the file\'s contents. Just paste the lines below the dashed line into a text file and name it slipsteam.bat (or whatever you like).

*watch out for lines that are wrapped because of your browser screen width. Batch file processing is not very forgiving as ive found out.

slipstream.bat -- file begins below next line
--------------------------------------------------------------------------------
@ECHO OFF

REM This batch file will call itself with
REM delayed environment variable expansion enabled
REM which is required for the FOR loop to work.

SETLOCAL

IF \"%1\" == \"\" (GOTO :Syntax)
IF \"%1\" == \"-?\" (GOTO :Syntax)
IF \"%1\" == \"/?\" (GOTO :Syntax)
GOTO :ReqCheck

:Syntax

ECHO;
ECHO Replaces all compressed versions of newer files in the build directory.
ECHO;
ECHO Usage: slipstream.bat [/b path] [/m path] [/x [/q]] [/nolog] [/test]
ECHO;
ECHO Parameters:
ECHO    /b \"dir\"    - Specifies \"dir\" as the build (i386) directory (defaults to current).
ECHO    /m \"dir\"    - Specifies \"dir\" as the directory to put replaced files (defaults to build).
ECHO    /x          - Deletes replaced files (overrides /m).
ECHO    /q          - No delete prompts.
ECHO    /nolog      - Supresses file replacement messages.
ECHO    /test       - Emulation mode. Prints messages instead of replacing files.
ECHO;
ECHO Example: slipstream.bat /b D:CDi386 /m .i386_replaced /nolog /test
GOTO :Finish

:ReqCheck

SET envTest=failed
FOR /L %%X IN (1,1,1) DO (
    SET envTest=passed
    IF NOT !envTest! == passed (
        ECHO --------------------------------------------------
        ECHO Enabling delayed environment variable expansion...
        ECHO --------------------------------------------------
        CMD /V:ON /S /K %~f0 %*
        GOTO :Finish
    )
)

REM Parse parameters

SET buildDir=
SET quiet=no
SET moveDir=
SET delete=no
SET nolog=no
SET emulate=no

IF \"%1\" == \"/b\" (
    SET buildDir=%~f2
    IF \"!buildDir:~-1,1!\" == \"\" (SET buildDir=!buildDir:~0,-1!)
    SHIFT 1
    SHIFT 1
) ELSE (
    FOR /F \"usebackq\" %%D IN (`CD`) DO (SET buildDir=%%D)
)
IF \"%1\" == \"/m\" (
    SET moveDir=%~f2
    IF \"!moveDir:~-1,1!\" == \"\" (SET moveDir=!moveDir:~0,-1!)
    SHIFT 1
    SHIFT 1
) ELSE (
    SET moveDir=%buildDir%
)
IF \"%1\" == \"/x\" (
    SET delete=yes
    SHIFT 1
)
IF \"%1\" == \"/q\" (
    SET quiet=yes
    SHIFT 1
)
IF \"%1\" == \"/nolog\" (
   SET nolog=yes
   SHIFT 1
)
IF \"%1\" == \"/test\" (
   SET emulate=yes
   SHIFT 1
)

REM Check directories.

IF NOT EXIST \"%buildDir%\" (
    ECHO Invalid build directory \"%buildDir%\"
    GOTO :Syntax
)
IF NOT EXIST \"%moveDir%\" (
    MKDIR \"%moveDir%\"
    IF NOT EXIST \"%moveDir%\" (
        ECHO Invalid move directory \"%moveDir%\"
        GOTO :Syntax
    )
)

:Start

ECHO;
ECHO Build directory is: \"%buildDir%\"
IF %delete% == no (
    ECHO Replaced files will be moved to: \"%moveDir%\"
) ELSE (
   ECHO Replaced files will be deleted.
)
IF %quiet% == yes (ECHO Quiet mode enabled.)
IF %nolog% == yes (ECHO Logging mode disabled.)
IF %emulate% == yes (ECHO Emulation mode enabled.)
ECHO;
PAUSE

REM Find, then move or delete replaced files. This checks all
REM files in the build dir (and sub-dirs) that dont end with
REM an underscore. If a file is found that has the same name
REM except with an underscore as its last char, then it is
REM moved or deleted.

SET file=
SET fileEnd=
SET fileCount=0
SET delSwitch=/P /F
IF %quiet% == yes (SET delSwitch=/F /Q)

FOR /R \"%buildDir%\" %%X IN (*.*) DO (
    SET file=%%~fX
    SET fileEnd=!file:~-1,1!
    IF NOT \"!fileEnd!\" == \"_\" (
        SET file=!file:~0,-1!_
        IF EXIST \"!file!\" (
         IF %delete% == yes (
            IF %nolog% == no (ECHO deleting \"!file!\")
            IF %emulate% == no (DEL !delSwitch! \"!file!\")
         ) ELSE (
            IF %nolog% == no (ECHO moving \"!file!\" to \"!file:%buildDir%=%moveDir%!\")
            IF %emulate% == no (MOVE \"!file!\" \"!file:%buildDir%=%moveDir%!\")
         )
           SET /A fileCount+=1
        )
    )
)
ECHO;
ECHO %fileCount% files were found.

:Finish

ENDLOCAL
Title: Security Rollup Package
Post by: Fjellu on July 09, 2002, 03:51:25 AM
Thanks for the batchfile, pretty impressive work. I have to try it out. I also got hang of how to delete the duplicate compressed files. Put the following in a batch file and run it (if your project is in d:w2ki386)

CD /D D:w2ki386
FOR %%X IN (*.dl_) DO IF EXIST %%~nX.dll DEL %%X
FOR %%X IN (*.ex_) DO IF EXIST %%~nX.exe DEL %%X
FOR %%X IN (*.in_) DO IF EXIST %%~nX.inf DEL %%X
FOR %%X IN (*.sy_) DO IF EXIST %%~nX.sys DEL %%X
FOR %%X IN (*.ce_) DO IF EXIST %%~nX.cer DEL %%X
FOR %%X IN (*.ca_) DO IF EXIST %%~nX.cat DEL %%X
FOR %%X IN (*.zi_) DO IF EXIST %%~nX.zip DEL %%X
FOR %%X IN (*.cp_) DO IF EXIST %%~nX.cpl DEL %%X
CD uniproc
FOR %%X IN (*.dl_) DO IF EXIST %%~nX.dll DEL %%X
FOR %%X IN (*.sy_) DO IF EXIST %%~nX.sys DEL %%X
;endfile

Iexpress is a superb tool for repackaging applications. I have used with Directx, Media Player + hotfix + bonuspack, MDAC27 and a few others, which I have included in my \"Clean Install Boot CD\".

The links to the updates are much appreciated. I could not find  them
Title: Security Rollup Package
Post by: Bryan Berns on August 08, 2002, 08:28:15 PM
Hey everyone.  I thought I might post this, might help out some people with related material.

http://berns.cae.wisc.edu/wincdman/ (http://\"http://berns.cae.wisc.edu/wincdman/\")
Title: Security Rollup Package
Post by: CRasH180 on September 03, 2002, 05:49:48 PM
Is it just me or is anyone else having a problem getting to that web site --->
http://berns.cae.wisc.edu/wincdman/ (http://\"http://berns.cae.wisc.edu/wincdman/\")

??
Title: Security Rollup Package
Post by: CRasH180 on September 03, 2002, 05:57:31 PM
The actual link for that site is:

http://berns.cae.wisc.edu/pages/wincdman.asp (http://\"http://berns.cae.wisc.edu/pages/wincdman.asp\")

Just thought you all might want to know....
Title: Security Rollup Package
Post by: Lync on September 26, 2002, 10:29:58 AM
Does anyone know if it is possible to integrate a novell client install into a slipstream of Win 2000?
Title: Security Rollup Package
Post by: Fjellu on September 27, 2002, 12:34:42 PM
I don\'t think it is possible with w2k and the newer clinets. There were some documents earlier for w9x and earlier clients according to which it was possible.

You can however automate the installation of the NW client using acu.exe. Create you own configuration file and modify acu.ini. Install with setupnw /acu.
Title: Security Rollup Package
Post by: Anonymous on October 03, 2002, 04:04:42 AM
It\'s possible to make Novell Client automatic using CMDLINES.TXT.  You could create your unattended script bu using NCIMAN.exe in the admin sub-folder of the extracted Novell Client directory.  Here you can specify that the installation should not reboot.
Title: Security Rollup Package
Post by: eagle00789 on October 16, 2002, 05:35:34 PM
does this work with windows xp to??
Title: Security Rollup Package
Post by: GuessHooo on November 24, 2002, 10:16:11 PM
This is a replication of the following url :
http://www.bink.nu/Bootcd/sliphf.htm (http://\"http://www.bink.nu/Bootcd/sliphf.htm\")

Installing Windows 2000 with Hotfixes
This scenario explains how to create a combination installation of Windows 2000 integrated with SP3 and post-SP3 hotfixes in a shared distribution folder on a network. You do not need to perform separate installations of either Windows 2000 or the Windows 2000 hotfixes.

Important

An attempt to slipstream an SP3 hotfix into an integrated SP3 shared distribution folder might cause Windows 2000 to stop working (because of the SP3.cat file getting overwritten and SP3 files becoming untrusted). For more information on this issue, see article Q290074, \"Slipstreaming Earlier Fixes Into an Integrated Installation Share Breaks the Share,\" in the Microsoft Knowledge Base.

Important

·                     This process installs the Windows 2000 hotfixes during Windows 2000 Setup.

·                     Because Windows 2000 Setup requires the 8.3 naming convention for all files and folders in the distribution folder, you must change the hotfix file names (from Q######_XXX_YYY_ZZZ_LL to Q######).

Preparing for the Installation
Before you run Windows 2000 Setup to deploy the installation of Windows 2000 and the Windows 2000 hotfixes across a network, you must copy the Windows 2000 and Windows 2000 hotfix installation files to a shared distribution folder and complete the following tasks.

If you are an OEM and plan to install any additional OEM files (for example, device driver, application, or component files) on the destination computers, create a $1 subfolder within the $OEM$ subfolder. The $1 subfolder maps to systemdrive, the destination drive for the Windows 2000 installation.

Note

In the following procedure, \"E:\" represents the drive name of the network or computer where your distribution folder is located.

To install Windows 2000 integrated with SP3 and Windows 2000 hotfixes

1.     Connect to the network or computer on which you want to create the distribution folder.

2.     Create an i386 distribution folder by typing the following (using the appropriate drive name):

mkdir E:i386

3.     Use the command-line utility xcopy to copy the files and subfolders from the Windows 2000 integrated SP3 installation CD to the E:i386 folder. For example, if D: is your CD-ROM drive, type the following:

xcopy /e /i /v d:i386 e:i386

4.     Edit E:i386dosnet.inf to add svcpack to the [OptionalSrcDirs] section as follows:

[OptionalSrcDirs]
uniproc
svcpack

5.     Create an E:i386svcpack folder. For example, to create a svcpack subfolder within the i386 folder, type the following:

mkdir E:i386svcpack

6.     Copy the hotfix executable program (Q######_XXX_YYY_ZZZ_LL.exe) to the E:i386svcpack folder by using the 8.3 naming format (Q######.exe), where ###### represents the actual hotfix number.

If you are deploying multiple hotfixes, rename all of the hotfix package files.

7.     Expand the hotfix to a unique temporary location. For example, to expand the files to the sample folder, type the following:

E:i386svcpackQ###### /sE:samplefolder

8.     Copy the catalog files (.cat) and hotfix binary files (such as .exe, .dll, .sys) as follows:

a.    Copy Q######.cat to E:i386svcpack folder. If multiple hotfixes are to be deployed together, make sure that you copy all catalog files from each of the hotfixes to be deployed. Each hotfix has a unique catalog file that you must copy in the format Q######.cat.

b.    If any binary files exist in multiple packages, keep only the file with the highest version number.

c.    Delete any binary files to be replaced in the i386 folder (usually you can identify the file name by an underscore at the end in the shared folder).

d.    Copy the hotfix binary files and any subfolders for the hotfix to the i386 folder.

For example, i386uniproc* files in the hotfix need to be copied to the i386uniproc folder of the shared installation folder. There is no need to copy Update.exe, update.inf, spmsg.dll, spcustom.dll, spuninst.exe, update.ver, or symbols files.

9.    Note

10. Step 8 can be cumbersome if you are installing multiple hotfixes. This step is necessary only if the hotfixes contain updated system files that are required to start the computer to GUI mode or to prevent a virus attack during upgrade.

11. Delete the E:i386svcpack.in_ file.

12. Create a new svcpack.inf file at E:i386svcpack.inf, with the following content:

[Version]
Signature=\"$Windows NT$\"

MajorVersion=5

MinorVersion=0

BuildNumber=2195

[SetupData]
CatalogSubDir=\"i386svcpack\"

[ProductCatalogsToInstall]
Q######.cat

[SetupHotfixesToRun]
Q######.exe /switches (the recommended switches for hotfixes are /q /n /z)

Important

If you will be deploying multiple hotfixes together, add an entry for each hotfix under [SetupHotfixesToRun] (as shown following this paragraph), and then add the Qchain.exe file to make sure that the correct files get replaced after the installation. You must also copy Qchain.exe to the svcpack folder. The following lines are a sample of the [SetupHotfixesToRun] section for an installation in which multiple hotfixes are installed.

[ProductCatalogsToInstall]
Q123456.cat

Q123478.cat

Q123490.cat

[SetupHotfixesToRun]
Q123456.exe /switches (the recommended switches for hotfixes are /q /n /z)

Q123478.exe /switches (the recommended switches for hotfixes are /q /n /z)

Q123490.exe /switches (the recommended switches for hotfixes are /q /n /z)

13. If you will be installing multiple hotfixes, copy Qchain.exe to the E:i386svcpack folder.

You can find Qchain.exe on the Microsoft Web site.
Title: Security Rollup Package
Post by: Anonymous on November 25, 2002, 03:56:51 PM
Does it include any of that Digital Restrictions Management crap?  If so, no thanks.
Title: Security Rollup Package
Post by: Beeper on December 28, 2002, 08:18:52 AM
I tried to follow the instructions on the web-page, and have all hotfixes located in i386svcpack together with the lastest sp3.cat file (and slipstreamed SP3 into the Win2K pro directory).  But when trying to install Win2K Pro I get an error:

The following value in the .SIF file used by Setup is
corrupted or missing:

Value 0 on the line in section [SourceDisksFiles]
with key \"sp3.cab.\"

Setup cannot continue. To quit Setup, press F3.

Any idea what causes this ??

The line in txtsetup.sif  looks like this:

sp3.cab      = 2,,,,,,_x,39,0,0

Regards,

/B
Title: Security Rollup Package
Post by: Same Here... on January 05, 2003, 07:33:13 PM
I had the same problem.

I was using Datacenter server, wanted to update to SP3, and got \"This service pack has not been qualified by your hardware vendor for installation on this copy of Windows 2000 Datacenter Server.\"

So I thought this may just be a driver I have loaded [or *some* kind of conflict] and thought, well, I can *extract* these files...

And I can simply dump the i386 directory from Service Pack 3 into the folder structure of my Windows 2000 Datacenter Server.

So i did this, and made a bootable iso with all files said and done.

I went to install using the cd, and i got that same error message you did.

When I did some more reading, it turns out that the correct action isn\'t to dump the i386 contents from the service pack into the original i386 tree...

But to run update -s:<dir>, where <dir> is the root directory of your original install.

This makes sense, when you think about it.  First, we must realize that any of these win2k service packs have to work for every version from professional to advanced server.  With Datacenter, it took me a *lot* of searching, but I *eventually* tripped across the page below...

http://bink.nu/Bootcd/ (http://\"http://bink.nu/Bootcd/\")

Which had the exact same problem I had... except with a fix for update to allow Datacenter to work too.

Anyway, it\'s my thought that if, rather than copying the files into the source directory of your original win2k you should run update with the -s switch.

If I\'m not mistaken you seen the suggestion to copy the files in an earlier post.  I think the author *probably* meant [though i shouldn\'t speak for anybody] to run update -s:<dir> which would then copy the files over for you.

I hope I am understanding your problem correctly, and I further hope this is the solution /smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />

Good Luck!
Title: Security Rollup Package
Post by: Anonymous on January 23, 2003, 06:03:19 PM
This looks to be a known issue  PIC  (http://\"http://www.bink.nu/bootcd/NOSP2ONDATACENTERSERVER.jpg\")
Title: Security Rollup Package
Post by: wm on May 04, 2003, 12:24:09 PM
is it possible to add media player 9 and/or IE6 to a SlipStream of windows 2000 so it installs itself with windows 2000??
and if so does anyone know how?

Thanks /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Title: Security Rollup Package
Post by: Guest on August 22, 2003, 08:32:44 AM
This is all Good, but no one aver answered the Question, Does this work the same way in XP. I can Already Tell you it doesn't, as the Dosnet.inf is not setup the same way as it is lacking an [optionalsrcdir] section and a few other minor things seem to be missing as well.
Title: Security Rollup Package
Post by: Guest on August 22, 2003, 09:21:44 AM
[quote name=\'CRasH180\' date=\'Sep 3 2002, 04:57 PM\']The actual link for that site is:

<a href="http://berns.cae.wisc.edu/pages/wincdman.asp">http://berns.cae.wisc.edu/pages/wincdman.asp</a>

Just thought you all might want to know....[/quote]
 I Get Page cannot be Displayed Trying to go to Anything under this Site. I can only find his pages in the little Cached link next to the real link, but I can't download the file from. Anybody know what happened to this guy? He is still on the Staff list at University of Wisconsin as of Aug 20.....
Title: Security Rollup Package
Post by: uru on September 04, 2003, 08:17:06 AM
ok I know this thread is old but I still use win 2000 and periodicaly have to reload a machine or two, I would like to know if and how I can incorperate "Windows2000-KB823980-x86-ENU.exe" (patch that came out with the msblaster virus) into my install cd or folder. I don't care if it's slipstreamed or as a hotfix but I was under the impression that hotfixes have to be "Q" files (starting with the letter Q)?
Thanks
Title: Security Rollup Package
Post by: Eric on September 15, 2003, 02:44:33 AM
For anyone that makes it this far: As of Sep 11, 2003, MS03-026/KB823980 has been replaced with MS03-039/KB824146.  Don't miss this one as it is remotely exploitable like the MS03-026 that triggered blaster and it's ilk.
Title: Security Rollup Package
Post by: lost_soul on December 20, 2004, 10:00:23 PM
[quote name=\'wm\' date=\'May 4 2003, 11:24 AM\']is it possible to add media player 9 and/or IE6 to a SlipStream of windows 2000 so it installs itself with windows 2000??
and if so does anyone know how?

Thanks /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />[/quote]
 both IE6 and MP9 can be added to a windows installation by using a CMDLINES.TXT file which you would create in the $OEM$ folder
Title: Security Rollup Package
Post by: ProClub on April 29, 2005, 06:17:03 AM
Hey, guys, check this site out: http://unattended.msfn.org/ (http://\"http://unattended.msfn.org/\") Definitely worth checking...

ProClub
proclub [at] karinthy [dot] hu
Title: Security Rollup Package
Post by: ProClub on April 29, 2005, 06:18:56 AM
You might also be interrested in the tool nLite. (http://nuhi.msfn.org/ (http://\"http://nuhi.msfn.org/\")) It saves a lot of time (and headaches) when creating unattended install CDs. /smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />

Have fun!

ProClub
proclub [at] karinthy [dot] hu