RaGhul

Ryan and nuhi work together to make sure their apps/packs work together. I often add Ryan's pack with Integrator, and then use nlite to tweak xp further. I've done many combinations without a hitch! So, could you be a little more specific? What problem are you having exactly?

Well, there could be several reasons for that: You didn't remove all that much, or the components that you removed weren't all that big. Your computer itself. If it's a low-end model, you might not see a noticeable difference. Some of the guys who post those 'Lite' Windows packs also perform extra tweaks (besides nlite) to slim them down. I personally wouldn't even TRY them. Too risky. Also, you can disable SFC under Options/Patches. Here's a pic: This takes about 10 minutes off the installation time, give or take.

You might also try downloading RyanVM's Windows XP Post-SP2 Update Pack here It'll save you the headache of all those dammed hotfixes, and also has a MD5 sum, so you'll KNOW if your download is good or not.

Thx, Madhits. You know, to be honest, after beating my head against my monitor for several weeks, I'm starting to come to the conclusion that most errors involving Component Removal stem from user error, simple mistakes, or simply not knowing how to do a particular thing. For example: Importing an .INI file from one version of nlite into another. Not using the latest version of nlite for the latest Ryan/Xable pack. Not disabling "High Compression" Your rig just sucks!! (Mine does! ) nuhi and Ryan DO collaborate, as do most of the creators of the major packs, and their releases coincide to reflect that. For example, if you're using Ryan's Pack v2.1.6, you must use nlite 1.3RC2 OR Integrator 1.4.3 Using an older version will cause you to lose a file or two, and possibly errors. Still, a note with some tips in an FAQ file or tutorial would be nice. It would be good for nuhi, too. Eliminating 'user-error' or 'hardware-error' from the equation would allow nuhi to focus on ACTUAL issues with nlite.

Thx, nuhi!! I'm gonna use this tonight! PS: Pistolero, Haces bien en aconsejar que no se ponga SP1, y luego encima SP2, pero, no debe de causar problemas montando los dos SP's. Simplemente, no es necesario, y una perdida de tiempo. Maxfutur, Si montas solamente SP2, y tienes problemas, entonces esta mal tu fuente, ó tu SP2... hay que bajarlo de nuevo.

Just wanted to say I thought this was a very cool thread!! I'll be watching it closely. (Sorry for going off-topic.)

What happened to the 'already-tweaked' version? Bummer.

Don't sweat it too much, nuhi. Most likely, it's bad RAM. I also noticed on that pc, when I would copy files from one directory to another, the copied file sometimes would not execute properly. Upon checking the hashes, they were not the same file. This occured more frequently with larger files than smaller ones. Burning sometimes produced bad files on cd's as well. I might add that it may not be bad RAM, so much as 'inadequate' RAM that was the culprit. That particular rig has 256mb of DDR266. One more thing: I don't know if this has anything to do with it, but I've also started using nlite with 'High Compression' disabled. All the successful cd's I've made so far have both been on another pc, and disabling this option, so I cannot determine which resulted in my newfound success. I'll try to run a test or 2 later in the week to narrow it down for you.

I DID IT!! :D Although, I feel kinda stupid. After going through the paces, Xable did the exact thing that I did and had 'zero' copy errors. So, he suggested it might be a 'hardware' issue. Sure enough, I slapped my hard disk (It's new, so I knew that wasn't the prob.) into another PC, and ....VOILA!! ZERO COPY ERRORS!! (Duh, I should have thought of that!) Well, with all the people posting about 'copy errors' with nlite, I naturally assumed something else was the prob. Never even occurred to me that the machine itself might be the cause! Many shout-outs go to the following people: 5eraph, Sigi, Ryan, Kel, ricktendo, MrNxDmX, Xable (without whom I'd still be trying to figure it out) ...and of course, nuhi. I'm sure he'll be glad to know it wasn't NLITE. (BTW, 1.3RC seems to run even smoother than 1.2.1, IMHO. PS: I really like the Import Session feature. I've been using it a bunch lately. It's a real time-saver!! BTW, Xable and I have had no problems importing 1.2.1 to 1.3RC. I know you really shouldn't, but I thought you'd like to know that it's possible ...and it WORKS!

Honestly, I'm pretty disappointed that this is a Sticky. Don't get me wrong, the concept is excellent. But the post itself is quite disorganized, and somewhat incoherent. Some suggestions: 1) Why not place the list of applications in alphabetical order? 2) You could also make an alternate list with the files (in order) and the programs affected by them. It would be much easier to sift through that way. 3) Why not also include Windows components that shouldn't be removed for certain apps, not just particular files. I don't know. Just a little more info (maybe a better explanation/intro at the top of the first post) and organization, guys. Adding BB Code also helps make it more readable. PS: I'd be glad to help out if you like. (This is a 'real' offer, not a 'sarcastic' one. Really. I'll help.)

Yeah, that's weird. Right off the bat, I see you added Process Explorer and CCleaner. I'd try doing it without adding those 2 and see what happens. If everything's ok, well then, you know...

nuhi, I've also read on the forums here that there is a file in I386 which tells XP what size the files are supposed to be, and if the size doesn't match up, XP whines. I'm thinking the problem is either this, or what I mentioned in the previous post. Just an educated guess. Perhaps you could put in a script in nLite to edit this file. It could potentially save many people ALOT of grief. (nuhi, you there?)

..

That's a good observation, Madhits. Maybe it well help nuhi in narrowing down what causes the problem. I too have had more problems with the newer releases. Maybe nuhi can track down what he does differently in the Component Removal process now that may explain the problem. Also, I saw more errors with Xable's than Ryan's, it seems. More interesting, though, is that neither pack got me to the coveted "zero copy errors" until I did the opposite of what everyone told me to do: Remove Components first, then Integrate. I would like someone 'in the know' to explain to me why everything should be added 'before' Removal. Maybe I'm nuts, but it seems to me more logical to Remove Components first. PS: Actually, come to find out I think my disk is not MS factory, but slipstreamed with SP2 after all. Same problems as you, though, so I'm not sure it's a big deal. Then again, maybe that's the problem: nLite is trying to remove stuff, but finds it in different places than expected. So it doesn't remove them entirely. Hmmm....

Thx, nuhi.

Why not just list agp440.sys in the "Keep files" section in Remove Components?

Ok, I start out with XP Corporate with SP2 already in it. Whether it's slipstreamed or not, I'm not sure, but I believe it's MS's version, not slipstreamed. The ISO file is 585mb, labeled "VRMPVOL_EN". I extract it to a folder using Winrar. After that, I've tried each of these: 1.) Integrator to add Ryan/Xable's pack, then Remove Components with nLite. 2.) Remove Components with nLite, then Integrator to add Ryan/Xable's pack. 3.) nLite for both. No other addons. Always produces at least 3 (usually more) copy errors. The only way that HASN'T produced errors was method 3.), using Ryan's pack. The files that won't copy are always different, but not random. They change depending on what I did, but if I try re-installing the same resultant CD on VMware, I get the same errors as before. VMware has saved me alot of coasters, and I've tested it with actual CDs burned from the same ISO. It will produce the same exact errors as if I had actually installed it with a CD, so I know the results are good. Attached is my INI file. I'll be happy to explain further, if need be. These links might also help: http://www.msfn.org/board/index.php?showtopic=90019 http://www.ryanvm.net/forum/viewtopic.php?t=4046

This post is more like a 'continuation' of a thread I started in Ryan's forums. Maybe this will help elaborate: http://www.ryanvm.net/forum/viewtopic.php?t=4046

Are you sure, MarkCoolio? I haven't used the Unattended Setup options for a couple versions, but I've seen quite a few posts about bugs here and there. So it may be a glitch with that. broonow, are you using Unattended?

You mean, "course"? Nuhi isn't American, so I can forgive him for the spelling errors. But if he wants some help, I'll be happy to, buddy!!

Personally, I don't see why not, as long as you have legal, store-bought CDs and serial keys. However, of course, all warranties with MS would be void by altering it with nLite. But if you know enough to enLighten it, hopefully you know how to reformat should things go wrong. (Who really needs MS Support anyways? ) If MS wants to make a big stink about altering XP, then technically, ANYONE who deleted ANYTHING ever from their PC would be in jail!! (Of course, that's probably how they would want it!! (Hahah), but the courts won't let 'em.

How about, 'Good work, man! It's not good that a program such as THIS has misspelled words.' Maybe, 'I meant audit team... that was the joke, to misspell the word.' Perhaps you meant this:"I just remembered that guys from the UK always blame Americans for eating too many letters in their words." Apparently, no one HERE will be making the audit team...

Ok, nuhi... Attached is the INI file showing all the removed components. Only 2 patches: SFC and uxtheme.dll As stated in RyanVM's forums, I've tried all possible combinations of orders with both Integrator and nLite, but only Removing Components first, then Integrating Ryan's update, will result in 'zero copy errors'. Let's figure this thing out! LAST_SESSION.INI

Ok, I've had copy errors before, but now it's getting out of hand. The thing is, if I just integrate Xable's Update Pack onto a clean XP cd using Integrator... no problems. If I just Remove Components from a clean CD using nLite... once again, NO problems. However, if I try to combine the two in any way, shape or form, I get this: "Windows cannot copy file..." It's the ULTIMATE definition of redundancy: trying the same thing over and over (and over) again, just to wind up with the same results. What really irks me is how all these people are saying things like, "Wow, I got my CD down to 187megs", or "Never had ANY problems". Yeah, I can do that do, but not if I want to integrate the latest hotfixes to stay up to date. So far, the best result I got was by first Removing Components with nLite, then Integrating Xable's pack. Just one copy error. But still... Seriously, I'm not a dope. I DO read. I've installed XP so many times, I've MEMORIZED the serial key. I know VMware. (It has saved me 'countless' CDs.) I even helped Kel with an Addon. I even ResHack boooggy's WMP so I can use the icon I prefer. What gives? PS: Going crazy!! :}

Puggsley, Nice tip!! I'll try it.