
tommyp
PatronContent Type
Profiles
Forums
Events
Everything posted by tommyp
-
I'm not sure if you can use FDV's fileset to remove IE and then install IE6 afterward. I suppose you can try it and see what happens. I would say that you need to make a decision if you want IE5, IE6 or no IE at all. If you do not want IE at all, then use FDVs fileset. If you want to keep IE5 or if you want IE6 slipstreamed instead, then visit Tomcat76's dynamic hotfix list for what file goes where.
-
I think XP has a wonderful special feature that if you have mapped drives where the letters start just one letter higher than your internal hd/cd drives, USB sticks don't work. I found that by mapping to an alternate letter, things work normal. This issues does not happen with 2k.
-
Nlite is easier because of its GUI, but needs .net. Hfcleanup has no GUI, but is trickier and doesn't need .net. The goal of HFSLIP is to not use .net, which also means no GUI. Unfortunately, you can't have the best of both worlds. Both nlite and hfcleanup are modular so to speak, so it's all about the level pain you want to deal with and how much time you want to spend by stripping down 2k. FYI, hfcleanup is very buggy with XP, but it works great for me with 2k. I use hfcleanup all the time with my 2k boxes, the iso is about 120 meg with ie6 core, dx9c, all my codecs, all my tweaks and icon swaps. Without codecs/tweaks/icon swaps the iso would be somewhere in the 95 meg vicinity.
-
Although it's not the right thread, I'll answer this. When visiting WU or the website you mention, various files are checked for revisions and even if they exist. So with removing components with NLITE you'll be missing components causing some flags to be raised. You're best bet would be to slipstream all updates and don't NLITE it. Install the full blown sourcess folder on a VM and check for updates and iron out any issues. If all is OK, then proceed with NLITE on the sourcess folder. If you want to discuss this further, please open a new thread.
-
oao - FDVs fileset removes IE completely in 2000, so it looks like it's not an option. There is something called hfcleanup, which is listed as a hyperlink on the main thread of this forum. The hfcleanup, although buggy, *may* work for what you want to do. To make life easier, I would suggest using NLITE to reduce your source. It's far easier to remove components, it shows some OS dependencies and IMHO NLITE is mature at this point. Prior to using NLITE, run HFSLIP with all the updates per Tomcat76's list. With TC's list, you'll see what files are required to slipstream IE6 and DX9C. Once you get a successful HFSLIP run, run NLITE on the sourcess folder.
-
http://www.microsoft.com/technet/security/...n/ms07-017.mspx
-
How are you checking for these discrepancies? Are you using an old outdated mssecure.xml file? Are you googling old windows updates on the web? The MSBLA will guide you the right direction for applying the latest and greatest updates. As far as some hotfixes you list..... Here is an interesting finding while searching the boards for hotfix 896422 - link. For KB912812, an cumulative update to IE6 released April 2006. Each month last year, IE6 had a cumulative rollup. 912812 is 12 updates behind at this point and it would be unwise to slipstream it. I can probably answer for the_guy with his hotfix lists. He concentrates on critical updates and not recommended updates. Tomcat76 includes some recommended ones and some fixes that are nice to have, xml stuff falls into this category.
-
Read the FAQ at HFSLIP.org or any of the stickies on this forum.
-
HFCleanup and XP don't mix well. Those cleanups need lots of work to make it XP friendly.
-
If you are talking about the file ShowDesktop.cmd, it creates a "%userprofile%\application data\Microsoft\Internet Explorer\Quick Launch" folder and then creates a show desktop icon in that folder. This file creates the folder early in the process that affects the default user. I have mine in the HFSVCPACK folder. Why did I create this? Well, if you remove some parts of IE, that folder isn't created (I think). That folder needs to be present if you want to do any any reg tweaks that pertain to that area. If the folder isn't there, and you try to do quicklaunch reg tweaks, nothing will happen because the folder isn't there.
-
The HFEXPERT\CODECS folder will work fine if it's registratable.
-
* This is not an HFSLIP issue. There was a non-critical MSFT update for 100% svchost.exe probs. Sorry I don't a link or the KB number, but it was mentioned a few weeks ago on some MSFN board.
-
RBCC - Before going wild with hfexpert and the svcpack folders, you should aim for getting a successful run with just the HF folder per Tomcat76's prescribed dynamic hotfix lists. Once you get that working, then put in the hfexpert/etc folders.
-
RBCC - I would suggest that you do two things. First, I have to reiterate supermagician's recommendation for you to review Tomcat76's dynamic hotfix list and make sure that only those are in the proper folders. Once you get a successful HFSLIP run with that, then add in the HFEXPERT and add ons. As Kiki discovers once in a while, there are bad addon's out there that just don't work (and mess up HFSLIP runs). Sometimes you gotta walk before you run.
-
You probably want to check your HF folder again, you have IE6.0sp1-KB905495-Windows2000-x86-ENU.exe and scripten.exe in there which are ie6 specific. You should only slipstream files meant for your OS. Tomcat has a dynamic list of all updates required for your run. How fast are you burning your CD? If you have bad media, you'll be missing files. In fact, just last week I had a bad burn which had the missing file errors. Once I reburned the sourcess folder, all was OK.
-
Did you select Y to filter FDV's setup files when you ran HFSLIP? Did you do a CD installation? How fast did you do your burn? It sounds to me like you got a bad cd burn, you should burn slower. Side note, you should check up on your HF directory, you have IE6 updates in there (they aren't needed). You should refer to Tomcat76's list of files required.
-
Are you using hfcleaupup? Are you using any icon tweaking programs? Maybe you're using Bugs Bunny's method of icon swapping with ICL files? Can you post your hfslip.cmd file from sourcess\i386\svcpack? Can you post your hfslipwu.inf file from sourcess\i386? Sorry about all the Q's.
-
I'm testing this out on a VM. I placed the dll file in the win\sys32 folder and typed in regsvr32 rpl2k.dll and I get an error window. I'm using a slim version of 2k with an IE6 core and dx9c slipstreamed. DllRegisterServer in rpl2k.dll failed. Return code was 0xffffffff Are there file dependencies for this DLL? Do I need to use a full blown installation of 2k to run this?
-
I found out that the order of entries in the winnt.sif file really doesn't matter. As long as the header section is correct. You probably want to read this or use the deploy program that is part of the admin tool pack on the cd.
-
Yes, you can place the winnt.sif in the FIX folder. If you prefer, you can place it in the source\i386 folder. Either way, it's the same effect.
-
There is a little program that may be worthwhile to aid this project. It's called transparent icons. Basically it gets rid of the boxes around the text of your desktop icons and leaves the text intact. You can download it here. This program uses very little resources. Hope this helps.
-
the_guy - if you have a slipstreamed source, there is typically a SP#.CAB, where the # is the service pack that is slipsteamed. The SP#.cab files have some binaries that are updates of the driver.cab binaries. With 2k, some of the dx9 binaries have to get packed in the driver.cab. Sometimes, there are hotfix binaries that have to get packed into the driver.cab too. Perhaps there is a workaround to create an optional hfslip pre-processing script to merge the sp#.cabs and driver.cab. If a hotfix and/or hfexpert drivers needs to get added during the normal hfslip process, an spx.cab will be created. Whattaya think? TC?
-
Sorry, I can't test out the fix. I'm out of town for a week.
-
TC - The hfslip.cmd inf processing doesn't work in the test release, but it works fine in the latest final. In the beta, the INF doesn't process, the only thing I get is an error window (and an INF that doesn't process). I never really understood why sometimes it's setupapi and sometimes advpack. But, if it ain't broke.....
-
I don't think those are the same INF files. The INF files I was talking about are the ones in the svcpack folder. These are launched via hfslip.cmd, also in svcpack. All of my hfslip###.inf files are working correctly. Open your hfslipwu.inf and see if something looks like this: [ROROE] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZA","200",0,"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %10%\HFSLIP\HFSLP200.INF,DefaultInstall" ... all of that was supposed to be one line