Subj : LINK386 Help To : Don Guy From : Fred Kantor Date : Wed Dec 05 2001 12:24 pm In a message dated 12-05-01, Don Guy said to Fred Kantor: FK> If I may ask... did you make a program .DEF file? DG> I did, however it has nowhere near the content of yours. NAME, DG> DESCRIPTION, and STUB directives only. DG> What puzzles me is LINK386's complaint about an invalid object DG> file, where Borland's linker has none. Just a thought, but... for two different assemblers -- ALP (IBM) and A386 (Eric Isaacson) -- I found that different starting material was needed to produce usable object code; at that time, A386 needed to have a particular setup "front-end" to set the order of components in the output object. I wrote that program a while ago: FWKFF.ASM 17134 01/18/1996 01:40 Things may have changed since then. Have you looked to see if some front-end material like that might be needed to produce acceptable .obj code? Here is what I used to set the .obj order for A386 (I've moved the ";<--<< ALP A386 different" to fit the message width): -----------------------------------------cut here TITLE FWKFF Fast Find NAME FWKFF .386 ; in A386, put FLAT in every SEGMENT definition ; the order of these empty segments sets order in .OBJ ;<--<< ALP A386 different CODE32 SEGMENT DWORD FLAT PUBLIC 'CODE' ; CODE32 ENDS ; ; DATA32 SEGMENT DWORD FLAT PUBLIC 'DATA' ; DATA32 ENDS ; ; CONST32 SEGMENT DWORD FLAT PUBLIC 'CONST' ; CONST32 ENDS ; ; BSS32 SEGMENT DWORD FLAT PUBLIC 'BSS' ; BSS32 ENDS ; ; DGROUP GROUP CONST32, BSS32, DATA32 ; ASSUME CS:FLAT, DS:FLAT, SS:FLAT, ES:FLAT ; ----------------------------------------------------cut here --- þ testing... þ * Origin: FONiX Info Systems * Berkshire UK * www.fonix.org (2:252/171) .