Mr_Smartepants

Yes, there are key files in your XP source disk that determine whether the source is Home/Pro or the license is Retail/OEM/VLK. dpcdll.dll pidgen.dll setupp.ini setupreg.hiv The files themselves are all named the same for each version, but the contents of the files are all different. Since XPtsp uses a batch file, I suppose the easiest method would be to check each files MD5 or CRC checksum then compare that to a list for possible match. Or (easiest for Bober) the user could be presented with a menu of choices "What source is being used: 1) Home 2) Pro" etc. Wow Proxis, that login looks nice. I wonder if the author would agree to it's inclusion?

Yes, LastXP is warez. :thumbsdown_anim: Unfortunately, all good work gets pirated eventually. DriverPacks have been targets for a long time. XPtsp will be no different unfortunately.

I love the new screenshots! :thumbsup_anim: Absolutely FABULOUS JOB guys! Really amazing work.

He didn't integrate any driverpacks. It's an nlite issue with the two drivers. Nice to see you back Muiz. :welcome:

I like the new shutdown logo.

I agree, any of the first three banners look great. Wow! :w00t: That display properties panel looks awesome!

I also like the first bar, but to call it a 'progress' bar is a misnomer since it doesn't show how far you've gone or how much is left. It's more of an 'activity' bar. The second bar is a true 'progress' bar. Too bad we can't have both merged.

You know, I didn't even check. The last test I ran on my notebook last week did change the intro music. But I can't remember which version I used on that iso.

Nevermind, it's an RVMI issue. I unchecked the 'optimize system files' & 'Use Advanced Settings' and all is well. Weird. I'm integrating in Vista64Ultimate environment. Maybe that explains it. Whatever! :w00t: This patch/addon is awesome!

Doesn't work for me. Using RVMI 1.5.3 on a clean source I get a "Error, no entries*.ini found, exiting". Tried about 10 times in a row, same result. I'll play with the entries file to see if I can get it working. *Edit Yep, deleting the Hexedit sections makes it integrate fine. More testing... *Edit 2 Weird, the hexedit section is identical to Zacam's uxtheme addon...but his works. :/

Cool. Ooh I just caught the screenies on the other thread...looks nice. Does the OOBE screen change based on XP version (Home/Pro/MCE)? Or just Pro? I would recommend the XP Ultimate OOBE screen from here: http://www.wincert.net/forum/index.php?aut...amp;showfile=69 It's all about the branding.

Looks good! Although it would probably work fine if you changed the .ini From this: [RunFile] XPtsp.exe,HIDE XPtsp.bat To this: [RunFile] XPtsp.exe,HIDE Since XPtsp.bat isn't included in the [filemove] section of the entries.ini. It would just generate an error in the log file, not really a problem. Also, are you sure you want to add the hexedit section? There are many patches out there already for that, it's redundant. Just my opinion. Good job! I'll try it later and report back.

I actually just made up that term. A list of entries.ini commands recognized by RVMI are listed here: http://integrator.siginetsoftware.com/inde...ual&entries If you don't declare a directory, RVMI assumes i386. Then ..\ is used to go to the source root. Hope that makes sense. %CD% is a good variable, it represents Current Directory.

Well the default "..\" is the root of the target i386. The syntax used is: [FileMove] test.exe,..\* ; moves the source file from the working dir to %XPtarget%\ dir (root). test.exe,..\i386\* ; moves the source file from the working dir to %XPtarget%\i386\ dir. SVCPACK\test.exe,..\OEM\* ; moves the source file from the SVCPACK working dir to %XPtarget%\OEM\ dir. SVCPACK\test.exe,..\$OEM$\* ; moves the source file from the SVCPACK working dir to %XPtarget%\$OEM$\ dir.

Good point. Yes, you're right. Well, typically the updatepack gets integrated first, then the addons, then the optimization. But just to be on the safe side, this should be done after any updatepack. BTW, the addon won't be unattended (unless you change the .bat file).

Well, a quick hack, but this should get the job done when integrating using the RVMIntegrator. I don't think nLite supports the entries.ini commands. I haven't actually tried this yet. Create a folder "XPtsp", drop your patcher into it. Combine the folder and this .ini into an addon (7z, cab, zip, rar) [general] builddate = 07/03/2008 description = XP Theme Source Patch Automator - launches it during integrations. language = Multi title = XP Theme Source Patch Automator version = 1.0 Windows = XP website = http://www.wincert.net/forum/index.php?showtopic=3842 [FileMove] XPtsp\XPtsp.v*.exe,..\XPtsp.v*.exe [RunFile] XPtsp.v*.exe,HIDE [FileDelete] ..\XPtsp.v*.exe [DirDelete] XPtsp

Very nice Kel! Any chance of getting a right-click "send-to" CAB extension? (if there is one :/ )

I for one prefer my XP install to be labelled "XP" instead of "Vista". I just want it to LOOK like Vista.

Dead link

Ooh, is this to install into Vista only or both XP/Vista?

Thanks Kel. This is awesome.

WinCert...my precioussssssss.

Yup! This is absolutely the best transformation project out there!

Any idea on how to get cabtool -> sendto working under Vista? Not an addon question, I know, but one that's been bugging me.

@amnesia, Anyway of getting a collection of your system property mods in one place (with Rick's fixed netid.dll) that work on both Home and Pro? I can get the "Remote" tab working only on Pro, not Home. and the "System Restore" tab doesn't work at all. The "Auto update" tab is hit-or-miss too. Thanks for your awesome contributions!