dougiefresh

What's Changed in v3.0.0.0: - Fixed the operating system detection code so that the correct OS is reported. - Added code to check for pending file operations before allowing program install folder to be selected. - Modified code dealing with file browsing to use SFX folder as default folder. - "Disable Resource Translation" checkbox added to Extra's GUI page (enabled for v2.x themes) - Removed OOBE replacement for Windows 2000 and Windows 2003. - Split NetMeeting components into their own group in Component Selection. - Rewrote code so that hardlinks to res files are created when possible to reduce disk space used. - Fixed file patching percent bar to start at 0% instead of 10%. - Eliminated unnecessary file copying in order to try and speed up Live Install process. - Corrected some GUI issues regarding disabling and enabling GUI pages. Features from Beta v2.999.0.x series: - Translation code has been included and enabled. - English language file has been updated with new strings for dialog boxes. - XPtsp.INI has been updated with dialog box line mapping information. - Using older themes with beta GUI will result in inability to translate package. Updated Experimental 64-bit support: - Upgraded Reshacker to version 3.5.2 in order to support 64-bit files. - Removed "Experimental Support" message from Repatcher after installation on x64 OSes. - Added another task for patching the AMD64 folder on x64 operating system source folders. - Added another task for patching the 64-bit files during a Live Install. - Added code to fix a Reshacker problem with icon 0 in Setup.exe and SrClient.dll. - Added code to account for file redirection mechanism in order to patch files in 64-bit OS. Other Words: First, I've been working a lot of hours at my workplace and haven't been able to get the 64-bit patching code working right. I'm not sure why the code is failing to patch the system correctly, as I'm still trying to figure out what I'm doing wrong. Furthermore, testing on Windows 2000 and Windows 2003 still hasn't been done, so I can't tell you whether it works or not. Feedback would be appreciated from anyone willing to try it..... Second, Fixit brought to my attention that with the .theme file extension, the theme appears to have deeper operating system support than should be implied. So I have decided to change the file extension to .xptsp, since it directly implies XPtsp ownership of the files instead of to the operating system. This shouldn't affect previous versions of the GUI, as the website will redirect requests for .theme files to the ones with the .xptsp file extension..... Third, I've made some code changes to try to speed up the patcher by removing unnecessary file copies and moves. There isn't much difference, but trust me, the difference is there... Lastly, the website is being redesigned to make it look even better (in my opinion) and to add forum functionality to it. Yes, I know I said I wouldn't add a forum to the site, but the fact is that the forum membership functions are substantially better than the code I can write. We've also have been having issues with the comments sections of some pages. One solution is to move that functionality to the forum, which would solve some or all of those issues.

Regarding the batch versions, Bober has officially retired from the XPtsp Green project, which (at least to me) pretty much explains why there has been no updates to the Green theme. Regarding the GUI, it is the goal of it's creation to completely replace the batch versions with the GUI. At that time, the batch versions will be removed from the threads and will be replaced by download links to the themes themselves.... Don't worry, the batch versions will be retained for historical reasons...

I've been working on the 64-bit file patching problem. I have been successful at making the patcher modify the resources in both a 64-bit live install and cd integration, however, neither seems to work properly once patched. This may indicate that some or all of resources in the 64-bit files are different from their 32-bit counterparts.... and that the current themes cannot be used with the 64-bit operating systems. The next version will also have the translation code enabled, with the option to turn it off on the page before the patching starts. The beta thread has been closed, as hardly any replies were received about the success/failure of the translation code.

Okay, since no one seems to want to reply about translation issues, I'm gonna close this beta run and will integrate the translation code fully into the code. It will be possible to turn off the translation code if required.

I really need some feedback on how the translation code is performing! If I don't get some feedback, I am going to assume that the translation code works fine and will proceed to integrate it fully into the patcher. Thanks!

I just got a copy of Windows XP x64 Professional to experiment with and found out that the patcher won't work with the install source as it stands currently. It turns out that there are TWO install folders to patch (AMD64 and i386), not just one like in x86 (i386) install folders! The patcher program does nothing to the second install folder.... Also, Fixit informed me yesterday that the patcher won't correctly patch a live install of XP x64, either. I had made no effort to account for the redirection mechanism built into the 64-bit operating systems. The net effect is that x64 won't be patched completely in order to effect the changes.... I've made some changes to the patcher in order to account for the redirection mechanism, however, I haven't tested the changes yet. But I haven't figured out how to do the second source install folder yet....

I just got a copy of Windows XP x64 Professional to experiment with and found out that the patcher won't work with the install source as it stands currently. It turns out that there are TWO install folders to patch (AMD64 and i386), not just one like in x86 (i386) install folders! The patcher program does nothing to the second install folder.... Also, Fixit informed me yesterday that the patcher won't correctly patch a live install of XP x64, either. I had made no effort to account for the redirection mechanism built into the 64-bit operating systems. The net effect is that x64 won't be patched completely in order to effect the changes.... I've made some changes to the patcher in order to account for the redirection mechanism, however, I haven't tested the changes yet. But I haven't figured out how to do the second source install folder yet....

Updated to v2.999.0.3

Updated to v2.999.0.3

Updated to v2.999.0.3

Updated to v2.999.0.3

What's Changed in v2.2.0.4: - Added experimental support for Windows 2000 and 2003 Server. - Added experimental support for Windows XP x64 Professional. - Added message about experiment support when using the patcher on for X64, 2000, and 2003. - Code modified to use Home Edition bootscreen for Windows 2000 and 2003. - XP Pro bootscreen still used for XP X64 Pro. What's Different between v2.2.0.4 and 2.999.0.3: - Translation code has been enabled.

What's Changed in v2.2.0.4: - Added experimental support for Windows 2000 and 2003 Server. - Added experimental support for Windows XP x64 Professional. - Added message about experiment support when using the patcher on for X64, 2000, and 2003. - Code modified to use Home Edition bootscreen for Windows 2000 and 2003. - XP Pro bootscreen still used for XP X64 Pro.

Okay. Here's the link: logonui.noshadow.res.7z

Sure! Download this res file: logonui.exe.res.7z

I wish I could claim credit for the original LogonUI.exe logos. Based on my discussion with Bober, I believe that the original logos were created by Stimpy. I'm literally trying to figure out how to recreate the entire logo based on the original logos, which is fustrating... especially since I'm just learning how to do this stuff..... How is this version of the x64 logo?

Here's the closest I could come to something similar to the XP Professional Edition logo for x64... Screenshot: Let me know what you think about it.

What's Changed in v2.2.0.3: - Fixed each page so that the "/SILENT" switch works as expected. - Copied bootscreens from batch versions and placed them in BOOT folder in GUI. - Before patching starts, bootscreens from BOOT folder are copied to resources folder. - Log file now shows minutes and seconds instead of total seconds as time completed. - Fixed Repatcher so that correct page is called in order to build a list of files to patch. What's Different Between v2.2.0.3 and v2.999.0.2: - Translation code is enabled. I'm sorry it took so long for this version to be released. Quite a few things have happened that this last two weeks, including a minor rewrite of the code because I found that certain things weren't happening when using the "/SILENT" switch. This should take care of the incorrect bootscreen issue that JAMIS246 found. JAMIS246: This weekend, we've been working on the new logo for Windows XP x64. We're coming close, however, figuring out how to do so has been a major pain in the buttocks..... :thumbsdown_anim: Once we're done, I'll try to write some new code into the GUI to allow it to detect XP x64....

What's Changed in v2.2.0.3: - Fixed each page so that the "/SILENT" switch works as expected. - Copied bootscreens from batch versions and placed them in <b>BOOT</b> folder in GUI. - Before patching starts, bootscreens from <b>BOOT</b> folder are copied to resources folder. - Log file now shows minutes and seconds instead of total seconds as time completed. - Fixed Repatcher so that correct page is called in order to build a list of files to patch. I'm sorry it took so long for this version to be released. Quite a few things have happened that this last two weeks, including a minor rewrite of the code because I found that certain things weren't happening when using the "/SILENT" switch. Also included in this version is the bootscreen fixes that was reported by JAMIS246 here.

We will look into doing so, although right now, I can't promise a timetable on it....

I'm sorry. This weekend, I have been trying to correct some other bugs I found. Unfortunately, the problem with the code is more extensive than I realized.... I've also had some personal problems which is slowing down my progress considerably.... I am trying to get everything implemented and it should be ready to release soon. I apologize if this is inconvenient, but life happens when it is least expected....

Unfortunately, I wish I could answer that question for you. I would ASSUME that the 32-bit resources are similar to the 64-bit, but I haven't looked at them at any length.

At present moment, there is no support for patching a 64-bit version of Windows XP. For both live installs and integrations, it is determined to be 32-bit or 64-bit by the kernel version number. 32-bit kernels have version 5.1.x.x attached to them, while 64-bits have version 5.2.x.x attached. This makes it easy to tell them apart. Regarding the request for 64-bit support, it's on the list (dunno if it is posted, but it's on there). Once I open up the GUI to patch previous versions of Windows (NT and 2000), I can work on the code support. By the way, live installs on Windows NT are not possible, nor is including the GUI in a Windows NT source. It has everything to do with lack of support in AutoIt for older Windows installs and nothing to do with my desires.... Windows 9x/ME is damn near impossible to patch because of the way it was packed. EDIT: XPtsp FAQ updated to reflect the information in this post.

What's Changed in the Green Beta theme: - Bootscreens were replaced with those from the XPtsp batch versions. - Version info was removed from RES files so that files weren't mis-identified as those from Vista.

What's Changed in the Green Beta theme: - Bootscreens were replaced with those from the XPtsp batch versions. - Version info was removed from RES files so that files weren't mis-identified as those from Vista. The next version of the patcher will have code in it that will replace the bootscreens found in the theme with those in the GUI. This is to ensure that the bootscreen in question is the correct one.