M2

Question 1

specifies the memory size assigned to each of the different parts or segments of a program

Answer 1

memory model

Question 2

there exist different memory models for the

Answer 2

8086 processor

Question 3

this specifies the size of the memory the program needs

Answer 3

.MODEL Directive

memory model directive

Question 4

Based on this directive, the assembler assigns the required amount of memory to data and code.

Answer 4

.MODEL Directive

memory model directive

Question 5

what are the segments

each one of the segments. in a program, is called a

Answer 5

stack, data, and code

logical segment

Question 6

depending on the model used, segments may be

Answer 6

one or in different physical segments

Question 7

here, segments are declared using the .MODEL directive

Answer 7

MASM 6.X

Question 8

This directive is placed at the very beginning of the program, or after the optional title directive

Answer 8

.MODEL Directive

memory model directive

Question 9

in this model, both code and data occupy one physical segment

Answer 9

TINY Model

Question 10

In the TINY model both code and data occupy one physical segment. Therefore, all procedures and variables are by default addressed as X, by pointing at their offsets in the segment.

Answer 10

NEAR

Question 11

On assembling and linking a source file, the tiny model automatically generates a X file, which is smaller in size than an Y file.

Answer 11

com

exe

Question 12

In this model, all code is placed in one physical segment and all data in another physical segment.

Answer 12

SMALL

Question 13

In this model, all procedures and variables are addressed as NEAR by pointing to their offsets only.

Answer 13

SMALL

Question 14

In this model, all elements of code are placed into one physical segment. However, each element of data can be placed by default into its own physical segment.

Answer 14

COMPACT

Question 15

In the compact model, all code elements (procedures) are addressed as X and data elements (variables) are addressed as Y

Answer 15

NEAR

FAR

Question 16

the model opposite of the compact model

Answer 16

medium

Question 17

In this model, data elements are treated as NEAR and code elements are addressed as FAR.

Answer 17

medium

Question 18

In this model, both code elements (procedures) and data elements (variables) are put in different physical segments.

Answer 18

LARGE

Question 19

In the large model, pocedures and variables are addressed as X by pointing at both the segment and offset addresses that contain those elements.

Answer 19

FAR

Question 20

no data array can have a size that exceeds one physical segment

Answer 20

true

Question 21

This model is similar to the LARGE model with the exception that a data array may have a size that exceeds one physical segment

Answer 21

HUGE

Question 22

For the LARGE model, the largest arrays size can not exceed X

Answer 22

64 KB

Question 23

For the HUGE model, an array may have a size X than 64 KB and hence can span more than one

Answer 23

greater

Question 24

The X and X are the major factors in determining the choice of an appropriate model.

Answer 24

amount of data that has to be manipulated

code that needs to be written

Question 25

For a small fast program that operates on small quantities of data, the X models are the most suitable ones

Answer 25

SMALL or TINY

Question 26

difference of small and tiny model

Answer 26

tiny model generates a COM module small model generates an EXE module

Question 27

what module does not allow references to be used

Answer 27

COM

Question 28

For very long programs that require more than one code segment and operate on large amounts of data which would require more than one data segment, the X models are most appropriate.

Answer 28

LARGE and HUGE