Jump to content

What happened to the OnePiece XP Add-on thread(s)?


waqqas31

Recommended Posts


The dot NET portions have been giving me headaches with Microsoft Update and I was *hoping* to ask the author about them.

Before you ask, there's a small bug in v4.8.0 that will be fixed in upcoming release.

Here's an easy workaround for running systems: copy and paste these lines in Notepad.

 [Version]
Signature="$Windows NT$"

[DefaultInstall]
AddReg =REGEntries.AddReg

[REGEntries.AddReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\62A79A60FA1136F438E2F4263C7A1D63","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\7A0DCDED98788304DB93CC7B4D95E24D","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\815DE197FE1BE664CB88CB6D3CA9C629","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FD01C6A9B00EFA749A5683F6D47045BD","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FD01C6A9B00EFA749A5683F6D47045BD","00000000000000000000000000000000", ,"%24%"

and save with .inf extension (EG fix.inf). Then run it, this should fix the MU issue

Edited by nonno fabio
Link to comment
Share on other sites

There was until recently a Topic entitled Onepiece XP Post-SP3 AIO Update Pack posted by nonno fabio. Is that the one you were looking for?

Yes, that's the one.

The dot NET portions have been giving me headaches with Microsoft Update and I was *hoping* to ask the author about them.

Before you ask, there's a small bug in v4.8.0 that will be fixed in upcoming release.

Here's an easy workaround for running systems: copy and paste these lines in Notepad.

 [Version]
Signature="$Windows NT$"

[DefaultInstall]
AddReg =REGEntries.AddReg

[REGEntries.AddReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\62A79A60FA1136F438E2F4263C7A1D63","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\7A0DCDED98788304DB93CC7B4D95E24D","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\815DE197FE1BE664CB88CB6D3CA9C629","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FD01C6A9B00EFA749A5683F6D47045BD","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FD01C6A9B00EFA749A5683F6D47045BD","00000000000000000000000000000000", ,"%24%"

and save with .inf extension (EG fix.inf). Then run it, this should fix the MU issue

Was this bug also in 4.6.0? That's the only other version I tried and I experienced the same issue.

Thanks in advance!

Link to comment
Share on other sites

The dot NET portions have been giving me headaches with Microsoft Update and I was *hoping* to ask the author about them.

Before you ask, there's a small bug in v4.8.0 that will be fixed in upcoming release.

Here's an easy workaround for running systems: copy and paste these lines in Notepad.

 [Version]
Signature="$Windows NT$"

[DefaultInstall]
AddReg =REGEntries.AddReg

[REGEntries.AddReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\62A79A60FA1136F438E2F4263C7A1D63","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\7A0DCDED98788304DB93CC7B4D95E24D","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\815DE197FE1BE664CB88CB6D3CA9C629","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FD01C6A9B00EFA749A5683F6D47045BD","DC3BF90CC0D3D2F398A9A6D1762F70F3", ,"%24%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FD01C6A9B00EFA749A5683F6D47045BD","00000000000000000000000000000000", ,"%24%"

and save with .inf extension (EG fix.inf). Then run it, this should fix the MU issue

Didn't work, btw :( Same updates fail to install.

Link to comment
Share on other sites

The Topic is currently subject to approval due to a belief that it may be in breach of the following section of our rules!

» No Illegal/Copyrighted Software Discussion

1.a This is not a warez site! Links/Requests to warez and/or illegal material (e.g., cracks, serials, etc.) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/license restrictions, use of keygens, or any other illegal activity, including, but not limited to, requests for help where pirated software is being used or being discussed, will also not be tolerated. Offenders may be banned on first violation.

1.b Respect the requests of companies who do not permit redistribution of their products without express permission - including unmodified hotfix/feature pack packages. Download sources for official software should be from the vendor directly where possible. Posts made containing this type of content may be removed immediately without warning, and offenders may be banned on first violation.

1.c Users should be made aware of what they are getting prior to any download/install package from a Member provided link. As such, every post which contains links to repackaged software MUST state specifically the nature of the software. This includes, but is not limited to, trialware, shareware, payware, freeware etc. If a trial version, the length of the trial should be stated as should whether an uninstall is part of the package. If registration keys/information is required to be input for continued usage of software in the package, then the post must state that fact as well. Any message with link(s) found to not state this required information will be removed and will result in measures being taken against the poster, up to and including a ban. Also, if the stated information is found to be deceptive or the software redistribution is found to be illegal (rule 1.b ), the poster will be banned.

1.d If a product's license agreement or license type specifically prohibits the usage of said product in a particular manner (for example, a Creative Commons license that prohibits commercial usage), please do not post questions or comments about the usage of said products in a manner that violates the license agreement. If there is any doubt about a license agreement's coverage and restrictions please question the owners or authors of the product directly if your usage violates their licensing agreement; please do not use MSFN for such requests (unless MSFN is the support forum for said product). Any offenders of this rule may be banned on first violation. We take issues like this very seriously here at MSFN.

Link to comment
Share on other sites

  • 2 weeks later...

Didn't work, btw :( Same updates fail to install.

It works for all the other users so there should be something else. You could try a new Windows installation with newer v4.9.0 UpdatePack (Test the updated .iso on a VM before installing in a real system.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...