dougiefresh

After intregrating the XPtsp package, I found XPTSP.IN_ in the I386. So I modified the code so that different values would go in TXTSETUP.SIF. Hopefully it will solve the problem. UXTHEME.DLL is not being patched correctly by the GUI. The GUI tries to fix the checksum on the compressed file.... not what was desired. So I fixed that. SETUP.EXE wasn't present in .10d and I fixed the AutoPlay folder so that the XP Pro image is in there, not Home as well. I had modified the code to read the INI for other stuff needing done. It worked in the uncompiled version, but for some reason, the compiled version is being like a bitchy little girl. So I moved the code back into the script. OEMGEN doesn't launch? Oh, lord.... WBEM has been fixed (again). Hopefully, this time it will stay fixed! Why does this problem in Setup happen? I'm guessing that it's one of Microsofts "gifts" to those that integrate stuff. Maybe they changed their philosphy to "If you screw with it, you will have more problems! Muh-ha-ha-ha!" (or not...) EDIT: The new version is available online at my site.

Hey, Bober. Regarding the primary/secondary IDE controller driver issue, I found a file called STORPROP.DLL in the SPx.CAB/DRIVER.CAB file that is being modified. Maybe since the driver is signed, maybe this file is part of the driver? Just a thought.....

Ok, I've recompiled the archive after making the detection changes and reverting the resources back to batch beta 8. Here it is: Download Page: XPtsp v1.0.10 beta 10d MD5: DE0D6DF6C4E3752BD9128496DC9567EB, Size: 28.8mb Let me know how this works for you..... EDIT: Tomorrow I'll start on the live system patching code. Hopefully, I'll be able to integrate the new code into the script without many changes.... Off-topic: I've received 203 hits on the download page so far....

Thanks for the idea, galileo. However, I've already checked into other ways to ID a Home and Pro copy and found this forum thread at MSFN.org. To sum it up, the first 5 digits of the PID are different numbers for different versions AND languages. I have the PIDs for English versions, but the localization problem comes back to bite me because, for example, Czech has 76389 and English has 76487 for XP Pro VLK. Not helpful.... (what I found, I mean!) I'm going to nLite both a Home and Pro version and see whether the nLited Pro version has any files that the nLited Home doesn't. I think that is going to be the best way to do it, as any other solution will be problematic.... Hopefully, the author of nLite won't figure out how to delete whichever file I select.... EDIT: I've completed the nLite-ing of both OSes, removing everything it would let me. I'm selecting SECEDIT.EX_ as the file to check for if the install is XP Professional. I will try to release another version soon. (I'm not going to use BOOTCFG.EX_ because another add-on that was created adds the program to the install, so a Home Edition with that add-on would be detected as Pro.)

Well, I'm checking TXTSETUP.SIF to see if I can find "Home Edition" or "Professional" in the file. If I find "Professional", I check for MEDIACTR.CAB as my check for "Media Center". It just struck me that those strings are probably localized for each language and these strings work only for English versions of XP....

Okay, good to know about the drivers thing. This source thing is getting annoying.... I can't seem to write the code correctly on everybody's computer so it will determine Home or Pro without checking for a file. I wonder how the RVM Integrator or nLite does it....

GUI Version 1.0.10b10c has been released. Download Page: XPtsp v1.0.10b10c MD5: A2524BDA4106861D73795DDE61D5BCF6, Size: 29mb What's Changed: - Since the cursors got deleted from GUI beta 10b, they are re-included. - File structure changed to move cursors out of Extra folder. - UXTHEME and WBEM fixes now work correctly. - OEM Info Generator batch now is run silently with a GUI notification window. Bober: If they are in batch beta 9, they are in this release. EDIT: When I run my tests in Virtual PC, I get 3 messages about unsigned drivers. One is for a battery driver and the other two are for the IDE controllers. Is this normal, cause I don't get the IDE controller messages without the XPtsp pack integrated? (The battery one I get sometimes...) Does the SFC patch take care of this? Other than that, it installs properly. Thanks.

(removed) EDIT: I removed this because I had confirmed that the file did not transfer properly before repeat power failures at my house.

Gorki: I've uploaded .10b, which has the debugging statements removed to enable the rest of the patching code. Sorry about that. (EDIT: The debugging code omitted everything but the UXTHEME patch, which is the last thing I was working on.) Something I forgot to mention in my last post: the GUI is intended to be seperate from the RVM Integrator and not require the add-on version, instead integrating those changes directly into the XP source files itself. treblA: Which version are you using? Are you using GUI, batch version, or add-on version? EDIT: My experience with that error usually meant that some registry setting isn't correct (wrong type setting was common for my experience).

New GUI Version v1.0.10.10a is now available. Download Link: XPtsp v1.0.10.10a (MD5: ED2D234C3B5FB2D85EBCEAFC5B91D6F3, Size: 28.8mb) What's Changed: - Instead of using EULA to determine OS type, TXTSETUP.SIF is searched for the necessary strings to identify Home or Pro. If Pro is identified, MEDIACTR.CAB is looked for to determine whether it is MCE. - WBEM and UXTHEME code has been fixed and confirmed operational. - Included all resource changes that are included in 1.0.10.8 batch version. Let me know if this works for you and if there are any problems! Thanks! ======================================================= Bober: Concerning resource changes in 1.0.10.8 batch, I got them. Thanks! Stimpy: I downloaded the most recent version of the Integrator and intregrated IE7 into a clean SP3 Home OEM source and checked WBEMOC.INF. This patcher apparently performs the same patch that the Integrator does (I don't have the source so I can't confirm 100%). So, yes, this patcher will be able to "detect" the patch made by the Integrator and perform the fix correctly. nLite is a different question, one we will be able to answer once a version comes out that can make the fix.... Gorki: When I began building the GUI, my goal was to duplicate the functionality of the way the batch file worked. My goal slighty changed to make sure that the GUI will be able to handle new resource files easily. I've added some stuff that the add-on was capable of, like the GUI resolution change and the UXTHEME hex-edit. Added options to add the resource files and new cursors to the mix, and finally the WBEM fix. Is there a difference in processing? I'd say that any difference between the two is small and reflects how the processing takes place, not the final result. To me, it is particularly important since the goal is to create a GUI that duplicates the functionality of the batch file. I hope this answers your question. The new version should be capable of correctly figuring out what type your OS is. Yes, you can place it in the folder you want to patch and the script will pick up on the folder the SFX was executed from.

Sloppy, I seem to be. I forgot that the Browse and Source code both contain the EULA.TXT code that doesn't work. I've changed the code over to the new stuff. I'm also not relying on EULA.TXT file anymore, instead I'm using the TXTSETUP.SIF because it also has the strings I'm looking for. This should take care of Stimpy's problem.... As for the AutoPlay, yep, I'm missing some files.... I'll put them back in. Sorry about that. EDIT: Do you want the files amnesia provided in with the new release? Also, the WBEM code doesn't work.... I'll try to fix it b4 next release.... EDIT2: I've fixed the WBEM code. I included the path twice by mistake.... EDIT3: I just completed my ISO test. The GUI Setup found the XPtsp.inf file just fine. Of course, the WBEM bug was a smaller pain this time around (just because I knew what I was doing). The UXTHEME patch didn't take, though. So I have to fix it before the next release. Just thought I'd let y'all know.

I took a clean XP Home OEM source and integrated the XPtsp package with the resources and cursors included. I found the XPtsp.INF file in the I386 folder. I need to compile an ISO to see if I can reproduce the Setup error. Mr_Smartepants: If you look at the discussion referenced (particularly towards the bottom), the add-on removes the WBEM "fix", then reapplies it. So if another program implements the fix, the patcher will unfix, then refix the WBEM problem. In essance, it does nothing to an already "fixed" installation. My test was performed on a clean XP Home OEM source without an Update Pack or any add-ons, and I found that the WBEM bug is present. The WBEM fix needs to be in this patcher because someone who hasn't used the RVM Integrator or nLite (like in my test install) will encounter the WBEM bug and THAT is not desirable! Stimpy: The patcher never searches for Setup.exe, only reads the EULA to determine OS type. Putting the EULA.TXT file in the source folder should allow the patcher to recognize which OS you're integrating into. I just figured out that TXTSETUP.SIF also contains the string I need to distingish between Home and Pro. Searching for MEDIACTR.CAB will distingish between Pro and MCE. I'll implement these changes once I test the new ISO.

Thank you, stimpy and amnesia! I didn't mean to leave you out of my praise. Thanks, rick for starting the original V'iso project in the first place. EDIT: Thank you, everybody who has contributed to this wonderful project! EDIT2: I just received a report that XPtsp.inf isn't found during the GUI setup. I will look into this once I get home this afternoon (it's 3am here).

Bober: I just looked at the install I did under MS Virtual PC 2k7 and I'm like "DAMN, that looks nice!" I like it better than XPize! Thank you very much for doing such a wonderful project!

I've actually had some time to test and correct bugs & problems as I found them, and I found some whoppers! I've fixed them and compiled the newest version. Here it is: Download Link: XPtsp v1.0.10.10 MD5: CE5AF82A943149558754A431CAC85C65, Size: 27.7mb I've got the WBEM fix coded in the script, as well as fixed the UXTHEME patching problem. I also saw duplicated AutoPlay files, so I removed all duplicated files from those folders and made sure the code was updated to reflect this. I don't think there are any more problems, however, please test this package and let me know if you encounter any problems. Thanks for your patience, everybody! EDIT: Oh, yeah, I remember a report about Home and Pro files mixed in, I'm pretty sure I fixed that by pulling files from beta 7.

Ok, I've been working on this all morning, so here's what's up at the moment. I've got the Browse button fixed, as well as rewrote the OS type detection code. It no longer looks for specific files, but looks at the EULA.TXT instead. I've fleshed out Page 6 and included code to create an ISO. I also replaced CABARC (which I put in there) with MAKECAB (which came with beta 7), mostly because CABARC was badly mangling my XP source. I'm working on testing the code right now, so please be patient. Thanks! mr_smartepants: I did see your bug report. I have fixed the code so that it scans for "Home Edition", "Professional" or "Media Center". I just need to run another test, seeing as a recent addition to the code resulted in errors.... Give me about an hour. Thanks! EDIT: It appears that I have to manually fix the WBEM problem, too.... This might take a little while longer than expected.... EDIT2: I've followed these directions to temporarily fix the problem during testing. I will try to incorporate the add-on by MrNxDmX into the script. EDIT3: Installation is proceeding normally. I fixed the WBEM problem in the script, as well as included the INI files that were left out.

I looked at the EULA you sent and figured out the problem. The search phrase is on the SECOND line, not the first (like Home and MCE). I have fixed the problem and am uploading now.... EDIT: Upload has been finished. It will now recognize XP Pro as a valid OS....

Download: XPtsb_v1.0.10.9.exe MD5: 5383C38208F962450868E2C1D2F27CEE, Size: 28.3mb Changes in this version: - All three previously mentioned problems are fixed. - Implemented the AutoPlay copying code, as I forgot it in my inital release. - Added a progress bar during compression so that the user won't be wondering what's going on... - Realized that when a repatcher was written, it would need the tools that the archive came with, so XPTSP.INF has been updated to include those... - Re-organized the code so that related functions would be grouped together. - Moved some code from the script itself to XPTSP.INI for future expandability.... (yeah, I know it looks weird) EDIT: Re-uploaded because the AutoPlay files were missing.... TreblA: Do you have a EULA.TXT file in your I386 folder? If not, the script won't pick up on it.... Is it English? Can you send it to me?

I've fixed the download link to the program. Last night, I lost my net connection. It came back on sometime after I went to bed. So I couldn't fix the foobar that I made.... I've received 3 reports. The first is that the Browse button doesn't work properly. I've fixed this. The second is that the script creates a CAB file containing the resources, regardless of whether the user wants the resources included. I've fixed this by pointing the script's archival code to the proper folder. A side effect of the 2nd bug reported happens during Setup, where Setup complains about missing files. It's because the Aero cursors and the script files aren't included in the XPTSP.CAB file that the script creates. The 3rd bug will be fixed by fixing the 2nd. When I get home today (it's 4am here), I will compile another version.

Hey, everybody! I have gotten a fair chunk of code completed, along with debugging it. I wish for people to beta-test it. I've gotten permission from Bober to use version 1.0.10 beta 8 as it's version number. So here it is: Download Link: XPtsp v1.0.10b8 MD5: 8C49F21F9E2965E0F7806AB84A6E1EF9, Size: 28.4mb Special features of this beta: - UXTHEME.DLL can be patched directly by the script. (based on Zacam's patch) - New Aero cursors can be installed by the script, along with modified themes using the new cursors. - Resources and the patcher can be included in the XP source. (Repatcher not written yet) - Option to include the OEM Info Generator at startup. (Not written yet) - Option to change GUI Setup resolution to 1024x768, 1280x800, 1280x1024, 1440x900, 1600x1200, 1680x1050, 1920x1200, 2560x1600 (all resolutions based on Zacam's patches) Things to note about this release: - The script doesn't overwrite the AutoPlay files yet.... - No version checking takes place in this beta, so if updated components that aren't updated through Windows Update (like Ricktendo's Windows Easy Transfer add-on ENU_user's or Movie Maker upgrade add-on) are included, patching these components may not result in the expected results. - The "Live System Patching" code has not been written yet. - Page 2 is not shown, because of the above reason. - Page 6 has not been completed, but will indicate completion of the integration. - If the archive is put in the XP source folder, the script will pick up the folder that the archive resides in and use it as the default folder. Otherwise, source folder will be blank. - OEM Info Generator produces a message box indicating it was launched, but doesn't do anything else. - Repatcher hasn't been written yet, so adding the resource files to the source doesn't really accomplish anything right now. - I've mashed it down as much as I can using 7zip.... (in case anyone is interested) I don't seem to have the time to fully test this because of long hours at work, so I'm asking (almost begging) people to check and evaluate this release. I need to know if the script produces the same or similar results in the XP source as version 1.0.10b7, preferably with an XP SP2/3 without an Update Pack (although with an Update Pack would be interesting as well). Any assistance would be appreciated! Thanks! EDIT (1.5hr after): Bober has updated some resources, but I don't know which ones. EDIT (2hr after): Fixed problem with Source browse button.

Yeah. Not problem, I got them added.

Well, I'm gratified to know that people think I'm good, but I'm not that good. I can't alter a resource file without a resource editor, and I don't know enough to programmably alter a resource file. Bober: About the cursors being part of an add-on: Ok! Can do. EDIT: Completed modification.....

Here's what you sent me (minus the INF): Cursors.rar (The cursor names end with a "_l") EDIT: I don't care which way we do it. Frankly, it would be Ok with me if we overwrote the cursor files.... EDIT2: We don't HAVE to edit the theme files.... but if I add them as an add-on, then if you want them as the default cursors, the theme file will have to be edited, either manually (by editing each theme file) or automatically (by way of the script).

Well, ummmm.... I thought you want to include them as part of an add-on, not as a replacement. Stoopid me, I forgot that this project REPLACES files in the XP source.... My bad, I'll fix it! (It'll be MUCH easier to do it that way, anyway!) EDIT: I just looked at the I386 folder just after I posted. There's a bunch of .CU_ and .AN_ files.... Bober, please tell me what files go where so I can implement the replacement! EDIT2: I wonder, does WinCert make a emot-icon that has a head put in 2 hands? If so, where is it? I NEED IT! LOL! EDIT3: Updated Page 4 again, if anybody is interested....

Yes, however, since there is an option to include the Aero cursors, the program should edit the theme itself. I just haven't programmed that in yet....