Q45165: "Too Many Segments" LINKing More Than 128 Modules

Article: Q45165
Product(s): See article
Version(s): 2.00 2.01 3.00 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | SR# S890512-130 B_BasicCom | mspl13_basic
Last Modified: 13-DEC-1989

The linker error message L1049 "Too many segments" occurs when you are
trying to LINK more than 128 modules into an .EXE program or a Quick
library. The default number of segments for LINK.EXE is 128. To
correct this problem, combine two or more of the modules (the .BAS
source files).

If the modules are too large to combine, you must set the number of
segments to more than 128 with the /SEGMENTS linker option. The
maximum number of segments is 1024, or 1K. If you compile and link
within the QuickBASIC environment instead of from the DOS command
line, you can set the /SEGMENTS option by including the following line
in your AUTOEXEC.BAT file:

   SET LINK= /SEGMENTS:<number of segments>

Note that there is no space before the "=", and one space after the
"=".

This information applies to Microsoft QuickBASIC Versions 2.00, 2.01,
3.00, 4.00, 4.00b, and 4.50 and to Microsoft BASIC Compiler Versions
6.00, and 6.00b and to Microsoft BASIC PDS 7.00.

To determine the number of segments you are generating, use the
following guidelines. A module in QuickBASIC is exactly the same as a
.BAS file. Each module compiles to one code segment. All of the data
in the program is combined at LINK time into one single data segment.
There is only one data segment, no matter how many modules you
compile. Therefore, the number of segments is as follows:

   NumberOfSegments = [number of .BAS files you start with] + 1

If you are using a library, each .BAS file that was compiled and put
into the library must be included in the above formula.

The "Too many segments" error message can also occur when using the
BUILDRTM utility of Microsoft BASIC Compiler 6.00, 6.00b and to
Microsoft BASIC PDS 7.00 to combine more than 128 modules into a
run-time module. This happens because BUILDRTM.EXE uses LINK.EXE to
create a run-time module. The workarounds are the same as above: combine
one or more modules or SET the LINK environment variable.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.