dougiefresh

What's Changed in v1.4.3.0: - Updated resources to match XPtsp batch v1.4.3. - No code changes occurred.

I think we ought to close this thread and keep for historical purposes to show everybody why this forum was opened..... and to keep links to everything that has been shared. Just my opinion, though. EDIT: If questioning why, please refer to first post..... VERY important!

The reason I opened this thread is because only moderators and admin have the ability to open new threads in this forum, per my request. The reason being is that the original thread for XP Theme Source Patcher became very confusing for our readers, including me. N1K created this wonderful forum solely for this project. Thank you, N1K! If you would like to discuss things related to XP Theme Source Patcher, but NOT directly related to a particular thread, here is the place to do so. If you need to discuss things relating to a particular XPtsp theme, do so in the CORRECT thread!!! XPtsp links to SPECIFIC themes: Original XPtsp: here Blue XPtsp: here Black XPtsp: here Purple XPtsp: here NOTE: As far as I know, the original thread is going to be preserved so we don't lose any history about XPtsp, as well as a monument to the mess that the original thread became. New Threads: If you want to create a new thread in this forum, please create your post in this thread and let me know which one it is and I can split the post from this thread. URL's are most helpful in this regard! Thanks! Oh yeah.... I probably should mention that only new themes will get new threads in this forum and they will be moderator approved....

The reason I opened this thread is because only moderators and admin have the ability to open new threads in this forum, per my request. If you would like to discuss things related to XP Theme Source Patcher, but NOT directly related to a particular thread, here is the place to do so. If you need to discuss things relating to a particular XPtsp theme, do so in the CORRECT thread!!!

I've created this thread for the discussion of the XP Theme Source Patcher GUI, whether it be bug reports or feature requests. If there is any problem with the GUI, discussion should take place here. Please keep in mind that the goal of the GUI is to create a GUI for the project, NOT to create or modify resources for it. Both the resources and extras have been seperated from the GUI in order to minimize the download size of the package. Downloading the theme package and extras package will be required in order to use the GUI. If there is any problems with the resources, please report those problems in the appropriate thread, as this isn't the thread to report them in. UPDATE: Starting with v2.1.0.0, the patcher requires administrative privileges in order to run. I found out that without administrative privileges, any local copies in the same folder as the GUI SFX won't show up. file: XPtsp_v3.0.0.26_GUI.exe md5: 32ced219c6e33d9a1c1aa7fc057a7771 size: 1.6mb (1,702,137 bytes) Official Changelog: here GUI To-Do List (in order of preference): - Integrated online Theme management tools - WINNT.SIF manipulation tab in Additional Options - ISO Burning ability - A request to do additional MUI Patching Notes about the GUI: - All resources are ENGLISH ONLY! Please don't ask for translations for any languages, as this isn't the purpose of this thread. - If the archive is put in the XP source folder, the script will pick up the folder that the archive resides in and use it as the default folder. Otherwise, source folder will be blank. Poll Results: GUI Version with Translation Code: posted here

Well.... I'm OK with WinCert hosting the project files. I've been doing some off-line work on my web site, but if WinCert hosts the files, it would probably be for the best. Granted, I'll have lost $2 but maybe I should have run the ideas by the group before I started...... Oh, well. A subforum would be real nice. However, I'm a little concerned about the number of topics. If there was some way to restrict the creation of topics in the new subforum to moderators only, I think it would be for the best....

I meant that I would provide a website for the programs, much like XPize. In my opinion, if the software is hosted on free downloading sites, a forum isn't much of a "home". That's what I meant..... I didn't mean to offend....

I've already taken a few steps on my own in order to give XPtsp a home on the web. ShortURL.com provides URL redirection to another web site, which works for me. I've also paid the $2/yr activation fee. http://xptsp.filetap.com now points to my web site and I'm in the process of redesigning my website to put XPtsp on the main page. It will also serve as the website for Drive Space Indicator. I've got 1GB of storage on my web site and can easily host all of the XPtsp versions, present and probably future. My only problem will be when/if I lose my Comcast account, because I'll have to find another site. But that's in the (hopefully) far future and won't be that difficult to deal with. I personally have no interest in "hosting" the forum and agree with Bober on that point.

What's Changed in v1.4.1.0: (Download link) - Visual Theme installation is successful! - Resources updated to match batch v1.4.1. - SYSDM.CPL resource updated so that System Properties dialog looks correct. - Fixed Page 3 Browse button so that Next button is enabled after selecting i386 folder. Ok, it looks like the live patcher is about finished. So I need testers to make sure that everything appears correctly and functions normally.... Thanks! Mr. FixIt: That trick you told me about for replacing the bootscreen works for the visual styles, too!

Mr_Smartepants: Ok, I fix it before my next release..... DyceFreak: Care to elaborate? If you do, maybe it'll get fixed.....

I like this one best for the GUI: Thanks, amnesia!

What's Changed in GUI v1.4.0.2: - Bootscreen installation successful! - Added hex-edit to SP3 version SETUPAPI.DLL to fix battery prompt during setup. - Fixed "/PASSIVE" switch so that it doesn't hang upon execution. - Added timer so that user can see how long it took to patch the system. - Added section to XPtsp.ini for SETUPAPI.DLL patching. - Rebooting is OPTIONAL again. Option whether or not to reboot is given. - Explorer is not killed at ANY point during the patching. - "/REBOOT" switch added to force rebooting the system after patching is complete. - "/NOREBOOT" switch added to force no reboot after patching is complete.

FINALLY! :dribble: Success installing the bootscreen! Thank you for your assistance, Mr. Fixit! I'll be posting the next version of the GUI shortly! tomorrow. I'm tired, I'm going to bed!

Bober: Tried your suggestion. Didn't work inside VM. Last patch test/session took 745 seconds (about 12 minutes).

When I said "Who da man?", it was meant like "Who's the man?". Sorry, I keep forgetting that everybody on this forum isn't familar with U.S. slang....

Windows has a feature that, when properly manipulated, will move files at system restart. INF files can make use of it easily, but AutoIt scripts have a little harder time (no sarcasm) with it as we must add to the string as we go. I have not gotten NTOSKRNL.EXE to be replaced by this mechanism, nor a "simple" file move/copy. If Windows is pulling from Driver.CAB/SP?.CAB, then that would explain why replacing NTOSKRNL.EXE is being a witch..... When I get home from work today, I'll give it your suggestion a try, utilizing the above mechanism to put the cab file back to it's original name. Thanks for the tip, Bober! Wish me luck! EDIT: Will replacer work?..... I don't know. I doubt it for this particular problem. I'm running RyanVM Post-SP3 Update Pack v1.0.2 on both my real system and my virtual machine. EDIT2: This last weekend, I've felt like throwing the machine out the window. My patience has gotten thin with the bootscreen problem..... Maybe all I need is a break.... Sleep doesn't help, it just gives me energy to try more things....

George King: Did you run PEChecksum on the file to correct the checksum? If not, Setup will give you that error every time!

Amnesia: You have a PM waiting for you regarding GUI source... Thanks! Regarding copy process, evidentally my computer and VM don't want to cooperate doing "simple copies". I've had to jump through hoops, trying to get it working properly.

Mine didn't. The original SFC file helps program for all circumstances....I understand the purpose of that patch, I just don't understand why people would want it....

anemsia: I don't think shell32.dll is one of them. I know some files won't allow themselves to be replaced because they are in-use. So, sometimes renaming them and copying the patched files into place works. When that fails, it's time to hack the registry to force them to be copied at reboot. EDIT: When trying to replace files like I told you, you also have to rename the DLLCACHE file FIRST. Otherwise, patched file gets overwritten automagically.... or WFP prompts from he11.... I'm not sure if killing Explorer is necessary, I'm trying to determine that now.... LOL! :beerchug:

I tried those same lines when I was building the live installer and came to the conclusion that they only work on a system with the SFC already installed. patched. (Conclusion supported by research into those settings...) Some of those settings are useless without an immediate reboot, something I know you don't want to do before starting to patch files. Others are useless without the SFC patch installed. Also, you'll probably also get the pleasure of trying to replace in-use files. Research "replacing files in-use" for your answer. I had to, as a precaution. Turns out I REALLY needed it. EDIT: Oh yeah, I've already found out that while I can patch the NTKRNLPA.exe and NTOSKRNL.exe files, I can't seem to be able to move them into place using the "replace files in-use" method, or by direct copying. Probably because the kernel can't replace itself while it's in use..... How Windows Update does it is beyond me! EDIT2: GUI reports patching took 1033 seconds (just over 17 minutes) in my virtual machine.

Yeah, change the Entries_DriveSpace.ini file so that it reads: DriveSpace.exe /SVCPACK /THEME:XPtspAny other settings that are supported by command-line parameters can be set as well. Hope that helps! EDIT: (Actually, the "default" theme is whatever theme comes first alphabetically! So if we get an "Apple" theme, that becomes default, because Apple comes before Blue.)

Okaaaay.... so those lines aren't necessary? That's weird. :shy:

Who da man? YOU DA MAN!!!! :dribble: :worthy: :giveheart: :thumbsup_anim: :wub_anim: No, seriously! Those are EXACTLY what I'm looking for! Thanks, bjfrog! EDIT: This time, I'll try to hold on to the icon converter! --- Yeah, I lost it last time! As Homer Simpson would say: DOH! EDIT2: I tried to include more emoticons, but the forum board said it was too many..... EDIT3: Did you notice the post times? 12 hours, 1 minute apart! (Not that it matters, just thought it was interesting!)

amnesia: Good question. Since I started developing the GUI, the batch file has always done it this way. I don't understand why, but that would be why RisingXun is getting a corrupted file without these lines.... I do this way because that is the way the batch file does it. I would redirect this question to Bober for further info.... RisingXun: Actually, no it wouldn't work like you indicated. The part to the left of the "=" identifies what resource file to use (w/o the .res part), while the part to the right identifies the location of the file to patch (unless we renamed every resource file, at which point trying to modify anything would become a hassle....) All of the resource files are located in the "Resources" folder, courtsey of the fact that I move the resource files from the Extra\Home or Extra\MCE folder into the Resources and Extra folders if I am patching either OS. I do this so that I don't have to check later over and over and over and over.... As for the BOOTSCR.RES, why not just modify the script to copy BOOTSCR.RES to the other resource files prior to patching? That's what I did to save space. That, and we only have to edit one file to change the boot screen, not 4..... or 8.... or even 12 (God forbid we get more - for example, the ability to CHOOSE what bootscreen to use! --- Hey, not a bad idea if I may say...) EDIT: Also, are you accounting for WFP? How about the DLLCACHE? If not, I suggest you go to the AutoIt forums and research both topics. An misunderstanding of either topic will result in fustration, as I have found out during my recent testing, simply because you will patch the file and the unpatched version will replace your patched copy automagically. Mona: I believe that Bober initially replaced some cursors in user32.dll, but had a bit of problem and removed them. I could be mistaken, but I don't think I am....