Tomcat76

Whoops...

I see no real difference with version 1.3; both can be run silently without dialog boxes using the exact same switches.For anyone that wants to know: suppress the reboot with /NORESTART. That's what I'm using in my silent installer.

MultiCompiler makes a silent installer out of the Hex Blog hotfix. So far, this installer should work on Windows 2000, Windows XP, and during Windows XP installation (SVCPACK). Windows 2000 installation (SVCPACK) still needs to be tested. Put it in HFSVPK when using HFSLIP. @TommyP: As far as I can understand this, the real problem is GDI32.DLL.

Microsoft: "Un-register the Windows Picture and Fax Viewer (Shimgvw.dll) (...). While this workaround will not correct the underlying vulnerability, it will help block known attack vectors." So it should be possible to unregister it with a CMD as a temporary fix until the real problem is dealt with by MS. If we had to take into account "unknown attack vectors" as well we'd be better off switching to Linux immediately.

290x8.0 @ 1.300V, MEM @ 2.70V, "southbridge" @ 1.50V. I tried 292x8.0 yesterday but that got me an error after 1.5 hours. It's now running at 1.325V again and I'll test it tonight. I shouldn't try 293 because it'll freeze Windows at some point. BTW... Prime95 is playing tricks with me again. You got me on the right track last time when you said I should set the affinity in Task Manager as well. This worked twice, but it doesn't anymore. I can only run one instance of Prime95. Check list: - Copy the P95 program files to two folders - Set one to CPU0 and the other to CPU1 - When started, go to Task Manager and set the one for CPU0 to CPU0 only and the other to CPU1 only - Start the Blend test for CPU0 and immediately after the Blend test for CPU1 It looks like I'm gonna have to use Windows XP for this sort of thing and not 2K...

Codecs? Well... I have to admit I didn't take a close look at the content of the WMP fixes; I only looked at the title for KB817787: "Flaw in Windows Media Player Skins Downloading could allow Code Execution", and the description for Q828026: "[The] content owner can add script commands (...) that are embedded in the stream. When the stream is played back, the script commands can trigger events in an embedded player program, or they can start your Web browser and then connect to a particular Web page. The 828026 update (...) modifies Windows Media Player to recognize three new registry values that permit a user or an administrator to control the scenarios where the player will run URL script commands that are embedded in a stream. (...) Additionally, logic was added so that when Windows Media Player does run URL script commands, the script cannot take the user from a less-trusted security zone to a more-trusted security zone." (Red was chosen to stay in the Christmas spirit ) So... From the list of "critical" fixes, I mark the two WMP fixes as "not-slipstreamable". Which of the marked recommended/optional fixes should I consider "not going to be processed" at the next HFSLIP release?

If it makes things any easier, I updated the list of SP1 hotfixes in the Windows XP thread. You'll find descriptions and links for every hotfix in there, and the ones that fail are marked.

OK... I added all updates including optional updates (except KB327405 which is nowhere to be found -- not even on WU Catalog). These are the things that didn't install... Required by WU: - WU v6 - BITS/WinHTTP5.1 - Package Installer Critical: - KB900725 - KB896426 - KB839645 - KB841873 - KB817787 *** - KB828026 Optional: - KB833998 - KB327979 - KB322011 - KB810243 - KB814995 Other: - Windows Media Connect 2.0 - DirectX 9.0c *** KB817787 is WindowsMedia8-KB817787-x86-ENU.exe. This one failed during the slipstream process, showing this error: Windows Media Update 817787 Command line option syntax error. Type Command /? for Help. This is what I got from the /? switch: /Q /T:blahblah /C /C:blahblah (The "blahblah" is mine B)) Should I put it in HFSVPK_SW? On the brighter side... 62 updates WERE installed fersure...

It's possible. I figured out that the "Fatal Error" is caused by editing LAYOUT.INF. If I use the original (unmodified) version, setup goes on to the end but then the drivers are not installed. I've never used FDV's fileset, but if I'm correct he employs a modded setupapi dot whatever which disables driver signing.

Changing the "2" to "1" got me to the end of the file copy stage. A bit into the second stage (after the reboot), I get a fatal error. I just went to take a look at the TXTSETUP.SIF file for Win2K, and the "= 2" is apparantly something special. Its XP equivalent is "= 100". I'm gonna try this now and see if it gets me any further.

I think you need "= 1" for WinXP instead of "= 2". 1 = \i386 2 = \cmpnents\tabletpc\i386

I just modified TXTSETUP.SIF manually to what it should be. I don't understand why the line isn't added. I also cleaned some of "the bloat": [SourceDisksFiles] CMDOW.EXE = 1,,,,,,,1101,0,0;HFEXPERT iuctl.cat = 1,,,,,,,1101,0,0;HFEXPERT iuctl.dll = 1,,,,,,,1101,0,0;HFEXPERT iuctl.inf = 1,,,,,,,1101,0,0;HFEXPERT HFDRV.CAB = 2,,,,,,_x,39,0,0 [SetupData] DriverCabName=HFDRV.CAB,driver.cab [FileFlags] HFDRV.CAB=16 (I added the reference to HFDRV.CAB in the [sourceDisksFiles] section created by HFSLIP and removed the empty [setupData] and [sourceDisksFiles] sections.) This allowed me to continue setup (second attempt), but somewhere near the end of the file copy stage, this message comes up: Insert the CD labeled: Windows XP Professional CD 2 into your CD-ROM drive • Press ENTER when ready. This is probably caused by the fact that this is inserted at the end of LAYOUT.INF: [SourceDisksFiles] [SourceDisksFiles] This apparantly activates the "need" for CD2. For some reason, these two lines in your CMD are not inserted into the relevant files: ECHO HFDRV.CAB = 2,,,,,,_x,39,0,0>>SOURCESS\I386\LAYOUT.INF ECHO HFDRV.CAB = 2,,,,,,_x,39,0,0>>SOURCESS\I386\TXTSETUP.SIF Instead, an additional [sourceDisksFiles] section title is created. So I don't think it's a Windows version problem... but I don't know what's causing this LAYOUT.INF/TXTSETUP.SIF editing to fail.

This is nice. I'd like to see it succeed. WinXP Pro (English) The following value in the .SIF file used by Setup is corrupted or missing: Value 0 on the line in section [SourceDisksFiles] with key "HFDRV.CAB." Setup cannot continue. To quit Setup, press F3. This is what the bottom of TXTSETUP.SIF looks like: [SetupData] [SourceDisksFiles] [SourceDisksFiles] [SetupData] DriverCabName=HFDRV.CAB,driver.cab [FileFlags] HFDRV.CAB=16 I've modified HFDRV.CMD a bit, but that only consisted of removing the superfluous spaces before and after the arrows (> and >>). This is the relevant part: ECHO INCLUDING HFDRV.CAB INTO TXTSETUP.SIF REM I am not sure if it is needed but just in case... echo DriverCabName>>txtsetup.log findstr /v /b /i /g:txtsetup.log sourcess\i386\txtsetup.sif>txtsetup.sif move txtsetup.sif sourcess\i386\txtsetup.sif del /f /q txtsetup.log ECHO [SourceDisksFiles]>>SOURCESS\I386\TXTSETUP.SIF ECHO HFDRV.CAB = 2,,,,,,_x,39,0,0>>SOURCESS\I386\TXTSETUP.SIF ECHO [SetupData]>>SOURCESS\I386\TXTSETUP.SIF ECHO DriverCabName=HFDRV.CAB,driver.cab>>SOURCESS\I386\TXTSETUP.SIF ECHO [FileFlags]>>SOURCESS\I386\TXTSETUP.SIF ECHO HFDRV.CAB=16>>SOURCESS\I386\TXTSETUP.SIF

I used to have a 5.25" drive in my system too until the beginning of this year. I got rid of it because nForce systems (first nForce2 Ultra 400, then nForce4) don't support more than one floppy drive...

9 hours and 11 minutes. It was a long night...

I think most people rely on Windows Update or Automatic Updates to keep their system up to date; they're not going to download updates manually from the Download Center. Windows Update wouldn't give me anything until I installed the BITS update and the Package Installer... The BITS update is not in your list, btw, so it's strange that MSBA came out clean. I double-checked, but I may have missed a couple. The ones that I didn't ask to remove from the SP2 list are for SP1 as well (at least they should be).

Still use 'em. System drive pre-partitioning with EFDISK.EXE (MasterBooter) and FORMAT.COM; killing hard drives with Norton Disk Editor; MemTest86+; fixing drives with BootMaster Partition Recovery... Not just my own but also the ones I get in from other people for repair/cleaning. It's just more universal, and, as someone said earlier, "I don't like to waste CDs". I used to use a floppy for flashing the BIOS but I leave the BIOS files on a FAT32 partition now, so the floppy is only used to boot into DOS in this case. I've never really liked CDs... They're too small for backups and it takes a long time to burn one of my 4x CD-RWs so I use DVD+RWs instead (which require a DVD-ROM, though). And I switched back to vinyl in 1994... LOL But I always suggest to other people to try to ditch the floppy. Most of them still want it for "their banking". IMO, this is safer than USB sticks, though, as USB sticks are more likely to be stolen than floppy disks, haha!

Shark: I was referring to the "Windows" folder inside your package. On Win2K, it's usually called "WINNT" except when upgrading from Win9x (or when changing it with an unattend). MultiCompiler = this

It used to be in the instructions but I can't find it anymore. It was something about hotfixes updating themselves during execution when having a live Internet connection.

No worries --- I'm not using it either. I just wanted to verify the list of SP1 fixes. But it's strange that noone else mentioned anything about it. Am I alone?

[Attachment removed] Windows XP Pro SP1a, English. These updates did not install: - KB900725 (Vulnerabilities in Windows Shell) - KB839645 (Vulnerability in the Windows shell) - KB841873 (Vulnerability in Task Scheduler) - KB898461 (Package installer) These programs did not install: - DirectX 9.0c (BDAXP.cab and dxnt.cab) - Windows Update v6 - Windows Media Connect 2.0 Concerning DirectX 9... The installation wizard for the nForce system drivers (which I ran manually afterwards) complained about not having DX9 installed, and dxdiag.exe reports version 8.1. These programs WERE installed: - HighMAT update - WMP9/10 codecs I didn't check these yet: - the 5 new cabs from DX9 - MSXML 4.0 SP2 - Windows Script 5.6 - LegitCheckControl.cab There are 18 updates missing from the SP1 list in my thread, so I still need to check if they would install properly.

Alrighty... Will go with the 170 then...

Thanks for the tip. They don't fully use the CPU simultaneously, but one of them does use 100% (aka "50%") of CPU now. This is how the program used to work for me in the past.

Uh... yeah. That's what I wrote in my first post in this thread...

Having an active Internet connection might...