Thank you ! Would you mind please posting the addon so that i can try it directly? How exactly did you modify your entries.ini file?molecule wrote:@skrell -- I dxupac'd your list, modded....
Onepiece XP Post-SP3 AIO Update Pack FINAL
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
create a folder (say DXUPAC_temp_XPsp3_PostEOS_Addon)
put your POSReady update patches in it (all *.exe)
startup dxupac
choose language, in my case ENU will be added to the file names
browse dxupac to the input folder that contains the source patches (*.exe)
leave the dxupac output folder location empty, so that output folder = input folder
run dxupac and wait until done (start button will be greyed out during waiting)
when its done, dxupac creates one file and two folders
the file, OnePiece_WinXP_Post-SP3_UpdatePack_ENU.7z, is in UpdatePack format and should be thrown out
the folder Archive_Files contains temporary files and folders and should be thrown out
the folder OnePiece_WinXP_Post-SP3_UpdatePack_ENU is called the working folder
with a small modification it contains everything needed to build an Addon
remove the word UpdatePack from the working folder name and substitute the word Addon
I rename my working folder OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
when you rename it, think ahead ... this will become the name of your future 7-zip Addon pack
I then match the future Addon name to the description= tag and title= tag in entries.ini
inside the working folder, I rename the file entries.ini to entries_Post-EOS.ini
OnePiece uses entries_EOL.ini
open the file entries_Post-EOS.ini in a text editor
it has a header section with comments, then a [general] section, followed by several more sections
the sections after [general] are applicable to UpdatePacks only -- they don't apply to Addons
delete all lines and sections after the [general] section but save [general] section
inside the [general] section, I edit the description= and title= tags to match the file name of the future Addon
in my case, description=OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
and, title=OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
between the header section and the [general] section, I add a build history section (see below)
using ;-semicolon for comment, I list filenames for the POSReady patches that were used to compile the Addon
save the modified entries_Post-EOS.ini file (the original entries.ini is gone)
Start 7-zip, and navigate to inside the working folder
select all files and folders (press ctrl+A)
drag the files and folders to the green plus button on the 7-zip toolbar
Select a compression (OnePiece used Ultimate) and wait
7-zip creates the Addon archive inside the working folder, named by the folder name
In my case, it's named OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU.7z
Move the 7zip Addon to your Addons folder for integration with OnePiece AIOv106 UpdatePack
Once the 7z Addon archive is saved, delete the working folder
The source folder (say, DXUPACtemp_XPsp3_PostEOS_Addon) now contains only its original patch files
The source starts with a Microsoft OEM Hologram CD for XP Professional SP3.
The following four folders are removed from the root folder
The following three files are removed from the root folder
The following three folders within the \I386 folder are removed
If the original OEM system CD is available, copy the four OEMBIOS files to the \I386 folder
Thus, for me, integration begins with a source that contains
Using an XP machine running AIO, start RyanVM Integrator, integrate the hologram source, with OnePiece AIOv106 UpdatePack and the Addon, in one run. I agree with Atari -- I don't use AV or firewall, or anything ... I just use a good backup program.
Build a bootable iso, and copy it into a thumbdrive. I use Rufus. Partition a respectable amount of space, say 10G, at the front end of a refurbished HDD for the OS, but leave room (as unformatted space) behind it, so that the boot partition boundary can be expanded to 20G for software, after the OS and drivers have been installed and defragged, and a backup made. This keeps the numerous $Pentagon shares, which NTFS installs at fixed addresses (bypassing file manager) and which cannot be moved by the NTFS defragging ap. Unplug your LAN connection, boot into the USB, install the OS and drivers, then cleanup and defrag (native MS defragger), then switch back to your builder-XP system and run a backup. Then expand partition, add software and make backup, then reconnect LAN ... that's what I do anyway
Whether or not the above procedure is correct, it seems to build a working system for me, so maybe it will work for you ...
====
entries_Post-EOS.ini
take note that -- title=, description=, and 7zip Addon filename match
put your POSReady update patches in it (all *.exe)
startup dxupac
choose language, in my case ENU will be added to the file names
browse dxupac to the input folder that contains the source patches (*.exe)
leave the dxupac output folder location empty, so that output folder = input folder
run dxupac and wait until done (start button will be greyed out during waiting)
when its done, dxupac creates one file and two folders
the file, OnePiece_WinXP_Post-SP3_UpdatePack_ENU.7z, is in UpdatePack format and should be thrown out
the folder Archive_Files contains temporary files and folders and should be thrown out
the folder OnePiece_WinXP_Post-SP3_UpdatePack_ENU is called the working folder
with a small modification it contains everything needed to build an Addon
remove the word UpdatePack from the working folder name and substitute the word Addon
I rename my working folder OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
when you rename it, think ahead ... this will become the name of your future 7-zip Addon pack
I then match the future Addon name to the description= tag and title= tag in entries.ini
inside the working folder, I rename the file entries.ini to entries_Post-EOS.ini
OnePiece uses entries_EOL.ini
open the file entries_Post-EOS.ini in a text editor
it has a header section with comments, then a [general] section, followed by several more sections
the sections after [general] are applicable to UpdatePacks only -- they don't apply to Addons
delete all lines and sections after the [general] section but save [general] section
inside the [general] section, I edit the description= and title= tags to match the file name of the future Addon
in my case, description=OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
and, title=OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
between the header section and the [general] section, I add a build history section (see below)
using ;-semicolon for comment, I list filenames for the POSReady patches that were used to compile the Addon
save the modified entries_Post-EOS.ini file (the original entries.ini is gone)
Start 7-zip, and navigate to inside the working folder
select all files and folders (press ctrl+A)
drag the files and folders to the green plus button on the 7-zip toolbar
Select a compression (OnePiece used Ultimate) and wait
7-zip creates the Addon archive inside the working folder, named by the folder name
In my case, it's named OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU.7z
Move the 7zip Addon to your Addons folder for integration with OnePiece AIOv106 UpdatePack
Once the 7z Addon archive is saved, delete the working folder
The source folder (say, DXUPACtemp_XPsp3_PostEOS_Addon) now contains only its original patch files
The source starts with a Microsoft OEM Hologram CD for XP Professional SP3.
The following four folders are removed from the root folder
Code: Select all
\DOCS 6,895 bytes
\DOTNETFX 41,094,408 bytes (v1.1.4322.573, 04/14/2008, included in OnePiece AIOv106)
\SUPPORT 13,474,255 bytes
\VALUEADD 9,288,325 bytesCode: Select all
AUTORUN.INF 110 bytes
README.HTM 34,652 bytes
SETUPXP.HTM 85,792 bytesCode: Select all
\I386
\LANG 103,868,589 bytes
(I use english so I don't need these files)
\WIN9XMIG 34,271,822 bytes
\WIN9XUPG 4,167,792 bytesCode: Select all
\I386
OEMBIOS.BI_
OEMBIOS.CA_
OEMBIOS.DA_
OEMBIOS.SI_Code: Select all
\I386 404,632,973 bytes (total)
\ASMS 7,805,081 bytes
\COMPDATA 764,725 bytes
\DRW 246,432 bytes
\SYSTEM32 1,176,064 bytes
\WINNTUPG 1,099,673 bytes
5,878 files 393,540,998 bytes
SETUP.EXE 1,314,816 bytes
WIN51 10 bytes
WIN51IP 10 bytes
WIN51IP.SP3 10 bytesUsing an XP machine running AIO, start RyanVM Integrator, integrate the hologram source, with OnePiece AIOv106 UpdatePack and the Addon, in one run. I agree with Atari -- I don't use AV or firewall, or anything ... I just use a good backup program.
Build a bootable iso, and copy it into a thumbdrive. I use Rufus. Partition a respectable amount of space, say 10G, at the front end of a refurbished HDD for the OS, but leave room (as unformatted space) behind it, so that the boot partition boundary can be expanded to 20G for software, after the OS and drivers have been installed and defragged, and a backup made. This keeps the numerous $Pentagon shares, which NTFS installs at fixed addresses (bypassing file manager) and which cannot be moved by the NTFS defragging ap. Unplug your LAN connection, boot into the USB, install the OS and drivers, then cleanup and defrag (native MS defragger), then switch back to your builder-XP system and run a backup. Then expand partition, add software and make backup, then reconnect LAN ... that's what I do anyway
Whether or not the above procedure is correct, it seems to build a working system for me, so maybe it will work for you ...
====
entries_Post-EOS.ini
take note that -- title=, description=, and 7zip Addon filename match
Code: Select all
;by OnePiece
;#############################################################################################################
;This section contains version information to nLite & RyanVM Integrator Entries.ini
;# SPECIAL THANKS TO NONNO FABIAO FOR ALL HELP AND SUPPORT
;# Thank you to RYANVM that with its update pack WinXP i'm inspired myself to create this pack
;# Thank you to NUHI (www.nliteos.com) that with its Nlite Soft i'm inspired myself to create this IE8 AddOn
;# Huge thanks SIGINET (http://www.siginetsoftware.com) for all suggestions and Support
;# Huge thanks Xable (http://thehotfixshare.net) for all Unofficial Hotifx
;# Huge thanks N1K (http://www.WinCert.net) and voidseesaw ( http://voidseesaw.com) host this Update Pack
;# Huge thanks Kelsenellenelvian (http://www.wpiw.net/) and ricktendo64 (www.ricktendo.com) for all Support
;# Huge thanks to all guys of Eng2ITA and WinCert Forum and RyanVM Forum
;# This file contains a list of all necessary entries to add in the various installation
;# files of Windows for the integration of OnePiece's Windows XP Post-SP3 Update Pack.
;#############################################################################################################
;build history -- the following patches were included in this Addon
;
;IE8-WindowsXP-KB3087038-x86-embedded-enu_cummulative.exe 10,664,576
;windowsmedia11-KB3033890-x86-enu.exe 5,821,120
;windowsmedia11-KB3067903-x86-enu.exe 597,696
;windowsxp-KB2926765-x86-embedded-enu.exe 708,848
;windowsxp-KB2957509-x86-embedded-enu.exe 680,176
;windowsxp-KB2961072-x86-embedded-enu.exe 581,360
;windowsxp-KB2989935-x86-embedded-enu.exe 785,624
;windowsxp-KB2991963-x86-embedded-enu.exe 1,024,720
;windowsxp-KB2993254-x86-embedded-enu.exe 805,584
;windowsxp-KB2998579-x86-embedded-enu.exe 582,872
;windowsxp-KB3004361-x86-embedded-enu.exe 638,160
;windowsxp-KB3011780-x86-embedded-enu.exe 650,960
;windowsxp-KB3019215-x86-embedded-enu.exe 594,136
;windowsxp-KB3020338-x86-embedded-enu.exe 766,168
;windowsxp-KB3020393-v2-x86-embedded-enu.exe 545,488
;windowsxp-KB3021674-x86-embedded-enu.exe 714,456
;windowsxp-KB3023562-x86-embedded-enu.exe 548,048
;windowsxp-KB3033395-x86-embedded-enu.exe 2,270,936
;windowsxp-KB3033889-x86-embedded-enu.exe 647,376
;windowsxp-KB3039066-x86-embedded-enu.exe 3,034,320
;windowsxp-KB3055973-v3-x86-embedded-enu.exe 689,904
;windowsxp-KB3069392-x86-embedded-enu.exe 647,408
;windowsxp-KB3072630-x86-embedded-enu.exe 1,672,432
;windowsxp-KB3072633-x86-embedded-enu.exe 1,069,296
;windowsxp-KB3073921-x86-embedded-enu.exe 680,176
;windowsxp-KB3076895-x86-embedded-enu.exe 1,382,128
;WindowsXP-KB3077715-x86-embedded-enu.exe 532,720
;WindowsXP-KB3078601-x86-embedded-enu.exe 2,393,328
;WindowsXP-KB3087039-x86-embedded-enu.exe 1,603,208
[general]
builddate=2015/09/17
description=OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
forcelang=English
language=English
ServicePack=SP3
title=OnePiece_WinXP_Post-SP3_Post-EOS_Addon_2015-0915_ENU
version=1.0.7
website=http://www.microsoft.com/technet/security/current.aspx
Windows=XPall the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3
-
mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Can you please elaborate on what this accomplishes exactly (In laymen's terms)? I'm not mocking you, I am genuinely fascinated by this process.molecule wrote:Partition a respectable amount of space, say 10G, at the front end of a refurbished HDD for the OS, but leave room (as unformatted space) behind it, so that the boot partition boundary can be expanded to 20G for software, after the OS and drivers have been installed and defragged, and a backup made. This keeps the numerous $Pentagon shares, which NTFS installs at fixed addresses (bypassing file manager) and which cannot be moved by the NTFS defragging ap. Unplug your LAN connection, boot into the USB, install the OS and drivers, then cleanup and defrag (native MS defragger), then switch back to your builder-XP system and run a backup. Then expand partition, add software and make backup, then reconnect LAN ... that's what I do anyway
Thanks
Grab a copy of MyDefrag while it's still available (it's owner is retiring this October after what IMHO amounts to ISP hassling ... it's best defragger ever because of its honesty (it reveals the existence of the $admin shares which MS hides, and no other defragger or hdd editor I know of reveals their existence, because they access the hdd through NTFS controls), and its flexible methods and high granularity). Expand the granularity (make each pixel show smaller hdd space) and have a look at all the little one-sector red-dots strewn across the so-called "empty space" at the back end of your best defragged OS partition.
You will find that when Microsoft sets up a system, it does some pretty weird stuff to your hdds. (DOH!) It sprays undocumented sector-coded admin $shares all over the place. These have the potential to become hard-coded backdoor entry points into the totality of your hdd and system. These entry points are not revealed by accessing the hdd through NTFS file system controls. They appear all over the place, covering whatever space is available during initial setup, within the initially empty OS partition.
Because these $shares are located by LBA physical address and not through file name controls, this means that (a) they can't be moved during a defrag -- all commerical defraggers use a standard MS defragging applet and that applet will not allow these hard coded $shares (pentagon entry points?) to be relocated, and (b) they provide a potential LBA-addressed access point into the HDD that bypasses normal system controls for allocation of space on a hdd. Thus, during setup, if you feed MS setup a 200G partition (initially empty), it will spray hundreds of tiny useless one-sector $entry points, way out into farthest reaches of available partition space.
If the farthest one out is at 19G, that means you can never fully defrag your OS partition lower lower than say 19 G of physical space. This is even if you have only 5 G of system files installed. And, that means ... if your system ever crashes, you can only restore your backup on a hdd that is 19 G or larger. Your backup program has to restore them to their original LBA location, at 19G of space, even if the rest of the system has only 5G of files.
These undisclosed admin $shares could also be used internally to bring about an early death to your hdd -- MS is part of an extended economic model, invented by Wall St. called "profit by planned obsolencense." (It's actually a form of theft. The economic concept started with lightbulbs and batteries, expanded to cars, clothing and computers, and now perhaps even to medicine and human beings as well.) I don't know what purpose this insane waste of hdd space might serve, but say these unmovalble $admin shares are part of the system ... loading the kernel for example. In order to bring up the system, the pickup arm of the hdd would have to flail itself up and down the entire space of the hdd, just to load what coudl be a few sectors if these $shares could be defragged and kept together. The resulting mechanical "banging" of the pickup arm, up and down, means your hdd wears out just a little bit sooner ... and voila ... all of a sudden you need a new hdd, which usually means ... a new system. MS and HDD manufacturers and Wall St are getting more of your money (a greater $share of your time actually ...). Truth be known, there is darn little that Windows 10 can do for a user today (not the Wall St thieves and their armies of pentagon-to-nsa spies and bedwetters, the user), that Windows 98se couldn't be doing today, if ordinary normal healthy economic processes were allowed.
So, the short answer is, (a) there's nothing we can do about these admin $shares, except feed MS as small a partition as we can for initilal setup, (b) I'd like my hdds to last longer, or at least I'd like to do what I can to prevent them being thrashed to early demise, for no necessary reason, and (c) in event of a system failure, I like the idea of having the option to restore an emergency backup onto a smaller partition if necessary.
You will find that when Microsoft sets up a system, it does some pretty weird stuff to your hdds. (DOH!) It sprays undocumented sector-coded admin $shares all over the place. These have the potential to become hard-coded backdoor entry points into the totality of your hdd and system. These entry points are not revealed by accessing the hdd through NTFS file system controls. They appear all over the place, covering whatever space is available during initial setup, within the initially empty OS partition.
Because these $shares are located by LBA physical address and not through file name controls, this means that (a) they can't be moved during a defrag -- all commerical defraggers use a standard MS defragging applet and that applet will not allow these hard coded $shares (pentagon entry points?) to be relocated, and (b) they provide a potential LBA-addressed access point into the HDD that bypasses normal system controls for allocation of space on a hdd. Thus, during setup, if you feed MS setup a 200G partition (initially empty), it will spray hundreds of tiny useless one-sector $entry points, way out into farthest reaches of available partition space.
If the farthest one out is at 19G, that means you can never fully defrag your OS partition lower lower than say 19 G of physical space. This is even if you have only 5 G of system files installed. And, that means ... if your system ever crashes, you can only restore your backup on a hdd that is 19 G or larger. Your backup program has to restore them to their original LBA location, at 19G of space, even if the rest of the system has only 5G of files.
These undisclosed admin $shares could also be used internally to bring about an early death to your hdd -- MS is part of an extended economic model, invented by Wall St. called "profit by planned obsolencense." (It's actually a form of theft. The economic concept started with lightbulbs and batteries, expanded to cars, clothing and computers, and now perhaps even to medicine and human beings as well.) I don't know what purpose this insane waste of hdd space might serve, but say these unmovalble $admin shares are part of the system ... loading the kernel for example. In order to bring up the system, the pickup arm of the hdd would have to flail itself up and down the entire space of the hdd, just to load what coudl be a few sectors if these $shares could be defragged and kept together. The resulting mechanical "banging" of the pickup arm, up and down, means your hdd wears out just a little bit sooner ... and voila ... all of a sudden you need a new hdd, which usually means ... a new system. MS and HDD manufacturers and Wall St are getting more of your money (a greater $share of your time actually ...). Truth be known, there is darn little that Windows 10 can do for a user today (not the Wall St thieves and their armies of pentagon-to-nsa spies and bedwetters, the user), that Windows 98se couldn't be doing today, if ordinary normal healthy economic processes were allowed.
So, the short answer is, (a) there's nothing we can do about these admin $shares, except feed MS as small a partition as we can for initilal setup, (b) I'd like my hdds to last longer, or at least I'd like to do what I can to prevent them being thrashed to early demise, for no necessary reason, and (c) in event of a system failure, I like the idea of having the option to restore an emergency backup onto a smaller partition if necessary.
all the platonic solids are created by sexigesimal modulation of rotational action ... the tetrahedron for example is modulo 3
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
At this point can i simply download everything from INTL/English/Windows XP Embedded from https://app.box.com/s/3e9184edlph1e8gw7hsd in order to have all the latest updates? Then simply make an SP3 update pack and POS addon?
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi All, need to update always by yourself the update of Windows XP Embedded\WEPOS\POSReady 2009, is very simple, you have to go in http://catalog.update.microsoft.com/ (attention need to always Internet Explorer) every month, and after search Windows XP Embedded and after only download the latest update, and after use (Last) DXUPAC to create the new addon
However even this time already updated the file, so you need to use the UpdatePack v1.0.7 (It must be in google drive soon), and after go in MEGA or BOX and use the (Last) DXUPAC to create the OnePiece_WinXP_Embedded_Post-SP3_True_AddOn
attention (for reason of time) only UpdatePack enu is been tested in Virtual Machines, so before burning the ISO as usual is recommended to test the ISO in Virtual Machine
Ciao.
However even this time already updated the file, so you need to use the UpdatePack v1.0.7 (It must be in google drive soon), and after go in MEGA or BOX and use the (Last) DXUPAC to create the OnePiece_WinXP_Embedded_Post-SP3_True_AddOn
attention (for reason of time) only UpdatePack enu is been tested in Virtual Machines, so before burning the ISO as usual is recommended to test the ISO in Virtual Machine
Ciao.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
OnePiece, GREAT to see a post by you again!!!!OnePiece Alb wrote:However even this time already updated the file, so you need to use the UpdatePack v1.0.7
I'm having a bit of trouble understanding the above (quoted) sentence, if I understand you correctly, you're "giving" us a new Final XP pack, version 1.0.7? That's WONDERFUL!!!! Thank you so so so much!
Furthermore, I understand from your message that, as before, you're NOT creating a POS pack, because it's simple to create by ourselves. You're correct, we've been doing that for some months now, using your great DXUPAC, and thanks to 5eraph, we're trying to keep the POS updates list current (remove superseded ones, etc.)
Once again, thank you very much for all your help through the years, I really hope there will be localized versions of 1.0.7 as well, if I understand you correctly there will be, only not tested. Looking forward to testing them!!!
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi Atari800xl, I upgraded UpdatePack because, 2 Update for WMP11 + Silverlight + DotNet Update + MRT (KB3033890_WM11 (Replace KB2378111_WM9), KB3067903_WM11, SilverLight v5.1.40728.0 (KB3080333), MRT v5.29, Adobe Flash Player v19.0.0.226)
however in case that I will update again UpdatePack, I will remove the MRT, is almost 50 MB ehhh, and now UpdatePack is more than 250 MB, so do not let me upload more in BOX and some other server
In the latest release I put in DXUPAC, that if located in directors only file Embedded, then automatically changes the entries.ini ect ect and rename the pack in OnePiece_WinXP_Embedded_Post-SP3_True_AddOn_Lang, in poor words the DXUPAC does everything automatically, you just put the Embedded file and make a single click, and create always the last adddon, I chose the DXUPAC mod because you can always choose what to put or not to put in the addon, or as it release an update will not have to wait for me to release the new addon, but you can now create it by itself, I think better this way
however, for testing purposes already created all the Embedded Addon, look (Google Drive) in WinXP_Embedded_Post-SP3_True_AddOn_v2015.10.20
those who want can always do everything by itself, just run the DXUPAC.exe /DX_ALL, and DXUPAC will create all UpdatePack & Embedded AddOn automatically (you need to copy all the INTL files, manually in all Local)
or only Embedded AddOn
Ciao.
however in case that I will update again UpdatePack, I will remove the MRT, is almost 50 MB ehhh, and now UpdatePack is more than 250 MB, so do not let me upload more in BOX and some other server
In the latest release I put in DXUPAC, that if located in directors only file Embedded, then automatically changes the entries.ini ect ect and rename the pack in OnePiece_WinXP_Embedded_Post-SP3_True_AddOn_Lang, in poor words the DXUPAC does everything automatically, you just put the Embedded file and make a single click, and create always the last adddon, I chose the DXUPAC mod because you can always choose what to put or not to put in the addon, or as it release an update will not have to wait for me to release the new addon, but you can now create it by itself, I think better this way
however, for testing purposes already created all the Embedded Addon, look (Google Drive) in WinXP_Embedded_Post-SP3_True_AddOn_v2015.10.20
those who want can always do everything by itself, just run the DXUPAC.exe /DX_ALL, and DXUPAC will create all UpdatePack & Embedded AddOn automatically (you need to copy all the INTL files, manually in all Local)
or only Embedded AddOn
Ciao.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
OnePice, this is wonderful!!!!! I downloaded the new Final XP pack 1.0.7 and your new Embedded True_addon. Thank you, thank you, thank you.
Of course, I also wanted to test the new automatic DXUPAC POS addon creation method, this also works perfectly and will save a lot of time!!! Thanks again, this was really a very nice surprise, totally unexpected!
For others who want to try this as well: please learn from my mistakes, and
(1) be sure to place the NEW DXUPAC.exe (1.2.3.3, not 1.2.3.2) into the \Updatepack folder.
(2) The subfolder has to be named "Windows XP Embedded"
(3) In the "Windows XP Embedded" subfolder, there has to be another subfolder, with the correct language name ("Dutch", in my case). On my first test run, I forgot this third subfolder.
So that's "\Updatepack\Windows XP Embedded\Dutch".
(4) Place all POS updates into that final subfolder. And here's what I didn't realize at first: You can change the original filenames of the POS addons (in my case, I shortended them, because the paths were becoming too long in my backup folder), but you must keep the word "embedded" somewhere in the filename. If you don't, dxupac will still work, but you'll end up with a "normal" updatepack, not an addon
(5) Use DXUPAC.exe with the /DX_ALL command line option.
So now I'm really excited to see how others like your great new contributions!
Of course, I also wanted to test the new automatic DXUPAC POS addon creation method, this also works perfectly and will save a lot of time!!! Thanks again, this was really a very nice surprise, totally unexpected!
For others who want to try this as well: please learn from my mistakes, and
(1) be sure to place the NEW DXUPAC.exe (1.2.3.3, not 1.2.3.2) into the \Updatepack folder.
(2) The subfolder has to be named "Windows XP Embedded"
(3) In the "Windows XP Embedded" subfolder, there has to be another subfolder, with the correct language name ("Dutch", in my case). On my first test run, I forgot this third subfolder.
So that's "\Updatepack\Windows XP Embedded\Dutch".
(4) Place all POS updates into that final subfolder. And here's what I didn't realize at first: You can change the original filenames of the POS addons (in my case, I shortended them, because the paths were becoming too long in my backup folder), but you must keep the word "embedded" somewhere in the filename. If you don't, dxupac will still work, but you'll end up with a "normal" updatepack, not an addon
(5) Use DXUPAC.exe with the /DX_ALL command line option.
So now I'm really excited to see how others like your great new contributions!
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Use RyanVM integrator, (like the forum name).master2 wrote:DXUPAC create the update pack 1.0.7 and another one pack, the Embedded AddOn pack.
So we add this 2 pack in NLite, right? Or must be 1 update pack with all updates?
http://integrator.professorcpu.net/?download
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Well, at leat master2 and me are both very happy with your new contributions.
I expected a little bit more excitement to be honest...
The new DXUPAC is bringing some wonderful improvements, so I guess it will take a bit of time until all the old XP geezers will discover its new power
Molecule, are you still out there?
I expected a little bit more excitement to be honest...
The new DXUPAC is bringing some wonderful improvements, so I guess it will take a bit of time until all the old XP geezers will discover its new power
Molecule, are you still out there?
Update Pack Updates
Hi Everyone I really would like to thank OnePiece for these new updates and ask that you dont give up on us and keep up the good work. Thank You Very Much.
I Just tested my new .iso made wih nlite. Everything works fine. Thanks everyone else for all of your hard work.
I Just tested my new .iso made wih nlite. Everything works fine. Thanks everyone else for all of your hard work.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Just saw another update to DXUPAC (timezone related, Argentina and Korea I believe).
Just found it very funny that creating a POS Addon with DXUPAC is now as easy as 1,2,3 [4], but the actual file version of DXUPAC is now also "1.2.3.4".
Oh well, little things like that make *me* smile
Also, OnePiece updated the Changelog and Hotfixlist files for 1.0.7 (found them in the Box folder).
And on an unrelated note (hopefully): It seems Youtube has now stopped working with IE8? No biggie, but wanted to throw that in. Again, seems completely unrelated to the update packs...
Just found it very funny that creating a POS Addon with DXUPAC is now as easy as 1,2,3 [4], but the actual file version of DXUPAC is now also "1.2.3.4".
Oh well, little things like that make *me* smile
Also, OnePiece updated the Changelog and Hotfixlist files for 1.0.7 (found them in the Box folder).
And on an unrelated note (hopefully): It seems Youtube has now stopped working with IE8? No biggie, but wanted to throw that in. Again, seems completely unrelated to the update packs...
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi All, about DotNet Update here http://www.ryanvm.net/forum/viewtopic.p ... 164#140164
Ciao a tutti.
Ciao a tutti.
Hello OnePiece, I just wanted to post here to thank you for your XP Post-SP3 All-in-One Update Pack, which I’ve used for almost two years now without a single problem.
I’m pleased that you have returned with version 1.07, and what a bonus your new DXUPAC 1.2.3.4 provides, so that we can make our own fully-updated XP installation if need be. Having said that, I do hope you continue to update your own XP Post-SP3 Update Pack, even if only once in a while.
Thank you very much for all your great work!
I’m pleased that you have returned with version 1.07, and what a bonus your new DXUPAC 1.2.3.4 provides, so that we can make our own fully-updated XP installation if need be. Having said that, I do hope you continue to update your own XP Post-SP3 Update Pack, even if only once in a while.
Thank you very much for all your great work!
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi All, could come out problems during the integration with the latest release of UpdatePack, is strongly recommended always to keep 7-Zip pluging of the nLite and RVMi updated, we return to http://www.ryanvm.net/forum/viewtopic.p ... 7b2#127849 but the fault is no longer of LZMA2 but the new 7-Zip seems ehhhh, however it is always recommended to keep pluging of nLite\RVMi updated (which is why I have not seen in testing it because for me (is a habit now) always update the pluging of the nLite\RVMi)
so always need to download the latest 7-Zip (in this case v15.09) extract and take 7z.exe and 7z.dll, and copy\replace\update in nLite folder, and also download the 7z%ver%-extra.7z in this case the 7z1509-extra.7z and extract and take 7za.exe and rename in 7zdn.exe, and after copying\replace\update in the RVMi\Plugins folder, here is already ready
nLite & RVMi 7-Zip Plugins
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Update (27 October 2015)
Hash MD5 44AC834A7F8947CD0968EE17D68BE693
Filesize: 0.61 MB (644680 bytes)
Ciao a tutti.
so always need to download the latest 7-Zip (in this case v15.09) extract and take 7z.exe and 7z.dll, and copy\replace\update in nLite folder, and also download the 7z%ver%-extra.7z in this case the 7z1509-extra.7z and extract and take 7za.exe and rename in 7zdn.exe, and after copying\replace\update in the RVMi\Plugins folder, here is already ready
nLite & RVMi 7-Zip Plugins
Update (27 October 2015) Update (27 October 2015) Update (27 October 2015) Update (27 October 2015) Update (27 October 2015) Update (27 October 2015) Update (27 October 2015) Update (27 October 2015) Update (27 October 2015)Hash MD5 44AC834A7F8947CD0968EE17D68BE693
Filesize: 0.61 MB (644680 bytes)
Ciao a tutti.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Thank you OnePiece!
I always use RVMi, so I will make it a habit to keep the plugin folder updated with the latest 7zip.
I must say I haven't had any problems with it for the latest 1.07, but then I again I used a self-made 1.07 (made from the Dutch and INTL folders in your Box folder), maybe that's the reason?
In the thread you mentioned, I saw Nonno Fabio mentioned something about this only being a problem for the Italian version? Must admit I'm a little bit confused, but I'll take your word for it and keep the plugin folder updated!!
Thanks for keeping us updated!!! Hope you;ll stick around!
I always use RVMi, so I will make it a habit to keep the plugin folder updated with the latest 7zip.
I must say I haven't had any problems with it for the latest 1.07, but then I again I used a self-made 1.07 (made from the Dutch and INTL folders in your Box folder), maybe that's the reason?
In the thread you mentioned, I saw Nonno Fabio mentioned something about this only being a problem for the Italian version? Must admit I'm a little bit confused, but I'll take your word for it and keep the plugin folder updated!!
Thanks for keeping us updated!!! Hope you;ll stick around!
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi, nothing to get confused, at that time (when 7zip installer\setup sets by defualt use of LZMA2 mod) was only UpdatePack ITA created in LZMA2 mod, but now is for sure every UpdatePack was created with 7-Zip v15.09, so need to update the nLite\RVMi 7-Zip plugin, to be sure that everything is always OK
Ciao.
Ciao.
About Updates
Thanks Again OnePiece for the information and all of your hard work and time.
Happy Holloween and all the best.
Happy Holloween and all the best.
Atari800xl About List
Hi Atari800xl Could you Please post an updated POSready list if it is not t much trouble.
Thanks in Advance.
Thanks in Advance.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Changes from OnePiece's october list, using
https://catalog.update.microsoft.com/v7/site/Home.aspx
(search for "xp embedded") and 5eraph's changelog
http://www.ryanvm.net/forum/viewtopic.p ... 021#138021
High priority update KB3092601 replaced high priority update KB2989935.
High priority update KB3097877 replaced high priority update KB3078601.
High priority update KB3100773 replaced high priority update KB3093983.
High priority update KB3081320 replaced additional update KB3055973-v3.
The new list (this is when you use the new OnePiece Final XP pack 1.07!!):
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254 kb2998579
kb3004361 kb3011780 kb3019215 kb3020338 kb3020393 kb3021674
kb3023562 kb3033395 kb3033889 kb3069392 kb3072630 kb3072633
kb3073921 kb3076895 kb3077715 kb3080446 kb3081320 kb3087039
kb3092601 kb3097877 kb3100773
I just finished my new iso (was busy yesterday), looking good...
I was hoping OnePiece would update his online folders as well, but the four changes above are easily done, and with the great new DXUPAC "auto mode", the new POS Addon can be created very quickly.
https://catalog.update.microsoft.com/v7/site/Home.aspx
(search for "xp embedded") and 5eraph's changelog
http://www.ryanvm.net/forum/viewtopic.p ... 021#138021
High priority update KB3092601 replaced high priority update KB2989935.
High priority update KB3097877 replaced high priority update KB3078601.
High priority update KB3100773 replaced high priority update KB3093983.
High priority update KB3081320 replaced additional update KB3055973-v3.
The new list (this is when you use the new OnePiece Final XP pack 1.07!!):
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254 kb2998579
kb3004361 kb3011780 kb3019215 kb3020338 kb3020393 kb3021674
kb3023562 kb3033395 kb3033889 kb3069392 kb3072630 kb3072633
kb3073921 kb3076895 kb3077715 kb3080446 kb3081320 kb3087039
kb3092601 kb3097877 kb3100773
I just finished my new iso (was busy yesterday), looking good...
I was hoping OnePiece would update his online folders as well, but the four changes above are easily done, and with the great new DXUPAC "auto mode", the new POS Addon can be created very quickly.
Hi Atari800xl
Hi Atari800xl I just Wanted to say Thank You and have a great day.
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
-
OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
@All
However this month was also updated DotNet40, already found a bit of free time, and already updated (I did not have time for testing it, but as I mentioned here http://www.ryanvm.net/forum/viewtopic.p ... 164#140164 is all OK)
As always you can find it in the INTL folder, or here http://www.ryanvm.net/forum/viewtopic.php?t=8317
Ciao a tutti.
However this month was also updated DotNet40, already found a bit of free time, and already updated (I did not have time for testing it, but as I mentioned here http://www.ryanvm.net/forum/viewtopic.p ... 164#140164 is all OK)
As always you can find it in the INTL folder, or here http://www.ryanvm.net/forum/viewtopic.php?t=8317
Ciao a tutti.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Thanks for the offer to edit your Box folder, OnePiece...
However, I normally only download the Dutch POS updates, I don't even know how I should get the other international version.
Also, there seem to be only a very few people left here interested in them (where's molecule!?), so a good solution for now is to keep the POS update *index* (/list) current (5eraph's changelog is a big help for me), so everybody can download the updates for themselves relatively easy.
Now that DXUPAC can create the Addon in a single run through, things have gotten a LOT easier!!
However, I normally only download the Dutch POS updates, I don't even know how I should get the other international version.
Also, there seem to be only a very few people left here interested in them (where's molecule!?), so a good solution for now is to keep the POS update *index* (/list) current (5eraph's changelog is a big help for me), so everybody can download the updates for themselves relatively easy.
Now that DXUPAC can create the Addon in a single run through, things have gotten a LOT easier!!
I tested UpdatePack 1.07 and DXUPAC 1.2.3.4 (never having used DXUPAC before) and would like to share the results here…
I created XP Pro install DVD using UpdatePack 1.07 and nLite, installed the operating system, applied the POS registry mod and ran Windows Update, which listed 32 critical updates available:
kb2926765 kb2957503 kb2957509 kb2961072 kb2993651
kb2998579 kb3004361 kb3006226 kb3011780 kb3013126
kb3019215 kb3020393 kb3021674 kb3023562 kb3029944
kb3033395 kb3033889 kb3035132 kb3065979 kb3069392
kb3072630 kb3072633 kb3073921 kb3076895 kb3077715
kb3078601 kb3080446 kb3081320 kb3087039 kb3092601
kb3097877 kb3100773
Then I tested UpdatePack 1.07 and DXUPAC-created embedded add-on two different ways, one by using the 32 updates suggested by WU, the other by using the 27 updates posted above by Atari800xl. (The two sets have 24 updates in common; the 27 listed here lack 8 from the WU list, and WU is missing 3 from the list of 27). I integrated the UpdatePack and the embedded add-ons using nLite.
In both instances the product OS installs smoothly, no glitches, hang-ups, warnings or errors, and I run the POS mod.
Afterward, WU finds no critical updates available for either method.
I created XP Pro install DVD using UpdatePack 1.07 and nLite, installed the operating system, applied the POS registry mod and ran Windows Update, which listed 32 critical updates available:
kb2926765 kb2957503 kb2957509 kb2961072 kb2993651
kb2998579 kb3004361 kb3006226 kb3011780 kb3013126
kb3019215 kb3020393 kb3021674 kb3023562 kb3029944
kb3033395 kb3033889 kb3035132 kb3065979 kb3069392
kb3072630 kb3072633 kb3073921 kb3076895 kb3077715
kb3078601 kb3080446 kb3081320 kb3087039 kb3092601
kb3097877 kb3100773
Then I tested UpdatePack 1.07 and DXUPAC-created embedded add-on two different ways, one by using the 32 updates suggested by WU, the other by using the 27 updates posted above by Atari800xl. (The two sets have 24 updates in common; the 27 listed here lack 8 from the WU list, and WU is missing 3 from the list of 27). I integrated the UpdatePack and the embedded add-ons using nLite.
In both instances the product OS installs smoothly, no glitches, hang-ups, warnings or errors, and I run the POS mod.
Afterward, WU finds no critical updates available for either method.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
That's wonderful news, bluebolt!!!
Reading your first few sentences (and experience from the other threads) actually had me worried for a bit, but then I read that everything went fine for you.
So a pretty rewarding experience, right?
Thanks for taking the time to share it with us, hope you will stick around and help us in the future!!
Reading your first few sentences (and experience from the other threads) actually had me worried for a bit, but then I read that everything went fine for you.
So a pretty rewarding experience, right?
Thanks for taking the time to share it with us, hope you will stick around and help us in the future!!
You are right, Atari800xl, definitely a rewarding experience, and I was surprised at how easy it was to use DXUPAC. I don’t know all the ins and outs of Windows updates, so I’m a little curious as to why the two sets of updates differ, yet either way we achieve “zero WU†(as nonno put it back on page one of this thread). Given the success of either method, I don’t think I will lose any sleep over it.
This is one of the greatest posts i've EVER seen! The amount of insight and understanding you have regarding Window's practices is admirable! I'd love to know how you even figured this out! BTW: Your POS addon instructions worked fine for me and i'm now building successful ISOs.molecule wrote:Grab a copy of MyDefrag while it's still available (it's owner is retiring this October after what IMHO amounts to ISP hassling ... it's best defragger ever because of its honesty (it reveals the existence of the $admin shares which MS hides, and no other defragger or hdd editor I know of reveals their existence, because they access the hdd through NTFS controls), and its flexible methods and high granularity). Expand the granularity (make each pixel show smaller hdd space) and have a look at all the little one-sector red-dots strewn across the so-called "empty space" at the back end of your best defragged OS partition.
You will find that when Microsoft sets up a system, it does some pretty weird stuff to your hdds. (DOH!) It sprays undocumented sector-coded admin $shares all over the place. These have the potential to become hard-coded backdoor entry points into the totality of your hdd and system. These entry points are not revealed by accessing the hdd through NTFS file system controls. They appear all over the place, covering whatever space is available during initial setup, within the initially empty OS partition.
Because these $shares are located by LBA physical address and not through file name controls, this means that (a) they can't be moved during a defrag -- all commerical defraggers use a standard MS defragging applet and that applet will not allow these hard coded $shares (pentagon entry points?) to be relocated, and (b) they provide a potential LBA-addressed access point into the HDD that bypasses normal system controls for allocation of space on a hdd. Thus, during setup, if you feed MS setup a 200G partition (initially empty), it will spray hundreds of tiny useless one-sector $entry points, way out into farthest reaches of available partition space.
If the farthest one out is at 19G, that means you can never fully defrag your OS partition lower lower than say 19 G of physical space. This is even if you have only 5 G of system files installed. And, that means ... if your system ever crashes, you can only restore your backup on a hdd that is 19 G or larger. Your backup program has to restore them to their original LBA location, at 19G of space, even if the rest of the system has only 5G of files.
These undisclosed admin $shares could also be used internally to bring about an early death to your hdd -- MS is part of an extended economic model, invented by Wall St. called "profit by planned obsolencense." (It's actually a form of theft. The economic concept started with lightbulbs and batteries, expanded to cars, clothing and computers, and now perhaps even to medicine and human beings as well.) I don't know what purpose this insane waste of hdd space might serve, but say these unmovalble $admin shares are part of the system ... loading the kernel for example. In order to bring up the system, the pickup arm of the hdd would have to flail itself up and down the entire space of the hdd, just to load what coudl be a few sectors if these $shares could be defragged and kept together. The resulting mechanical "banging" of the pickup arm, up and down, means your hdd wears out just a little bit sooner ... and voila ... all of a sudden you need a new hdd, which usually means ... a new system. MS and HDD manufacturers and Wall St are getting more of your money (a greater $share of your time actually ...). Truth be known, there is darn little that Windows 10 can do for a user today (not the Wall St thieves and their armies of pentagon-to-nsa spies and bedwetters, the user), that Windows 98se couldn't be doing today, if ordinary normal healthy economic processes were allowed.
So, the short answer is, (a) there's nothing we can do about these admin $shares, except feed MS as small a partition as we can for initilal setup, (b) I'd like my hdds to last longer, or at least I'd like to do what I can to prevent them being thrashed to early demise, for no necessary reason, and (c) in event of a system failure, I like the idea of having the option to restore an emergency backup onto a smaller partition if necessary.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
No not yet....i'm a bit nervous to as i finally got things working using your instructions which really aren't all that hard to do anyway. If the latest DXUPAC actually downloaded and THEN made the addon i'd probably be more enticed...but so far it seems like it just prevents a couple name changes correct?Atari800xl wrote:Skrell, nice to see you're back...
Did you try the "automatic mode" of the latest DXUPAC version, to create the POS addon? It's great!!!
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
I just wanted to point out the new DXUPAC "POS Auto mode" ("/dx_all") because I guess we need to build new a POS Addon again in about 10 days, so it might be worth a try.
From my notes:
- Make a folder d:\makepack
- Put latest dxupac.exe (1.2.3.3 or later) in d:\makepack
- Create these folders: "d:\MakePack\Windows XP Embedded\English" (Or different language)
- Put all updates in that "deepest" subfolder, make sure they all have "embedded" somewhere in their filenames
- Start "dxupac /dx_all" in d:\makepack
You might want to give it a try, it's easy! (Thanks OnePiece!!!!)
From my notes:
- Make a folder d:\makepack
- Put latest dxupac.exe (1.2.3.3 or later) in d:\makepack
- Create these folders: "d:\MakePack\Windows XP Embedded\English" (Or different language)
- Put all updates in that "deepest" subfolder, make sure they all have "embedded" somewhere in their filenames
- Start "dxupac /dx_all" in d:\makepack
You might want to give it a try, it's easy! (Thanks OnePiece!!!!)
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
New updates today, hope this is correct:
kb3104002 (ie8) replaces 3100773
kb3105579 (not needed when you use the ie8 update, contains jscript, vbscript)
kb3108381 (new, comsvcs.dll)
kb3109094 (win32k.sys, does not replace kb387039, which has extra atmfd.dll)
kb3112148 (replaces 3077715, tzchange)
So that's 5 new ones, of which we need 4 for the POS Addon.
2 older POS updates are replaced.
For November we had 27. Add 4, remove 2, new total is 29:
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254
kb2998579 kb3004361 kb3011780 kb3019215 kb3020338
kb3020393 kb3021674 kb3023562 kb3033395 kb3033889
kb3069392 kb3072630 kb3072633 kb3073921 kb3076895
kb3080446 kb3081320 kb3087039 kb3092601 kb3097877
kb3104002 kb3108381 kb3109094 kb3112148
kb3104002 (ie8) replaces 3100773
kb3105579 (not needed when you use the ie8 update, contains jscript, vbscript)
kb3108381 (new, comsvcs.dll)
kb3109094 (win32k.sys, does not replace kb387039, which has extra atmfd.dll)
kb3112148 (replaces 3077715, tzchange)
So that's 5 new ones, of which we need 4 for the POS Addon.
2 older POS updates are replaced.
For November we had 27. Add 4, remove 2, new total is 29:
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254
kb2998579 kb3004361 kb3011780 kb3019215 kb3020338
kb3020393 kb3021674 kb3023562 kb3033395 kb3033889
kb3069392 kb3072630 kb3072633 kb3073921 kb3076895
kb3080446 kb3081320 kb3087039 kb3092601 kb3097877
kb3104002 kb3108381 kb3109094 kb3112148
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Thanks 5eraph!!! I made a little mistake, and stopped searching in my list when I found the found the first instance of "win32k.sys" (in 387039).
I should have continued the search, then I would have found it in 3097877 (the superseded one) as well!
THANK YOU! (Still learning here...)
So I guess it should be like this:
kb3104002 (ie8) replaces 3100773
kb3105579 (not needed when you use the ie8 update, contains jscript, vbscript)
kb3108381 (new, comsvcs.dll)
kb3109094 (win32k.sys, does not replace kb387039, which has extra atmfd.dll)
But *does* replace kb3097877 (thanks 5eraph!)
kb3112148 (replaces 3077715, tzchange)
So that's 5 new ones, of which we need 4 for the POS Addon.
3 older POS updates are replaced.
For November we had 27. Add 4, remove 3, new total is 28:
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254
kb2998579 kb3004361 kb3011780 kb3019215 kb3020338
kb3020393 kb3021674 kb3023562 kb3033395 kb3033889
kb3069392 kb3072630 kb3072633 kb3073921 kb3076895
kb3080446 kb3081320 kb3087039 kb3092601
kb3104002 kb3108381 kb3109094 kb3112148
I should have continued the search, then I would have found it in 3097877 (the superseded one) as well!
THANK YOU! (Still learning here...)
So I guess it should be like this:
kb3104002 (ie8) replaces 3100773
kb3105579 (not needed when you use the ie8 update, contains jscript, vbscript)
kb3108381 (new, comsvcs.dll)
kb3109094 (win32k.sys, does not replace kb387039, which has extra atmfd.dll)
But *does* replace kb3097877 (thanks 5eraph!)
kb3112148 (replaces 3077715, tzchange)
So that's 5 new ones, of which we need 4 for the POS Addon.
3 older POS updates are replaced.
For November we had 27. Add 4, remove 3, new total is 28:
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254
kb2998579 kb3004361 kb3011780 kb3019215 kb3020338
kb3020393 kb3021674 kb3023562 kb3033395 kb3033889
kb3069392 kb3072630 kb3072633 kb3073921 kb3076895
kb3080446 kb3081320 kb3087039 kb3092601
kb3104002 kb3108381 kb3109094 kb3112148
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
For the last couple of months, OnePiece surprised us by updating his online repositories with the latest POS updates and Final XP Pack updates, so I wonder if he will update them for the January POS updates as well, but for now I would like to share my current list of POS updates, just for reference. (Thanks to 5eraph for confirming!)
With dxupac, these can easily be made into a new (localized!) POSReady addon.
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254
kb2998579 kb3004361 kb3011780 kb3019215 kb3020338
kb3020393 kb3021674 kb3023562 kb3033395 kb3033889
kb3072630 kb3072633 kb3073921 kb3076895 kb3080446
kb3081320 kb3087039 kb3092601 kb3108381 kb3109094
kb3109560 kb3112148 kb3121918 kb3124000 kb3124001
kb3124275
With dxupac, these can easily be made into a new (localized!) POSReady addon.
kb2926765 kb2957509 kb2961072 kb2991963 kb2993254
kb2998579 kb3004361 kb3011780 kb3019215 kb3020338
kb3020393 kb3021674 kb3023562 kb3033395 kb3033889
kb3072630 kb3072633 kb3073921 kb3076895 kb3080446
kb3081320 kb3087039 kb3092601 kb3108381 kb3109094
kb3109560 kb3112148 kb3121918 kb3124000 kb3124001
kb3124275
About Update List
Hi Atari800xl Thank You for the Updated List.
PS: Can you give me what replaces what. Thanks Again
PS: Can you give me what replaces what. Thanks Again
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Stormit, you can always check 5eraph's changelog for that (like I do):
http://www.ryanvm.net/forum/viewtopic.p ... 021#138021
http://www.ryanvm.net/forum/viewtopic.p ... 021#138021
I've posted a Resultant Set of Changes that should roughly coincide with OnePiece's update pack. The exceptions are below. Otherwise our lists match, Atari800xl.
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Thanks 5eraph. I should have mentioned your great RootsUpd and RvkRoots updates, but I include these in my "PostInstall" tool, so I don't consider them part of the POS Updatepack.
Still no word from OnePiece, hope he'll be back again soon (we warned us last year he won't be around as much anymore). Also, where's Molecule!!?
Still no word from OnePiece, hope he'll be back again soon (we warned us last year he won't be around as much anymore). Also, where's Molecule!!?
-
Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
I downloaded the latest POS updates yesterday and created a new Addon with DXUPAC.
I believe these are the new ones:
kb3124280 replaces kb3019215 (mrxdav.sys)
kb3126041 replaces kb3011780 (kerberos.dll)
kb3126587
kb3126593 replaces kb3072633 (ole32.dll)
kb3134146 replaces kb3033395 (ntkrnlmp etc)
kb3134214 replaces kb3124000 (win32k.sys) (thanks, 5eraph!!)
kb3134814 replaces kb3124275 (ie8)
I was in a bit of a hurry, so no guarantees, I will await 5eraph's changelog for confirmation.
I didn't have time to check out the new SP4 by Harkaz either, as I understand it this is enUS only, for now it seems to me the "OnePiece" solution is still preferred for localized updatepacks?
As usual, I'm still hoping to hear from OnePiece, but as he told us, he will not be able to update his online repos each and every month...
I believe these are the new ones:
kb3124280 replaces kb3019215 (mrxdav.sys)
kb3126041 replaces kb3011780 (kerberos.dll)
kb3126587
kb3126593 replaces kb3072633 (ole32.dll)
kb3134146 replaces kb3033395 (ntkrnlmp etc)
kb3134214 replaces kb3124000 (win32k.sys) (thanks, 5eraph!!)
kb3134814 replaces kb3124275 (ie8)
I was in a bit of a hurry, so no guarantees, I will await 5eraph's changelog for confirmation.
I didn't have time to check out the new SP4 by Harkaz either, as I understand it this is enUS only, for now it seems to me the "OnePiece" solution is still preferred for localized updatepacks?
As usual, I'm still hoping to hear from OnePiece, but as he told us, he will not be able to update his online repos each and every month...
Last edited by Atari800xl on Thu Feb 11, 2016 12:55 am, edited 1 time in total.