Hey guys, I'm confused about 1 thing. Usually MS releases updates on the 2nd Tuesday and Onepiece shortly thereafter. The latest pack here was released 12/1. I didn't even come to see if it was released yet till today. Why so early, and will it then not include December updates? Thanks!

edit: Okay, I just woke up so bear with me. Now I see that was November update, just later than usual. Any idea when December will be released? @Onepiece, Nonno Fabio and Ricktendo, you guys are all awesome! Thanks so much for all your help!

sathanas65 wrote:Right, second Tuesday. That I am aware of. But since the last release here was more than 3 weeks after patch Tuesday, just wondering if there will even be a December release of this pack. Thanks.

Thanks so much for taking the time to point this out. Now I understand. I only update my PowerPack disk every other month on the even numbered months, so I never use releases from November and was totally out of the loop. Thanks!

There's a new version already?! I just got v5.20 two weeks ago! I just checked and I downloaded it December 2, 2011.

I just slipstreamed v5.20 with 5araph's rollback(to allow window's live install) which worked like a charm along with all my CABS the only thing I didn't slipstream was the driverpacks with DriverBase.

Dang it now I have to start all over again with v5.30.

Oh well, I guess it's best to use the recent version with all the current updates. However, I'm still going to make a disk with v5.20 just to be on the safe side.

I just tested my source. No issues at all. Once I apply this pack, and then the bug fix, the issues appears. I am a bit confused because you said "Bug and bugfix are both harmful." Should I be integrating them at the same time in the same operation? Thanks.

I am now integrating bug and bug fix in a single operation and will report back.

I mean they can't cause such issues. Yes, you must integrate the fix after the updatepack in the same integration session. You can also edit directly updatepack OPMWXPUP.inf file.
Sorry if I've not clearly state it, I'll fix that post too

Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead

nonno fabio wrote:I mean they can't cause such issues. Yes, you must integrate the fix after the updatepack in the same integration session. You can also edit directly updatepack OPMWXPUP.inf file.
Sorry if I've not clearly state it, I'll fix that post too

nonno fabio:

When you say "You must integrate the fix after the updatepack in the same integration session", do you mean that you should have both the One Piece Post XP Pack v5.30 and the Repair One Piece v5.30 set up to install at the same time? If that is the case that didn't work for me. Please see my attachment and the errors.

However, when I added both the One Piece Post SP3 Pack v5.30 and One Piece Repair Addon v5.30 separately I had no issues at all.

@ lapetite66: Why use Nlite? You are posting on a RyanVM board. Addons released here, though some may work with Nlite, are designed for RVMIntegrator. In Integrator, addons and update packs are added in separate fields. I integrated both without errors.

@ lapetite66 and to those complaining
I don't know how I understand this, I can only repair when I have something to repair....
Therefore use "RVM_Integrator_1.6.1b2.1.7" and integrate the pack on a fresh XP sp3 source. Thereafter do the same with the repair.cab and all will be fine.
I have done this for long now (since version 3.8 or so) and I have never had any problems whatsoever
BTW:- some Addons work better when you integrate them one by one not all in a bunch. that way you can easily tell which Addon causes which problem/s and can be corrected or eliminated.

sathanas65 wrote:@ lapetite66: Why use Nlite? You are posting on a RyanVM board. Addons released here, though some may work with Nlite, are designed for RVMIntegrator. In Integrator, addons and update packs are added in separate fields. I integrated both without errors.

sathanas65:

I'm sure I'm not the only person on this board that uses Nlite.

As for my reasons in choosing Nlite, it was because when I first started out trying my hand at slipstreaming I found Nlite to be less confusing than RVMIntegrator. Why haven’t I changed to Ryan’s Integrator? That’s like asking some men why they prefer blondes over brunettes and redheads (personally I think brunettes rock but then I’m a brunette so I’m biased). Basically, it’s just their preference it’s as simple as that. I’m comfortable using Nlite and until that changes that’s what I will continue using.

Thanks,

ianymaty wrote:In the screens the Repair addon is added before the Update Pack

I think you need to change the order...

ianymaty:

I added both at the same exact time. I don't know about anyone else but I don't have any control over which addon is integrated first.

By the way, I did try again and the second time around I integrated the OPPSP3 v5.30 first and then went back the second time and integrated the Repair Addon and it integrated without any issues.

Thanks,

cosy wrote:@ lapetite66 and to those complaining
I don't know how I understand this, I can only repair when I have something to repair....
Therefore use "RVM_Integrator_1.6.1b2.1.7" and integrate the pack on a fresh XP sp3 source. Thereafter do the same with the repair.cab and all will be fine.
I have done this for long now (since version 3.8 or so) and I have never had any problems whatsoever
BTW:- some Addons work better when you integrate them one by one not all in a bunch. that way you can easily tell which Addon causes which problem/s and can be corrected or eliminated.

cosy:

I wasn't complaining. Please see definition of complaint(ing) below.

com•plain [kuhm-pleyn]

1. to express dissatisfaction, pain, uneasiness, censure, resentment, or grief; find fault: He complained constantly about the noise in the corridor.

2. to tell of one's pains, ailments, etc.: to complain of a backache.

3. to make a formal accusation: If you think you've been swindled, complain to the police.

First, I’m very happy that you personally have never had any issues while installing/integrating all the previous versions of OPPSP3 but that isn’t the case for many others, myself included.

Second, I did use a fresh XP source. And I’m also aware that some addons work better when they’re added one by one as opposed to in a group. As you should have seen from my attachment I only added 2 things.

Third, I posted to show how my attempt/experience at adding both the One Piece Post SP3 pack v5.30 and the Repair v5.30 went and the errors that I received when doing so.

Last but not least, I could understand you saying that I was complaining if I had posted something negative and bitched people out but that wasn’t the case here. Correct me if I’m wrong but isn't that the point of the board to post and get feedback whether things are going fine or if you're having issues?

In the future, if you don’t have any helpful ie positive feedback I would appreciate it if you didn’t respond to my posts at all.

lapetite66 wrote:In the future, if you don’t have any helpful ie positive feedback I would appreciate it if you didn’t respond to my posts at all.

Thank you for the quotations from the dictionary which I seem not to have ( I will always call on you for further choice of words ).-needless to say it has no meaning to this thread..?
would be better you try to follow the instructions before you post about problems---
It is self evident here that you never read them correctly.. see nonno fabio's first post ( ....why all of a sudden all is fine?)
...take some time to experiment a few things yourself ( before posting)
sorry if I was to personal
NB:- I would suggest that you stop whining

@lapetite66: I really don't understand your attitude. You have a problem. You are instructed to use RVM rather than Nlite. Rather than attempt this, you choose to refuse to try it, claiming it is not your preference. How can someone like you be assisted? You have your mind made up already. We can't help you.

5eraph wrote:The AddReg sections of time zone updates are usually inaccurate. I always export the "Windows NT\CurrentVersion\Time Zones" key and check the changes there after installing the update on a virgin Windows installation (no updates or update packs).