On Thu, 19 Jun 2008 09:53:48 +0200, "Luke" <luke987_1@[EMAIL PROTECTED]
> wrote:
>
>"Michael Mattias" <mmattias@[EMAIL PROTECTED]
> skrev i melding
>news:j2d6k.8722$jI5.8581@[EMAIL PROTECTED]
>> Strangely enough, the error message is exactly correct: you are trying
to
>> allocate too much memory. Your available physical must now be such that
>> the total requirements for your program when you try to allocate all of
>> that 'available physical' exceed your 2 Gb user limit per process.
>
>I'm not sure I understand you correctly. The help file says, under
Features
>of PBCC, "Use of all available memory(up to 2GB) for arrays and strings"
>In my case I have 1.3GB memory available.And there was no problem with
1GB
>memory installed.
While I agree with Michael's answer to you, I have a suggestion for a
possible generic approach. Why don't you use a binary kind of scan to
find out how much memory you can allocate? Something like:
Can I get 2Gb?
If no, can I get 1Gb?
If yes, can I get 1.5Gb?
If yes, can I get 1.75Gb?
if no, can I get 1.625Gb?
Etcetera until the delta amount is too small to bother.
Also, maybe you do have something like 1.2Gb free memory, but it could
be split up so the largest amount you can actually allocate may be
just half of it (depending on how well Windows manages memory
allocation).
--
Peter Manders.
I like to sing to the songs on the radio in my car. When you go into a
tunnel, it's hard to come out on the right note. Actually, the news is
more difficult.
|
