24/11/97      - Script connection timeout function supported. #45 after
		a connection line in a script file indicates the
		connection must be established in less than 45 seconds.
		After that, the script file is aborted.
		By default, timeout is set to 60 secondes.

		script file example
		-------------------
		F5MZN-3
		.C F6HPP		connect a KANTRONIC node
		#40			40s of timeout
		.X F5MZN-3
		#120    		120s of timeout
		+MADE
		?FAILURE


13/12/97      - Adjacent incoming connections wasn't identified as a
		a cluster for SSID different of -0. Fixed. (Tks F1TE).

13/12/97      - When running DxNet from a W95 DOS window, the SHUTDOWN
		command crashed. Fixed.

13/12/97      - Adding the new command EXIT. This command is used to exit
		DxNet with a specified error code. This allows to run
		any program in place of DxNet, or to reload DxNet. See the
		following example (assuming DxNet is run from the GO.BAT
		file).

		Syntax : EXIT/n <comments>
			 where n is the exit code and <comment> the
			 optionnal message send to the local users.

		Under MS-DOS, how to either run a YAPP program for uploading
		a new release of DxNet or to reboot the computer ?
		GO.BAT file
		-----------
		rem EXIT/1 runs a YAPP program
		rem EXIT/2 reboots the computer
		DXNET -s50
		IF EXITCODE 1 GOTO YAPP
		IF EXITCODE 2 GOTO REBOOT
		GOTO END
		:YAPP
		rem Run TPK and reboot the computer
		TPK
		:REBOOT
		rem Reboot the computer
		REBOOT
		:END

		Under W95, how to restart DxNet ?
		GO.BAT file
		-----------
		rem EXIT/1 restarts the computer
		:START
		DXNET -s50
		IF EXITCODE 1 GOTO START

		I hope distant sysop will appreciate this new command.

15/12/97      -	The language files management turning out quite complex
		owing to the lack of identify them with the file name,
		the language file names have been changed like following :

		* The whole LANGn.TXT are now called xxx.TXT, where
		  xxx designs the language.

		* The whole HELPn.TXT are now called xxx.HLP, where
		  xxx designs the language.

		* The whole MOTDn.TXT are now called xxx.MOT, where
		  xxx desgins the language.

		eg : FRENCH.TXT, ENGLISH.TXT, RUSSIAN.TXT, ...
		     FRENCH.HLP, ENGLISH.HLP, RUSSIAN.HLP, ...
		     FRENCH.MOT, ENGLISH.MOT, RUSSIAN.MOT, ...

		You must set in SYSTEM\LANGUAGE.DAT the	languages you
		want to allow.
		For example :
		FRENCH
		ENGLISH
		RUSSIAN
		SPANNISH
		GERMAN

		Of course, you can put languages in the order you
		want.

		As previously, up to 10 languages are supported.

		This should ease updating the language files. I suggest
		to use english to name these files (particularly if you
		send me them for adding in the distribution package), but
		everybody can do like he wants !

16/12/97      - Adding the new command SET/TZ #n, which can set the
		difference between the local time and GMT.

		Example : SET/TZ -5

	      - Provided a reboot program (REBOOT.EXE) for DOS.

03/01/97      - Providing an interface program (BUCKMSTR.EXE) to access
		the hamcall's BuckMaster CD-ROM for DOS.

		Syntax : BUCKMSTR <drive> <callsign> [I/xx]

			 drive    : CD-ROM drive letter
			 callsign : searched callsign
			 /Ixx     : BUCKTSR interrupt number (hexa).
				    This Argument is optionnal.

		Source code in C is available (SOURCE.ZIP).

	      - Creating the new directory dxnet\callbook. This directory
		will be used to access a cdrom callbook database.

		How to declare the callbook database (for DOS)
		----------------------------------------------

		1/ Create a BATH program in the directory CALLBOOK. See
		   the example below (assuming your CD-ROM letter is D:) :

		   HAMCALL.BAT
		   -----------
		   @ECHO OFF
		   rem You MUST include the directory path
		   C:\DXNET\CALLBOOK\BUCKMSTR D: %1

		2/ Declare the database in dxnet\system\local.dat. For that
		   you must put the word "callbook" in place of the chain
		   field.

		   LOCAL.DAT
		   ---------
		   BUCK	   HAMCALL    callbook   #Buckmaster's callbook

		   where - BUCK is dxnet command (SH/BUCK) to access the
			   database
			 - HAMCALL is the program name (locate in the
			   callbook directory) to run the interface program.

		3/ Before running DXNET, don't forget to run BUCKTSR.EXE

		This is a bit complex, but this will allow sysops to be able
		to declare any other CD-ROM in place of the one of
		BuckMaster. He just has to develop an interface program.

		BTW, linux sysops are not forgot because they will also be
		able to access callbook	databases via a DOS session
		(sorry I can't help you for that myself ... linux gurus,
		go head !)

	      - Adding an external command directory (called SYSCMD). Same
		as extcmd, but for sysops only.

	      - Adding the command SH/U which allows to show the local
		user configuration.