| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Mystery 12 |
PE> PF> When I placed a ".model flat" in two.asm, PF> everything worked correctly. PE> questions. Would you be able to explain to me further PE> just why this is required? Like why TLINK doesn't have It is an alignment problem, I think. The .flat makes sure the segments are 32bit, and aligned on a 4byte boundary. If you look at the *.MAP file generated by link386 with and without the .flat, you will see that the address of the variables have moved -- this is what caused your trap. Tlink must, by default, aligning the code even though it was not instructed to do so (which would cause it to fail for other programs that do not want this behavior). A possible workaround for link386 is to define another *.asm file that contains the same SEGMENTS with at least one variable defined, and link that *.obj in first. --- Maximus/2 2.01* Origin: Sol 3/Toronto (905)858-8488 (1:259/414) SEEN-BY: 12/2442 620/243 624/50 632/348 640/820 690/660 711/409 410 413 430 SEEN-BY: 711/807 808 809 934 942 949 712/353 515 713/888 800/1 7877/2809 @PATH: 259/414 400 99 250/99 3615/50 229/2 12/2442 711/409 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™.