fdv

?? huh?? Open HIVESYS.INF find HKLM,"SYSTEM\CurrentControlSet\Control\Lsa Add your lines, save, close Open LAYOUT.INF Replace all ,_x, with ,, (comma underscore x comma with comma comma) Save, close Done

Sorry I can't tell you the exact name of the file, I forget, but it is a common controls issue. I ran into it a long time ago on NT4 Ser when I installed something that put its own dll in place of the system dll. I am surprised that re-applying everything didn't fix it though. Sorry I could only narrow it down a bit and not solve it.

Back a long while ago, the radio stuff, when removed from the explorer bar, caused explorer to crash all the time. That may have been due to an earlier version of explorer -- it's a holdover from SP1 days. The radio stuff is in SHELL.INF. Open that file, find [add.fixes] and you'll see it. I never tried running without it since SP1. The bug has probably been fixed, I'm guessing. Remember of course that since everything is open and modifyable, you can write an INF to add anything at all and put it into SYSSETUP.INF under [infs.Always]; I use a reg snapshot program if I -really- want something installed this way and write my own INF. Just remember to add the files also to TXTSETUP and LAYOUT with = 1,,,,,,,,3,3 after them so that Windows puts them on the drive so the INF you create can later find them.

Ambassador: User accounts applet: I'm actually not too sure what you mean. I remove the control panel account wizard; the only one left that's usable is the one that's like the Win2000 one. Describe to me how you open the classic one so I can be sure. glaurung, let me know if there are more in my fileset to be dealt with and I'll see what I can do to make things normal. Offhand I don't know of much I have left in of the "wizard" crap. Browncoat, my fileset takes care of all of that stuff you mention (I also keep themes, but everything defaults to classic, that's all). I am working eventually toward a Car-MP3 fileset with nearly nothing in it, just leaving the ability to run media player software. I'm not there yet of course, but it will be worked on. For now, I agree, nLite will probably fit your needs better. My fileset isn't as flexible, but it does yield a consistent result without loading the old session every time, modifying your source, and it puts dozens of popular tweaks right into the HIVE files including fixed timezones right off the bat, and lots of other little things that make it easy for the do-it-yourselfer to get in and see what's going on.

As far as I am aware, HFSLIP, both 32 and 64 bit XP versions, slipstream 100% of XP hotfixes. The program's compatible with nLite.

Updated. If anyone has additional ideas for stuff to remove, let me know. I'm interested especially in unique stuff, not necessarily stuff that nLite removes. This fileset needs testing so comments are welcome...

It doesn't matter, but the fix was so easy I just did it the old way, which was to do it as I did for Windows 2000. In that method of course no DLLs are used. New revision coming probably tonight. Right click > Properties on the Win32 directory says "243mb." And that's -with- Active Directory and non-English keyboard layouts, which will later be moved to INTL.INF. OOBE is still in because it's got networking dependencies. Which I completely understand, but it would be nice to make it truly optional. I will at some point later. I was also thinking of making the MS Management Console (MMC) optional too, but it might not really save much space. I got this when replying: "Your secure key, used to verify you are posting the topic, did not match the one submitted. Please go back, reload the form, and try again." I -was- logged in. What the heck?

Hi all, those who were using my 2003 hotfix list, I wanted to let you know that I eliminated a bunch of obsolete fixes that Microsoft does not list as replaced (in cases where two fixes replace the files on one fix, the original fix is not listed as being deprecated). Because the eliminations were numerous, anyone who used the list should simply re-download the fixes.

2003 users, I have "gone deep" and eliminated a number of hotfixes that had files that were replaced by more than one subsequent fix. In other words, if kb111111 updates A.DLL and B.DLL, and kb222222 updates only A.DLL and kb333333 updates only B.DLL, Microsoft will not let you know that kb111111 is obsolete. I've done that, and in the process, eliminated a bunch of obsoletes (there might even be more, but for now I think I've got them). So, 2003 users, please just re-download everything, it's just easier. TP: I saw your note above after my email so never mind on that bit.

I have to confess, this was done for TommyP, I don't know a darned thing about MPC and I don't know why it's asking for that binary. The INF file was mainly to switch associations to MPC. You have to open any files not found in TXTSETUP and LAYOUT and uncomment them (so the install copies them over) if that is a problem; I don't have the files in front of me ATM, and I don't recall how I arranged that. So, basically you are correct; uncomment logagent, although I don't know why its asking. Remind me Tuesday or so and I'll have a look at the file to see what's going on. I am traveling on business though on Wed so I might not have the time but I will look into it if reminded.

400MHz chip, 320 RAM, I'd say nLiting Windows 2000 or using my fileset and HFSLIP is your best bet.

The problem is that you installed on a notebook, and XP saw this during the install, so it installed the power saving kernel. There are four: ntoskrnl.exe (laptop systems get this) ntkrnlpa.exe (desktop systems get this) ntkrnlmp.exe (legacy/older systems) ntkrpamp.exe (legacy/older systems) I have to apologize as I swapped the kernel in my notebook but I can barely remember how (I had the same problem as you did on my IBM ThinkPad). There is a settings somewhere... Try: Right click on My Computer Properties Hardware Device Manager Double click "Computer" at the top You will see some descriptor. Mine says "ACPI Multiprocessor PC" meaning desktop system. If you go to System Devices, there is an item that you have to uninstall to make XP think that it's a desktop computer. Again, I am sorry but I cannot recall exactly. After you do it, you system will reinstall everything on next boot one device at a time and it will take FOREVER. After that, XP thinks that there is no power saving feature on the computer and it will stop powering devices down. At least you have a start to go Googling

Digitally signed, etc etc etc. What's wrong with just using HFSLIP? Beta here. (Yes, Gurglemeyer did it, but I'm not going to go down that road because he probably had access to a signing tool and other MS binaries that one cannot normally get.)

The new betas have worked for me 100% fine FWIW. 2000 and XP. Haven't tried 2003 with any betas beyond C, but C worked fine.

Security (secunia): IE7, IE8, Firefox 3.5, Chrome, Opera Looks like Opera 10 wins, but they all follow each other more or less, with IE having the most critical exploits, but not by much. The advantage to the other browsers is that they seldom go for very long with unpatched exploits. (In addition, IE 6/7/8 have hooks to the system via zones; Microsoft has never made this API data available so FF, Chrome, Opera et al are simply not exploitable the same way in the Internet Zone/Localzone area). Upgrading IE6 to IE7 or 8: We all know windows can be installed without IE, but there are some files that are required that have IE crap in them: SHDOCVW.DLL and BROWSEUI.DLL are two. If Microsoft issued a hotfix or even an updated version of, say, SHELL32 or EXPLORER, would you get it? Some people would, some people wouldn't. I'm a "maybe." If you're the type that wants newer system files, you should know that IE 7/8 have newer system files than IE6. Does that mean they're better? Hard to say, but the fact of the matter is that newer IE versions do, in fact, update core system files. Personally, for me, that's not enough reason to upgrade, but to each his own.

That's the trick I used in the win2k fileset; I was looking for the DLL, wanted to try something new I guess, but really, I might as well do what I did before. While I have you reading this TP what's your immediate take on eliminating the need for the WIN51* root files? The fileset only needs one now; it would eliminate instances of accidental noninclusion or deletion. Feels odd communicating this way (for the rest of you TP and I usually communicate 98.7% via email and 1% via going outside and yelling really loud)

Thanks, PROBLEMCHYLDE As for the insert disk... that is very odd. In fact the only time it could ever happen due to the file mods I made in TXTSETUP is when win51ip is missing, so the most likely cause is an INF file, a different one, that requires the root files that jaclaz is referring to. Try adding not only the required files: WIN51 WIN51IP WIN51IP.SP2 But also add two more, just in case: WIN51IP.SP1 and WIN51IP.SP3 Make them all single byte at least. They should not be empty. Put at least one character in them and save them before you proceed. Maybe I should remove the requirement for the root files altogether. BTW, since you are using SP2, you are going to get some file copy errors (as in "press ESC to ignore") and they are nothing really to worry about. I really, really recommend that you slipstream SP3 though. Martin H, ah, I see what you meant now. Ok, I will make the necessary change. I admit IE.INF is a kludge. You want to know the truth here -- if I prevent install in the first place like I really want to, the 'minimize to desktop' icon next to the start button doesn't get created. The reg entries to make it are in AXANT5 but one of the IE DLLs actually sets the stage. I am not sure which one... if anyone wants to find out which DLL needs to stay through setup to allow the show desktop icon to be made, it would help me greatly! Then I wouldn't have to do the "install IE first, delete just before first boot" method that is rather boneheaded. What's everyone findings so far? Anyone not using nLite that is, which would make you rare indeed!! Anything that is broken? Any software that won't work? I have system32 down to, what, 270megs or so, and I am still optionalizing things. I've been isosizing all week testing various configs. It's scary how many network dependencies there are in XP. I mean if you just look at it funny, networking stops working. It's ridiculous. Anyway, I plan to use this myself pretty soon as I'm pretty comfortable with it.

You're right, and I changed the file on 2/2. This section now says: [DeletePartial] DelFiles = ie.system.opt, ie.appdir, ie.triedit, ie.vgxcopy The SYSSETUP stuff actually is correct, but does look weird, I know. Try re-downloading. Sorry for any confusion

No biggie, really. In 2006 or so, I set permissions on all of the empty directories in 2000 in DEFLTWK.INF so that an admin call truly delete them. I carried that trick over to XP. The added request for E is to run a new file, DELDIRS, to delete directories like: system32\com_dmi, system32\ias, system32\1028 and others, etc. just before first boot. There are a bunch listed in the file but networking in XP has a dependency on one of the folders, I don't know which one yet. I suspect dhcp or oobe. Haven't had time to find out. So, beta E is just doing a bit more cleanup. If this topic intrigues people, I encourage them to have a closer look at DEFLTWK.INF. FWIW, I also assign WORLD to the time set permissions, and a few other little things as well, such as a branch in the registry required for my eventual mp3-Car PC fileset.

"Where are the instructions to get this working. You said put the files in i386. I did that, now what?" Using this with HFSLIP is preferred, but if this is all you want to do, then you're all set. In other words, you copied the files into i386, so now you're good to go -- you download or make a boot sector and make a bootable ISO or CD and install.

Is there a master list of core XP files that XP absolutely needs? I know you use an alternate shell and I fully understand why, I'm just looking to see if there is a minimum list for the regular MS Explorer shell. Also, there is a new revision of the fileset up if anyone wants to try it. I added support for installing from DOS but I have no intention of testing it. Also, at the bottom of TXTSETUP is Intel IASTOR driver support, but getting the files from Intel is up to you (you can get some from Driverpacks I guess, but I used Intel driver files that are actually newer to make this). Can I redistribute such files or would Intel frown? I leave that question unanswered for now. I did grab an idea from Driverpacks, which was to add the version number to the filename (right click, properties gives the version). See the readme for other items.

I downloaded it and checked its structure. Indeed it will not work with HFSLIP. I was going to suggest expanding the .7z and compressing the files and putting them into the REPLACE/i386 directory, but that's so much work (and you might accidentally compress a file that is not compressed and thereby fail to replace it). It might seem a lot of work, and that RyanVM hotfix list does look mighty long, but if you see the official TommyP hotfix list on my site, it's really not that much. Tom also trims out obsolete fixes. It will take you maybe 20 minutes to D/L everything and put it into HF, and you'll have an easier time going forward.

I don't use the DLL anymore. In my XP filset, open HIVESFT.INF The first commented out items for SFCDllCacheDir should be uncommented and SFC will be off at install time. The discovery of this was an accident! AFAIK Microsoft only documents this on one of their pages. Two lines instead of a hacked DLL seems better to me because turning SFC back -on- means just changing the Z: value back to C:\WINDOWS\system32\dllcache and it's nice to have SFC turned on when you're installing for Grandma

v5. The confusion results from the fact that Remote Desktop has three hotfixes and three hotfix numbers, and the three are under one (different) master hotfix number, so there are FOUR numbers to choose from. Choose the lowest number for SP3; there is 5.0, 5.1, 6.0 IIRC. You want 5.0. The other versions will slipstream but will give errors when you try to actually run them. I wish I could tell you how to make 6 work, but since I do not use it, I don't other with it, sorry

The modified setup dll from my XP fileset works okay too which is a smaller download. As for sfc_os, I guess I didn't know that was needed. I don't provide one of them. (Is it really needed? I seemed to test the sets out without it just fine IIRC).