7 replies to this topic

[Tiribulus]

Hi folks,
Thanks for this great tool btw. I am wondering why after usnig the new updater to create a new x86 xp package it only like 400 megs and there aren't very many updtaes in there. Thanks.
Greg

[ViroMan]

Yours seems rather large. Mine is at 298mb. You should let sweeper run and clean out all the old files that are not supposed to be there. When you run it the first time just hit no when it asks to delete. You can then scroll up the log file and see all the extra files you have without needed to delete any yet.

[Tiribulus]

I did it all from scratch. Started a new package altogether. How come when I deleted the old one it was like 1.2 gigs or something and when I ran AP on a newly loaed XP box there as like 150+ updates, but now it's this small and there's only like 14 or something?

[Whatacrock]

@ Tribulus --- The Windows XP x86 release should be around 275 MB in size and contain 177 updates totalled.
It should contain 366 files in 10 folders.

[_def_x_]

1.2 GB for XP x86 alone is likely not accurate. XP Ptb was about 700+ MB due to some needed extra files. I would guess there were additional Addons in the OP's \modules folder, maybe .NET, DirectX...

Out of curiosity I looked and found some of my old notes and a couple of releases lists. September 2010 (Size=247 MB) & February 2011 (Size=279 MB) - not sure of how many updates.

I did find an old archive of XP x86 for October 2011 - Size=257 MB, ~170 Updates.

[ViroMan]

From the oldest XP script in the server backup.
Jan 12th, 2011 - 287mb 171 updates

[Tiribulus]

First, I do so very much appreciate your guys help. Second, I'm sure you know better than I do, so I muxt have done soething wrong. Ya know what it might have been? I was usnig a different XP disc than usual and I bet it had most of the updates slipstreamed in which would explain why AP only wanted to add like 14 more. Wadda goof. Sorry.

[ViroMan]

Thats definitely a possibility.