Bilou_Gateux

Because the new type 1 Cumulative security update for Internet Explorer DLLs have 2 different folders (RTMQFE and RTMGDR) and we should keep only one for integration, according to M$: MS05-014: Cumulative security update for Internet Explorer

Latest news from AR Soft: AR RAM Disk stopped Friday, 11 March 2005 We are sorry to inform you that we have stopped the development and the support for our well established virtual disk product "AR RAM Disk". Read more...

Windows Update was intended to be a consumer update site allowing easy detection and installation of patches made available by Microsoft. WU checks your registry and see what had been installed based on the presence of registry values: HKLM\Software\Microsoft\Updates or HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix WU simply checks a value stored there called "Installed" to see if its 1. If it is, WU won't show you the patch, it assumes its been installed. Microsoft Network Security Hotfix Checker (Hfnetchk.exe) Tool does a file check. HFNetchk uses a reliable mechanism, downloads an XML file containing all of the pertinent details of all patch files (and their contents) and then scans the files actually on disk to make a comparison. Any discrepancy, for whatever reason, is reported (or can be reported if verbose mode is enabled). Microsoft Baseline Security Analyzer (MBSA), free tool from Microsoft, not only looks for missing patches but also checks various configuration settings to see if you haven't addressed known insecure configuration settings. Since it uses HFNetchk for patch checking, it can be considered the same as HFNetchk with respect to patches. WU cannot be trusted to display "the most up-to-date and accurate versions of anything you choose to download from the site". WU's method of determining successful patch installation can't be trusted either. The premise upon which WU works is just too simplistic. Although write access to the registry keys where the information is stored is restricted to Administrators and SYSTEM, there's no verification that what it thinks has been done has actually been done. It relies upon Windows File Protection to ensure that files haven't been altered, but it can't (and doesn't) reconcile itself. Add keys for as yet unreleased patches and it will think they're installed, get a corrupt or altered hive and it will think they're not installed. So in the end, don't use Windows Update.

@GreenMachine Maybe could you improve the plugin feature of the new version to write a plugin that detect the OS (2K or not, that is the question) we build a new CD and then checks the existence of 841356 HF in SVC-HF1 and then do the actions needed to clean the i386 folder after SVC-HF1 sliptream and before creating ISO and burning? Maybe the problem will be solved by himself when M$ release the post-sp4 Update Rollup for Windows 2000.

It's not a problem if my SFX is not digitally signed. I don't edit the inf file and neither break the digital signature. What i want to achieve is just extracting 30x Windows2000-KB<number>-x86-<language>-express.exe, keep the needed files in ROOT (empty.cat spmsg.dll spuninst.exe) and in UPDATE folder (eula.txt spcustom.dll update.exe) of the extracted HotFix and build a single SFX which i can extract where i want. then i will write a batch file which take each update.inf update.ver and KB<number>.cat files from the HotFixes, copy the three files in UPDATE folder and launch UPDATE.EXE /Q /U /O /N /Z I have already checked this method to install HotFixes from SVCPACK using extrac32.exe and cab files with a batch, just having to deal with some delay between each command. but i would like to use a "Microsoft" SFX for the first part of the process. It can help me saving space because it 's stupid to: having 30x SFX containing the same 6 files + 3 different files and launching 30x SFX to install HotFix If we can extract the 6 files one time from a single SFX, and then issuing a command (batch file) that put the 3 files from each Hotfix in UPDATE folder, launch UPDATE.EXE, then delete the 3 files, put the 3 next, and so on... I already know the GreenMachine method with cabarc.exe and looks as an alternative if i can't find another solution. If you can put me in the right direction to create such single SFXCAB...

I have checked WU and we can grab from here special express updates that do not contains outdated binary files but a special file with .psm extension. Look likes infos about Binary files are downloaded from Web and then binary files patched. log file The name of this update is Windows2000-KB<number>-x86-<language>-express.exe Most of the HF type 1 are available as Express version Windows Update.log file Using these express HF can help to reduce footprint of the HF in SVCPACK. Full HFs type 1 = 46.2 Mb in SVCPACK Express HFs type 1 = 10.1 Mb in SVCPACK Examining KB<number>.log files creation and last modified date properties in %windir% Installation with full HFs replaced with Express HFs in SVCPACK take less than 5mn at SVCPACK stage (T-13). For my tests (Windows 2000 Server w/o any SP ENU), i have only added SP4 in SPACKS folder, set SLIPHF1=YES in XPCREATE.INI for checking the Type 1 HF integration and only added 30x Windows2000-KB<number>-x86-<language>.exe in SVC-HF1 folder. Following are the result of my first build with the new XPCreate February 2005 version : We found duplicate files in the resulting i386 folder, both compressed .??_ and not compressed versions: DTCSETUP.EX_ LLSSRV.EX_ NTDLL.DL_ SCHANNEL.DL_ We can save some space by replacing the non compressed version by the extracted version of the compressed files and deleting the .??_ (compressed) files. In the original source CD, these files aren't compressed. DTCSETUP.CAT file should be moved from SVCPACK subfolder to i386 and compressed to replace the original DTCSETUP.CA_ Microsoft have removed the WU checking on Q329115 HF. On a fresh install without any HF applied, WU don't claims about this HF not installed. On Post #51, i suggested to remove KB839645 HF. You shouldn't because WU checks the registry and claims about this HF not installed although a more recent HF owerwrites the binary files with newer versions. Already mentionned are the not needed files added in 2 subfolders by KB841356 and DOSNET not needed added lines.

Where can i get the sfxcab.exe from M$ or how can i build M$ like SFX.

@Michael When i use XPCREATE to slipstream Windows2000-KB<number>-X86-<language>.exe Type 1 HFs, i always edit DOSNET.INF and remove the added lines starting with d1, under the [Files] section. Files in subdir doesn't need an added line referencing them. KB840987, KB841533 and KB891711 contains a subdir named UNIPROC to update the original UNIPROC subdir on 2K source. The files are updated versions of existing files. Only newer files should be added.

Win32 Console ToolBox by Steve Miller

You can query registry and check for existence of INFO: MSXML 4.0 Specific GUIDs and ProgIDs

@tommyp I have downloaded your last slipstreamer_Feb25 archive. After reading instructions.txt, i have noticed some errors: ADD TO [OleControlDlls] SECTION 11,,wshcon.dll,R;SCRIPTEN HOTFIX 11,,msxml2.dll,R;MSXML SUPPORT FILES 11,,msxml2r.dll,R;MSXML SUPPORT FILES 11,,msxml3.dll,R;MSXML SUPPORT FILES 11,,msxml3r.dll,R;MSXML SUPPORT FILES 11,,msxml4.dll,R;MSXML SUPPORT FILES 11,,msxml4a.dll,R;MSXML SUPPORT FILES 11,,msxml4r.dll,R;MSXML SUPPORT FILES msxml<version_number>a.dll and msxml<version_number>r.dll are resource only DLLs. so the correct instruction is ADD TO [OleControlDlls] SECTION 11,,wshcon.dll,R;SCRIPTEN HOTFIX 11,,msxml2.dll,R;Microsoft XML <version_number> parser 11,,msxml3.dll,R;Microsoft XML <version_number> parser 11,,msxml4.dll,R;Microsoft XML <version_number> parser Quote Version list for the Microsoft XML parser

Use BITS for your own downloads A Download Manager using BITS can be found here: BITS Download Manager™ Another one can be found here: WinBITS * Following is the method to determine BITS version installed on the machine Check the file version of %windir%\system32\qmgr.dll If it is 6.0.x.x => BITS 1.0 6.2.x.x => BITS 1.2 6.5.x.x => BITS 1.5 6.6.x.x => BITS 2.0 * To troubleshoot problems with BITS jobs, please use bitsadmin.exe

You can add it in the one you want, all [Files] section from DOSNET.INF are parsed by setup during install. In my W2K DOSNET.INF, i add new dlls sorted in alphabetical order on the biggest [Files] section. Example d1,msxml3.dll line is added just after d1,msxml.dll line In my W2K TXTSETUP.SIF, i add new dlls sorted in alphabetical order on the biggest [sourceDiskFiles] section. Example msxml3.dll = 2,,,,,,,2,0,0 line is added just after msxml.dll = 2,,,,,,,2,0,0 line It's the same if you add msxml2*.dll

infos related to IE6SP1 slipstream into W2K source moved Microsoft Internet Explorer 6 Service Pack 1 (SP1) Version 6.0.2800.1106

infos related to IE6SP1 slipstream into W2K source moved Microsoft Internet Explorer 6 Service Pack 1 (SP1) Version 6.0.2800.1106

How To Use Setup Manager to Create an Answer File in Windows 2000 Sample: UNATTEND.TXT Adjust to your needs.

My post here shows how to use script directive files to achieve this modifications with GNU SED, the Stream EDitor v3.02.80

Have you tried to build your own IE6SP1 package with my batch file: Internet Explorer 6 Service Pack 1 (SP1) The hardest part is to grab the ie6sp1-WUCAB-DEU.cab download link for your language (Deutch ?) from a running 2K box with IE5.x

Do some editing while you re reading

Strange i don t retrieve info about the others DOSNET.INF append in any thread but for sure i delete all the added lines. Bilou Gateux self-proclamed "expert" to figure out 2K issues answer page 5 Windows 2K Security Updates, detailed info thread. My prefered methods for Starting Setup are: from RIS server WINNT32.EXE When the Computer is Running Any 32-bit Windows Operating System WINNT.EXE sometimes When the Computer is Running DOS TCP/IP network boot Never burn a XPCREATE CD to Starting Setup When the Computer is Started from the Product CD

infos related to IE6SP1 slipstream into W2K source moved Microsoft Internet Explorer 6 Service Pack 1 (SP1) Version 6.0.2800.1106

Ooops! Same answer as Dahi. :: set local install DatabaseUpdateDirectoryHttp variable :: 3 tokens are 'ValueName' 'Type' 'Value under selected Key' :: delims is a tab delimiter for /F "tokens=3 delims= " %%I in ('REG QUERY "HKLM\SOFTWARE\Data Fellows\F-Secure\Anti-Virus" /v "DatabaseUpdateDirectoryHttp" ^| findstr "REG_SZ" ') do set DatabaseUpdateDirectoryHttp="%%I" :: For troubleshooting purposes IF %DEBUG%==TRUE echo. DatabaseUpdateDirectoryHttp = %DatabaseUpdateDirectoryHttp%

MITeC select "System Information Component" download the freeware package: contains RBE ROM BIOS Explorer - tool for BIOS/SMBIOS/DMI browsing and disassembling. Works fine under XP Embedded, haven't yet checked under PE. File > Details <CTRL>+<D> will give you all infos read from SMBIOS.

PXE Network - Linux Based - Boot winpe from the net You can map a network share from WinPE and launch the install WINNT32.EXE from the distribution share. PXES HOWTO: Installing in a Microsoft only environment. PXELINUX and Micro RIS I'm using a mixed method and these links showed me the way. 2K Server with DHCP and TFTPD services. MS network DOS boot disk image stored on the 2K server PXE boot load DOS and MS Network map to network share launch WINNT.EXE (16 bits version)

Thanks RyanVM Something new for Win2K users. This new IE6 update is the first one to use this kind of HF for upgrading OS. Should solve the issues we having with GreenMachine when integrating IE6 HF to W2K RTM + IE6 install from SVCPACK.