tommyp

Bug report with hfslip-70203b. In hfslip.cmd in svcpack, there is bad commandline START/WAIT rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 .... Version hfslip-1.2.2 does not have this problem. The correct commandline is: rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 ....

@whitehorses - on the test release thread, you said that your hfslipwu.inf isn't getting run. There should be this entry in your sysoc.inf file. That INF is key to make hfslip and hfcleanup to run properly. I just tested hfcleanup with the current test release and all is fine on my side. [Components] WinUpdate=ocgen.dll,OcEntry,HFSLIPWU.INF,HIDE,7 Also, a few days ago you had posted a zip file with some txt files in it. The readme of the zipfile says you are making custom strings, which is evident because some of those strings are not part of the listed hfcleanup fileset. I'm not sure if you are copying and pasting things to create those filter.txt and other txt files or not, but.... There are some blank lines in those txt files. Blank lines are NG with hfcleanup. If any of those reducers have blank lines, setup will fail because it will be reducing more than you bargained for. Sometimes it could erase the entire contents of an INF! EDIT - I have to double check the WINLite70203b version out, I saw some errors during installation. Version hfslip-1.2.2 works fine.

Thanks for the file. It could be a dependancy thing as you suggest. I totally agree with the dependancy thing. Nlite has some dependency issues too. Files/programs get installed a few different ways. These include combo installation INFs with separate sections, individual setup INFs, syssetup.inf and the HIVExxx.INF files. Some are spread out across multiple INFs and some are one INF for one particular program and some INFs install a torrent of programs. [by programs I mean EXEs, DLLs, etc.] Services are probably the toughest to remove because there are tons of dependencies. Windows is pretty complex (and sloppy) and because it's proprietary, there isn't information out there that tells about dependencies. Linux lists dependencies. Everybody has unique needs, and a default windows pretty installs everything. With reducing windows, it's a learning process of what to remove to suit your needs. I could have generated a 3 or 4 reducer files that could do everything in one shot, but some things just wouldn't work because of the dependency thing. I took a stab at reducing, as you point out it's 100% perfect, but it's a shot. NLITE on the other hand has many great things as far as reduction, but sometimes doesn't reduce enough IMHO. Maybe there is some obscure dependancy he is taking account.

Sorry, I'm not familar with regex. I was thinking of parsing infs for filenames and deleting the filenames and somehow doing some sort of filtering. It's easier maintaining a list of INF files instead of a few thousand individual files inside the rem/rdv/rin files. Are the files in your source folder read only? Can you attach your hfslipwu.inf file from a fdv/hfcleanup?

Nice find dude. I think this may help some of those pesty files that accidentally get erased once in a while! Only the txtsetup, dosnet and the drvindex files should be processed like this. The other hfcleanup type files should continue using the existing filtering method (i.e. without the /L switch). It will need to get tested first though. Ouch!

Yea, that is a bit abnormal. This question is dumb because I'm not familar with that type. Is your i386 folder like this? driveletter:\hfslipdir\source\i386 BTW, would you be interested in a new hfcleanup method? I have some ideas that may work. But it's a large undertaking.

On an unadulterated system (haha), the task scheduler registry info is installed with ie.inf. FDV"s fileset places the task scheduler stuff in the del add section so it won't get installed. When hfcleanup is run, the registry entities are removed totally. But, IIRC, the mstask INF file in hfcleanup corrects things for the false icon (I could be wrong, that was a year ago when that icon was fixed). Are you using a virgin source? Are you using some other reducer? edit - you editted your above reply when I typed the above out. Let me try this. There is an option when running hfcleanup with fdv's fileset. You have the option to leave fdv's files alone or to hfcleanup them too. True, editing of the IE.INF is risky, but I tried to mimic FDV's work when not using his fileset. In other words, I typically slipstream ie6, but I remove iexplore with hfcleanup, leaving the ie6 core behind. There are many ways to skin a cat with reducing the source... this was my spin on it. I could be wrong with the way I clean things up, but it works for my needs. I encourage people to generate reducers and test them out before submitting.

I tested with hfslip-1.2.2. There are some others that use HFCLEANUP that don't have the same mstask issue as you. Are you changing the hfcleanup files at all? Are you using all 3 mstask files?

dirtwarrior - I meant to say that NLITE is easier with XP. I love 2k with hfcleanup. It works like a champ. whitehorses - I just tested an FDV version of 2k with dx9/hfcleanup. I can't repeat your empty task manager icon in control panel, all seems ok on this side.

@whitehorses - All seems to work well with ie6/dx9/hfcleanup. I haven't thorougly tested with FDV's fileset. Pls report any findings. @kiki - I think nlite is easier to use instead of hfcleanup. I don't have time to tame the XP beast tame.

I know exactly what you are talking about with the "dummy" icon in control panel when removing mstask. Tinkering with that INF was pretty tricky (I don't use the existing 2k ie.inf). Which string of characters shouldn't be removed? If it means anything, the following strings are only in the IE.INF file (reg add sections) CLSID_MSTASK CC2A9BA0-3BDD-11D0-821E-444553540000 The SchedulingAgent string is in IE.INF (reg add section) and wkstamig.inf. The latter file really doesn't matter, it looks like it is for an upgrade or something non important. In either case, only the original ie.inf has these reg add sections. FDV's ie.inf just moves it to the delete section so it can't get installed anyway. He could have just deleted those lines instead. If it means anything & if I remember correctly, if you run that mstask inf, and reboot, the dead control panel icon will be fixed. That was tricky to find/fix at one time.

I think I can answer this one. While Oleg2 was away (remember he hasn't been to the board in about 10 months), I grabbed the reigns and added some reducers. I kind of thought Oleg lost interest in this stuff, and there was some reduction needed. I compliled the cleaners and have them on the hfslip site. I'm working on some more, but I'm not having much luck with getting them XP friendly. Maybe I have a weird hotfix or something....

If you are using an OEM folder like it says in unattended.msfn.org, you can put the OEM folder structure alongside your source\i386 folder. When run, HFSLIP will simply copy the OEM folder to the sourcess\i386.

Kiki - The files in the hfexpert\appreplacement folder get "pemodified" (if required) and compressed. The FIX folder assumes the files are already compressed and pemodified (if required). Not all files require pemodify, but the ones in appreplacement typically do. I suppose putting your winnt.sif file in appreplacement could work, but I never tried it. Why not test and report back? Sorry I can't answer your first part of your q.

I could be wrong, but if you are using the sfcfiles from his IE reducer, you're using the 2000 version (won't work with XP). I haven't seen it on his site, but if you somehow found a sfcfiles version for XP, then disregard this message.

If any installation INF isn't written correctly, it won't install. Sounds like you modded the script and it broke some installation INF. Sorry, I don't plan on helping with this one, there are too many variables. If it means anything, the main setup infs are sysoc.inf, sysssetup.inf, and the hfslip infs. IIRC, syssetup.inf is only processed if using hfcleanup and/or using FDV files.

The first time I heard a Sony, I was absolutely disgusted. Nowadays, the audio manufacturer's are really pulling the strings with they way they spec them out. Audio equipment manufacturers forced people to believe that less THD is better. To get less THD, the design of the circuitry would need lots of feedback. This makes practically no distortion, but it also kills the character of the music. IMHO, the change came about in the mid 1980's. Like dirtwarrior, I had an old 55 wpc receiver back in the early 80's. In the 90's I thought I did an upgrade when I bought a 100wpc model. I was extremely disappointed, especially since I was 500 bucks lighter! The past few years, I was busy designing and building my own audio amps, I made 3 so far just to say I could do it. I opted for tubes with my designs. The smallest of the amps is a 20 wpc amp. It may be hard to believe this, but the 20 watt amp outperforms the 100 watt amp (and the 55 wpc amp) hands down. It's louder, has character, and adds lots of realism (and it looks better too). The 70 wpc tube amp I made is an absolute masterpiece, but it weighs 70 lbs. From a people's perception of music, it gets interesting. Any type of amplification distorts, there's no way around it. Transistors distort in odd order harmonics. Tubes distort in even order harmonics. People perceive even order distortion as a pleasant thing... which makes it sound warm. Bottom line, sometimes distortion isn't a bad thing, just as long as it's perceived nice.

datarelm - I don't doubt your expertise, I'm only trying to help. HFSLIP works best when it detects a clean source. What you may want to try is to let HFSLIP slipstream the USP5 instead of you doing it manually. The point I'm trying to make is that if *any* setup INF files are incorrect, you will get a bum installation. This brings up a question you asked about IE6 hotfixes. Well, HFSLIP processes IE5 hotfixes different than IE6 ones. HFSLIP *thinks* you have IE5, so it may be processing your IE6 hotfixes the way you wouldn't expect. This could lead to bad installation INFs, which could render a bad sourcess folder. Personally I don't use the USP5, I use individual CAB and hotfix files. All DX9 components are successfully installed less pictures of joysticks/controllers. Many others report successful DX9 slipstreaming with HFSLIP too. On a sidenote, if you use the list of hotfixes on the link I previously posted, there isn't a 137 gig barrier with a CD install.

datarelm - You don't have the IE6 cabs, but you have IE6 hotfixes. You have a wmp9 hotfix, but you have the WMP9 installer in the incorrect place. So of coarse it's not working, you don't have it set up properly. I would recommend you read up on what file goes where (link) and retest. Also, you are using a pre-hacked 2k disk. You should really use a unadulterated installation source. You will not get the proper results if you use a prehacked source.... Sorry for intruding on the NLITE board to post an HFSLIP answer.

datarelm - I feel funny posting an HFSLIP question in the NLITE forum, but can you post your hfslip.log file so I can see how you are slipstreaming dx9c on 2k?

To help track your previously patched source... Is there a source\i386\svcpack folder? Is there a source\i386\NLITE.IN_ file? Is there a source\i386\hfsl***.inf file(s)?

You can put reg files in the HFSVCPACK folder too.

Last 6 months.... Hussain is dead, war continues, pinkos are in charge of congress, and no actions of driver packs other than the posts in this thread.

Can we have a link to this? http://www.siteadvisor.com/sites/hfslip.org/

I have a feeling that you will run into problems with that folder, but you are more than welcome to test the waters and report back. You should call your vendor up and request an installation cd.