Martin H Posted February 27, 2010 Posted February 27, 2010 @Mim0Would it be possible to implement using '*' or something else in the ignore lists?I'm reffering to e.g. the lame MRT update(which changes versions each month):+IGNOREH|HF\windows-kb890830-v3.4.exe-No biggy, but just a thought...And again, thanks for all your nice work!
jvidal Posted February 28, 2010 Posted February 28, 2010 (edited) I think you should change the description for LegitCheckControl.cab to something more "understandable", like "Windows Genuine Validation" or similar.The other name doesn't actually say anything. It doesn't mean anything also. the phrase has no logic in it.bye!BTW: I survived the Eartquake! Edited March 3, 2010 by jvidal
tommyp Posted February 28, 2010 Posted February 28, 2010 mimo - can you add in a check for any RAR files in HFAAO and alert the user that rar files should be remade as CABs or 7z's? Rar files don't work well when placed there. Thanks!
jvidal Posted February 28, 2010 Posted February 28, 2010 why would anyone place RAR files knowing they don't work????
tommyp Posted February 28, 2010 Posted February 28, 2010 why would anyone place RAR files knowing they don't work????Because not everybody RTFM.
Kiki Burgh Posted March 1, 2010 Posted March 1, 2010 hello! posted my findings on this in test rel thread. see change log 1.3.0 ... cheers!
Mim0 Posted March 1, 2010 Author Posted March 1, 2010 Would it be possible to implement using '*' or something else in the ignore lists?I'm reffering to e.g. the lame MRT update(which changes versions each month):+IGNOREH|HF\windows-kb890830-v3.4.exe-Done! You can use regular expressions now in the sense in FINDSTR (see FINDSTR /? for details). But regarding yours: You can place a dot (.) as the wildcard for a single character in the filename:H|HF\windows-kb890830-v3...exeBut because the backslash is the escape-character you have to replace it also by the dot:H|HF.windows-kb890830-v3...exeBut you can it make it now more simple: just write KB...H|kb890830I think you should change the description for LegitCheckControl.cab to something more "understandable", like "Windows Genuine Validation" or similar.The other name doesn't actually say anything. It's doesn't mean anything also. the phrase has no logic in it.Yes, if it will be more clear I will do it. I don't know these file and I think the better info comes from users who are using it THXmimo - can you add in a check for any RAR files in HFAAO and alert the user that rar files should be remade as CABs or 7z's? Rar files don't work well when placed there. Thanks!It's included now! 2010-03-01- Changed: The description of LegitCheckControl.cab- Added: Regular expressions allowed in IGNORE-list. How to use RegEx will be described in the INI now.- Added: Hint for RAR-packed AddOn(s) (*.rar) found in HFAAO- Added: When using hints for multiple files (by using wildcards), all matching files will now be listed (instead of only one like before)Mimo
Lilla Posted March 1, 2010 Posted March 1, 2010 (edited) Mimo,Suggestion to make your list a bit more intutitive to use, especially for new users...now...HFSLIP 1.7.9 (final) / HFSLIP 1.7.10 (beta H)suggestion, add links below (or use whatever links you think is best)...HFSLIP 1.7.9 (final) / HFSLIP 1.7.10 (beta H)Thank you for the brilliant HFSLIPFC,Lilla Edited March 1, 2010 by Lilla
theruan Posted March 2, 2010 Posted March 2, 2010 Hi is there any kind of intention on adding the updates that are shown in thehotifxshare(google for it), all of them are downloads originaly from microsoft, you most probably know it already, i have found at least 20 updates in there that are needed in the update process.Tomorrow, i will a list of the updates a have used, and a list of the ones that could be directly slipstreamed, i'm at work right now, and no net until friday at home. Thanks for this great job
Mim0 Posted March 2, 2010 Author Posted March 2, 2010 Suggestion to make your list a bit more intutitive to use, especially for new users...now...HFSLIP 1.7.9 (final) / HFSLIP 1.7.10 (beta H)suggestion, add links below (or use whatever links you think is best)...HFSLIP 1.7.9 (final) / HFSLIP 1.7.10 (beta H)Hi Lilla,thx for this idea. I've thought about it and I come to the conclusion to leave it as it is, because I want to recommend the latest beta. If I add links on th top of the page, a user will probably use the final instead of the latest beta (betas often have the touch of 'unstable'). But I've modified the line with the download-links for HFSLIP in table 6. Until now the final was more in the foreground than the current beta (which is to prefer). I changed it now in that way, that the latest beta stands more in the foreground. What do you think?Hi is there any kind of intention on adding the updates that are shown in thehotifxshare(google for it), all of them are downloads originaly from microsoft, you most probably know it already, i have found at least 20 updates in there that are needed in the update process.Tomorrow, i will a list of the updates a have used, and a list of the ones that could be directly slipstreamed, i'm at work right now, and no net until friday at home. Thanks for this great job Interesting! Yes, I would like to see your list. : I've just quick looked at this side. Many hotfixes!!!
Martin H Posted March 2, 2010 Posted March 2, 2010 "i have found at least 20 updates in there that are needed in the update process."Needed??? Hotfixes are fixes for non-widespread, non-critical issues, which is developed fast and hasen't gone through as much regression-testing as the normal updates...Also, since HFSLIP allready is using the QFE branch of the updates, then the files in the updates allready include the fixes from the hotfixes(only for the included files in the updates that is...)
Lilla Posted March 2, 2010 Posted March 2, 2010 (edited) Suggestion to make your list a bit more intutitive to use, especially for new users...now...HFSLIP 1.7.9 (final) / HFSLIP 1.7.10 (beta H)suggestion, add links below (or use whatever links you think is best)...HFSLIP 1.7.9 (final) / HFSLIP 1.7.10 (beta H)Hi Lilla,thx for this idea. I've thought about it and I come to the conclusion to leave it as it is, because I want to recommend the latest beta. If I add links on th top of the page, a user will probably use the final instead of the latest beta (betas often have the touch of 'unstable'). But I've modified the line with the download-links for HFSLIP in table 6. Until now the final was more in the foreground than the current beta (which is to prefer). I changed it now in that way, that the latest beta stands more in the foreground. What do you think?I like it! I like that you give a recommendation as this will help people!Lilla Edited March 2, 2010 by Lilla
tommyp Posted March 3, 2010 Posted March 3, 2010 First off, sorry for contaminating this thread with an off-topic post. As far as I am concerned the beta is pretty stable. I still await others to chime in (on the right thread) to say it works for them too. If I don't hear anything, then I'll assume it works and release it. I'll give it until the end of the week and then I can call it a day.
theruan Posted March 5, 2010 Posted March 5, 2010 (edited) "i have found at least 20 updates in there that are needed in the update process."Needed??? Hotfixes are fixes for non-widespread, non-critical issues, which is developed fast and hasen't gone through as much regression-testing as the normal updates...Also, since HFSLIP allready is using the QFE branch of the updates, then the files in the updates allready include the fixes from the hotfixes(only for the included files in the updates that is...)Sorry, i may have used a worng word for that, i'm brazilian, my english isn't that good, lol.A good word would be as optional updates, and also, you that obviously knows more about updates Tommyp could take a better look on them.In HF folder:WindowsXP-KB944898-x86-PTB.EXEWindowsXP-KB945060-x86-PTB.EXEWindowsXP-KB945436-x86-PTB.EXEWindowsXP-KB946554-x86-PTB.EXEWindowsXP-KB946666-x86-PTB.EXEWindowsXP-KB946775-x86-PTB.EXEWindowsXP-KB948046-v2-x86-PTB.EXEWindowsXP-KB948101-v3-x86-PTB.EXEWindowsXP-KB948277-x86-PTB.EXEWindowsXP-KB948720-x86-PTB.EXEWindowsXP-KB949033-x86-PTB.EXEWindowsXP-KB949127-v2-x86-PTB.EXEWindowsXP-KB949764-x86-PTB.EXEWindowsXP-KB949900-x86-PTB.EXEWindowsXP-KB950162-x86-PTB.EXEWindowsXP-KB950312-x86-PTB.EXEWindowsXP-KB950565-x86-PTB.EXEWindowsXP-KB950616-x86-PTB.EXEWindowsXP-KB950982-x86-PTB.EXEWindowsXP-KB951312-x86-PTB.EXEWindowsXP-KB951347-x86-PTB.EXEWindowsXP-KB951624-x86-PTB.EXEWindowsXP-KB951709-x86-PTB.EXEWindowsXP-KB951822-v2-x86-PTB.EXEWindowsXP-KB951937-v2-x86-PTB.EXEWindowsXP-KB952079-v2-x86-PTB.EXEWindowsXP-KB952117-v2-x86-PTB.EXEWindowsXP-KB953028-x86-PTB.EXEWindowsXP-KB817688-x86-PTB.EXEWindowsXP-KB889320-v2-x86-PTB.EXEWindowsXP-KB932521-x86-PTB.EXEWindowsXP-KB940648-x86-PTB.EXEWindowsXP-KB943326-x86-PTB.EXEIn HFSVCPACK_SW1 folder:WindowsXP-KB974266.exeAll of this ones were taken from thehotfixshare, i know that may be not all of them are available in every language and so far will sometimes be hard to acquire them, but they still are hotfixes that could or not be added to the list.They are optional, and still have to check if they are not replaced already.What i can say for sure is that i have tried using them with nlite to see if any problems related to older updates beeing used and so far it showed me only five(or something like that) updates that were replaced that i already removed from my list.Also i think you could remove this:missing (S): HF\WindowsXP-KB960225-x86-PTB.EXE (MS09-007: SChannel (Secure Channel))as this check in my opinion is not need 'cause it's replaced, only the new one sould be checked.ThanksTheRuan Edited March 5, 2010 by theruan
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