Notes:

• Software Versions:  The version number displayed represents the most recent version of the software available, whether from disk or downloaded.  Software compatibility is based on this listed version only.   If there are multiple supported versions of a given software package, multiple listings will be displayed. 
• Software Suites:  A "Suite" of software is generally a collection of separate software programs that have been packaged together in a bundle and sold for a single price.  An example would be "Microsoft Office"; this is a package that included Microsoft Word, Microsoft Excel, and Microsoft PowerPoint.  Each of these programs can be purchased separately, or as a package called "Microsoft Office."  Buying the package usually provides discounts over purchasing the products separately. It is important to note that if the software has been purchased as a package, it must be distributed as a package!It is not legal to purchase a copy of M'Soft Office, and then install Word on one computer and Excel on another computer, even if the two are installed only on one computer each.
• Bundled Software:  "Bundled" software usually refers to software that has been included with the purchase of a computer.  An example would be Apple iLife, which usually comes with any Apple Macintosh purchased.  Software that is "Bundled" with a computer is licensed only for use on that specific computer; in most cases it cannot legally be transferred to another computer without purchase.  Further, "Bundled" software rarely includes updates; Macintosh computers that were purchased two years ago and came with iLife '06 are not entitled to upgrade to iLife '07 or '08 for free; the newer versions must be purchased, athough they can usually be purchased at a discounted 'upgrade' price.
  

Licensing

• Required License: This is a purchased product.  Before the software may be installed (either individually or through FileWave), the requesting party/school must be able to prove that they have purchased licensing sufficient to cover their request(s).  Proof may be a license key, a purchase order, or other documentation.  In many cases, the software will require that a license key, serial number or other similar information be entered on each computer before the software will run normally.
  
• "Required/Serial":  When delivered through FileWave, the application will request a valid serial number when first run on each individual workstation.
• "Required/Register": When delivered through FileWave, the application will require a registration when first launched on each individual workstation.  The registration will need a serial/key number and user information.  The registration may take place through a website or through the software itself.
  
• "Required/Key": When delivered through FileWave, the application will require a key code when first launched on each individual workstation. 
  
• Hardware License:  This is generally a license for software that is specifically used with a particular piece of hardware, such as the 'Clicker' system or the Data Logger system.  Without the hardware, the software does not work. 
• District-Wide License: This product has been purchased by the district, and is available as needed.   
• Individual: This product is purchased as a single-user license, and is registered during installation, branding the application with the users name and related information.  This product *must* be installed on each individual user's computer.
  

Proof of Purchase

What the hey?  What's with this proof of purchase stuff?

In case of a software licensing audit at the district level (which would encompass all the schools in the district) we are asking for proofs of purchase for each application we distribute, so we can file them for future reference.  A proof of purchase can be as simple as a completed purchase order, a completed sales order, or really anything that can reasonably be used to prove that the district/school actually did pay for each copy of the product in use.  These licensing proofs will be filed by school and kept separate to prevent intentional or accidental 'borrowing' of licensing from one school to another.

Also - please note that saying "Well, we really did buy it" or "But we've been using it for years as part of our daily curriculum" does not actually constitute a proof of purchase.  Sending a copy of an unsigned, unnumbered (as in, no PO number, no Sales Order number) purchase requisition also is not a proof of purchase.  In a very few cases, a simple photocopy of the face of the CD may be accepted, but this will generally only be accepted as proof of a single-copy purchase, unless there is a verfiable (and legible) serial number or other individual identifier for the disk.  We're sorry, but a photocopy of a disk with the words "10-pack" handwritten on the face does not provide proof of ten licenses.  And, yes, each and every one of these 'proofs' has been attempted.