Onepiece XP Post-SP3 AIO Update Pack FINAL
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Well, I think DirectX for Managed Code register itself even if in your integration list there's a .Net AIO svcpack Addon, not only with .Net 1.1 true Addon.
So in that case there would be no need to remove DXM registration with the addon or the Remover.
So in that case there would be no need to remove DXM registration with the addon or the Remover.
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:
I am confused.
So, if I want to integrate Onepiece's 2.2.1 and just .Net 2-3.5
(not 1.1) do I need the Disable_DXM_Registration_AddOn or not?
Can you please reconcile your comment above
with 2 places on the first page:
1. If you don't want to add .NET 1.1 (or a .NET AllInOne addon)...
2. right after all the KBs:
...only if integrated along with Onepiece .NET 1.1 True Addon)
Oh, and thanks to you and Onepiece for all the work!
I am confused.
So, if I want to integrate Onepiece's 2.2.1 and just .Net 2-3.5
(not 1.1) do I need the Disable_DXM_Registration_AddOn or not?
Can you please reconcile your comment above
with 2 places on the first page:
1. If you don't want to add .NET 1.1 (or a .NET AllInOne addon)...
2. right after all the KBs:
...only if integrated along with Onepiece .NET 1.1 True Addon)
Oh, and thanks to you and Onepiece for all the work!
-
- Posts: 2
- Joined: Mon Mar 02, 2009 7:05 pm
I never post ? or comments so please excuse me if this is not the correct location for my question.
I have been using RyanVM's and OnePiece's update packs and such for some time now and appreciate their efforts along with anyone else who makes a contribution or helps the scene.
The problem I have is with Windows Search 4
I take a clean SP3 source and simply update it with OnePiece's update pack, just the root files and the I386 folder. No other folders, nothing extra like reg tweaks, drivers or other appz added. If I do a manual install with this source using the defaults during, everything installs and works fines, including WS4.
If I take this same minimized updated source, add my winnt.sif and perform an unattended install, everything again installs and works fine, except for WS4. The icon in the notification area always says Waiting to receive indexing status, never begins to or complete indexing anything and get to the point where it should say Indexing Complete as it does during a manual install. The Windows Search Results window always says Windows Search isn't running. It will however initiate IE to search the web if I choose, and the old Search Companion option will find files and folders. But the main WS4 does not work or give any results.
I have tried my full winnt.sif file with Indexsrv_system = On under the Components section, but this did not help. So I used the following minimal winnt.sif hoping there would be less in it to cause a conflict, but no better. Is there anything included or excluded in it which would perhaps cause a service to not install or start any differently than during a manual install?
;SetupMgrTag
[Data]
AutoPartition=0
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=Yes
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1
[UserData]
ProductKey=XXXXX-XXXXX-......................
FullName="FullName"
OrgName="Organization"
ComputerName=Unattended
[Networking]
InstallDefaultComponents=Yes
Sorry if this has already been discussed. Thnx for any help.
I have been using RyanVM's and OnePiece's update packs and such for some time now and appreciate their efforts along with anyone else who makes a contribution or helps the scene.
The problem I have is with Windows Search 4
I take a clean SP3 source and simply update it with OnePiece's update pack, just the root files and the I386 folder. No other folders, nothing extra like reg tweaks, drivers or other appz added. If I do a manual install with this source using the defaults during, everything installs and works fines, including WS4.
If I take this same minimized updated source, add my winnt.sif and perform an unattended install, everything again installs and works fine, except for WS4. The icon in the notification area always says Waiting to receive indexing status, never begins to or complete indexing anything and get to the point where it should say Indexing Complete as it does during a manual install. The Windows Search Results window always says Windows Search isn't running. It will however initiate IE to search the web if I choose, and the old Search Companion option will find files and folders. But the main WS4 does not work or give any results.
I have tried my full winnt.sif file with Indexsrv_system = On under the Components section, but this did not help. So I used the following minimal winnt.sif hoping there would be less in it to cause a conflict, but no better. Is there anything included or excluded in it which would perhaps cause a service to not install or start any differently than during a manual install?
;SetupMgrTag
[Data]
AutoPartition=0
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=Yes
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1
[UserData]
ProductKey=XXXXX-XXXXX-......................
FullName="FullName"
OrgName="Organization"
ComputerName=Unattended
[Networking]
InstallDefaultComponents=Yes
Sorry if this has already been discussed. Thnx for any help.
-
- Posts: 7
- Joined: Mon Feb 16, 2009 1:20 am
- Location: Zutah, USA Welcome to the 1960s
I just made a CD using the followin steps:
1. started nLite.
2. told it to get WinXP Pro from my CD drive.
3. did not do any presets
4. for Task Selectin I did Service Pack, Update Packs, Unattended, ISO
5. told it where my local copy of SP3 was.
6. inserted OnePiece_Microsoft.NET_Framework_v1.1.4322.2407_True_AddOn_ENU.CAB
7. inserted OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.1.1_ENU.7z
8. inserted OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (I updated this line).
9. set Unattended Mode to GUI Attended (will customize it later).
10. when it finished integrating everything I told it where to put the ISO.
After making a CD of the ISO I installed and tried MS Update. It listed the following:
High-priority updates (they have Feb 2008 release dates):
- Update for WinXP KB967715
- Update for MS Silverlight KB960353
Optional software updates:
- Update for WinXP KB959772
- Update for Root Certificates
- MS .NET Framework 3.5 SP1 and .NET Framework 3.5 Family Update KB951847 (it's 248MB)
I don't understand why the above .NET one is listed. I thought this AIO had it, although searching thru post #1 I didn't see it or something related to it.
Also, the c:\WINDOWS\Microsoft.NET\Framework directory contains the following:
- 1033 (subdirectory)
- v1.0.3705 (subdirectory)
- v1.1.4322 (subdirectory)
- NETFXSBS10 (file)
- NETFXSBS10.hkf (file)
- sbscmp10.dll (file)
Do I need to insert something else to get the other .NET stuff?
If so the instructions in post #1 should be updated to reflect that.
Love what you've done so far!!!
Cheers,
Bret
1. started nLite.
2. told it to get WinXP Pro from my CD drive.
3. did not do any presets
4. for Task Selectin I did Service Pack, Update Packs, Unattended, ISO
5. told it where my local copy of SP3 was.
6. inserted OnePiece_Microsoft.NET_Framework_v1.1.4322.2407_True_AddOn_ENU.CAB
7. inserted OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.1.1_ENU.7z
8. inserted OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (I updated this line).
9. set Unattended Mode to GUI Attended (will customize it later).
10. when it finished integrating everything I told it where to put the ISO.
After making a CD of the ISO I installed and tried MS Update. It listed the following:
High-priority updates (they have Feb 2008 release dates):
- Update for WinXP KB967715
- Update for MS Silverlight KB960353
Optional software updates:
- Update for WinXP KB959772
- Update for Root Certificates
- MS .NET Framework 3.5 SP1 and .NET Framework 3.5 Family Update KB951847 (it's 248MB)
I don't understand why the above .NET one is listed. I thought this AIO had it, although searching thru post #1 I didn't see it or something related to it.
Also, the c:\WINDOWS\Microsoft.NET\Framework directory contains the following:
- 1033 (subdirectory)
- v1.0.3705 (subdirectory)
- v1.1.4322 (subdirectory)
- NETFXSBS10 (file)
- NETFXSBS10.hkf (file)
- sbscmp10.dll (file)
Do I need to insert something else to get the other .NET stuff?
If so the instructions in post #1 should be updated to reflect that.
Love what you've done so far!!!
Cheers,
Bret
Last edited by bretmaverick999 on Tue Mar 03, 2009 4:35 pm, edited 2 times in total.
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
@vmor: sorry, I've forgotten to modify changelog line. DirectX for Managed Code are automatically registered only if you integrate a .Net 1.1 addon, alone or inside an AIO .Net addon.
If you use an addon which doesn't include .NET 1.1, and you want an unattended XP installation, you should remove DXM using the addon or the remover.
@cliff claven: adding WDS in Update Pack hasn't been a good idea... Your Winnt.sif don't have any problem about services. I've just tried an integration like yours with this winnt.sif:
and I got no such issue.
Have you used Nlite or RVMi?
@bretmaverick999:
I think .net1.1 is already updated but needs again a few registry lines. However the real update is not so big.
P.S.
If you use an addon which doesn't include .NET 1.1, and you want an unattended XP installation, you should remove DXM using the addon or the remover.
@cliff claven: adding WDS in Update Pack hasn't been a good idea... Your Winnt.sif don't have any problem about services. I've just tried an integration like yours with this winnt.sif:
Code: Select all
[Data]
Autopartition=0
MsDosInitiated=0
UnattendedInstall="Yes"
[Unattended]
UnattendMode=DefaultHide
UnattendSwitch="No"
OemPreinstall="Yes"
OemSkipEula="Yes"
FileSystem=*
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
NonDriverSigningPolicy=Ignore
[SystemRestore]
[GuiUnattended]
AdminPassword=*
TimeZone=110
OEMSkipRegional=1
OemSkipWelcome=1
[Components]
[UserData]
ProductKey="xxxxxxxxxxxxxxxxxxx"
ComputerName=ONEPIECE-PC
FullName="OnePiece"
OrgName="OnePiece Organization"
[RegionalSettings]
Language= "0409"
[Networking]
InstallDefaultComponents="Yes"
[Identification]
JoinWorkgroup="WorkGroup"
Have you used Nlite or RVMi?
@bretmaverick999:
I think .net1.1 is already updated but needs again a few registry lines. However the real update is not so big.
P.S.
that is not an addon, it's a tool! Read better first post8. inserted customizes_onepiece_update_pack.exe
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
-
- Posts: 7
- Joined: Mon Feb 16, 2009 1:20 am
- Location: Zutah, USA Welcome to the 1960s
Sorry nonno, it was late when I wrote up my post, and I goofed. It was the second time I wrote my problem up. First time my login must have timed out as when I clicked Submit it asked me to login, and after login my write up was gone (always control-A control-C before submitting).
What my #8 above used to say:
What my #8 above used to say:
What my #8 above now says (I've edited it):8. inserted customizes_onepiece_update_pack.exe
Still wondering if anybody has tried this FANTASTIC Update Pack lately and then did a MS Update and had it report the .NET 3.5 update.8. OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z
-
- Posts: 2
- Joined: Mon Mar 02, 2009 7:05 pm
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Pack updated.
Onepiece has decided to remove the... Remover and to replace it with single disabling addon: they're successfully tested with RVMi 1.6 (but not with Nlite).
Furthermore, he decided that IE7 and WMP11 are mandatory for his pack, so no disabling addons: you can always unistall them from WCW or use a DIY way to remove it. .NET 1.1 is back too, but you can disable it
By the way, I remember first commandment:

Onepiece has decided to remove the... Remover and to replace it with single disabling addon: they're successfully tested with RVMi 1.6 (but not with Nlite).
Furthermore, he decided that IE7 and WMP11 are mandatory for his pack, so no disabling addons: you can always unistall them from WCW or use a DIY way to remove it. .NET 1.1 is back too, but you can disable it
By the way, I remember first commandment:
If you prefer a different configuration of Onepiece AIO Update Pack I suggest you to use RyanVM Update Pack with your preferred addons and you'll get your own XP disc without the need to remove anything.

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
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
because it's the only .Net which can be directly integrated.
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
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Have you used Nlite?
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
-
- Posts: 7
- Joined: Mon Feb 16, 2009 1:20 am
- Location: Zutah, USA Welcome to the 1960s
@Salid
I've made two different CDs using the 2.2.0 Update Pack and did not have any problems.
Here is how I did the first one:
1. started nLite (version 1491)
2. told it to get WinXP Pro from my CD drive.
3. did not do any presets
4. for Task Selectin I did Service Pack, Update Packs, Remove Components, Unattended, ISO
5. told it where my local copy of SP3 was.
6. inserted OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.1.1_ENU.7z
7. inserted OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (I updated this line).
8. set Unattended Mode to GUI Attended (will customize it later).
9. when it finished integrating everything I told it where to put the ISO.
It installed fine.
MS Updated listed the 248MB .NET updated. So I did a second build like this (added steps 8-9):
1. started nLite.
2. told it to get WinXP Pro from my CD drive.
3. did not do any presets
4. for Task Selectin I did Service Pack, Update Packs, Unattended, ISO
5. told it where my local copy of SP3 was.
6. inserted OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.1.1_ENU.7z
7. inserted OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (I updated this line).
8. inserted Stimpy's "DotNetFx 3.5SP1 3-in-1 Silent Addon" which I got from here http://www.ryanvm.net/forum/viewtopic.p ... sc&start=0. I also want to try JD976's .NET package as they are both supposed to work.
9. I removed about 60 items. Adding .NET results in an ISO that is about 750MB, and it woill not fit on a CD. By removing those 60 items, even with the .NET addon, my ISO is 552MB.
10. set Unattended Mode to GUI Attended (will customize it later).
11. when it finished integrating everything I told it where to put the ISO.
It installed fine, MS Updated listed ZERO updates.
Next try will be to insert my drivers, make the Unattended install changes, and my tweaks.
A suggestion, start with the absolute minimum first (XP, XP3, this Update Pack). Is that what you tried?
I've made two different CDs using the 2.2.0 Update Pack and did not have any problems.
Here is how I did the first one:
1. started nLite (version 1491)
2. told it to get WinXP Pro from my CD drive.
3. did not do any presets
4. for Task Selectin I did Service Pack, Update Packs, Remove Components, Unattended, ISO
5. told it where my local copy of SP3 was.
6. inserted OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.1.1_ENU.7z
7. inserted OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (I updated this line).
8. set Unattended Mode to GUI Attended (will customize it later).
9. when it finished integrating everything I told it where to put the ISO.
It installed fine.
MS Updated listed the 248MB .NET updated. So I did a second build like this (added steps 8-9):
1. started nLite.
2. told it to get WinXP Pro from my CD drive.
3. did not do any presets
4. for Task Selectin I did Service Pack, Update Packs, Unattended, ISO
5. told it where my local copy of SP3 was.
6. inserted OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.1.1_ENU.7z
7. inserted OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (I updated this line).
8. inserted Stimpy's "DotNetFx 3.5SP1 3-in-1 Silent Addon" which I got from here http://www.ryanvm.net/forum/viewtopic.p ... sc&start=0. I also want to try JD976's .NET package as they are both supposed to work.
9. I removed about 60 items. Adding .NET results in an ISO that is about 750MB, and it woill not fit on a CD. By removing those 60 items, even with the .NET addon, my ISO is 552MB.
10. set Unattended Mode to GUI Attended (will customize it later).
11. when it finished integrating everything I told it where to put the ISO.
It installed fine, MS Updated listed ZERO updates.
Next try will be to insert my drivers, make the Unattended install changes, and my tweaks.
A suggestion, start with the absolute minimum first (XP, XP3, this Update Pack). Is that what you tried?
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
The removal addons must be used in the RVMi session, not in the Nlite one.Salad wrote:Yes
Here is my order
RVM Integrator
nLite
It's so?
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
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
@nonno fabio
If use "Remove_Windows_Search_AddOn.7z" then i get popups in nLite that doesn't make sens but installtion works.
If use "Remove_Windows_Search_AddOn.7z" then i get popups in nLite that doesn't make sens but installtion works.
Last edited by Outbreaker on Fri Mar 06, 2009 2:58 am, edited 2 times in total.
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Re: Onepiece XP Post-SP3 AIO Update Pack v2.2.0-090304
nonno fabio wrote: NB these removal addons are tested with RVM Integrator 1.6 only! It's possible that they don't work with Nlite
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
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
Re: Onepiece XP Post-SP3 AIO Update Pack v2.2.0-090304
nonno fabio, I just wanted to thank you for all the effort you put into this package!
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
@salad: if so, it's the very first time RVMi fails with the removal addon. Please try using your clean XP source only with Update Pack and .Net removal addon along with RVMi. If it doesn't work again, then report. thanks
@Outbreaker: it's not suggested, however open the WDS removal addon and execute manually the instruction inside.
@amerrykan: many thanks from me and Onepiece.
@Outbreaker: it's not suggested, however open the WDS removal addon and execute manually the instruction inside.
@amerrykan: many thanks from me and Onepiece.
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
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
anyone else has got Salad issue?
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
-
- Posts: 2
- Joined: Tue Apr 29, 2008 5:25 am
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
@Salad & masterpong: RVM Integrator can manage no more than about 600 reglines in txtsetup.sif/dosnet.inf640 lines in dosnet.inf and about 750 in txtsetup.sif and Onepiece's XP update pack only has already 552 lines. I hope it isn't that but if you could try to redo with RVMi a new integration on a clean XP SP3 source only with UpdatePack, then before making the iso another integration session on the same source adding only .Net removal addon. When done, create the iso and install on a VM. thanks.
EDIT: clarified exact noticed lines limit
EDIT: clarified exact noticed lines limit
Last edited by nonno fabio on Tue Mar 10, 2009 10:06 am, edited 1 time in total.
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
i think that's it.nonno fabio wrote:RVM Integrator can manage no more than about 600 reglines in txtsetup.sif/dosnet.inf .
when i tried to use Wdsearch and MSslight remove addon i got the same error for the MSSLIGHT.inf but if i only use one of them it works just fine.
hope this helps you sort the problem
Post SP3 XP Update
Hello,
I'm new here & frankly a bit out of my depth.
I just want to be in a position to re-format XP Pro with all updates & service releases in a one hit install, preferably unattended.
It won't be long before MS will take down the various updates saying they no longer support etc.
I don't much care, but would prefer to do such an install from a HD file although one or more CD's (DVD'd) would be OK.
A problem I have noticed recently is that my original legal MS discs for both XP Pro & Office 2000 no longer work well, deterioration maybe??
Anyway a HD file is more reliable especially if its an external HD right.
My question now is does this "post SP3 update" meet this requirement, & if so how do you get the HD file installed in such a way that a reformat from that file in the future would be possible.
I know this is second nature to most of you but the situation applies to average guys just as much agreed.
Rgds to all,
Peter O
I'm new here & frankly a bit out of my depth.
I just want to be in a position to re-format XP Pro with all updates & service releases in a one hit install, preferably unattended.
It won't be long before MS will take down the various updates saying they no longer support etc.
I don't much care, but would prefer to do such an install from a HD file although one or more CD's (DVD'd) would be OK.
A problem I have noticed recently is that my original legal MS discs for both XP Pro & Office 2000 no longer work well, deterioration maybe??
Anyway a HD file is more reliable especially if its an external HD right.
My question now is does this "post SP3 update" meet this requirement, & if so how do you get the HD file installed in such a way that a reformat from that file in the future would be possible.
I know this is second nature to most of you but the situation applies to average guys just as much agreed.
Rgds to all,
Peter O
Works fine now though it's a bit inconvenient.nonno fabio wrote:@Salad & masterpong: RVM Integrator can manage no more than about 600 reglines in txtsetup.sif/dosnet.inf and Onepiece's XP update pack only has already 552 lines. I hope it isn't that but if you could try to redo with RVMi a new integration on a clean XP SP3 source only with UpdatePack, then before making the iso another integration session on the same source adding only .Net removal addon. When done, create the iso and install on a VM. thanks.
Thanks!

- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
2.2.1 is out
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
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Only the main pack: removal addons wouldn't need to be updated.
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
Tried this last night and it installs fine with two issues - no IE icon created on the start menu. Or rather the icon is not the correct one and selecting it just brings up the IE properties menu box. Selecting windows update from the start menu does start IE so it is integrated, just no icon.
Second issue - can't create the quick start toolbar.
Got the same behaviour 3 times in a row with just the new pack and a clean XP CD.
Going to drop back 3 versions which does work correctly, quicker than trying to sort the problems out.
This looks exactly the same as the issues reported with an earlier pack.
Second issue - can't create the quick start toolbar.
Got the same behaviour 3 times in a row with just the new pack and a clean XP CD.
Going to drop back 3 versions which does work correctly, quicker than trying to sort the problems out.
This looks exactly the same as the issues reported with an earlier pack.
just finished testing and i cant say i had any problems. everything A ok.all ie7 shortcuts working. dunno about the quickstart thingy tho.
EDIT:
i commented out desktop search and wga.
EDIT:
i commented out desktop search and wga.
Last edited by bober101 on Thu Mar 12, 2009 10:34 pm, edited 1 time in total.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
Mandarin wrote:Tried this last night and it installs fine with two issues - no IE icon created on the start menu. Or rather the icon is not the correct one and selecting it just brings up the IE properties menu box. Selecting windows update from the start menu does start IE so it is integrated, just no icon.
Second issue - can't create the quick start toolbar.
Got the same behaviour 3 times in a row with just the new pack and a clean XP CD.
Going to drop back 3 versions which does work correctly, quicker than trying to sort the problems out.
This looks exactly the same as the issues reported with an earlier pack.

me too
what other addons r u guys using?
also what version of the rvmi r u using?
also what version of the rvmi r u using?
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
@mandarin & geforce:
This happens when an unknown addon corrupts the .inf file: try a RVMIntegration on a XP SP3 fresh source with UpdatePack only and you won't see those issues
This happens when an unknown addon corrupts the .inf file: try a RVMIntegration on a XP SP3 fresh source with UpdatePack only and you won't see those issues
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. did you do something when you have integrated ie7 and wmp in your aio to make it compatible with optional components? everyone has a problem integrating other addons which breaks wmp and ie7 install. I tried your msxml4 install but ive finally done a clean svpack method- (same problem with my addon ie7 and wmp)
Dear all,
i was having same problem as geforce & Mandarin but at last i managed it.
the order is
1) XP SP2
2) SP3 integration (using command line)
3) OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.2.1_ENU 11-03-2009.7z (RMVI)
4) OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (RMVI)
5) Stimpy_JD976_DotNetFx_3in1_Addon_v2.2.7z (RMVI)
6) Drivers + Tweaks (nLite)
(only one integration at a time)
and after installation it says 0 update on MS site.
i was having same problem as geforce & Mandarin but at last i managed it.
the order is
1) XP SP2
2) SP3 integration (using command line)
3) OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.2.1_ENU 11-03-2009.7z (RMVI)
4) OnePiece_Repair_IE_Cosmetic_Problems_AddOn.7z (RMVI)
5) Stimpy_JD976_DotNetFx_3in1_Addon_v2.2.7z (RMVI)
6) Drivers + Tweaks (nLite)
(only one integration at a time)
and after installation it says 0 update on MS site.
u manualy slipped it (sp3) and it worked fine?
edit: nvm using rvmi and an updpack will fix the WBEM problems.
edit: nvm using rvmi and an updpack will fix the WBEM problems.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources