XP Theme Source Patcher: FAQ
1) How do I install this package?
There are two method to install the XPtsp theme packages. The first method is to perform what we
call a Live Install, which is integrating the changes into your running operating system. After
integrating the changes, a reboot is required in order to finish replacing the necessary files.
The second method is to perform an Integration into a installable copy of your operating system.
This involves copying the install source to the hard drive and running the patcher on that source.
This will change the source so that when installed, all of the resources will be of the integrated
XPtsp theme source.
2) What operating systems are supported?
The XP Theme Source Patcher was originally designed to work with the 32-bit versions of Windows XP
Home Edition, Professional and Media Center editions, Service Pack 2 and higher. Gold and Service
Pack 1 support was added later.
Beginning with v18.104.22.168, experimental support was added in order to perform the same modifications
to Windows 2000, Windows 2003 (all editions), and Windows XP Professional x64. Problems during testing
of Windows XP x64 have come to light with integration to that OS and little work has been done to date
to resolve those problems.
3) Can I uninstall the resources that this program installs?
When the resources are integrated using the Live Install method, they are uninstallable via both the
XPtsp Control Panel applet and the Start Menu shortcut. If you have performed an Integration into a
XP source folder, then the changes cannot be undone, as the original files don't exist in that source
4) At what point should I integrate the resources?
The XPtsp theme packages should be integrated LAST, as the patcher replaces a lot of files.
Failure to observe this rule will cause the patcher to have to patch the changed files after OOBE
(Out of Box Experience), which may require a lot of time and render the computer unusable until
it finishes patching those files.
5) How fast does this patcher work?
I have seen patching time around 8 minutes for a source integration without Media Center
components. Live install takes about 6 minutes. I'm still working on gathering the times
for other scenarios.
6) Can I install this as a SVCPACK add-on to my source?
The patcher wasn't designed to be run that way. However, I don't know of anything that would prevent
it from running correctly during the SVCPACK phase.
7) What languages are available for the GUI?
At present moment, the only language that the GUI supports is English. If you feel up to
translating the English.ini file into your own language,
please feel free to do so. You may submit the new language file through the forum and it will
be included in the next version.
8) Why can't the programmer supply translations?
Well, I only speak/read/write English. I've tried using the Google translation service in order to
convert the English DSI language file into other languages and was told by some people that they
would rather read good English than a bad translation....
9) What languages are available for the resources?
All resources come only in English. However, the versions starting with 22.214.171.124
have the ability to translate the resources into whatever language that the source files are
in. It should be noted that it has been tested with a Dutch copy of Windows XP.
10) Does the patcher require .NET Framework?
Absolutely not! There is no requirement BY THE PATCHER for any of the .NET Frameworks.
11) What included program(s) require .NET Framework?
The only program that this program can include and/or install that requires the .NET Framework
is the QTabBar/QAddressBar program.
12) Can this program patch the UXTHEME.DLL?
Yes, this patcher does patch the XP Gold, SP1, SP2 and SP3 versions of UXTHEME.DLL file in order to
enable unsigned visual styles to be used, as the Aero visual style isn't signed by Microsoft.
Patching has also been enabled on Windows 2003. Windows 2000 does use visual styles, nor contains
any version of UXTHEME.DLL.
13) I've heard some patchers cause memory allocation problems. Does this one?
According to the XPize Help & FAQ, certain
non-English versions of Windows have memory allocation issues when your Shell32.dll weighs more
than 15MB. This condition is often caused by including higher resolution icons in the Shell32.dll
than what Windows XP orginially includes.
Having stated what causes the problem, I have not received any complaints of this issue. Each
XPtsp theme packages does not contain icons larger than what XP original contains.
14) My antivirus founds a virus/keylogger inside xptsp. Does xptsp contain any spyware?
No. The patcher does not contain any malware of any description. Since XPtsp works with system files,
some antivirus software may detect that as dangerous, but they can be safely ignored as false positives.
We will NOT bundle spyware and/or malware into the patcher, so please don't ask either.
15) Error "XPtsp has detected that a previous installation has made changes to your
computer that will take effect after restarting. You must restart your computer before you can run XPtsp setup."
XPtsp checks for the Windows Automatic Update "RebootRequired" key as well as the
PendingFileRenameOperations ("PFRO") table to see if any changes are due to be made
to your system. If either of these registry keys suggest changes are pending then setup will
refuse to run. Ordinarily rebooting your system will clear these keys, however some background
programs may add entries to the PFRO table every time they run thus preventing XPtsp from running at all.
16) Can I build a theme package for XPtsp?
Sure. However, there are no templates available for download yet, so you will have to create your own at this time.
6b) How do I submit a theme for the XPtsp GUI?
You will need to contact
Dougiefresh at our forums. You will have to give a download link to your new theme in the PM.
17) Why is XPtsp free? What's the catch??
On the Internet, there are a lot of people with too much free time on their hands and need something to burn
away ther time. We're doing this to stroke our own ego and get us positive attention, and not much else.