NASM Forum > Using NASM

Object files and address linking for flat file programs

(1/1)

Deskman243:
Greetings chat

In this post I'm trying to go through the segmentation of these models using the org addressing on bin files. I'm happy to resume these topics as a continuing series where links to the earlier posts and code can be found here
https://forum.nasm.us/index.php?topic=2958.0

Just to really quickly summarize the previous post was about learning how to use and make object files from elf types and creating the bin files from this. The difference here is to my knowledge the elf files can not use the option for org addressing so in this 2nd model I verified that the code does work using a bin based setting on the Makefile's settings. To my surprise I observed the SAME results! This is when I realized that I could really use a review of flat file systems. I will be available for any review of this subject and again would be happy to continue the conversation further.

Declan69:
A flat file consists of a single table of data. It allows the user to specify data attributes, such as columns and data types table by table, and stores those attributes separate from applications. This type of file is commonly used to import data in data warehousing projects.

Myhdfs App

Winifred58:
In flat file programs, object files are compiled machine code modules linked by the linker to form an executable program. The linker resolves symbol addresses, combining multiple object files into a single program. MyPaymentPlus

Navigation

[0] Message Index