Re: writing overlays with VB6
- From: Bob O`Bob <filterbob@xxxxxxxxxxxxxxx>
- Date: Sun, 18 Jun 2006 08:41:03 -0700
Claus Igeltupf wrote:
It's not a matter of pure code size neither a matter of data size. Windows uses virtual memory since 1.0 so memory size isn't the question at all. But there have been aditional limits in windows like system resources which disallowed programs to grow up and use all of the available virtual memory. Even in XP limits still exists (but aren't well known to the users). Avoiding such limits before starting a new project seems to be a good strategy in my opinion.
You're hung up on some particular words.
The fact that they have little to do with how Windows works now
doesn't seem to be getting through to you.
And you appear not to be willing to actually discover where and how
your existing app is *really* running into difficulty.
Learn to work WITH your tools, not AGAINST them.
Find out what boundaries you are ACTUALLY running into, else you
will put large efforts into "optimizing" preconceived things
only to find they confer no actual improvement whatsoever.
Bob
--
some great improvement for horseshoes wouldn't help you win a NASCAR race
.
- Follow-Ups:
- Re: writing overlays with VB6
- From: Claus Igeltupf
- Re: writing overlays with VB6
- References:
- writing overlays with VB6
- From: Claus Igeltupf
- Re: writing overlays with VB6
- From: Thorsten Albers
- Re: writing overlays with VB6
- From: Schmidt
- Re: writing overlays with VB6
- From: Thorsten Albers
- Re: writing overlays with VB6
- From: Claus Igeltupf
- Re: writing overlays with VB6
- From: Thorsten Albers
- Re: writing overlays with VB6
- From: Claus Igeltupf
- Re: writing overlays with VB6
- From: Thorsten Albers
- Re: writing overlays with VB6
- From: Claus Igeltupf
- writing overlays with VB6
- Prev by Date: Re: writing overlays with VB6
- Next by Date: Re: writing overlays with VB6
- Previous by thread: Re: writing overlays with VB6
- Next by thread: Re: writing overlays with VB6
- Index(es):
Relevant Pages
|
Loading