dougiefresh

Please note that this add-on requires .NET Framework v2.0 in order to operate. Failure to install it will result in no navigation buttons or address bar by default, however, it will show up once .NET is installed. QT Address Bar 0.9.6 Replaces the standard address bar to make your XP addressbar more handy, like in Vista. QTTab Bar v1.2.2.1 Adds tabs to your Windows Explorer and replaces the standard buttons with the QT Standard Buttons. file: Doug_QTBar_AddOn_v2.0.7z File Size: 941kb MD5 Hash: 211B1BF6E22BCF8E6DC2E682B5566321 ChangeLog: v1.0 = Initial release of add-on v1.1 = Fixed entries to add correct filenames to the XP source. v2.0 = Added uninstaller so it is now removable. NOTICE: I've corrected the incorrect version numbers in the topic title by swapping the 2 version numbers around. Sorry if this lead to confusion for anybody! QT Address Bar 0.9.6 ONLY mooms modified my original add-on to remove the QT Tab Bar portion and added a working uninstaller to the add-on! Thank you, mooms, ricktendo64, and Kelsenellenelvian!!! Uninstaller Present file: QT_AddressBar_inf_AddOn_v2.2.rar File Size: 117kb MD5 Hash: B7BEFB40E8834F461F5857530036FB6A No Uninstaller Present file: QT_AddressBar_inf_AddOn_v1.2.rar File Size: 116kb MD5 Hash: CD248071B17DE01200BC1E7FA8B94980

Sorry about that! I fixed the link in the first post!

Ok, I thought I'd show you what I've been working on. (or maybe I'm a little bored...) It's not done yet, so hopefully by the time Bober gets his batch v1.4.7 done, my v1.4.7 will be ready to roll. So here are the preview screenshots for my next release: Revised Page 8 (Additional Options): Revised CPL Applet:

UberIcon v1.0.4 Quote from UberIcon's HomePage:: Quote from UberIcon's Features Listing: Other add-ons are simply the installer wrapped in a self-extracting archive. This add-on is a true add-on. There are several additional plug-ins that are included in this add-on: "Blur", "Break", "Fly", "Ripple", "Roll", and "Runaway", as well as the newest "Explosion" plugin. Filename: Doug_UberIcon_AddOn_v2.1.7z File Size: 1.25mb MD5: 26176A9504141BD5862F51A499A64A43 Changelog: v1.0 = Initial release v1.1 = Added instructions and INF sections for setting default plug-in. v2.0 = Removed original uninstaller and added uninstaller in the INF. v2.1 = Fixed uninstaller and added Explosion plugin.

According to this website, "GrpConv" is the group conversion code that Windows uses to convert groups to folder.

I was looking for a way to silently install the INF associated with an add-on. I found this website, which explained how to do so. To sum it up, the command line should read: rundll32.exe advpack.dll,LaunchINFSection myinf.inf,DefaultInstall,1where myinf.inf is the INF that you want to launch and DefaultInstall is the section to use for installation. The 1 is an instruction to RunDll32 to run the command quietly, while a 2 would instruct it to use"no GrpConv", whatever that means. The numbers can be added together to get 3, which would instruct it to run quietly and with "no GrpConv". Please move that you will have to manually move the CAB file into a i386 folder for most add-ons in order for this to work. If you don't, the user will be prompted for the location of the files.

What's Changed in v1.4.6.10: - Fixed code so that the current file info is taken out of correct registry branch. - Added 7za.exe and Process.exe to XPtsp.CAB, as it is impossible to update without them. =========================================================== What's Changed in v1.4.6.11: - File structure changed in order to better support theme support. - Added environmental fix to move resources from "Resources\Green" back to "Resources". - Modified code to move wallpaper from "Resources\Green" back to "Extra". NOTE: As I was starting on the theme support for this script, I had made some modifications to the file structure of the SFX. Each theme has it's own "unique" wallpaper and I had to move the wallpapers to the resources folder so that the theme would be built properly. The building script rebuilt the v1.4.6.10 SFX with the new file structure and uploaded that. Naturally, v1.4.6.10 is incompatible with the new file structure.... It has been taken care of in v1.4.6.11. I apologize for any inconvenience that this may have caused.

I'd be happy to take a look at your latest add-on version and see what I can do about the problem.....

What's Changed in v1.4.6.9: - Fixed uninstaller so that program isn't launched again and shortcuts are removed. - Added code to flag which programs and/or options were set during installation. - Added message in log indicating how long patching took for non-repatching activities. - Modified code so that the working environment is fixed if required for compliance. - Moved all lines from Current.ini into the registry. The updated compiled script should be available via the updates functionality. The script will take care of moving the settings from Current.ini into the registry for those updating the patcher. Update: I'm sorry.... I really don't know how this topic got closed.... but it's open again! Anyways, my computer is running as it should again, so updates should be coming out without the problems I was encountering prior to complete re-install of my computer.....

Everybody: For some dumb reason, my computer isn't allowing me to upload to my Comcast site or the WinCert server. I finally managed to do so using another computer and I've updated the first post to reflect this! avneet: I'm glad to hear that the bug you reported is finally fixed! It drove me crazy trying to figure out what was happening with the code.... just to figure out that it wasn't the code, but XP Setup was the problem! www.CyberKhalsa.Co.Nr: Please read 2nd paragraph of first post. Thanks!

First post updated to point to new version.What's Changed in v1.4.6.8: - Renamed XPtsp.inf to XPtspCom.inf so that XP Setup doesn't copy wrong file to folder. It's not, yet. I've been focusing on the GUI at the moment.

I just figured out what's going on during XP Setup..... During processing of XPTSP.INF, Setup is extracting XPTSP.IN_ into XPTSP.INI from the i386 folder instead of from the XPTSP.CAB file.... Of course, this results in a file that doesn't have in it what's expected. I have come across this STOOPID XP bug during the development of DSI, and I should have remembered about it! So, I'm gonna rename the XPTSP.INF to XPTSPCOM.INF. Doing so should fix this particular bug. If you want the XPtsp.ini file right now without reinstalling, browse to the i386 in the XP source folder and open XPTSP.CAB. It's in there. Just extract it to %ProgramFIles%\XPtsp, overwriting the current XPtsp.ini. That should fix that error message that you found in the patcher. EDIT: Forgot about SYSOC.INF as well..... first test was a bomb.... EDIT2: Second test was successful. Only, did the integration ever produce more than one shortcut? Cause I only got one shortcut created for XPtsp.....

:ranting: Arghh, stupid code....... :doh: :shy: Ok, I've fixed the code so that two command-line parameters, "/OEMINFO" (which is the OEM Information Generator) and "/CACHE:5" (which is Clear Icon Cache, Then Delete Script function) get processed before anything else happens in the script. I'll post the updated SFX shortly. EDIT: Here is the changelog: What's Changed in v1.4.6.7: - Added "/MODIFY" switch and "Modify XPtsp" shortcut to call Component Selection. - Modified Page 7 to clarify what checkboxes mean during a non-install Component Selection. - "Modify files" in CPL re-enabled after v1.4.6.6 disabled that functionality. - Modified code so patcher completes uninstallation successfully w/o XPtsp.ini present. - Modified code so that OEM Info Generator completes successfully w/o XPtsp.ini present.

What's Changed in v1.4.6.6: - Fixed problem where message about missing "Clear_WFP_Message.vbs" keeps popping up. - UXTHEME hexing code modified to fix "The visual styles could not be applied" problem. - Fixed problem where Repatcher was launched and after repatch, Page 7 was pulled up. - Flagged groups as non-patchable to avoid "mystery file" repatching problem. - Moved code around so that internal file list gets built at beginning of program. - Rewrote Page 7 file difference function to return correct values for each file. - Modified code so that functions read the proper files for XPtsp re-installation. General Notes: - Please note that once the updating code is confirmed working, the "XPtsp_Diff" archive in the first post will be removed, as the updating code within the script will be taking care of that function. - Installing XPtsp GUI on a system that has been installed/integrated previously by the GUI will result in only the files with modified resources being changed. - I received a request to add a shortcut to invoke the "Component Selection" code in an already installed version. I forgot to put it in this version, but I have added this and will be available in the next version.

The only place that "LivePatch" appears is in the i386\XPtsp.INF file. The XPtsp.INI is stored in i386\XPtsp.CAB in the i386 folder. I've modified the INF section labeled LivePatch to LiveInstall to try to avoid confusion between the 2 files.... I've modified the script to resolve the filenames at the beginning of the script instead of at several points in the script. Not only should this resolve this, but it should make it easier for me in the future.... ................Huh? Live patch addon... what's that? The GUI should be able to build the INF/CAB file combo and place it into a i386 source without problem. I can't recommended using Bober's add-on along with the GUI. It may work, I'll grant you that, but you may have problems doing so. Then again, you may not have problems.... I don't know. If you're asking whether you need the INF/CAB combo in your XP source folder, it's purpose is to provide repatcher abilities post-installation. Naturally, backups aren't available for this situation.... If you're not asking that question, then you'll have to explain to me what you're asking..... Sorry about that! The problem (which I didn't foresee) has been fixed in the GUI. Are you needing a virgin copy of SP3 UXTHEME.DLL?

When do you get this error? Cause it doesn't occur during installation.... If the theme fix fails, what you will have to do is extract a copy of UXTHEME.DLL from your XP source (hint: run EXTRACT UXTHEME.DL_ UXTHEME.DLL) into the %ProgramFiles%\XPtsp\Backup folder, then run the fixer proggie.... Doing so should work....

It is a problem with uxtheme.dll. It happens when the sequence of bytes to replace is replaced not once, but twice. I thought I fixed that problem.... dangit! Give me a few minutes and I'll try to get you a solution.... I've fixed the code so that this doesn't happen again (hopefully). Unfortunately, the "Modify Files" code (can be found in the CPL applet) doesn't work. I tried this with the installer and it didn't work there. I had forgotten about the CPL applet, so it is still enabled. I have to rewrite this (and other) code in order to make that work correctly.... So, I wrote a quick little program to fix the problem. Fix_UXTHEME.exe should fix this problem on your system. (MD5: d3cb373aaaf7250bf8323095def1aba0, Size: 251kb)

avneet: Ok, Page 3 (the page where you select whether to do a Normal Install or an Integration) doesn't appear when the patcher is running on a Non-XP machine (such as Windows Vista). It will automatically default to the "Integrate To Source" option, unlike versions prior to v1.4.6.4, which just skipped that page (intentionally) and proceeded to try to install itself on the OS, regardless of the actual setting. Now, if you want this page regardless of the OS it's running on, I can modify the code to do so. But I don't think it would be a good idea to do so on non-XP systems. This patcher was only intended to be run on either a XP system or a XP source folder. It may work on Windows 2000, but I don't know. I doubt it would run on Vista, but then again, we are modding the OS to look more like Vista, so what would be the point? How does the rest of the program run for you under Vista? Do you see Page 5 (Live Install) or Page 4 (Integration)? When answering this question, make sure you're paying attention because the pages look alike! Thanks for the feedback! (EDIT: Ooops! Looks like I didn't pay attention when I posted the screenshots.... Page 4 and 5 were swapped! I've fixed this issue with the 1st post, so the correct images will come up now!) Everybody: XP Theme Source Patcher's web site has been reorganized and updated for completeness. I've got more work to do on the site once I complete the GUI, though.

OOOPS!!! I did it again, i messed it all up.... lol! No, really! :shy: I'm sorry, guys! I've uploaded v1.4.6.5 with the corrected code so that the patcher can integrate correctly again.

What's Changed in v1.4.6.4: - Rewrote OS detection code for Live Installs, since Vista is detected as XP on some systems. - All MD5 hashes are updated per GUI build. - Removed all "About" links from installation pages. - Added Page 2 for a License Agreement. Former Page 2 moved to Page 1, Page 1 to Page 0. - Fixed Page 3 to force integration into a XP source instead of installation on non-XP systems. - Fixed code in Page 7 that resulted in script aborting with recursion error. - Fixed problem with Page 7 in which unchecking group didn't uncheck items in group. - Fixed problem with Page 7 in which unchecking System Restore checked Boot screen. - Removed Maintainance Mode from the script, as the functionality was redundant. - Added "About" tab to Control Panel applet, with credits, thanks and links. - Added "Updates" tab to Control Panel applet. - Some files moved around so that all parts of a particular resource are together when zipped. - Fixed Page 9 so that elapsed time is figured BEFORE calling next page. - Fixed Repatcher code so that files that user didn't want patched don't get patch. - Found MCE wallpaper location on Live system, add locations to XPtsp.ini. - Modified all pages to disable current page after pressing Next/Start button. - Modified replace file code to add file check in %WinDir%\LastGood\System32. - File replacement happens at system restart now to get a few stubborn files replaced. I've been experimenting with code to install only the resources that have changed between versions on systems with XPtsp already installed. However, I haven't gotten far. As a matter of fact, I'll probably have to rewrite some portion of the code in order to get it to work properly. I haven't had the energy lately to do so and decided today to release what I've got. Oh, yeah! I almost forgot! Anyone running the patcher on a Vista system, please let me know if the patcher now works correctly integrating on Vista. I don't have a Vista machine available to test on. Thanks!

avneet: Please check your PMs. Thanks! STATUS UPDATE: Repatcher via CPL works. Repatcher at system boot kinda works. Installer on non-XPtsp-patched system works. Uninstaller has been fixed. Various other issues fixed. What I'm working on right now is the code for "Installer on already XPtsp-patched system". It seems to pick up which files need to be patched in order to bring the system up-to-date, but then seems to complete ignore the entire list. I've been struggling with trying to figure out what is causing these problems, but I'm telling you, it's getting irritating with 3400+ lines of code to search through.... I'm hoping for a new release tomorrow. It just depends on how lucky I am with finding a solution to this problem.

Future of DSI: I found some code that will help me to correctly ID not only drive types, but media as well. This means the Icon Theme format will have to be updated. It won't tell virtual drives from real drives, but it's much closer to the solution than my code is. So once the new code is integrated, DSI will stop attempting to detect virtual drives, as the code never worked to my satisfaction anyway. Thought I'd let you know! I'll also fully implement Component Selection, since I've written a fully working version for XP Theme Source Patcher, which has about 400 files to choose to patch or not, another 100 files to install or not, and a few other options. I'm sorry that this project hasn't received much attention in a last few months, and NO, this project isn't dead yet. How much farther it can be taken is questionable, though.

I'm sorry. I guess I misunderstood what you were saying. I've fixed that error in the script, although it looks like I have a ways to go before repatcher works correctly. I figured out what is going on with the Task Manager. The appropriate res file wasn't copied into place prior to copy the resources. That's been fixed. I'm gonna look into the programs issue that you mentioned. I received a PM, as well as a video showing the error in the GUI, about a script recursion error on the Component Selection page. It took a while to figure it out (not to mention quite a few code changes), but it's been fixed.

What's Changed in v5.3.5.4: - Added new command-line parameter "/STARTUP" to deal with delay at system startup. - Removed general delay at program startup. - Altered installer and GUI to add new parameter when writing value to registry. What's Changed in v5.3.5.4: - Fixed how the code generates it's Run entry in the registry.

Mona: He wouldn't see the Page 3 screen simply because he is not running Windows XP. This is by-design, as the patcher is intended for XP. avneet: Ok, I've looked through the code and found that I ASSUMED that the Integration option would be selected by the code when running the patcher on a non-XP system.... An assumption that was not only incorrect, but resulted in the patcher trying to patch the non-XP system. This morning I fixed that situation, so the next version should work with Vista for patching a XP source folder. Sorry about that! Second, that screen that you showed: Is that on Vista? Because if it is, then that certainly would back up the statement that it tried to patch your OS, not a XP source folder.... and it would confirm my statement in the last paragraph....