COEN 3114 INDIVIDUAL REPORT EXPERIMENT NO 2. INTRODUCTION TO TURBO ASSEMBLER NAME: BAHAYA, MARICAR C. SECTION: 3-2 DATE PERFORMED: JULY 1, 2!14 DATE SUBMITTED: JULY 3!, 2!14 PROFESSOR: ENGR. ROLITO L. MAHAGUAY ANALYSIS: Our focus on this experiment is to introduce the Turbo Assembler. Turbo Assembler (TASM) is an assembler package developed by orland !hich runs on and produces code for "#$ or %&$bit x'# MS$(OS or Microsoft )indo!s. *t can be used !ith orland+s high$level language compilers, such as Turbo -ascal, Turbo asic, Turbo . and Turbo .//. *n this experiment, the re0uirements !e used are personal computers, system disk, data disk. )e need also an editor, assembler, and loader. A text editor is a program that allo!s us to enter and prepare our program from the ordinary keyboard into a computer readable form. Assembler is a program !ritten in assembly language is translated to machine code by an assembler. The loader is the program that actually takes the machine instructions and places it in memory at the specified starting address for execution. The ob1ectives of the experiment are to be able to learn the basics of turbo assembler, to properly assemble and link a program using tasm and tlink, and to be able to create an assembly language program using turbo assembler !ith S2 as editor. The things that !e experimented are 3 ". )rite a program using 4(*T as our text editor &. )rite a program !ith an output5 6 " & % 7 8 # 9 ' : 5 CONCLUSION: Turbo assembler can read, display any format including binary, hexadecimal and even decimal unlike the debugger !hich only reads hexadecimal characters. To assemble my code, * need to use TASM. The syntax is3 TASM ;*<4=AM4 !here FILENAME is the name of my assembly language file "#$%&'$ $%( )*+ (,$(-*#&-. The only files created in assembling process are ;*<4=AM4.asm and ;*<4=AM4.ob1. The only files created in linking process are ;*<4=AM4.MA-, ;*<4=AM4..OM and ;*<4=AM4.4>4. *t is very easy to locate my error because once * assemble my program , it displays !hat columns my errors are located if there?s any. *t also indicates my specific error. To link my code, the syntax is3 .3@tlinkAt ;*<4=AM4. There should be no A( OB4.T ;*<4 message in the linking process, if bad ob1ect file occurs assemble the program once again.
;inal Ceport -age " of " Format & Presentation : 5% _____ Timeliness: 10% _____ Correctness: 15 %_____ Analsis & Concl!sion: "0%_____ FINAL SCO#$: Format & Presentation : 5% _____ Timeliness: 10% _____ Correctness: 15 %_____ Analsis & Concl!sion: "0%_____ FINAL SCO#$: