Microsoft KB Archive/11999

Unreachable Code Segment ID Number: Q11999

4.00 MS-DOS buglist4.00 fixlist5.00

Question:

Should MASM check if segment names and class names conflict? In the following example, “code” is both a segment name and a class name. When “code” is used for a class, followed by a group statement that includes segment code, MASM will produce “no or unreachable CS” for the procedure.

The following is an example:

bc_code segment byte public ‘code’ bc_code ends

pgroup group code, bc_code assume cs:pgroup

code segment byte public ‘code’

getpsp proc near getpsp endp

code ends end

Response:

Microsoft confirmed this to be a problem in Version 4.00 of the Macro Assembler. The problem was corrected in Version 5.00.