Assmebler programming.
These are to study for a test , so they must be well commented.
Also, if you cannot answer all 3, please let me know which problems
you could solve, and I will set a new question up with a new price for
you. Thanks !
1.
Timer ---
Write a new timer tick that when activated will cause the word 'help'
to
appear on the screen for 5 seconds. The word will appear 4 times.
2.
Flash ---
Write a program called 'flash' that when activated causes the screen
to cleaned and waits for an input of a number. When a number (N) is
typed the screen will flash for (N) times at any collor for a second.
For example if the number typed is 2 the screen will turn green (or
any other collor) and then black twice, then if the next number is 4,
the screen will flicker 4 times, and so on untill the letter 'E' is
typed which will exit the program. All the computer ticks exchanged
will have to be returned to there original state.
Remark : Legal input is one number or the letter 'E' if any other
input is typed the system will not do anything. Make sure the typed
symbol appears on the screen.
3.
Swap ---
Write a resident program (TSR) called 'SWAP', when activated the 'Caps
Lock' and 'Num Lock' will trade functions , everytime the user clicks
'Caps' the 'Num' light will go on and vice versa. Remeber the preserve
the properties of 'Caps' and 'Num'.
Remarks :
Use address : 40:17h
for 'Caps' : byte no. 6
for 'Num' : byte no. 5
For simplicity reasons disregard problems that might rise regarding
address 40:18h.
Thanks for the answers |
Request for Question Clarification by
jeanluis-ga
on
10 Jun 2003 15:11 PDT
In order to answer this question to your satisfaction I will need to
know what architecture you are targeting? Intel x86? MIPS? ARM? other?
The more specific you can be the better... Also if you have certian
platform/assembler you prefer please specify what it is as well. (i.e.
Windows 2000 + MASM, or Linux + gas, or something like that, please
include version numbers of assemblers, not that it will matter much)
Another thing to note is that solving any one of these problems will
probably take considerable time... If you don't get any takers you may
want to consider upping the list price... Another thing that may help
(as you suggested) is breaking this question up into 3 seperate
questions, and closing this one... that way you can have 3 different
people tackle the problems at the same time (assuming we have 3
researchers who "do" assembly :)
Just so you know, I would be inclined to work on either 1 or 2 (or
both) later on in the week if time permits, and if my
hardware/software meets your requirements... However number 3 is
something that I don't care to attempt, because I have never written a
TSR, and I doubt I will ever have to...
Anyhow let me know
--jld
|
