Tomcat76

E = end of line V = exclude I = case insensitive L = literal search L is probably used so you can do without a backslash in front of the dots in these search strings. I was thinking of having HFSLIP compress new ASMS files anyway but just exclude *.man files. But I don't know how nLite copes with a source of which some ASMS files are already cabbed and some not so I thought it safer to just leave all files uncompressed.

It's working for me in IE6. Make sure nothing on your PC is blocking referrers...

I tried all three of 'em... Can't see the problem...

@Camarade: Try 60809a...

Nothing was changed for XP and 2003 in 60808x...

KB917008 for Win2K is not OK. I'll revert to HFSLIP_60808a once I get my computer running again (spilled coke on the keyboard... again!). I'll then try to figure out how to have it slipstreamed properly. @Camarade: I'll check it out.

@Camarade... What I find strange is that Windows complains about an error in a manifest file, but it names a catalog file instead. Are you sure that isn't a typo? That folder contains: gdiplus.cat gdiplus.dll gdiplus.man The manifest file is gdiplus.man. When reducing the source, does nLite also delete files from ASMS?

I like that better. Done.

Win2K: MS06-040 Vulnerability in Server Service: Windows2000-KB921883-x86-ENU.EXE MS06-041 Vulnerability in DNS Resolution: Windows2000-KB920683-x86-ENU.EXE MS06-044 Vulnerability in MS Management Console: Windows2000-KB917008-x86-ENU.EXE MS06-045 Vulnerability in Windows Explorer: Windows2000-KB921398-x86-ENU.EXE MS06-046 Vulnerability in HTML Help: Windows2000-KB922616-x86-ENU.EXE MS06-049 Vulnerability in Windows Kernel: Windows2000-KB920958-x86-ENU.EXE MS06-050 Vulnerabilities in Hyperlink Object Library: Windows2000-KB920670-x86-ENU.EXE MS06-051 Vulnerability in Windows Kernel: Windows2000-KB917422-x86-ENU.EXE Win2K + IE5: MS06-042 Cumulative MSIE5: IE5.01sp4-KB918899-Windows2000sp4-x86-ENU.exe Win2K + IE6: MS06-042 Cumulative MSIE6: IE6.0sp1-KB918899-Windows-2000-XP-x86-ENU.exe Win2K replaced: KB908523 and KB916281 ************** WinXP SP1+SP2: MS06-040 Vulnerability in Server Service: WindowsXP-KB921883-x86-ENU.exe MS06-041 Vulnerability in DNS Resolution: WindowsXP-KB920683-x86-ENU.exe MS06-045 Vulnerability in Windows Explorer: WindowsXP-KB921398-x86-ENU.exe MS06-046 Vulnerability in HTML Help: WindowsXP-KB922616-x86-ENU.exe MS06-050 Vulnerabilities in Hyperlink Object Library: WindowsXP-KB920670-x86-ENU.exe MS06-051 Vulnerability in Windows Kernel: WindowsXP-KB917422-x86-ENU.exe WinXP SP1: MS06-042 Cumulative MSIE: IE6.0sp1-KB918899-Windows-2000-XP-x86-ENU.exe WinXP SP2: MS06-042 Cumulative MSIE: WindowsXP-KB918899-x86-ENU.exe MS06-043 Vulnerability in Outlook Express: WindowsXP-KB920214-x86-ENU.exe WinXP replaced: KB888113 and KB916281 ************** Win2K3: MS06-040 Vulnerability in Server Service: WindowsServer2003-KB921883-x86-ENU.exe MS06-041 Vulnerability in DNS Resolution: WindowsServer2003-KB920683-x86-ENU.exe MS06-042 Cumulative MSIE: WindowsServer2003-KB918899-x86-ENU.exe MS06-043 Vulnerability in Outlook Express: WindowsServer2003-KB920214-x86-ENU.exe MS06-045 Vulnerability in Windows Explorer: WindowsServer2003-KB921398-x86-ENU.exe MS06-046 Vulnerability in HTML Help: WindowsServer2003-KB922616-x86-ENU.exe MS06-050 Vulnerabilities in Hyperlink Object Library: WindowsServer2003-KB920670-x86-ENU.exe MS06-051 Vulnerability in Windows Kernel: WindowsServer2003-KB917422-x86-ENU.exe Win2K3 replaced: KB916281

Yeah, I noticed that too. There's a new test version already; I'm in the process of updating the Test Releases thread. Get it here if you can't wait...

Balance (security updates): 2K = 9 updates (5 replaced) XPSP1 = 7 updates (4 replaced) XPSP2 = 8 updates (4 replaced) 2K3 = 8 updates (2 replaced) I still need to check if there are any problems with any of those....

The actual hotfix lists aren't part of the main HFSLIP site.

No further info available at this time. Brace yourself....

Yes; your TXTSETUP.SIF is clean. These things happen. Anti-virus or anti-malware programs doing their thing or hard drives that screw up. You may want to do a chkdsk e: /r (from a DOS box) to see if everything's still fine with it.

Hi, kenlau. Can I have a look at your txtsetup.sif file, please?

No wonder you never noticed... You already have a boot.bin file. Move boot.bin out of the HFTOOLS folder and then use an older version of HFSLIP. It won't make a new boot.bin.

Done.

I see why. Sorry about that. I was so focused on fixing the BBIE problem that I didn't notice I broke the section that comes after that (the actual ISO creation). A new version will be released immediately. Thanks for reporting this.

Or they did it once a couple of months ago. There's no need to create it again if you already have it.

It didn't work for me -- neither in HFSLIP, nor in another program I'm currently working on. I actually never noticed this because I don't use HFSLIP to make an ISO. When I noticed the problem in that other program, I tested it in HFSLIP and it didn't work there either.

When you the least expect it... I'm waiting for TommyP's results. Then we can release a new one.

Did you apply the service pack and the hotfixes to an admin install of Office 2003 or to a basic "CD copy"?

So far, it's coming along quite nicely. I lost a bit of time trying to figure out how to specify the destination folder of an admin install up front -- I don't want to force the user to fill it in him/herself. I couldn't find any documentation on this but it's OK now. Done: - check for administrative rights - create admin installs off the installation CD into predefined folder - skip creation of admin installs if they already exist - detect version of Office (limited to "OFFICE") - overcome "missing files" problem with Office 2000 English (CD1) - patch Office 2000 with SR1 and SP3 (CD1 & CD2) - exclude Office 2000 SR1/SP3 from list of hotfixes to be parsed - slipstream hotfixes for Office 2000/XP/2003 ("first CD" only) - exclude PVMSO.MSP from being parsed To do: - service packs for Office XP and 2003 - hotfixes for subcategories other than "OFFICE" - find out which *.MSP files should be ignored (hotfixes) - find a way to detect already applied service pack to bypass error dialogs ** **Using /qb- or /qn rather than /qb as an install switch isn't workable. Those bypass dialogs messages, but, if an error occurs during installation, the installation will "roll back" without telling you (your only lead is the blue bar which moves to the left). So I have to use /qb.

@TAiN: Thanks. @ricktendo64: Is there any way not to make it so? One thing you may encounter is buggy detection on the Office Update site, especially with Office 2000. But everything seems to be OK lately. There is one "problem", though: sometimes, Office Update may disallow you to do a quick install of a missing update via its web interface, telling you that "you need the administrative version of the update". This is not the case with the Microsoft Update web site, but Office 2000 isn't supported by it. So users of Office 2000 may need to download and install the full admin version of an update from time to time.

Download Office Patcher can silently update admin installs of the mainstream Office CDs with the latest service pack and hotfixes. Supported versions: Office 2000, XP/2002 and 2003. Supported "subcategories": Office, Frontpage, Project, Visio, OneNote and Publisher. Features: - allows user to create an administrative installation from CD if no admin install exists for the relevant subcategory (this part is obviously not fully automated) - if an administrative install already exists in the relevant subfolder it isn't created again - by default, only the main Office CD is treated; the others need to be "unlocked" via an external answer file - the answer file can also be used to skip certain subcategories (useful for example when you patched Visio before but don't want or need to patch it this time) - silently slipstream the service pack and hotfixes you provide into the admin installation(s) - for Office 2000: overcome "destination file doesn't exist" errors - supports all languages Subfolder structure: OFFICE FRONTPAGE PROJECT VISIO ONENOTE PUBLISHER The OFFICE folder is created by default. You should only create the others manually if needed. The updates for these categories go in a subfolder with the same name as the one for the subcategory but with an underscore in the front. For example: updates for FRONTPAGE go in _FRONTPAGE. The service pack for Office and Frontpage needs to be placed in _OFFICE only; no need to have it twice. System requirements: - Windows 2000 or higher - Windows Installer 2.0 or higher - administrative privileges - enough hard disk space Quick how-to: 1) Log on as a user with administrative privileges. 2) Extract this package into a folder of your choice. 3) Place the hotfixes ("fullfiles" only) into the relevant subfolders; create as necessary: _OFFICE _FRONTPAGE _PROJECT _VISIO _ONENOTE _PUBLISHER 4) By default, only the first CD (Office) is handled; if you wish to update other CDs from the same package, create an answer file called OFFPATCH.INI and place it in the same folder in which the main script file resides. The answer file should contain the following entries: OFFICE= FRONTPAGE= PROJECT= VISIO= ONENOTE= PUBLISHER= Add "1" (without quotes) next to those you wish to see handled or "0" (without quotes) next to those you want the script to ignore. 5) If you don't yet have an administrative installation of the package(s) you wish to update, have your installation CDs at hand; when the program asks if you want to create a particular source, insert the relevant CD and then answer the question with "y". Doing so, the standard administrative installation wizard will show; you can pre-insert your user information at that point if you wish. If you already have administrative installations, create the needed subfolders and copy your administrative sources into them: OFFICE FRONTPAGE PROJECT VISIO ONENOTE PUBLISHER 6) Run the program and wait till it's finished. Known current limitations: 1) The Office version can only be determined based on the first Office CD. 2) There's no exclude list for unneeded *.MSP update files for Office 2000 and XP yet, so you may receive error messages for Office versions other than Office 2003. You can ignore these but it would help if you report the name of the hotfix that was being slipstreamed at that time. 3) A known issue with patching Office 2000 is that you may get errors about missing destination files. Office Patcher contains a list so it can work around that, but the list is not complete. Please report any missing destinations including the path as stated in the error messages.