Subj : Re: Incremental linker problem
To   : borland.public.cpp.borlandcpp
From : Ed Mulroy
Date : Mon Jun 13 2005 09:35 pm

> Fatal:  Fatal: Block overflow for block 'BrowserCache'

When you get that error it creates a file.  I want to say it is a *.cfg file 
but I'm going from memory and could be wrong about the name.  Do a dir /od 
on the project directory and if you don't find it then in the compiler's BIN 
directory.

In the file is a set of statements of the sort

  something = value

and the browser cache is one of the statements.  The current values used by 
the linker are in there.  Increase the size of the browser cache and, 
assuming that the new size doesn't exceed some absolute limit, the new value 
will be used in the next build.

I am speaking of tlink32.exe.  I do not know if the incremental linker, 
ilink32.exe, does this.

..  Ed

> Alan Jones wrote in message
> news:42ae2316$1@newsgroups.borland.com...
>
>I have added BDE to an existing application.  When I link in
> the idapi32.lib I get the error:
>
> Info :Making...
> Info :Linking E:\RSNetDev\rsnet.exe
> Fatal:  Fatal: Assertion failed: prev->size <= vHeap->maxSize at "LMEM.C",
> line 1630
> Fatal:  Fatal: Assertion failed: free->size <= vHeap->maxSize at "LMEM.C",
> line 1221
> Fatal:  Fatal: Assertion failed: memHndl->size <= vHeap->maxSize at
> "LMEM.C", line 1156
> Fatal:  Fatal: 't4n\idapi32.ASM': ILINK32 does not support segmentation -
> use TLINK32
>
> If I turn off the incremental linker, I then get the error:
>
> Info :Making...
> Info :Linking E:\RSNetDev\rsnet.exe
> Fatal:  Fatal: Block overflow for block 'BrowserCache'
>
> Any ideas?

.