With the exception of Lab#1, which must be done in Prism, you can do the labs either in a campus lab or at home. If you prefer to work on a home PC, you will need to set it up first so that you can have a home-based development environment, and the Lab Handbook has all the needed details to achieve that. Note that working at home should not be confused with a
remote connection since the latter does not support GUI programs like
In order to compile and run Lab programs, you need a console that allows issuing commands. This is provided by an application called
(a TYPE software) that is available on all
platforms. If you use Unix or Linux, you can either use
or the terminal window that comes naturally with these operating systems.
On Windows machines, however, the console interface (known as the DOS command prompt)
is cumbersome at best, and hence it is recommended that you use
n must ideally be completed during week #
n of the term
but it is accepted if done during week #
n+1. For example, Lab#3 can be
eChecked until Sunday midnight at the end of week #4.
Each Lab ends with a section entitled CHECKING that poses one or more problems to be solved; e.g. in Lab #4, the checking problems are numbered 4A, 4B, and so on. To solve a problem like 4A, you will need to develop an application called
Check04A; i.e. named
Check, followed by the lab
number zero-filled to two digits, followed by the problem number (A or B or ...).
You compile and run your app repeatedly in
UniCon (or some other
console) until you are convinced it produces the desired output under a variety
of input conditions. At that point, you use
eCheck, a software
UniCon, to check your app.
eCheck is a test harness that runs your app under several
test cases that are semi randomly chosen. If the app failed to produce the
eCheck displays both outputs (yours and the
expected) and the input that caused the problem. You would then investigate,
fix the problem, and retry. Otherwise,
eCheck connects to York
to record your name as having completed that Lab (assuming the deadline has
Important Notes on eChecking:
Uniconare seemingly identical yet
eCheckinsists they are not, yours must have trailing spaces and/or carriage returns. The very last output, for example, must be made with
ePostare reporting authentication problems, it is probably due to an incorrectly-entered password or a character in it that failed to encrypt somewhere along the way. The easiest way to verify/resolve this is to change your password on Unix to something involving letters (upper/lower) and digits only and then retry. In particular, symbols like the single quote and the colon will cause problems.
ePostafter having successfully eChecked a Lab, then the most likely reason is that you are not registered in the course.