bphlpt, usually people give up after the first steps. That's why I always say "give me feedback after these (x) steps". Most of the time, it turns out they want things done just a little bit differently, or don't want to use a particular tool or whatever.
It has been like that on the MDL forum a few times as well (with XP updatepack, but also WinPESE bootable USB, etc.), people start enthusiastically, but soon give up. No problem at all, in cases like that I'm just glad I didn't make a full-blown tutorial...
Every time I explain stuff for others, I understand it a little better myself, so that's nice, too...

@Atari800xl, I wasn't trying to rush you. I think everyone likes feedback on their advice, I know I do. But if/when you and skrell make it all the way through the process, that was the point at which I was suggesting that it would be nice to put everything together in a single post as a summary. I hope it gets to that point.

@skrell, sorry, but I can't help you directly since I don't have an XP build to give you feedback about. I have a feeling that if you redo the build in stages, testing after each one, that you will quickly either find your mistake, or will narrow down exactly what is going wrong so that others can give you the help you need. If you find your mistake, pleas let us know so that if others have similar symptoms we can suggest a likely solution.

It's probably an idiom that didn't quite translate to English, or at least not to something recognizable to those not already familiar with the phrase. Similarly, I doubt that "Kiss my grits" or "Well butter my buns and call me a biscuit" would translate well to those not familiar with those Southern US expressions.

But I think he meant that even though OnePiece seems to be gone, you can still make a valuable impact to the community with his tool.

Probably the best idea would be to wait until next week's new POSReady updates, hopefully 5eraph will tell us which updates are superseded, so we can make a litte HowTo on making a personal (and again: localized!) POS Addon with DXUPAC. I guess the easiest way is to start with OnePiece's box folder (updated until April), after that add the May, June and July updates (which you'll have to download yourself, I get them from https://catalog.update.microsoft.com/v7/site/Home.aspx), and remove the superseded ones.
Then after another month, rinse and repeat (the soup bowl?).

I'll try to make that little HowTo today or tomorrow. My idea was to start with OnePiece's april files, than add the may/june/july files (you'll have to download them one by one) and remove the superseded ones. Unless anybody had a better idea?

EDIT (on that KB3074886-IE8): I googled for it, found it on microsoft.com, selected language, 2 files had to be downloaded. Is that the correct way to get it? I have to admit the catalog.update.microsoft.com would be a lot easier, as it allows to get a lot more in one go... Still wonder how you found this one.

Thanks a lot!!
I'm taking this one step at a time now, first thing I tested was making a "DXUPAC" addon with just all the new updates added to last month's POS files (except this kb3074886 one), then removing all the superseded updates from the "source" folder (per your instructions) and creating the addon again. This seems to produce identical addon files, so that's perfect!

I will first make a new XP iso now with all the new stuff (updatepack, addon, etc), test the new XP, after that make the HowTo on getting all the files together in one place.

2. KB3067903_Security Update_WMP has 3 files.
I expanded them and based on the inf files (I'm not experienced) it appears that there is a separate file cewmdm.dll for WMP10, WMP10L and WMP11.
windowsmedia-KB3067903-x86-enu_sha hash 65c7e... =WMP10
windowsmedia-KB3067903-x86-enu_sha hash 17cad... =WMP10L
windowsmedia-KB3067903-x86-enu_sha hash 51015... =WMP11

Hi Skrell, thanks for your reply!! I was just checking this thread for replies, I was worried nobody cared anymore, so I was close to forgetting about this altogether. Also, after Molecule's original post (before the edit), I started to think my list of updates was wrong anyway.

But now I feel a bit better, looks like you're still interested.

So, have you followd my directions of July 15, downloaded the OnePiece folder, added the new ones, then removed the superseded ones? Also, have you downloaded the latest (=final?) DXUPAC from the OnePiece folder?
Make a folder c:\makepac, put dxupac there, make a subfolder c:\makepac\updates, copy all the updates there. Then report back, we'll make the Addon next!!

(2) Make a folder c:\makepac, put dxupac there (DXUPAC 1.2.3.2 20150415), make a subfolder c:\makepac\updates, copy all the updates there.

You would normally use DXUPAC to make an UpdatePack, which would be pretty straightforward. As we're making an Addon instead of an UpdatePack though, there are some extra steps needed.

(3) Start dxupac.exe from c:\makepac. Under "Choose language", select your language. Under "Browse to the location that contains the Hotfix/ Update files", click the "...." button and browse to c:\makepac\updates. Press the "Start" button and leave your PC alone until it finishes.

(6) Change "UpdatePack" to "Addon" in this folder name:
C:\makepac\updates\OnePiece_WinXP_Post-SP3_UpdatePack_XXX
to
C:\makepac\updates\OnePiece_WinXP_Post-SP3_Addon_XXX
If you don't change the foldername, the 7z file we're creating later won't have the word "Addon" in it, and integration will fail.

(7) Edit this file:
C:\makepac\updates\OnePiece_WinXP_Post-SP3_Addon_XXX\entries.ini
Only the [general] section of this file is needed, so remove all lines after that section, starting with line 27 (";This section contains entries that need to go" etc.) This is also a very important step.

(9) Again very important: rename this file from "entries.ini" to "entries_EOL.ini". If you forget this step, your new XP iso will fail completely (believe me, I tried).

(10) Start 7zip. Browse to
c:\makepac\updates\OnePiece_WinXP_Post-SP3_Addon_XXX
You have to be "inside" the folder, so you should see the subfolders "ASMS", "LANG" etc. now.
Press control+a to select all files and press the big green plus. If all went well, the correct name for the 7z file is already there, click "OK" to create the 7z file.

(11) The file has been created in this folder:
C:\makepac\updates\OnePiece_WinXP_Post-SP3_Addon_XXX
move it from there and put it somewhere safe. It's ready for integrating into your XPSP3 source, using RyanVM integrator, together with the OnePiece Final XP Updatepack.

====================

Skrell, please test these steps and let me know if there are still any errors or unclear parts. It's just a first draft, using my own personal notes.

@atari
KB2993651 (gdi32_5.1.2600.6625, win32k.sys_5.1.2600.6625)
may have been replaced by KB3069392 (gdi32.dll_5.1.2600.6852) and KB3070102 (win32k.sys_5.1.2600.6856) SP3QFE contains only those two files, but there might be other changes as well?

these next KBs have .dlls wtih the highest version numbers I could get out of the files I downloaded from the MS content site for XP embedded
KB3050945 (jscript.dll_5.7.6002.23659)
KB3067903 (cewmdm.dll_11.0.5721.5295, for WMP 11)
KB3068368 (vbscript.dll_5.7.6002.23712) replaces KB3050945
KB3079904 (atmfd.dll_5.1.2.243) replaces KB3077657

@seraph
I see you left out KB3049874 (tzchange.dll_5.1.2600.6777, tzchange.exe_5.1.2600.6777).
It replaces KB3013410, which replaces KB2998527 which replaces KB2981580 which replaces ... etc.
Some sites report tzchange (time zone change) has a memory leak or something? -- would you recommened that that AIO users just leave it out as well?

When I run DXUPAC with the .NET files, it doesn’t crash. But I have no idea if the result will integrate .NET files, or if the default Update Pack can be converted to an Addon by the modifications that Atari summarized above. (Thanks Atari!)

Since the AIO update pack has .NET 1.1, 2.0sp2, 3.0, 3.5 and 4, it would be nice if someone knew how to integrate the updates for them. Has anyone tried integrating .NET updates from POSReady as Addons using DXUPAC? If I try it, anyone have idea on how to test if POSReady .NET updates install ok?

KB2979575 is shown on MS14-057 for NDP4 on Server03sp2 systems, which as regards updates I gather is similar to XPsp3. But it is not included on the XP Embedded list. It is rated critical, remote code execution.

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

Molecule: I had hoped things might be a bit simpler to maintain, but I'm afraid it looks like it's becoming quite complicated.
Could you please answer me this first, please:
- How did you find those 4 new updates (the three "added" and one "replaced"), I'm just asking if this was a "reproducable" method you used? I mean, the updates I mentioned were easily found on the MS catalog site, so where did you find them (sorry, hope you understand what I mean).

SORRY! Please ignore my last post.
Molecule, THANKS!! For those 4 corrected updates. We should keep your new list as the current POS Updates list!
- KB3068368: This one's NOT superseded, this was an error on my part
- KB3079904: Not on my list because it was newer than July 14 (in fact, July 17)
- KB3067903: I removed it because it was for Windows Media, but for completeness we should keep it
- KB3050945: Another error on my part, sorry!

Thanks again for the updated list, hope you'll stay around to keep it updated.

molecule wrote:@seraph
I see you left out KB3049874 (tzchange.dll_5.1.2600.6777, tzchange.exe_5.1.2600.6777).
It replaces KB3013410, which replaces KB2998527 which replaces KB2981580 which replaces ... etc.
Some sites report tzchange (time zone change) has a memory leak or something? -- would you recommened that that AIO users just leave it out as well?

I used your link to the MS catalog site -- it's new to me and seems pretty cool. Entered XP Embedded in search box, and clicked "Add All" page after page. I must have caught MS in a good mood, because it downloaded everythng.

Then I cleaned up the file and folder names and then grouped them as Windows system updates, or WMP11, IE8, .NET. When I opened the files I saw that all kinds of jumble that made no sense, so I fed them into DXUPAC. I then 7zip'd the translated files, together with the DL exe files.

DXUPAC rehashes the file names back into usable file names, so you can see what the update is doing with the system. I'm using Ghisler's Total Commander so it gives me version page for any exe file. I went through each file and made a spreadsheet database (pretty messy ...) of KB #s, with the exe file name, the exe date, and the internal .dlls (there can be many, like IE, but most of the time there are just a few). If there are several related dlls, I only picked on the main one.

I then rotated the database, so I could sort by (a) .dll name, (2) exe date and last KB num. Where there are several dlls with same name I check the two highest dates for version numbers.

I then cross referenced your list with seraph's list from his QFE POSReady work (http://www.ryanvm.net/forum/viewtopic.php?t=10479). Of course he's using IE6, WPM8?, no .NET, and we need IE8, WMP11 (even if we don't use it) and .NET. I just hacked into the gaps to check the version numbers. There's a way to configure the TC panels to text dump the version numbers on all files, but I just did it by hand.

It's nice to have someone to work with. I don't have virtual machine, so when I do a thumbdrive ISO, it takes ... forever ... Arghhh. I'll try two ISOs one without .NET and one with.

OnePiece and Nonno did some amazing magic with that DXUPAC and I think they may have got the .NET stuff working ...

more later ... peace!

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

molecule, same here: great to work on this.
I think our last few posts crossed, but I'm sure we'll have it figured out by tomorrow... Just read my last post before your last, please (kb3050945, kb3068368). Please tell me what you think (you checked versions etc., I have not, only 5eraph's notes).

@seraph -- I had googled on "tzchange" -- since the 2 files in KB3049874 are tzchange.dll and tzchange.exe_5.1.2600.6777. It looks like 3048974 (tzchange.exe,.dll) is quite different from file 3062741 (which has tzres.dll)

I googled "tzchange" and there were several sites saying problems, some memory leak. Google is so trashy now, they might be snarfy trouble makers trying to trick someone into "fixing" something that ain't broken.

When I use the search box in the MS catalog database, nothing comes up on KB3062741. The download from the KB db is a requested "hotfix." As I understand it they aren't as widely tested as the regular updates.

It's also not on the XP Embedded database. That's the only access I know of i.e. the one Atari gave above.

If you're not using his search method, where do you get your source files? Are you using bulletins MS15-xxx to build your list? I don't see XP Embedded on any of them. Are using Sever 2003 SP 2 to make your selections, when XP and XP Embedded doesn't appear?

===EDIT===

I see at the bottom of the page "all versions XP, which includes XP Embedded" so I am in error above. However, for XP, the files and versions are the same in https://support.microsoft.com/en-us/kb/3062741 as they are for KB3049874 -- v_5.1.2600.6777

Last edited by molecule on Fri Jul 24, 2015 5:07 pm, edited 1 time in total.

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

molecule wrote:@seraph -- I had googled on "tzchange" -- since the 2 files in KB3049874 are tzchange.dll and tzchange.exe_5.1.2600.6777. It looks like 3048974 (tzchange.exe,.dll) is quite different from file 3062741 (which has tzres.dll)

molecule wrote:When I use the search box in the MS catalog database, nothing comes up on KB3062741. The download from the KB db is a requested "hotfix." As I understand it they aren't as widely tested as the regular updates.

You need to use the "Hotfix Download Available" link in the Knowledge Base article to get the update. I have never put much stock in their "testing" explanation. Microsoft must test an update to some degree before release. But I believe the only thorough testing is done by the end users. When Microsoft gets complaints from enough of their users, they test again to confirm a problem. Fewer XP users means less testing by XP users. That's just how it is.

molecule wrote:It's also not on the XP Embedded database. That's the only access I know of i.e. the one Atari gave above.

I'm not familiar with the "XP Embedded database." Can you provide a link?

molecule wrote:I googled "tzchange" and there were several sites saying problems, some memory leak. Google is so trashy now, they might be snarfy trouble makers trying to trick someone into "fixing" something that ain't broken.

I googled tzchange + "memory leak" and got nada. The first page of results from only tzchange gives me no meaningful results.

molecule wrote:If you're not using [Atari800xl's] search method, where do you get your source files? Are you using bulletins MS15-xxx to build your list? I don't see XP Embedded on any of them. Are using Sever 2003 SP 2 to make your selections, when XP and XP Embedded doesn't appear?

Afterward, I'd check for updates using snapshots of Win2003x64 and POSReady virtual machines updated the previous month, and compare what the Microsoft Update website reports in those VMs against what I'd just downloaded. Then I'd download anything missing there from the Microsoft Update Catalog as well.

Sometimes new updates wouldn't appear in the Catalog right away. In those cases, I'd check the Microsoft Download Center for the KB numbers. And if they were unavailable there then I'd capture downloads from the Microsoft Update website on my VMs and use those files for my update pack and addons instead.

Now that Win2003 isn't widely supported, I'll have to make some changes to my routine.

@seraph -- you're right they're not the same version. same file size but not version.
KB3062741 tzchange.dll_5.1.2600.6852 tzchange.exe_5.1.2600.6852
KB3049874 tzchange.dll_5.1.2600.6777. tzchange.exe_5.1.2600.6777
so we should probably amend.

-- edit -- It's interesting that, down at the bottom, the MS bulletin for your KB3062741 gives versions as the old 5.1.2600.6777.

Google gives different answers to different "customers." Maybe google has a different profile of me?? I now suspect the site might be an advertising operation. "your computer's broken, press this button to fix it" kind of thing.

What I meant by the MS XP Embedded database is the list of all XP POSReady files that MS generates when you enter https://catalog.update.microsoft.com/v7/site/Home.aspx and then search on "XP Embedded" The download setup 64 local folders, where one IE folder had 2 files, one WMP folder had 3, all NDP had 2, and the rest had just 1 file. But there is no heirachy like the MSxx-xxx gives, this KB supercedes that etc., so I had to open them. I'm so happy with my XP AIO that I've lost touch with the update hairball.

You're right, I think the catalog.update database is about a day or two or more behind. But it is convenient.

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

molecule wrote:2. KB3067903_Security Update_WMP has 3 files.
I expanded them and based on the inf files (I'm not experienced) it appears that there is a separate file cewmdm.dll for WMP10, WMP10L and WMP11.
windowsmedia-KB3067903-x86-enu_sha hash 65c7e... =WMP10
windowsmedia-KB3067903-x86-enu_sha hash 17cad... =WMP10L
windowsmedia-KB3067903-x86-enu_sha hash 51015... =WMP11

I wanted to include kb3067903 in my list as well, to make sure your list and mine are the same, even though I don't use WMP11.
First I wanted to add all 3 versions, but that's confusing. 5eraph only mentions the WMP11 version, so maybe we should focus only on that. You used part of the sha hash to identify it, but of course that changes per language!
So the best way for me was to expand them, check which one was for WMP11 (it was the largest of the three) and keep only that version.
So that's the one I'll keep as "kb3067903" in the list. For comparison, using only "kbxxxxxxx" seems the best solution to me.

Atari800xl wrote:Hi Skrell, thanks for your reply!! I was just checking this thread for replies, I was worried nobody cared anymore, so I was close to forgetting about this altogether. Also, after Molecule's original post (before the edit), I started to think my list of updates was wrong anyway.

But now I feel a bit better, looks like you're still interested.

So, have you followd my directions of July 15, downloaded the OnePiece folder, added the new ones, then removed the superseded ones? Also, have you downloaded the latest (=final?) DXUPAC from the OnePiece folder?
Make a folder c:\makepac, put dxupac there, make a subfolder c:\makepac\updates, copy all the updates there. Then report back, we'll make the Addon next!!

Which folder of Onepeice's has the POS addons? I'd like to start by just downloading whatever he has compiled rather than attempt to DL a single KB update at a time.

I can't check right now how many of the original OnePiece files are still valid (not superseded). Can you tell us?
Maybe it's easier to start with the catalog site, and search for the approx. 30 files by hand, might not even be too hard if you search for "XP embedded" and sort by date (new to old). I will try this later, but please share what you think is the best way...

1. Why are there THREE versions of kb3033890
2. Atari800xl, why don't you just make a box account and keep an uptodate folder of POS updates? You are already doing the work and could share your efforts?3. Also are you including updates for ie8?
4. Also do i need all 3 of the 3033890 updates? I figured after using OnePiece's latest addon i probalby have WMP11 so i dont need updates for WMP10/9 right?

skrell wrote:2. Atari800xl, why don't you just make a box account and keep an uptodate folder of POS updates? You are already doing the work and could share your efforts?

There are many reasons:
- The nice thing about the OnePiece pack and DXUPAC is that you can build it in your OWN LANGUAGE!! This was discussed before. I'm not building the EN-US version.
- Knowing HOW it's done is important. I like to discuss stuff here, so others can check if I'm doing it right.
- Take the kb3033890 example. Personally, I'm not including it at all, but it's there, so we have to deal with it, others might need it.
- Teaching you how to fish is better than giving you a fish, etc. (this one's getting old, I know).
- I don't want to "have to do it" every month, when there's an "audience" of just a few guys left. I'd rather have the interesting discussions, etc.
- I'm not sure uploading the files is even allowed.
- Etc.

to Seraph, for building a benchmark to work from, just my opinion but one could either choose to stay with the regular patch KB3409874 (universally available, my preference) or use the email-specific hotfix patch KB3062741.

I've compiled the above with DXUPAC (see Atari's detailed instructions above) and RVMI'd it with AIO Update v106. I tested the result just straight, no mods, not nLite, no remove cabs, etc. and it installs the OS. Beyond that, I don't know much.

Then, I used DXUPAC to build an Addon pack for the .NET patches, again following the standard method described by Atari above. I RVMI'd a fresh XPsp3 source, plus the AIO v106 Update, plus then two Addons, one for the regular patches, one for the dotNET patches. The system does not install.

Installing from WinSetupFromUSB v1.5 to clean HDD, the install collapses soon after the 1st reboot, when GUI appears. After DOS copy files and reboot, with the grub4dos selecting second half, the dark XP screen appears, with sliding blue balls ... that finishes, and the screen changes to a light blue background with hourglass (in preparation to announce "windows is an exciting experience" or something, so ... light blue backgrouind with hourglass for a few seconds, then, the machine reboots again ... recycling back into grub4dos phase2 in an endless loop.

For building the .NET Addon, I tried two file sets, one with just the 7 type-2 dotNET updates, one with the above 7 plus the msipatchregfix.exe which is included 7x, once in each of the KBs. The result is the same ... installation failure.

Last edited by molecule on Mon Jul 27, 2015 11:56 am, edited 2 times in total.

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

I've looked for an explanation showing how One Piece and Nonno Fabio built their .NET Addon packs. I can't find one.

Does anyone know what method they used to do that? There are apparently some catch points to watch for when building an Addon with the .NET patches.

If someone contacts OnePiece, or Nonno it would be nice if they could post a copy of the archive build folder that they used for the AIO v106. In other words, we could use that to build an AIO v106_less_Flash ... resulting in an AIO with just MS patches. Flash is large and keeps changing.

If we can't learn how to generate an Addon for POSReady patches for .NET 2 and 4, then is there a way to run them in manually, in XPsp3? I guess, maybe try the registry changes that are covered elsewhere. Does anyone know if the POSReady patches "feel at home" and work in that case?

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

About your entry:
"KB3055973 schannel, English only? see MSFN forums":

I've posted a question about it there as well, but I'm afraid the google-translated answer from "heinoganda" makes no sense to me. I explained to him that DXUPAC added the files to my Dutch POS addon, from that I concluded that it's not English only, but that conclusion may be wrong.
I still have no clue what these files are actually for, so not sure what to do with them anyway or how to test whether they're English only.

Can someone compare the OPMWXPUP.inf file from the final update pack and the one created using the posready addon? Are there any differences? There are the correct registry references of the posredy kb, or not?
And no, I'm already some sort of fisherman, I just want you to check if you understand that dxupac can really make a full pack or just extract some file.
About .NET addon: no way that dxupac can update the addon, since it was made converting a msi-based installer to a inf-based addon.

Does anyone have a recommended update slipstream for me? I'm not yet made new XP CDs for a while. But I'm afraid to just use any update pack, they don't seem mature enough, and I definitely don't want to hack the machine into POSReady mode (I don't want it to automatically download POSReady Updates).

You will probably have to build your own (-- you want the responsibility?)

Since I may be in the same process here's my 2¢ input -- plus writing helps me think it through.

1. AIOv106 seems pretty clean. I use RyanVMI for it. It has the .NETs, which sadly, are pretty much needed. .NET maintenance is a real PIA. It has IE8, and WMP11 (I never use either, but still want the system files updated for security ... just because I'm not using them doesn't mean someone else isn't ...)

IMHO, it's sad that OnePiece never made an Addon to remove the always out of date Adobe Flash and always out of date MRT Malicious Software Removal Tool. They are huge files.

2. regarding the .NETs

KB2833941 (MS13-052, 2013-0709, i.e. pre-EOL) (link) for .NET1.1sp1 isn't shown on the AIO changelog. Kind of hard to imagine it it got missed? It can be run in by hand after buildnig.

regarding the .NETs

I can't find a description of the process for how to build a .NET Addon ... I gather MS made it so hard, it ends up feeling like a kept secret or something.

XDOT.TK ( link ) has a batch which shows how simple it can be to create an Addon cab for patches for windows mediaplayer. WMP is an application and its patches might (??!!) similar to .net patches, since .NETs are also considered applications.

My suspicions is that there's a DOS batch out there somewhere that will take a .NET msi installer and reduce it to a CAB and inf ... or do most of it with some manual tweaking of an inf or two ... so on that point your feelings are heard by many of us ... blame falls squarely on M$, not on forum members

3. the RemoveCAB called BrowserChoice removes files from I386 that are programmed to be copied by setup. In a manual install, when setup can't find them, setup will require multiple user interactions.

4. DXUPAC sounds complicated. It's not. It's explained by Atari above, and elsewhere on youtube. It's no harder than RyanVMI. After the 3rd use, you won't understand how the 1st use could have taken so long -- which feels like hours on hours for me. Now building a DXUPAC Addon takes 3 to 4 minutes. Gathering files ... another matter.

5. When a clean XPsp3 source is integrated by RyanVMI with AIOv106 Update and a DXUPAC Addon of the above list of PostEOL POSReady system patches, the ISO appears to build a stable system (I'm no expert)

6. there are 4 postEOL-POSReady patches for .NET 1.1sp1 that have to be tweaked to install in an XP system that is straight XP (that is not masquarading as XP Embedded) (Not that M$ hasn't already embedded ALL OF US).

I tried to integrate them into a source using the /integrate:path switch. The installer reports a successful install but my I386 source doesn't change and no new folders are added.

I haven't tested whether the /nobackup switch works. Otherwise on a manual install no switches they create useless piles of dead MS stuff on the HDD once again.

8. I use XP for my legacy software (engineering) ... so unlearning XP and learning Windows 7 would involve 1000s of hours of defensive training, learning and trial and failing at closing anew 1000-set of MS holes. And with 7 then I have to install an XP layer inside 7 ... I may as well use WINE at that point and have a stable system.

For myself, I have to say I too am tired of being force-embedded into a pool of MS bubblegum.

Last edited by molecule on Fri Jul 31, 2015 12:19 pm, edited 3 times in total.

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

Atari800xl wrote:I had some time to spare, so let's get cracking. I really hope we can keep the list of POS updates somewhat current over the next few months, so...

So i finally got around to trying your procedure here and for the most part it worked well. I did every step you specified but integrated the addon using nlite. The ONLY thing that doesn't seem to work is that these POS updates don't seem to be installed...could the names possibly be too long? I double checked the 7z file i made and they ARE listed in the SVPACK folder. Thoughts?

Did you DXUPAC them? Once you've checked the dl, you can drop the SHA1 tags on long file file names. I'm pretty sure that they won't integrate unless they've been converted from XP Embedded to plain XP. That 's what DXUPAC does. It's probably MS Setup that's blocking them, not the fault of nLite.

After building, I checked the installation for presence new files and versions. I checked 3 or 4 and they were all installed. IMHO, RVMI makes a nicer OS. Somehow , for me, they come out feelign stronger. Completely intangible. Probably because I don't understand enough about nLite.

After installing, I ran in the .NET updates 2,3,4 for POSReady and Server2003 by batch. The updates for .NET 2,3,4 are for XP Embedded and Server 2003 but they go straight in. See batch below for the ones that work with the /nobackup switch. The updates for .NET 1.1 plus a major .NET 1.1sp1 patch that One Piece missed (or at least it's not on his change log) have to be hacked. The inf files need some simple changes and the exe needs a small Hx0 hack.

For me it's faster to just tweak in the setup I want, rather than try to figure out the deep ins and outs of nLite -- nLite can make a smaller source, but the old CD boundary doesn't apply anymore. To build the USB, I use Rufus. The WinSetupFromUSB project over at MSFN is also nice, but for me I don't need the options created by Grub4Dos. If you're not installing AHCI drivers (the default, incorrectly called "sata drivers" -- a popular misnomer -- also for most desktop users sata disks in native "emulation mode" will be faster than with overhead of ahci drivers -- defrag otherwise MS will beat your HDDs to death -- MS profits by planned obsolesence ...), but with WinSetupFromUSB you will have about 2 seconds to read and understand the Grub4Dos menu, and quickly select option 3.

After integrating I ran the following Remove Cabs from OnePiece -- the cab to remove browser choice will cause installer to issue message boxes on files that it cannot find. Then I ran setup.

batch with switches for .NETs and VB VC runtimes will follow as an edit when I find it -- the /integrate switch didn't work, the /nobackup did on some of them I had to test them 1 by 1 -- see MSFN for POSReady 2009 ported to XP

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3

Please don't complicate things. If you have created the POS Addon successfully, integrate it with RyanVMi. Use XPSP3 as source, use RyanVMi to integrate Final XP pack and self-made POS Addon. Nothing needs to be converted from POS to XP, that's not needed in this step.

After RyanVMi, use nLite for other stuff if you want.

Molecule, I briefly saw your NET stuff on another forum. Is this something you could explain here as well? I know nothing about that stuff, so if you could explain it here in your very clear and understandable manner, that would be great!!

skrell -- I agree with Atari800xl -- Try RyanVMI to integrate update packs and addons. For some reason, nLite has some layers in it that are simply too deep for me. I seem to end up with tricky systems that just don't feel smooth. I run in OnePiece's AIOv106 Update, then build a test system on a $10 refurbished hdd. (I don't have time to install and learn a virtual machine.) It takes about 15 minutes to build an integration, and about an hour afer that to verify it -- 30 mins to integrate and bulid an iso, then copy to bootable USB. (I use nLite only to build the unattended WINNT.SIF, and to build the ISO, and Rufus to move the ISO to bootable USB). Then Setup takes 30 mins to install a test system. I run in drivers by hand (since every driver extraction utility I've tried seems to give a different answer.) Once an ISO has been validated, it becomes a platform for addons. I give validated layers names, like XP_build_01, 02 etc. Once I know that an ISO builds a working system, the ISO goes in lockdown, and it becomes a known stable layer to work from. When you try to integrate everything all at once, if a problem comes up, you can go dizzy trying to figure out where the problem is.

I stopped using the OnePiece Remove Addon CABs. As Nonno Fabio pointed out, the same result can be removed by Add/Remove Programs (and system components) in control panel.

The slightly fat ISO is nice as a lockdown format because Winrar, 7zip and Ghisler's Total Commander can open them and copy files out of them, but I don't want software that easily alters an ISO. Once an ISO is proved to build a stable system for your computer, let Ryan VMI build your next layer, for addons like DXUPAC of POSReady. Once you validate a stable layer, then try nLite -- but almost almost all the tweaks etc that nLite does can be easily done in a few minutes after a validated system is installed.

@atari800xl -- ok. I'll post a summary here (a few days), because the thread on XP and POSReady is kind of long. BUT!, I don't want stick a fork in the energy of that thread. It has some very helpful members whose knowlege far surpasses mine. So as hairy as that thread is, I don't want to start a competing thread. I'd like to keep the focus over there. All of its membes are watching POSReady, Server 2003 and the .NETs patches for XP. Seraph's thread on this site is also excellent meeting point.

I'd love to see a modular breakout of OnePiece's AIO. I don't have the system or huge compilation of KBs that would be needed to build one. Remove the MS Malicious Software tool and Adobe Flash for IE. They are huge, change way too frequently, and, like the JREs, they are easily added after an OS is up and running. That would leave 4 modular components to watch post-EOL -- System patches, .NETs, IE8, and WMP11. Being almost 100% trust-disabled, I liked OnePiece and Nonno Fabio, because they included IE8 and WMP11, and the .NETs (which is even needed by nLite). But on a personal level, OnePiece and Nonno Fabio were never dismissive. Everything was straight forward and simple, and nothing was "too complicated" or slinky or secretive.

IMHO, XP is going to be around for a good while yet, especially now that MS is trying to automatically install a "free 10" (haha) overtop of a stable and sovereign 7s, and eventually maybe even XPs. MS has some strange and mysterious motives, which IMHO, cannot be fully understood until we look at its origins, and the outer geometry of its culture of secrecy. From its inception MS has been a spinoff from IBM, which is embedded with the CIA. To cut to the chase MS is actually a Wall St subsidiary of "the Pentagon." And, that military (and now so-called "industrial") institution has been, from its inception, in the 1830s, when opium was discovered in the Sierra Madre of Mexico, a ressurrection of the old British East India Company. By deception, the BEIC has fought for and won a global monopoly on trafficking in opium and piracy in gold. Now with vaccines it's messing with children, and food, and information. It's actually a Bolshevik fifth column that evolved as reaction to the independences that the Americans and Indians won from the BEIC in the late 1700s. A global bunch of total creeps. On MS download pages for KBs, MS gives me a popup which tries to get me prepared for a future fee upgrade, from my fast stable and sleek, and sovereign XP to a "free 10" (with a 140 page licence agreement). A small group of Russians is working on open source version of XP (ReactOS). It's still in alpha, but as open source it has the support of the Russians and the Russian government.

all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3