Microsoft KB Archive/29918

= Defining &quot;Intersegment Short Jump&quot; (LINK Error L2002) =

Article ID: 29918

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft QuickBasic 4.0, when used with:
 * Microsoft MS-DOS 6.22 Standard Edition
 * Microsoft QuickBASIC 4.0b, when used with:
 * Microsoft MS-DOS 6.22 Standard Edition
 * Microsoft QuickBasic 4.5 for MS-DOS, when used with:
 * Microsoft MS-DOS 6.22 Standard Edition
 * Microsoft BASIC Compiler 6.0
 * Microsoft BASIC Compiler 6.0b

-



This article was previously published under Q29918



SUMMARY
The L2002 linker error message is as follows:

&quot;fixup overflow near in frame seg target seg target offset .&quot;

One possible reason for this error is that an assembler program contains an intersegment short jump or intersegment short call.

LINK.EXE can also give this error if one of your compiled Basic object modules is too large. The solution is to split the module into two or more separately compiled modules. This information applies to QuickBasic Versions 4.00, 4.00b, and 4.50 for MS-DOS, and to Basic Compiler Versions 6.00 and 6.00b for MS-DOS and OS/2.



MORE INFORMATION
During the normal execution of a program, instructions residing in the current code segment are being executed in a sequential order. A program flows sequentially from one instruction to the next by incrementing the IP register as each instruction is executed.

However, it is possible to alter this normal program flow. One method is to transfer control to instructions residing in a different segment. Referred to as an intersegment jump or intersegment transfer, it is accomplished by altering both IP and CS.

If the size of the jump is less than 64K, but still involves transferring to a different segment, then this is called an intersegment short jump.

This error is usually associated with assembly language routines. It usually doesn't occur with QuickBasic programs.

Additional query words: QuickBas BasicCom

Keywords: KB29918

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.