
tommyp
PatronContent Type
Profiles
Forums
Events
Everything posted by tommyp
-
Deploy on a bunch of machines huh? Are you using this for a corporate environment?
-
xof - Does this mean that you will give me your paycheck? Please refrain from using hfslip and do your own job integrating hotfixes. HFSLIP is not the tool you can use. Please obey the licensing, IT people should know better about software licensing. Thread closed.
-
You can start by comparing your hfslip.log hotfix list to the stickied post hotfix list.
-
Thanks for the apology. There's tons of information for setting up in a corporate environment, it just happens that HFSLIP is not the avenue to drive down to do it. iamtheky said a mouthful there. Let's get on to getting the hfslip forum happy again. But I'm sorry to say that please don't expect ie8 integration at this point (unless someone wants to contribute a subscript).
-
See first post for the special "shduff edition" of HFSLIP.
-
shduff - You do realize that hfslip is for PERSONAL use and not for corporate use. Since you are using it for your job, does that mean that I get paid for doing your work instead of you doing the work yourself? People like you make me want to stop hfslip altogether. I have prepared a special fix that supports this issue. Please visit the beta thread.
-
Thanks for the input. Strange how the old HF was updated only for server.
-
It kind of sucks when a hobby turns into a job (and a job that you get absolutely nothing for).
-
In txtsetup.sif, you should see mplayer2.exe = 2,,,,,,,,3,3 If you see a semicolon in front of it, remove it. In mplayer2.inf, you should see [WMPCopy.Core] mplayer2.exe,,,33 if you see a semicolon in front of it, remove it. I had probs with fdv's fileset with mplayer2.inf. I used to delete his and put my own file there. Mine worked to my liking.
-
That's done via the winnt.sif file. Here's mine: [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] Unattendmode=FullUnattended OemPreinstall=Yes TargetPath=WINDOWS Filesystem=LeaveAlone OemSkipEula=Yes Repartition=NO WaitForReboot="No" DriverSigningPolicy=Ignore I'm not quite sure if the "unattended" part is needed, it could be. But the combo of both will definately give you what you want.
-
No IE8 support will be available and there are no plans for it either. Soon HFSLIP will not be supported either. Sorry about that.
-
Sounds like you are a wmp11 type of guy. How unfortunate. lol. There's FAR better media players than wmp11. Assuming your using the latest beta, you can use HF for the 959772 update. I'll have to add this to the WU listings. The 961118 is a .net related issue not a windows update. I don't plan on integrating a .net update into hfslip. Sorry about that.
-
I don't know the workings of the driverpack program, but I guess I can try as good as anyone. I'd suggest to try eliminating FDV's fileset, rerun hfslip and then run the driverpack program on the sourcess folder.
-
Can you check to see if the file attributes of all the files in the source directory are not read only?
-
I'll take the Stewarts. Thanks.
-
Mimo - Thanks for the contribution. I'll add in your link to the update list.
-
Tomalak - After saying what the deal is with the windows search v4 and where it goes, is this thread still valid enough to be stickied? Is the windows search v4 a critical update?
-
I use replace\i386 to replace files inside teh i386 folder. The replace may be a better option for replacing too. If a hotfix binariy has a newer date than what you manually replaced, the files you want may not be in the sourcess. A safer bet is to use the replace folder where the files will overwrite irregardless of filedates. The replace actions happen at the tail end of hfslip, just before it makes the iso.
-
Holy run on sentence! Sorry pal. You're just going to have to use a virgin source (like the rest of us clowns). lol. It's not the intent of hfslip to detect what you already did to your cd. The problem lies is that when slipstreaming wmp11 or its hotfixes, hfslip first detects if the wmp11 installer is present. If it's present, the script branches off to extract key folders of the extracted hotfix. Since hfslip is not detecting the wmp11 installer, it won't branch off. Since you already slipstreamed the wmp11 installer, maybe you can just slipstream the individual binaries manually.
-
I'd suggest to revisit the WU lists on the first stickied thread and get the appropriate hotfixes. It seems that you are trying to slipstream a WMP11 hotfix, but you aren't slipstreaming WMP11. You have 5 IE7 hotfixes, there's only 3 required (plus the installer). There are 5 WMP11 hotixes (plus the installer) and you only have 1 hotfix. Also, HFSLIP is detecting a modified source. HFSLIP works best with a virgin source.
-
Is this an non-english hotfix prob? Here's my update list. It only flags the new autorun hotfix and the malicious software tool, which I didn't include in my HF folder. I don't consider either a mandatory hotfix. I am not using hfexpert or replace. Anyone want to verify that we are running the same files? I don't intend on being the one to compare lists. If it means anything, I am using the D beta. Constructive criticism appreciated! Files in your HF folder: directx_9c_redist.exe IE6.0sp1-KB905495-Windows2000-x86-ENU.exe IE6.0sp1-KB938464-Windows2000-x86-ENU.exe IE6.0sp1-KB958215-Windows2000-x86-ENU.exe IE6.0sp1-KB960714-Windows2000-x86-ENU.exe MDAC253-KB927779-x86-ENU.exe MPSetup.exe msxml2.msi msxml2sp6-kb887606-x86-enu.exe msxml4-KB954430-enu.exe msxml6-KB954459-enu-x86.exe OE6.0sp1-KB951066-Windows2000-x86-ENU.exe rootsupd.exe Windows2000-KB842773-x86-ENU.EXE Windows2000-KB891861-v2-x86-ENU.EXE Windows2000-KB893756-x86-ENU.EXE Windows2000-KB896358-x86-ENU.EXE Windows2000-KB896423-x86-ENU.EXE Windows2000-KB899587-x86-ENU.EXE Windows2000-KB899589-x86-ENU.EXE Windows2000-KB900725-x86-ENU.EXE Windows2000-KB901017-x86-ENU.EXE Windows2000-KB901214-x86-ENU.EXE Windows2000-KB905414-x86-ENU.EXE Windows2000-KB905749-x86-ENU.EXE Windows2000-KB908519-x86-ENU.EXE Windows2000-KB908531-v2-x86-ENU.EXE Windows2000-KB911280-v2-x86-ENU.EXE Windows2000-KB913580-x86-ENU.EXE Windows2000-KB914388-x86-ENU.EXE Windows2000-KB917008-x86-ENU.EXE Windows2000-KB917537-x86-ENU.EXE Windows2000-KB918118-x86-ENU.EXE Windows2000-KB920213-x86-ENU.EXE Windows2000-KB920670-x86-ENU.EXE Windows2000-KB920683-x86-ENU.EXE Windows2000-KB920685-x86-ENU.EXE Windows2000-KB921398-x86-ENU.EXE Windows2000-KB922582-x86-ENU.EXE Windows2000-KB923191-x86-ENU.EXE Windows2000-KB923810-x86-ENU.EXE Windows2000-KB923980-x86-ENU.EXE Windows2000-KB924270-x86-ENU.EXE Windows2000-KB924667-x86-ENU.EXE Windows2000-KB925902-x86-ENU.EXE Windows2000-KB926436-x86-ENU.EXE Windows2000-KB927891-x86-ENU.EXE Windows2000-KB928843-x86-ENU.EXE Windows2000-KB930178-x86-ENU.EXE Windows2000-KB931784-x86-ENU.EXE Windows2000-KB933729-x86-ENU.EXE Windows2000-KB935839-x86-ENU.EXE Windows2000-KB935840-x86-ENU.EXE Windows2000-KB938827-x86-ENU.EXE Windows2000-KB941569-x86-ENU.EXE Windows2000-KB942831-x86-ENU.EXE Windows2000-KB943055-x86-ENU.EXE Windows2000-KB943485-x86-ENU.EXE Windows2000-KB944338-x86-ENU.EXE Windows2000-KB945553-x86-ENU.EXE Windows2000-KB950749-x86-ENU.EXE Windows2000-KB950974-x86-ENU.EXE Windows2000-KB951071-x86-ENU.EXE Windows2000-KB951698-v2-DX9-ENU.exe Windows2000-KB951748-x86-ENU.EXE Windows2000-KB952954-x86-ENU.EXE Windows2000-KB953155-x86-ENU.EXE Windows2000-KB954211-x86-ENU.EXE Windows2000-KB955069-x86-ENU.EXE Windows2000-KB956802-x86-ENU.EXE Windows2000-KB957097-x86-ENU.EXE Windows2000-KB957280-x86-ENU.EXE Windows2000-KB958644-x86-ENU.EXE Windows2000-KB958687-x86-ENU.EXE Windows2000-KB960715-x86-ENU.EXE Windows2000-WindowsMedia-KB952069-x86-ENU.exe WindowsInstaller-KB893803-v2-x86.exe WindowsMedia64-KB954600-x86-ENU.exe WindowsMedia6-KB925398-v2-x86-ENU.exe WindowsMedia9-KB936782-x86-ENU.exe WindowsMedia-KB911564-x86-ENU.exe WindowsUpdateAgent30-x86.exe wmfdist.exe wmp6cdcs.exe
-
okram98pive - I think you nailed it on the head. I'm assuming that there is some hotfix out there where strmdll.dll is version 4.1.0.3936. The filedate of that file is newer than the one in the troublesome hotfix. There is already code in the script (line 1369) that copies things over from the wm41 folder. Things will need to get modified somewhat to force copy it instead. Can someone determine what hotfix has strmdll.dll version 4.103936? Funny story. When I first wrote hfslip it was fun. Now it's more of a job. I want to quit this job.
-
I think OE and IE are tightly knit together, but I could be wrong. Perhaps you can use xnews for newsgroup reading and posting. It's free and free of dependancies, and most of all it's not tied to IE to automagically launch stuff you don't want.
-
Active desktop is one of those IE things. IIRC, Fred's site mentions that active desktop is killed.
-
I'm lost on this one. Perhaps you can just add in a line in hftools\hfanswer.ini that has this entry: LCIDD=1032 It may work, then again it may not. Sorry not much help here.