I'm still picking away at producing an OS/2 text-mode
application which uses a DOS executable as the stub.
I ran into problems using the linker which accompanies Borland C++,
and after some helpful input from others decided to have a go at
using LINK386. It does not appear to like me however.
Using the object files produced by Borland's compiler, it returns
the following error:
main.obj(main.cpp) : fatal error L1101: invalid object module
Object file offset: 22d Record type: b0
I'm still picking away at producing an OS/2 text-mode
application which uses a DOS executable as the stub.
I ran into problems using the linker which accompanies Borland C++,
and after some helpful input from others decided to have a go at
using LINK386. It does not appear to like me however.
Using the object files produced by Borland's compiler, it returns
the following error:
main.obj(main.cpp) : fatal error L1101: invalid object module
Object file offset: 22d Record type: b0
If I may ask... did you make a program .DEF file?
If I may ask... did you make a program .DEF file?
I did, however it has nowhere near the content of yours. NAME, DESCRIPTION, and STUB directives only.
What puzzles me is LINK386's complaint about an invalid object
file, where Borland's linker has none.
Just a thought, but... for two different assemblers -- ALP (IBM) and<snip>
A386 (Eric Isaacson) -- I found that different starting material was needed to produce usable object code;
Have you looked to see if some front-end material like that might be needed to produce acceptable .obj code?
Here she be:
=== Start pwd2.def ===
NAME pwd WINDOWCOMPAT
DESCRIPTION 'Password Generator v1.1, by Don Guy'
STUB 'pwd2-d.exe'
EXETYPE OS2
=== End pwd2.def ===
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,028 |
Nodes: | 17 (0 / 17) |
Uptime: | 180:58:53 |
Calls: | 503,706 |
Calls today: | 9 |
Files: | 158,903 |
D/L today: |
13,695 files (4,203M bytes) |
Messages: | 444,340 |
Posted today: | 2 |