CSCI 240 - Preparing Files to Hand In on Disk

This document contains instructions on how to put your C++ program files on a 3.5 disk (from the NIU computer labs) for backup.  These methods will place both the source code and the executable on the disk.  Similar methods will allow you to place them on a USB drive.

Method 1 - Creating Files on the Network f: Drive, then copying them to the a: disk

1. In the Quincy C++ IDE, type in your program. Before you try to compile it, go to File/Save and type in the name of the program's source code. For assignment 1 it should be assign1.cpp

This will save your "source code" on the computer lab network f: drive. (This is your personal hard disk space on the lab network - however, you should still make copies of all your work on a diskette in case the lab disk crashes.)

2. Compile your program. If you have errors, fix them.

3. Once the program compiles with no errors, do File/Save again to save the most recent copy.

4. Run the program. If there are errors, fix them, recompile, and re-run until you get the final correct version.

5. Do File/Save again to save the final correct version.

At this point you have the following files on f:

• assign1.cpp
• assign1.exe

6. Open Windows Explorer and access the f: drive ( a lab assistant can help if you don't know how)

7. Check that the files are there

8. Put a diskette in the disk drive.

9. Drag the files with the mouse from f: to a: ( a lab assistant can show you how to do this, too)

11. Finally, to print your source code, use File/Print in Quincy with the source code window open.

Method 2: Saving Files directly to a:

1. Get into the Quincy C++ IDE and open or type in a program.  After you have saved it to your hard disk and you want to save a second copy on the floppy (a:)

2. Use File/SaveAs, specifying a:assign1.cpp (or a:assign2.cpp, etc.) as the location and name.

From here on while you are logged in, File/Save will reSave your source code file to the a: diskette.

4. Now when you compile, build, and execute the program, it will write the .exe file to your a: diskette.  Note that there may not be enough room on your floppy for everything in some cases.  See the notes below.

Notes:

• if you compile and build with debugging information, the .exe may exceed the size of the floppy.  To make it smaller by truning off debugging information, go to Tools/Options/Build and uncheck "Debugging Information added"
• it takes a few seconds to write to the a: diskette, so compile/run performance will be a bit slower.