Welcome to the BOINC Readme file.

What is it about?
I just got tired of seeing the same old questions on the message boards. It also became a problem to find certain things that you know you saw in a post somewhere, but for the life of you, you can't remember where...

Below you will find a draft edition of the README file. Please review it and post any contributions / comments / criticisms to the BOINC message boards.

There are a few things missing:


The rest of it is up for general improvement.
Some Q&A items have been moved over to the BOINC FAQ. Q&A items here will be limited to those pertinent to instalation and set-up issues.
Also I'm sure it's peppered with spelling & grammar mistakes. It's also likely to have a few technical issues that I've got completely wrong. The hyperlinks will have to be checked as well. I'm more worried about content than style at the moment.

The story so far....
As far as I'm concerned this README is by BOINC, for BOINC and belongs to BOINC. You won't find my name in it. ;-)
I've tried to keep it reasonably light-hearted. If possible, it would be nice to keep it that way. :)
The home of this file is temporary at the moment and I'm considering a more permanent one. Watch this space for details.

Without any further ado...


README for BOINC

Readme revision 0.05 (31/03/2004)

Table of Contents

1. Introduction
1.1 What is BOINC?
1.2 C'mon give me the fast answer?
1.3 Where do I get BOINC?
1.4 Where can I get help?

2. General Information
2.1 Getting started
2.2 Updating your preferences
2.3 Posting questions
2.4 Contributions
2.5 Credit for work done
2.6 Participating in multiple projects

3. Windows
3.1 Installation
3.2 Using BOINC
3.3 Known Issues
3.4 Frequently asked questions(FAQ)
Q.) Why does it take so long to process a WU?
3.5 Debugging help

4. UNIX
4.1 Installation
4.2 Using BOINC
4.3 Known Issues
4.4 Frequently asked questions(FAQ)
Q.) How do I use a proxy with BOINC on linux?
Q.) How do I pre-empt the next scheduled result upload?
Q.) How do I pre-empt the next scheduled RPC?

5. Macintosh
5.1 Installation
5.2 Using BOINC
5.3 Known Issues
5.4 Frequently asked questions(FAQ)

6. Anonymous
6.1 Installation
6.2 Using BOINC
6.3 Known Issues
6.4 Frequently asked questions(FAQ)

7. Frequently asked questions(FAQ)
Q.) Is the source code available?
Q.) How can I get more debug information to troubleshoot a problem?
Q.) What happened to Astropulse?
Q.) What does MD5 check failed mean?

8. Glossary
9. Disclaimer
10. Document History


1. Introduction

1.1 What is BOINC?
BOINC is an acronym for Berkeley Open Infrastructure for Network Computing.

It is a software platform for distributed computing using volunteered computer resources.
For an overview of BOINC, please visit the BOINC homepage at
http://boinc.berkeley.edu. You'll find a lot more detail and up to date information on the whole BOINC environment at the BOINC homepage.

The BOINC framework is presently being beta tested, together with the Astropulse and Setiathome projects. If you have heard of the SETI@home project, you could refer to BOINC as SETI@home II. To find out more about SETI@home, please visit the SETI@home website at http://setiathome.ssl.berkeley.edu

Please be advised that as Beta software, BOINC is currently still under development. What this means is that some parts of the system may work OK, and some may not work OK. If you would like to contribute to the testing of the framework, please continue and become part of the community, but only if you're sure that you can handle a few aggravations every now and then.


1.2 C'mon give me the fast answer?
Sure. Your PC spends most of its time doing nothing but increasing your electricity bill. Download and install this software and apart from having a new heater, you can contribute to the magical world of science. When you're working, this software is doing nothing, but when you're not, it's analysing data for the science project of your choice. You do want to help find ET, don't you?


1.3 Where do I get BOINC?
BOINC can be downloaded from the "Download BOINC" link on the BOINC Beta Test homepage
http://setiboinc.ssl.berkeley.edu/ap/, but you will need to create an account first. BOINC is currently available for the following platforms:

Before you dive in and start downloading, please read through the general information section and then refer to the relevant section of this readme file for the platform that you are interested in.


1.4 Where can I get help?
So you've hit a snag have you? Don't worry, help is at hand.
You should look for help in the following places:

This document (First place to look)
The answer you are looking for might be closer than you think. Have a look through the FAQ sections of this document and see if your problem has already been covered. You are already here after all.

The BOINC FAQ (Second place to look)
Should you not find an answer to your question or problem in this document, have a look through the BOINC
FAQ. Chances are that someone has already asked the same question and it has already been answered there.

BOINC Message Boards (Third place to look)
Review the BOINC questions and answers section for your platform on the BOINC messageboards. If you've searched and are unable to find a suitable answer or solution, then you could post a question with a new topic, but please review the posting questions section of this document first. You won't make any friends in the community if you post a question that's already covered in this document, so please think before you post. On the other hand, if you do find the answer you were looking for, and think it should be included in this document or in the FAQ document, please let us know.
Details on how to do that are covered in the posting questions section of this file.


2. General Information

2.1 Getting started
First thing you need to do is create a BOINC Beta Test account. You do that from the "Create Account" link on the BOINC Beta Test
homepage. Once you have done that, the project URL and Account key are emailed to you. You did use a valid email address, didn't you?

You only need one account for all the platforms and all your PC's. You do not need one account for each platform or each PC you are going to use.

Now that you've created an account, you can download the software for your platform. Refer to the "Where do I get BOINC?" section above, then come straight back here.

While you're waiting for the software to download, have a read through the "Getting Started" section of the BOINC Beta Test homepage, then read through the Installation section of this file, for your platform.


2.2 Updating your preferences
There are no preferences that you can set in the core client itself. All of your preferences are configured and stored on the project homepages. To get access to these preferences, you must log in to your account from the project homepage. Have your Account key handy, because this is your ticket to get in. If you have lost it, it can be emailed to you by selecting the necessary link from the login page.

TODO: Description of all the possible preferences goes here.


2.3 Posting questions
Up to now, the posting of questions on the message boards has been a sometimes messy affair!
The message boards are broken into two distinct categories:

Too many times, people have posted questions in the message boards, instead of the questions/problems section. (Even I'm guilty too) So if you do decide to post a question, lets try and keep the questions in the questions area and the discussions in the message boards area.
Of course, if you begin your post... "I would have posted this question in the question section, but there isn't a suitable section..." then you may be forgiven, provided you are being truthful. We could always lobby for an extra section, provided it is necessary.

Should you post a question that has already been covered in this readme or in the FAQ, without referring to the readme or FAQ and without explaining why you think your question hasn't been answered in those documents, your post will at worst be ignored and at best result in a reply like, JQ - Read the readme / FAQ.

So what is suggested?
Message boards are a pretty much free-for-all when it comes to topics, however to help everyone find the correct answer to your/their problem, you can assist everyone by following these guidelines when posting a question/problem:

Topic subject:
Try to keep it uniform.
Start with "CC" if the problem relates to the core client, "SAH" if it relates to SETI@home, "AP" if it relates to Astropulse, FAQ if you're commenting on the FAQ or "README" if you're posting about this file.
Next, use the version number of the program/document involved, eg. "2.28" followed by a brief description of the problem.
For instance,
"CC 2.25 : Crashes when returning result and no Internet connection"

Topic body:
Type as much as you want here that will describe the problem, what you have done to fix it (if anything) and the results of what you've done.
Please don't post your whole stdout.txt or stderr.txt file, unless it's really short. Rather look through it and post the parts that show the error in progress, and any other parts before and after the error that are relevant to the problem.

Be helpful towards those that are trying to help you. Post as much info about your system that you feel secure to post. Don't post your account key, IP address, root password or things that you are not comfortable sharing with the whole world.
For instance,
CC: 2.25
SAH: 2.23
OS: Windows XP SP1
CPU0: Intel P4 2.6Ghz
CPU1: AMD P4 2.6Ghz
RAM: 1024MB
DISK: 80GB / FREE: 2GB


2.4 Contributions
No, not that kind of contribution. We're not asking for money, or maybe we are, but not here.
Just by downloading and running the BOINC framework you are considered a contributor. We all contribute in some way or another. The BOINC team thanks you for your support.


2.5 Credit for work done
After you have completed a work unit, your computer will calculate what it believes that work is worth in Cobblestones. This is referred to as "credit". Sorry, but you can't transfer it to your AmEx card, it's not that kind of credit. It doesn't stop there though. The credit that your system claims is not automatically granted. The same work unit is passed to other users for them to process and for their system to claim credit. If you are the first to return a particular result, your credit is termed "pending", until other people have also returned results for the same work, and the BOINC server has validated the results. All users that have returned valid results for the work are then granted the credit that is equivalent to the lowest claimed.


2.6 Participating in multiple projects
Yes, it is possible to share your computing resources with more than a single project. You can join multiple projects and then allocate your resources accordingly. The technical issues involved in doing this are the domain of John. You can read all about it in this
thread.I'm not re-inventing the wheel. :-)


3. Windows

3.1 Installation

3.1.1) Prerequisites
You must have administrative privleges on the machine on which you are installing. This is necessary to update the system files and to install the screensaver in the system folder.

3.1.2) Installing BOINC is easy.
Double click / run the downloaded version of BOINC and the setup program is launched automatically. Follow the prompts and at the end decide if you wish BOINC to start automatically, when a user logs in, and if you'd like to start BOINC now.


3.2 Using BOINC

3.2.1) First run
The first time you start BOINC, you will be asked for the project URL and account Key. These were mailed to you when you created the account. You did create an account, didn't you? If not read the "Getting Started" section of this readme now, because you're going nowhere without an account.

Note: You must be connected to the Internet when you start BOINC for the first time. If you need to operate through a proxy, cancel the request for an URL and key, then read through the proxy section below, then read through the section on attaching to projects.

3.2.2) Proxy
If you operate behind a proxy, you can configure this in the core client through the "Settings -> Proxy Server..." option. You can choose between HTTP proxy, or SOCKS proxy and set the necessary options accordingly. Currently it is not possible to connect through an HTTP proxy that requires password authentication. This feature is on the feature list.

3.2.3) Attaching to a project
If you have detached from a project, are connecting for the first time through a proxy, or would like to join another BOINC project, you will need to attach through the "Settings -> Attach to project..." option. You will be asked for the URL and account key for that project. Don't have this info? Then read the getting started section of this readme.

3.2.4) Application Layout
The BOINC application has 5 tabs:

3.2.4.1) Projects
This tab shows the names of projects to which you have attached and some data on the project. If you right-click on the project name, you are presented with four options related to the project:

3.2.4.2) Work
This tab lists your work in progress for the various projects that you have attached to.
The status of a work unit could be:

3.2.4.3) Transfers
This tab shows any transfers that are in progress, or that have failed to complete, otherwise it is empty. If a result upload has failed, you can right-click on the work unit with this status, you will have the option to "retry now".

3.2.4.4) Messages
All the messages regarding the current and past state of BOINC, since the last time it was started, are being logged to this screen. This should be your first step in troubleshooting a problem. The message files are currently being overwritten at each restart, however there is a task being addresed that will allow archiving of these files.

3.2.4.5) Disk
This tab gives you a graphical and textual interpretation of your total disk usage and what proportion is being used by the BOINC framework and its projects.

3.2.5) General Operation
After you have installed BOINC and attached to a project, the BOINC core client will begin transferring files to your system.
These are typically:

3.2.5.1) Project executable
The project executable is the program that actually does all the work to process the work unit. In windows these files will typically have the extension ".exe".

3.2.5.2) Project executable debugging files
The debugging files are files that are automatically downloaded (if present) to assist in troubleshooting problems that are appearing within the project executable. These will not always be present. These will typically have the extension ".pdb".

3.2.5.3) Project executable required libraries
The project executable may require some additional files, called libraries, that may not be present on your system, or they may be present but not useable. These will typically have the extension ".dll".

3.2.5.4) Work Unit
This is what it's all about. The work unit is a small portion of a large stream of data that has been recorded. If it was possible for the people recording the data to process the data stream easily, this project would not exist. Instead, the stream is broken down into small pieces that can be analysed within a set period of time and passed out to millions of users around the world. These users, of which you are one, will contribute their computer's unused CPU cycles to analyse the work unit and report the results back to the project servers, which will in turn analyse the results and record any interesting features therein. What a mouthful!

All of the activity will be completely invisible to you unless you do not have a continuous link to the Internet, or a problem is encountered. Without a continuous link, you will be required to keep an eye on the application to upload results and download new work as required. After BOINC is installed and operating, a small icon will be placed in your system tray. This icon will change to reflect the current state of BOINC, so that you can see at a glance what is happening. A blue (I) indicates that there are new messages, but not a fatal problem, whereas a red (I) indicates that BOINC has experienced a problem, and needs your attention, perhaps to download more work.


3.3 Known Issues

3.3.1) General (All versions of Windows)
On some hosts, the show graphics works fine.
On some hosts, the show graphics results in a blank screen. - Possibly fixed with SAH 2.31
On some hosts, the show graphics causes the WU to abort abruptly.- Possibly fixed with SAH 2.31

3.3.2) Windows NT 4.0
The screensaver does not work.

3.3.3) Windows 2000 Advanced Server
The screensaver is installed in the user's windows folder, and not in the system folder.

3.3.4) Windows XP
The core client does not suspend while on batteries.
This appears to be related to the web prefernces and usually after a project detach. If you have this problem, update/save your prefernces on the web and then update prefs from your client.


3.4 Frequently asked questions(FAQ)

Q.) Why does it take so long to process a WU?
A.) Because the windows client currently contains debugging code to help find and report problems. This will be removed once it is no longer necessary.


3.5 Debugging help

The windows platform is the one currently undergoing the most active development work. The problems being experienced are quite obscure and due to this there is a large initiative underway to identify and squash them. To aid the developers in finding out the circumstances that are causing the problems, they have turned to debugging for assistance.
The current debugging takes the following forms:

3.5.1) Compiler debugging
This type of debugging is turned on when the development team compiles (creates) the BOINC application and the SAH project executable. This is the type that is responsible for the lengthy time that it takes to process a workunit. You can not do anything to avoid this, unless you download the source and compile it yourself.

3.5.2) BOINC Core client symbol files
These files are not downloaded automatically. To download these files you will need to click on the 'Download debugging files' link on the BOINC Beta homepage. The files are quite large and are therefore compressed into a single zip file. After you have downloaded the compressed file, you will need to decompress them with 'unzip', 'winzip' or some such utility and place the decompressed files (extension .pdb) into your BOINC application folder. This is usually '?:\Program Files\BOINC' unless you changed the installation path during the BOINC installation process. That's it. Now, if a problem is encountered, Dr Watson will be able to locate the debugging files and provide more human readable information in the dump file, which will be more beneficial to the developers.
Note:
The downloading of these files is entirely optional. You do not have to download them if you do not wish to do so, although having them present does assist the developers.
Each time a new revision of the BOINC core client is released, the previous debugging files are useless and you will need to download the new set of debugging files.

It has been asked "Why not just include the debugging files in the application package?"
The feelings on this are:
a.) The debugging is optional;
b.) Including the debugging files would result in a much larger application package, which may be detrimental to users with limited bandwidth.

3.5.3) Project executable symbol file
This file is automatically downloaded, together with the project executable and work unit when you attach to a project, do a project reset, or when a new revision of the project executable is released and you request new work.


4. UNIX

4.1 Installation

4.1.1) Prerequisites
There are no prerequisites to install the unix cli. You do not need root permissions to run BOINC. You only need create and write permissions in the directory from which you intend to run the application.

4.1.2) Installing BOINC is easy.
You should create a directory which will be your BOINC home directory, then move or copy the compressed file to this directory. Unzip the BOINC application that you downloaded. e.g. 'gzip -d boinc_version-platform.gz'. Before you can start the application, you must make it executable. Probably a 'chown 700 boinc-application-name' will be the safest.


4.2 Using BOINC

4.2.1) First run
Start the boinc application. If you do not have "." in your PATH, then don't forget to prefix the application name with a './' i.e. './boinc-application-name' The first time you start BOINC, you will be asked for the project URL and account Key. These were mailed to you when you created the account. You did create an account, didn't you? If not then RTFM. You're a unix user now, don't let the side down!

Note: You must be connected to the Internet when you start BOINC for the first time. If you need to operate through a proxy, cancel the request for an URL and key, then read through the proxy section below, then read through the section on attaching to projects.

4.2.2) Proxy
If you operate behind a proxy, you have a little bit of work to do. There isn't a command line option to configure a proxy, so read the FAQ on how to configure a proxy below. You can choose between HTTP proxy, or SOCKS proxy and edit the necessary options accordingly. Currently it is not possible to connect through an HTTP proxy that requires password authentication. This feature is on the TODO list.

4.2.3) Attaching to a project
If you have detached from a project, are connecting for the first time through a proxy, or would like to join another BOINC project, you will need to attach through the command line option "-attach_project". You will be asked for the URL and account key for that project. Don't have this info? Then RTFM! You're not really into this unix thing are you?

4.2.4) Application Layout
You don't really have any layout to speak of, unless you are playing with one of the GUI's and I haven't done that, so I'll stick with what I know for now. Instead of layout, you have some basic command line options to play with.
These are:

4.2.4.1) -help
This shows the available command line options. BOINC will exit and no processing takes place.

4.2.4.2) -version
This will output your cli version information. BOINC will exit and no processing takes place.

4.2.4.3) -show_projects
If you are attached to any projects, this will display the project names and their associated URL's. The URL is handy for further command line options listed below.

4.2.4.4) -attach_project
This will attach you to a project. You will be asked for an URL and an account key of the project. If successful, the executables, any libraries and the work units required for the project are downloaded, and presto, processing starts.

4.2.4.5) -detach_project [URL]
This will detach you from the project specified by the URL. Warning...clears any incompleted work and completed work that has not been uploaded. It also deletes any files that were downloaded for that project.

4.2.4.6) -reset_project [URL]
This will clear any work that is currently in progress, delete any incompleted work and completed work that has not been uploaded and all files downloaded for the project. You would probably use this if you are having problems trying to process work on your system. BOINC will exit and no processing takes place.

4.2.4.7) -update_prefs [URL]
If you have changed your preferences on the server and need to get your client updated, use this option.

4.2.4.8) -run_cpu_benchmarks
This is not something you will do very often. Perhaps only if you have changed your hardware. RAM, CPU, etc.

4.2.5) General Operation
After you have installed BOINC and attached to a project, the BOINC core client will begin transferring files to your system. These are typically:

4.2.5.1) Project executable
The project executable is the program that actually does all the work to process the work unit.

4.2.5.2) Project executable required libraries
The project executable may require some additional files, called libraries, that may not be present on your system, or they may be present but not useable.

4.2.5.3) Work Unit
This is what it's all about. The work unit is a small portion of a large stream of data that has been recorded. If it was possible for the people recording the data to process the data stream easily, this project would not exist. Instead, the stream is broken down into small pieces that can be analysed within a set period of time and passed out to millions of users around the world. These users, of which you are one, will contribute their computer's unused CPU cycles to analyse the work unit and report the results back to the project servers, which will in turn analyse the results and record any interesting features therein. What a mouthful!

All of the activity will be completely invisible to you unless you do not have a continuous link to the Internet, or a problem is encountered. Without a continuous link, you will be required to keep an eye on the application to upload results and download new work as required. You will need to watch the output generated by the BOINC core client to see if any action is required on your part. Both standard output and standard error streams are directed to the terminal from which you started BOINC. If you would prefer to redirect stdout and stderr, please review the FAQ questions below.

Some functions available to the BOINC core client for windows, are not yet implemented in the unix cli. For example, the ability to retry result uploads and force RPC requests. This does not mean that they are impossible, you just need to do a little extra work. Below are two of the ones you will most likely come accross. Put on your unix wizard hat before continuing...

How to upload a workunit that has completed, and not have to wait until the next scheduled update: See the FAQ section below.

How to send an RPC without having to wait until the next scheduled RPC update: See the FAQ section below.


4.3 Known Issues

4.3.1) gethostbyname problem
You may get a segmentation fault or may be unable to connect due to problems resolving hostnames. This is related to static vs. dynamic linking of libraries on the unix platform, and is currently being addressed.


4.4 Frequently asked questions(FAQ)

Q.) How do I use a proxy with BOINC on linux?
A.) Add the following lines to your client_state.xml file
< use_http_proxy/ >
< proxy_server_name > your.ip.address.here < /proxy_server_name >
< proxy_server_port > yourproxyport < /proxy_server_port >

Q.) How do I pre-empt the next scheduled result upload?
A.) Try the following:
Stop the BOINC core client.
Edit the client_state.xml file.
Search for the XML tags <next_request_time>ZZZ<next_request_time/>
Replace the ZZZ value with 0.
Start the boinc client with the '-update_prefs [URL]' option.

Q.) How do I pre-empt the next scheduled RPC?
A.) Try the following:
Stop the BOINC core client.
Edit the client_state.xml file.
Search for the XML tags <min_rpc_time>ZZZ<min_rpc_time/>
Replace the ZZZ value with 0.
Start the boinc client with the '-update_prefs [URL]' option.


5. Macintosh
5.1 Installation
5.2 Using BOINC
5.3 Known Issues
5.4 Frequently asked questions(FAQ)


6. Anonymous

6.1 Installation
If you're reading this, you should be writing the installation instructions for your platform. If you disagree, chances are you're in the wrong section.


6.2 Using BOINC
6.3 Known Issues
6.4 Frequently asked questions(FAQ)


7. Frequently asked questions(FAQ)
Here you are likely to find the questions that do not apply to any specific platform.


Q.) Is the source code available?
A.) Yes, the source code for the BOINC framework, the SAH client and AP client is available. You can download the BOINC source from here
http://boinc.berkeley.edu/source/, the SAH source from here http://boinc.berkeley.edu/seti_source/ and the AP source from here http://boinc.berkeley.edu/ap_source/. Latest snapshots are in the "nightly" directory, but be warned that this source might not always compile cleanly. This is due to the fact that the source is constantly under development.


Q.) How can I get more debug information to troubleshoot a problem?
A.) Use the log_flags.xml file, with various options.
Stop the BOINC core client.
Create a file in the BOINC folder/directory called 'log_flags.xml' and containing the following mandatory two lines:
<log_flags>
</log_flags>
Then between these two lines, add any combination of the following options:
<task/>
<file_xfer/>
<sched_ops/>
<state_debug/>
<task_debug/>
<file_xfer_debug/>
<sched_op_debug/>
<http_debug/>
<time_debug/>
<net_xfer_debug/>
<measurement_debug/>
<poll_debug/>
Start BOINC core client.
Depending on what options you chose, a little or a LOT of debug information will be written to the stdout text file.
Note: This detail is not written to the Windows Messages tab.
I hope to bring you more detail on exactly when to use which option, but if you review the output, you can easily see what output is generated by each debug option. If you do not want to log that particular information, then simply stop the client, remove that option from the file and restart the core client again.
Warning: Some private site/host specific information may be recorded during the debug excercise. You are strongly advised to read through the files generated *before* posting them to the message boards. Some information may be recorded that you do not want the whole world to see.
In addition, you will not make any friends if you post a 500kb output file. Try and locate the areas where the error occurs, then post the error and perhaps the 10 or so lines above and below the error. Do not discard the file, because you may be asked to email it to one of the developers if necessary.


Q.) What happened to Astropulse?
A.) The development team are currently focused on eliminiating bugs in both BOINC and SAH, therefore Astropulse is currently in limbo. It will be picked up again once more development resources become available.


Q.) What does MD5 check failed mean?
A.) To ensure that you receive an accurate copy of the data sent by the servers, each file is given a special check sum, based on the MD5 algorithm. After the BOINC client has completed the download of a file, it compares the checksum of the file received against the one that is on the server and if they are the same, then BOINC knows that the files are the same. This is good. If the checksum is different, then BOINC knows that the file it received is bad and records the MD5 checksum failure in the message log.
If you get a MD5 failure on any of the files that BOINC downloaded, then you must do a 'project reset' to get the correct files. BOINC will be unable to process any work until it has received all the files correctly.


8. Glossary
ALPHA - Use at your own risk.
AP - Astropulse.
BETA - Use at your own risk, but you're not the first to do so.
BOINC - Berkeley Open Infrastructure for Network Computing.
CC - BOINC Core Client.
CLI - Command Line Interface. Non GUI version of BOINC.
COBBLESTONE - The unit of measure of work done in BOINC.
CORE CLIENT - The BOINC framework executable.
CPU - Central Processing Unit / Processor.
CS - Cobblestone.
FAQ - Frequently Asked Question.
GUI - Graphical User Interface.
JQ - Newbie.
MPC - Multiple Project Control
OS - Operating system.
PLATFORM - Operating system.
RAC - Recent average credit.
RAM - Random Access Memory / Main Memory.
RPC - Remote Procedure Call.
RTFM - Read The Manual. For F, use the first 'F' word that comes to mind. Usually 'Fine'.
SAH - SETI@home or setiathome.
SETI - Search for ExtraTerrestrial Intelligence.
WU - Workunit, a piece of the work being processed.


Some things you might come across on the message board posts:
LOL - Laugh out loud.
n00b - An Internet Newbie / Person unfamiliar with the Internet.
ROTFL - Rolling on the floor laughing.
ROTFLMAO - Rolling on the floor laughing my a** off.


9. Disclaimer
I wrote it, I won't deny that. Even the spelling and grammar misteks are mine.
If you use any of the information in this readme and, as a result, you throw a brick through your computer screen, I won't buy you a new one. In fact, I won't accept any responsibility for anything that you do after reading this document, so don't even bother wasting your breath or losing sleep about it. If anything in this document works, great. If not, tough luck, chalk it up to a bad life experience.
If you do find any inaccuracies, or would like to contribute something to the document, no problem, your input will be appreciated provided it makes sense. As a reward for your efforts, you too can be protected by this disclaimer.


10. Document History
2003-03-31: rev 0.05
Updated unix reset details.
Update to preamble.
Included references and links to the FAQ document.
Removed duplicate FAQ's that are now in the FAQ document.
Linked to John's post regarding MPC.
2003-03-27: rev 0.04
More General Q&A.
Added a bit of an explanation about windows debugging.
2003-03-27: rev 0.03
First public release.
2003-03-23: rev 0.02
Convert to HTML and now it's time for some input from the rest of the team...
2003-03-11: rev 0.01
So I got tired of seeing the same old questions and answers on the messageboards and figured that it was time to put what I have learned so far into a document for everyone else to criticize. Hopefully, it will allow the developers more time to focus on their development work, and reduce the duplication on the message boards.