Sitatex for Windows


1.1 How do I change the password in Sitatex for Windows X28?

In the dial gateway choose Configure/Parameters/Session Parameters. Here you can change the password by first typing the old password and then the new password. If you do not know the old password please refer to the next item.


1.2 How do I reset the password in Sitatex for Windows X28?

There is no direct button to force the password to default. However, a workaround is to go into the dial gateway and look at Configure/Parameters/Sessions and change the session address to something different. If you then revert back to the original session address the system will think it is a new session and ask for a new password without first asking for the old one.


1.3 How do I change the password in Sitatex for Windows X25/P1024C?

Go into the Gateway Setup and select the appropriate session. Choose Session/Edit/MMS-Password. Here you can directly enter any new suitable password.


1.4 How do I reset the password in Sitatex for Windows X25/P1024C?

Go into the Gateway Setup and select the appropriate session. Choose Session/Edit/MSS-Password. Here you will find a button saying ‘Set Default’ which will reset the password into PASSWD


2 In Sitatex for Windows X28 V3.2C I cannot install disk 6.

When installing Sitatex for Windows V3.2C/X28 the software contained on disk 6 is not needed and the installation program will skip that disk, asking for disk7 after disk5. This is normal behavior!


3 Can my company set up our own public address book instead of using SITA's?

Yes, this can be done with the DIRMGR utility, which can be found in the \WINGW\BIN directory.


4 In the user configuration, the origin address cannot be modified.

To change that, launch Gateway Setup (GS.EXE).
Then double-click on the "session address".
A window named "Edit Session ( Session Identifier : xxx )" will open
On the 5th line, called "Edit Address Privilege:" there is a check box which is probably not checked. If you check it, the user will be able to change the origin address.


5 Why is there a musical note in my IN/OUT Box Summary

This indicates that this message has information in the usernotes. The UserNotes is the equivalent of a Post-It note on a printed message and can contain information entered either by the user or by the system. When the information is entered by the system it very often means that it is an incomplete message. Messages have a limited maximum size and before being transferred can be split up in several smaller parts when needed. Sitatex for Windows will try and reassemble all these parts into the origi nal message but if it fails to do so because one part was missing it will indicate so by adding a musical note to the list in the in/out box.


6 My gateway will not recognize my Eicon card.

By default the Eicon install program adds some commands to the autoexec.bat. One of these is the ECBIOS START command. However, it does not put some very much-needed parameters. The proper syntax is: ECBIOS START /I 5A When the card used is an Eicon C2x card you should add even more: ECBIOS START /I 5A /READPORT ANY


7 My gateway crashes often, mostly when I start a DOS session.

The Eicon installation often 'forgets' to add a needed line to the SYSTEM.INI file in the windows directory. This line should be under the [386ENH] and read: DEVICE=C:\WINGW\VNABIOS where of course the C:\WINGW should be changed if the files resides in a different drive or directory.


8 How do I copy messages from one machine to the other?

Create an 'Archive volume' on a floppy disk or the LAN and file the concerned messages to that volume. Than open that same volume on the destination machine and copy the concerned message over.


9 How do I copy folders from machine to the other?

This slightly more complicated. First you have to find the file name of the folders by single clicking it, do not open it! Now click on 'details' and you will see the real filename. Second, copy that file from the Folders directory onto a diskette or the LAN and on the destination machine exit Sitatex. Now copy the file into the Folders directory on the new machine (If needed, rename it first to another number). Lastly go up one level from the folders directory and delete the file FOLDERS.DBS. This f ile will be automatically rebuilt and the new folder should be there.


10 Why is there an empty page after every message I print?

This is a feature (not a bug!) from Windows. Sitatex uses the Windows print spooler to print and this spooler inserts a formfeed in between jobs to separate them. The only way to save a rainforest in this case is to stop printing every single message. If that is not an option then the paper waste can be cut down by setting the paper size to something like envelop or maybe even a custom size. Of course this means that a long message would be cut in multiple smaller ones.
There is no way to completely stop the formfeed.


11 I forgot the password of my folders and now cannot read the messages anymore.

An undocumented feature (or bug) is that when you run a password protected folder through the repair folder program that process will remove the password and you can normally access the folder.


12 How do I make Sitatex for Windows print messages automatically?

In Sitatex for Windows these tasks are done via the so-called 'Assistant'. You can find the assistant under an icon in the shape of a Swiss-army knife.


13 I try to filter out messages but now receive nothing anymore.

Please be aware that when you apply ‘Exclude’ filters there also has to be at least one include filter. If you only have an exclude and no include filters you will not receive anything


14 How many sessions and users can I realistically configure?

The theoretical maximum number of sessions and users for the different versions are:
X281 session with 16 users
X251000 sessions with each 1000 users
P1024C31 sessions with each 1000 users

Note that these are theoretical maximum. For example, the X28 gateway can be configured with more than 16 users but it is very strongly recommended not to do so as it would severely impact the performance.

With the X25 or P1024C gateway you can handle many more sessions and users but the 1000 is a purely theoretical maximum. The hardware needed to handle this sort of amounts has not yet been invented. Some guidelines are:
Number of SessionsCPU TypeCPU SpeedMemory
1 to 10Pentium7532 MB
10 to 32Pentium133+32 MB
32 to 64Pentium200+32 MB
Greater than 64Pentium233+64 MB

Of course these are not mandatory, they serve as guidelines. If you have many messages you will need more processing power, not so many users you can get away with less, etc, etc.


15 Why can I only have 6528 messages in one folder?

This is because of a function of Windows, which is used by the Sitatex program to build a list like a list of messages. This function only allows 6528 entries so more than that is not possible.


16 Some of my folders have a little bomb in front of the name, what does that mean?

This normally means that the folder is reaching the maximum capacity. You can check this by selecting the folder and then click details. This will show you the maximum number of entries possible in that folder and can be enlarged if needed.


17 What is the function of the REL000x directories on the LAN versions?

Normally when you need to update a program with a new version everybody would first have to shutdown that program. In a large setup with many users this would be a major annoyance so a system has been devised in which this is not needed.

Every program module in SFW consists of two parts; for example the gateway setup program consists of: WINGW\BIN\GS.EXE
WINGW\BIN\REL0000\GS!.EXE.

When the user executes GS.EXE it will look in the highest REL000x directory for the GS!.EXE program which it will call. When you upgrade the software a new REL000x directory will be made with the latest version in that directory. Now if you exit and start the program again, it will automatically load the newest version.


18 Can I use the LAN and the dialup version at the same time?

Yes. There are some restrictions though. First of all both the LAN and the X28 version have to be the same release i.e. if the LAN version is 2.1 the X28 version also has to be 2.1. Since LAN 1.2 and X28 2.1 were never released to customers they could (in theory) not use a dualmode system. The only customer-released version that has dualmode capabilities is V3.2C.

With the Sitatex for Windows/LAN version the gateway controls the session. Therefore if you switch off the workstation the messages will still be delivered to the gateway and will not be queued in the MSS until the X28 version makes a session. This makes it necessary to close the session before you switch from LAN to X28 and open it when you switch from X28 to LAN.

This opening and closing creates a problem with document transfer. When a user receives a document he does not see this until the document is complete or until a certain timer expires. If this timer expires he gets to see only that part that was received up to now and since it was not yet complete he cannot do anything with it.

If the user starts received a document in one version and halfway through the reception of the document he switches to the other version that would result in two incomplete documents. Therefore, before closing a session make sure that no document transfer is in progress.

The third problem is where people share a session with several users. If one of the users decides to close the session all other users from that session are affected so if somebody wants to use 'dual mode' he has to make sure he does not create problems for other users.

Once the above is understood you can install the dual mode by first installing the LAN version. When configuring the user in the Session Manager use the default directory on a local drive for the User Working Path. Finish the installation as if you are installing a normal single mode LAN user.

Once that is all ok you can install the X28 version onto the same drive and configure that as a normal X28 station.

Once that is done you can run the SETMODE program to make sure the two versions work together.

To open or close the session you can use the Session Manager. Choose Session/Close Requests from the main menu and click one of the available boxes to close the session. To open the session again go into the same menu and uncheck any boxes which are ticked.

N.B.: please be aware that the opening and closing of the session is not instantaneous but might take up to 10 minutes.


19 When trying to run SETMODE it complaints about MFC250.DLL not found.

The SETMODE.EXE program is most likely in the \WINGW\BIN directory but the MFC250.DLL program is in \WINGW\BIN\REL000x directory. The easiest way to get this to work is to copy one of the two to the other directory.


20 My existing station can send but not receive messages.

Not applicable.


21 Can I run Sitatex under Windows 95/98/NT?

Yes. Sitatex for Windows is a 16 bits Windows application but it will work ok in Windows 95/98/NT. Note only that long filenames are not supported in the current Sitatex for Windows versions.


22 Every now and then I receive hundreds of old messages again.

In Sitatex for Windows it can happen that every now and then you receive hundreds of old messages again even though they might have been filed, killed, purged, etc weeks before. This is due to a problem of a corrupted pointer file, which may come from some older versions of NetWare Client Software.

In Sitatex V1.x or V2.x there is no way to solve this but in Sitatex V3 the problem can be overcome by creating a little file called SECURE.RP in the WINGW\CONFIG directory. The file can be empty as it is not the contents of the file which will trigger a solution to this problem, but the creation of the file and the availability of it.

Note that while this solves the problem it also has a minor impact on the system performance.


23 Sitatex For Windows Error Prompts

Cannot create: <file>

Cause: Cannot create the named file.
Action: Ensure that the access rights to the directory are: r, w, c.
Ensure that the path exists.
Ensure that there is sufficient space on the disk.

DNA is not set

Cause: The Data Network Address of the SITA messaging service host has not been entered.
Action: Type the DNA of the SITA messaging service host (9001234)

Drive format invalid

Cause: The drive set (on command line or in WSTXDRV environment variable) contains an invalid drive.
Action: Ensure that the drive specified on command line and in WSTXDRV environment variable is correct.

Error: Not enough memory

Cause: There is insufficient memory to run the Gateway.
Action: Close some applications to free enough space to run the Gateway.

Error in Communication Queue Path creation

This path is specified with Gateway Setup utility.
Cause : 1) The Gateway is unable to create the Communication Queue path.
2) The disk is full.
Action :1) Ensure that the access rights are correct.
2) Free sufficient space on disk

Error in configuration DNA does not exist

Cause : The Data Network Address of the SITA messaging service host computer has not been entered. Action: Type the DNA of the SITA messaging service host, see Network Parameters on page 5 - 13, and contact the registered NUI manager in your company.

Error in MSGSVR.LOG or MSGSVR.STA File Creation

These file are located under x:\WINGW\DATA, where x is the drive on which SITATEX for Windows is installed.
Cause: 1) Message Server is unable to create the MSGSVR.LOG or MSGSVR.STA file.
2) Disk is full.
3) Data path has been destroyed
Action:1) Ensure that the access rights are correct.
2) Free space on disk.
3) Reinstall SITATEX for Windows.

Error in TELCO.IMA File Access

This file is located under x:\WINGW\DATA, where x is the drive on which SITATEX for Windows is installed.
Cause: The Gateway is unable to access the TELCO.IMA file.
2) TELCO.IMA file has been destroyed.
Action:1) Ensure that the access rights are correct.
2) Stop, then restart the Gateway to create the TELCO.IMA file.

Error in TELCO.LOG File Access

This file is located under x:\WINGW\DATA, where x is the drive on which SITATEX for Windows is installed.
Cause: 1) TELCO.LOG is locked by another application. For example, Gateway Monitor.
2) The TELCO.LOG file has been destroyed.
3) The disk is full.
Action:1) Identify the application that locked TELCO.LOG and close it.
2) Stop then restart the Gateway to create the TELCO.LOG file.
3) Free space on disk.

Error in TELCO.STA File Access

This file is located under x:\WINGW\DATA, where x is the drive on which SITATEX for Windows is installed.
Cause:1) The Gateway is unable to access the TELCO.STA file.
2) TELCO.STA file has been destroyed.
Action:1) Ensure that the access rights are correct.
2) Stop then restart the Gateway to create the TELCO.STA file.

Error in updating TELCO.STA Statistics file.

This file is located under x:\WINGW\DATA, where x is the drive on which SITATEX for Windows is installed.
Cause:1) The Gateway is unable to write to the TELCO.STA file.
2) TELCO.STA file has been destroyed.
3) TELCO.STA file is locked by another application.
4) Disk is full.
Action:1) Ensure that the access rights are correct.
2) Stop then start the Gateway to create the TELCO.STA file.
3) Identify the application that locked TELCO.STA and close it. If TELCO.STA is always locked, disconnect the guilty application from the LAN to release resources.
4) Free space on disk..

Error loading CONFX28.DLL Cause : An error occurred while loading the file CONFX28.DLL.
Action: Ensure that the file exists, if it does not, re-install SITATEX for Windows Standalone.

Error when launching the Message Server
Cause: 1) Insufficient memory available to run the Message Server
2) The file MSGSVR.EXE does not exist in the directory \WINGW.
Action:1) Free enough space to run the Message Server
2) Re-install SITATEX for Windows Standalone.

Failed to create empty document

Cause :This message may occur immediately after another error message.
Action:None.

File error: <file>
Cause:An error occurred reading from or writing to the named file.
Action:1) Ensure that the access rights to the directory are: r ,w, c.
2) Ensure that the path exists.
3) Ensure that there is sufficient space on the disk.

File not found: <file>

Cause:

The named file was not found on the specified path.

Action:

1) Ensure that the access rights to the directory are: r, w, c.

2) Ensure that the path exists.

Invalid STXDLL.DLL version
Cause: The version of the STXDLL.DLL loaded is not the one needed by the Gateway.
Action:1) Verify the version of the STXDLL.DLL in the x:\WINGW\BIN\REL.nnnn directory, where x is the drive
on which Windows is installed.
2) Check if there is a remaining old version of STXDLL.DLL in DOS path (C:\WINDOWS\SYSTEM for instance)
3) An application using an older version XSDLL.DLL is running. Stop the application and upgrade it to use the current version of XSDLL.DLL.

Invalid XSDLL.DLL version
Cause:The version of the XSDLL.DLL loaded is not the one needed by the Gateway.
Action:1) Check the version of the XSDLL.DLL in the x:\WINGW\BIN\REL.nnnn directory, where x is the drive
on which SITATEX for Windows is installed.
2) Check if there is a remaining old version of XSDLL.DLL in DOS path C:\WINDOWS\SYSTEM for instance)
3) An application using an older version XSDLL.DLL is running. Stop the application and upgrade it to use the current version of XSDLL.DLL.

Missing Gateway Configuration File

This file is located under x:\WINGW\CONFIG, where x is the drive on which SITATEX for Windows is installed.
Cause: 1) Message Server is unable to access the GWSESS.CNF file.
2) The drive set (on command line or in WSTXDRV environment variable) does not refer to the drive on which SITATEX for Windows is installed.
3) Config path has been destroyed.
Action:1) Ensure that the access rights are correct.
2) Ensure that the drive specified on command line and in WSTXDRV environment variable is correct.
3) Reinstall SITATEX for Windows.

MSS password is not set

Cause: The MSS password of the session has not been entered.
Action:Type the MSS password for the session.

NUI number is not set

Cause: The Network User Identifier has not been entered.
Action:Type the NUI for the SITATEX station.

NUI password is not set

Cause: The Network User Identifier password has not been entered.
Action: Type the NUI password for the SITATEX station.

Phone number is not set

Cause: The Telephone number of the X.28 PAD has not been entered.
Action:Select the phone number of the X.28 PAD from the PAD directory.

Please SET your drive on command line as follows: WINGW.EXE /drive

Cause: The format of the application command line WINGW is not correct.
Action:Verify the format of the command WINGW as specified in the message. It is also possible to set WSTXDRV environment variable in the AUTOEXEC.BAT file. See Modifying System Start-up Files for more information.

Please set your SITATEX environment. Use SET WSTXDRV=drive command.

Cause: The environment variable has not been set.
Action:Set the WSTXDRV variable to point to the drive SITATEX for Windows Standalone is installed on.

Session Address is not set

Cause: The session address of the Gateway has not been entered.
Action:Type the session address, the session address is shown on the Connection Request Acknowledgment message.

TELCO.LOG corrupted.

Cause: The file TELCO.LOG has been corrupted.
Action:Delete the file TELCO.LOG, it is recreated automatically. If the error persists, contact your local Help Desk.

The WINSTX Data path does not exist.

This path is named x:\WINGW\DATA, where x is the drive on which SITATEX for Windows is installed.

Cause: Installation of SITATEX for Windows was not successfully completed or data path has been destroyed.
Action:Reinstall SITATEX for Windows.

User Password not correct Please retry

Cause: The user password typed is not correct.
Action:Type the correct user password. The default value is PASSWORD.

USRMODEM.DBS corrupt or does not exist.

Cause: The file USRMODEM.DBS has been corrupted or deleted.
Action:If you do not have a backup copy of this file, re-install SITATEX for Windows, this creates a new empty USRMODEM.DBS file with the correct format.

WINSTX Config path does not exist.

This path is named x:\WINGW\CONFIG, where x is the drive on which SITATEX for Windows is installed.
Cause: 1) The drive set (on command line or in WSTXDRV environment variable) does not refer to the drive on
which SITATEX for Windows is installed.
2) Installation of SITATEX for Windows was not successfully completed.
3) Config path has been destroyed.
Action:1) Ensure that the drive specified on command line and in WSTXDRV environment variable is correct.
2) Reinstall SITATEX for Windows.

WINSTX comqueue path does not exist
Cause: 1) The variable WSTXDRV is incorrect or does not exist.
2) The specified path does not exist.
Action:1) Ensure that the variable WSTXDRV is correct.
Ensure the path is correct.
3) If the problem persists, re-install SITATEX for Windows.

WINSTX data path does not exist
Cause: 1) The variable WSTXDRV is incorrect or does not exist.
2) The specified path does not exist.
Action:1) Ensure that the variable WSTXDRV is correct.
2) Ensure the path is correct.
3) If the problem persists, re-install SITATEX for Windows.

X.25 Configuration Detected. Please change your WSTXDRV variable

Cause: The Gateway found an X.25 configuration file on the specified path.
Action:Change the WSTXDRV variable to point to the drive on which SITATEX for Windows Standalone is installed.

X28MODEM.DBS corrupt or does not exist.

Cause: The file X28MODEM.DBS has been corrupted or deleted.
Action:Re-install SITATEX for Windows to restore the SITA modem database file.


24 Events appearing in the Telecommunications Log

Below is the Sitatex for Windows X28 dial screen. This shows you the status of various components during a dialup session:
On the screen you can see pictograms for the components involved i.e. the Computer, the Modem, the PAD or SITA Network and the host or MSS. During session establishement or session ending you will see start to appear or disappear to indicate what stage the connection is in. If something goes wrong it is important to find out where it goes wrong i.e. in which stage. The stage is identified by the message and the two concerned components. In the picture below the different components are numbered to help you identify them.

In the dialing process there are a number of distinctive steps going from the PC to the modem, from the modem to the PAD and from the PAD to the MSS. The steps are:
step:Component:Stage:
1Initialize modemBetween the computer (1) and the modem (2).
2Open PAD sessionBetween the modem (2) and the PAD (3).
3Open MSS sessionBetween the PAD (3) and the MSS (4).
4Exchange messages and documentsBetween the PC(1) and the MSS (4).
5Close MSS sessionBetween the MSS (4) and the PAD (3).
6Close PAD sessionBetween the PAD (3) and the modem (2).
7Hang-UpBetween the modem (2) and the computer (1).

In the Sitatex software these steps can be viewed in the dialgateway where the screen shows a PC, a modem, the PAD and the MSS, all interconnected with coloured lines. In the following error messages and descriptions you will find a number of references to these steps.

Lost Carrier Detect
Cause: The modem is not functioning correctly or the line went down.
Occurs: From step 2 to step 7
Action: Ensure that the modem works correctly and the line is available

MODEM: Busy Signal detected
Cause: The PAD specified did not respond, it was busy.
Occurs: During step (2).
Action: Ensure that the phone prefix and the phone number of the X.28 PAD is correct.

MODEM: Invalid command
Cause: The script file for the modem has an error.
Occurs: During step (2) or step (7).
Action: Edit the script file for the modem and correct the error.

MODEM: No answer
Cause: The destination address specified did not answer.
Occurs: During step (2).
Action: Ensure that the phone number of the X.28 PAD is correct.

MODEM: No carrier detected
Cause: There is a problem on the telecommunications line, the CD signal did not go to High within 60 seconds of making the call.
Occurs: During step (2).
Action: Ensure that the line is functioning correctly.

MODEM: No dial tone detected
Cause: The line was down.
Occurs: During step (b).
Action: Ensure that the line is up.

MODEM: No Modem attached
Cause: The modem was not connected to the PC.
Occurs: During step (b).
Action: Ensure the modem is correctly connected to the PC.

MODEM: Script file corrupted
Cause: The command file for the modem is corrupt.
Occurs: During step (b) or step (h).
Action: To re-select the script file, in the Parameters dialog box, position the selection cursor on modem parameters, then select the modem type.

MSS: BCC error.
Cause: A block of data received with an incorrect cyclic check count, probably due to poor line quality.
Occurs: From step (d) to step (f).
Action: If the message occurs often, report the problem to your local telephone service engineer.

MSS: Duplicate frame data detected.
Cause: A block of data with a duplicate marker set was detected, probably due to poor line quality.
Occurs: During step (e).
Action: If the message occurs often, report the problem to your local telephone service engineer.

MSS: IMA lost
Cause: The timer for message IMA has elapsed, probably due to poor line quality.
Occurs: From step (d) to step (f).
Action: If the message occurs often, report the problem to your local telephone service engineer.

MSS: No traffic
Cause: No further traffic from the MSS was detected, probably due to poor line quality.
Occurs: From step (d) to step (f).
Action: If the message occurs often, report the problem to your local telephone service engineer.

MSS: Receive - CLOSE IMA failed
Cause: The timer for message acknowledgment timed out, probably due to poor line quality.
Occurs: During step (f).
Action: If the message occurs often, report the problem to your local telephone service engineer.

MSS: Receive - DATA IMA failed
Cause: The timer for message acknowledgment timed out, probably due to poor line quality.
Occurs: During step (e).
Action: If the message occurs often, report the problem to your local telephone service engineer.

MSS: Receive - OPEN IMA failed
Cause: The session password is incorrect or the quality of the telecommunications line is poor.
Occurs: During step (d).
Action: Ensure that the session password is correct. If the message occurs often, report the problem to your local telephone service engineer, who should investigate the quality of the telephone line.

PAD: CLR failed
Cause: Using a leased line, the X.28 PAD was unable to clear the circuit.
Occurs: During step (c).
Action: Call again or reset the modem.

PAD: Connection failed
Cause: The X.28 PAD was busy at the moment called, or the X.28 PAD phone number called was not correct.
Occurs: During step (c).
Action: Ensure that the phone number of the X.28 PAD is correct, and call again.

PAD: Error Input Data Lost
Cause: The X.28 PAD detected that input data was lost, probably because it was busy.
Occurs: From step (c) to step (g).
Action: None.

PAD: Error Message received
Cause: The X.28 PAD sent an error message.
Occurs: From step (c) to step (g).
Action: Call again. If the problem persists, contact your local Help Desk.

PAD: Incorrect DNA, NUI number, or NUI password
Cause: One or more of the DNA, NUI, or NUI password have not been set.
Occurs: During step (c).
Action: Ensure that the configuration of the Gateway is correct, in particular the DNA, NUI, and NUI password.

PAD: Overflow
Cause: The transmission queue at X.28 PAD is full.
Occurs: During step (c).
Action: Call again later. If the problem persists, contact your local Help Desk.

PAD: Set Language failed
Cause: The X.28 PAD was unable to set the language parameter.
Occurs: During step (c).
Action: Call again. If the problem persists, contact your local Help Desk.

PAD: Set Profile failed
Cause: The X.28 PAD was unable to set the profile parameter.
Occurs: During step (c).
Action: Call again. If the problem persists, contact your local Help Desk.

Resend BACKLOG - Serial Number: xxx
Cause: The Gateway has not received the backlog and requests it again.
Occurs: From step (d) to step (f).
Action: None.

Resend DATA - Serial Number: xxx
Cause:The Gateway has not received the acknowledgment of the data block and sends it again.
Occurs: During step (e).
Action:None.

Receive BACKLOG - Serial Number: xxx
Cause:The Gateway has received a backlog block.
Occurs: From step (d) to step (f).
Action:None.

Receive DATA - Serial Number: xxx
Cause:The Gateway has received a data block.
Occurs: During step (e).
Action:None.

Receive IMA/CLOSE - Serial Number: xxx
Cause:The Gateway has received a close acknowledgment block.
Occurs: During step (f).
Action:None.

Receive IMA/DATA - Serial Number: xxx
Cause:The Gateway has received a data acknowledge block.
Occurs: During step (e).
Action:None.

RS232: BuildCommDCB error
Cause:The Data Control Block was incorrect.
Occurs: During step (a).
Action:Call again.

RS232: Clear DTR failed
Cause:The clear Data Transmission Ready signal failed on the modem.
Occurs: During step (i).
Action:Ensure that the modem functions correctly.

RS232: Clear RTS failed
Cause:The clear Ready To Send signal failed on the modem.
Occurs: From step (i).
Action:Ensure that the modem functions correctly.

RS232: ClearCommBreak error
Cause:The clear break signal failed.
Occurs: From step (c) to step (g).
Action:Call again.

RS232: CTS timeout
Cause:The wait for CTS (Clear To Send) signal timed out on the modem.
Occurs: From step (a) to step (i).
Action:Ensure that the modem functions correctly.

RS232: Default parameters in error
Cause:The default parameters for this modem are set incorrectly.
Occurs: During step (a).
Action:Ensure that the default parameters are set correctly, then call again.

RS232: Device already open
Cause:The port is being used by another application.
Occurs: During step (a).
Action:Close the application that is using the port, then call again.

RS232: Device identifier invalid or not supported
Cause:The device identifier is incorrect or the device is not supported.
Occurs: During step (a).
Action:Ensure that the device identifier is correct, then call again.

RS232: Device not open
Cause:The device has not been opened yet.
Occurs: During step (a).
Action:Ensure that the device identifier is correct, then call again.

RS232: Device's baud rate unsupported
Cause:The baud rate for the device is not supported.
Occurs: During step (a).
Action:Set the device to a baud rate that is supported, then call again.

RS232: DSR timeout
Cause:The wait for DSR (Data Set Ready) signal timed out on the modem.
Occurs: From step (a) to step (i).
Action:Ensure that the modem functions correctly.

RS232: Function cannot allocate the queues
Cause: The path for the file COMQUEUE is corrupt or missing, or there is no space on the drive.
Occurs: During step (a).
Action: Ensure that the path for the file COMQUEUE is correct and that there is sufficient space on the drive.

RS232: Hardware detected a break condition
Cause:A break condition occurred.
Occurs:From step (a) to step (i).
Action:None.

RS232: Hardware detected a framing error
Cause:A framing error occurred.
Occurs:From step (a) to step (i).
Action:None.

RS232: Hardware detected a parity error
Cause: A parity error occurred, probably a cable or modem error.
Occurs: From step (a) to step (i).
Action: Ensure that the cable is OK, ensure that the modem functions correctly.

RS232: Hardware not available
Cause: The required hardware is locked or does not exist.
Occurs: During step (a).
Action: Ensure that the required hardware is installed and is not locked by another application.

RS232: Receiving queue overflowed
Cause: The receiving queue overflowed.
Occurs: From step (a) to step (i).
Action: None.

RS232: Requested mode not supported
Cause: The requested mode is not supported by the modem.
Occurs: ;During step (a).
Action: Ensure that the modem supports the required modes.

RS232: RLSD time-out
Cause: The RLSD (Receive Line Signal Detect) timeout failed on the modem.
Occurs: ;From step (a) to step (i).
Action: Ensure that the modem functions correctly.

RS232: Set DTR failed
Cause: The set Data Transmission Ready signal failed on the modem.
Occurs: During step (a).
Action: Ensure that the modem functions correctly.

RS232: Set RTS failed
Cause: The set Ready To Send signal failed on the modem.
Occurs: During step (a).
Action: Ensure that the modem functions correctly.

RS232: SetCommBreak error
Cause: The set break signal failed.
Occurs: From step (c) to step (g).
Action: Ensure that the modem functions correctly. If the problem persists, contact your local Help Desk.

RS232: Specified byte size invalid
Cause: The byte size specified for transmission blocks is not valid.
Occurs: During step (a).
Action: Set a correct block size.

RS232: SetCommState error
Cause: The set communications state command failed.
Occurs: From step (a) to step (i).
Action: Ensure that the modem functions correctly. If the problem persists, contact your local Help Desk.

RS232: Temporary overrun on serial port
Cause: The PC is unable to cope with the workload.
Occurs: From step (a) to step (i).
Action: 1) If there are other applications running, close some of them.
;2) Install SITATEX for Windows on a more powerful PC.

RS232: Timeout during an attempt to communicate
Cause: The PC is unable to cope with the workload.
Occurs: From step (a) to step (i).
Action: 1) If there are other applications running, close some of them otherwise install SITATEX for Windows on a more powerful PC.

Send BACKLOG - Serial Number: xxx
Cause: The Gateway sent a backlog data block.
Occurs: From step (d) to step (f).
Action: None.

Send CLOSE - Serial Number: xxx
Cause: The Gateway sent a close block.
Occurs: During step (f).
Action: None.

Send DATA - Serial Number: xxx
Cause: The Gateway sent a data block.
Occurs: During step (e).
Action: None.

Send IMA - Serial Number: xxx
Cause: The Gateway sent a data acknowledge block.
Occurs: From step (c) to step (g).
Action: None.

Send OPEN - Serial Number: xxx
Cause: The Gateway sent an open command.
Occurs: During step (d).
Action: None.

User hang up
Cause: The user selected Hang-up.
Occurs: From step (a) to step (i).
Action: None.


25 The gateway password has been changed and I do not know what it is.

If the password has just been changed, and has been forgotten, AND no subsequent modifications to the GW Setup utility have been done, this method may be the best chance to retrieve it from the backup. Of course, the old password must be known. Remove the GWSESS.CNF file - save it to a diskette - and rename the GWSESS.BAK to be the GWSESS.CNF file. This is the best and easiest way and will get you back up with everything intact.
There are no guarantees for the second method, but you can try the following (make a backup of the file first!!!):
- Open the GWSESS.CNF file with a good file editor.
- Go to offset (displacement) 492 (01EC), the number in parathesis is in hex.
- For the next 8 bytes, enter the series DB 3E B7 A7 2D 73 C5 07
This will allow you to get in to the GW Setup with PASSWORD.


When first installing the Sitatex for Windows software it asks you which version you want to install (X28, X25 or P1024C). The software comes in single-user and multi-user versions and one package contains the software for all three communications protocols. The protocol selection screen looks like this:

If you choose the X25 version there is an extra screen asking you which version of the gateway you want to install. The options are 16 and 32 bit.

The one you have to choose is dependant on the Eicon software you are going to use on this gateway.
Eicon has a DOS and a Windows version of their gateway software. If you use the Eicon DOS software you will have to use the 16-bit Sitatex gateway version, if you use the Eicon Windows software you can use the 32-bit Sitatex gateway.

Once the software is installed you can start the gateway and the workstation programs. The X28 gateway program looks like this:

Under the configurationbutton you can find/set all needed options:

This is what the user software looks like:

In the user program there are two ways of customizing it to your liking. the first is to go to the options (Tools, Options) which will present you with this screen:

The second is to use the assistant which is a program within the Sitatex program which you can use to automate tasks: