fdv

Quick question... I posted a while back about thinning out the registry. It gets packed with garbage when DLLs install. Has anyone gone through the registry and made note of keys that are just garbage? For example, if ripping out DHTML, there is no point in keeping its keys in the Registry. But its keys don't amount to five or six... There are HUNDREDS. In Win2k alone, my files manage to save me about 10mb in my registry. XP's probably got even more to save. For example... One would need to export the registry, open the file in Word, cut out the group of DHTML keys, clean it up a little, then write an INF to delete them (or supply me with the list of keys, and I could do it, but INF writers are probably a dime a dozen around here ) The task would be repeated for all useless key sets. Once you find the first one, the rest tend to be in increments of one, so once you find one, the others are always right behind. I guess what I'm asking is this... Has anyone thought of an XP Registry Thinner?

@kukris - please post these for tommyp when he gets back your [DRIVE]:\HFSLIP\SOURCE\i386\prodspec.ini the filename of any of your Type 1 hotfixes whether or not your win2k already has sp4 slipstreamed There is a new version coming that will change folder structure a little bit. you might want to wait until it's released, because you might have a little better luck with it. it will be up by week's end. @outatouch - your q's will be answered in the documentation for the next version. we'll be making this whole 'unattended install' thing a bit clearer. @all - we're going to need a "situation tester" for the next version. it won't be beta testing since you wouldn't be working with beta software, but with the current release. what we'd like to know for purposes of documentation is "what happens when you try to install an HFSLIP'ped Windows from DOS?" I'd like to know about: Windows 2000 with slipstreamed dx9 Windows 2000 with slipstreamed ie6 Windows 2000 with slipstreamed dx9 and ie6 This is a "be ready for me to ask" post -- there is no need to reply. When the next version is released, I'll post again asking this.

@outatouch - no, hadn't addressed this post yet, but let me say that documentation will soon change. as for the problems you describe, well, you should retest using the next version, due by week's end. things change enough so that whatever bug is happening might not in the next version.

hi folks just got back from a few days away, some VERY quick answers @saugatak - i always had to keep other languages in due to users from other countries, so i never did the research as to which files are which codepages (in other words, which files are which languages). nlite is better for this kind of thing. my fileset started its life long, long ago in 2001 and it was more popular with users from places like italy, germany, russia and such than in english speaking places, so i never went ahead and removed languages. @vci - my fileset is totally incompatable with nlite. nlite runs a scan to see what OS its dealing with and does some spot checking of other files as well like dlls. since my files are modded, it throws nlite off. compatability is not something nuhi or i ever shot for since we developed parallel projects in different ways. since we both remove bloat, our projects will never work together, because they try to edit the same files. now, on a related item, you say you were not able to get my "plain-fileset + hotfixes to work." give me some more info and i'll see what's what... because my fileset is (as far as i know) totally compatable with a fully slipstreamed and hfslip'ed win2k. what mods did you have to make? let me know. i'll be back in a few hours after i get some sleep...

@saugatak - You will be working in the files in FDVFILES for this: open syssetup.in_ and find [Accessories] %cmd% = cmd.exe,cmd.exe,cmd.exe,0,%cmd_infotip% %notepad% = notepad.exe,notepad.exe,,0,%notepad_infotip% Put a semicolon in front of notepad, then find [Infs.Always] [....] dfrg.inf,DefaultInstall Put a semicolon in front of it Save Open TXTSETUP and LAYOUT and comment out: defrag.chm = 1,,,,,,,21,0,0 defrag.hlp = 1,,,,,,,21,0,0 [....] dfrg.inf = 1,,,,,,,20,0,0 dfrg.msc = 1,,,,,,,2,0,0 dfrgfat.exe = 2,,,,,,,2,0,0 dfrgntfs.exe = 2,,,,,,,2,0,0 dfrgres.dll = 1,,,,,,,2,0,0 dfrgsnap.dll = 2,,,,,,,2,0,0 dfrgui.dll = 1,,,,,,,2,0,0 [....] notepad.chm = 1,,,,,,,21,0,0 notepad.exe = 1,,,,,,,2,1,0 notepad.hlp = 1,,,,,,,21,1,0 using semicolons in both files. (The lines above were taken from TXTSETUP just for illustration.) Some notes on defrag (applies to all versions of Windows) I don't know what this will do -- probably nothing except install without Notepad and Defragger -- but I just have to make the standard "here's how to do it but I don't know if it will make your cat die or cause an unemployed circus midget to chase you with a broadsword" disclaimer. There is, of course, nLite as well for component removal. My way was developed as a tutorial and the files are only designed for things nearly everyone who hates IE wants to remove. Removing the built in defragger is not a common request nLite lets you be more flexible about it.

@saugatak - to answer #1, no, this will unfortunately not take both items from the start menu. The start menu is populated by SYSSETUP.INF in the beginning of the file. Carefully scanning the start of the file, you will see: [StartMenuGroups] Accessories = %accessories%,0 Accessibility = %accessibility%,0 Startup = %startup%,0 StartupCommon = %startup%,1 AdminTools = %admintools%,1 Entertainment = %accessories_entertainment%,0 StartMenuCommon = %startmenucommon%,0 SystemTools = %systemtools%,1 What you want to do in this case it to also add semicolons to Accessories. As for optional components, I don't have my notes at the ready... But perhaps commenting out in SYSOC.INF as you have noted also takes care of its start menu. I forget for Accessories (and will be away from my comp for the weekend, so you might have to troubleshoot that one on your own via trial and error unless it suddenly comes to me As for issue#2. You correctly note that my page doesn't quite match my files... My page only shows those things for illustration. I leave the INF entries in and the files are actually emptied out, so they never actually install. I did this for two reasons: 1. I needed to add registry settings and files at various times, so I just "hijacked" Microsoft's INF files. If you check out IE.INF, it has all sorts of IE removal info in it. The other files are simply blank (I planned on using many of them but ultimately never did), but if I ever need to add something like registry keys or filecopy operations, I can slip it into one of these hollowed-out INFs. 2. It's a byproduct of the way I was working when I created the latest fileset. Sometimes I'd have hundreds of things open, and in order to see what I was leaving out, it was easier to have an empty INF in a directory to see what I'd removed rather than having to keep re-opening SYSSETUP. Ultimately, most of the files from these INFs under [infs.Always] get installed in TXTSETUP and LAYOUT, so I not only empty out their INFs, I comment their files out individually in those two files as well. You can freely comment out INF entries in [infs.Always] but MPLAYER2.INF and IE.INF should be left alone. (mplayer creates file type associations that are necessary, and IE normalizes the interface, adds interface tweaks, registers key DLLs, and guts the registry of IE junk). Makes no difference. Sorry for the confusion, I'll add a note to my page at some point about why the example's different from the file.

No, Microsoft versus Sun, MS lost.As part of the settlement they can no longer issue new versions of the MS Java Virtual Machine, which is no longer installed when you install a slipstreamed version after SP3, IIRC. MS can update existing versions, though. This fix from 2003 is a fix for the MS Java Virtual Machine file that was part of Windows Scripting as an IE extension and has been phased out. The file JSCRIPT.DLL is an MS file meant as a fix for systems that fit within this narrow category, where the MS JVM exists (as in Windows 2000 RTM): "Our settlement agreement with Sun allows us to make security fixes until January 2004. After that, our settlement does not allow us to make any changes to the Microsoft VM, even to fix critical defects or security holes." Source "Customers are encouraged to take proactive measures to stay informed about obsolete software and move away from the MSJVM in a timely fashion. The MSJVM is no longer available for distribution from Microsoft and there will be no enhancements to the MSJVM." (September 12, 2003, Updated: August 16, 2004). Source I understand, just giving background to others who may see and not understand the why's behind this issue.

Okay I gotta ask Tomcat76, why do you want to make Windows Update happy? It all boils down to an obscure legal decision with MS Java, and WinUpdate would replace the DLL in question with an earlier one not because it's better but because of the obscure licensing issue. Anyway, my larger point, not flaming, just asking... In one month MS will no doubt issue hotfixes and WinUpdate will complain again. What is this thing with making it happy? Just curious.

Tomcat76 glad to hear the reboot issue is resolved at least in terms of HFSLIP. Setup50.exe is, far as I know, an Outlook file. Sound, video, game controller error is a DX issue, and I can't imagine how it's related to setup50. expand setup50 and check its version and report back. i don't believe any of the rest of us are getting a DigSig error; this happens when MS thinks a file has been modified usually (to state the obvious). maybe if we supply you with a known good setup50 for ie 5 or 6, whatever you're using, it will take care of the problem... the more i think about it the more i believe it's corrupted. can't think of what scripten might have to do with it, either.

Great Grandma's Spatula, MS has done it yet again. And Tomcat76's 100% right, the IE downloads are unavailable. Nice. Maybe MS will just decide to issue to new rollup with these files. HA HA HA!! I kill me. Too funny. Imagine, such a sensible thing. Allright, just alerted TommyP. Keep your eye on this space.

Hey, I know this does not answer the question, but it will answer WHY this is happening. A DLL that is on the system keeps creating these folders. For example, have a look at the Windows 2000 versions of two DLLs here. The Internet Cache folders kept getting created in this case until I gutted the REGINST sections. Now, I can't tell you which DLLs are doing this in XP, because I don't know, but I would suggest getting Resource Hacker and going through ones you suspect (the core DLLs of the OS). Hope this puts you on the right track at least, and sorry I can't answer specifically.

http://www.msfn.org/board/index.php?showtopic=32125 Download and run HFSLIP Put the Windows Update hotfix in the HF subfolder, with all of your other Type 1 and 2 hotfixes Run it, done

samogon, I dont see a link to Rollup for Russian language. Can you give us a link?

Oleg_II - if you consolidate (for example) 10 hotfixes, and later, a bunch of hotfixes replace what you already have, you'll have the same problem again. In other words, picture this. You make a hotfix that has an IE rollup. Then, MS issues another rollup. And, say, they do this again and again and again for a total of six (Oh wait, Microsoft actually DID issue six IE hotfixes ). Your big, merged hotfix would just be obsolete over and over. tommpy actively analyzes hotfixes for what you need and what you don't. Of course I have zero doubt that tommyp could create a script that was a "Really Big Hotfix Creator" but as of right now there isn't all that much duplication in the hotfixes (and it would still be pretty big). While the script is running, the WORK (or is it WORKING?) directory has all the updated files; I suppose the process could stop and ask if you wanted to CAB them all into a Mighty Big Hotfix or if you wanted to go ahead and slipstream, but it seems kind of duplicative to me personally.

The quote 'shoulders of giants' refers to people who see a work and build on it. Yes, others have done it first, but it's impossible to prove who saw what. Personally, because I was around watching Jeremy and Fridge-raideR do their thing and saw it develop over time, I believe they are 'clean room.' I think they did it themselves and did not see anyone else's work, because as they worked, they made a lot of the same mistakes that would have been prevented if they had seen the solution at the outset. And they used file differences from nLite (yeah, I know, I said the dreaded word... nLite.) I removed IE from Windows 2000. Shane Brooks did too. No one in their right mind would tell Nuhi that he's standing on the shoulders of a giant. Just because someone else did it doesn't mean the thread starters are plagiarists. gdogg: Agreed gdogg. No one is congratulating themselves. That doesn't stop others from wanting to take a jab at us (between bouts of cleaning their toilet).

This should be a good start, in a general way: http://support.microsoft.com/default.aspx?...;300549&sd=tech

Whoops! Yeah <smacks forehead> Oleg_II, please include this in your WIINT.SIF file. Better yet please look at mine as an example.

Okay, tweakui 133 repacked as a Type2. Also, that stupid "everything stops until you close the displayed help screen popup" bug should be fixed. Get it here (tweakui.exe). edit: made a link rather than just listing url

Just a thought for both Oleg_II_ as well as TommyP In SOURCES, create $OEM$\$$\system32 In other words, make a new directory in SOURCES called $OEM$. Inside that, a new directory called $$. Inside that, a directory called system32. Inside that, put whatever programs you'd like. Here is a GREAT list of little programs I put in here! http://www.vorck.com/2ksp5.html#13 (and some of the programs from Step 12 above it) Works for me.

@Oleg_II - Dude I am sorry about the pagefile thing. You're right, I should let people know... but I'm going to take it back out, that's just unkind to throttle someone's shutdown process like that. Mea culpa. CHM files - here's the thing that I just discovered (and already fixed). It _USED_ to be that shdoclc.dll was the heart of Internet Explorer. Here's something embarassing for me... try typing a URL into an explorer location bar. Boom, the Internet comes up. Not so nice, huh? As it turns out, Microsoft has, with IE6SP1, integrated VASTLY more browser functionality into fewer files. Go here and scroll down to 'the stumble'. IE 5.x needed a LOT of files to run. Now, it only needs a few. Microsoft has been very busy consolidating browser functionality. With all of the IE files ripped out of Windows, as it turns out... MSHTML.DLL is now the culprit, not SHDOCLC.DLL any longer!! So, my latest fileset removes it (you can too, just have all apps closed, search for mshtml, and rename it .xxx or just delete it). You'll be IE free again, but the point is that MS is paring down the files needed to run IE. The HTML display DLL used to be just a small part of IE, not the core of it. Slow startup - I am not sure. My system starts up lightning fast. Please try a startup manager and report back to me via e-mail or PM just what you have loading at startup; this will help me figure things out. Outlook - thanks for testing it Pretty cool that it works (for those who need it) @TommyP - in reference to the problem that gzduke5 is having - a possibility. Maybe the problem is ActiveX killbits, and when he reinstalled, he overwrote new files with old files, and the old files do not have recognition for the killbit settings, effectively allowing all sorts of ActiveX controls to do their thing? In other words, nothing is wrong but MS's security settings are too high and the old, unpatched IE6 files allow any ActiveX controls through. Just a thought.

os2fan2 let me see a link to the latest one for Win2k (PM me if you like) and I can repackage it as a hotfix. I never did figure out which one was the "real" one recommended for use in w2k.

I'd say yes. Every $#@%$ing time I visit a family member and have to do a re-install, I want WFP to be ON so they can't screw it up so fast!!!

HFSLIP: Your alternative. "Windows2000: Slipstreams IE6SP1, DX9C, OE6, WAB6, IE6 type 1 and type 2 hotfixes, W2K type 1 and type 2 hotfixes, MSI type hotfixes, and the MDAC update. Support is available if you wish to install the "recommended" but non-essential updates such as DirectX9C, WMP9 and DotNet." "WindowsXP: Slipstreams Type 1 and Type 2 hotfixes, as well as MSI hotfixes. Also installs REG registry tweak files and silent installers such as DotNet, etc. Visual guide for Windows 2000.

[url="http://www.msfn.org/board/index.php?showtopic=32125"]http://www.msfn.org/board/index.php?showtopic=32125[/url] "Windows2000: Slipstreams IE6SP1, DX9C, OE6, WAB6, IE6 type 1 and type 2 hotfixes, W2K type 1 and type 2 hotfixes, MSI type hotfixes, and the MDAC update. Support is available if you wish to install the "recommended" but non-essential updates such as DirectX9C, WMP9 and DotNet." Does Win2k perfectly. (Also does XP and 2003, though we don't link to their hotfixes.) [url="http://www.vorck.com/data/hfslip.zip"]Download Total Slipstreamer here.[/url] For instructions on removing IE from this "super" win2k build, visit: [url="http://www.vorck.com/2ksp5.html"]http://www.vorck.com/2ksp5.html[/url] Cheers

HAHAAHAAHAA!! TommyP you've done it again. He said he would, folks, and I told him not to bother way back. I'd said that slipstreaming -- NOT integrating, but actually slipstreaming -- DirectX 9c was not worthwhile because it would take forever learning how to do it and besides, DX9 includes files not in DX7 (so it's more than just a replacement). Well sometimes I just need to be proved wrong Tested out the latest Total Slipstreamer for Windows 2000 and created the Win2k SP4 + Rollup + IE & OE 6 + DirectX 9c and it works perfectly. See the main change at my site here: http://www.vorck.com/2ksp5.html#6 Scroll a little bit and you'll see a pic of the files you need to add to the IE directory. And yes, it works with and without my IE removal files, and works whether or not you include IE 6. Oh, BTW, I should mention it has non-EN language support now. Bravo, man! B)