Re: Printers.slx (www.xpefiles.com)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: KM (konstmor_at_nospam_yahoo.com)
Date: 10/14/04


Date: Thu, 14 Oct 2004 10:32:40 -0700

akusoft,

I am glad those templates helped someone. I can't say I used them myself in a real project (expect maybe the XPProEmulation) :-)

-- 
 Regards,
        KM, BSquare Corp.
> Hello KM,
>
> ok, thanks, I could create a build from printers.slx without a dependency
> check, no error occured. Then from the build I've copied the contents of the
> directory ..\i386\drivers (all printers files) into my other build (main
> project, xppropemulation). On my final image now all printer components are
> available. I've tried many installations and this seems to work. Though this
> is a roundabout method only the result is decisive :-)... Thansk again.
>
> akusoft
>
>
> "KM" wrote:
>
> > akusoft,
> >
> > I guess this question is on my plate.
> >
> > Well.. I have not note here that I haven't seen such problem with Printers.slx.
> > In any case, I would not recommend you to run the Dependency Checker (especially with Auto-Resolve Dependencies On) on this
project.
> > You can build it, though.
> >
> > XPProEmulation, since it is huge, is even harder to run through the Dependency Checker. I can do that here (and I, of course,
have
> > done that million times) but there is a known issue with the RAM usage of the TD. If you project has too many components
included
> > (in my tests it was more than ~2500), TD crashes often with the error you mentioned. Very unstable environment to try with huge
> > projects :-(
> > The time I was playing with all this, I got an impression it is happening because of VB script used by TD. Some limitations on
VB
> > script array size or etc.
> >
> > Anyway.. coming back to Printers. I have actually done that a while ago just for fun. I've got "XPProEmulation&Printers.slx"
project
> > that I have not tested much but it loads in TD fine and I can build it. Let me know if you are interested in this project and I
will
> > upload it to the www.xpefiles.com (be aware it is huge and, of course, even bigger than XPProEmulation :-) ).
> >
> > -- 
> >  Regards,
> >         KM, BSquare Corp.
> >
> >
> > > Hello,
> > >
> > > dependency check of the project file printers.slx fails with:
> > >
> > > Configuration Management Interface (CMI) error
> > > Code = 0x800a00d
> > > Description = Type mismatch
> > >
> > > I'm using Windows XP Prof. and Windows XP Embedded Suite with SP1 and almost
> > > all available critical and important updates installed, 1,3 GB RAM.
> > > By the way I've inexplicable problems by adding all printer components in
> > > another project file (xpproemulation.slx).
> > >
> > > Any ideas?
> >
> >
> >


Relevant Pages

  • Re: Config. Management Interface CMI Error
    ... script code did not show any specific scenerio you could get ... You use XPProEmulation component from XPeTools package. ... trying to add all printer components. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Config. Management Interface CMI Error
    ... My computer has 768 MB RAM. ... > trying to add all printer components. ... > build into your XPProEmulation build. ...
    (microsoft.public.windowsxp.embedded)
  • Re: DependencyExplorer does not show components that need the named component
    ... We know from the XPe Tools release notes that XPe Tools component will list ... XPProEmulation as one of five dependencies. ... So the 'XPe Tools' component will list XPProEmulation as a dependency, ... Enhanced Write Filter API component does depend on the ...
    (microsoft.public.windowsxp.embedded)