Free iii software for linux

This is the source code for Quake III Arena version 1.32b, released by id Software. Quake III Arena Source is subject to the terms of the GNU General Public License.
While we made sure we were still able to compile the game on Windows, GNU/Linux and Mac, this build didnt get any kind of extensive testing so it may not work completely right.
Whenever an id game is released under GPL, several projects start making the source code more friendly to nowadays compilers and environements.
If you are picking up this release weeks/months/years after we uploaded it, you probably want to look around on the net for cleaned up versions of this codebase as well.
The build system using cons, which may be known as sconss perl ancestor now you dont have to track it down though, the build script is provided in the tree you will need nasm and gcc 2.95
Make sure you have the X Direct Graphics Access and X Video Mode extensions headers for your X11 a typical compile command goes like this:
[..]/code$ ./unix/cons -- gcc=gcc-2.95 g++=g++-2.95
Enhancements:
- Fix for a security exploit.

pgAdmin III is designed to answer the needs of all users, from writing simple SQL queries to developing complex databases.
The graphical interface of PgAdmin III supports all PostgreSQL features and makes administration easy.
The application also includes a query builder, an SQL editor, a server-side code editor and much more. pgAdmin III is released with an installer and does not require any additional driver to communicate with the database server.
pgAdmin III is developed by a community of database specialists around the world and is available in more than 30 languages. It is Free Software released under the Artistic License.
Main features:
Multiplatform
- MS Windows 2000 & XP
- GNU/Linux
- FreeBSD
- MacOsX and SunOS ports are under development.
Designed for PostgreSQL latest versions
- PostgreSQL 7.3
- PostgreSQL 7.4
- PostgreSQL 8.0
On-line help
- PostgreSQL documentation (on-line and off-line)
- SQL command guide
Multilingual interface
- pgAdmin III user interface is translated in more than 30 languages. A detailed list of supported languages is available on the Translation page.
Data access
- Native PostgreSQL acccess (no ODBC layer needed)
- Powerful query tool with color syntax highlight
- Very fast datagrid for display/entry of data
Access to all PostgreSQL objects
Objects are displayed with their SQL definition.
- Aggregates
- Casts
- Columns
- Constraints
- Conversions
- Databases
- Domains
- Functions
- Groups
- Indexes
- Tablespaces
- Server-side languages (like PLpgsql, PLpython, PLperl, etc...)
- Operator classes
- Operators
- PostgreSQL servers
- Rules
- Schemas
- Sequences
- Tables
- Trigger function
- Types
- Users
- Views
Multibyte support
- pgAdmin III supports most PostgreSQL server-side encodings:
- SQL_ASCII
- EUC_JP, EUC_CN, EUC_KR, EUC_TW
- JOHAB
- LATIN1, LATIN2, LATIN3, LATIN4, LATIN5, LATIN6, LATIN7, LATIN8, LATIN9, LATIN10
- ISO_8859_5, ISO_8859_6, ISO_8859_7, ISO_8859_8
- UNICODE UTF-8
- MULE_INTERNAL
- KOI8
- WIN
- ALT
- WIN1256
- TCVN
- WIN874

Major Features:

1. Better Thunderbird integration
2. emailtask linkage
3. Integration with the Thunderbird address book
4. iMIP support (meeting invitations)
5. Improved CalDAV support
6. Cached calendar support for offline calendar use
7. Device synchronization

Enhancements:

• Events spanning days now have a visual indicator indicating them as connected events
• When reloading a remote calendar a progress indicator is now shown
• The so-called "minimonth" (small calendar month in the upper left) has been given a visual overhaul
• The calendar views (day, week, multiweek, month) have been given a visual overhaul
• The today pane can now be displayed in calendar mode and task mode as well
• CalDAV support and interoperability with various CalDAV servers has been improved
• iMip/iTip support (support for email invitations) has been greatly improved
• The application stability and memory consumption has been greatly improved
• Lightning 0.9 is intended to be the last release for the Thunderbird 2 series. For the future we are planning to integrate Lightning fully into the upcoming Thunderbird 3 release
• A full list of changes that have gone into this release can be found on The Rumbling Edge website

Requirements:

• Software Requirements Please note that Linux distributors may provide packages for your distribution which have different requirements.
• • Linux kernel - 2.2.14 or higher with the following libraries or packages:
  • glibc 2.3.2 or higher
  • XFree86-3.3.6 or higher
  • gtk+2.0 or higher
  • fontconfig (also known as xft)
  • libstdc++5 (Many modern Linux distributions only package libstdc++6, which is incompatible with Lightning. Therefore please install the package "libstdc++5" or "compat-libstdc++" on your system before installing Lightning)
• Minimum Hardware
• • Intel Pentium II or AMD K6-III+ 233 MHz CPU (Recommended: 500MHz or greater)
  • 64 MB RAM (Recommended: 128 MB RAM or greater)
  • 52 MB hard drive space

Hafiye is a POSIX-compliant, customizable TCP/IP packet sniffer. When I looked at the source code for various famous sniffers, Ive noticed that they all had all seperate .C files for interpreting various protocols. Why not have a sniffer that can understand user-supplied protocol details? Here it is.
When fired, Hafiye first visits each sub-directory under its knowledge-base directory and opens to see whether it is a protocol knowledge-base file. If so, It loads the necessary information from that file and places it into its memory space.
After constructing the supplied knowledge-base, Hafiye starts looping for receiving packets. When a packet arrives, it demultiplexes the layers according to its knowledge-base and prints protocol information.
Main features:
- Multi Platform Support (Posix Compliant)
- Customizable Protocol Definitions (Layer II, III and IV)
- Customizable Packet Interpretation (Layer II, III and IV)

Audio::TagLib::MPEG::Properties is an implementation of audio property reading for MP3.

SYNOPSIS

use Audio::TagLib::MPEG::Properties;

my $f = Audio::TagLib::MPEG::File->new("sample file.mp3");
my $i = $f->audioProperties();
print $i->layer(), "n"; # got 3

This reads the data from an MPEG Layer III stream found in the AudioProperties API.
new(PV $file, PV $style = "Average")

Create an instance of MPEG::Properties with the data read from the MPEG::File $file.

DESTROY()

Destroys this MPEG Properties instance.

IV length()

IV bitrate()

IV sampleRate()

IV channels()

see AudioProperties

PV version()

Returns the MPEG Version of the file.

see Audio::TagLib::MPEG::Header

IV layer()

Returns the layer version. This will be between the values 1-3.

BOOL protectionEnabled()

Returns true if the MPEG protection bit is enabled.

PV channelMode()

Returns the channel mode for this frame.

see Audio::TagLib::MPEG::Header

BOOL isCopyrighted()

Returns true if the copyrighted bit is set.

BOOL isOriginal()

Returns true if the "original" bit is set.

Final Fantasy VI Save State Editor project is an editor for Final Fantasy VI characters.

Final Fantasy VI Save State Editor is a tool for editing characters in Final Fantasy VI (or III in the USA) saved games. It makes it possible to increase skills, learn spells, gain weapons, and more using an easy to use GUI.

This
program does not edit battery based saved games, but complete game save states
generated by Snes9x and zsnes.

USAGE:

Open the program and select File->Open. Select a game save on your filesystem,
and then edit away! Use File->Save when done. Enjoy!

SiSU is a Serialized information, Structured Units for Electronic Documents, is a document creation and management framework.
Main features:
- (i) markup syntax: (a) simpler than html, (b) mnemonic, influenced by mail/messaging/wiki markup practices, (c) human readable, and easily writable,
- (ii) (a) minimal markup requirement, (b) single file marked up for multiple outputs,
- (iii) (a) multiple outputs include amongst others: html; pdf via LaTeX; (structured) XML; sql - currently PostgreSQL (and SQLite); ascii, (also texinfo), (b) takes advantage of the strengths implicit in these very different output types,
- (iv) provides a common object positioning and citation system for all outputs, which is human relevant and machine usable: object citation numbering, all objects (paragraphs, headings, verse, tables etc. and images) are numbered identically, for citation purposes, in all outputs (html, pdf, sql etc.),
- (v) use of Dublin Core and other meta-tags to permit the addition of some semantic information on documents, and making easy integration of rdf/rss feeds etc.,
- (vi) creates organised directory/file structure for (file-system) output, easily mapped with its clearly defined structure, with all text objects numbered, you know in advance where in each document output type, a bit of text will be found (eg. from an sql search, you know where to go to find the prepared html output or pdf etc.)... there is more; easy directory management and document associations, the document preparation (sub-)directory may be used to determine output (sub-)directory, the skin used, and the sql database used,
- (vii) search of document sets, the relational database retains information on the document structure, and citation numbering makes it possible for example to present search matches as an index of documents and locations within the document where the match is found,
- (viii) "word maps" rudimentary index, consisting of all the words in a document and their (text/ object) locations within the text, (and the possibility of adding vocabularies),
- (ix) easily skinnable, document appearance on a project/site wide, directory wide, or document instance level easily controlled/changed,
- (x) in many cases a regular expression may be used (once in the document header) to define all or part of a documents structure obviating or reducing the need to provide structural markup within the document,
- (xi) is a batch processor for handling large document sets, ... though once generated they need not be re-generated, unless changes are made to the desired presentation of a particular output type,
- (xii) possible to pre-process, which permits: the easy creation of standard form documents, and templates/term-sheets, or; building of composite documents (master documents) from other sisu marked up documents, or marked up parts, i.e. import documents or parts of text into a main document should this be desired
- (xiii) future proofing, a framework for adding further capability or updating existing capability as required: (a) modular, (thanks in no small part to Ruby) another output format required, write another module....(b) easy to update output formats (eg html, xhtml, latex/pdf produced can be updated in program and run against whole document set), (c) easy to add, modify, or have alternative syntax rules for input, should you need to,
- (xiv) scalability, dependent on your file-system (in my case Reiserfs) and on the relational database used (currently Postgresql and SQLite), and your hardware,
- (xv) only marked up files need be backed up, to secure the larger document set produced,
- (xvi) document version and comparison considerations (a) possibility to easily check or guarantee that the substantive content of a document is unchanged, through md5 (or other) hash keys, (b) version control, documents integrated with time based version control system, default CVS with use of $Id$ tag, which SiSU checks (c) SiSUs minimalist markup makes for meaningful "diffing" of the substantive content of markup-files,
- (xvii) document management,
- (xviii) use your favourite editor, syntax highlighting files for markup, primarily (g)vim so far,
- (xviv) remote operations: (a) run SiSU on a remote server, (having prepared sisu markup documents locally or on that server, i.e. this solution where sisu is installed on the remote server, would work whatever type of machine you chose to prepare your markup documents on), (b) alternatively, (assuming sisu is available to you locally but not installed on the remote server) configure sisu to securely copy (scp) its output to your remote host and run sisu locally, (c) request a remotely located sisu markup file and process it locally by identifying it by its url.

libdbf is a C-library for reading dbase files.

dBASE Converter is a command line tool to show and convert the content of dBASE III, IV, and 5.0 files.

dBASE Converter project reads dBASE databases and prints the content to the screen or converts it to CSV files or SQL instruction sets.

It reads xBASE-compatible databases and prints the content to the screen or converts it to comma-separated (*.csv) files which can be opened in Excel, StarOffice, and most other spread sheets. It can also be used to show some statistics about the content.

NOTES

If you have problems to build your own binary of libdbf, please read the following.

Error Message:
Cant locate object method "path" via package "Request"
at /usr/share/autoconf/Autom4te/C4che.pm line 69

Solution:
Execute the command
rm -rf autom4te.cache/
in the libdbf directory and run autogen.sh again.