In EMU$8086$Assembly Language Only! Do the following & make sure its complete in assembly language code only.

Awesome Autos needs a lot inventory management system. Using all of the knowledge that

we$$ve gained in the last few sections on structs and files, you need to write a program that does

the following:

A$)$Design a structure that can hold the information on an automobile: manufacturer

$($string$),$model $($string$),$color $($string$),$engine size $($float$),$and doors $($integer$).$

B$)$When your program is run, prompt the user to enter each of these pieces of data into

the structure.

C$)$Once the last piece of structure data has been entered, prove the structure is working

correctly by neatly printing the structure$$s contents to the screen.

D$)$Write the structure out to the file.

E$)$Allow the user to add more automobiles until they indicate that they are done $($repeat

steps B through D$).$

F$)$Close the file and print a message out to the screen once the file has been created.

G$)$Open the file back up for reading.

H$)$Using a loop while there is data to process:

a$.$Clear any data in the structure out.

b$.$Read the data back into the structure.

c$.$Print the structure out to the screen again.

I$)$Close the file.

Here$$s a sample run:

Manufacturer: Chevrolet

Model: Corvette

Color: Ticket Me Red

Engine Size: $6\mathrm{.}2$

Doors: $2$

Add more inventory $($Y$/$N$)?$Y

Manufacturer: Kia

Model: Sorento

Color: Green

Engine Size: $2\mathrm{.}8$

Doors: $4$

Add more inventory $($Y$/$N$)?$N

Struct information written to file C:$\backslash$asm$\backslash$test$.$txt

Manufacturer: Chevrolet

Model: Corvette

Color: Ticket Me Red

Engine Size: $6\mathrm{.}2$

CIS $333$James Assignment $5$Page $2$

Doors: $2$

Manufacturer: Kia

Model: Sorento

Color: Green

Engine Size: $2\mathrm{.}8$

Doors: $4$

$***$Awesome Auto Lot Inventory file has been processed $***$

Hints: Think procedures! You can simplify the code and your debugging life by writing

procedures. For example, a print structure routine, a save to file routine, a read from file

routine, et cetera. Secondly, DO NOT code this application in a single shot $$incrementally build

up each piece of logic otherwise you will get lost when things don$$t work right.