Re: netstat dependencies

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

From: Brad Combs (brad_at_imagotechnologies.no.spam.com)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 14:04:01 -0500

Roger,

I think Robert is giving you an option as a quick test for functionality,
not a production fix. If simply copying the exe from an XP Pro machine works
on your runtime, then take the next step.

Locate the exe in your main repository for XPe. Copy it to a new folder, and
make a component that has this file, and it's destination location
specified. Add this component to your slx in TD. All set!

HTH, 

-- 
Brad Combs
Imago Technologies, LLC
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Roger Levy" <rhl@i3e.org> wrote in message
news:4044BB55.6D6B69C9@i3e.org...
> Can anyone tell me if such a practice is consistent with the licensing
> agreement?
>
> Roger
>
> Robert wrote:
> >
> > Roger,
> >
> >    Sorry, I misunderstood your post.  Have you tried just
> > pulling the netstat.exe from the system32 directory off an
> > XP Pro Box?  This should work for you.
> >
> > Robert
> >
> > >-----Original Message-----
> > >Robert,
> > >I think my message indicated that I didn't have trouble
> > finding netstat
> > >(although it wasn't in the TCP/IP Utilities macro
> > component as advertised).  The
> > >problem I have is in understanding why adding it to my
> > configuration results in
> > >a 40MByte increase in size when netstat is a text based,
> > command line utility.
> > >I'd like netstat but not at a cost of 40Mbytes and 60
> > other components including
> > >IE pulled in during depedency resolution.
> > >
> > >Roger

Relevant Pages