🚀 go-pugleaf

In what you show you have PUBLIC _externproc  The PUBLIC line is a 
declaration that a symbol is to be placed into the public symbol table.  It 
is not a declaration of the symbol.  I think _externproc should be a 
procedure (a proc) in the code.

As an example, here is some assembly that does that.  Unlike your code it 
actually declares segments instead of using the "simplified" directives that 
you seem to prefer.  The comments about the symbols are not related to the 
difference in segment declaration.  They refer to the symbol WinMain.

----------------------------
        .386p
        model flat

HWND_DESKTOP    equ   0
MB_OK           equ   0

_TEXT   segment dword public use32 'CODE'
_TEXT   ends
_DATA   segment dword public use32 'DATA'
_DATA   ends
_BSS    segment dword public use32 'BSS'
_BSS    ends

; This program does not use _BSS, the unitialized global data segment,
; but is generally needed in programs so I've added it here
DGROUP  group   _BSS,_DATA

        ; declaration of Windows' ascii MessageBox function
        ; the linker will find a reference to it in the Windows import 
library

        extrn   MessageBoxA     :near

_DATA   segment dword public use32 'DATA'
        align   1
msg     db      " Hello World! ",0
mtitle  db      "Hello Message Box", 0
zero    dw      0
        align   4
_DATA   ends


_TEXT   segment dword public use32 'CODE'
WinMain proc    near
        push    ebp       ; save EBP register and load stack ptr into it
        mov     ebp,esp

        ; MessageBox(HWND_DESKTOP, msg, mtitle, MB_OK);
        push    MB_OK
        push    offset mtitle
        push    offset msg
        push    HWND_DESKTOP
        call    MessageBoxA

        xor     eax,eax  ; return value is zero
        pop     ebp      ; restore EBP register value
        ret     16       ; free up 16 bytes of stack when returning
WinMain endp
_TEXT   ends

        public  WinMain

        end     WinMain
----------------------------


.  Ed

> Daniel wrote in message
> news:46e95c9e@newsgroups.borland.com...
>
> No, I don't use that in the assembly module. The assembly module
> is extremly
> simple:
> .386
> .model flat
> PUBLIC _externproc
> DATASEG
> ;one or two things here just to define something.
> ENDS DATA
> CODE
> mov eax, 05Ah; just to have something happen
> ENDS CODE
> END
>
> patterned after a previous post on this group. I created this file by
> choosing File->New->Assembly then adding it to the project. Although I can
> assemble it with the command-line assembler and add the object file to the
> Builder project, it doesn't make any difference whether the asm file or 
> obj
> file is part of the project.
>
> Borland's documentation advises to use the same .model in the assembly
> module as the C++ program, but nowhere in Builder does it give any
> indication of what the model is. Nor can I find anything that says 
> anything
> about what the COW32.obj file might be or do.
>
> Any help is much appreciated since I'm going nuts.