tommyp Posted February 4, 2007 Posted February 4, 2007 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?
whitehorses Posted February 4, 2007 Author Posted February 4, 2007 (edited) hmm.. interesting, but sounds effective. What infs are these? does every component has an inf? I know that dfrg.inf is the defragger, but many other component's installer code is obfuscated by MS.I think that such parsing is not possible without accidentaly deleting other unwanted things, or not perfectly removing those which wanted.There is the problem with the current method, that it does not manage dependencies, but that could be solved by not fregmenting, but merging removal files, ie. merging dependig packages, and making a more complete removal on that area.I don't know.HFSLIPWU.INF Edited February 4, 2007 by whitehorses
tommyp Posted February 4, 2007 Posted February 4, 2007 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.
whitehorses Posted February 4, 2007 Author Posted February 4, 2007 I don't know. This is a hard question.I think I take a nap.
tommyp Posted February 4, 2007 Posted February 4, 2007 (edited) @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,7Also, 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. Edited February 4, 2007 by tommyp
whitehorses Posted February 5, 2007 Author Posted February 5, 2007 (edited) I'm making some test too. I will report back later. the custom strings are at the very begining of filter.txtBy the way task scheduler issue is solved. The task scheduler registry key is created by a dll (shell32), not just by ie.inf by default.FDV's IE.INF is registered as RunOnce by hfslipwu.inf, to run its [FDVPATCH] section. Now that will occur AFTER shel32.dll gets registered, so the task scheduler entry in the delreg section re-removes the entry from the registry. If hfcleanup filters fdv-s ie.inf this issue occurs. Edited February 5, 2007 by whitehorses
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now