dougiefresh

Yes, I did. I just updated the GUI SFX this morning. Sorry about the delay. Awesome. The newest version of the GUI deletes those files prior to starting the patching, so you should be able to use the next updated Extra's package once it becomes available.

I think I actually misspoke about my understanding of what's happening with the new kernel. I meant to say that I've heard some reports that indicate patching the color palette on systems with KB977165 results in a BSOD. I haven't confirmed that the problem exists with the patcher, but I will try to test this situation this weekend. Work has just been really busy this week and I haven't had much time to do much of anything :shy: It's kinda getting annoying, but hey, it's a job and I can't complain too much! Either feast or famine.... no middle of the road for us... But maybe this weekend..... :g:

AH!! Okay, that's very good information to have! Thanks!

Well, it wouldn't be the first time that's happened.....Okay, I've rebuilt my XPtsp test platform and omitted the Quartz.dll file from patching.... or rather, I tried to and the GUI patched it anyways. I went back in and manually replaced the patched copy with the original copy from the UpdatePack. Installed the new XPtsp test platform in a VM and went to Microsoft Update once it was completed. KB955759 still shows up as a patch to install, so obviously Quartz.dll isn't the culprit here.... (which to me is kind of a relief because I don't have to write some convoluted code to try to deal with that mess) Running this test revealed a problem with the GUI, namely a unchecked file in the Component Selection gets patched anyways. So I think I've fixed this issue in the patcher, however, testing is still necessary to do to verify that the new code works. I've also gotten some reports that patching the bootscreen on systems with KB977165 installed (a new kernel) results in BSODs. I can confirm that the bootscreen images can be patched on this kernel, however, I will also be testing to see if changing the color palette results in the BSOD. If it does, I will be adding code to omit patching the color palette of that kernel. EDIT: Oh yeah, I'm holding off on releasing the version 2.1.0.2 until I can get a few issues worked out of the code.... I'm apologize if this is an inconvenience to anybody....

First of all, I wish to say thank you for your hard work! I know it's not easy to build these things..... Second, I've received some reports with XPtsp regarding KB977165 (a kernel update) with BSOD after patching the kernel. So I did some searching on Yahoo (search link) and found this article: Microsoft withdraws flawed Windows update and Microsoft halts Windows Update distribution of security fix after blue-screen.... Does this mean that the update will be pulled from your updatepack? Thanks!

Later today, I'll rebuild my XPtsp test platform and omit the Quartz.dll from patching. If this solves this issue, I really don't know how I'll integrate the solution into the patcher.....

Okay, my tests indicate that the solution Fixit and I came up with has worked for the Remote Desktop hotfix. I am likewise able to reproduce the issue with KB955759, however, neither file that is in the hotfix is modified by the XPtsp patcher. I used Microsoft Update to install the hotfix several times and each time, it said the hotfix was needed again. Searching Yahoo on KB955759 yielded hits variations on this solution, which is not a good answer (in my opinion). So I'm at a complete loss on how to fix this situation....

Depends on how you pack the 7z file.... I pack my 7z files into what is called "Solid" packs and the every version of the 7zip program I've tried won't add files to it because it would have to repack all the files. But if you don't pack it as a solid pack, then maybe.... I just dunno. I use solid 7z files because the size is the smallest....

Regarding KB969084 (Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3), I can take a pretty good stab at what is causing the "problem". Both the GUI and batch versions actually REPLACE some (if not all) of the Remote Desktop program with an "updated version", but this "updated version" is actually an older version number of those files than those in the UpdatePack. So, that is probably why KB969084 is being prompted for reinstall. A short-term fix for this is to remove the lhmstsc.exe, lhmstsc.mui, lhmstscx.dll, and lhmstscx.mui files from the Extra's package. I will release version 2.1.0.2 to deal with this issue, probably this weekend. Regarding KB955759 (AppCompat update for Indeo codec: December 08, 2009), I honestly have no idea at the moment. The files that the KB article lists aren't modified by the GUI or batch versions, so I don't see any reason that it would prompt for install/reinstall when it doesn't without XPtsp installed. I would have to do some more research to determine the cause.... UPDATE: In order to fix the Remote Desktop problem, those mentioned files are going to be removed and the GUI will duplicate the proper res files in order to correctly patch those files. This should take care of this problem, as well as problems caused by future versions.

I received confirmation from newbeyninja that the screenshot is from the XPtsp Blue batch, so I moved both posts from the Non-Specific Theme Discussion thread to here, since it is relevant to this thread.

Great news! Thanks for the feedback, Mr_Smartepants!

Well, I know from my discussions with Bober and Fixit that themes take a long time to design. I believe that Fixit said it took something like 3 months to make the Red theme. So, I can only recommend that you keep working on it and eventually you'll finish it.

Yes, there is a way to customize the GUI Extra's package. You must first unpack the Original.Extra package (assuming you're modifying the Original Extra's), using any decompression program you like. Make your modifications to the files, then use 7zip to compress the files back down in the 7z format. I prefer to use LZMA method for compression, 64MB dictionary with solid block size, as these settings produce the smallest file. (Of course, it doesn't matter if you don't need to upload/download it....) As for the AutoRun, you can decompress it and modify the background to your liking. When recompressing it, use the above mentioned settings, then use the files from this post. It contains the SFX module and the Config.txt that must be combined in order to create the SFX. DO NOT use the standard 7zip SFX module, as it cannot set the needed environmental variable which the AutoRun program requires. EDIT: I forgot to mention that there are actually 3 different sets of OOBE files, as well as 3 different AutoRuns. The Professional is in the root of the Extra's folder, Home Edition is in the Home\ folder, and MCE is in the MCE\ folder.

I apologize about the delay in answering your question. As I understand it, there is a second file that is applied if IE8 is present during integration/install. In the batch versions, it is 8IEFRAME.DLL.MUI and can be found in the Resources folder. In the GUI theme packages, it is IEFRAME.DLL.MUI found in the Resources\IE8 folder. This second file contains modifications that are specific to IE8 and must be applied in addition to the IEFRAME.DLL.MUI file found in the Resources folder. Although I have one question for you: Is the screenshot you posted from the blue XPtsp theme or a customize or home-made theme?

I fixed the download link to the XPtsp.com server in the first post. I'm aware of the mirror containing v1.4.6.0 instead of v1.4.7.1 and I will try to fix that...

Update: Got around the problem with the newest CAD2009 by writing a "wrapper" function that resizes the biggest background file into the appropriately-named and -sized background and then called the actual program. I'm only including the largest background in the add-on. I'm also updating some of the add-ons for other software, so as soon as I get done with that, I'll be updating both of the sets of Extras.

No problem! To answer you question, the CAD add-on will eventually be upgraded to version 1.6. However, I haven't found the time to do so. The CAD add-on is actually a part of the Extras packages, not specifically linked to a specific version of XPtsp. EDIT: I've found a INF/CAB combo and have made a few changes to it in order for it to be a proper add-on. :thumbsup_anim: However, I've noticed a problem with it in regards to compatibility with XPtsp: I will have to resize the background within XPtsp several times in order to replace the background images that are present.... :thumbsdown_anim: Bummer... :shy:

What's Changed in v2.1.0.1: - Seperated XPtsp logo from XPtsp.exe in order to allow theme packages to replace the logo. - Default GUI mode changed to Install for XP, Integration for all other OSes. - Modified Integration page to prompt whether to create folder to copy to if not exist. - Added code to make Home/Pro integrated with MCE components read as MCE during text setup. - Modified Live Install code to add back code that was removed in v2.1.0.0. - Fixed issue with background image not getting replaced during Live Install. - Fixed memory leak issue with the Update GUI page. - Added code to actually install latest GUI when it is downloaded via GUI. - Added code to download and install new DSI versions when available. - Added code to download and install updated language files when available. It is my intention to relax the XPtsp OS restriction so that the patching can be done on OSes prior to Windows XP for GUI Version 3.0.0.0. Once we figure out how to do the patching for Windows Vista and Seven OSes (and theme packages become available), they will be included in this patcher program. A name change may also be warranted at that point... ========================================================= Mr_Smartepants: Thanks for that information. Jatin Beniwal: I've fixed the Live Install code so that it operates properly. Sorry about the wait...

Everybody: I haven't had any time to research the translation/transcription problem because of the long hours I worked this week. However, I think I've located the code I removed from v2.1.0.0 that relates to the Live Install code. I've put it back in and am testing it. Thanks for your patience and understanding! QUICK UPDATE: Reinserting that line of code solved the Live Install problem that was noted earlier. I'm looking into the background issue now. Oh yeah, my VM is running at a normal speed now. Installation took about 7 minutes.... Mr_Smartepants: You're welcome! And thanks for the feedback about v2.1.0.0! Concerning the DriverPack & XPtsp install, I am able to rule out #3 because I don't know of and can't imagine any method to interfere with the writing of a file using AutoIt. I can rule out #2 because I know the XPtsp GUI doesn't delete any files during ROE. Unfortunately, that leaves #1.... My question is whether the finisher actually executes, because if it doesn't, then that is probably why the log file isn't being written. Please let me know what you figure out during the course of your investigation! Thanks! hamedledam: You're welcome!

Mr_Smartepants: Thank you for the information! I'll update the CAD to v1.6 with the next release. I'll also look into the branding issue, however, I'm not sure that I can do anything about it. Fixit: Thank you for the hexing information. I'll try to get that into the next version of the GUI. Everybody: My computer is FINALLY up and running after the fun of a really blotched weekend installing stuff on my new hard drive.... I should be able to begin testing of the GUI again this week. By this weekend, I hope to deliver a version of the GUI that has translation code built-in. (Maybe I should call it "transcription", since it's a more accurate term :shy: ) Regarding the poll, there have been 7 votes in roughly 2 weeks. Everybody except 1 member voted for the next version with the translation code to be version 3.0.0.0, so that is going to be the next version number.

Everybody: Okay, I've got my hard drive in yesterday. The hard drive and package was kinda cold, so I had to let it warm up overnight. I've got my OS reinstalled today and I'm still working on trying to get everything transferred over from my other hard drive... This is a royal pain, though... (losing a hard drive) I'll tell y'all this: it's nice to have my normal speed back... Last night, I updated the first post of this thread with 2 links to certain topics, both of which I may be able to solve (finally). While I was searching for these topics, I can across a post of mine that reminded me why I coded things the way I did. Specifically, the registry edit on a Live Install that enabled protected system files to be replaced at reboot.... which is probably why patching a Live Install didn't work (I took out that code, not realizing what that would break).... So it'll be reincluded in the next version. Let's see.... the first test of the translation code was partly successful. It was completely successful for resource files that didn't have dialog boxes. Resources files that did have dialog boxes were not converted to the new language ID code. I suspect this is because the code I used to transfer the coordinate information from the Dutch XPtsp to the English XPtsp also included a new stringtable line. The translation code ALSO included this line. So the res file wasn't able to be built, as there were two stringtable lines with the same string number.... I'm guessing that it will be later this week that I will be able to start testing the XPtsp GUI. I'll be testing the Live Install code first. I may release that before working more on the translation code. I'm not sure yet... Mr. Fixit: Thanks for the hex edit information! But are you certain that the the English phrases "Professional" and "Media Center" are used in non-English installs? If not, then hex editing won't work for the solution that I am hoping for.... information!

Awesome news on the Device Manager button issue! Thanks, Bober!

I will try to look into the Device Manager and battery icon issue. I'm still very new at dealing with RES files, so please be patient.

Update: Since I can't do any VM testing right now, I've been working on the translation code. I've got the code down, and I can transfer the coordinate info from the Dutch versions into the XPtsp resource files. However, some res files may require some additional tweaking. I also need to go through and determine what line of the source file goes where in the XPtsp resource file. Once everything is complete, I will be able to drop the new function into the patcher script with minimum of modification to the script and a new version will be issued. I haven't decided on the new version number, so I'll set up a poll to see what people think... I'll also be issuing updated theme packages. These will be necessary to be downloaded in order to use the translation code. BTW, my replacement hard drive should arrive Monday if anyone is interested...

My last GUI test took over 40 minutes during a Live Install, which is an abormally long time. Previous tests took no more than 10 minutes. I encountered no issues with the GUI installing the 3rd-party software, however, it patched the files but did not replace the original files with the new ones at next reboot. I don't understand why it didn't.... :confused02: So I regret to inform everybody that I will not be able to do any virtual machine testing for about a week or two due to severe hard drive problems I am currently experiencing. 5 days ago, I sent off one of my defective drives and it should get there Monday. (Damn New Year's holiday.... :shy: ) Once I receive the replacement drive (which should be in the next week and a half), I should be able to do some more testing.... Meanwhile, I am not able to do further testing. UPDATE: I've been fiddling with the code some since I can't really do Live Install testing right now and I just noticed something in the v2.1.0.0 GUI... When v2.1.0.0 finds an updated version, it will download the newest version but it won't install it. Also, the updating code has some major memory leak issues....