Re: XPe SP2 bloat
- From: Larry Waibel <lwaibel@xxxxxxxxxxxxxxx>
- Date: Thu, 09 Jun 2005 08:05:41 PDT
My point is that I have 41 additional components (if you want I will list them
in another post) that weren't necessary before and that I appear to have no
choice about unless I go back and start my configuration over. Why should it
be our responsibility to search all around archives and start from scratch just
to get back to the point we were at before the upgrade? I don't mind having to
search, etc. to add new features but I should be able to make that choice.
In article <e05A#KQbFHA.2900@xxxxxxxxxxxxxxxxxxxx>, Andy Allred [MS] wrote:
> From: "Andy Allred [MS]" <andyall@xxxxxxxxxxxxxxxxxxxx>
> Subject: Re: XPe SP2 bloat
> Date: Thu, 9 Jun 2005 07:51:37 -0700
> Newsgroups: microsoft.public.windowsxp.embedded
>
> Roger, checking the archives will answer some of your questions. I'm not
> going to get into a debate with folks that don't read the docs and can't
> supply specific information, general complaints don't enable me to provide
> you answers or to target specific features for more work, if you're just
> wanting to blow off steam then please say this so I can invest my time more
> efficiently.
>
> An example of a discoverable issue of yours is that a 16MB swap file is not
> needed. What's needed is at least a Maximum 2 MB swap file for the perf
> counters, and that is a *bug* not a functional requirement per the feature
> specification so the Perf counters folks are fixing that bug in a future
> release.
>
> As for 'unwinding the dependencies', let's be clear that with very few
> exceptions (like Minlogon and NTLDR), XPe uses the same binaries as XP Pro.
> This means that if to effect security changes in Pro SP2 a feature needs to
> introduce a dependency that was not there for SP1 or Gold, then we also have
> the same dependency. Where the embedded team can come in and assist is
> identifying *optional* dependency feature teams have introduced and expose
> those in the configurable UI of the component. Simply unchecking the box in
> the config ui for those can have dramatic effect on the footprint (and
> behavior) of the feature. We also monitor features that comprise the main
> features of the most popular device categories and negotiate with those
> feature teams to think of the embedded customer's requirements when they are
> making functional changes.
>
> I encourage you to read the documentation and peruse the newsgroup archives
> and then ask specific questions (like the perf counters deal) if you
> honestly feel a dependency is weird. Otherwise there's not much I can do to
> answer general questions like 'my footprint is too big' without details.
> With those details you can now search the archives, if the question isn't
> answered there then ask it here or file a bug via the WECRT @Microsoft.com
> alias so I know someone is actually interested in using Telnet Server for
> instance in a minimal system.
>
> I'm not going to continue this thread however feel free to pile on here,
> I'll monitor it but not respond. But if you have specifics then please start
> new threads or file a bug, it goes right to my inbox.
>
> Thanks
> Andy
>
> --
> Embedded team blog: http://blogs.msdn.com/embedded/
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Roger H. Levy" <rhl@xxxxxxx> wrote in message
> news:uG4OAxPbFHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
> >I think Andy has dodged the issue. My SP1 image was about the same size as
> > Larry's (50-60M, which I think is huge relative to what I need it to do)
> > but
> > even after removing the firewall from SP2, the image grew by 20-25M. The
> > real issue, I think, is the terrible job TD does in resolving
> > dependencies.
> > My image is bloated because it contains many DLLs and components that have
> > nothing to do with my application and which will never be used but they
> > are
> > pulled in because there was inadequate effort by MS in unwinding the
> > dependencies. If you haven't seen this, try taking a small minlogin,
> > command shell system and then include a telnet server and watch your image
> > size nearly double. Another perverse example is the need for me to have a
> > 16M swap file because performance statistics depend on it. This got more
> > bizarre when I moved to ram-reg ewf on flash and found out that it's
> > unhealthy to have a swap file. What am I supposed to do with those two
> > facts?
> >
> > RL
> >
> > "Andy Allred [MS]" <andyall@xxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:#0KYK$KbFHA.3332@xxxxxxxxxxxxxxxxxxxxxxx
> >> Did you read the relnotes or the documentation for SP2 or search the
> >> newsgroup archives on this subject?
> >>
> >> Here's one example for you:
> >> Since (for your device's protection) more features depend on the firewall
> > in
> >> SP2 you're footprint will naturally go up , if you choose to attempt to
> >> *not* bring in the firewall in order to reduce your footprint, then read
> >> this blog post after checking out the relnotes and the SP2 help:
> >> http://blogs.msdn.com/harshs/archive/2004/10/12/241426.aspx
> >>
> >> --
> >> Andy
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >> ------------------
> >> "Larry Waibel" <lwaibel@xxxxxxxxxxxxxxx> wrote in message
> >> news:VA.00000299.01c8b20d@xxxxxxxxxxxxxxxxxx
> >> >I just installed the SP2 update and updated my target designer
> >> >configuration.
> >> > It's now over TWICE the size. It added all sorts of components that I
> >> > don't
> >> > need/want such as disk indexing services, distributed transaction
> >> > coordinator, and a bunch of other stuff that I'm not sure what it is
> >> > but
> >> > didn't need it before. How do I get a reasonable sized (60MB or so)
> > image
> >> > back again?
> >> >
> >>
> >>
> >
> >
>
.
- References:
- XPe SP2 bloat
- From: Larry Waibel
- Re: XPe SP2 bloat
- From: Andy Allred [MS]
- Re: XPe SP2 bloat
- From: Roger H. Levy
- Re: XPe SP2 bloat
- From: Andy Allred [MS]
- XPe SP2 bloat
- Prev by Date: Re: XPe SP2 bloat
- Next by Date: Problems installing hardwareless driver
- Previous by thread: Re: XPe SP2 bloat
- Next by thread: Re: XPe SP2 bloat
- Index(es):
Relevant Pages
|