SB> code that is net  obsolutely required. My point was that you could make
 SB> straight API calls or  pull into your source only what you really
 SB> needed and probably get it even  tighter. 
 
Hmm...perhaps...then you look at other examples...there's always the guy
that optimizes until he's blue in the face, compiles, and it's the
same size or larger than the "loose" code.  :(
 
I usually don't write Windows programs.  I have one that I wrote
that reboots Windows 95 through the API (yeah, I know, pretty
unoriginal but it works), and no matter what I took out or left
in the uses clause it was still the same size.
 
My point being that perhaps sometimes it's better to devote time to
developing the substance of a program than endlessly searching for the
one-byte wonder.  Obviously you don't want to be irresponsible about
the code you put out and leave it grossly unoptimized, though.  That's
not nice either.  I think there's a happy balance.
 
With my DOS programs, I'd compile it without debug information and then
run an executable compressor (usually lzexe) on it.  That would not
slow it down too much.  I don't know of anything comparable for
Windows platforms, though...
 
Speaking of Windows programs, my reboot program is of course written
in Delphi -- can't justify distributing the entire VB 4.0 runtime
for a little reboot program.  When it runs, a form pops up temporarily.
Do you (or anyone else) know of a method that this form might be made
to not pop up?  I set the form properties so it's as small as it can
go, and I'm sure there's probably some API call I'm missing.  I just
am wondering if there's another way besides cut'n'paste from an API
reference.
 
... rtfm (314) 843-1855  
***
 þ Blue Wave/QWK v2.12 þ
--- GEcho/32 1.20/Pro
---------------