I just received this message. Whats going on with the list?
I am on the list from three different accounts, and get different messages
in all of them at different times.
This one is a month old, and has only just arrived. But I have it at the
other accounts.
Dave.
-----Original Message-----
From: Dave [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 7 June 2001 08:25
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Exe Size
Have a look at a program called UPX - http://upx.sourceforge.net/ I use this
to drop the size of an exe before distribution, and have had no problems
with it as yet. I tend to get 50%ish drop in size.
Dave.
----- Original Message -----
From: "Steve Peacocke" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Thursday, June 07, 2001 7:58 AM
Subject: Re: [DUG]: Exe Size
> Thanks to all who replied, we have all (finally) found an answer to this
> very frustrating question.
>
> Win 9x does indeed, despite it's marketing blurb, have limits with the
size
> of the EXE and we exceeded this.
>
> The problem occurs when we start the application of just over 11 megs. The
> application immediately, without running ANY code whatsoever, halts with a
> windows message relating that it has insufficient resources and to close
> some programs.
>
> Watching the memory meter shows no change in the memory used.
>
> Running Memory Sleuth over the application on another computer (win2000)
> shows that it only takes a few hundred K of memory at the main menu and up
> to 3.5 megs at the most memory hungry and largest piece in the program.
>
> This lead us all to believe that Win(lose)dows simply said "oooh - your
too
> big and thinking that hard hurts me, go away!".
>
> We were then faced with the choice of splitting the the app into smaller
> chunks using either several exes or DLLs. In mid season with still a few
> million trays to pack in the next few weeks, this seemed a bit drastic.
>
> We finally solved the problem by compiling with runtime packages. This
> dropped the exe to about 9.5 megs but left us with the problem of now
> ensuring that all users also have the BPL files that we excluded.
>
> An interesting side to this is that, without changing code, we have
> decreased the EXE but drastically increased the total size of the
> distributables in that there is about 4.5 megs of bpl files needed giving
a
> total of around 14 megs instead of the original 11.2 megs.
>
> Thanks for everyone's help in this. It was a doozy that had 5 us running
in
> circles for a couple of days, interrupted only by telephone calls from
> pannicky users and trips to the coffee pot.
>
> Steve
>
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
