CSCI 1300, Section 100
Software Notes

Acknowledgement

We owe thanks to Professor Michael Main who assembled the software package that we use for CSCI 1300 as well as the documentation and style guide he has put together.

Description

This page provides information on the programmer's tools for CSCI 1300 at the University of Colorado. All tools are free and may be used by programmers here or elsewhere. The tools include:

Minimalist GNU Windows 32 Tools with
- g++ (Version 2.95.2),
- gdb (Version 4.18),
- make (Version 3.77), and more from bintools (2.9.4) and elsewhere: addr2line, ar, as, awk, bison, c++, c++filt, cc, cmp, dlltool, echo, ed, egrep, ex, fgrep, flex, flex++, g++, gasp, gawk, gcc, gcov, gdb, genclass, gperf, gprof, grep, gunzip, gzip, ld, m4, make, nm, objcopy, objdump, protoize, ranlib, red, rm, sed, size, strings, string, tail, tar, unprotoize, wc, windres, zcat.
Windows Emacs editor
Elvis vi editor
BGI graphics library for the Gnu compiler

Original sources are listed at www.cs.colorado.edu/~main/cs1300/authors.html

Installation Notes

Download these two files to the top level of one of your hard drives. If you are working at home, this will probably be the C drive. If Windows asks you what to do with the download, chose "Save to disk", and when the "Enter name of file to save to..." window pops up, left click in the "Save in:" box and choose the appropriate drive (C: or whatever). Make sure you are downloading to the root directory of the drive.

The first of these files is large (over 20MB) so downloading with a phone modem will take a few hours.

Once you have the two files, you must start up a DOS Command Prompt window. If you don't see the Command Prompt icon on the Start|Programs menu (Windows 98) or the Start|Programs|Accessories menu (Windows XP), then you can start it via Start|Run... and entering "command" in the pop up window. Ask someone to help you create a short cut for your desktop. Once the Command Prompt window is open, type the following series of commands. If you copied the two files to a drive other than C:, then use that drive letter in these instructions:

C:
CD \
unzip -q cs1300.zip
del cs1300.zip
C:\cs1300\gocs

After running the unzip command, you should have a new directory (called C:\cs1300). If you get an error when you type the unzip command, it is probably because you did not download the files to the right directory (i.e., to C:\ ). Ask someone for help to move the files to that directory. (You can use the Windows Start|Search menu to find out where the files were downloaded.)

Now the software is installed. In the future, each time you open an MS-DOS window, you need to tell the operating system about the software by running just this one command:

C:\cs1300\gocs

See the CSCI 1300 hints for advice on setting up your Command Prompt to avoid typing "C:\cs1300\gocs" each time you open a window.

What the Installation Provides

After the installation is complete, you can execute any of these commands from an MS-DOS command line:

addr2line, ar, as, awk, bison, c++, c++filt, cc, cmp, dlltool, echo, ed, egrep, emacs, ex, fgrep, flex, flex++, g++, gasp, gawk, gcc, gcov, gdb, genclass, gperf, gprof, grep, gunzip, gzip, ld, m4, make, nm, objcopy, objdump, protoize, ranlib, red, rm, sed, size, strings, string, tail, tar, unprotoize, wc, windres, zcat.

Documentation

Documentation on GNU tools including g++, gdb, make, etc.::: HTML documentation in www.cs.colorado.edu/~main/cs1300/doc/gnu1/; Windows help documentation in www.cs.colorado.edu/~main/cs1300/doc/gnu1/
Geoff Voelker's Emacs for Windows documentation in: www.cs.colorado.edu/~main/cs1300/doc/emacs/
Steve Kirkendall's Elvis (vi) documentation in: www.cs.colorado.edu/~main/cs1300/doc/elvis/
Winbgim (BGI graphics library for Windows) by Konstantin Knizhnik, Michael Main and Mark Richardson has documentation in: General use: www.cs.colorado.edu/~main/cs1300/doc/bgi/bgi.html; Complete function list: www.cs.colorado.edu/~main/cs1300/doc/bgi/

OUT OF ENVIRONMENT SPACE: How To Fix This Problem

Running or installing DOS or Windows tools can sometimes result in the message "Out of Environment Space." This section describes three ways to usually solve the problem.

Method 1: For Microsoft Windows 95/98: You might need to modify the desktop shortcut to Emacs as follows:

Right-click on the emacs shortcut on the desktop, and select Properties.
You probably want to set the Close on Exit checkbox to be set. This will close the extraneous DOS prompt used each time to launch Emacs.
Set the input field under the Memory tab labeled Initial Environment to be 4096.
Click Ok.

Method 2: Changing the DOS Session Properties This method will work if you don't need too much extra space and you are running the tools from the MS-DOS prompt.

Start the DOS session and make sure that it is a window rather than full-screen. If it is full-screen, then press Alt-Enter to change it to a window.
Click on the MS-DOS icon in the top left corner of the window.
Select Properties from the pop-up menu.
Select the Memory tab from the command box.
Click the arrow on the Initial Environment box. Move down in the box as far as possible (by clicking the downward arrow). Click on the biggest number that you see in this box.
Click OK in the command box.
Click OK in the MS-DOS Prompt information box.
Stop the DOS Session by clicking the X in the top-right or by typing the command "exit".
Restart a new DOS session and try running your commands again.

Method 3: Changing the config.sys file This method works for Windows 95. I'm not certain whether it also works for later versions of Windows.

From a DOS prompt, use the edit command to open the file C:\config.sys.
Find a line that begins: shell=...
Within this line, find a parameter that starts /e:... and increase the size of the number after the /e:. For example, I increased mine to /e:4096.
If there was no /e:... on your line, then you can add /e:4096 at the end of the line. If there was no shell= line, then you can add this one:
```
     shell=C:\command.com /e:4096 /p
```

Uninstallation Notes

To uninstall this software package, simply delete the CS1300 directory from your hard drive.

CSCI 1300, Section 100 Software Notes