eXodus Frequently Asked Questions
Alert and Error messages details:
Note: Use the Find feature of your browser to search this page.
<number> windows now contain urgent data. Please check the windows that are marked with a diamond in the rootless window menu.
Background windows have urgent messages. Bring them to the foreground to read the messages.
A color with this name already exists. Do you wish to replace it?
You are defining a new color name in the Server Settings, colors control panel that matches an existing color entry. Enter a different name or click Yes to replace the existing color entry.
A window couldn't be opened because of insufficient memory. Unfortunately, the client application has stopped running?
A client application attempted to open a new window, but had run out of application memory and the client stopped running. Increase the available memory.
Another window manager is running?
You are trying to launch a window manager to a screen that is already running a window manager. Typically this alert is generated when you try to start a window manager in rootless mode. When in rootless mode, eXodus uses it's own local window manager. If you need to run a remote window manager, you must use rooted mode. Click settings, Server settings, Screens, type and choose a mode.
Are you sure you want to abruptly halt the client, closing all of its windows?
You are using the Disconnect command in the Windows Menu to close a rootless client window(s).
Click Yes to disconnect the client.
Are you sure you want to delete the selected color(s)?
You have selected a color in the Server Settings, Colors panel and clicked Delete color. Click yes to remove the selected color from the color database.
Available memory is getting low.
Available memory is dangerously low. xxxx Proceed with care xxxx.
These messages indicate that you are running low on application memory. You can continue with your operations, but you may want to increase the application memory to avoid running out of memory. Click Quit to quit eXodus to avoid a system crash or Continue to return to the application.
Button Definitions conflicts with a menu Command key equivalent. To continue, you must change a definition?
Verify your modifier key settings and change one of your definitions. See chapter six for a complete list and description of each command.
Cannot initialize <protocol> driver. If you don't plan to use this driver and wish to avoid this alert, choose <protocol> from the Drivers Settings Dialog and deselect the Enable check box.
This alert appears if a network driver is not already installed on your system. To avoid this alert, you can un-initialize the driver interface for those drivers you don't have installed on your system. To do this, choose the protocol(s) you are not using from the Driver Settings from the settings menu. Deselect the Enable check box.
Can't open display.
This error indicates that the X client cannot find an X server at the provided IP address. The command may have the incorrect network address of your Macintosh, invalid server number, invalid screen number or be blocked by a firewall or proxy server. Check that the IP address is correct and the screen you are launching the client to is defined using the Edit Screens command. A quick test; Telnet to the host and from the command prompt try to Ping the IP address of the computer running eXodus. If it can't see your IP address, you may either have entered an incorrect address or may be attempting to through a firewall or similar impediment. Contact your network system administrator for assistance.
Cannot upgrade settings file: version not understood(<version>)
The current settings file was created with a more recent version of eXodus or the settings file has become corrupt. Use a more recent version of eXodus or trash the current settings file and create a new one.Updating Settings File: If you are upgrading your software to a newer version of eXodus, the alert box will display after you enter the serial number. Click Yes if you want eXodus to update your settings file. If you click NO, eXodus quits. You must then move, rename or delete your old settings file before running the new version. Note: You may wish to copy your existing Connections folder and settings file into the new eXodus folder.
Making a backup copy: The Save Settings As... command in the File menu will save the current settings file to a Copy of eXodus Settings file.
Client Launch Facility: Unable to complete connection?
eXodus is unable to remotely connect to the specified host. This error often occurs if the wrong host name or address was entered in the Connection Manager dialog box. The host is not available (for example shut down) or the host name or address was entered incorrectly.
Client Launch Facility: Unable to open a channel?
eXodus was unable to create/open a new communications channel. This message may appear if you are low on memory below 100k. Increase the available memory for eXodus by clicking once on the eXodus icon and choosing Get Info from the File menu on the desktop or by pressing Command I. Enter a larger number in the preferred size text field.
Client Launch Facility: <host system message>?
A host system error has occurred. Please refer to host system error documentation.
Client Launch Facility: Unable to resolve host name/address?
The host name entered for the client you are attempting to launch could not be resolved into a host address. If you are using a Hosts file on your Macintosh, make sure that it resides in your host folder and it contains your host node name and address. If you are resolving the host name using a Domain Name Server (DNS), verify that your TCP driver is installed and/or configured properly and that the DNS is also setup properly. Please refer to your Mac TCP documentation and/or see your system administrator.
Client Launch Facility: Unable to send connection information?
eXodus could not transmit the necessary information to establish a connection with the host system. The communications link between eXodus and the host system may have been broken. Try launching the client again. If this fails, check the following:
-
Host system is up and running on the network.
-
Network hardware/software are functioning properly.
-
Driver has not become corrupted.
-
Driver is not conflicting with other drivers on the system.
Client unable to convert to <format> format?
The client owning the current selection failed to convert it to the format specified by eXodus or could not store it in the property specified by eXodus.
Clipboard Transfer Error: The contents of the Macintosh Clipboard cannot be moved to a Selection.
Make sure the contents of the Macintosh Clipboard are in a supported format, "Text" and "Pict" or they have been corrupted. This message may also appear if you are low on memory (below 100K). Increase the available application memory.
Clipboard Transfer Error: Insufficient memory available.
eXodus was unable to transfer the contents of the Macintosh Clipboard to the specified Selection because the application had run out of memory. Increase the available application memory.
Clipboard Transfer Error: This Selection cannot be moved to the Macintosh Clipboard.
Make sure the application memory isn't to low (below 100K), clear the clipboard and try again.
Clipboard Transfer Error: Unable to paste Macintosh PICT into X String.
You tried to paste the Macintosh Clipboard containing Macintosh PICT data into an X client, but the client was expecting to receive text data.
Clipboard Transfer Error: Unable to paste Macintosh TEXT into X Pixmap.
You attempted to paste the Macintosh Clipboard containing Macintosh TEXT data into an X client, but the client was expecting to receive pixmap data.
Color <color> not found. eXodus will substitute default color (black).
The client application requested a color that was not defined within eXodus. Use the Server Settings Color Panel to add the specified color. Make sure to spell the color name EXACTLY as it appears in the message.
Command not found.
This is typically due to the client name being incorrect, the file path is not complete (for example, using the default X path of /usr/bin/X11/client when your host requires another, such as /usr/openwin/bin/client, or the client is not installed on that particular host.
Command key is being used in a mouse button definition.
Verify your modifier key settings.
Connect Channel: No new listening channel available (temporarily).
The client attempted to connect to eXodus, but no channels were available at that time. This message may appear if you are low on memory (below 100K). Increase the available application memory.
Could not find resource - <resource type>.
Reinstall eXodus, using the procedure outlined in the following FAQ.
Could not open default cursor font 'cursor'
eXodus could not find the correct fonts for the cursor. Make sure that the fonts are actually installed in the right place where eXodus can find them. To do that look on the "local fonts" tab of the eXodus control panel, at the directory listed there, and then look in that directory to verify that the eXodus fonts are actually installed there. If they are, then the fonts.dir file may have become corrupted. IN the fonts/misc folder. look for the file cursor.fon and change the name to altcursor.fon. Delete the file called fonts.dir. Restart eXodus and the fonts.dir file should be regenerated and the problem solved.
Do you really want to remove that client file?
You selected a client script name from the Connection Manager dialog box and clicked Remove. Click Yes to delete the client script, or click No to return to the Connection Manager dialog box without deleting the script.
Driver setup failed: Could not load driver for this client.
eXodus was unable to find the driver specified by the client script. Make sure the driver is installed properly and you only have one driver per protocol installed, ie.. make sure you only have one TCP/IP driver installed.
Error activating image DECW$client image file not found.
If this VMS error appears in screen 0, in an X window created by MSAX$CLIENT, it indicates that the client name entered in the Connection Manager dialog box does not exist on the host system, or that the client name was entered incorrectly.
Error creating client: Authorization failed - this connection cannot be made during an XDMCP session.
A client from an unauthorized host attempted to connect during an XDMCP session.
Error creating client: Could not create a new client.
This is because the number of clients running exceeded eXodus' maximum of 128.
Error creating client: Could not read connection prefix.
Error creating client: Length error in prefix for protocol authorization.
Error creating client: Length error in prefix for protocol string.
Make sure the available memory is not low(below100K). Increase the available application memory. Also, make sure the driver is installed properly and you only have one driver per protocol installed, ie.. make sure you only have one TCP/IP driver installed. If neither of these solutions correct the problem, log client/server communications and verify the client is sending the correct connection prefix.
Error creating client: No memory for connection information.
There is no available application memory to store connection information sent by the client.
Error creating client: Protocol version mismatch.
The X protocol version sent by the client application does not match the accepted X protocol version in eXodus.
Error creating client: User rejected connection.
This error appears after you click No in the Confirm Connections alert box. If you didn't mean to refuse the client connection request, launch client again.
ERROR: DECW$client not found on host.
This is a VMS error that could appear if the client name entered in the Connection Manager dialog box does not exist on the host system, or that the client name was entered incorrectly.
eXodus has recovered from initialization failure: A minimal (Rootless, Black&White) Screen 0 has been opened.
The settings you have choosen for Screen 0 require more memory than is available. Since eXodus cannot run without Screen 0, it tries to restore your old settings rather than cause a fatal error. If no previous settings are available, eXodus defaults to the screen which requires the least amount of memory: a Rootless, Black and White screen. To avoid this error, increase the available application memory.
eXodus has recovered from initialization failure: The previous Screen 0 settings have been restored.
The settings you have choosen for Screen 0 require more memory than is available. Since eXodus cannot run without Screen 0, it tries to restore your old settings rather than cause a fatal error. To avoid this error, increase the available application memory.
eXodus must perform a Reset for changes to take effect (killing active clients). Are you sure you want to do this?
Click Yes to reset eXodus. Click No to return to the Settings dialog box.
Fatal Program Error: Settings file has been corrupted.
Your current settings file has become corrupted. Trash you current settings file and use your backup settings file (if you have one). If you don't have a backup file, eXodus will create a new one with only the default settings.
Fatal Program Error: Unable to open default screen.
eXodus was unable to open the default rooted screen due to insufficient application memory. Increase memory.
File Transfer Protocol (FTP): The changes made will not affect currently active FTP sessions.
You made changes to the File Type and File Creator text fields in the MacTCP Driver Settings dialog box. These changes will not affect any current FTP sessions, but will affect any new sessions.
Illegal Screen Name: A screen or window with that name already exists!
You entered a screen or window name that is already being used by another screen (or window).
Illegal Screen Name: Screen names cannot begin with "-".
Enter a screen or window name that doesn't begin with a hyphen (-).
Initialization of the following driver failed: <driver name>
eXodus could not initialize the interface to the specified driver. Make sure the driver is installed properly and you only have one driver per protocol installed, ie.. make sure you only have one TCP/IP driver installed. Make sure you are not using NCSA Telnet/MacTCP and MacTCP. Also, check that the driver has not been disabled by a utility such as Aask.INIT from CE software or the Extensions Manager.
Invalid pixel size (<size>) for screen <screen#>
You are attempting to run eXodus using an unsupported screen depth. eXodus only supports 1-bit (black and white), 8-bit (256 colors), 16-bit (thousands) or 32-bit (millions) screen depths. It does not support 4-bit (16 colors).
Macintosh clipboard contains data longer than 32KB.
Displayed text will be truncated to 32KB. The contents of the clipboard exceed the maximum size that eXodus can paste. Any information beyond 32KB will not be pasted. To make sure you get all the data you need, copy it to the Macintosh Clipboard in smaller chunks.
Major revision protocol mismatch. Client major revision => <client major version>.
The client X major revision specified in the alert does not match the current eXodus X major revision. eXodus is compatible with version 11 of the X Window System from the X Consortium.
Memory allocation failed due to low memory. Proceed with care.
eXodus is running extremely low on application memory. Increase the available application memory immediately to avoid further problems. Click Quit to quit exodus to avoid a system crash or click Continue to return to the application. Note, continuing may cause a system crash.
Memory unavailable for connection information.
There is no available application memory to store connection information sent by the client.
Missing name for redirect
If your command line looks like "setenv DISPLAY $$ME$$ && <clientname>", the problem is that you have not yet edited the Command Line and the host is trying to act upon the default entry. The host should have no problem with the setenv DISPLAY $$ME$$ command, but the ,clientname> command will give it several problems; '<' and '>' are redirect symbols in UNIX. Their presence in the command line is telling the Host to try redirecting the output of an action or program to another location (this is what is giving you the "Missing name for redirect" error). In addition, the command "clientname" is not a real X or UNIX command. If the host were able to get past the '<' and '>' it would return and error complaining that the command was not found. A good command line to start with is:
setenv DISPLAY $$ME$$ && /usr/bin/X11/xterm -ls -sb
Only one key can be used for the Alt key. To continue, you must change a definition.
You selected X Alt Key from the "Use Command Key as" and "Use Option Key as" pop-up menus. Only one key can be designated as the X Meta Key.
Only one key can be used for the X Meta Key. To continue, you must change a definition.
Only one key, the Option Key or the Command Key, can be designated as the X Meta Key.
Option key is being used in a mouse button definition. Verify your new Modifier Key settings.
You cannot use the same definition for both a mouse button and a command key. Change one of them
Out of memory.
Increase the available application memory. Click Quit to quit exodus to avoid a system crash or click Continue to return to the application. Note, continuing may cause a system crash.
Permission Denied
The host has refused your connection. Verify that the account specified in the Connection Manager dialog box has the correct privileges to login to the host. Refer to your operation system documentation or your system administrator to assign the correct privileges.
Please re-enter a name beginning with A-z or 0-9.
You tried to enter a color name beginning with an invalid character. Enter a name beginning with an alphanumeric character (a-z, A-Z or 0-9).
Possibly fatal low memory error occurred. Running client may cause system crash. Do you wish to kill client?
This message appears when a client is running, but the available memory is low. Increase the available application memory. Click Quit to quit exodus to avoid a system crash or click Continue to return to the application. Note, continuing may cause a system crash.
Remote Connection Error: Unable to complete connection.
eXodus is unable to connect to the remote font server specified in the Default Font Settings dialog box. This error often occurs if an incorrect host name or port number was entered in the Default Font Settings dialog box or in the MacTCP hosts file
Remote Connection Error: Unable to connect, timeout expired.
eXodus is unable to connect to the remote font server specified in the Default Font Settings dialog box. This alert may appear if the host is not available (for example, powered down) or if there are long network delays unrelated to eXodus.
Remote Connection Error: Unable to open channel.
eXodus could not create/open a new communications channel due to a networking problem, therefore it cannot connect to the remote font server. This message may appear if you are low on memory (below 100K). Increase the available application memory.
Remote Connection Error: Unable to resolve host name/address.
The address you entered in remote font server name does not exist. - or - The host name you entered could not be resolved into a host address. If you are using a Hosts file on your Macintosh, make sure that it resides in your System Folder and that it contains your host node name and address (refer to your MacTCP documentation). If you are resolving the host name using a Domain Name Server (DNS), verify that your TCP/IP driver is installed and/or configured properly and that the DNS is also set-up properly (refer to your MacTCP documentation and/or see your system administrator).
Replace Keymap <New Keymap>?
You are saving the current keymap settings using the name of an existing keymap. Click OK to overwrite the existing keymap or click Cancel if you do not want to save the current keymap.
Save changes to client file?
You made changes to your client file and have selected Quit without saving your changes. Click Yes if you wish to save your changes.
Screen <screen #> has an invalid depth. Defaulting to 1 (monochrome).
You are attempting to run eXodus using an unsupported screen depth. It does not support 4 bit (16 colors).
Should eXodus update your settings file to be compatible with the current version?
Your current settings file was created with an older version of eXodus than you are currently using. You may want to make a backup of your old settings file before you update it (in case you want to run the old version of eXodus again with that settings file). Otherwise, click Yes to update the settings file. This will make it compatible with your newer version of eXodus, but it will no longer be compatible with the older version.
Text buffer full. All prior text in monitor window will be deleted.
The monitor window's text buffer is full. All text stored in the window's buffer will be deleted.
The color <color> is not defined. Do you wish to define this color now?
You have defined a color in the client script that does not exist in eXodus. Click Yes to define the color using the Macintosh Color Wheel. After you click OK in the Macintosh Color Wheel dialog box, the color is added to the list of colors in the Color Editor and the client appears with the color you specified. Clicking No results in another alert notifying you that the default color, black, will be used for the missing color.
The file <filename> was not found. Please remove or modify the following font path element: '<font path element>'
The font files ‘fonts.dir’ and ‘fonts.alias’ could not be found using the current font path element defined within eXodus. Click OK and set the font path element to point to a font folder containing the fonts.dir and fonts.alias files.
The window resize command failed because of insufficient memory. Unfortunately, the client application has stopped running.
A client application attempted to resize one of its windows, but ran out of application memory and the client stopped running. Increase the available application memory.
The window resize command failed because of insufficient memory. Its previous size has been restored.
A client application attempted to resize one of its windows, but ran out of application memory. Increase the available application memory.
The X selection is empty (contains no data).
You chose Print or Copy, but the primary X selection currently contains no data. Make sure a selection has been made in the client window and check that the client supports the primary selection. If the client does not support the primary selection mechanism, use the Clipboard Transfer command.
The X server's font server protocol version (<X server protocol version>) does not match that of the remote font server (<font server protocol version>).
The version of the font server built into eXodus doesn't match the version of the font server on the host. eXodus has Font Server Version 2. See your system administrator to determine the version of the font server implemented on the host.
The X server is not authorized to connect to the remote font server.
eXodus does not support font server authorization mechanisms. If your computing environment requires access to a font server requiring authorization, contact Technical Support at Powerlan USA. Refer to Appendix A, “Technical Support” for more information.
There are active clients. Do you still wish to Reset?
You chose to reset eXodus while there were X clients running. It is recommended that you quit from X clients before resetting eXodus.
There are active clients. Do you still wish to Quit?
You chose to quit eXodus while there were X clients running. It is recommended that you quit from X clients before quitting eXodus, then quit from eXodus.
There is not enough memory available to open eXodus <memory needed, memory available>. Do you want to open it using available memory?
eXodus needs more memory than is currently available. Opening it may cause unpredictable results. Either assign less memory to the eXodus application or increase the available system memory.
The window <Test> now contains urgent data. Please bring it to the foreground.
The window <test> has an urgent message. Bring the window to the foreground in order to the message.
This keyboard mapping does not allow the Option key to be a modifier.
You have selected Macintosh (Intl) from the Keyboard Mapping hierarchical menu, which requires that the Option key be used to generate extended characters. The Option key is currently defined as an X modifier key in the Modifier Settings dialog box. If you click Yes, eXodus disables the “Use Option Key as:” pop-up menu (in the Modifier Settings dialog box) so the Option key is available for keyboard mapping. Clicking No in the alert returns you to eXodus without changing the keyboard mapping or the Modifier Key settings.
To run eXodus, do the following: Move, rename, or delete your old settings file.
You are using an old settings file with a newer version of eXodus, and you did not to update your settings file. Move, rename, or delete your old settings file before restarting eXodus.
Unable to access cursor font => <cursor font>.
eXodus requires the Default Cursor Font specified in the Default Font Settings dialog box to exist in either the fonts.dir or fonts.alias files. Change the font, or click Cancel in the Default Font Settings dialog box to use the existing font name. The default value is “cursor”.
Unable to access text font => <text font>. Please modify text font and/or font path.
eXodus requires the Default Text Font specified in the Default Font Settings dialog box to exist in a fonts.dir or fonts.alias file. Change the font, or click Cancel in the Default Font Settings dialog box to use the existing font name. The default value is “fixed”.
Unable to connect to the remote font server named: <font server>.
eXodus was unable to connect to the specified remote font server. Make sure you entered the host name or address correctly. See “Designating a Default Font Path” in the eXodus Reference Guide for information on defining a remote font server path. Also, see your system administrator to ensure that the remote font server is running and that there are no current networking problems.
Unable to create default colormap.
eXodus ran out of application memory. Increase the available application memory.
Unable to establish connection.
eXodus is unable to establish a connection with client application. Make sure the available memory is not low (below 100K). If necessary, increase the available application memory. If this does not correct the problem, log client/server communications (using the Log Clients command from the Settings menu) and verify that client is sending the correct connection prefix.
Unable to open new settings file => <filename>
eXodus could not save a copy of the settings file. Check available disk storage or try using a different filename in the Save Settings as dialog box.
Unable to process URL.
You are either trying to paste a URL from the Macintosh Clipboard into the Connection Manager Client Information or a URL from another application such as Internet Config. The URL contains invalid data.
Unsupported copy format => <format>.
You attempted to paste the Macintosh Clipboard into an X client, but eXodus was unable to convert the Macintosh Clipboard into a format supported by the client.
Unsupported paste format => <format>.
You attempted to paste a selection into the Macintosh Clipboard, but the client owning the selection was unable to convert the selection into a format currently supported by eXodus.
Value out of legal range (<min. value> to <max. value>).
You have entered a value that is outside the specified range of values. Enter a value within the specified range of values.
XDMCP Message: A host name must be specified to use this start-up mode.
While in Query or Indirect mode, a host name is required. Either enter the name of a valid TCP/IP host, or switch to an XDMCP mode that does not require one (Broadcast or Not In Use).
XDMCP Message: A write error occurred: can't send data.
This message may appear because eXodus can't connect to the host you have specified. Verify that you are correctly specifying the host computer you choose to connect to. As an alternative, try using Broadcast mode.
XDMCP Message: Authorization failure: This connection cannot be made during an XDMCP session.
Clients can connect if they can obtain the “Magic Cookie” for authorization. This is a file in the user's home directory created by XDMCP. Therefore, clients from the same host, and any other hosts that cross-mount the user's home directory, can connect.
XDMCP Message: Host sent DECLINE:
XDMCP Message: Host sent FAILED:
These messages are the result of an XDMCP session that started, but somehow failed along the way. eXodus restarts the process, trying again to initiate a session on the host. The probable cause for such errors depends on how xdm is implemented on the host, and may also be due to network errors. If eXodus consistently returns this error, the host implementation should be checked. If it is an uncommon occurrence, it may be due to network traffic.
XDMCP Message: Host sent UNWILLING:
While in Query or Indirect mode, the xdm program on the specified host has indicated that it will not allow eXodus to connect. This could happen for a number of reasons, but it is most likely because the host does not recognize the Macintosh as a valid “terminal.” See your system administrator to make sure your Macintosh is recognized by xdm for an X server or terminal.
XDMCP Message: Timed out waiting to read data.
A timeout occurred during a critical part of the XDMCP session-starting function. Since an important message was not received promptly, eXodus restarted the connection. Verify that xdm is running properly on your host, and that you are not experiencing network problems.
XDMCP Message: Unable to create XDMCP stream.
This may appear if the TCP/IP driver is not working properly.
XDMCP Message: XDMCP is being turned off because the TCP/IP driver cannot be opened.
You are trying to use XDMCP, but the TCP/IP driver apparently is not installed properly. Install (or reinstall) MacTCP.
You forgot to enter a default font path. Please enter one now.
The Default Font Path Elements text field is empty. eXodus requires access to a fonts folder that contains the fonts.dir and fonts.alias files. Designate a font path in the Server Settings, Font Paths panel. See “Designating a Local Font Path or “Designating a Font Server” in the eXodus Reference Guide for more information.
You forgot to enter a default text font. Please enter one now.
The Default Text Font text field is empty. After you click OK in the alert, the Default Font Settings dialog box displays. Enter a font name in the Default Text Font text field and click OK. The default value for this field is “fixed”.
You forgot to enter a default cursor font. Please enter one now.
The Default Cursor Font text field is empty. After you click OK in the alert, the Default Font Settings dialog box displays. Enter a font name in the Default Cursor Font text field and click OK. The default value for this field is “cursor”.
You have matching button definitions. To continue, you must change one.
You defined two or more mouse buttons the same in the Mouse Buttons dialog box. Change one of the button definitions. Make sure the Command and Option check boxes in the Keyboard Mapping dialog are set correctly. These options may be disabled, causing eXodus to recognize two buttons with the same definition.
Should you have any questions or issues please use our Support Request Form.
NOTE: For discontinued products or products no longer in development, contact Sales at 603.880.9118 or via e-mail at: sales@powerlan-usa.com.
|
