small footprint

  • Thread starter Thread starter Joe
  • Start date Start date
Easy, don't include anything, and it is small :)
That was a fact that is useless.

You can use minlogon based build, and you need to filter out TAP results
before you import them in your build.

Try searching this group on this topic, and also tell us what functionality
(purpose) you need from your device since this will dictate minimum size
that you can achieve.


Best regards,
Slobodan
 
I am creating a application that will talk to the comm
port and network card. I assume i just add the filtered
pumpkin file, add the minlogon, add basic networking and
then check dependancies? any other tips on reducing the
size?

Thanks

Joe
 
Joe,
I am creating a application that will talk to the comm
port and network card. I assume i just add the filtered
pumpkin file, add the minlogon, add basic networking and
then check dependancies? any other tips on reducing the
size?
Click to expand...

If this is only you need (no user interface, etc) than you can write driver
that will use NDIS for access to network adapter and COM you can access
directly (user mode or kernel mode it is irrelevant).
If you need minlogon, then you can use sample from DDK called NDISUIO than
will allow you to access and use network adapter from regular application.

Checking dependencies will import many drivers, services, and files that you
don't need.
But if you need TCP/IP, or other features than you will need to check every
dependency to see if it is required.

This is very rough description, but it should help you.

Best regards,
Slobodan
 
Joe said:
I am creating a application that will talk to the comm
port and network card. I assume i just add the filtered
pumpkin file, add the minlogon, add basic networking and
then check dependancies? any other tips on reducing the
size?
Click to expand...
Once you've got it working, turn off auto-resolve dependencies, print
out a list of all the components, and then diable a few. Save it,
appending a revision number, so you don't lose what you had before. Put
a dot on your print-out next to the ones you've removed. Rebuild, and if
it still works, highlight them pink. If it doesn't, go back to your
previous build, and remove them one at a time, rebuilding each time.
When you find one it breaks without, highlight it green. Lather, rince,
repeat.
Once you've got everything highlighted one way or another (you probably
want to highlight things like your hardware green first, though, but
things like sound you probably don't need, and the generic/headless VGA
driver is presumably smaller than a full driver) you've got it as small
as you're going to get it.
It takes a long time to do, but if size really is an issue, it's worth
doing.
 
Heidi,
Once you've got it working, turn off auto-resolve dependencies, print
out a list of all the components, and then diable a few. Save it,
appending a revision number, so you don't lose what you had before. Put
a dot on your print-out next to the ones you've removed. Rebuild, and if
it still works, highlight them pink. If it doesn't, go back to your
previous build, and remove them one at a time, rebuilding each time.
When you find one it breaks without, highlight it green. Lather, rince,
repeat.
Once you've got everything highlighted one way or another (you probably
want to highlight things like your hardware green first, though, but
things like sound you probably don't need, and the generic/headless VGA
driver is presumably smaller than a full driver) you've got it as small
as you're going to get it.
Click to expand...

This is very colorful :), but only on paper :(
Too bad that this can't be done in TD :(

Slobodan
 
Slobodan Brcin said:
This is very colorful :), but only on paper :(
Too bad that this can't be done in TD :(
Click to expand...
Yes, well, colourful stops me getting lost. You have to remember, you're
coming to this as an expert in things already, I'm coming to this as a
helpdesk monkey who got given the project because someone left
unexpectedly.
 
Back
Top