NQC 2.0.2 Readme
----------------

Please send bug reports to dbaum@enteract.com.  Be sure to include
details about what platform you are running nqc on and a sample
file that demonstrates the bug if possible.

For updates and additional documentation, visit the NQC Web Site:
http://www.enteract.com/~dbaum/nqc


Getting started
---------------

Download the appropriate compiler (nqc or nqc.exe) and put it where
your shell can find it as a command.

The IR tower should be connected to your modem port (macintosh) or COM1
(Win32/Linux). The IR tower should be set for "near" mode (small triangle).
The RCX should also be set for this mode, and firmware must already be
downloaded.

Compile and download the test file using the following command line:

nqc -d test.nqc

The test program assumes theres a motor on output A and a touch sensor on
input 1.  It turns on the motor and waits for the switch to be pressed,
then it turns off the motor and plays a sound.

If you want to use a different serial port, you can set the RCX_PORT
environment variable to the serial port name.  Here are some examples:

Mac/MPW printer port:
	set -e RCX_PORT b

Win32 COM2 port:
	set RCX_PORT=COM2

Linux:
	The syntax for setting environment variables is shell specific.  By
	default nqcc uses "/dev/ttyS0" as the device name for the serial port.
	If you are using the second serial port, then "/dev/ttyS1" should
	work.  Other device drivers may or may not work depending on if they
	implement the expected ioctl's to setup the baud rate, parity, etc.


Note that NQC no longer requires the RCX API include file (rcx.nqh).  However,
for reference purposes copies of the 1.3 and 2.0 api files (rcx1.nqh and
rcx2.nqh) are included in the NQC distribution.


version 2.0.2
-------------

Fixed a bug which caused NQC to crash when compiling programs containing
functions with certain errors in them.


version 2.0.1
-------------

Fixed a bug that caused the compiler to crash when more than 32 variables
were used in a program.

The Win32 version no longer aborts due to serial driver errors - the retry
algorithm will remain in effect.  This makes download of very long programs
much more reliable (especially under WinNT).

The retry algorithm is now more forgiving if the IR tower doesn't echo the
serial data properly.  This makes very long downloads a little more reliable.


version 2.0
-----------

First official release of NQC 2.0
