Introductory guide for Windows customization II


Recommended Posts

This is an updated and reworded version of my w2k guide, this now applies to both w2k and xp

The introductory guide to customization.

First you need to collect your tools, Im going to recommend some of my favorite:

Resourcehacker: Your resource hacker (or modifier), your best friend here, url: http://www.users.on.net/johnson/resourcehacker/

Toolbar control: With this tool you can change easily the toolbar background bitmap and the Internet zones properties, very cool, url: http://www.virtualplastic.net/html/down_app.html

Jasmin 3D Color changer: The best color modifier available, url: http://jotenet.idealscience.com/temp.asp

Color schemes for Jasmin 3D Color: http://f1.aaacafe.ne.jp/%7Epassage/ and http://www.skinnables.org/3dcc.php

Tclock light: The best program when you need to modify your taskbar, url: http://homepage1.nifty.com/kazubon/tclocklight/index.html

Longhorn systray clock: longhorn systeray clock, url: https://www.neowin.net/forum/index.php?&act=ST&f=34&t=157465

Replacer: Replaces your system files, url:http://www3.telus.net/_/replacer/ it helps you to replace your system files

Windowblinds (This is optional for windows 2k systems): url: http://stardock.com

Now, you have all the necessary and basic tools to start your modification (ALL FREEWARE) , so lets start:

The first and the easiest part is to modify the files that control almost every piece of visual in the W2k box: explorer.exe located in x:\windows\ (x is your harddrive letter, also, take note that the windows dir can be winnt), shell32.dll located in x:\windows\system32\, and browseui.dll located in the same directory, copy these files into your reshack directory (COPY THEM, NOT CUT THEM).

To modify the files you need resourcehacker, open the files with reshack and start to browse the folders list, you can modify the icons, the bitmaps, even the menus and the text.

Once you finish your modding you need to save (IF YOU CHANGED AN SCRIPT THEN MAKE SURE THAT YOU PRESSED THE "COMPILE SCRIPT" BUTTON FIRST IN EVERY STRING), the program itself kindly make a copy of the original file first, if you screwed up the original.

Now, you need to replace the files, for that I use "Replacer", here is an explanation of the app, copied from its website:

Basically, Replacer works by using a combination of tools to successfully replace a protected system file, without disturbing the user. First, three files are extracted from the data file into a temporary folder: db.csv, Clear_WFP_Message.vbs, and zap.exe.

The CSV file contains a list of replaceable system files, along with their paths and attributes.

Clear_WFP_Message clears the Windows File Protection message that may pop up after replacing a file. Some anti-virus programs may incorrectly detect this as a malicious cript. Access to this file is not required, but it is recommended. After replacing, the script will continue to run for about 15 seconds, to ensure that it doesn't miss any late messages.

Zap.exe, a tool from Microsoft, forcefully deletes the system file. This may leave temporary files on the root of the drive (named _@??.tmp), which will be automatically deleted after rebooting.

Second, after the user inputs the files, a backup is created. It is stored in the same folder as the system file, with a "backup" extension (such as "notepad.backup"). Then, the replacement is copied to up to five directories which contain backups of the system file.

Finally, the VBScript is executed to clear any messages, and the system file is replaced. If Replacer is closed properly (following the on-screen instructions), the temp folder that it uses will be automatically deleted. Otherwise, manually delete the folder called ".ReplacerTemp" in Replacer's folder.

If you are experiencing constant errors, or are running Windows 2000, you may need to download the components package. In most cases, this is not required.

Tested, but use at your own risk.

There is a lot of tricks to modify your system files to a certain degree, so Im just going to post a couple of links that will help you to succed with this:

http://wint.virtualplastic.net/

http://virtualplastic.net/

For system files locationes there a very good list here:

http://www.virtualplastic.net/html/hacklist.html

In there you can find what file do what in your system.

Thats the end of the reshacker tutorial, lets go to the rest of the tools:

Toolbar: Great tool by beaker (member of the virtualplastic.net crew), very easy to use, just select what do you want to modify, select your bitmap, click apply and restart the explorer.

Jasmin 3D: very friendly, its like the default color manager in windows, but his allows you to change every little pixel in the colors, just open the app and start modding or simply open a Scheme file (.3dc).

Tclock light: This have a lot of options, but is very easy to use, so this doesnt need a tutorial, just run it, then your clock change, right click on the clock and select tclock2 properties, have fun.

Longhorn systray clock: An utility based on tclock light that haves the basic functionality of tclock light and also it lets you cutomize your clock to make it looks like the longhorn one (note, dont try to run this app with any tclock version)

Windowblinds: a great system skinner, if you do some research you can find awesome minimalistic skins, like the ones made by essorant: http://www.essorant.com/

Here's an example of what you can do with a little work:

Windows XP

Windows 2000 (ss1, with windowblinds)

Windows 2000 (ss2, just heavily modified)

Can i ask which themes/etc you have used in this http://www.timdorr.com/saintdark/2k1.jpg to get it looking so god damn awsome, i'd like to know thanks :).

/Primie

to be honest I dont remember the name of the theme, but its on the essorant website at the end of my post

  • 4 weeks later...
  • 1 month later...
  • 1 month later...

I've reshacked explorer.exe, logonui.exe, ntoskernel.exe, shell32.dll and some others without any trouble, but when it comes to reshacking luna.msstyles, WinXP will not accept it unless I have styleXP installed. I've patched UXTheme.dll and I assumed that my modified luna would be acceptable, but after uninstalling stylexp, my Luna still wasn't acceptable, even after changing anything that said Microsoft in it. Any help please? I'd rather not have styleXPservice taking up memory. Cheers.

/edit: by the way, my desktop looks like this after using ResHack.

tskmgrsmall.jpg

  • 2 weeks later...

hmmm, sanctified, could u plz give a full guide on how to make windows xp look like ur screenshot? I REALLY LIKE UR LOOK! i got lotsa stuff done to my xp, but i need to know how to edit the run dialog (i know its thru reshacker, but i dunno how to edit the one that comes with windows) and also which theme you are using and how you make your explorer so minimalistic! (oh ye, and what icon set ur using. i use smoothmetal + novola, but im bored of the eye candy tbh)

  • 4 weeks later...

For everyone asking, he made his desktop look like that by reshacking explorer.exe. There are guides on how to do this along with other xp hacks on www.virtualplastic.net which he provided.

I'd like to know where I can find that desktop wallpaper sanctified used. Wow.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!