BorlandTalk.com

Ed Mulroy [TeamB] · Guest

One man who had that pair of errors got rid of them by rebootong Win98. His
guess as to why was that Win98 doesn't do a very good job of handling memory
and wouldn't give the linker as much memory as it wanted.

While I agree with that, if you are calling the linker yourself I also think
this might help. Add the option /Gn to the ilink32 command line to suppress
the generation of state files (*.il? files).

.. Ed

Cactus · Guest

Ed Mulroy [TeamB] · Guest

FYI: 128 M is not a lot of memory. Win98 itself uses more than half of
that (Win95 with IE5 takes >80M without MPlayer and both Win98 and IE6 are
bigger). The 64M free that you speak of is what is free from the total of
memory and virtual memory on the disk. On my 128M Win98 machine I set up a
128M fixed swap file to get more stability.

Memory has gotten cheap these days. If I were still running Win98 I'd
probably load in as much memory as the mother board would hold. My wife's
Win98SE machine has 192M, the motherboard's limit, and the change helped a
lot.

I looked up our machines on Crucial ([url]http://www.crucial.com/)[/url], saw the types
of memory and how much could fit and ordered it. At least look up your
machine there to see what kind of memory (SDRAM, DDR, PC133, PC100, parity
or no parity etc) and how much your machine can take and what kind of price
it might cost. Crucial is not the absolute cheapest but I like them because
there's no question about quality (they don't buy memory from others, they
manufacture it themselves).

With 128M of memory the machine does a lot of swapping between disk and
memory during a compile and link of any but the smallest program. Other
limitations are independent of how much memory in the machine. As I
remember it Win98 is built on a 16 bit foundation and limits the resource
record table to a 64K segment (one each for GDI and data memory tables). It
does not take a huge program for the number of selectors allocated during
the linker's allocations to fill the table. I was a Win98 fan until my
machine died and the replacement had Win2K. The difference in stability
between a 128M Win98 machine and a Win2K or XP machine suprised me. My
replacement machine came with Win2K and 128M (and Win2K is much bigger than
Win98). Even with 128M the stability was much greater. I upgraded to XP
Pro and increased the memory to 512M and am very happy with its performance.
My wife's Win98SE machine now annoys me <g>

.. Ed

Ed Mulroy [TeamB] · Guest

The gentleman who lists his name as 'cactus' jumped in with a reply saying
Win98 was being used. I did not notice that the message was from a
different person.

I run XP Pro which is essentially XP Home with a couple of different
settings. The LME* errors seem to be related to out of memory isues.

The out of memory can reflect the inability to get enough memory from the
OS, and if you are running with 128M of RAM and/or with not much free disk
space you'd probably get it more quickly under XP than under Win98 because
XP uses more memory.

The out of memory can also be because the linker ran up against the limits
of one of its internal tables. I know that the linker in C++ Builder 6
expanded some table space, expanded what size *.TDS file it can handle and
increased the allowable size of resources (1 Meg bitmaps can now be linked).

If you are using the free compiler (the 5.5 compiler) then you are using the
command line tools form C++ Builder 5 so retain the old limitations. If you
are using that then at some point it might be worth considering offloading
some of the code to a DLL.

.. Ed

Ed Mulroy [TeamB] · Guest

I agree that the error message does not make sense.

I've seen anyone build a project in the "My Documents" directory before. I
create a directory for each project so that things from multiple projects do
not get mixed together.

Here are some guesses as to things that might cause that message to be
generated are:

- The current version of the *.TDS or *.EXE file is already open,
for instance in the debugger or in the IDE or the helloworld
program is already running
- The file is marked read-only
- The disk is full
- The compiler was installed under a different account/user name
- The current log in does not have administrator or power user privileges

Delete all the project's *.obj, *.il?, *.exe and *.tds files. Check the
list above and correct whatever might be found and try building the project
again.

Here is a screen capture of my building and running the console mode version
from the command line. I don't have version 5.5 on this machine but I
assure you that when I do this on my wife's Win98SE machine with 5.5 it also
builds and runs correctly.

---------------------------

C:ProjectshelloHelloCon

Ed Mulroy [TeamB] · Guest

The linker version is not an issue. Your linker version is 5.00 because you
are using the command line tools from C++ Builder 5 while my screen capture
showed the use of those from version 6. The build you show should work with
any version of C++ Builder.

Ed Mulroy [TeamB] · Guest

Didn't you get the hello world examples I posted?
http://www.mulroy.org/hello.zip

Each has its own batch file or make file to build it. For the simplest
there is a batch file called build.bat so all you need to do is say BUILD to
build it.

.. Ed

Steven J Masta · Guest

Nuclear Joker wrote: