tommyp

This is by design. FDV has a rather large fanbase for IE removal, and most do not report problems on this board.

That hfsliplog says it takes 3 minutes to run? I don't believe it. Dumb statement, but you need to select the merged driver option for the hfcleanup files to be parsed. Unless the hfslip log generation is whacked.. You may want to remove the cluster file to keep AD as well. I don't know for sure, I don't use AD.

Dirt, don't run HFSLIP with HFCLEANUP or FDV's fileset with HFSLIP and you'll be OK.

IIRC, the user creation was out from the beginning, not the latest build. Try the wbem/wmi. I use the NET USER command to add users.

whitehorses - Please keep your questions HFSLIP related as this is the HFSLIP forum. It sounds like you have basic windows setup file questions. Your best bet would be to search/ask in the correct forum and/or search the web.

Can you attach your winnt.sif file?

I'm kind of swamped for the next few weeks (or months) doing non-computer activities, so I really can't test & incorporate. A few Q's. Is your CMD smart enough to pick which drive has the cd burner?

Give us your batch file and I'm sure we can incorporate it.

If your PC takes 58 minutes to run the script, you have a really slow machine and/or it's bogged down with spyware/junkware and/or your source is bloated. If I run in hfcleanup mode, it takes about 16 minutes. I'm siding with Yzowl on this. Let's keep hfslip lean and not dependant on too many windows functions and most importantly not a remedy for a computer user's short term memory loss.

Can you copy the HF folder to the "other" HFSLIP folder? Hard drive space is cheap, less then 50 cents a gig. My 2k HF folder is 100 meg, XP's HF folder is less than 100 meg. Add 'em both up and you get far less than 50 cents.

I'm a bit confused here because I'm not sure what are doing there. Please just run HFSLIP with your codec packs, media players, etc, install your sourcess and try out the media files. Next run NLITE on the hfslip'd sourcess and then try your media files.

That list was compiled using a 2k source, heavily NLITE'd in order to achieve proper playback of wmv and other "windows media" type files. Because NLITE doesn't like inputs for 2k users, I had to figure out how to make wmv files play correctly. Thus the creation of the list. Bear in mind, this was put together waaaay before wmp10 or wmp11 was out, and I have no intention of using either.

Sounds like you [almost] answered your own question. Why not try it out?

Here's a hint if you are using nlite and you want your codecs to work. Don't remove any audio drivers.

That link may be a grey area. I could have forwarded your post to the super mods of this site where you may have been banned without notice. However, I was nice to just delete the post and look the other way. Hope I did not offend anyone. http://www.msfn.org/board/index.php?showtopic=18408

Now now now, let's keep this clean.

By reading the KB article.

Don't use spaces in your HFSLIP folder. Change C:\My Work Files\HFSLIP to C:\MyWorkFiles\HFSLIP.

I forgot to report back. I had no issues with that last file you sent me. Sorry dudes.

Agreed, this is not what HFSLIP is all about. I'm sure it's possible though. I'll leave it to the community to figure out.

wela - please refer to the HFEXPERT page for fine details. Short answer, create a folder structure alongside your hfslip cmd file: HFEXPERT\WIN. Place your file in that folder.

saugatak - Thanks for noticing that in the forums. I waited well over a year for a change request to get processed and got practically nothing. This is why the HFCLEANUP efforts started.

tadc - Sounds like you are using this for a corporate thing and not personal use. Thanks for your support.

The program files will cause countless errors from users. I would strongly recommend to delete this section of code and not rebloat hfslip. EDIT - TC informed me that he thoroughly tested this feature. Nevermind.

Double check your hotfixes to be sure that you are slipstreaming the correct hotfixes for the service pack level you are running. One thing that sticks out is that you are slipping a mediacenter edition hotfix.