fdv

Removing IE core is going to cause problems with any Control Panel applets that need the MS HTML subsystem to display contents and/or work correctly. Add/Remove Programs is one example of an applet that won't display correctly, and user accounts is one that needs IE. Why IE core is affecting user account pictures I don't know, as I don't recall a warning in nLite about that. I think you might be able to right click on My Computer and select Manage and that will work, but I don't remember. In any case without IE core you will need some registry keys in place to trick most programs that look for IE -including- the Management Console. I don't remember if nLite does this though. I have them if you think you'd find it useful; shoot me a pm and I'll track that info down for you if you thin kit will help.

Also, someone should point out that removing Outlook Express will later cause problems with an MS Office install when you try to install regular Outlook. (I wrote an OE RE-installer that someone has linked in the 'what not to remove' thread, IIRC)

IE: Flash plugin needs reinstalling probably. Search: You'll have to solicit the reg keys for the search from an XP user. Give this a try Hope this works. Save as an INF and right click / install. The delreg section is the Dog Destroyer, if anyone wants to have that handy. xp_search.txt

This did! We needed a poll anyway. Grape Fanta and red wine... LOL

[reply] continue with 2

Which Grape Soda? I love Stewart's.

Sure. The main file you want is msimsp.exe, unfortunately only available to Windows Installer Developers in an SDK just for them. It also has a companion DLL, patchwiz.dll. That's what Gurgelmeyer used. I will bet you a can of Grape soda that you won't be able to find this, though.

Whoa, dude... next time put the word "solved" or something at the top because I was racking my brain trying to follow and troubleshoot in my mind as I read! Files in REPLACE should end up in the correct dir, it is not normal that they went into the root. But to save some trouble anyway, if you are POSITIVE that you want to replace the files, I personally would just go ahead and put them into the original SOURCES/I386 and replace the originals (maybe name the old ones .bak). I personally have done this with many files in my win2k. Something I just noticed, are some of those files in REPLACE not in 2k normally? As in, they are not all replacing existing files?

No -- it doesn't work like that. You have to comment out the individual drivers. BTW if you use MS or VMWare however, those "pretend" to use some older drivers, I forget which ones. So you cannot comment them all out and have it work in VMWare (I don't know if you are using VMWare).

brand new answers provided in thread in link #3.

FWIW, the fastest install that can take place will be achieved by: installing Unknown Device Identifier running it to get ALL of your hardware device strings opening TXTSETUP.INF scrolling to [HardwareIdsDatabase] put in all of your device strings, edit the driver files accordingly Open SYSSETUP.INF scroll to [DeviceInfsToInstall] remove INFs for devices you don't have. for example: mchgr.inf (media changer -- trust me, you don't have one) 1394.inf -- Firewire tape.inf -- tape drivers netirsir.inf -- Infrared devices pcmcia.inf -- laptops only battery.inf -- laptops only etc etc etc etc etc etc here are the devices from win2k's TXTSETUP that the WinXP TXTSETUP does not have. in other words, support for these was removed from xp... this probably means that it would be very rare for you to encounter any of these: cpqfws2e = cpqfws2e.sys,4 ; XP doesn't have cpqarray = cpqarray.sys,4 ; XP doesn't have cpqarry2 = cpqarry2.sys,4 ; XP doesn't have ncrc710 = ncrc710.sys,4 ; XP doesn't have buslogic = buslogic.sys,4 ; XP doesn't have flashpnt = flashpnt.sys,4 ; XP doesn't have lp6nds35 = lp6nds35.sys,4 ; XP doesn't have ql2100 = ql2100.sys,4 ; XP doesn't have cpqfcalm = cpqfcalm.sys,4 ; XP doesn't have fireport = fireport.sys,4 ; XP doesn't have fd16_700 = fd16_700.sys,4 ; XP doesn't have tffsport = tffsport.sys,4 ; XP doesn't have so you could comment them all out. editing empty lines will not gain you any speed. much may be learned by analyzing my files.

attach your log. also let us know if the files have made it into the i386 folder in SOURCESS by expanding and checking the versions of Spupdsvc.exe (should be 6.3.13.0) and Wmp.dll (should be 11.0.5721.5260).

Oh no you don't, if I'm here, you're here: misery loves company, pal (Though your 'job' is a HECK of a lot more work, I know)

i know that procmon was supposed to replace filemon but is it possible to run filemon at the same time to see what files are being manipulated? This shld be a separate thread but if you discover Opera is writing reg entries as opposed to updating some file, let me know, and I can write them in INF format and add them to MRU_KILL.INF.

I know I should keep more detailed notes... but ripping out Active Desktop was killing some other piece of software. I can't recall what it was. You can make it invisible, and I probably should look into making it not show, but I'm more interested in -killing- it than making it invisible, which is honestly why I just left it alone. I suppose I will look into making it not show in the next revision. Having a hard time recalling what the problems with it were...

It is toggleable but only insofar as installing files that you need in order to install (regular, non-express) Outlook in MS Office. In fact the msoe inf file is a standalone installer so you can right click/install and the files necessary for MS Office will be put in place. But the newsreader functions? I have no idea, sorry... which I why I recommend TommyP's advice to you. XNews by Luu Tran is an amazing piece of software. So good in fact that a lot of Linux users run WINE in order to be able to run it; it's one of the best newsreaders/newsposting software packages you'll ever use.

Hmm. Let me download and run CCleaner and get back to you so I can see myself. It reports some things that are legitimately errors (the jpg and png CLSID reassignments for example) but it also reports some things as errors that I don't think are wrong, like the Active Directory timestamp CLSID. You can go ahead and fix all of these, the ones I think are correct -- the ones that CCleaner and I disagree on -- are very trivial anyway. I have made some changes in my files so that some of the errors reported are eliminated.

Hey Schadenfreude! A new rule on the board forbids (re)distribution of unofficial binary packages like unofficial fix packs. But in any case, this project was about pre-slipstreaming all fixes into NT before installation, none of us worked on a SP7 that you load after installation, so it never happened. A while back Tomcat had created NT 4 support for HFSLIP but the code was never made public. Due to a hard drive data loss a looong time ago, I no longer have that code.

I'm not clear on what you are triggering this event with -- which files are you replacing? I don't understand why the "CD" goes away. I am stumped on this one. I set SFCQuota to ffffffff to save all files but somehow I guess it's not happening. I will check into this more but I can't promise a solution because "on paper," SFC should work fine...

Fileset is no longer valid. Try this newer one http://www.vorck.com/data/fdv-xp.zip It's my personal setup so I know it works. Installs without IE but leaves a lot of stuff. Produces one error about runlast.inf which I don't have time to fix right now.

Setup is using DOSNET, which I don't include. Technically this will work for an IE free install, but my fileset, and HFSLIP, are optimized for CD installs. So, while this method does work, it produces the errors you note here... To avoid all problems, do NOT use the winnt32 method for installs.

I have fixed this. Sorry about this! One of the ways I got the message cleaned up was to set the SFC path, and the install path, as the same. The lines below make it work now. HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SfcQuota",0x00010001,ff,ff,ff,ff HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCDllCacheDir",,"e:" HKLM,"SOFTWARE\Policies\Microsoft\Windows NT\Windows File Protection","SFCDllCacheDir",,"e:" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Setup","SourcePath",,"e:" Change "e" to whatever your CD-ROM path is. Mine now says "Insert your Windows 2000 CD" and recognizes the CD. This is fixed in the fileset now along with Martin's "%11%\acelpdec.ax" thanks

Hi guys! My general policy on this topic is: 1. A hotfix that slows Windows down: I instruct users not to use it 2. A hotfix for some component I remove like IIS: I give no instruction, as it wouldn't install anyway I find that only telling users about #1 keeps confusion to a minimum. Also, it keeps TommyP from having to create annotations because his list is not quite autogenerated, but generated very quickly, and I wouldn't want to slow his process down. Good eye though, PMikeP...

If you did not change anything, the Inaccessable boot device wouldn't be from my fileset, actually. If you download my fileset and did not modify it at all and ran HFSLIP, then all it does is look for the uniata file -- it does nothing else. You can comment uniata out of the file lists in TXTSETUP and LAYOUT. The install WILL default to the regular, no-frills atapi driver. If, however, you made changes to the TXTSETUP file and at any point uncommented any uniata sections, setup matched a uniata device string with the device string of your hard drive controller. BTW... I don't understand how windows 2000's default atapi driver can work if you have a SATA drive. Did you install XP and find that XP's default atapi driver worked? 2000's default atapi driver just does not see SATA.

You know, to be honest, it's a message I have always dismissed. I never knew that it didn't work. Not sure what's going on. I'll have to check into it. I'll have to do a regular install and monitor the file replacement with some tools to see what's being called.