3A11a	- User count problem (linux version) fixed (Tks SM5HUA).

3A11b	- External commands (extcmd directory) crashed if no arguments was
		  specified. Fixed (Tks SM5HUA).

3A11c	- A problem was occurring if DxNet was receiving a negative hop
	  count value. True, this normally shouldn't happend but as you
	  probably see it does !! Fixed.

	- Two New user commands : SET/BEEP & SET/NOBEEP
	  If SET/NOBEEP is activated, the user will no longer receive the
	  BELL characters for DX, WWV, ANNOUCEMENT and TALK.

	- DISC/CALL <callsign> disconnects <callsign> from DxNet.

	- SET/SPY <port> <hops> - where <port> is the port number and
	  <hops> the hop count you want to use for forwarding the spyed
	  dx spots.

	  This command is used to listen a cluster link for getting the
	  PC11 (dx spots) protocol without the need to be connected.

	  ******************************************************************
	  * Take care using this command : you cannot use it if you are    *
	  * connected to the cluster network you are spying. If you did,   *
	  * you will generate a lot of trouble. The best way is to not use *
	  * this feature except if you really really need it !             *
	  ******************************************************************

	  This command was available with DxNet v2, and very appreciated by
	  some african guy who have very poor link on HF with the other part
	  of the world, and not so much of cluster activity in their area.

	  NB : SET/SPY is available for the DOS version only.

	- Carriage return and some other special characters are supported
	  in a script connection file. If you want to send, say, two strings
	  at once, your script file should be like that :

	  F5MZN-3
	  .C NO4J		//Connecting a telnet gateway
	  .f5mzn-3\nguest	//Will send first "f5mzn-3" (login),
				//and then "guest" (password)

	  Supported characters are the same than JNOS (DxNet uses the same
	  function) : \n \t \v \b \r \f \a \\

	  If you want to send the '\' character, put '\\' in place of.

	- If you would connect to the cluster for any reason while you
	  are already connected, DxNet crashed. This problem has been
	  fixed by changing the user ssid automaticaly.

	- SH/CONF support a filter : "SH/C F" will show the cluster for
	  which the callsign is starting with a F. More than one letter is
	  supported as well. SH/C F6F will show the callsign starting with
	  F6F. Etc ...

	- A system like C_FILTER is now present. This system is used to
	  filter connections by password. By default, this system
	  is disabled. Use the command SET/CFILter (e.g. in SYSTEM\DXNET.CFG)
	  to enable it :

				SET/CFILter <n>

	  n = 0 : CFILTER is OFF
	  n = 1 : CFILTER in ON - a password is required. If the user send
		  the right password, DxNet works as usual. If not, the
		  user is diconnected.
	  n = 2 : CFILTER is ON - a password is required. If the user send
		  the right password, DxNet works as usual. If not, the
		  user can receive the cluster informations but can not
		  send datas (like DX, WWV, ...), except a mail to SYSOP.
	  n = 3 : CFILTER is ON - no password is required. If a declared
		  user connects the cluster, DxNet works as usual. If the
		  user is not declared in SYSTEM\PASSWD.DAT, he will receive
		  the whole cluster information but he will not allowed to
		  send datas.

	  If the user is going to be disconnected, or if the connection is
	  limited to the RX mode only, the file "language\cfilter.txt" is
	  sent. This file is used to explain the user he have not a full
	  acces to DxNet. Don't forget to create/edit it !

	- Update field added to the cluster information (both at the
	  connection and with the SH/CLuster command).

        - Fixing a bug with the PC50 protocol (linux version).