tommyp

The script wasn't tested on windows 7. The script does not work on Vista. The host PC OS could be the prob. I suppose you could attach the zipped hfslip.log for starters though. On a sidenote, there are no plans in the works for vista or win7 & hfslip compatibility.

Is this thread dead? Can I desticky it?

occache.dll has been discussed to death in this thread. The conclusion I get out of the messages is that it's a non-problem. My suggestions are twofold - don't use IE and don't open the setuperr.log file. LOL New M beta is up that addresses a w2k issue. Nothing changes in regard to xp.

You didn't do anything wrong. You found a bug. I missed some lines of code when redoing version G to L. Look for beta M.

WindowsXP-KB961373-x86-ENU.exe should be in the HF folder. After running the script, you should have quartz.dll version 6.5.2600.5731 in the sourcess\i386 folder (compressed). After installation, the same file should be in the system32 folder. If that's not happening for you, you probably have a corrupted hotfix & you should re-download it.

You need a bin file there too. If the hftools folder is populated as prescribed at hfslip.org and if your boot cd is in the drive, toward the completion of running the program, the bin file will be extracted from your bootable install disk.

New beta up. Hope this does the trick.

No. Here's the story in short form. I took what rhadamants did in the IE8 thread, trusted that the work was as advertised and used it as the newer beta. Following that, I rolled in the usage agreement changes. Now we're stuck with a script where the old version works for some things, and a new script that works for other things. So, this means I will go back to rev G, and manually put in the things that rhadamants suggested as well as re-roll the usage agreements changes to remake a new rev. So, for now, I am comparing code, line by line. I should be done in a day or two as long as real life doesn't get in the way. Lesson learned - don't trust anyone.

Something tells me that we'll just have to revert back to the G beta. The changes after G were from rhadamants. I was hoping that the changes made were only for IE8, but apparantly there were some other not-so-nice changes that I didn't catch. When I get some free time, I'll have to re-roll in the changes he suggested and repost a new beta.

Can you zip your txtsetup.sif & hfgui*.* & any CMD/INF files you have in your svcpack folder? This is really interesting.

jvidal brings up a very good point. Sometimes dlls can be registered, sometimes they can't. Perhaps someone has the same IE level as you have as on a regular non-hfslip'd machine? If they do, they can test to see if that troublesome dll really is registerable or not.

pr0fessor - please check to be sure your hard drive has plenty of space and/or proper cd burning media. If it means anything, I have not verified KB888111 on w2k, which could be cause of the whole prob. On a sidenote, you want to consider updating your hotfix list, you have plenty of old ones that are superceded.

Very strange, that part of the code hasn't changed in sometime, unless it's a fluke when IE8 was introduced (there were plenty of other not so nice codechanges when someone contributed a few months back). The hfguirunonce files should be copied to the sourcess\i386 folder. To eliminate non 8.3 filenaming file copy issues, the files are renamed with a HFGUI prefix and number suffix. The copied files aren't in the svcpack folder. Simply placing the HFGUIRUNONCE to the sourcess\i386\svcpack folder will not fix this issue. Are you sure that the renamed files aren't in i386? Can you confirm the problem is HFGUIRUNONCE or the HFSVCPACK_SW1/2?

This is good news. Does this mean that if you add the code below to the registry after T-13 (or later) then the SFC will be on? HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCDllCacheDir",,"%SystemRoot%\System32\Dllcache" HKLM,"SOFTWARE\Policies\Microsoft\Windows NT\Windows File Protection","SFCDllCacheDir",,"%SystemRoot%\System32\Dllcache"

geigs - please edit your post to zip the hfslip.log instead of full text. Thanks sabregreen - any luck troubleshooting the IE8? Is it acceptable to call those lines of code ONLY when IE8 is slipstreamed?

Sorry Martin. I had updated the 2k list a few weeks back to reflect your requests but didn't want to release them until I went through patch Tuesday's offerings. Patch Tuesday ended up being a dud & I forgot about giving the lists to FDV for posting. I just emailed FDV a few minutes ago with the lists.

I've just sent an update to FDV for the IE compatibailty update. The 929399 update has always been listed as a bugfix, which is neither critical nor optional. SOME systems require it, some don't. It's up to the user of the HF lists to decide what they want to slipstream. WMP is a buggy software to begin with, I don't see the point of using it when there are far better programs out there. Anyway, let's not get too wrapped around the axle with a bugfix, the intent of the HF lists (and this thread) is for critical updates that I have missed.

What's the sp5 fileset?

Can someone else verify KB929399? This is one of those fixes that go on and off the list. Besides, it's a bugfix that will typically not get reported as a critical update.

It failed because I haven't tested it, don't plan on testing it and don't plan on troubleshooting it. I don't have 2003 and don't plan on buying 2003 either. Sorry to say, but HFSLIP is in maintenance mode at this point. Sometimes real life gets in the way of sitting in front of this machine.

Check the windows updates thread that is stickied in this forum for what goes where.

My bad, try this line of code instead.. make a new line 382 and place there. BTW, when posting your hfslip.logs, please ZIP them instead. IF EXIST HF\IE8-WindowsS* FOR /F %%I IN ('DIR/B HF\IE8-WindowsServer2003-x*') DO SET IE8EXE=%%I&SET DefExcHF=%DefExcHF% \-win IE8

sabre - Thanks for the inputs. Have you verified your suggestion with all flavors of IE?

jvidal, I haven't tested it, but you can do a test run if you do some editing. Open the script, locate line 381 and insert the following code after it. IF EXIST HF\IE8-WindowsX* FOR /F %%I IN ('DIR/B HF\IE8-WindowsServer2003-x*') DO SET IE8EXE=%%I&SET DefExcHF=%DefExcHF% \-win IE8 (the above should be one line, not two as displayed) Report back your findings. tommyp

This probably won't help, but I'll offer my $.02. Try including Windows2000-KB827675-x86-ENU.exe in your HF folder. IIRC, it's a USB fix for the via chipset.