Updating from SP1 to SP2 the Target Grows UP!!!!

[Jordi Giró \(ALVIC\)]

I have a XPe image with SP1 to fit in a 256 Mb CF and it size is about 110
Mb

when I update to SP2 and upgrade the project, target designer installs new
"required" components and the size of the XPe image grows up to 270 Mb!!!!!

Anyone knows how can I update to Service Pack 2 replacing only the
components that I use with SP1 project?

 

[Richard]

I haven't done it, but there were several posts in the NG stating that the
new fiewall is huge. I beleive they stated it had to be disabled. Check
the NG for details. Firewall had many more dependencies to satisfy.

http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded?hl=e
n&lr=&ie=UTF-8&oe=UTF-8

 

[KM]

Read this link: http://blogs.msdn.com/harshs/archive/2004/10/12/241426.aspx

Reading the upgrading only the components that you already have in SP1 configuration to SP2. This is risky and you will have to make
sure to test your final image a lot.
Anyway, disable autoresolve dependencies and change the cmiServicePack level property for each component you want to upgrade. Then
upgrade it to a new revision.
Similar things but with more automation you can do with SmartUpgrade component from XPeTools package on www.xpefiles.com.

KM

 

[Lucvdv]

I have a XPe image with SP1 to fit in a 256 Mb CF and it size is about 110
Mb

when I update to SP2 and upgrade the project, target designer installs new
"required" components and the size of the XPe image grows up to 270 Mb!!!!!

Anyone knows how can I update to Service Pack 2 replacing only the
components that I use with SP1 project?

Target size isn't much of a problem here because it runs from a 1GB
partition on harddisk, but what disturbs me are the memory requirements.

I'm working on an upgrade for an existing device that runs fine in 128MB of
RAM with XPe RTM (SP Zero).

The SP2 version doesn't get through FBA without adding more memory.

It fails in the COM registration with a "contact Microsoft" message, but
increasing the memory to 256MB fixes it.
Giving it a 256MB pagefile on a separate partition doesn't help, so it
looks like it crashes before it has created the pagefile, or else it needs
it to be on the boot partition.

I had already noticed before that SP1 has higher memory requirements than
RTM: there I got 'system is running low on virtual memory' popups in the
finished target (post-FBA, no pagefile, disk EWF), but that version was
never deployed because the upgrade wasn't really necessary (no network, so
the security fixes aren't that important, and it ran fine for the rest).

This time the main application is being upgraded, so the SP2 version will
be deployed.

 

[Jordi Giró \(ALVIC\)]

This machine has 128 Mb of RAM and runs Ok with SP2

Uses 52.9 Mb of RAM without virtual memory (disabled) with 4 programs
running (3 non visual) and runs fine with a Industrial PC (Celeron 400) with
128 Mb RAM and 256 Mb Compact Flash. (without hard disk)

 

[Lucvdv]

This machine has 128 Mb of RAM and runs Ok with SP2

Uses 52.9 Mb of RAM without virtual memory (disabled) with 4 programs
running (3 non visual) and runs fine with a Industrial PC (Celeron 400) with
128 Mb RAM and 256 Mb Compact Flash. (without hard disk)

This target contains the .Net framework and DirectX 9.
Because I had very little time to prepare and test it and because disk
space is no issue, I didn't pay as much attention to avoiding unneeded
components as I would normally have.

It now uses about 60MB after FBA, without the main application (replaced by
a cmd shell and task manager), but FBA fails if there is only 128M present.

I wish there was a way to check memory use while FBA is running.


Memory use for the system alone was 45-50MB in the SP0 version.
The main app is rather hungry, and brought the total up to 80.
I had expected more because of the shortcuts I took, but not that I'd have
to add memory.