tommyp

cacls is a nice script/dos utility to change permissions.

T - Please allow a few more days for others to test and report back. Sit back, don't code, relax and wait for the population's feedback. Once all is fine, then go for it.

To all (not Tomcat) - What is the big h@rdon about DOTNETx? I mean, IMHO, it's not really required for the OS. It's a program. Is MS Office a operating system an OS requirement? No. Why not just use your own crafted post-windows installers for installing dotnet (and any other programs you want to install)? My PC runs GREAT without dotnet.

I am still unclear on the problems with the latest fileset. What are the issues you have after you install using an hfcleanup/hfslip? Is it just the startmenu items? What start menu items do you want; what are you expecting there? Please don't use comparisons from the march release, they really don't help me troubleshoot. If it means anything, the 2kextra was originally part of the march hfcleanup, but those files don't work well with 2003 and xp. This is why I separated them in the may release. BTW, what is the s3legacy?

The 2003 files can be left in. I don't think they reduce anything with 2000, but I leave mine in. As far as the shortcuts goes, some are installed by syssetup.inf. What shortcuts are you missing? From the sounds of it, it sounds like the cat issue is resolved? There is no need to see your winnt.sif file. If it worked before, it should still work. Can you make a list of specific issues you have? The only reason I ask is that I'm not sure if some were resolved and/or if others popped up. I'd like to make hfcleanup compatible with fdv's fileset as much as possible (for me all works fine).

NtegrA - Thanks for your troubleshooting, patience and solution to the problem. We welcome solutions that help out.

Are you excluding any files from the hfcleanup? Are you selecting Y to filter FDV's infs? (you should be) Are you using alternate files in the fix folder other than winnt.sif? (you shouldn't be).

My vote is to dump that netdiag all together. But maybe to keep others happy, perhaps the best is to stuff it into that tools directory in the source.

Nah, I don't think you'll be able to type with your fingers crossed.

If I do a manual install of kb911280 on 2k, I do not have a netdiag.exe after rebooting. Perhaps this is because my OS is so slimmed down it's not needed? I will test tomorrow on a regular 2k box.

Squeet - Sorry about the multiple hfslip runs. Type your Y's in CAPS for now, especially when prompted about filtering FDV's infs. I'll make sure that the next release has this fixed up for case sensitivity.

Why are you replacing FDV's DLLs in your fix folder? You're probably better off not replacing them. For me, I don't use FDVs fileset, but I do use FDV's sfc.dl_, sfcfiles.dl_ and setupapi.dl_ in my fix folder. If that doesn't work, you can always delete the nt5.ca line from your 2000_Only_WorthlessUpdates.rem file.

Crash - You nailed it right on the head. All HFSLIP does is automate what any IT person should be able to figure out. Heck, I'm not IT person, I don't even do computers for a living. So if a dummy like me can figure out how to automate it, a trained IT person should be able to do it at his/her company.

Squeet - There's two zips to get for cleaning up w2k. I don't get any copy errors (or any others) during installation when doing hfcleanup with that fileset. BTW, in case anyone is wondering, if you have your dialup settings the way you like it, create a copy of this file: "%systemdrive%\Documents and Settings\All Users\Application Data\Microsoft\Network\Connections\Pbk\rasphone.pbk" Place this file back in it's happy home during installation and create a shortcut to it on your desktop. Works for 2k and xp.

Squeet - Are you using hfcleanup?

Can you try deleting your hfcleanup folder and re-running the script? HFSLIP detected an HFCLEANUP folder.... and FYI, HFCLEANUP isn't the smoothest out there reductionwise.

Doesn't look like a zip file.

Forwarder - I haven't checked your hotfixes you want to slipstream, but have you verified your files are the ones listed on tomcat76's signature? Garbage in = garbage out. Don't go too wild at first, start off slow and work up from there. Also, is the machine you are sitting in front of have a functional 16 bit subsystem? Or have you removed the 16 bit subsystem using nlite?

Squeet - If you are running hfcleanup, search through all the hfcleanup reducers (use the search feature in windows) and search the contents for the "offending" file you want to keep. Remember, you need to search leaving that last character off in your search string.. ex getuname.dl Once you find the rem file, delete the rem file and the corresponding rin file from the hfcleanup folder. BTW, dlls and some exes get installed via an INF files. You'll need to find the right inf file to restore. Good luck.

Kiki, HFSLIP is a HotFix SLIPstreamer. You are best off making your unattended program installation on your own.

Ummmmm.... this was fixed a long time ago with hfslip. HFSLIP slips the rollup halmapi and already applies the proper registry info.

Are you sure you thoroughly searched the forums? I had to slipstream some via raid/sata stuff a while back. I ended up manually modifying the files in my source folder. I found the answers on the msfn messageboard. Perhaps this link will help you out.

Kiki, Please read the readme in the ZIP file. I didn't write it for my enjoyment. hehe. Sounds like you are using all the reducers and you have no idea what you are doing. If you are running NLITE on the sourcess folder, don't bother using HFCLEANUP, just use NLITE instead. It's a far better reducer than HFCLEANUP. BTW, the Gosh reducer was written in honor of a great poster on the MSFN boards. She had great tips for reducing the source if you want to install by CD only. Hint... a CD only install doesn't need dosnet.inf.

yaz - I'm loooking at some of these files and I don't quite understand what the reg.keys is. What are they supposed to be filtered out of? Here's some info for you (and important too). If you have any setup INF files that aren't right, you'll have strange errors on the installed source. In other words, an INF will not process if any files to copy aren't available, or if you call to register a DLL file and the DLL isn't registerable. So, you have to be quite careful on what to filter out. Deleting files is a piece of cake. The problem lies in the setup INFs. It seems that you are the one the VERY few who actually are contributing to this. I ran out of time and patience on these reducers... Here's a little commandline you can run. Create an folder called INFS inside your HFSLIP folder. Run this: FOR /F %I IN ('DIR/B/A-D/ON source\I386\*.in_') DO EXPAND -r SOURCE\I386\%I infs This expands all of the setup infs to a folder called INFS. In there, you'll need to search through the INFs for various things.

Please don't contaminate this thread with multiple posts, can you please condense them into ONE zip file? I assume that you tested these with 2k, xp and 2003? BTW, I had a volume shadow copy reducer with those same files at one time, all it did was give a failed installation. If you haven't tested any of these, please don't post them. We're not here to troubleshoot your work.