Main Command Menu

Introduction

Navigation Console

Global Commands

Hidden Keys (Not on Menu)

<&> Synchronize Local Session

When running the game on one computer and accessing the data files over a network on another computer, the synchronization of the computer clocks becomes important. If one clock is not synchronized, a player on that computer may not be able to send and/or receive messages. This function can be used to synchronize other computers to the computer from which the command is invoked. When you use the & command, Trade Wars attempts to synchronize the clock for each local session, and ignores sessions with a dial-in connection. This command is not accessible from a dial-in connection.

See TWSYSOP.DOC under troubleshooting for more details on this command.

<|> Toggle Message Silencer

The Computer/Personal Settings option to toggle the message silencer mode can be triggered with this global key. With the silencer on, you will not receive any incoming messages.

<<> Return to Previous Sector

This function can be used to quickly return to the sector from which you just came. Particularly useful in port-pair situations, where you can effortlessly move between two adjacent paired ports.

NOTE: Use of <,> (no shift) has been discontinued as of v3.05.

<@> Game Details

This global command displays important information about the active game session.

Header:

The title area displays the Trade Wars version, and the environment that the game thinks it is running under. If this is incorrect, the game may not function properly. Supported environments are WinNT/95, Win 3.1, DOS, OS2, and DESQview.

Example:

Trade Wars 2002 Version 3.05

WinNT Detected.

Memory Status:

Displays the current memory available to this session, as well as the largest free block and minimum bytes available so far. If, while at the main command prompt, the current memory is much greater than 30K, you might consider overriding the BUFFER size to make more memory available for the overlay buffer. This will increase the game's efficiency. See the BUFFER parameter in TWSYSOP.DOC included with the game.

The minimum bytes available value is a danger flag. If this value becomes low in relation to the Object Memory, you may need to attempt to gain more memory for your sessions, or BIGBANG a smaller universe.

Example:

32,392 bytes available.

32,392 largest free block available.

29,792 minimum bytes available this session.

Stack Status:

Displays the current and minimum stack available to the game. The minimum value is an estimate, and the actual value is always less than or equal to this amount. The stack allocation is static and defined when the game is compiled. If you find the stack running dangerously low, report it to Martech, and we'll increase the stack size with the next release.

Example:

32,920 stack bytes available.

30,154 minimum stack bytes available this session.

Object Allocation Status:

Indicates the current and maximum pool of memory allocated for dynamic structures within the game. This pool grows and shrinks as you access different features of the game.

Example:

132,856 bytes allocated.

135,456 maximum bytes allocated.

Overlay Buffer Statistics:

These stats help you determine the optimum overlay configuration for your system. By default, the program attempts to allow about 135,000 bytes for dynamic allocation, and leave 30,000 bytes available for future allocation after entering the game. The rest of memory available is given to the overlay buffer. A minimum buffer size currently is 46,000 bytes. In order to meet this requirement, your game may show less than 30,000 bytes free at the main command prompt.

You can set this value yourself with the BUFFER= command line parameter (see RUNNING TW2002 ON YOUR BBS in TWSYSOP.DOC included with the game) to free up some more memory, or increase the buffer size to improve game performance. The Reload Count gives an indication of the number of times an overlay has been reloaded. A smaller buffer will result in a higher reload count, and a larger buffer a smaller count.

If this line reports "Loading from disk", then you have either disabled EMS, or there wasn't enough EMS memory available to load the overlay file. If you're using some sort of disk caching, there's no need to load the overlay into EMS. If you intend to use EMS, the game requires enough memory to hold the entire TW2002.OVR file. At this release, 460K will suffice.

Example:

Size 58,000 Bytes, Reload Count 99, Loading from EMS.

Average Interval Lag:

Another warning sign, this value should remain small. This is a measurement of the average amount of time spent in interval processing. If it approaches or exceeds the interval period (the delay between background processes, typically one second), there is too much load on the game. Move odds for Aliens and Ferrengi will effect this load, particularly in long-running games.

Example:

0 hundredths

Introduction

Exit Help

Global Commands