TheTechGuide Forum
General Category => Software => Topic started by: stimpy on June 02, 2002, 05:07:07 AM
-
Been looking into this whole BOOTCD WIN2k integrated SP2 thing and have a few questions.
Okay I understand how to slipstream SP2 into W2k.
support.microsoft.com/default.aspx?scid=kb;en-us;Q290074
But which way is best for SP3 Hotfixes, i.e
1. unattended with %OEM%CMDLINES.txt
www.cheese.org/~scott/useful/Slipstreaming%20Builds.doc
or
2. by unattended and by svcpack.inf with i386svcpack
support.microsoft.com/default.aspx?scid=kb;EN-US;q296723
Dont forget Qchain utility for multi hotfixes
support.microsoft.com/default.aspx?scid=kb;en-us;Q296861&ID=kb;en-us;Q296861&GSSNB=1
The second way is reccomended by M$, but its bloody cumbersome to do properly, i.e uncompress all hotfixes and delete ALL duplicate compressed files from i386 directory.. anyone got a tool to do this?? Also have to use the LATEST sp3.cat in svpack dir
What about for DX8.1??
dxsetup.exe /install /silent which should this be done in??
Any suggestion would be good.
regards
-
have you had a look at http://www.tech-hints.com/ (http://\"http://www.tech-hints.com/\") , this site may help you.
Let us know if you find any other methods of applying the hotfixes
-
Better wait for SP3 final to come out...(really, I mean it)
On the other hand, i\'ll say unattended using [GuiRunOnce] in winnt.sif or cmdlines.txt if you want, because the other method is too complicated. It\'s not a problem to delete all the duplicates files in i386 (if you want my self-made program to do it contact me at email below) but the real problem for me is sp3.cat. Let me explain: using multiple hot-fixes, e.g: qxxxxxx.exe, i have encountered hotfixes that had greater number than others but the date of sp3.cat was older. I don\'t think it\'s logical. I read a while ago in this forum about some utility catver.exe but i can\'t find it anywhere. I remember that someone even asked about it on M$ OEM System Buider\'s Forum but the response from M$ was: \" Catver is an internal tool and this information should not have been made public in the article. This will be changed. The workaround for this is take the *NEWEST* sp3.cat from all of the hotfix packages you are including and use that one.\"
If anyone (Fjellu ??) can send me this program by email: winetooEmail Removed, please let me know.
About DirectX8.1, I use DX81NTopk.exe, which doesn\'t need any parameters, it just installs silently, I run it in [GuiRunOnce] together with IE6 and other updates and I put it in the $OEM$ folder
Regards,
Victor Chirita.
-
I prefer the second method for several reasons.At the moment you should maybe however wait for the upcoming SP3.
If you choose to slipstream the files, the small catver.exe is a helpful tool which gives you the number of the sp3.cat. To make a complete slipstreamed SP2 + SP3 hotfix CD you also need to repackage some of the .cab files. Cabarc.exe in IEAK6 lets you do this.
For DX8.1 IE6, WMP7 + updates I prefer cmdlines.txt. To make troubleshooting easier I have a separeate batch file for each update which is called from cmdlines.txt
-
Win2k SP3 is expected to come out in August.
-
This is yet another reminder that I need to work on the unattend and oem usage page at my site. I would like to point out to everyone that I know of only two people who appear to have worked this out and tried explaining to everyone. A writer at Windows .NET magazine, who was less than helpful when I contacted the person and then Fjellu. Fjellu has been more than helpful in posting here and emailing me while trying to help everyone. It is my hope that as I try and work on the page soon, to start an email correspondence with Fjellu to help me out on this one.
Maybe is I ask real nice, Pretty Pleeeeeeeese.....
-
Of course I will give every piece of advice I can.
First check out my instructions in the \"Security Rollup Package\" thread. Feel free to contact me directly.
-
MS is right about the \"workaround\", but remember to check for the \"modified\" date in properties. Sometimes the \"created\" date gets twisted when you unpack the hotfix.
I usually use WinRar which in explorer gives you the possibility, when rightclicking the hotfix, to extract to q123456