johndoe74

updated to v8.00.64

hi! would there be a topic dedicated to HFs that need to be placed in the aforementioned folders or could it be specified in the HF lists around? ... most of the HFs i have are Type 1 ... thanks! only the hotfixes NOT supported by hfslip are required to be put in HFSVCPACK_SW1 OR HFSVCPACK_SW2 (depending on the type of the hotfix and what installation switches it accepts). The rest of the supported hotfixes are supposed to go in HF as usual

i know - what with work and everything it took me two days to do a new build, make an image, install and then run HFNetChk and MBSA before reporting my results

Maxthon Browser v1.6.1 build 22 [2007-05-31] What's new: Added Auto suggest in search box. Enable/Diable it at Maxthon Options->Search. Added Option to use old style multiple search (Maxthon Options->Search) Fixed a resize problem under Vista Standard File size :: 1.36 MB (1,430,078 Bytes) MD5 :: A8BD68D68BF1AD91B9106573F3C609C0 Main :: Esnips Mirror :: FileFront Combo File size :: 4.30 MB (4,504,666 Bytes) MD5 :: C1BFC240656BD1DFC2F03621DF48185A Main :: Esnips Mirror :: FileFront

no, it's fine. check to see if maybe your downloaded file isn't corrupted by comparing MD5 hashes. if they do match, try with some other antivirus. or just wait a day or two then update avast and try again. sometimes these antivirus definitions have "issues"

hi, i just did a new build with 70524a. It's awesome Everything installs fine, everything works great. Even the unsupported hotfixes, KB907265, KB934238 and KB907306! (although only KB907265 shows up in add/remove, i checked and the files from the other two are also present - i believe the reason they don't show up in add/remove has to do with the way the patches are built/installed rather than anything to do with hfslip itself) just one question regarding the capicom thingy - yes again earlier you had suggested using the msi from the sdk "capicom_dc_sdk.msi" yet the latest builds include support for the other CAPICOM hotfix "CAPICOM-KB931906-v2102.exe". i know this one also contains an .msi "capicom2.msi" but what's the difference between the contents of the two and which one would you personally suggest going with ?

so by the way, i just manually installed the webfolders thingy on a virtual machine with the quiet and norestart switches and it worked fine. so is it alright to put it in HFSVCPACK_SW1 ? it should work, right ?

RIP HFSVCPACK_SW - died bravely fighting till the very end - deserved nothing less than a medal of honor and a 21-gun salute

well i did suggest here that maybe you could modify the code such that if hfslip were to detect an unsopported hotfix in HF that it automatically create a switchless silent installer so the hotfix does end up installed one way or the other (there really aren't too many of those unsupported HF floating about so it should hopefully not take up a lot of time/resources/effort of the part of you guys)

i suggested exactly this sort of thing to the tc and tp, didn't get a reply tho, maybe they're quietly workin on it or maybe they just plain ignored it

you'll have to repack those hotfixes in the form of switchless silent installers in order for them to work via HFSVCPACK. It does work that way, I currently have KB907265 installing that way (it's not supported by HFSLIP for direct integration)

regarding those switchless installers, maybe you should try those that have been created by roguespear or ryanvm. as for the .net 1.0 sp3 hotfix, it works perfectly with the last few version of hfslip - just put it in the HF folder. regarding your posts they are located here and here

hi tcp/ip, sorry, i mean tc/tp those morons did it again! just released a new hotfix with a knowledge article base number that is different from the number of the hotfix itself, the hotfix doesn't use the standard naming sequence or the standard installation routine. i'm constantly surprised at how many different ways they can find to screw themselves sideways and they keep coming up with new ways everytime! i doubt this is supported by hfslip, right ? could you guys get it to work ? also, on extracting, it comes up with an .MSI and a .CAB. I extracted the cab but it didn't contain any files matching those from my source though

there's a few things you need to do. MCE comes with .net 1 SP3 built in, so you have have the hotfix for it in HF folder : NDP1.0sp3-KB887998-X86-INTL-Ocm-Enu.exe next, a prerequisite for the installation of the update rollup is that .net 1.1 SP1 should already be installed, so what you gotta do is get a switchless silent installer from like roguespear or ryanvm for that and put it in SVCPACK so it gets installed at T13 and then you gotta put update rollup, the update for that and your .net3 switchless/silent installer in HFGUIRUNONCE. so at the end of the day, you end up with .net 1 SP3, .net 1.1 SP1, .net 2 and .net 3 (.net3 includes .net2 as well). messy, but that's how the people that make 'em like 'em

updated to v1.40.520

regarding those hotfixes that are NOT supported by hfslip, just an idea but is it possible that if found in HF, HFSLIP would make an SFX of those those patches (update\update.exe) and install via SVCPACK at T-13 (the same way IE7 is installed when NOT slipstreamed)? Two specific patches I have in mind are KB907265 and KB934238

which six ? anything I should know about ?

great thanks

sorry to have to do this but *bump*

Hi Tomcat76, I was just going through your update list for Win2K SP4, I notice you include both SCRIPTEN.CAB in HFCABS and KB917344 in HF when slipstreaming IE6. My question is, do we need to have both there ? Don't they both contain the same thing with 917344 being the latest available, hence SCRIPTEN.CAB contents being obsolete ? I've removed SCRIPTEN.CAB from my source and MBSA doesn't complain that it's missing (if 917344 is present) Also 928090 needs to be replaced with 931768

you can download it here

you're from there too ? nice to meet you brother

i tried. it works. everything perfect. 'nuff said oh yeah, before i forget... vary nyce

that was cuz I didn't play with it yet, just excited the issue has been resolved! doing a build now, will surely provide feedback (hopefully all positive)