Jump to content

dougiefresh

Members
  • Posts

    761
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by dougiefresh

  1. Testing: I've completed my testing with the OnePiece UpdatePack, OnePiece IE8 and Boogey's WMP11 Slipstreamer. With the exception of the repatcher INF error made in version 2.0.1.1, I cannot find an issue with any of the add-ons that might be breaking the script. WMPENC.EXE remains in every scenario that I've run, and I can confirm that the GUI does not modify the WMP INF file. Other: Because the SFX will not pass the path to the script under Vista, I'm rewriting the Theme Selection page in order to be able to browse for themes. It will list both the online and any local themes it finds, as well as tell you whether the local theme is up to date or not. This modification will help me with the testing of the script, as I will be able to use my local copies instead of downloading the themes in order to use them. Once the modification is complete, I'll upload the new version. I've had to move some pages around in the script in order to make room for new features as previously discussed. Page 7 will contain the code for downloading the Extra package. Page 9 will contain the code for downloading theme modifications, such as the different color AVIs for moving files. In addition, the language file has been reorganized to match the script organization. Here is a quote of the current changes to the language file: I'm also working on modding the script in order to change the CAD2009 add-on so that it matches the current theme. UPDATE: I figured out that if I right-click on the SFX and select "Run As Adminstrator", the SFX does pass the path to the script.
  2. newbeyninja: I've "fixed" an issue with the site that causes the download dialog not to show up, but to redirect to the batch download page. This fix consisted of removing the automatic forwarding that the site does to the file to get. So downloading any batch version will require an additional click. I hope that this is what you were referring to.... If not, let me know. Robi450: Interesting pictures... Would like to see the videoes, too. Perhaps a way can be found to include them via the GUI without repacking the "Extra"s folder....
  3. Results So Far: I've used the GUI to integrate the resources into a XP Home Edition source with the "Program Resources" group checked without any other add-on included. This includes the repatcher, the OEM info generator and resources used in the XP source. The VistaPix and Fonts/Cursors addon is included via the Extra's group. The repatcher's INF didn't properly refer to one of the files in the CAB file, which may have broke the XP install. But I've got more testing to do to confirm other add-ons aren't breaking the installation, so if anything else is broken, hopefully I'll find it quickly.... EDIT: It also occurs to me that I need to repack the CAD2009 add-on in order to replace the background that it uses. After all, if you are using a non-Green theme, does it really make sense to have a green background for the Vista-like Ctrl-Alt-Delete program?
  4. I'm starting my testing up to try to isolate the problem. Hopefully, I'll have an answer or two shortly.... EDIT (12 hours later): I've built a single XP Home install with the UpdatePack, IE8 add-on, and Booogey's WMP11 slipstreamer as specified by Mr_Smartepants. Made a copy and integrated the batch into one and the GUI with no add-ons into the other. Both source folders were installed in a VM with success. So I'm sure that the problem Mr_SmartePants found is an add-on related issue.
  5. I've tried to download the patches via the links on the website, but there are certain patches that I wasn't able to download. So uploading the whole batch of files would be appreciated. Thanks in advance and I apologize about the inconvenience that my request may cause. EDIT: Did the new version fix the bootscreen issue?
  6. Okay, I need you to upload the patches that you are using with Booogey's WMP11 Slipstreamer so that I can reproduce this.... PM me if you need a place to upload to.
  7. is going crazy....

  8. What's Changed in v2.0.1.1: - Updated AutoIt to newest beta version. - Added code to check to see if installer resides on writable medium. - Modified XPtspCom.INF to add RunOnceEx entry during Windows Setup. - Modified expanding code to return the internal filename of an compressed file. - Removed Invalid folder line from Theme Selection page. - Rewrote part of Theme page for bug workaround in latest AutoIt beta version. - Modified Components page so that counters are incremented for .NET Framework. - Changed list of web servers for downloading and updating components. Mr_Smartepants: This update should fix the missing file problem. I believe that when the GUI was extracting files, on occasion a file would get extracted to another filename. This situation wasn't picked up on the script, so the file literally got deleted. The new code literally looks for the filename extracted and passes it back to the calling function, so hopefully, there won't be any missing files from now on. EDIT: I think it is worth mentioning that I couldn't reproduce the WMPEnc.exe error you got, but I also couldn't download all the WMP patches to use with the WMP11 Slipstreamer.... The above mentioned fix should fix the WMP11 INF error, since the GUI doesn't touch that INF.... I've modified the INF to add a RunOnceEx entry during Windows Setup, so anything requiring last-minute patching will happen after the GUI part of Windows Setup has rebooted the machine. Hopefully, it'll take care of the bootscreen issue you reported. On other notes, I was unable to reproduce the Setup.exe bug that you reported.
  9. I've noticed two things about this add-on. In the Entries_XP_to_MCE05.ini file, the [sysoc] section is missing a line, which installs the Media Center components. I believe the section should read: Second, RyanVM Integrator does work if you add a backslash to each line, like so: cause if you don't, then RyanVM Integrator moves those files to CMPNENTS/MEDIACTR as I386, not to the I386 folder.I hope this helps.
  10. When I built the website, I noticed that every batch version had the color in the filename, but the Green version didn't. So I had changed the filenames so that it would appear to the world that the batch versions had a common naming scheme. This makes it easier to correctly id which theme was which, however, it seems that I forgot to update the first post with the new name. So I've updated the first post so that the download link is now correct, and changed the title to reflect the color that this theme is. I'm sorry for the inconvienence that this caused. By the way, the color of the original XPtsp Batch is Green. There is no version of XPtsp that doesn't have a color "preselected".
  11. Oops... I must have been sleeping when I compiled that code. I included some code that was going to help me combine icons together and didn't realize that the code had it's own GUI that it created! I've removed the "offending" code from DSI and uploaded v5.3.7.1. It's in the first post! Thank you for reporting that and I'm sorry about that.... EDIT: I just realized that my profile's email address on file points to an email account that has been closed for quite some time. I've corrected my e-mail address, so I should get notifications of new posts....
  12. I've zipped up the NeonBlue resources into a package for the GUI and uploaded it. The NeonBlue resources should be available via the GUI now. The NeonBlue extras will have to wait until "Extra"-selection code in the GUI becomes available.
  13. Mann41: I had moved the script in anticipation of adding the header and footer to it. The move broke the script. It's fixed now. Sorry about that! Mr_Smartepants: Thank you for the feedback.
  14. At this moment, I can't support the NeonBlue package via the GUI without some major alterations to the code, such as seperating the Extra's folder out and making the GUI download a Extra's package. Doing this will make the GUI SFX much smaller, something like 1.6mb in size, which will mean that the update code has to be changed as well. So while this release isn't everything I intended to do, this interim release works with the functionality provided by the new website, both for the counters and the site structure. All hits from the older versions of the GUI have been redirected to my Comcast account. I have no intention of updating the packages stored there, nor adding to those packages, so if you want updated packages, please upgrade to the latest version of the GUI. I am doing this as a courtesy to our users so that people with older versions can still use their copies. Thank you for understanding.
  15. Kirk, at what point did the GUI crash your machine? You will have to give more information in order for me to resolve the problem....
  16. What's Changed in v2.0.1.0: - Modified last-minute code to check the OS type before patching bootscreen. - Modified download page so that counters are incremented before each download. - Modified download page so that package is downloaded from correct location. Everybody: At this moment, I can't support the NeonBlue package via the GUI without some major alterations to the code, such as seperating the Extra's folder out and making the GUI download a Extra's package. Doing this will make the GUI SFX much smaller, something like 1.6mb in size, which will mean that the update code has to be changed as well. So while this release isn't everything I intended to do, this interim release works with the functionality provided by the new website, both for the counters and the site structure. All hits from the older versions of the GUI have been redirected to my Comcast account. I have no intention of updating the packages stored there, nor adding to those packages, so if you want updated packages, please upgrade to the latest version of the GUI. I am doing this as a courtesy to our users so that people with older versions can still use their copies. Thank you for understanding. =========================================================================== Mr_Smartepants: I apologize about the delay in fixing the problem. Hopefully checking for the OS type in the last-minute code will correct the bootscreen problem you found. I haven't looked into the missing WMPEnc.exe file or the advanced INF problem yet.... Mc Hammer: I don't have a problem if you want to translate the English.ini file (right-click to download. Or you can also translate the English.ini in the GUI SFX. Either way, I'll include the translation in the GUI once you've translated it. Be aware that the language files only covers the GUI, not the resources.
  17. I have managed to figure out how to make the site "compatible" with older versions by redirecting requests to the proper folder. That having been done, I'm moving the http://xptsp.filetap.com url to the new site since everything should work properly. EDIT: Struck everything out.... I've been told that the server times out if the download takes too long, so until v2.1.0.0 comes out, I'm moving the http://xptsp.filetap.com back to my Comcast account.
  18. I have managed to figure out how to make the site "compatible" with older versions by redirecting requests to the proper folder. That having been done, I'm moving the http://xptsp.filetap.com url to the new site since everything should work properly. EDIT: Struck everything out.... I've been told that the server times out if the download takes too long, so until v2.1.0.0 comes out, I'm moving the http://xptsp.filetap.com back to my Comcast account.
  19. Mr_Smartepants: I've managed to successfully build a XP Pro with the Media Center components with IE8 and WMP11 integrated. However, I haven't had time to do much else.... Everybody: Because of the major site restructuring to clean up the site, the current version of the GUI is NOT compatible with the structure of XPtsp.com. Please expect a new version of the GUI in about two weeks, which is probably when I will actually have some free work to work on it. In addition, I'll have the NeonBlue package ready for use with the GUI. Unfortunately, the new package uses a completely different Extras folder, so I plan to split the Extra's folder off of the GUI SFX and include both as a downloadable package, too.
  20. First post updated (again.... argh!)
  21. I was gonna test the various XP installs, see if I can duplicate the problem on various systems. I realize that the bootscreen isn't an issue on XP Pro, but I'm hoping to figure out what's up with the patcher across a variety of installs. I can't download Rick's XP to MCE add-on, nor the Win7 mod add-on. Any chance you can send them to me? Thanks!
  22. Is there any chance that a mirror can be posted? It seems that the link in the first post has expired.... Thanks a lot!
  23. Wolfsoul: Batch v1.4.7.1 is available at the XPtsp site. Unfortunately, it's not listed on the website at this time. (That'll be fixed this weekend) So here is a direct link: XPtsp.v1.4.7.1_batch.exe. As for the Batch changelog, you would have to look at the XPtsp Batch v1.4.7.1 thread for more information, as I don't have that information. The GUI changelog is available here. EDIT: I'll be looking into the repatch issue as well. Thanks for the info... Mr_Smartepants: Thanks for the info.... EDIT: I'll build an XP Pro using the WMP11 and IE8 add-ons you specified. However, I forgot to ask which update pack you were using....
  24. I'm sorry my response to your questions has been glacial.... Life has been kinda hectic lately. I think I've got the bootscreen resource files straightened out, courtsey of Mr. FixIt. I'll upload them this weekend. In order to try to reproduce the issue, we need more information. Please tell me what options you were using when you integrated using the GUI. When you were using Bober's batch, did you use the add-on or just the batch version? Which IE8 and WMP11 add-ons were you using to create your install? Was your XP Pro copy a OEM, retail, or VLK? I assume it's an English version of XP, right? Hopefully, with more information, we will be able to determine what's causing the problem....
×
×
  • Create New...