GrofLuigi

First thing I would check is .Net Framework installation. Version 2.0 SP1 works fine for me and is the recommended version. See the bottom of nLite download page. GL

Reading the topic title... I see nowhere "my idea about Microsoft's profit". No offense, but too many people worry about that. I never could understand the urge some ppl feel to defend Goliath from David. Microsoft invests millions of dollars in that anyway. GL

"Skinbois" have the unfair advantage that they have Microsoft on their side. So they can force us to use skins, but we can't force them not to use skins. GL

What I would like to see in the future in nLite is not much more removals (there is little left to remove) but debugging and resolving the not-so-obvious internal Windows dependencies. Examples i've encountered: - Tweaks not applied (I think Windows overrides them during the "applying settings/registering components" stage). - Defrag with volume shadow copy (if VSS removed, there is complaint in the event log, although everything works fine). - Sometimes services are not deleted or their startup state isn't set as desired (dnscache not deleted). - Microsoft Update not removed (in system32 - cdm.dll, iupdate.dll, wu*.*) - Let's try to unbind more unnecessary dependencies. I know that most of the time this is not nLite's fault, but it would be nice to have workarounds (like for XP SP3). GL

Always take these numbers with a grain of salt and look who is the source of this. Not every pirated copy would have been sold. GL

According to your ini, hyper terminal shouldn't be removed. I think it's the "Communication tools" component in ;# Network #. (Check in program files\windows nt for the exe.) Same for Remote Assistance - it shouldn't be removed. Maybe your source is somehow flawed? Also, try the latest version of nLite (there are always bugs fixed). GL

You mean something like THIS? *Edit: I don't know if it actually stops the installation, I had never used it (because I didn't need to). GL

I think it's pointless to remove stuff from windows just to install more bloat. Just keep the whole thing if you use it. GL

After install, it seems that the tweaks were applied. Can't know for sure because I don't know the exact location for some of them. But I don't understand why were they removed from Last Session.ini. Again, what I did was: - Load nLite - Import Old Session.ini which I work with most of the time - Adjust some settings (not the ones above, I usually don't touch them; maybe only USB idle) - make ISO and finish nLite - binary compare Old Session.ini and Last Session.ini - they are not present - but they are applied?! Now I don't understand anything. I guess it isn't a bug, it's a feature - only Nuhi can tell. Off to building New Session.ini. GL

I tried it in a VM and it broke a lot of stuff. The least problem was that the 'lited away' components returned. GL

Windows XP = Windows 2000 + skin. I laughed my a$$ off when I first saw it. Skins are for kiddies. GL *Edit Oh yeah, + activation.

I was lured into XP by the promises that no app could crash another or the OS itself - memory isolation (protection). Coming from Amiga OS, I know it was a good thing. Unfortunately, it wasn't true at first - I've seen my fair share of blue screens. After the service packs the situation is better, but Micro$oft has grasped a new fetish - security (through obscurity = drm, bloat, slugishness). And taking away the control from the user. So the time is moving backwards now. GL

GL

OK, holy thread resurection Batman and all that. I ran into this once again. I was reinstalling a driver and it picked up the .sys (usb ehci/ohci something) from the SP2.cab instead of the one sitting beside it in WINDOWS\Driver Cache\i386 . Not installed SP3 yet, because this install is working beautifully, but for God's sake, isn't there a driver.cab recompressor for already installed systems? (taking .cat files into account). I tried with WinRar at the time, but it didn't work (can't remember any more what was the exact message, but I think it wanted the CD). GL

Hi, I don't think Microsoft's solution to The Dll Hell is effective. In fact, as I'm not a programmer, I can't see how many times it has saved my a$$, but I can clearly see the overhead it creates on my system. Some even say it creates new problem(s). BTW I don't understand much from that link, so I might be wrong. But there are many others. For starters, I'd expect they would put most work on correcting the problems created by rogue programs from some big $$$ companies I (and most normal users) rarely use, or created by their Visual *** compilers, which are just bloating like a baloon over time. Not the problems of small/freeware applications that are most common. So: Can I clean the WinSxS mess on XP and how? Has someone tried it? Is someone working on that? Will a simple delete (+move the DLL to System32) do? I see there is something done on Vista, can it be applied on XP? I don't care about versioning problem, I think it's overrated. I think it can be solved in at least three ways: 1. Find out the Dll file with largest version number and stick with that. Most of the time, features are added in programs, not removed. 2. Find out that speciffic app needs speciffic dll. Put it in the app's folder. 3. For hopeless cases, find another app that does the same job. And so on... Comments? Suggestions? GL

From your source disk, of course. GL

I knew that, I just didn't feel comfortable suggesting a change that could be seen as a real security risk. BTW, you'd be surprised how many LowRiskFileTypes I have. GL

In registry terms: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] is a key RTHDCPL is value data is whatever was inside it GL

You mean: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "RTHDCPL"=- "SkyTel"=- "SoundMan"=- "AlcWzrd"=- "Alcmtr"=- ? I doubt they appear as you described them, or they wouldn't get executed anyway (except on win2000). GL

I think you can, but there was some information at the time that DefaultUser is not just a simple template for users, but it is used for i.e. Local System (also). I can't find this right now, and don't know if it's relevant to your question (and I don't do unattended), but by all means - try. GL

I'm not sure if nLite does (all) of this. But this is what you need: REGEDIT4 [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Download] "CheckExeSignatures"="no" "RunInvalidSignatures"=dword:1 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Attachments] "SaveZoneInformation"=dword:1 or In Internet Explorer, click Tools/Internet Options > Security. Click the Internet icon, then the Custom Level button. Under Downloads, check the radio button marked Enable under the heading "Automatic prompting for file downloads." Click OK here and in the next dialog. GL

I doubt it. But you can try - here's the registry entry of the service (probably there are more). Again, you didn't say what OS you're working with, so I assume XP. REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LmHosts] "Type"=dword:00000120 "Start"=dword:00000002 "ErrorControl"=dword:00000001 "ImagePath"=hex(2):25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,73,79,73,74,65,6d,33,\ 32,5c,73,76,63,68,6f,73,74,2e,65,78,65,20,2d,6b,20,4c,6f,63,61,6c,53,65,72,\ 76,69,63,65,00 "DisplayName"="TCP/IP NetBIOS Helper" "Group"="TDI" "DependOnService"=hex(7):4e,65,74,42,54,00,41,66,64,00,00 "ObjectName"="LocalSystem" "Description"="Enables support for NetBIOS over TCP/IP (NetBT) service and NetBIOS name resolution." [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LmHosts\Enum] "0"="Root\\LEGACY_LMHOSTS\\0000" "Count"=dword:00000001 "NextInstance"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LmHosts\Parameters] "ServiceDll"=hex(2):25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,53,79,73,74,65,6d,\ 33,32,5c,6c,6d,68,73,76,63,2e,64,6c,6c,00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LmHosts\Security] "Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\ 00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,00,60,00,04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,\ 05,0b,00,00,00,00,00,18,00,9d,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,\ 23,02,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,\ 02,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,\ 00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00 You need to put lmhsvc.dll (extract and unpack it from your source) into system32. There are probably other dlls needed, you could try examining lmhsvc.dll with Dependency Walker. GL

To connect, only tcp/ip. But I presume you want to do more. For file and printer sharing, usually (I'm assuming XP): (Services) Computer Browser Network Connections Server Tcp/Ip NetBios Helper Workstation Then there is the Windows Firewall, which is not needed, but can cause problems if disabled/deleted/misconfigured. Then there is Wireless if you connect through wireless device. Then there are the four new services in SP3 (NAP, Wired autoconfig, health key certificate management and ... ), not always needed, but can cause problems if disabled/deleted/misconfigured. Then there is DHCP if you need it (you don't use static IP addreses and have router/DHCP server). (Drivers) (these are under device manager, non-plug and play drivers - you should usually not touch them, just check) AFD NDIS*something (there are several of them, you need probably just one or none - or all of them) NetBios over TCP Remote Access* (see NDIS) Your network card's driver There are also many other possible combinations, depending on hardware, but with these I think it should work. You gave too little information. GL

Loaded a preset created with some of the previous versions of nLite (but not too old). Made some adjustments and created ISO. Seems to work OK, not burned/installed the ISO yet (don't have enough time), but I noticed some of the options from the old preset were not present in the Last Session.ini. They are: Boot and Shutdown-Setup Prefetch-Cache-Disabled Explorer-Disable Accessibility keyboard shortcuts Explorer-Launch folder windows in a seperate process Performance-Enable USB Idle Endpoint support Start Menu-Disable popup on first boot Visual Effects-Smooth edges of screen fonts-ClearType Windows Media Player-Disable silent acqusition While working with nLite, I didn't check specifically for these items, but everything seemed fine, just the way I always do it. Are these tweaks: a ) removed from nLite? b ) removed from XP SP3? (the previous preset MIGHT have been from SP2) c ) moved to another place in nLite? (but there were no new entries similar to them) d ) a bug in nLite? (forgot them)? e ) my mistake? (should've started from scratch, but then why have Import Last Session Ini anyway?) This was checked by doing text compare of the Old Preset.ini and Last Session.ini. When I install the CD, I will know more, but sometimes some of the tweaks don't 'take', so... Which letter is it? GL

I know, and I understood from the start what were you asking for, but those differences are not in nLite, they are in the OS's themselves (well duh!) and Nlite detects them. I personally haven't dealt that much with 2000 to know it 'by heart' while the opposite can be said for XP. You can try this: make two test runs with your versions of 2000 and XP removing everything; compare the two Last_Session.ini's with some text compare tool. You'll get a pretty good idea about the differences. It will be easy, because nLite sorts the items under each section (unlike many other programs that use ini files) and that's what I like about it. GL