Free recovery chat software for linux

The gzip Recovery Toolkit attempts to automate the recovery of data from corrupted gzip files (including tarballs) through a program called gzrecover. gzip Recovery Toolkit package is still very experimental at this point.
99% of "corrupted" gzip archives are caused by transferring the file via FTP in ASCII mode instead of binary mode. Please re-transfer the file in the correct mode first before attempting to recover from a file you believe is corrupted.
This program is provided AS IS with absolutely NO WARRANTY. It is not guaranteed to recover anything from your file, nor is what it does recover guaranteed to be good data. The bigger your file, the more likely that something will be extracted from it. Also keep in mind that this program gets faked out and is likely to "recover" some bad data. Everything should be manually verified.
Usage:
Run gzrecover on a corrupted .gz file. Anything that can be read from the file will be written to a file with the same name, but with a .recovered appended (any .gz is stripped). You can override this with the -o option.
To get a verbose readout of exactly where gzrecover is finding bad bytes, use the -v option to enable verbose mode. This will probably overflow your screen with text so best to redirect output to a file.
Once gzrecover has finished, you will need to manually verify any data recovered as it is quite likely that our output file is corrupt and has some garbage data in it. If your archive is a tarball, read on.
For tarballs, the tar program will choke because GNU tar cannot handle errors in the file format. Fortunately, GNU cpio (tested at version 2.5 or higher) handles corrupted files out of the box.
Heres an example:
$ ls *.gz
my-corrupted-backup.tar.gz
$ gzrecover my-corrupted-backup.tar.gz
$ ls *.recovered
my-corrupted-backup.tar.recovered
$ cpio -F my-corrupted-backup.tar.recovered -i -v
If you have a previous release, please note that the patches to GNU tar have been discontinued. They were only marginally successful at best and GNU cpio does what is needed out of the box and does it far better.
Enhancements:
- Documentation updates, including a man page, plus code cleanup to better enable inclusion in GNU/Linux packages and eliminate compilation warnings.

Claros Chat is finally ready. It is a web based (fully Ajax) instant messaging client which is capable of talking with the Jabber protocol. Claros Chat is well tested with Google Talk and it supports all major browsers such as Internet Explorer, Firefox, Safari, Mozilla.
The project has a minimalistic and an elegant user interface which looks much like a desktop application. Anyone interested in the application can test drive it at http://www.claros.org/chat.
Main features:
- Works with any Jabber server, including Google Talk.
- No setup needed on the client machine, works 100% within the browser, no plugins required.
- It is a 100% Ajax application, with a clean and nice user interface.
- Supports all major browsers.
- It can display user avatars including your own.
- Supports many of the emotions with MSN like smileys.
- All features such as changing status, changing status text, loading buddy list, adding/removing new buddy are all implemented.
- Can chat with as many users as you like.
- Users can set auto away at the preferences screen.
- Much words are useless, youve got to see it yourself, "it is one of the best looking and usefull open source instant messaging applications(or simply the best) in the world". See and believe for yourself. Just try the demo to see.(Login with your own Google username/password)
- You can start your own corporate chat network. Download a Jabber server from http://www.jabber.org and use Claros Chat to chat with your collegues.
- You can connect and chat with MSN, AOL, ICQ, Yahoo chat networks providing that you have your own Jabber server with a suitable gateway installed.
- It is open source and completely free software.

RobChat is an XML/HTTP chat script. It features multiple users, automatic updates without reloading, IE and Mozilla support, and a "whos online" window.

RobChat has the look and feel of a client-side chat client, but is written entirely in XML/HTTP, Javascript, and PHP.

Peekko Chat is a new Firefox extension that makes every web page a location where people can congregate.
Peekko Chat adds a toolbar to Firefox that shows how many people are in that pages chat room and allows you to instantly connect with them.
Installation:
- Install the extension by clicking on the following link using Firefox 1.5.
- Click on the "Options" button in the toolbar and select a set of nicknames to give yourself. If your nickname is taken, it will use one of your alternate nicknames. Note: If you skip this step, you might be given an unfavorable nickname from the nickname generator like "kurblatz18".
- To see how many people are at a given page, click "Connect."

Poisson Media Recovery project can be used to retrieve slightly damaged files from CD-ROM media.

It sequentially mounts and umounts the device, and on each mount it tries to read as many new 512 byte sectors as possible.

I was able to use this tool to save some files from old CDs.

Cmos password recovery tools decrypts password stored in cmos used to access BIOS SETUP.
Works with the following BIOSes:
- ACER/IBM BIOS
- AMI BIOS
- AMI WinBIOS 2.5
- Award 4.5x/4.6x/6.0
- Compaq (1992)
- Compaq (New version)
- IBM (PS/2, Activa, Thinkpad)
- Packard Bell
- Phoenix 1.00.09.AC0 (1994), a486 1.03, 1.04, 1.10 A03, 4.05 rev 1.02.943, 4.06 rev 1.13.1107
- Phoenix 4 release 6 (User)
- Gateway Solo - Phoenix 4.0 release 6
- Toshiba
- Zenith AMI
With CmosPwd, you can also backup, restore and erase/kill cmos.
AWARD 4.50 have a backdoor, a generic password : AWARD_SW SOYO motherboard have "SY_MB" as master password for Award 4.51. CmosPwd give equivalent passwords for Award BIOS, not original one.
CmosPwd works and compiles under:
- Dos-Win9x,
- Windows NT/W2K/XP/2003,
- Linux,
- FreeBSD and NetBSD.
Enhancements:
- This version adds support for the VAIO EEPROM and Samsung P25 CMOS.

Voc is a stream-chat engine which is designed to work on high-loaded chat-servers. It is written in PHP, but uses Perl or C++ for Voc-daemon -- the special program to handle multiple user-connections. With Voc you can make a chat that will serve many conversations simultanously. And its html-based, so your chatters can use it from almost any browser.
The Voc-engine includes a lot of features so it will be interested not only for a big chat owners.
Whats so special about Voc-engine?
There are 2 classes of html-chats. Classic-type, with refreshing messages-window, And stream-type.
Refresh-type is known to everybody, so lets think about streams. What is the common way to introduce such functionality? Webmasters make cgi-script (PHP-script, jsp-srcpt, e.t.c) which checks for new messages every second (2,3...) and prints something to the client. Of course, you need one instance of the script for each client. Now calculate how many data-requests you need to process every second... At least two for each client -- get messages, get users-list.
Also dont forget about memory and CPU usage. For instance, if you have PHP-scripts and PHP is compiled as an Apache-module, be ready to spend 5 Mbytes of memory and 0.1-1% of CPU for each client (only for messages-window).Multiple it to number of users online.
Do you still want to use such scripts?
Is there any solutions? I guess, yes -- try Voodoo chat. It uses Perl- or C++-daemon which processes users-requests to a messages list. And you need just one daemon for all clients. This daemon takes approx. 10 Mbytes of memory for 100 users. CPU usage is also small (of course it depends on your CPU, i.e. for 100 users online it is 0.5% of Pentium 4 2.4 Ghz). Do you see the difference now?
Main features:
- Daemon-stream type (recommended)
- Classic-type (with refreshes)
- PHP-stream script (read text above and use this type only when you have less then 20 simultaneous visitors and cannot use daemon-type)
- JavaScript stream-emulation (refreshing hidden frame which just add text to the main message-window)
- Themes-support. You can use one of exisitng designes, or easily create your own
- rooms
- private messages
- ignoring
- you can enable to use bold, italic, underlined messages
- inline images
- personal info-page with photo for registered users
- avatars
- internal mini-mail system
- status (online/offline/not available/dont disturb)
- web-indicator (see example at the left)
- nick & string highlighing for personal messages
- anti-flood
- messages and ban/unban logging
- limits for maximum number of users and maximum number of users from one ip (anti-nick-flooding)
- graphical statistic, example
- admin-zone to manage the chat
- moderator-levels for registered users, so you can give someone permissions to ban/unban users, change rooms-info, edit/delete registered users

Small Telnet Chat provides a chat server to which you can connect via a telnet client.

Small Telnet Chat (STC) is a chat server to which you can connect via a telnet client. It provides logging, automatic kicking, and IP blocking.

Requirements

Server: All you need are the files of the chatserver and a functional JRE.

Client: To connect to the server you need at VT100 capable telnet client.
Simple telnet to a server on which the STC is running. (You need to know the port on which the server is listening since STC can run on any port).

STC is known to work with:
-> PuTTY works fine
-> Win2000 telnet works
-> WinXP telnet works (some versions of WinXP telnet seem to have problems but up to date ones (with service packs, etc.) work)
-> Linux telnet (netkit) works

Installation

No special installation procedure is required. Simply unpack the archive into a directory and run it.

The configuration file (config.xml) has to be in the same directory as the server.

For those who want to put the server to place where executables usually reside (/usr/local/bin, etc.), a .jar file is provided.

Running

To run the chatserver, cd into the directory into which you have copied the files.

Run the server by typing:
java stc