On 17 Feb 2002 17:39:04 GMT [EMAIL PROTECTED] (Henry Sobotka) wrote:
> Mikus Grinbergs wrote:
> >
> > My time to load 0.9.8 VACPP - 30 sec
> >
> > My time to load 0.9.8 EMX - 25 sec
>
> If the .xpt files in the vacpp bin/components aren't linked, that could
> well account for the difference.
>
> If they aren't, you can take xpt_link.exe from the emx build and in the
> vacpp /bin run:
>
> xpt_link warpzilla.xpt components/*.xpt
>
> (To do this with the vacpp xpt_link.exe, you have to feed it a list of
> the *.xpt files in components because it doesn't support wildcards.)
>
> If the command succeeds, you'll have a 300K+ warpzilla.xpt in /bin. You
> can then remove all the *.xpt files in bin/components and move
> warpzilla.xpt (you can actually name it anything you want) into
> bin/components. Delete components/xpti.dat and, to be safe,
> component.reg in /bin, Relaunch to regenerate them, and then time a
> vacpp launch for a more accurate comparison.
You are right.
After doing the above, my time to load 0.9.8 VACPP is 25 sec
Thanks, mikus
p.s. The newly-generated bin\component.reg is identical to
the one in place before the *.xpt files were "compacted"
