Node Status

The sysop can customize the strings used to represent the state of Terminal Server nodes and the actions of users when a node is in-use.

Static

To replace node status or activity strings with static custom or translated text, create or modify a ctrl/text.ini file and in the root section, set the desired NodeStatus* or NodeActivity* text.dat string IDs to your desired custom/translated string.

NodeStatusWaitingForCall
NodeStatusLogon
NodeStatusNewUser
NodeStatusOffline
NodeStatusEventWaiting
NodeStatusEventRunning
NodeStatusEventLimbo
NodeStatusLogout

NodeActivityMainMenu
NodeActivityReadingMsgs
NodeActivityReadingMail
NodeActivitySendingMail
NodeActivityReadingTextFiles
NodeActivityReadingSentMail
NodeActivityPostingMsg
NodeActivityAutoMsg
NodeActivityXtrnMenu
NodeActivityRunningXtrn
NodeActivitySettings
NodeActivityFileMenu
NodeActivityDownloadingFile
NodeActivityUploadingFile
NodeActivityBiXferFile
NodeActivityListingFiles
NodeActivityLoggingOn
NodeActivityLocalChat
NodeActivityChatChannel
NodeActivityGlobalChat
NodeActivityChatMenu
NodeActivitySysop
NodeActivityQWKmenu
NodeActivityNodeChat
NodeActivityPagingNode
NodeActivityRetrievingFile
NodeActivityCustom

Dynamic

To replace “in-use” node action/activity strings dynamically (during run-time, e.g. while a user is connected to a terminal server node), use the Baja or JavaScript replace_text functionality to replace the NodeAction* text.dat string corresponding with the current node action value (e.g. set the NodeActionCustom string when setting the current node action value to NODE_CUSTOM from load/nodedefs.js).