Tomcat76

Thanks, Kramy. Using HFSLIP version 60409a, mkisofs.exe should accept any variation in case.

I've seen that a couple of weeks ago but forgot all about it. Thanks.

That update is about the length of the HFSLIP source. It should be nearly 1990 lines now...

@Camarade_Tux -- If size really matters, check the latest... Now I need to lie down for a while... I'm not gonna explain what I did with those lines... Thanks to TommyP, btw... He gets the credit for the last couple of updates...

Done.

@PROBLEMCHYLD: OK

@dziubek -- Try the new version. @Camarade_Tux/TommyP -- What folder?

ROFLMAOIf you're into this sort of stuff, you might wanna try hooking up a 4-pin molex to 3-pin male converter for a case fan to the same power cable the hard drive is connected to, and then bring the three pins in touch with the computer case while it's running. Fireworks guaranteed!

It's not supported. I'm afraid that's all I can say. Maybe TommyP or FDV can clarify it better.

Redist Web

Funny... My imaginary wife tells me the same thing...

Updated. XPize**.exe in HF folder ==> slipstreamed XPize**.exe in HF folder + answer file in HFTOOLS folder ==> silent svcpack install Note that you'll probably need a modded sfc.dll or sfc_os.dll file if it's going to be slipstreamed. I'll add a check for the presence of these files in the next version. Edit: Done.

Just an FYI... XPize is not slipstreamed. I asked for more info on this a couple of posts back but nobody got back on that. It is merely being installed through SVCPACK.

During Windows setup, the SP4 version is installed and registered and then overwritten with the version from the latest hotfix that contains it. Basically, for non-English versions of Windows 2000, HFSLIP does what the non-English Rollup and KB900725 installers do.

@Kiki: You didn't send the wrong message. I was just mentioning it as an aside. 407b is out. Support for XPize plus optional removal of CAT files if sfc.dl_ or sfc_os.dl_ are detected in FIX.

HFSLIP still supports it. There wasn't even a period in which it was temporarily removed, to my knowledge. I love 2K too much. The looks, the icons, the speed at which folder content displays, Windows not automatically removing backslashes when copy/pasting a URL as a folder name... I only use XP for video editing.

I like that one... The hyperthreading problem is worked around by USP5 and HFSLIP (and possibly by other slipstreaming programs too but I don't know for sure). The only remaining problem -- as some people have reported -- is that the fix doesn't kick in after the computer wakes up from hybernation. Hybernation is one of the buggiest features of Windows so I'm not really sure if the fix is to blame or even Windows itself. Also, there are other programs that "don't work as expected" after Windows returns from hybernation. I always disable the hybernation and standby features so everything works great for me in this regard.

Apparantly, security problems (vulnerabilities) affect webvw.dll from SP4 and the one in the Rollup. The latest version is included in the KB900725 hotfix. BTW... HFSLIP *does* install the latest version of webvw.dll. The problem you read about on FDV's page (which is a registration problem) is worked around. I don't know much about the halmacpi.dll issue. That's "before my time", hehe.

Hehe...

What "command to run"? HFSLIP uses FINDSTR. Make sure it exists in your system32 folder.

Huh... what?

do you mean "If this doesn't work"? No... "If this works" = "If it works using an XP Gold source from friends"...

What you see in TXTSETUP.SIF is correct. Those files need to be copied into two folders. I could use an alternate method to see if it satisfies Livestate. Edit: try 60406a. This should work around the problem with Livestate. The "10-15 first"?

@dziubek... What's that install prompt you're getting when going to the Windows Update site? What are you being asked to install? I don't really understand your problem with My Documents. When you install on a VM, does Windows think your documents are located in C:\My Documents? It's to be called "mplayer2.exe", yes. Appreplacement replaces files in I386 and the file you want to replace is called "mplayer2.ex_". I've taken a look at the XPize program but I fail to see how nLite is being told which switches you want to use. Also, does this work from SVCPACK? @Kiki Try mplay32 from Run. That's not "the DOS player" but WMP 5.0. It would be more of a nuisance if it flashed "Thank you for using a genuine copy of Microsoft Windows!" once in a while...

@dziubek... Remove Boooggy_ASPI_Addon.cab for now. I'll check what's going wrong with it tomorrow. I'll try to fix the CDImage problem too.