GrofLuigi

It's SpeedStep (EIST). Turbo Boost is on top of that. Congratulations on your new machine! GL

I can't see anything that would prevent it. It would help if you clarify what you mean by "Internet connection". Isn't it coming through the Local Area Connection? Also, maybe you need to enable/install/configure something in VirtualBox. GL

I think it's not possible using ONLY regedit. My Computer, My Documents, etc. are shell folders built in to Windows (Explorer). You can't navigate IN/OUT of an Excel document or INTO/OUT OF the Excel program in Windows Explorer*. Think of what would happen with unsaved work, for example. Besides, the place you mention is just controlling what to hide/show on desktop. The place where one would put a CLSID (if it's possible) would be HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\DelegateFolders (with or without the last part). or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace (in control panel) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\DelegateFolders (in My Computer) (with or without the last part). Microsoft Office 2003 CLSID's start around HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{00020810-0000-0000-C000-000000000046}. If you are dead set on making a try, you may place some of them in the above mentioned places and see what happens. Who knows, maybe we'll find something new. You'd have to find the main CLSID of Excel (there are several of them for several types of documents). GL * If not using OLE and/or Shell Extensions

That's so sad May she rest in peace

Hello, Your last session.ini indicates that nLite didn't change anything it shouldn't have. I think it changes some small things behind the curtains, but they shouldn't have such serious consequences. I would be more suspicious of the source disk (Dell reinstallation disk) as it's unknown (to nLite) what and how much differs from original disks from Microsoft. Also, I would place the drivers in a shorter path (example: c:\drivers), just in case, but it's unlikely that that is the reason. To be sure, you can try manual integration (note: I haven't tested it, but it looks like that should be it. Around there you can also find instructions for creating a bootable CD). GL

KRH, Yes, it was an example copy/pasted from my user.js (you access it through about:config, it's the same thing). I suggested the three lines above because they gave me rock solid download directory for my needs (fixed), whereas before FF was also 'forgetting' where it was. My idea was for you to set it to the starting directory you want and then just toggle the "ask me every time" thingy in preferences (which I think is the browser.download.useDownloadDir line in user.js/about:config). As I said before, I don't know anything about KernelEx, I'm talking about 'normal' usage of Firefox. @rloew: definitely ajax.googleapis.com (that's where some javascript libraries used by IPBoard are hosted). I block it in hosts file and the panel can't retract. Unblock it, panel behaves. Or, in your case, IE doesn't like it that they are hosted on another site or it has general javascript problems. GL

1. Edit/check user.js with the following lines: user_pref("browser.download.defaultFolder", "C:\\DOWNLOAD"); user_pref("browser.download.dir", "C:\\DOWNLOAD"); user_pref("browser.download.lastDir", "C:\\DOWNLOAD"); I think the (default) location might change if you toggle download mode (download every time to this dir/ask every time...). This is general, I'm not taking into account any oddities of KernelEx or the OS. 2. Unblock ajax.googleapis.com in hosts file/firewall or live with it or persuade administrators to abandon it (tough chance ). *edit: If the box is empty, then maybe it's general javascript issue? GL

For the first two, no. GL

I don't know anything about the program, but I can offer you an answer to your first question: You need to make the package non-advertised, if the program allows it. In case you ask, I don't know how to do it in any other program too. But it's an annoying feature of MSI that comes around often. GL

Clean source is original CD from Microsoft, not OEM (most of the time they work, but you never know) or obtained from some questionable source (so you don't know if someone modified it). Running nLite again on the same source (the resulting folder of the first run) is better avoided. It works fine with simple operations, like slipstreaming a service pack first time, but there were many reports of unexplained problems. So you should take special care if you want to integrate .Net, WMP and IE8 addons - they must come first before their updates (if any). Reorder them on the Hotfixes and Update Packs screen. Making a first run with them might also work, but according to the reports I've seen on the forum, has less chances of success than doing it all in one go. Finding good addons is essential. Forum user -X- has a good page on updates. There are also all kinds of addons on this board and over at Ryan's. GL

Hi, It coudn't possibly be nLite's fault because it does nothing special - it's just the updates. I see you have updates for .Net, WMP and IE8, but where have you integrated them? You need to integrate them before. Search the forum for addons (some/all of these three cannot be integrated directly into SP3 by nLite). Also, some WMP updates are problematic (depending which version you have in the source - nLite just picks the highest version), so they too need to be taken care of. Always assuming you have a "clean" source and it's better to not use nLite more than once on the same source. MSVBVM60.dll update, AFAIR, was different then others (it lacks some of the information regular hofixes have). I just replace the dll after install without problems. In any case, it shouldn't pose any significant problem, whatever you do. And by the way, it's lsass (Local Security Authority SybSystem), small letter L. But the error is serious. GL

Extract and read the update_SP3QFE.inf (or update_SP3GDR.inf). For example, in KB2483614 (i only have that currently) there are those lines: [PreReq.RDC7.IsPresent] PresentOp= CheckFilever, System32.files, mstscax.dll [PreReq.RDC7.IsRightVersion] GreatOrEqualOp = CheckFilever, System32.files, mstscax.dll , >= , 6.1.7600.16385 LessOp = CheckFilever, System32.files, mstscax.dll , < , 6.1.7601.0 *Edit: it is confirmed in your log file: GL

Stupid of me to try to find logic with Microsoft. I just set it to 2 and enjoy. As for my list of low risk file types, it's much much longer than that. I try to include every possible filetype I have on my HDDs. Why? Because this "feature" isn't a real protection, just an annoyance. GL

. I've never seen such a line in any of my builds. Hi, Kurt_Aust It's the second checkmark. Very useful, if you ask me (applies only during working with NLite). (Image courtesy of -X-) GL

WMIDiag probably would have helped. GL

Everyone is welcome to comment about: - eventual experiences with this on a live system; - list of other dlls that contain REGINST, if any; - recommended program(s) (resource hacker? Is there anything else more reccomendable?) - how to deal with windows updates later on? (unfortunately, IE cumulative updates are the most frequent produced. My concern is that there will be a time frame when the dlls will be able to re-register themselves). GL

@CharlotteTheHarlot: You're preaching to the choir, really. I am that kind of person that does ProcMon boot traces (multiple times) for no apparent reason other than to find out what's hiding inside the box. I also know about Asprotect and its annoyances. On the bright side, I found what I was looking for. Where else than on FDV's site (Step 17). Now all that is left for me is to organize myself and get to work. GL

I'm pretty sure if I denied SYSTEM account access to the whole CLSID branch, bad things would happen. Besides, it overrides. Example: Winlogon doesn't respect permissions to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Credentials HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceCurrent and overwrites them whatever they are. But that's another question. GL

Thank you for your reply. I am quite familiar with both methods and use them very often. Actually, I never ever start any exe that was not used previously on my system without monitoring changes (method 1). Using Total Uninstall and/or Regshot Unicode. And often I examine what the new program wants with method 2. Many interesting things to be learned there. But this situation is different. If I were to use method 1, I should first deregister everything (probably just delete regkeys CLSID, Interface, Typelib in HKCR). And then Windows won't work on reboot. I have seen it a long time ago when a registry cleaner deleted HKCR/Interface. Windows was unusable and only reinstall helped. Also, method 2 wouldn't help if they weren't deregistered because I think Windows (sometimes?) doesn't bother writing the values if they are present, so I couldn't be sure that, if I isolate writes, I will have complete list. What I want to achieve is to have partial or selective registration of COM objects, and in many places I succeed. For example, I delete few functions of urlmon.dll (roughly four out of ten) which I think are non-essential for my needs, but provide some speedup because urlmon is invoked in EVERY explorer operation. At the same time, if I deregister it completely, many things don't work (IE for sure). Also everything related to Search Assistant, but I don't touch other functions of that dll (I forgot which one was it, but it was pretty essential, like browseui.dll or shell.dll). There is no way I could get away with full deregistration of that. The above two examples are harmless because they are not re-registered on every boot, but some others are. I don't have many examples, but one of them is this (regsvr32 actxprxy.dll). Of course it's a placebo, but I've tracked the changes (Method 1 ) and after a reboot the changes are reverted by shdocvw.dll which also contains list of other potential re-registration components. I'm just asking for a way to make them humanly readable and/or prevent them. Also, I'm asking if there are other dlls and which are they. This example is actually easy to keep under control permanently with permissions, but there are some functions that I don't want to reappear, and I can't place permissions on non-existing objects. I'm sure this issue has been discussed before, but it might have been a long time ago, and I don't think a definitive solution was given, or I'd be using it right now. But my memory might be failing me, or I have decided against (patching?) because it would be reverted by hotfixes, but now they are not so frequent for XP, so that reason could be crossed off. GL

Hi, This has been mentioned somewhere, but I can't find it. What I'm looking for is a list of CLSIDs/Interfaces that Windows (mostly IE libraries) register in every session (on boot?) and a way to selectively prevent some of them from being re-registered. Even by patching/reshacking if needed. GL

Maybe, but the cause is still not fully determined. Maybe post an Autoruns or HijackThis log to see if there's anything obvious. GL

If I understood you correctly, that points to the drivers. See this topic if you haven't already. I don't have much experience with Nforce 4. GL

Nothing obvious. Just the usual suspects: the fact that it was prepared on Windows 7 or the "cleanliness" of the source or drivers/addons. GL

If the file you received is .zip, enter the password you received when the unpacker asks you to. I use WinRar, don't know how others behave. Or you could download it from here. Then, you need to unpack the .exe with parameter /x or -x (sorry, I forgot the exact parameter). I use Universal Extractor for that. Than you need to apply Universal Extractor again to the .msp file. You will get the .ttf files and you install them normally. If they don't want to install, I'd find a way to forcefully replace them in Windows/Fonts and just open that folder in Explorer. If you have Office 2007 installed, you just install the .msp or .exe. GL

As far as I know, it restricts the number of icons in the cache, not its size in kilo/megabytes. I once counted on a computer with many programs installed, it had around 500 icons. GL