tommyp

If you get copy errors during txtmode, it's usually a modifype related issue. Sorry I haven't tried the codec packs out.... I figured I would actually "use" my computer for a while. I already have my picture purfect install so there really isn't any need for improvements and/or changing my hfexpert stuff......

the_guy - can you verify this with installing the problematic HF onto a non-hfslipped machine and check the file versions?

Dirt, you should read up on fdv's site.

Yes

IIRC, the new windows update *replaces* the original files (the new windowsupdate has the same filenames and a few extras). So there is really isn't any old windowsupdate files to remove.

Why not just NOT run the windowsupdate reducer? It's much easier.

Kiki is 100% correct. You can delete it post-intall if you like.

Microburner? A small exe that does it all. No formal installation program, just an exe file.

It's either an old hotfix with binaries that are old -or- it may be a hotfix with extra files to be slipstreamed. By extra, I mean it's files that aren't part of the source\i386 folder. In any event, those messages can be ignored.

Let's not make hfslip fix hfnetchk mistakes (yes they make mistakes). The aforementioned update was an issue for quite some time. FYI, I use hfnetchk as a guide to see if the binaries are up to snuff. WindowsUpdate does a great job at check registry values. The MSBLA is most thorough.

The "NET USERS" command if you want make a CMD file and throw it in the right folder.

Here's two things... skinning a cat & the file to put into FIX is sfcfiles.dl_. The FIX files are copied over at the end, overwriting anything that is in the sourcess\i386. The contents of the appreplacement gets fixed with the MODIFYPE.EXE program, is cabbed and then placed into the sourcess\i386 folder.

A1. Yes, but only if you put the correct reducer in the folder. A2. Yes, if you modify the reduction files. If you need windows update utilities that bad, just don't use the WU reducer. I think the orig WU is only two or three files, but IIRC they get overwritten when running hfslip (if the folders are populated correctly).

There's more than one way to skin a cat.

Those reducers are crafted by me with lots of inputs from Oleg from earlier this year... and yes they are a bit buggy. Have you read the readme in that zip file? They do work great on a 2k install.

Reducing 2k3 is very time consuming. I spent weeks on it. TC - if you want mplayer2.exe shortcuts, don't run the latter file you mentioned. Typically I stay clear of the 3Z, 4Z and 5Z reducers. You just get a small OS that you can't really use. BTW, if you want a small OS with all functionality, go with SLAX. Everything you need in a 200 meg iso.

IIRC, someone asked for SP1 fixes to be put into the script. Let's just keep it in, but not do any more updates.

I saw this file recently too (before the C was added to that cmd file). I was kind of convinced it was due to my virus scanner removing my cmdow.exe file when running hfslip to get my new sourcess. Perhaps I am wrong?

The work directory was not deleted in certain cases is because it came in handy when developing hfslip. Sometimes I had to see what was happening in the work directories. I guess you are playing with another variable in the INI file. You probably want to not include that variable in there.

(hint hint) We welcome coder's inputs. Anyone feel like contributing some code?

unregister mydocs.dll? Sorry, re-read first post again.

It's not in the works as far as I know.

I think it was vaporware. Nothing ever became of it.

Have you read the info on FDV's site? Or have you read the main hfslip thread on this board?

Thanks for reading the documentation about HFSLIP. As you have read, HFSLIP is for PERSONAL use and not for company use. Thread closed.