fdv

You could try deleting the contents of the prefetch too.

Heh Windows Error Reporting is not a dependency as such. Try this again with FILEMON and forget this dependency walker; it will mislead you. TRUST me on that one. Run filemon, select filters, uncheck successes, click OK, and then relaunch MP9 and see what's actually failing. WER.DLL is not actually needed for MP9 to work. (Because MP9 works for me and my dozen systems and I don't have WER.DLL, before you ask). The IE shim is neither here nor there; it's a legacy for launching media within IE. And for God's sake get rid of all that extra DX9 stuff in cabs. I examined the log but I don't see anything obvious, so try the FILEMON bit.

Honestly I think if people studied my files for 2k and xp they'd find a goldmine. Tiny example: nLite leaves files in SYSTEM. Solution: open SYSSETUP.INF, scroll to [Files.Install.CleanInstall] and put ONLY this line: CopyFiles=Files.System If you like, delete all of those files under [Files.NoWin31.System32ToSystem] Another example: the HIVE*.INF files are filled with petabytes of useless, outdated information (okay not that much, but you get the idea). You can cut out obsolete data by editing the heck out of them. nLite does this to some degree, but there's always more to add. Also, a lot of tweaks that nLite adds can be added here, and timezones are in HIVESFT, so why not fix them permanently? Another, while I'm at it: you can set windows permissions in DEFLTWK.INF so that all of those un-deletable directories can be deleted. You can also disable prefetch by denying system permissions to it. etc etc.

modify TXTSETUP or add them in an $OEM$ configuration.

PMikeP see the other topic you posted in for that list of components. buggyprog re-download the fileset. chefken the only time you would get this is if you also eliminated mini-filters, like if you were using TommyP's reducers as well. Avira is confirmed to work with my fileset (on the second install -- blame Avira for having crap dependencies). nh_wzg I will check on these

Tom's got the right answer. As for reg tweaks, give my HIVE*.* files a try. They have a zillion tweaks already in them, and they cut out a LOT of crap that nLite doesn't. My fileset is compatible with driverpacks so that's what I recommend for people there. Give my set a try as well as nLite and compare functionality and installation size. In a VM, this is easy to do and will tell you what you're better off doing. So FWIW, here are the items that can be removed in XP, if you haven't done it already. Remember... My name is in the nLite credits for a reason I know what nLite removes, I am kinda looking for -new- things. As I look through this list I see that there are indeed things I do not and would never remove... and I'll tell you why for each. Communication tools Comtrol Test Terminal Program Connection Manager - I don't recall FrontPage Extensions H323 MSP Internet Connection Wizard Internet Information Services (IIS) IP Conferencing MAC Bridge MSMail and MAPI MSN Explorer Netmeeting NetShell Cmd-Tool Network Diagnostic Network Setup Wizard - various dependencies NWLink IPX/SPX/NetBIOS Protocol Peer-to-Peer Share Creation Wizard Synchronization Manager TAPI Application Support TCP/IP Version 6 -- this is 221kb. Vector Graphics Rendering (VML) Web Folders Windows Messenger Blaster/Nachi removal tool Disk and Profile Quota -- these add up to 500kb Document Templates DR Watson -- this is an ENORMOUSLY helpful file and it's only 45kb Extensible Storage Engine (Esent97) FAT to NTFS converter -- 26Kb Help and Support IExpress Wizard -- this is very useful and it's only 112kb Manual Install and Upgrade -- see note MS Agent MS XML 2.0 Private Character Editor Remote Installation Services (RIS) -- see note Search Assistant Security Center Shell Media Handler - Adobe CS4 dependency Symbolic Debugger (NTSD) Tour User account pictures Visual Basic 5 runtime Web View You might be tempted to think that some components are bigger than they are simply because they're listed -- not true. Sure, FAT to NTFS seems trivial, but look how small it is! What if you want to recover data on a legacy system? 26Kb is a small price to pay for this 'what if'. Manual install and RIS: RIS doesn't install by default on the HDD. This is in nLite to delete the files from your CD. Manual install would kill DOS-based installs and I actually have users who do that -- they install from another HD instead of the CDROM. That 44Mb you see in nLite also reflects files on the CD that do not full get copied to HDD -- so you're not keeping 44Mb of garbage. Disk and profile quota -- I use my fileset in an office environment, and others do as well (or used the Win2k set, I don't know about XP yet). Anyway, 500Kb is pretty small to retain a feature that some admins might want. Same for Remote Registry Service: try using the Winternals PS utilities on remote systems without it. The Adobe CS4 has several crap files it requires, so I put them in OFF2007.INF (I am going to change the name of that). Anyway you control that the old fashioned way -- in SYSSETUP under [infs.Always]. Although IE installs by default, it's in there too -- easy to comment out with one semicolon. As for services, I killed a bunch after reference checking them on Blackviper's site. If any others can TRULY be removed, let me know. Open AXANT5.INF and have a look under [addreg.services]. Those are service stoppers. (Some services are totally removed, like indexing. I don't want to type an explanation why for the next 45 minutes, but the "indexing service" in search might say enabled when it doesn't exist. If you add the reg key for it not to start, it would appear in the list of services (again, when it's not even on the system).

This is/was the INF I wrote for Win2k. Save as an INF, etc etc etc etc etc. You will have to add the boot time defrag reg key value. I don't recall what that is offhand but it's an easy enough search on the net. I cannot guarantee that all of the files will be the same for XP but I think it's probably a pretty sure bet. [Version] signature="$Windows NT$" ClassGUID={00000000-0000-0000-0000-000000000000} SetupClass=Base LayoutFile=layout.inf [DestinationDirs] files.add.sys = 11 [DefaultInstall] UnregisterDlls = unregister RegisterDlls = register RenFiles = files.rename CopyFiles = files.add.sys,files.add.win DelFiles = files.del.sys,files.del.inf,files.del.help,files.del.win AddReg = keys.add DelReg = keys.del ProfileItems = DefragInstallItems ;Reboot ; this will prompt you, not do it automatically [DefaultInstall.NT] UnregisterDlls = unregister RegisterDlls = register RenFiles = files.rename CopyFiles = files.add.sys,files.add.win DelFiles = files.del.sys,files.del.inf,files.del.help,files.del.win AddReg = keys.add DelReg = keys.del ProfileItems = DefragInstallItems ;Reboot ; this will prompt you, not do it automatically [SourceDisksFiles] dfrg.inf = 1 ; this file dfrg.msc = 1 dfrgfat.exe = 1 dfrgntfs.exe = 1 dfrgres.dll = 1 dfrgsnap.dll = 1 dfrgui.dll = 1 [files.add.sys] dfrg.msc dfrgfat.exe dfrgntfs.exe dfrgres.dll dfrgsnap.dll dfrgui.dll [unregister] [register] 11,,dfrgsnap.dll,1 11,,dfrgui.dll,1 [files.rename] [files.add.sys] [files.add.win] [files.del.sys] [files.del.inf] [files.del.help] [files.del.win] [files.del.prog] [files.del.desktop] [keys.add] HKCR,"Drive\shell\Defrag",,0x00000012 HKCR,"Drive\shell\Defrag\command",,,"mmc.exe /s ""%11%\dfrg.msc""" HKLM,"SOFTWARE\Microsoft\Dfrg","FreeSpaceErrorLevel",0x00000000,"15" HKLM,"SOFTWARE\Microsoft\Dfrg","PathName",0x00020000,"%systemroot%\system32" HKLM,"SOFTWARE\Microsoft\Dfrg","ResourceDllName",0x00020000,"%systemroot%\system32\DfrgRes.dll" HKCR,"CLSID\{80EE4901-33A8-11d1-A213-0080C88593A5}","",0x00000000,"Defrag NTFS engine" HKCR,"CLSID\{80EE4901-33A8-11d1-A213-0080C88593A5}\LocalServer32","",0x00000000,"DfrgNtfs.exe" HKCR,"CLSID\{80EE4902-33A8-11d1-A213-0080C88593A5}","",0x00000000,"Defrag FAT engine" HKCR,"CLSID\{80EE4902-33A8-11d1-A213-0080C88593A5}\LocalServer32","",0x00000000,"DfrgFat.exe" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\DefragPath",,0x00000010 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\DefragPath","",0x00020000,"%systemroot%\system32\dfrg.msc %c:" [keys.del] [DefragInstallItems] Name = "Disk Defragmenter" CmdLine = 11,, dfrg.msc SubDir = "Accessories\System Tools" WorkingDir = 11 InfoTip = "Defragments your volumes so that your computer runs faster and more efficiently." IconPath = 11,,DfrgRes.dll IconIndex = 0 [Strings]

You'll have to settle for an alternate using HFSLIP. Method one, method two Or use nLite

If that doesn't do it, add to keep: scardssp.dll sccbase.dll sccsccp.dll slbcsp.dll slbiop.dll wmasf.dll wmidx.dll

What file in this fileset controls its removal? open TXTSETUP and uncomment nusrmgr.cpl = 1,,,,,,,2,0,0 mshta.exe dependent, so you must have that installed too

PVU, this work is important -- thanks. I'd like to add it to my site, which already hosts XP and 2003. Tom has available an Excel spreadsheet for this. Or you can reformat any way you like... That's the privilege you enjoy when you take a list over! Muppet Hunter uses the Excel. I use a linear date format and mark obsoletes as I go. I hope that you will decide to convert the existing list and add to it!

I suppose in TXTSETUP, one could find console.dll = 1,,,,,,,2,0,0 and ADD: console.dll = 1,,,,,,,2,0,0 console.dll = 1,,,,,,,2,0,0,console.cpl Would make it auto. Wendy, I assume you are also scanning other DLLs for this "hidden" capability? (You don't want someone else to have all the glory do you?!

I don't see protecting the root here. I once contacted MS about doing this in Win2k and they didn't know!! WTH?! I know that copying Vista perms to XP does work only because I read it in a MS blog. Ohhh, that's pretty clever jaclaz!! Any link to the SYS file download? That looks awesome. Esp for recovery console!

I can't make any changes to the XP CD (as mentioned in my previous post) Sorry! I read too fast I guess I don't understand how my CD-ROM drive could not be recognized, given that I booted the laptop from the XP CD? Initial boot would work because of the BIOS recognizing it and handing it off, but once at filecopy it's up to Windows. Anyway without editing these files I don't know how to force things... Sorry man

Found it http://support.microsoft.com/kb/810903 Step #4, then substep #7, second to last para. You are of course going from ACPI to non, though it's written non to ACPI. You must -update- drivers not remove them. When I did this on my laptop (got sick of it shutting down ALL the time) I had to re-install the drivers for all of my devices, including built-in Windows drivers for such things as monitor and hard drives... just so you know. Took me 15 minutes to get up and running again.

Edit TXTSETUP. It will take me about 6,000 words to explain further, so it's best to look at mine and compare the non-file copy sections with your own TXTSETUP and LAYOUT files. http://www.vorck.com/windows/data/fdvfiles-xp.zip Scroll to the [strings] section You will see cdname = "Windows XP Professional CD-ROM" cd2name = "Windows XP Professional CD-ROM" spcdname = "Windows XP Professional CD-ROM" productname = "Windows XP Professional" cdtagfile = "\win51" cdtagfilei = "\win51" cdtagfilem = "\win51" spcdtagfilei= "\win51" cd2tagfilei = "\win51" Note that I changed everything to \win51. That's the key right there. You'll see some other neat stuff too. You also should edit LAYOUT (don't worry, this applies to XP too): 1. go here: http://www.vorck.com/windows/2ksp5.html 2. scroll to step 14 3. start reading at "TXTSETUP.SIF and LAYOUT.INF file "protection." " There is a strong possibility that your CDRom drive is not being recogzied too of course, in which case we'll need you to slipstream the drivers into TXTSETUP manually. (I probably don't need to explain that, I don't think; that's a very popular topic here at MSFN)

Yes, I don't have time to type it out, but in My Computer hardware properties, you will see an ACPI BIOS. Change it to non-ACPI. I'm sorry, I have posted the longer answer here in this forum a while back; I don't have the time tonight to dig it up (I normally don't mind)

and if you do want to spoof, open HIVESYS and find or add keys: HKLM,"SYSTEM\CurrentControlSet\Control\Windows","CSDVersion",0x10001,0x300 ; service pack HKLM,"SYSTEM\CurrentControlSet\Control\Windows","CSDReleaseType",0x10001,0 ; 1 shows build num.

Sure. Expand, and have a look in, DEFLTWK.INF You will see security descriptor permissions for root, as well as all other windows directories. You can even do clever stuff like deny system write to certain directories, or open them up so that the undeletable can be deleted easily by you. Of course, this is only for new installs. It might help also to copy Vista or 7 permission data from their security files to XP's. I have never done that. But I have edited DEFLTWK.INF and I know it works to my satisfaction. I think this might help you: ;--------------------------------------------------------------------------------------- ; Descriptors ;--------------------------------------------------------------------------------------- ; A - ACCESS ALLOWED ; D - ACCESS DENIED ; OA - OBJECT ACCESS ALLOWED: ONLY APPLIES TO A SUBSET OF THE OBJECT(S). ; OD - OBJECT ACCESS DENIED: ONLY APPLIES TO A SUBSET OF THE OBJECT(S). ; AU - SYSTEM AUDIT ; AL - SYSTEM ALARM ; OU - OBJECT SYSTEM AUDIT ; OL - OBJECT SYSTEM ALARM ;--------------------------------------------------------------------------------------- ; CI - CONTAINER INHERIT: Directories inherit the ACE as an explicit ACE. ; OI - OBJECT INHERIT: Files inherit the ACE as an explicit ACE. ; ID - ACE IS INHERITED ; NP - NO PROPAGATE: ONLY IMMEDIATE CHILDREN INHERIT THIS ACE. ; IO - INHERITANCE ONLY: ACE DOESN’T APPLY TO THIS OBJECT, BUT MAY AFFECT CHILDREN VIA INHERITANCE. ; SA - SUCCESSFUL ACCESS AUDIT ; FA - FAILED ACCESS AUDIT ;--------------------------------------------------------------------------------------- ; P - Inheritance from containers that are higher in the folder hierarchy are blocked. ; AI - Inheritance is allowed, assuming that "P" is not also set. ; AR - Child objects inherit permissions from this object. ;--------------------------------------------------------------------------------------- ; GA - GENERIC ALL ; GR - GENERIC READ ; GW - GENERIC WRITE ; GX - GENERIC EXECUTE ; *********************** Directory service access rights ; RC - Read Permissions ; SD - Delete ; WD - Modify Permissions ; WO - Modify Owner ; RP - Read All Properties ; WP - Write All Properties ; CC - Create All Child Objects ; DC - Delete All Child Objects ; LC - List Contents ; SW - All Validated Writes ; LO - List Object ; DT - Delete Subtree ; CR - All Extended Rights ; *********************** File access rights ; FA - FILE ALL ACCESS ; FR - FILE GENERIC READ ; FW - FILE GENERIC WRITE ; FX - FILE GENERIC EXECUTE ;--------------------------------------------------------------------------------------- ; AO - Account operators ; RU - Alias to allow previous Windows 2000 ; AN - Anonymous logon ; AU - Authenticated users ; BA - Built-in administrators ; BG - Built-in guests ; BO - Backup operators ; BU - Built-in users ; CA - Certificate server administrators ; CG - Creator group ; CO - Creator owner ; DA - Domain administrators ; DC - Domain computers ; DD - Domain controllers ; DG - Domain guests ; DU - Domain users ; EA - Enterprise administrators ; ED - Enterprise domain controllers ; WD - Everyone ; PA - Group Policy administrators ; IU - Interactively logged-on user ; LA - Local administrator ; LG - Local guest ; LS - Local service account ; SY - Local system ; NU - Network logon user ; NO - Network configuration operators ; NS - Network service account ; PO - Printer operators ; PS - Personal self ; PU - Power users ; RS - RAS servers group ; RD - Terminal server users ; RE - Replicator ; RC - Restricted code ; SA - Schema administrators ; SO - Server operators ; SU - Service logon user While you're here, be kind and let users change the time when it's wrong: SeSystemTimePrivilege = *S-1-5-32-544, *S-1-5-32-551, *S-1-5-32-547, *S-1-5-32-545, *S-1-1-0 Let's disable Prefetching, in conjunction with the registry edit: "%SystemRoot%\Prefetch",2,"D:PAR(D;;FAGAGRGWGXWD;;;SY)" ; DENY system Let's make a few useless directories easier to delete after installation: "%SystemDirectory%\ias",2,"D:P(A;CIOI;GA;;;WD)(A;CI;GA;;;WD)" ; allow world "%SystemDirectory%\oobe",2,"D:P(A;CIOI;GA;;;WD)(A;CI;GA;;;WD)" ; allow world "%SystemDirectory%\inetsrv",2,"D:P(A;CIOI;GA;;;WD)(A;CI;GA;;;WD)" ; allow world etc etc.

From http://www.vorck.com/windows/about.html "In 1997, I modified some INF files in Windows NT and got it to install without Internet Explorer (it was IE version 2 at the time). In December 2001, I wondered what would happen if I modified Windows 2000 INF installation files to prevent Internet Explorer from being installed, added the modified INF files to a service pack, and then slipstreamed the result (at the time, it had to be done in that order to avoid digital signature errors). The process such as it was then was hosted by a guy named Shawn (anon) in November, 2001." At that time, I did not hack any DLLs! The SETUPAPI.DLL mod came courtesy of a developer in Russia who wished, and still wishes, to remain anonymous. He literally kept giving me hints until I got it straight. You will note that nLite uses a different DLL, which came courtesy of a French dev named 7imo, who appears to be gone now (nLite used to use my mod WAY back; 7imo's was original and a slight bit cleaner for technical reasons too long to explain right now). To get into what files do what, you need to have known and used Windows 3.1 all the way forward. That's how for example I know that all the files in SYSTEM (not 32, just SYSTEM) could be removed. You need to know that files starting with OLE2 are obsolete technology from the 90's. You need to expand INF files and see what files are associated with what processes. For example, open up IIS.INF. What a mess! Scrapping those made install go faster. For more INFs to look into, visit http://www.vorck.com/windows/2ksp5.html and scroll to Step 15. Also, when you use something on a Windows system, you can run FILEMON to see what DLLs it uses. And sometimes, you just need to try stuff. Like OEMBIOS in XP -- I said 'what the heck' and installed without it and discovered both what it actually is (I don't really feel comfortable saying it publicly what it is really used for) and why most systems don't need it. And, you have no idea how much isosizing Tom and I have done just testing stuff.... Trying to install Windows without Active Directory. I've done it. Without -any- encryption support. Done it (Windows was unbelievably slow). Without any MDAC support (many programs won't work). My list of failures is both unpublished (not worth anyone's time) and that list of failures is longer than my list of successes -- I learned a lot, in other words. Server 2003 was easier than you might think. Once you've fiddled with XP, you know the media junk in 2003 is easy to spot, and the R2 stuff was pretty much nonessential to most people's use of Server. (Who really needed connectivity DLLs for Unix that didn't work with Linux anyway, and besides, *nix has the FAR better and constantly developed SAMBA). On November 16, 2004 TommyP sent me the following message: "I posted a message the other day (with little fanfare), but I think it's right up your alley. Basically, it's a batch program that slipstreams all the hotfix binaries, so you don't need to do anything manually." Everything kinda got kickstarted at that point. When TP and I exchanged notes, it was like pouring gas on fire. Trivia: there was one time when both TP and I stayed up 24 hours IIRC working on a feature, and that was DRIVER.CAB integration with the SP?.CAB. So, in short, I did not use any tools. Just slow INF examination, FILEMON, registry combing, HIVE*.INF analysis, and help on a key DLL from an anon Russian. In fact, if you have a peek in the nLite credits box, you'll see my name. There's a reason for that

nh_wzg Because they (simplified Chinese) come from the LANG directory on the CD and probably the file pointer numbers in TXT... and LAY... are either wrong or were deleted. Just a guess. I can't recall. I did a much more logical job in my XP fileset. AGT* is Agent... There are a lot more! All of your Simp Chi files may be found in INTL.INF. Once you get them you can add them permanently. PROBLEM Direct X -is- installed. Make sure HFCABS is correctly populated. I never removed DX at any point.

If that´s true, I guess my days with HFSLIP are over even before the beginning... Either I played to a troll, or I am just not cutting it as a source of help here. I give up. Edit: made infinitely more polite

The SVCPACK directory has CATalog files for digital signature checking. There are dependencies here. If you really wanted to get rid of them, you would need to shut off digsig checking (using my SETUPAPI.DLL in my fileset, or using SYSSETUP.DLL in nLite) and edit the HF*.INF files to ensure no CAT dependencies. This is quite a bit of work for 49 CAT files that add up to less than 600 kilobyes. If you really want to save space use my fileset (and don't forget to delete INTL.INF in my fileset before you run HFSLIP so you get languages). Or use HFCLEANUP or nLite.

It's okay, it's just that this crowd (I'm one) believes that he best, most optimal space saving way to do it is direct slipstreaming for NEW installs. Welcome aboard, by the way. There is no real problem and you do not need to do anything to your existing install. It's just that using /integrate on a NEW install is a sloppy, inefficient way to do it. Whatever you do, don't go deleting CAT files, config data, or hotfix info on your existing install.

Ohhhhh. Dude. I love you, man. Rock on.