| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | asm + link problems |
PF> What happens if you replace tasm with masm?
PE> If I change to masm 5.1, and change the ".model flat" to
PE> ".model small", then I get the same problem, a trap-5.
Then don't change ".model flat"! I don't think 5.1 actually
supports the .flat instruction. Look on the ddk cdrom for megabytes of
*.asm samples that all assemble with masm 5.1.
I've got a tiny one here I wrote for a no-CRT dll init:
.386p
_TEXT segment dword public use32 'CODE'
assume cs:_TEXT
extrn DllInit:PROC
Init proc near
jmp DllInit
Init endp
_TEXT ends
end Init
PE> The "-oi" option to tasm is meant to produce "intel
standard"
PE> object code.
I think that means the file format -- not the names of the segments, or
their alignments.
--- Maximus/2 3.00
* Origin: Sol 3 * Toronto * V.32 * (905)858-8488 (1:259/414)SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 259/414 400 99 250/99 3615/50 396/1 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.