dougiefresh

Silent update of GUI. Amnesia fixed the Manifest of the GUI SFX. (Don't understand what that does, but as long as it's fixed... I don't think it affects the GUI any.) Bober: Any chance you might want TaskSwitchXP included in the package? I think it would make a nice replacementfor XP's Alt-Tab thingy addition.... Here's a pic of it in action: Link to software: http://www.ntwind.com/software/taskswitchxp.html EDIT: It would only add about 400kb to the package....

I'm pretty sure that Replacer will cancel out the WFP box. Vista Icon Pack Ultimate - System Patch add-on used it and I don't recall ever seeing a WFP box during installation.

Bober: Here ya go: Cursors and Fonts add-on. Just drop these files into your add-on and the cursors and Segoe UI fonts will be included. EDIT: I modified the Entries_XPtsp.ini at the end to include the necessary lines for the Integrator to do the editing. EDIT2: Sorry about the lateness.... EDIT3: MD5: 06AA39FC0DF82C8004F1B1012D318E1F, Size: 752kb EDIT4: Thanks, glad you like the logo. Probably not want you wanted, though.... Amnesia: Try this link. It's a batch file called "Replacer".

Uploaded version 1.0.10b13 of the GUI. Resources updated to match batch v1.0.10b13 and logo changed to a more generic version of previous logo. Gorki: I appreciate all of the replies that you and others gave. It helped to fix the GUI version. Thanks! And don't feel guilty.... Beta testers return bug reports about what's wrong with the software. It's the developer's job (Me!) to fix the software. Thanks for the feedback!

Idea for a logo: http://vistastyles.org/2006/11/07/vista-orb

Glad to hear that! I was really beginning to wonder.... I probably won't be able to work on the live patching this weekend. Maybe next week....

CABARC is a command-line program. It doesn't open any windows. The progress bar you see is the script parsing the output of the program. About time that the script works correctly! I look forward to reading the results. I'm going to bed, now. Nite-nite!

I reuploaded the latest version after realizing that certain files had been moved by the script. So it should be available now. And no, I hadn't tried Vista's MAKECAB. Like I said, I got fustrated and rewrote that function to use a program I knew would work. It may be a little extreme, but hey, hopefully it'll work this time... If it doesn't, I don't know what I'm going to do. I really don't....

Damn it! I thought I fixed that! I'm gonna use CABARC to build the fricken CAB files, since MAKECAB doesn't want to work outside my computer. EDIT: Sorry, I've been having a difficult time with this patching program. It's funny.... I've never had a problem with CABARC, but I can't make MAKECAB work properly, no matter how I code it. I've looked at the batch file and my script does things basically the same way. Yet, the batch file works and the AutoIt script doesn't. I've gotten really fustrated with this.... EDIT2: Uploaded v1.0.10b11c. Rewrote entire CAB building function to utilize CABARC instead of MAKECAB.... Please test and let me know how this one goes....

GUI Version 1.0.10b11b has been released. I'm pretty sure I fixed the CAB building code. So please test this and give me some feedback. Thanks! Link is in first post leading to my website. EDIT: Oh, yeah. I updated the resources to match batch v1.0.10b11b....

Bober, if you need/want to use letters as well, that's your choice. Don't let me stop you.

Yeah. I'm going to use your version number as mine. If there is GUI code improvements or changes, I'll change my version number with letters (v1.0.10b11a). That way everybody is clear on what version of the resolution files each contains. EDIT: Wha.... hold on! It's your thread, you're the person releasing the package. I'm just trying to develop the GUI for it, keeping the resources the same as the batch file! I'll follow your lead on version numbers, however, if GUI changes come out between batch releases, I'll modify my version number with letters, like I mentioned before this edit. So, just to be clear: When you release v1.0.10b11, I'll release the same. Improvements in the GUI that occur between batch versions will get letters attached (ex: v1.0.10b11a). I hope that clears what I meant up! I never meant to control the version numbers in any way!

Gorki and Mr_Smartepants: In the GUI, I managed to reproduce a situation that produces no CAB files. The destination folder had spaces in the name. I'm going to try to fix the script so that this bug is squashed. I'm going to wait for Bober's release to release my next update, so it will probably be tomorrow. EDIT: Gorki, the MIGWIZ.EXE message was incorrect. I tested the code on original SP3 copy of the file. Test was positive for the "NoPatch.ByVersion" check. It should have been negative. The next release will fix the script in regards to the improper detection.

Stimpy: Hey, any progress creating a logo for the GUI? Just wondering.... Thanks! Gorki: Have you tried the v1.0.10b11a release of the GUI yet? Kaylar: Bober suggested here that BLISS.BMP might be renamed, instead of converted. I tried that, it didn't work. Mr_Smartepants: I will add an option to use Mkisofs instead of Cdimage. Hopefully, that will solve this particular problem... Bober: Huh, I haven't had a problem just plopping the BLISS.JPG file into the %WinDir%\Web\Wallpaper folder. I want to replace each file correctly, and since BLISS.JPG isn't on the system and BLISS.BMP is, I didn't know if there was a different way. Anyway, I found a proggie to convert JPG files to BMP files, so there's no problem there. Can you update first post to reflect v1.0.10b11a release of the GUI? Thanks!

Download: XPtsp v1.0.10b11a GUI MD5: 4AEE540827F811799E7B280B528E1997, Size: 31.2mb Bober: Found some info online about a problem with BLISS.BMP, how it can't be selected on XP Embedded because it wasn't installed. Article gave steps on how to remedy, including selecting image and saving as a BMP. This seems to indicate that Setup actually converts the BLISS.JPG to BLISS.BMP, instead of renaming it.... EDIT: Tried renaming the BLISS.JPG file and placing in %WinDir%\Web\Wallpaper as BLISS.BMP. Doesn't work...

Ok, I've integrated these add-ons into my clean XP Home OEM SP3 source: - 5er_KB893056_SP3_Addon.7z - CyberVistaBootScreen(KB944092)_AddOn.7z - DirectX_9.0c_End-User_Runtime_AddOn_0.5.1_-_redxii.7z - ENU_MovieMaker_2.6_Addon.7z - NR_WBEM_Fix_AddOn_v1.1.7z - OnePiece_IE7_WinXPSP3_v2.3.0_AddOn_ENU.7z - OnePiece_Windows_Media_Player_11_True_AddOn_v1.2.0_ENU.7z - PatchAddon_TCPIP_100_v14a.7z - PatchAddon_UXTHEME_v14a.7z - PatchAddon_XPRAID5_v14.7z - RVMAddonsWGAN_1.8.31.0.7z - RVMUpdatePackSP3_1.0.1.7z - Bober101_MultiCore_AddOn.rar - ENU_Addons_BVProSvcDescriptions_SP3.zip Then I patched that install with the GUI of XPtsp. I confirmed before attempting installation that XPtsp.CAB and XPtsp.INF are created and added correctly. I then ran it in a Virtual PC machine, with no installation problems apparent thru GUI Setup. Since your install is missing XPTSP.CAB, I made a small change to the script to force it to put the new cab in the script folder during creation, then transfer to I386 folder. I also altered the notification function for Page 5 so that it outputs a log in the XP source folder, named XPtsp.log. I'll upload shortly. EDIT: MIGWIZ.EXE version 6.0.6001.18000 or higher triggers this message. Rick's Vista Easy Transfer Wizard add-on contains this file. The file has different resources than the one that comes with XP, so Rick mentioned that the file should be excluded from the patch if it was found, which is what I've done.

Gorki: What exactly are you experiencing? I can't help if you don't supply information. "It breaks the install" simply isn't enough information. "Such-and-such file is missing" is much more helpful.... Meanwhile, I'll look at the script and the XPtsp.ini to see if there is something I missed. Thanks! EDIT: Hold on, I reread your post right after I posted this. Sounds like the add-on INF isn't there.... Can you verify that XPTSP.IN_ and XPTSP.CAB is present in the XP source folder? Is the error you're encountering something like "XPtsp.inf isn't present on the CD"? EDIT2: I'm rerunning the patcher to see if there is something wrong. Everything tested fine, but that was before I added the fonts (which shouldn't cause a prob).... Bober: I don't know where to put the MCBLISS.JPG and BLISS.JPG files. I can locate a BLISS.BMP file (which is in %WINDIR%\Web\Wallpaper), but that doesn't help me.... EDIT: Looked at the source for the XPize installer system and found a proggie to convert JPG images to BMP format! Solved!

What add-ons are you integrating into your XP source? XP version? Service Pack? Anything else I need to know (like what breaks...)? EDIT: Or what you're encountering?

Updated version to match batch beta 11. Here it is: Download link: XPtsp v1.0.10b11 GUI MD5: AC21355E5A36895E10D3ACE94AEB952F, Size: 31.2mb What's Changed in GUI: - Updated resources to match batch beta 11. - Added 1 more file to NR_IE7 section of XPtsp.ini. - Found destinations for more files for Live System Patching. - Removed WMM2RES.DLL version check from XPtsp.ini under "NoPatch.ByVersion". - Added new code to correctly handle LOGONUI.EXE editing.

Bober: I got the batch beta 11 and will include in next GUI release. Thanks for the info about the WINNTBB?.DLL and WINNT32?.DLL files. I got the updated INI from your last post and have included it. I located a few more files via Yahoo and that web site you listed. (Can't seem to figure out MCE stuff and BLISS.JPG....) Why did IEFRAME.DLL.MUI get compressed when it's not compressed in the CAB? Well, in my haste, I forgot to change the file extension on the right side of equal sign. Last character of _ in a filename on right side of equal sign tells the script to compress the file. I also included that other file in the IE7 section that I apparently missed. EDIT: I'll add the lines you specified for the logonui file to the patcher.... Oh, WMM2RES.DLL doesn't come from Rick's Easy Transfer add-on. I got it from the Vista Movie Maker add-on.... Gorki: That's not actually an error... I took the version number from the Vista Movie Maker add-on. I guess I assumed that the later version might not need to be modded.... my bad. I've removed the line under "NoPatch.ByVersion" for the next release. Let me know if it needs to be added again.... EDIT: Any other problems/troubles that you've had? I'd like to know if you've encountered any! Thanks! Everybody: For some dumb reason, I'm having a hell of a time keeping stuff working while I'm getting other code fleshed out. It's probably because I'm tired and it's the end of the day for me.... So I want to apologize to everybody for the GUI problems. Hopefully, this last update will resolve these last few problems... Thanks for all of your assistance with testing the GUI! I appreciate it. (No, really, I do!)

I'm using %Win% to refer to the Windows folder, %Sys% to refer to the System32 folder under Windows, and %Prog% to refer to Program Files folder. We can make changes to the variables if there are a lot of files going to one location, such as the case with the Windows and System32 folder. If it's one or two files, it's just easier to use one of the simple variables and type the rest of the path in.... for example: Nothing else goes to that folder, so it's easier to type it in like that.I actually wrote a script to locate a lot of the files. When it couldn't find the file at certain locations, it executed a folder search for each file via CMD, recursing thru the folder structure. I had to manually edit the output of that mess... In order to figure out the sound files, I looked in the TXTSETUP.SIF file. I haven't had time to look for the other files. The live patcher will have to look to see if the file exists before attempting to patch, just like the source patcher. In the case of the kernels, the right kernel is copied to the hard drive to some file. Each kernel uses the same resource file to mod it, so applying the bootscr.res to it will mod it correctly.... Thanks, Bober!

Ok, here's the latest version of the GUI. I've done a bit of testing to verify that things work properly, with both Pro and Home. Everything seems to work properly, so I'm releasing this version to the public! Download: XPtsp v1.0.10 beta 10f MD5: C36E0A1DAF2548A9C50D46885057D5B3, Size: 31.2mb What's Changed: - Updated resources to match batch beta 10. - Added code to check version number of files in order to avoid updating certain files. - Added code to remove read-only attributes from all files in source folder. - Added code to allow script to update files inside NR_IE7en.CAB. - Added new sections to XPtsp.ini for file locations for Live System Patching. - Added Segoe UI fonts to the add-on that the script creates. So, let me know what y'all think and if you have problems! Thanks! EDIT: I need some help finding the rest of the files... The new sections in XPtsp.ini lists where they are supposed to be and I've found about 95% of them. I need some help locating the rest of the files on an ALREADY installed system! If you want to help, please PM me with the location if/when you find them! Thanks! Off-Topic: Updated the download page with the entire changelog, as far as I can track it in the few minutes I looked. (I'll probably find more if I look more...)

Oh, yeah. I forgot to mention that I added code to allow the developer to omit files if they met or exceed a certain version number, per Ricktendo's request. I included two files in the new "NoPatch.ByVersion" section in the INI, as well as included links. The XPtsp.ini file will include file locations for live system patching. I've got 95% of the files located and I'm working on locating the rest of them. I think writing the code will be much easier than the source patcher, simply because most of the work has already been done! Eventually, I will include file descriptions in the XPtsp.ini file, as well as write up a component selection page to replace page 4. Anyway, GUI Beta 10f should be out soon, once I reverify Home is good. Thanks to everybody for your feedback and responses! Kal: I can include the font file(s) in the add-on that the GUI builds....

I've been fine-tuning my code and running tests. I've added code to remove all read-only attributes from the XP source, as well as added the NR_IE7en.cab code to the script. I've tested with XP Pro. I ran into one problem, which was quickly fixed. XP Pro looks great, installed without errors (except for the small one that I fixed). Patching XP Home right now, will run through a test with it. P.S.: I see that the thread title has changed, but I don't see the new link to batch beta 10.....

Bober: I just completed a successful XPtsp'ized XP install. No errors! Who-Hoo! I've got MrNxDmx's IE7 add-ons downloaded and will examine later today to add necessary code, as well as the other stuff you mentioned! Thanks for the feedback! EDIT: No new versions of the GUI have been uploaded yet. Please be patient! Thanks! bjfrog: The only difference between batch and GUI that I'm aware of is cursors. I'm trying to stay matched with the batch file on the resources.