04/07/98 - Both commands SP and SB are now working. - Monitor function can be disabled. Start DxNet with the extension -moff. Example : dxnet -moff - Creating of the directory dxnet\users. This directory contains files in which there is a list of commands you want to execute each time a usern connects the server. DEFAULT.CMD : list of commands by default CALLSIGN.CMD : where CALLSIGN is the callsign (without SSID) for a specific user. List of commands for this user. 06/09/98 - Mail forwarding using PC protocol enabled for incoming messages. 10/09/98 - The file SYSTEM\FORWARD.SYS will contain the bulletin forwarding routes. If you want to, say, forward to F6BEE the recipients ALL, DX, FRPA, QSL, and forward to F6KIF-3 the recipients ALL, DX, QSL, the file FORWARD.SYS will contain the following information : FORWARD.SYS ----------- :F6BEE #Forward to F6BEE >ALL #the recipient ALL >DX #and DX >FRPA #and FRPA >QSL #and QSL END :F6KIF-3 #Forward to F6KIF-3 >ALL #the recipient ALL >DX #and DX >QSL #and QSL END END #End of file - The command FB [callsign] shows the message waiting in the forwarding queue to [callsign]. is optionnal. If you omit it, you'll show the entire forwarding queue. - The command FD <#msg> <@Callsign> dequeues a mail from forwarding queue. - The command FA <#msg> <@Callsign> queues a mail into the forwarding queue. 24/09/98 - The command SET/USERCmd allows users to upload a list of command they want to execute each time they connect to the serveur. This command updates the file USERS\CALLSIGN.CMD where CALLSIGN is the user callsign. - The commands SHow/USERCmd shows the list of these commands. - Implementing of the forward protocol (PAVILLON's one only). A lot of job to implement it - the code certainly not free of bugs ! Please your reports !! The CluLink forwarding protocol will be available soon. - The command FWd [#msg] [@Callsign] starts forwarding mails. [#msg] and [@Callsign] are optional. I suggest you to add this command in SYSTEM\DXTODO.DAT - Clulink forwarding protocol implemented. This is a non compressed, non optimized protocol for now but it should work waiting a better one. *** Don't forget to create the new directories USER and MAIL ************* *** fix3a9-1 26/09/98 - Display "FROM:" field of incoming messages incorrect. It uses "FromPC" instead of "FromUser" (PC28) - The "@DXCluster" field in FORWARD.SYS is not used (correctly???). Address a message to a (logged-on) user; in my case G1TLH (who is connected to GB7DJK). I have FORWARD.SYS like this: :GB7DXH >ALL >DX >QSL @GB7DJK END END Fixed. - *Incoming* messages are left with an entry in the Forward Queue, after they have been received by the DXNet. The "Fwd to" field is null, the date and time of the queue entry is suspicious. In my queue, 25-Sep-1998 00:00z for *every* incoming message. Cannot delete these queue entries using "FD", because they have no @Callsign ! Fixed. - The date/time stamp of incoming messages is incorrect; seems always to be "today" at 00:00z. Fixed. *** fix3a9-2 - User Command doesn't work under linux. Fixed (Tks F1TE). - If you enter a command line like either S/RR or SP/RR, a "return receipt" mail will be generated as soon as the addressee read the message. Return Receipt is not supported for public mail (=bulletin). Tks G0RDI for the help understanding the PC protocol. ** IMPORTANT ** : You must not set on the CluLink protocol if you are using the 3a9-2 fix when one of your adjacent is still running an older version. - A killed mail wasn't removed from the forwarding queue. Fixed (tks G0RDI). - Sending a BID number (when uploading a mail) crashed DxNet. Fixed (tks LA3WAA). - Some terminal problem (F3) are fixed when using the G8BPQ's switch (Tks G0RDI and LA3WAA). - A PC28 bulletin message arrives with the "StartPC" blank. Due to this ununderstandable things (stupid protocol ?), DxNet was forwarding the message back to the sender ! This "bug" with DxNet since v2 but has never been discovered. I was just thinking that the code of DxNet v2 was so much bad that the mistake could never be fixed. This is why I decided to rewritte to whole code (DxNet v3). BTW, this allows now to have a multi languages software for both dos and linux platforms. Thank you _very_ much to Iain, G0RDI, who has found this problem. - DxNet sends a bad PC^0^ protocol. This bug exists since a long time, I just missed to fix it before. So, fixed. - Link external problem fixed. You must add the row : external in the script\callsign.cfg file, where : is the hop-count you want to use to send the single PC19 protocol (with the callsign of your cluster) needed during the initialization sequence. You can also the default value ON (which is equal to 99). callsign is the callsign (without ssid) of the protocole configuration file of your adjacent with which to want a link external. If a "link external" link is enabled, the both commands NODE and USER of the protocol configuration file are not used. - PC41 (Home node data) was wrong. Fixed. - EU allows the sysop to Edit the user information of the user database. A normal user can also modifie his personnal information using this command. N Sets the name H Sets the Home Node Q Sets the QTH L Sets the locator WQ Writte the user information and quit Q! Quit without saving