Tomcat76

Works for me. What's the date on the original file? Edit... Oh wait... What do you mean by "you put the QFE file in the HF folder?" The HF folder is for hotfixes...

I'll PM you...

Sure you aren't removing anything with nLite? Open WindowsUpdate.log (not Windows Update.log) from the WINDOWS folder in Notepad and look for a "Setup: Checking whether self-update is required" header. Below that, you should see a bunch of files being referred to and some details on whether they need to be updated or not. Is everything OK there?

Funny... I never experienced this RunOnceEx problem... Not even when HFSLIP slipstreamed IE7 and didn't delete the IE7 version of iernonce.dll...

I thought the tokens weren't needed either, but I'd consistently get "ECHO is on" or "ECHO is off" (depending on whether I added the ECHO command at the top) if I didn't include the TOKEN for this particular case. I experimented a bit to find out why but I have better things to do so I gave up. The /IR isn't necessary. You can see I didn't spend much time on it...

I'm guessing the DLLs didn't get registered properly. Which version of HFSLIP were you using?

Imagine them doing overtime... Just a quick FYI for people that visit their local shrink every week... If you re-downloaded this cab after reading Kiki's, Super-Magician's or my post, it's still the same version. So relax and everything will be fine...

I know that, but you wrote: This confuses me. The SOURCE folder is supposed to contain a copy of the original CD. That would include the WINNT.SIF that's on the CD. So what's the point in copying the file into FIX too? I can't imagine anyone having done a "Select all" in the CD's I386 folder, deselected WINNT.SIF and then copied the selection into SOURCE\I386...Either way, if the OEM supplied a copy with a modded WINNT.SIF, just put it in SOURCE\I386 with the rest. There's no need to use the FIX folder unless you actually make a change that you don't want to use all the time (it's easier to remove something from the FIX folder than it is to remove something from SOURCE\I386).

I don't understand this. HFSLIP copies all content of the SOURCE folder into SOURCESS, including WINNT.SIF if it exists. So putting WINNT.SIF in the FIX folder doesn't serve any purpose unless you make modifications to it.

@Kiki IE6.0sp1-KB918899-Windows-2000-XP-v2-x86-ENU.exe --> this is not for XPSP2 MBSASetup-EN.msi --> put this in HFSVCPACK_SW

Me again I'm trying to post some code in a CODE box but the forum software is eating up the space in front of a semi-colon. This breaks the code. ECHO>>FILE.TXT ;%%I ECHO>>FILE.TXT;%%I This might be related to the problem Yzöwl reported over a year ago... http://www.msfn.org/board/index.php?showtopic=48600

If you want to parse every line with a filename it could be something like this: FOR /F "TOKENS=* DELIMS=" %%I IN ('FINDSTR/IR ",,," SOURCE\I386\TXTSETUP.SIF') DO ECHO>>SEMITXT.TXT ;%%I This is on one line.

Please follow IcemanND's link and download the driver for your OS.

HFEXPERT\DRIVERCAB. The INF file goes in there as well. But this only works with merging options A, B or C.

There have been four releases after 61129a. Can you please try the latest? KB926139 is not supported.

@Kiki That's some interesting reading, but if HFSLIP really causes Dell pre-activation to break then I'd like to know how that happened. @bingho In the Microsoft article that the page Kiki links to is linking to, they outline a possible workaround. Edit OOBEinfo.ini in the I386 folder and add the following to it: [Version] ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" ...where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is your product key. See if that gets you anywhere...

Updated again.

RBCC-- I'm a bit confused here. Does it have anything to do with HFSLIP? If so, into which HFSLIP folder are you putting that file?

Considering that command line, it should work with the following entries in HFANSWER.INI: CDBURNAPP="C:\IS Burner\IsoBurner.exe" CDBURNSW1= CDBURNSW2=/BURN /EXIT-IF-OK But don't you need to specify the destination drive somewhere? Or will the program auto-detect blank media?

Oleg! Welcome back... Go in the BIOS and see if you can set the controller to RAID. Normally, this should configure the controller for JBOD mode if you only have a single drive connected to it. I think Windows will require a floppy then...

KB918005 -- supported (should've been supported for a long time) KB922120 -- not quite. The new binaries are handled fine since HFSLIP version 1.0, but you still need to manually execute one command post installation: %SystemRoot%\System32\rspndr.exe -i

I need to know how Dell keeps it activation-free before I can check out what's causing this. I don't think I have a Dell OEM lying around but I'll look in the box for my father's Dell laptop if I can find it again. I'd leave a message on the Hardware subforum for your CPU problems. It looks to me like your BIOS doesn't pick up the correct FSB and/or multiplier by default (Sempron 2200 is 166x9). BTW... If you can afford 3 CPU's, why don't you take an Asrock ALiveNF6G-DVI for a motherboard and a Sempron64 2800+ AM2 or an Athlon64 3200+ AM2 for a processor? These don't get fried...

So? Any comments? This didn't make it into version 1.1.0 because nobody said if the implementation was workable or not. Please let me know (by using the current test release) if it's good or if you'd prefer to see some changes.

The power of IE7's iernonce.dll. The latest test release (61203a) no longer slipstreams IE7, but instead has it installed at T-13. For me, this fixes all problems related to IE7 so you can try it too.

KB920213 is a hotfix for Microsoft Agent but you are removing that application with nLite. The hotfix updates agentdp2.dll, agentdpv.dll and agentsvr.exe but MS Agent consists of more files than that, so I'm not sure what advise I should give (keep only those files or keep MS Agent as a whole).