WS_Chat - A chat application for WfW 3.11 using the TCP/IP protocol.
--------------------------------------------------------------------

This is version 2.01 of ws chat. 

It enables you to chat over the internet by the use of the TCP/IP protocol. Therefore it doesn't matter whether your friend lives down the hall or at the other side of the world.

It replaces version 1.0 and 2.0. The TCP/IP problems should now be fixed.

Features:
---------

Real-time Bi-directional Chatting over the internet using physical or SLIP/PPP connections.

Easy to use automated Address-book.

Customisable for your particular use.

Event driven programming: uses almost no processor time when not in use. Leave it minimised on your desktop.

Tested with:

* 	WfW 3.11, should work for 3.1 though.

* 	trumpet winsock 2.0b
  	TCP/IP 32 (Wolverine) ver 3.11a

*	TIA (The Internet Acces) in combination with trumpet. Only works for connecting to people; you can't listen to incoming connections. 

*	Should work over standard SLIP/PPP connections as well.

Basic requirements
------------------

At least 386 PC with internet access (either physically or using SLIP/PPP).
WfW 3.11 or 3.1, and a TCP/IP package: TCP/IP 32 Wolverine (Free at ftp.microsoft.com), Trumpet winsock (shareware, found at several ftp  sites around the globe), Chameleon (not shareware, a try before you buy package is available at several ftp-sites). 


Regsistration
-------------

WS chat 2.01 is beggerware.

Registration is not required for ws chat version 2.01. That means that it's free to use this software. For information about distributing this software, see the disclaimer section at the end of this document.

However, I had to invest 50$ in the IPDaemon and IPPort custom controls, and a lot of time went into this program. Therefore, I would appreciate it if you sent me 5$ if you keep using this program. I will then notify you of updates of ws chat. If you have special requests, tell me what they are and I'll see what I can do.

Future versions of ws chat will not be free. If you register your copy now, you will get a 5$ discount on future  versions.

My address is:
Danny Brands
Molukkenstraat 122-L
1094 BV Amsterdam
The Netherlands


Manual
------

This manual will only contain some basic information, the next update will contain a help function (I promise).


Set up
------

Start by installing the package. Unzip the Zipfile. You can do this by typing pkunzip ws_chat2 -d. This will create a wsc_tmp directory. From program manager choose File - Run and browse for setup.exe in the wsc_tmp directory. Choose OK and follow the instructions.

Setup for Windows NT users and for people running windows from a network
------------------------------------------------------------------------

Users reported that ws chat is compatible with Windows NT. The setup program however is not. You should manually decompress the .XX_ file with the expand utility that came with windows. People running Windows from a network should do the same.


Starting ws chat
----------------

Double click the ws chat icon and the ws chat flyer appears. The Windoze Chat window will appear.

If anything went wrong until now, you probably have no TCP/IP package (properly) installed (trumpet, TCP/IP 32, Chameleon etc.) don't ask me anything about that, refer to your network administrator.

WS Chat has two modes, a listening mode (default) and a hailing mode. In listening mode, WS Chat will accept incoming calls. The hailing mode is for connecting to other people. You can toggle the modes by clicking on each of the four buttons (explained below). Watch the line under the remote box, it will give information on what's happening.

In order to chat, a copy of WS_Chat of your friend will have to  be in listening mode (automatically entered at start-up by default). You will then have to type in the IP name *or* IP number of your friend in the correct box and a port number at which your friend is listening. If you do not understand the port thing, just leave it at 22.

You can then make a connection by hailing your friend by clicking on the "HAIL" button. Watch the line under the remote box, it will say what's happening. It does first try to resolve your IP name and number, then it will try to contact the other side. When the line says: "Connected with xxx.xxx.xxx.xxx on Port yy" (where xxx.xxx.xxx.xxx is your friends IP number and yy the port number your friend is listening at) you can start typing.

You are now ready to Chat!

If nothing happens your friend probably did not have WS Chat in listening mode or something else is wrong (Do you have a TCP/IP package, is the IP and the Port number right?).

If you use dynamically addressed SLIP or PPP connections, your friend might have trouble contacting you, since you do not have the same IPnumber or name every time you log in. However, WS Chat now has a System info menu under help, so you should always be able to find out your IP name or number.


Commands
--------

I will now, briefly, go through all of the commands.

* The unnamed combo box: Here you can type in the name of your friend (just to remind you who it is).

* "IPNumber" and "IPName" box. Here, you can type in the IP name or number of your friend. Both Names and numbers work, you do not have to supply them both. The IP number should be in the: "XXX.XXX.XXX.XXX" format, where XXX is a number between 0 and 255. An IPName should be in the "jack.somecompany.com" format. Do not put an E-mail address in here! It has nothing to do with your IP name. If your friend can't figure out what his number is, let him use the System info option under help.

* Port: The name of the port your friend is listening to. It defaults to 22, and you should only change it if it conflicts with other applications (FTP, Telnet, WWW etc.)

* Hail: After you filled in the right address and port, you can click here to Hail your friend. After hailing a connection is made (if everything goes right). Watch what the line under the remote box says, it will give some useful information.

* Disconnect: when finished chatting, you can click Disconnect to disconnect from your friend. WS_Chat automatically goes into listening mode after disconnect is clicked if you were in this mode before hailing or answering.

* Enable: Can be used to go into listening mode to allow incoming connections. 

* Disable: to Disable listening for incoming messages. Also disconnects chatting sessions. You can use this to disconnect from a chatting session without getting into listening mode.

* The Local window: Type your text here when a connection is made. You can not and should not type anything while not connected, or use special keys like arrows, home, end etc. Backspace is supported however. Please do not keep pressing any keys, it might fill the network buffers.

* The Remote window: In here the text of your friend will appear. You cannot change anything here, but selecting and copying is allowed.

* Under the remote window there's a message line which will supply you some useful information. Watch it closely if anything goes wrong.

* The File menu:
-Add remote to list: A very useful option. You can add the remote you just typed in the combo, IP/DNS and Port boxes to the combo box list. All the entries (10) will slide down one place. The next time you want to connect to a friend you can pick it from the combo list.
-Registration: Not implemented.
-Change Port: The default value for the port is 22. If for some reason this will give you conflicts with other software, change it to another number. From then on, the new number will be used automatically. Do no change this while connected. Listening mode however, doesn't matter.
-Enable at start up. By default, WS_Chat goes into listening mode after start-up and chat sessions. If for some reason you do not wish this to happen, use this menu option.
-Minimised at start-up. You can launch WS_Chat automatically by adding "c:\ws_chat\ws_chat.exe" to the "load=" statement in your WIN.INI. It is nice then when WS_Chat is automatically ionised and sits on your desktop waiting for incoming connections. Use this option to launch WS_Chat ionised (see the Password section on how to lose the reminder).
-Answering machine: This will play a message that is in the ws_chat.msg file upon incoming connections. This comes in handy when you are drinking coffee.
-Edit message: Edits the message to be played.
-Exit: Exits WS_Chat
*The Help menu:
-Help: Not implemented. OK it will be in the next version, I promise.
-About: Try it!
-System info: Gives some useful information about your system. It tells you what winsock is installed.
-Personal IP: Tells you what your computers IPName or Number is.
-IP of incoming: Tells you who you're speaking with. This comes in handy when you want to be shure. Also useful for trouble shooting. This will only work when you have an incoming connection of course!
-Registration info: Not very useful yet since it's not required for version 2.0.

Trouble shooting
----------------

OK, something goes wrong or does not operate in the right way. First look in the Know limitations section down here to see if it is a limitation of the package. Then ask yourself: "Do I have a TCP/IP package installed?". If you are not shure, ask your network administrator. Try WS Chat's System info (under help). Does it say what winsock you have and your IPnumber? If not, you have problems with either your TCP/IP software of your network connection.

Then look at the message line under the remote box; does it say "Could not enable socket"? Then either you have some other application using the same port (change it using the "File" - "Change Port" menu option) or your network setup is not correct (refer to your network administrator).

One way of trouble shooting is chatting with yourself. Open two copies of WS Chat, one goes automatically into listening mode, and the other (generates an error - ignore this) you should type in your own Addres and click the Hail button. If you have a connection now, probably something else than your TCP/IP package is wrong. There's one remark: some TCP/IP packages allow no connection with yourself (trumpet 1.x versions - upgrade to ver. 2.0). So chatting with yourself will not work. Also, you might need to connect to your host if you're using SLIP/PPP.

If there's still something wrong, you can mail me a detailed description of your setup, error messages and what System info say (brands@sara.nl). If it is possible, I will try to solve it.

TIA: ws_chat is tested with TIA and it works for connecting to other people. However, since you do not have an IPNumber when you are using TIA, you cannot have incoming connections. (Thanks due to Bill for supplying this information to me) 


Known limitations
-----------------

*	You can not (and it shouldn't be possible) to use cursor, Home, End keys in the Host Box. But *Backspace* is supported. Although fundamentally supported, you should not paste large amounts of text in the Host and remote boxes and keep pressing keys. This counts especially for slow or long distance connections. If there's too much text in ws chat's buffers, an Out Of Stack Space (OOSS) error will occur. Often, you can just wait for a second or two and start typing again.
I hope to fix it in the next version.

*	The length of the correspondence is limited to the size of the textbox (about 32767 characters). This should take you for a while.

*	Currently the window is not resizable. It is now small enough for 640x480 users though.

*	When the remote uses a backspace, the remote textbox will be updated completely, but no characters are sent over the network though!. This can cause flashes in this box (but works fine 486/66).


Additional information
----------------------

WS Chat 2.0 is written in visual basic 3.0 with the use of a two VBX custom controls: IPPort and IPDaemon. I had to pay 50$ for them (although try before buy packages are available via cica and sunsite).

DISCLAIMER & Copyrights
-----------------------

This Software is owned by Danny Brands. Danny Brands grants to the user a nonexclusive license to use this WS_Chat Software solely for its internal business purposes.  The user may not commercially distribute, sublicense, resell, or otherwise transfer for any consideration, or reproduce for any such purposes, the WS_Chat software or any modification or derivation thereof, either alone or in conjunction with any other product or program.  Further, the user may not modify the WS_Chat Software, other than for its own internal business use.

THIS WS_CHAT SOFTWARE IS PROVIDED TO THE USER ''AS IS.''  Danny Brands MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS WS Chat SOFTWARE AND/OR ASSOCIATED MATERIALS PROVIDED TO THE USER, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR AGAINST INFRINGEMENT. Danny Brands DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED.  FURTHERMORE, Danny Brands DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF THE SOFTWARE OR ANY DOCUMENTATION PROVIDED HEREWITH IN TERMS OF THEIR CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.  NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY Danny Brands SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY.

LIMITATION OF LIABILITY -- Danny Brands is NOT LIABLE FOR ANY CLAIMS OR DAMAGES WHATSOEVER, INCLUDING PROPERTY DAMAGE, PERSONAL INJURY, INTELLECTUAL PROPERTY INFRINGEMENT, LOSS OF PROFITS, OR INTERRUPTION OF BUSINESS, OR FOR ANY SPECIAL, CONSEQUENTIAL OR INCIDENTAL DAMAGES, HOWEVER CAUSED, WHETHER ARISING OUT OF BREACH OF WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, OR OTHERWISE.

Bug fixed and enhancements in ws chat version 2.01:
--------------------------------------------------

*	When ws_chat connected to a remote that did not have an IPNumber, still an error was generated, because it tried to resolve the IPName also. This has now been fixed.

*	When you exit ws_chat, the coordinates are saved in the ini file, to place ws_chat at the same place on your desktop the next time you open it. This happened also when iconized. Fixed.

*	The menu item 'system information' is now split in 'system information' and 'personal IP', because the last item causes an error when one doesn't have an IPName.

*	It's now unpossible to keep pressing keys and have multiple characters flood ws_chat buffers. This should prevent most of the OOSS problems.


Bug fixed and enhancements in ws chat version 2.0:
--------------------------------------------------

*	Changed the TCP/IP custom controls. The problems people had with an IP number and without an IP name should now be fixed.

*	Fixed several small errors, like Boolean problems with disabling the command buttons.

*	Added several icons. You can -in fact- use your own icons if you want to.

*	Added an answering machine option. It simply reads the ws_chat.msg file and sends it to the incoming user.

*	Added System info and incoming IP info. A user should now be able to see if a winsock is enabled, his IP number and an IP number of the incoming connection.

*	Better error trapping and error messages.

*	New looks, reduced the program's form so that it is now possible to use it in 640x480 modes.


Can't get a grip on:
--------------------

*	OOSS error. It would be better to completely rewrite the ws chat protocol. The TCP/IP problems forced me to do this later.

*	The problem of people with IPNames but without numbers. I can't deternine what IPNumber they have if they havn't got an IPName.


Future versions will have:
--------------------------
In the future I'm planning to:

*	Better buffering (OOSS error -see known limitations)

*	Add a Help option.

*	Let ws_chat speak the UNIX talk protocol.

*	Add a simple file transfer utility.

*	Add the possibility to transfer and view pictures.

*	Data (PGP) encryption.

*	Adding multi-user possibilities.

...... Your own wishes go here, mail them at brands@sara.nl and I'll see what I can do.

