head	1.11;
access;
symbols;
locks
	yap:1.11; strict;
comment	@# @;


1.11
date	98.10.06.03.52.31;	author yap;	state Exp;
branches;
next	1.10;

1.10
date	97.12.04.16.21.47;	author yap;	state Exp;
branches;
next	1.9;

1.9
date	97.11.10.18.56.58;	author yap;	state Exp;
branches;
next	1.8;

1.8
date	97.10.28.14.59.10;	author yap;	state Exp;
branches;
next	1.7;

1.7
date	97.09.26.21.23.58;	author yap;	state Exp;
branches;
next	1.6;

1.6
date	97.09.24.17.13.23;	author yap;	state Exp;
branches;
next	1.5;

1.5
date	97.09.22.18.51.39;	author yap;	state Exp;
branches;
next	1.4;

1.4
date	97.09.22.16.39.31;	author yap;	state Exp;
branches;
next	1.3;

1.3
date	97.09.17.18.22.39;	author yap;	state Exp;
branches;
next	1.2;

1.2
date	97.09.17.18.17.41;	author yap;	state Exp;
branches;
next	1.1;

1.1
date	97.09.08.19.00.21;	author yap;	state Exp;
branches;
next	;


desc
@@


1.11
log
@*** empty log message ***
@
text
@<html>
<title>
	FAQs: V22.0201, Machine Org I, Yap
</title>
<body bgcolor=ffffff>

<a name="top">
		<h4>
		<font color=ff00aa>
		V22.0201, Machine Organization I, Yap
		</font>
		</h4><h2>
		<font color=ff00aa>
		FAQs: FREQUENTLY ASKED QUESTIONS
		</font>
		</h2>
</a>

<ul>
<li>
<a href=#tasm>What is TASM, MASM, the linker, debugger
	and related software?
</a>
<li>
<a href="#tasm_acf">Where do I find TASM in the ACF labs?
</a>
<li>
<a href="#tasm_windows">Can I run TASM under Windows?
</a>
<li>
<a href="#debug">How can I use the debugger?
</a>
<li>
<a href="#msdos">What is the MS-DOS COMMAND PROMPT?
</a>
<li>
<a href="#dos">I am unfamiliar with DOS.  Can you help?
</a>
<li>
<a href="#editors">Do I need to use a text editor?  What shall I use?
</a>
<li>
<a href="#print_screen">How do I print what is on my screen?
</a>
<li>
<a href="#ps_print">How do I print POSTSCRIPT files?
</a>
<li>
<a href="#ps_what">What are POSTSCRIPT files?
</a>
<li>
<a href="#unprintable">Why does my .ASM file contain unprintable characters?
</a>

<li>
<a href="#set_path">I want the TASM directory to be automatically
searched.  How do I modify environment variable PATH to allow this?
</a>

<li>
<a href="#bat">What are bat files?
</a>

<li>
<a href="#nt">I happen to use an Windows NT system. 
Can you give me some hints?
</a>

<li>
<a href="#mouse">Can you please give me the basics of mouse programming?
</a>

<li>
<a href="#com">
What are .com executable files and how do I produce them?</b>
</a>

<li>
<a href="#bot">Bottom of this file
</a>

</ul>

<p>
<hr size=4>
<pr>

<ul>
<li>
<a name=tasm>
<b>What is TASM, MASM, linker, debugger and other software?
</b>
</a>
<br>
TASM is the name of the Turbo Assembler, and is the main software
assumed for this class.  The latest version
is version 5, but older versions will probably be OK
for this course.  Indeed, the PC labs has version 4.1.
You can purchase your own copy from the NYU bookstore
for about $75 (for other sources, look at the course homepage
under "other information").
MASM stand for Microsoft Assembler.  
Appendix D and Chapter 4 of the text has
some basic information on MASM.  It is very similar
to TASM, and it is the assembler assumed by the text.
Associated with each assembler are linkers and debuggers.
Information about debugging is given in another FAQ, below.
The linker for TASM (resp. MASM) is called TLINK (resp. LINK).
<br>
	<b><font color=ff0000>
	&gt;&gt;
	For more information about assembling and linking,
	<b><a href="tasm.htm">CLICK HERE</a></b>.
	</font>
	</b>

<li>
<a name="tasm_acf">
<b>Where do I find TASM in the ACF labs?
</b>
</a>
<br>
There are two answers:
<br>
(a) If you are in windows, you can look under the start menu.
In any case, there is an applications folder
on the desktop.  Look under the 
"programming" folder and then the "dos programming" folder.
There is also a turbo debugger under "programming", under "C++".
<br>
(b) If you are in the MS-DOS PROMPT, you probably
want to locate the TASM directory:
	<pre>
        Z:\bin\tasm4\bin
	</pre>
We suggest that you append this directory to the current value
of your environment path variable (see another
<a href="#set_path">FAQ question</a> for this).
Note that Z:\bin\tasm25 contains an older version of TASM.
Other folders that might be of interest in the
future are Z:\courses\yap and Z:\courses\v220201.002.

<li>
<a name="tasm_windows">
<b>Can I run TASM under Windows 95?
</b>
</a>
<br>
No, TASM does not run under Windows 95.
You need to go into a MS-DOS PROMPT window to
run TASM.
<!-- However, you can debug directly from Windows.
-->
<li>
<a name="debug">
<b>
How can I use the debugger? 
</b>
</a>
<br>
A debugger is a tool to help the debugging process.
Of course, you can debug your programs without using
a debugger.  But the special nature of assembly
language programming makes it hard to debug complex
programs unless you can actually examine the
registers and memory locations of your computer.
These functions are provided by any debugger.
Hence it pays to make the little effort to
learn the basics of TD.
DOS comes with a very elementary form of debugger
called DEBUG.  Chapter 5.4 and Appendix E of the text shows you how
to use this debugger.
We will be using the Turbo Debugger ``TD'',
which is much more sophisticated than DEBUG.
<br>
        <b><font color=ff0000>
        &gt;&gt; 
        For more information, especially about TD,
        <b><a href="debug.htm">CLICK HERE</a></b>.
        </font>
        </b>  


<li>
<a name="msdos">
<b> What is the MS-DOS COMMAND PROMPT? </b>
</a>
<br>
We assume that you will initially be facing the
WINDOWS 95 operating system.  But for using the Turbo
Assembler, we need to fall back to the older operating
system called DOS.  WINDOWS 95 gives you access to this
DOS environment in the form of window called MS-DOS COMMAND
PROMPT (or MS-DOS PROMPT, for short).  You can usually get this
window from the start menu.  If not, is it probably
called <b>command.com</b> under the windows directory.
(This means you can also invoke this by typing
``command'' at the start->run menu.) To find out more
about DOS, see the next question. NOTE: <b>cmd.exe</b>
is the corresponding WinNT command prompt.
<p>
HINTS for MS-DOS PROMPT window:
Usually, this is just another window on
the Win95 desktop.   But to make this window
take over the entire screen, press ALT-ENTER.
You can return to the Win95 desktop
by pressing ALT-ENTER once more.
There are basic window functions (such
as making a copy of the window output)
you can do from the MS-DOS PROMPT.
To access these, left-click the icon on the left of the
title bar, or right-click the title bar itself.

<li>
<a name="dos">
<b>
I am unfamiliar with DOS.  Can you help?
</b>
</a>
<br>
The text editor ``edit'' in DOS is useful to know.
(see the next <a href="#editors">question</a>).
Some useful DOS functions are
<ul>
<li>	<b>dir</b> (list the current directory)
<li>	<b>cd</b> (change the current directory)
<li>	<b>set</b> (set or show environment variables)
<li>	<b>type</b> (type the contents of a file)
<li>	<b>copy</b> (copy a file)
<li>	<b>ren</b> (rename a file)
<li>	<b>mkdir</b> (create a new directory, i.e., folder)
<li>	<b>rmdir</b> (delete a directory, i.e., folder)
<li>	<b>echo</b> (echo command -- useful for batch files)
<li>	<b>rem</b> (remark command -- useful for batch files)
<li>	<b>call</b> (calls another batch file)
<li>	<b>if</b> (conditional processing)
<li>	<b>for</b> (runs a program for each file in a set)
<li>	<b>goto</b> (jumps to label)
<li>	<b>pause</b> (pauses program and awaits a key press to continue)
<li>	<b>command</b> (starts a new copy of command window)
<li>	<b>edit</b> (MSDOS editor)
<li>	<b>exit</b> (exits command window)
</ul>
To find out more about any of these commands, you can type
the command name followed by ``/?''.  E.g.
	<pre>
	:&gt; dir /?
	</pre>
HINT:
<br>
(a) When you do ``dir'' or ``type'', the output
can fill more than one screenful.  To allow
you to view the output one screenful at a time,
you can ``pipe'' the output to the function called <b>more</b>.
	<pre>
	:&gt; dir /? | more
	</pre>
You type a space-bar to get the next screenful of output from more.
Note that ``|'' indicates the pipe from output of ``dir''
to the input of ``more''.  Another original from the
UNIX world.
<br>
(b) DOS folder or file names
are 8 characters, possibly followed by a 3 character extension.
E.g., myprogra.asm.  But Windows 95 allows much longer
file names.  If the Windows 95 name of a folder is myprograms,
then its DOS name is assumed to be "myprog~1".  That is, the
first 6 characters are taken, followed by "~1".  If a previous
file already have the same 6 characters, it is followed "~2", etc.


<li>
<a name="editors">
<b> Do I need to use a text editor?  What shall I use?</b>
</a>
<br>
In this course, you need an editor to enter your assembly
        language programs.  These programs are stored
        in a file of ascii characters.
<p>
You can use any of your favorite editors.
The simplest WYSIWYG editor from Windows 95 is Note Pad.
The simplest is <b>edit</b> from
        within the MS-DOS COMMAND PROMPT.  Edit is very
        simple and intuitive to use.  You can figure
        it out without reading instructions.
        But if you wish, there is online help.
        Normally, you invoke "edit <filename>".  But if 
        you simply invoke "edit",
        you will be put directly into the online help facilities.   
<p>
If you use Note Pad or editors
        such as MS WORD, you need to beware.  These editors
        inserts all kinds of formatting commands (such as 
        the font information, paragraphing and other commands) 
        among your pure ascii text.  If you simply "save" what
        you type in such an editor, you will get 
        a file that contain these non-printable (non-ascii) characters. 
        TASM will complain.  Instead, you should choose
	(in Note Pad or MS WORD)
        the "save as" command.  In the dialog box, choose the 
        "save as text only" option.
 
<li>
<a name="print_screen">
<b>
How do I print what is on my screen?
</b>
</a>
<br> 
The easiest is to invoke the [PRINT SCREEN] key
        (this is a single key).
        To print the image of the entire screen, press [PRINT SCREEN]
        To print the image of the window that is currently
        active, press [ALT]+[PRINT SCREEN] (this is a combination
        of two keys).
<p>
        Unfortunately, [PRINT SCREEN] seems to
        be disabled in the ACF labs.  An alternative
        was is to use the COPY and PASTE
        functions of the windowing system.  In the MS-DOS COMMAND PROMPT
        window, you can left-click the MS-DOS icon at the left
        corner of the title bar, or right-click the title bar.
        A pull-down menu appears, and you can choose edit->mark.
        You now mark the region of the window you want to copy:
        press the left button at the top-left of the region and drag
        the mouse to the bottom-right of the region, and release mouse.
        Next, use the pull-down menu again and choose edit->copy.
        This saves a copy of the region into a temporary file.  If you
        now open a new file (say "foo")
        in a text editor, you can choose edit->paste to paste the
        contents of the temporary file into "foo".  You may 
        now print "foo" from your editor.
<p> 
        A third option which may work for you is to
        re-direct the output of your program to a file 
        and to print that file.  For instance, to redirect
        the output of your program hw1.exe to the file "foo",
        you invoke 
        <pre>
        :&gt;   hw1 > foo
        </pre>
        Normally, the output of hw1 is sent to your screen
        ("the standard output").  The ">" command tells
        the system to send it to "foo" instead.  (This is
        another idea that originated in UNIX.)
 
<li>
<a name="ps_print">
<b>How do I print POSTSCRIPT files?</b>
</a>
<br> 
Basically, you send the file to a printer that
has a postscript driver.   This is available on
any NYU printer connected to unix machines
(your ACF email account is a unix account).
<br>
        <b><font color=ff0000>
        &gt;&gt;
        For more information on printing postscript at NYU
        <b><a href="postscript.htm">CLICK HERE</a></b>.
        </font>
        </b>

<li>
<a name="ps_what">
<b>What are POSTSCRIPT files?</b>
</a>
<br>
Postscript is a computer language for describing
layout of a document.  In this class, we like to
distribute notes and homework assignments using
postscript files.  To print a postscript file, you
just send the file to any printer that has a postscript
interpreter.  All unix-based NYU machines will be able
to print such files.  We are working to get this ability
in the PC labs as well (it can sometimes be done).
<br>
A postscript file is an ascii file, so you can view it using an editor!
You can recognize a postscript file by its first line,
which is something like this:
	<center>
	%!PS-Adobe-2.0
	</center>
(PS stands for postscript, Adobe is the company that
owns postscript, and 2.0 is the version of postscript.)
However, the rest of the file might not make
much sense to you unless
you know the postscript language (actually, the basics
of this language are easy to learn).  The problem is
that postscript is very low level, much like an assembler
language.  So postscript files are often generated
by some program from other files.

<li>
<a name="unprintable">
<b>Why does my .ASM file contain unprintable characters?
</b>
</a>
<br>
This happens if you create your .ASM file using
a fancy editor like MS WORD.  It will not happen
if you use editors such as <b>edit</b> which is
a very simple editor available under DOS.
You may not realize you have this problem, as it may show
with the TASM complaining about some problems with your .ASM
file (which you think is a problem with your syntax).
To see if you have this problem, try to open your .ASM
file using <b>edit</b> in MS-DOS.  If what you see contains
funny characters, you definitely have this problem.
These funny characters may representing page formatting instructions,
font changing instructions, etc.  
<p>
For related information, see <a href="#editors">editors</a> above.
<p>
The solution (say, from MS WORD) is to save your file
using the "save as" command.  This throws up a dialog window
which contains an option to save your file as "text only".
Choose this option. 
<li>
<a name="set_path">
<b>I want the TASM directory to be automatically
searched.  How do I modify environment variables PATH to allow this?
</b>
</a>
<br>
(a) Here is how to do it in Windows 95:
go to the start menu->control panel.  Click on the
        the system icon.  Choose the environment tab,
        and click on the user PATH variable.
        You can now modify its value in the
	appropriate value box.
        When done, click apply.  Now when you invoke
        MS-DOS or WINDOWS, the new value of the path
        variable will be used. [Note: you can add new
	environment variables this way too]
<br>
(b) You can also do this within the MS-DOS (but
unlike the previous approach, it will not survive a reboot).
Suppose your TASM is found is in Z:\tasm\bin.  To add this
to the path, you type the following to the DOS prompt:
	<pre>
	:&gt; set path = &lt;old-path&gt;; Z:\tasm\bin
	</pre>
where &lt;old-path&gt; is the original value of path.
One way to automate this process is to create a
``bat file'' (say, mypath.bat) which performs this function.
Note that ``path'' will print the value of the
current path variable.  Hence, to put this information
into mypath.bat, do:
	<pre>
      :&gt; path &gt; mypath.bat
	</pre>
Now use an editor to edit mypath.bat, i.e., you insert
``set &nbsp;'' to the beginning of the line, and ``; Z:\tasm\bin''
to the end of the line.  Now you can execute this bat file
each time you need it.

<li>
<a name="bat">
<b>What are bat or batch files?
</b>
</a>
<br>
Batch programs are stored in batch files.
These are ascii files whose extension is ``.bat''
or ``.cmd''.  They contain instructions for the
operating system.  When you execute
such a file (you need not type the .bat or .cmd extension
if this is unambiguous), it is as if you issued those instructions
in your window (or MS-DOS prompt).  It is useful to
use such files to store a set of related commands
that you want to use frequently.  E.g., for this class,
you might want to prepare a batch file containing
the sequence
<pre>
	@@rem my homework batch file
	echo -- Processing Homework Batch File --
	tasm /zi /z hw.asm
	tlink /v hw.obj
	hw.exe
	echo -- Done Homework Batch File --
</pre>
Some general commands are:
<ul>
	<li><b>
	rem</b> (remark or comment)
	<li><b>
	echo</b> (echo just prints the arguments on the screen)
	<li><b>
	call</b> (calls another batch program)
	<li><b>
	if</b> (conditional processing)
	<li><b>
	pause</b> (pauses and asks for any key press to continue)
	<li><b>
	for</b> (runs a specified command for each file in a set)
	<li><b>
	goto</b> (jump to a label)
</ul>	
	
<li>
<a name="nt">
<b>I happen to use an Windows NT system. 
Can you give me some hints?
</b>
</a>
<br>
In many ways, Windows NT (or, WinNT) feels just like
Windows 95 (Win95).
The difference is that WinNT is geared towards multiple
users (like UNIX).
Each user has his or her own ``user profile'' that is
usually stored in the folder C:\winnt\profiles\&lt;usr-name&gt;.
Thus, your will find that your desktop files
and start menu are stored here.  
<p>
<!-- the following  info are found in the file config.nt
-->
Two basic files in DOS, CONFIG.SYS and AUTOEXEC.BAT,
used to configure your system.  In WinNT, these files
are called <b>CONFIG.NT</b> and <b>AUTOEXEC.NT</b>
and are found in the directory /%systemroot%/System32,
where %systemroot% is where WinNT system information
are found (e.g., %systemroot%=WINNT).
Config.nt (not config.sys) and autoexec.nt (not autoexec.bat)
are used to initialize your MS-DOS environment,
unless some different startup files are specified in the
application's PIF.
<p><b>echoconfig</b>:
By default, no information is displayed when MS-DOS environment
is initialized.  To display information, add the
command <b>echoconfig</b> in the config.nt/autoexec.nt files.
<p><b>ntcmdprompt</b>:
When you return to the command prompt from a TSR or while
running a MS-DOS application, WinNT runs command.com
(see <a href=#msdos>above</a>)
This allows the TSR to remain active.  To run <b>cmd.exe</b>
(the WinNT command prompt) rather than command.com,
add the command <b>ntcmdprompt</b> in CONFIG.NT or
other startup file.
<p><b>dosonly</b>:
By default, you can start any application from command.com.
But if you start an application other than MS-DOS application,
any running TSR may be disrupted.  To ensure that only MS-DOS applications
can be started, add the command <b>dosonly</b> to config.nt or
other startup file.



<li>
<a name="mouse">
<b> Can you please give me the basics of mouse programming? </b>
</a>
<br>
Please click <a href=mouse.htm>here</a>.

<li>
<a name=com>
<b> What are .com executable files and how do I produce them?</b>
</a>
<br>
Normally the executable files have the extension <b>.exe</b>.
An alternative form of executables have extensions  <b>.com</b>.
Read section 14.1 in the textbook for general
information this alternative format.  In particular, it
is more compact and useful for small programs.
Section 14.1 also tells you how to create .com files from
the source program, if you were using Microsoft's MASM and LINK.
For Turbo's TASM and TLINK, it is slightly easier.  You use TASM
in the normal way, but you call TLINK with an extra ``/T'' flag.
If your object file produced by TASM is called ``myprog.obj'',
then you issue
	<pre>
	:> TLINK /T MYPROG
	</pre>
to produce MYPROG.COM.  


<li>
<a name="bot">
<b>Bottom of FAQs
</b>
</a>
<br>
Click <a href="#top">here</a> to go to the top of FAQs.
<br>
</ul>

<p>
<hr>
<p>
Bug reports? Suggestions? 
<br>
Please send email to <a href="yap.nyu.edu">yap@@nyu.edu</a>.


</body>
</html>

@


1.10
log
@*** empty log message ***
@
text
@d233 10
@


1.9
log
@*** empty log message ***
@
text
@d3 1
a3 1
	FAQs: V22.0201.002 (fall 97)
d8 6
a13 4
		<h3>
		<font color=ff0000>
		V22.0201, Machine Organization I
		<br>
d16 1
a16 1
		</h3>
d54 1
d59 1
a68 1
</a>
d74 5
d81 1
d194 7
a200 3
PROMPT (or MS-DOS PROMPT, for short).  You can get this
window from the start menu.  To find out more
about DOS, see the next question.
d202 6
d499 3
a501 2
In many ways, Windows NT feels just like Windows 95.  
The difference is that Windows NT is geared towards multiple
d507 31
d539 2
d543 1
a543 3
<b>
Can you please give me the basics of mouse programming?
</b>
d549 22
@


1.8
log
@*** empty log message ***
@
text
@d59 1
d65 1
d67 4
d488 8
@


1.7
log
@*** empty log message ***
@
text
@d87 7
a93 4
MASM stand for Microsoft Assembler.  It is very similar
to TASM, and it is the assembler assumed in the text book.
There are linkers and debuggers associated with TASM
and MASM.
d97 1
a97 1
	For more information, including how to use these software,
a145 1
The Turbo Debugger is called ``TD''.
d155 5
d163 1
a163 1
        For more information,
d293 1
a293 1
        Next, use the pull-down menu again and choose edit->paste.
d296 1
a296 1
        in a text editor, you can paste the
@


1.6
log
@*** empty log message ***
@
text
@d19 2
a20 1
<a href=#tasm>What is TASM, MASM, linker, debugger and other software?
d23 1
a23 1
<a href="#tasm_acf">Where do I find TASM on ACF machines?
d26 1
a26 1
<a href="#tasm_windows">Should I run TASM under Windows?
d29 3
d56 7
d80 1
a80 1
TASM stands for Turbo Assembler, and is the main software
d101 1
a101 1
<b>Where do I find TASM on ACF machines?
d105 3
a107 1
This is not always found under the start menu.
d109 2
a110 2
on the desktop.  Look under "programming"
and "dos programming" under that. 
d112 12
d127 1
a127 1
<b>Should I run TASM under Windows?
d131 29
a159 5
Version 4 of TASM does not seem to work
well under Windows (tell me if you know
how to do this adequately).  I prefer to
work from the DOS prompt.  I believe version 5 works
under Windows.
d161 1
d173 2
a174 3
window from the start menu.  To find out most
about how to work in the DOS environment, see the next
question.
a190 1
<p>
d192 10
a201 7
<b>dir</b> (list the current directory),
<b>cd</b> (change the current directory),
<b>set</b> (set or show environment variables),
<b>type</b> (type the contents of a file),
<b>copy</b> (copy a file)
and
<b>ren</b> (rename a file).
d208 2
a209 1
When you do ``dir'' or ``type'', the output
d220 8
d229 1
d236 2
a237 2
        language programs.  These programs are represented
        as a file of ascii characters.   
d239 3
a241 2
The simplest (and sufficient for this course)
	is to use <b>edit</b> from
d250 2
a251 3
If you are familiar with fancier editors
        such as MS WORD, you can also use them to enter
        your programs.  The problem is that these editors
d254 2
a255 2
        among your pure ascii text.  If you just "save" what
        you type in such an editor, chances are that you get 
d257 2
a258 1
        TASM will complain.  Instead, you should choose (in MS WORD)
d385 2
a386 1
Go to the start->control panel.  Click on the
d395 2
a396 2
<p>
You can also do this within the MS-DOS (but
d398 1
a398 1
Suppose your TASM directory is in Z:\tasm.  To add this
d400 16
a415 3
	<center>
	set path = <old-path>; Z:\tasm
	</center>
d417 57
d475 1
@


1.5
log
@*** empty log message ***
@
text
@d7 9
a15 3
<h3><font color=ff0000>
FAQs: Machine Organization I
</font></h3>
d28 12
d49 2
a50 3
<a href="#set_path">How can I set up my path variable
so that the TASM directory
will automatically be searched?
d53 3
d113 132
d310 2
d318 2
a319 2
<b>How can I set up my path variable
so that the TASM directory will automatically be searched?
d323 12
d338 1
a338 1
	set path = %path Z:\tasm
d341 9
d355 1
a355 1
Bug reports? Suggestions?
@


1.4
log
@*** empty log message ***
@
text
@d28 3
d140 23
@


1.3
log
@*** empty log message ***
@
text
@d47 3
a49 3
assumed for this class.  The most current version
is 5.0 (but older versions will probably be OK
for this course as well).  It is provided in the PC labs.
@


1.2
log
@*** empty log message ***
@
text
@d61 1
a61 1
	<b><a href="postscript.htm">CLICK HERE</a></b>.
d98 1
d102 1
a102 1
        <b><a href="tasm.htm">CLICK HERE</a></b>.
@


1.1
log
@Initial revision
@
text
@d3 1
a3 1
	ACF software information
d5 6
a10 1
<body color=ffffff>
d13 54
d69 2
d78 1
d81 2
d86 2
a87 1
work from the DOS prompt.
d90 14
a103 3
<b>HINT: set up your path so that the TASM directory
will automatically be searched.
</b>
d106 33
a138 2
<b>If you have further suggestions for making
the lab experience more enjoyable, please let me know!
d140 8
d150 6
d157 1
@
