Camarade_Tux

HFNetChk has two big advantages : -it doesn't rely on so many services as MBSA (AutoUpdate & Co) -it doesn't report a hotfix as being missing when the targeted file does not exist (because it has been deleted) So HFNetChk is far easier when you use nlite of HFCleanUP imho.

Thanks. I've recently checked the MSFN's forums for that and similar pages exist but they are simply less usable or advanced and the adress is easier to remember.

I totally agree with you. I have started something similar. You can find the link in my sig. Also, I've taken a look into DAF and I had a similar approach to restore BITS and some other components. But DAF is far more complete. And using such things is not being lazy, it's simply the best way to get some components back. edit : the link : http://www.uawiki.org/doku.php?id=wxp:reduce:restore

Just don't remove Battery in Hardware Support. Then, no difference. Just don't forget to install all drivers.

As far as I'm concerned, I use CDBurnerXP and have the IMAPI service from XP removed. :?

It's hard and long... However, reshacker accepts directives files (or so). Once the file is written, you just run reshacker with the switch telling it to use a directives file. It will do everything that is needed (CPU consumming but not to long) XPize works just the same way, but not in the same sections. This is not an overwrite (visual mods used to but all use reshaker now). Btw, I'm using Xpize right now. Not that much I think.Lots of things still have to be put in the registry. But I think visual tweaks could probably be applied by modding shell32.dll. And maybe many others. It's too beta right now and the posts here are probably enough if you want to experiment (if not, tell me). Once it is proven stable, doable and usable, I can post a few files for reshacker that will do all the work (WMP, CDBurning, Time, AutoPlay, file associations and open with menu). And, btw, once extracted from the registry, the AutoPlay thing takes 48KB on its own. It's a lot and not much at the same time. Not much compared to the size of the registry (approx. 0.25%). But a lot because it is a stupid, simple thing that is repeated many times.

Good idea. But, this : "UNA Trojan.Win32.Autoit" makes me think many AVs just classify all AutoIt scripts as dangerous. One should try with a script such as : "MsgBox, hello world!". :/

I just finished a first pass for shell32.dll. Best seen in Notepad++, with C as a language : This can be used in 2 ways : -editing shell32.dll's REGINST section with Reshacker -editing the registry after installation (in fact starting at T-13 afaik) Also, this shows which settings cannot be set before T-13 because they will be overwritten. Everything musn't be deleted. I fully realized there was a lot of things that were needed. I also understood it would be interesting to have them listed (visual tweaks especially). Also, important : the shell32.dll I used is the latest available for XP SP1a. Some things may have been added or removed (1). I think I've sorted 40% of the REGINST section at this moment. (1) I guess that when installing a service pack, the installer first calls "regsvr32 /u *.dll" to clean the registry, and then it uses "regsvr32.dll *.dll". regsrv32.7z

Thanks. I was starting to wonder if anybody could find this interesting. Reading so many lines is pretty hard but it lets you learn new things, such as how to change which infos are displayed in dialogs such as this one: Also, I've just found more Autoplay things (the dialog that pops up when you insert a CD in your drive).

Try with a dummy advpack.dll (just launch notepad and save a blank file as advpack.dll). It *may* work.

Quick question: will xp sp1 still be supported in hfslip when microsoft ends support for it? As far as I'm concerned, I think HFSlip for XP SP1 should be put into another cmd file. There is no need to keep it in the main code since there shouldn't be any new update. (and I am still runnning XP SP1)

Untested, taken from XPize Settings (Regshot). 32 pixels HKCU\Control Panel\Desktop\WindowMetrics\IconSpacing: "-1275" HKCU\Control Panel\Desktop\WindowMetrics\IconVerticalspacing: "-1125" HKCU\Control Panel\Desktop\WindowMetrics\Shell Icon Size: "32" 48pixels HKCU\Control Panel\Desktop\WindowMetrics\IconSpacing: "-1371" HKCU\Control Panel\Desktop\WindowMetrics\IconVerticalspacing: "-1371" HKCU\Control Panel\Desktop\WindowMetrics\Shell Icon Size: "48"

It's clear BoldFortune's lists has some nice aspects, especially with functionnality. He clearly establishes what is needed for which app. Moreover the file approach is more precise than the nlite component one but I don't know how BF manages with services. :.? And it's a pity he did not put that in a central place so you immediately know the consequences of removing a certain file. (that's what I tried to do on the wiki page) From a practical point of view, we can.Then, would we be allowed to ? Even if he stated his guides were freely available, I think we have to respect the author. I mean, someone makes project to reach a goal and licenses it under GPL or BSD and then someone uses the code to reach the opposite goal. This is allowed but not really respectful. Afaik nuhi and BoldFortune are not the best friends in the world. However, this has happened before I arrived, so I can't say much things. (you may search the forum). HFS...

I think they are just the sames. MS says : 'Use Windows classic folders.'(1) or, 'Show common tasks in folders'(2) In folder options, As far as I see, there is no difference at all.

About XFCE, I find it fast, light, smooth, clean. That's why I love it. But it's clear KDE has more libs and functions.

32 bit icons ? 32bits of colors ? Are you sure you don't want 48pixels by 48pixels ?

Especially cool. Thanks.

But it's clear! classic view: http://www.microsoft.com/windowsxp/using/s...ew/folders.mspx common tasks : http://www.microsoft.com/resources/documen...b.mspx?mfr=true classic view : Common tasks: The difference is so obvious : on the common task page, there is no screenshot !

So, if I use waaa But I still wonder why Yzöwl was able to write them without actually getting the codebox :? , I should get a nice thing ? edit, OK, I do. edit2: it would be better if it width was maximal.

You're victim of something called "mirage". Consult your ophtalmologist quickly or you will loose the ability to see shells... And moreover my glasses are broken. (girls are sometimes dangerous, especially when they want smack you, and suceed!) ++ Didn't see, I'm blind. Also, back to the topic. I don't have 'toshop, so I used Picasa (which I didn't have before btw) http://xs102.xs.to/xs102/06254/collage11.jpg (removed because collage was not good in fact) The bad thing is I have a wide screen and this soft only takes 4/3 images I think. Also, I really enjoyed fatlwoomera's desktop : http://www.msfn.org/board/index.php?s=&amp...st&p=521843 (btw, fatalwoomera, what's your VS ? I find it so simple and nice) and grunth0s : http://www.msfn.org/board/index.php?s=&amp...st&p=522452 dagonet : http://www.msfn.org/board/index.php?s=&amp...st&p=518282 pS- : http://www.msfn.org/board/index.php?s=&amp...st&p=515684 Echolomax : http://www.msfn.org/board/index.php?s=&amp...st&p=515392

What is it with you bringing back old threads and webcam support. Two topics and no one has given you the walkthrough, because there IS NO walkthrough. Redo your ISO. The time you spent searching for these dead threads could have been spent doing just that. If you dont like me brining back old threads then why dont you do your job and simply delete them if there useless then why have them clogging up the board? I also cant redo the Iso as I did not make it And you know an iso is especially bad and untrustable when the "last session.ini" has been removed.

There's a way... I don't know it.

Quickly, what can be done in shell32.dll : -get rid of remanent WMP, CDBurn, Time Service entries. -remove search from My Computer and My Documents (each take 5 lines in the dll) -modify the webservice Windows uses when trying to open an file with an unknown extension (takes 3 lines) -play with context menus, labels and titles And now, what I found in a few minutes: Format is : Componant{ .dllname.[sectionname] data1 data2 CDBurn: Burn{ .Shell32.[RegShellNamespace]{ HKCR,"CLSID\%CLSID_CDBurn%\%EXTVIEW%\%VID_WebView%" HKLM,"%PATH_EXPLORER%\CD Burning\Handlers" HKCR,"CLSID\%CLSID_CDBurnFolder%",,,"%DESC_CDBurnFolder%" HKCR,"CLSID\%CLSID_CDBurnFolder%\%IPS%",,%REGEXSZ%,"%_SYS_MOD_PATH%" HKCR,"CLSID\%CLSID_CDBurnFolder%\%IPS%",ThreadingModel,,Apartment } .Shell32.[RegShellObjects]{ HKCR,"CLSID\%CLSID_CDBurn%",,,"%DESC_CDBurn%" HKCR,"CLSID\%CLSID_CDBurn%\%IPS%",,%REGEXSZ%,"%_SYS_MOD_PATH%" HKCR,"CLSID\%CLSID_CDBurn%\%IPS%",ThreadingModel,,Apartment HKLM,"%SHLSVC_DELAY%","CDBurn",,"%CLSID_CDBurn%" HKCR,"CLSID\%CLSID_CDBurn%\MergedFolder","Attributes",,"0x0" HKCR,"CLSID\%CLSID_CDBurn%\MergedFolder","AttributeMask",,"0xffffffff" HKCR,"CLSID\%CLSID_CDBurn%\MergedFolder","Location",,"@shell32.dll,-12589" HKCR,"CLSID\%CLSID_CDBurn%\MergedFolder","ConflictOverlayIcon",%REGEXSZ%,"%_SYS_MOD_PATH%,-232" HKCR,"Drive\shellex\ContextMenuHandlers\%CLSID_CDBurn%",,,"" HKCR,"Drive\shellex\PropertySheetHandlers\%CLSID_CDBurn%",,,"" HKCR,"Drive\shellex\FolderExtensions\%CLSID_CDBurn%",,,"" HKCR,"Drive\shellex\FolderExtensions\%CLSID_CDBurn%","DriveMask",%REGDW%,0x20 HKCR,"CLSID\%CLSID_CDStagingFolder%",,,"%DESC_CDStagingFolder%" HKLM,"%PATH_EXPLORER%\CD Burning\ExcludedFS","UDF",, HKLM,"%PATH_EXPLORER%\CD Burning\ExcludedFS","CDUDF",, HKLM,"%PATH_EXPLORER%\CD Burning\ExcludedFS","CDUDFRW",, HKLM,"%PATH_EXPLORER%\CD Burning\ExcludedFS","UDFREADR",, HKLM,"%PATH_EXPLORER%\CD Burning\ExcludedFS","UDF1.50",, HKCR,"CLSID\%CLSID_CDStagingFolder%\MergedFolder","Location",,"@shell32.dll,-12590" HKCR,"CLSID\%CLSID_CDStagingFolder%\MergedFolder","Attributes",,"0x8000" HKCR,"CLSID\%CLSID_CDStagingFolder%\MergedFolder","AttributeMask",,"0xffffffff" HKCR,"CLSID\%CLSID_CDStagingFolder%\MergedFolder","DropEffect",,"0x2" HKCR,"CLSID\%CLSID_CDStagingFolder%\MergedFolder","DefaultOverlayIcon",%REGEXSZ%,"%_SYS_MOD_PATH%,-231" } } WMP: WMP{ .Shell32.[RegShellObjects]{ HKLM,"%PATH_EXPLORER%\WMPInfo","verb",,"WMPBurnAsAudioCD" HKLM,"%PATH_EXPLORER%\WMPInfo","CLSID",,"{8dd448e6-c188-4aed-af92-44956194eb1f}" HKLM,"%PATH_EXPLORER%\WMPInfo\FileExts","MP3",, HKLM,"%PATH_EXPLORER%\WMPInfo\FileExts","WAV",, HKLM,"%PATH_EXPLORER%\WMPInfo\FileExts","WMA",, HKCR,"CLSID\%CLSID_WMPExtension%",,,"%DESC_WMPExtension%" HKCR,"CLSID\%CLSID_WMPExtension%\%IPS%",,%REGEXSZ%,"%_SYS_MOD_PATH%" HKCR,"CLSID\%CLSID_WMPExtension%\%IPS%",ThreadingModel,,Apartment } } Time: Time.Shell32.[RegShellNamespace]{ HKLM,"Software\Microsoft\Windows\CurrentVersion\DateTime\Servers",,,"1" HKLM,"Software\Microsoft\Windows\CurrentVersion\DateTime\Servers","1",,"time.windows.com" HKLM,"Software\Microsoft\Windows\CurrentVersion\DateTime\Servers","2",,"time.nist.gov" } Now, you have to know all needed CLSIDs are also written in the same dll. Parts of Mine: CLSID_CDBurn = "{fbeb8a05-beee-4442-804e-409d6c4515e9}" CLSID_CDBurnFolder = "{00eebf57-477d-4084-9921-7ab3c2c9459d}" CLSID_CDStagingFolder = "{00da2f99-f2a6-40c2-b770-a920f8e44abc}" CLSID_WMPExtension = "{f83cbf45-1c37-4ca1-a78a-28bcb91642ec}" PATH_EXPLORER = "Software\Microsoft\Windows\CurrentVersion\Explorer" (of course, it's not the format that can be found in the dll, but it's easier for me to maintain something like that) This is a quick list of reg keys that are present on your computer though you removed the corresponding components with nlite. Now, why not delete them ? (make a registry backup first, I'm not responsible of any damage. ) I hope you now want to get rid of this. This list is far from being complete but I'll work on it.

I think you used img tags. Didn't you ? I don't. And on wikipedia, in the See Also section, I stumbled on:

Hey guys I thought I could share some things I found in the last few months. Today is regsvr32 fun. And more especially, regsvr32 /s fun. You probably know dlls can be registered with a command like that one: regsvr32.exe file.dll And you probably know the /s switch makes this operation silent. Now, you certainly know all dlls can't be registered. And the vast majority will fail with this error : So what's the difference between dlls that can be registered and others ? I don't know the whole thing. However, I know that dlls than can be registered have a REGINST section in ResHacker. But, wait, it's strange. The content of this section reminds me of something. Registry ! Next, something I noticed thanks to nlite. I had no time to make a setup billboard for XP and those "ads" do nothing than getting on my nerves so I used nlite's "classic setup screen". One nice thing is this gives you much more information on what windows installation is doing. One stage that struck me had to do with registering some things. At first, I thought it registered COM objects. However, newer WinUBCD show a similar stage with GuiRunOnce and afaik COM is removed from these installs. Meanwhile, I also played with Resource Hacker and shell extensions that need to be registered to work. I don't know how, one day I understood what was happening : during installation, windows calls regsvr32 /s and registers a number of dlls. As far as I saw, this is a pretty heavy operation and explains why this stage is so long to complete. And ...? What it implies: A number of settings is set and this explains why some parameters can't be found in hives but are present at the end of the installation. It overwrites already present keys afaik. That's probably why you Removing dlls from installation CD will result in smaller registry even if hives stay untouched. Since nlite doesn't modify these files (really hard to do) you will be getting strange entries in your registry. For example, when you remove CD Burning, you still get corresponding entries such as HKCR,"Drive\shellex\ContextMenuHandlers\%CLSID_CDBurn%",,,"" Same applies to WMP. I'm certainly not the first to understand that but I never found such a post and thought it would not be a bad idea to write it. Moreover...