GrofLuigi

This is madness. Full IE8 installer for Windows 2003 won't install if Windows Update is not around, although options are unchecked. Traced with ProcMon, it stops on class {4CB43D7F-7EEE-4906-8698-60DA1C38F2FE}. Although I faked empty strings of InprocServer32 and LocalServer32, which usually works for other checks, including some Microsoft's, this time it won't give in. I guess it tries to communicate through COM. There is no chance of reinstalling Windows Update here, ever. I've looked into the .inf's, but I can't seem to find anything that would prohibit installation or looking for prerequisites, but I'm not that good with inf's. Installing through right click on .inf's leaves the system in mixed state where much of IE6 is still left. The installer is downloaded from http://download.microsoft.com/download/7/5/0/7507EBD5-0193-4B7F-9F14-9014C7EB5C67/IE8-WindowsServer2003-x86-ENU.exe and I'm absolutely positive it's the one needed. I've tried YumeYao_IE8_Addon_Nosetuperr_ENU_1_4_11, but it also won't install through inf's, and I vaguely remember that integration in source didn't work (missing file). Yes, I have done the instructions for 2003. For now, I've just copied some (most) of the files where they're supposed to be, but there are some unknowns (.mui files all over the place), according to a clean install on XP on VirtualBox, but maybe there is a difference in locations for 2003? Regsvr'ing them is done, as far as I can see, no problems there, but I would prefer a "proper" solution. So here is the question: How can I install IE8 on a live system without Windows Update?. I suspect it's the same thing with XP, not only with 2003. Google had nothing to say. GL

Maybe some combination of these: Options > Playback - Repeat forever - Rewind when done playing (I haven't tried it). GL

Hotfix adds new functionality to suppress Plug and Play-related UI messages in Windows Server 2003 or in Windows XP Not a full solution, but it might help you somewhat, since you say you already lock some other places. GL

XP Fast Logon Optimization feature Maybe WaitForNetwork (XP reads that key too). But... What exactly is "Autostart"? GL

Yeah, If I could strip everything but the kernel, I would do it in a heartbeat,but it doesn't work that way. I don't have too much experience with 7, I use Windows7 Toolkit. But Win7 itself is even more unfriendly towards removal, it has many more hidden/unknown dependencies and many more components overall, so I'll wait until I have more time to tinker with it (which might be never ). Before it came out, Win7 was supposed to be "modular", but now nobody (from the officials) even mentions it. GL

Those are not services, they are in Nlite sections components or network or operating system options... So no state to be set to. I don't see them in your latest INI, so they are not removed (I hope you didn't run Nlite twice on the same source and removed them ina previous run ). It seems OK now. GL

I don't know about that, it might be so. But it has tons of options, maybe its one of them? All I know is my jaw dropped when it made a nice report with command lines to uninstall obsolete and install new (I haven't tried that yet) on a system that was in a pretty chaotic state in regards to updates (multiple ones installed, two or three SoLoR packs applied on various dates, some hotfixes failed and left in unknown state). It's been working nicely after that, at least the utility didn't break anything and I'm sure it cleaned up some of the mess. GL

Another term to Google: "KUC Update Checker". It's much more than a list! GL

Oh yeah... The utility that was formerly known as tool and it made a funny acronym. GL

It looks like PNG. Try opening it in image viewer. GL

I'm not that familiar with drivers, sorry. I hope someone else can help you. Usually I just slipstream the storage controller drivers, and others manually post-install. And I don't have X58 class hardware, so I don;t know if there are any other requirements. .Net isn't required for windows itself. GL

They are not, I guess they meant it's a setup for that update/hotfix. I didn't know if the setup for .Net has a KB number, so I googled these two, and they are hotfixes/updates, not the setup of .Net. GL

I didn't see the setup for .NET, just hotfixes (if the KB numbers are right. Of course, if it doesn't work, change it to DISABLED or any other state it allows. GL

There's not much to go wrong in your session, just a few thoughts: 1. Too many drivers? Try installing just the ones you need (but you cant' do without ICH10 & Marvell at least). 2. Try moving the IE7 and .Net installers to the top, so that they will be installed first. I don't see any installer for .Net, but haven't looked very hard. I don't know if IE7 (and .Net) are able to be slipstreamed, or you would have to use addons. Check that. 3. Try not to work on Windows 7. *After your edit: It usually is USB legacy mode in BIOS. GL

To quote myself from a recent post, very rarely will nLite totally break something, even with many things removed. Most often the reasons are external - unclean source, double processed source, working under Vista/7, antivirus meddling... For your situation: yes, ACPI can be directly related to shutdown problems. It might be the hardware (too old, broken, misconfigured in BIOS or somehow incompatible with XP). Otherwise, you don't really remove anything, so nLite shouldn't be the problem. Does the same thing happen if you install from your unmodified source? * Edit: and I also see you're setting a custom resolution. Try without that. Also, try to avoid working with nLite under Windows 7. GL

Yeah, very rarely will nLite totally break something, even with many things removed. Most often the reasons are external - unclean source, double processed source, working under Vista/7, antivirus meddling... And yes, I meant after installation. I also noticed it's not good to make too many changes to the "services" tab in nLite. Maybe it's Windows that's not happy, but... Glad you made it work! GL

Now I really don't see anything that would create these problems. Maybe the source is tainted somehow or the fact you're working under Windows 7. GL

Just some thoughts, maybe not related to your issue, but then again, maybe yes. - Maybe it has something to do with nLite working on Windows 7. It should work since you're not slipstreaming service pack, but it's kind of uncharted territory. It's not definitely known what kind of errors can occur. - Things I don't remove (in theory they should create no problems if removed, but I decided a long time ago, mostly by intuition and observation, and without any solid proof, that they are better left alone): Auditing Resource Dlls Extensible Storage Engine (Esent97) Help and Support (*) Input Method Editor (**) DNS Client (*) Internet Authentication (IAS) (I'm not sure I have it and/or is hidden by my compatibility options) Message Queuing (MSMQ) (*) Network Location Awareness (NLA) (*) Performance Logs and Alerts (*) Protected Storage (***) Task Scheduler (*) TCP/IP NetBIOS Helper Text Services Framework (**) Uninterruptible Power Supply (*) Universal Plug and Play Device Host (*) WebClient (*) * I disable the service afterwards ** because I need Office *** I set the service to manual afterwards I'm not saying you should do exactly like me, but believe me, I also would like to have these things gone. However, through experimenation and countles fails I have concluded they are better left alone. And it was such a long time ago I don't even remember the reasons for some of them. But everything is working as expected, and I even have the Remote tab which I promptly unregsvr32 after installation. * Edit: From NETWORK I would deselect just NetShell Cmd-Tool and Network Setup Wizard, all others seem OK to me. About SERVICES I wrote above, and from COMPONENTS i would deselect Ethernet (LAN), Printers and Wireless Ethernet (WLAN), just in case. GL

1. See the announcement in red letters above (attach, not paste, your last session.ini) 2. Tell nLite not to load last session on startup. While starting a new nLite session don't reuse the files, re-copy them from your source media. GL

Hi and welcome to the forum. Since there are many questions, and to help the discussion a little, let me answer those I know the answer to. 1. By disabling SFC, either in nLite or afterwards (by patching DLLs), but you will also lose the "protection" SFC offers. Search this forum for SFC. 4. You don't have to, but it would be good if you do. Many programs rely on IE engine for various things, less so on WMP (maybe codecs), but it wouldn't hurt to have the latest bugfixes. Especially IE files are used system-wide (shared with Explorer in certain circumstances), so I'd say install the latest you can (IE8+updates), but don't use it if you don't want to. 5. It's up to you to decide. I personally love them all and view them as a method to deliver higher version files (mostly DLLs) to my computer. 9. That's Photoshop's problem. Maybe reshack Photoshop, but I think it has self-protection. GL

Ah, you're talking about UPB (Universal Parallel Bus)? GL

More than you ever wanted to know or read GL

Don't know about changing password, but you usually can't run Administrator account unless in safe mode. That's why it's called XP Home. GL

I concur with everything Sp0iLedBrAt wrote. IE8 and .Net need to be installed as addons, which usually contain most of the updates. You can find some on RyanVM's board. Your issue is definitely caused this update: WindowsServer2003.WindowsXP-KB2567680-x64-ENU.exe (64-bit version of Winsrv.dll). Don't know how NLite let it integrate for another architecture. Remove it and download the 32-bit version. You also have WindowsServer2003-KB930178-x86-ENU.exe which is the same file, just older version. I didn't check other hotfixes, but this tells me you might have other duplicates. You might want to try fdv's 2003 Server hotfix list that contains no or very few duplicates. It is important for 2003 not to have too many (I think over 300) catalogs in Catroot folder because it will break. One hotfix=one Cat file, sometimes more. XP also had (has?) this limitation, but one hotfix claimed to fix that. ^ I'm writing this from memory, so it's definitely not very accurate, but nevertheless, it's a good practice not to have duplicates, they are useless anyway. And don't clear page file at shutdown, it's also useless. GL

No it's not. Why, any thing wrong in there? If you had defined a network connection previosly and if it gets populared after a while, it's a sign you need to set to Automatic one or more of the following : RasAuto, RasAcd, RasMan, TapiSrv . It (the network) will work anyway, but there might be pauses on boot and other subtle problems. Maybe could be the reason for your Firewall problem. For now, you can remedy most of it if you go into Network Connections folder, wait until it gets populated, then open Services.msc and see what manual services have started, set them to Auto. If you had not defined a network connection before, disregard this (but then why would you need a firewall ) GL