Re: XPProEmulation without auto-resolve of dependencies

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

jimt,

I feel your pain. With not enough RAM it is slow and painful to add
components to the huge config.
The very first version of the XPProEmulation I developed on a slow machine
with only 512M of RAM. But even available RAM wasn't the bottleneck there
but the tools which had that awful memory related bugs. The toolkit in
FP2007 is way better now and it just took Microsoft to modify a few lines of
VB code of TD to fix the issue.

Anyway, my point is that adding more RAM to your dev machine will help you
more than anything else to start working with the big XPe projects on a
different level.


I typically disable "CompactPCI Hot Swap Support" stack (most of my targets
didn't support it anyway) so that it doesn't cause many build errors. Look
at the release notes (readme.txt) of the project to see what components are
disabled by default in that config.

Also, if you want to explore dependencies I encourage you to use
DependecyExplorer and ConfigurationExplorer components from XPeTools
packages on www.xpefiles.com website. Those will allow you to explore
components in XPe database or your own config only with some graphic UI and
helpful search filtering functionality built-in.

There are two possible ways on how to approach the "XPe Emulation macro"
idea you are suggesting below:
- the XPProEmulation is a macro listing *all* the software
components from the database. This way the XPProEmulation dhtml page and
script would be amazingly huge and TD would always "die" trying to load the
component's settings.
- XPProEmulation combines certain groups of components and only
shows options per groups. When the actual build starts the component's
script will add all the components from the defined and selected groups.
This approach is already implemented - original XPProEmulation component
from XPeTools packages mentioned above does that. Also, Microsoft's Generic
Driver Support component also implements the group approach.
But please keep in mind that with this "macro component approach"
you will always spend much time trying to add the required components to
your config on the fly. The beauty of the current XPProEmulation project is
that it has already been done once and you can take an advantage of that by
simple loading the project and adding your platform components only.

Please let me know if there is more things you'd like to enhance in the
XPProEmulation project. I am always open to good ideas :-)

Regards,
KM

Hi KM,

Thanks for confirming that dependency auto-resolve can be enabled for
FP2007 toolsets. I only have 700MB of ram; yes it is slow. Yes, I am
using the latest XPProEmulation configuration.

Even so, there are many things to manually resolve. Since I am not
familiar with the modules, it takes a little while to research each one
(xpecmd helps on this to show dependencies). For example "CompactPCI Hot
Swap Support" apparently needs one of these four different computer
components:

"Intel NetStructure ZT5531 System Master Processor Board"
"Force Computers CPCI-730"
"Generic CompactPCI CPU Board"
"Motorola CPV 5300/Motorola 5350"

And each of them pulls in the Standard PC component... but my "tap"
component calls for the "ACPI Multiprocessor PC". Fun fun...

I wonder if there would be any advantages to packaging the XP Pro
emulation package as a macro component instead of it's own project(?).

Thanks,

--
jimt


"KM" <konstmor@xxxxxxxxxxxxxxxx> wrote in message
news:OdG730cOHHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
You can safely turn on Autoresolve dependencies feature and let TD do the
job. ...

Hopefully you're using the latest and greatest version of the
XPProEmulation config posted to www.xpefiles.com (created on RTM'd FP2007
toolkit). Later I will update the readme.txt file on the component posted
there. Thanks for pointing that documentation bug!




.

Relevant Pages

  • Re: XPProEmulation without auto-resolve of dependencies
    ... Regarding the xp pro emul config file, some of the sw components tend to ... With not enough RAM it is slow and painful to add ... The very first version of the XPProEmulation I developed on a slow machine ... I typically disable "CompactPCI Hot Swap Support" stack (most of my ...
    (microsoft.public.windowsxp.embedded)
  • Re: XPProEmulation without auto-resolve of dependencies
    ... Regards the "CompactPCI Hot Swap Support". ... Dependency Auto-resolver in TD and run the dependency check again, ... components in your own config depend on the "CompactPCI Hot Swap Support". ... The very first version of the XPProEmulation I developed on a slow ...
    (microsoft.public.windowsxp.embedded)
  • Re: how to test this piece of C code
    ... RAM vendor. ... probably be, relatively speaking, about the same as a 64GB config is ... 4GB is only two binary orders of magnitude away. ...
    (comp.programming)
  • Re: [PATCH] initramfs: Allow rootfs to use tmpfs instead of ramfs
    ... initrd or initramfs image won't eat up valuable RAM. ... +config RAMFS_ROOTFS ... +#ifdef CONFIG_RAMFS_ROOTFS ...
    (Linux-Kernel)
  • Re: number of components limited in td SP2 ?
    ... the XPProEmulation automated script allows to automaticallysave ... SLX by some interval. ... It rather has to do with VBScript, # of component in Config ...
    (microsoft.public.windowsxp.embedded)