Sitatex V4.x


1 How do I reset the password to default?

You can use the SETPWD or DEFPWD password for this. Running DEFPWD sets the password to default while running SETPWD allows you to set the password to something else. Note that this only changes the password in the local config file, NOT in the MSS.


2 I tried to reset the password but it still does not work

There are two versions of the DEFPWD/SETPWD program. The old versions of these programs do not work properly and should not be used. Looking at the date-time stamp can recognize them. The old version, which does not work properly, has a date-time stamp of 05-11-1993. If you encounter this version of these programs please delete them and replace them with the new version with a date-time stamp of 07-10-1995.


3 I can send messages but not receive them.

This can have two reasons. One is that the turnup procedure was not followed (see general questions). If the turnup was arranged you should check the Q_In directory to see if there is a file called CURINPUT. If so, rename this file and check if messages are now logged into the In/Out box. If everything is now back to normal there was a corrupted message in the CURINPUT file. After the rename of the file all is ok again. Note that any message in the file will be lost to Sitatex although you can l oad the file in a text editor or suchlike to view the messages.


4 When viewing a folder STX crashes or gives an error like ‘Attempt to read beyond end of file’.

This indicates a corrupted message file. Going to the DOS prompt and running the RF (Repair Folder) program can solve this. To do this you have to know the name of the folder file and then type:

RF <folderfile>

The output from the program will look something like this:

WARNING:
Repair flag not set, folder(s) will only be analyzed
Input folder: <folderfile.fdo>
Folder name: <folderfile.fdr>
Number of messages: 3
Processed messages: 0;*** Message all links broken (front, back & EOM): message #0
*** SUB character lost: message #0
Processed messages: 1, bad messages: 1;
Processed messages: 2, bad messages: 1;
Processed messages: 3, bad messages: 1;
>>> Message #3 unrecoverable
Diagnostic completed...
To fix problems use the flag '+R'

The last line indicates what 'flags' should be used, in this case +R. The command then should be:

RF +r <folderfile>.

After this the folder should be all readable again.


5 I tried running the RF program but it does not work.

Sometimes when you try to run RF it will display the following error: Can't rename FOLDERFILE.FDR to FOLDERFILE.FDO: 5 To overcome possible file loss the RF program first of all tries to rename a folderfile from a .FDR to a .FDO file. If such a file already exists it cannot rename it and aborts. In order to be able to run the RF program now you have to either delete the .FDO files or rename the folderfile into something different.


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

Create a folder on a shared drive on the LAN or a floppy disk. Then file the concerned message to that folder and you can read them on the other machine from the same folder.


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

This can be done from the DOS prompt or with the 'Copy folder' function under 'Manage folders'.


8 My Sitatex station gives a library error XXX. What is this?

Below is the official list of all the numerical error codes. Not all of them have a very good error description but a lot of them at least will get you started to wards finding a solution.

00 Critical type critical error.
If this error occurs, you have a big problem. Reboot the PC and if the problem still exist, report the problem to the support team.
01 Not enough memory
There is not enough memory is left on your PC when you start STX4 (370 Kb at least is necessary), remove some TSR’s and retry.
02 Slide creation: Invalid l/h dimensions.
Your STX.SWP file is probably garbled. Remove it and retry.
03 Not enough memory
Not enough memory is left on your PC when you start STX4 (370 Kb at least is necessary), remove some TSR and retry.
04 Invalid video configuration
Your video may not be supported by STX4. STX4 supports CGA/EGA/VGA (CGA not recommended.)
05 Slide not defined in file.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
06 Call to (re)allocation with size==0.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
07 Cannot open primary slide file.
Check to see if the STX.COL file exists. If it doesn't reinstall the product. If it does check it isn't locked by another process.
08 Invalid/garbled primary slide file.
Reboot, if the problem still exist, remove the STX.COL and reinstall the product.
09 Error in reading primary slide file.
The file is probably garbled, reboot, if the problem still exist, remove the STX.COL and reinstall the product.
10 Attempt to save an internal slide.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
11 Error in saving slide to file.
This problem occurswhen we can't write the slide in the swap file. Chkdsk your disk if you’re working path is on the local disk. If your working path is on the LAN, check the LAN access.
12 Window stack overflow.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
13 Place slide: Invalid x/y position.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
14 Attempt to load an internal slide.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
15 x/y zone position out of the slide.
The stx.swp file may have been garbled. Remove it; reboot the PC to avoid memory problems then retry. If the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
16 Box dimensions must be 3x3, at least.
The stx.ppt file may have been garbled. Remove it, reboot the PC and reinstall it.
17 Attempt to fill with pattern=0000.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
18 Invalid handler initialization.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
19 Too many EMS memory allocations.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
20 Attempt to activate same handler twice.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
21 Too many handlers declared.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
22 Error in timeout management.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
23 Error in task management.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
24 Undefined keycode in hot-key installation.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
25 Attempt to delete a handler inside itself.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
26 Attempt to use same hotkey twice.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
27 Error in lift initialization.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
28 Context stack overflow.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
29 Error in locate_mouse parameters.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
30 Error in mouse_limits parameters.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
31 Invalid field initialization string.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
32 Video adapter does not allow high density.
Check your video adapter.
33 Mouse button list initialization error.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
34 Error in context list parameters.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
35 All fields of the map are By-passed.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
36 Error in directory management.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
37 Error in memory (re) allocation/liberation.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
38 Cannot (re) open DiskLog file.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
39 Error in DiskLog file append.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
40 Error in DiskLog file access.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
41 Cannot (re) open DiskQueue file.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
42 Error in writing to DiskQueue.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
43 Error in reading from DiskQueue.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
44 Cannot (re) open DiskFIFO file.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
45 Error in writing to DiskFIFO.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
46 Error in reading from DiskFIFO.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
47 Error in memory queue parameters.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
48 Error in Record File management.
If this problem occur while using address book, it may be garbled. Reboot, and if necessary remove or rename your address book.
49 Error in LAN File management.
If this error occurs when managing your folder or history, the folder may be garbled. Run the following command on the folder and try again: RF +R foldername. This will repair your folder, save the old folder on foldername.FDO, and store the unrecoverable data in foldername.ASC.
Other possibility: When you try to rebuild a folder, your Sitatex hangs up with critical 49: 1.13 bug, run the rebuild from a directory you have writing rights in.
50 Error in EMULEX shared memory address setting.
Check no process is using the EMULEX memory range.
51 No EMULEX card found, or initialization not done.
StartUCP has not been run, or another process is using the EMULEX memory range. Use checkEMX to check this.
52 EMULEX card management error (Load/start/stop).
Check the EMULEX card with checkEMX, and then contact the support.
53 Error in downloading program to EMULEX.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
54 Attempt to activate EMS manager twice.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
55 EMS manager initialization not done.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
56 Unrecoverable error in EMS memory access.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
57 Error in EMS management.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
58 Multiple SPOOLER activation.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
59 File access error, during CRC control (open or read).
The file may have been manually modified, remove it and reinstall.
60 Multiple HYPERTEXT HELP activation.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
61 Error in HYPERTEXT HELP management.
Error in Hypertext help management; Check that your stx.hlp is in your working path and that you have the read/write rights for this file.
62 Reserved for future use
63 Cannot access slide swapping file in WRITE mode.
64 Error in slide swapping file generation.
You probably don't have enough room on your disk to create stx.swp file.
65 Error in LANQUEUE parameters.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
66 LANQUEUE overflow.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
67 Cannot open slide swapping file.
Check the rights access on stx.swp file.
68 Cannot read slide swapping file signature, or signature garbled.
Remove the stx.swp file and retry.
69 Error in reading slide swapping file.
Remove the stx.swp file and retry.
70 Reserved for future use.
71 Error in RAM BUFFER management.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
72 Invalid initialization.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
73 Reserved for future use.
74 Cannot open prompt file.
Check to see if the stx.ppt file exist in the program path, if it does, check the rights access. If the file exist and the right are OK, remove the file and reinstall.
75 Error in reading prompt file.
The stx.ppt may be garbled. Remove it and reinstall.
76 Invalid prompt file signature.
The stx.ppt may be garbled. Remove it and reinstall.
77 Line too long & edit buffer full.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
78 UCP error. Invalid LC name (less than 4 chars).
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
79 EMULEX card or UCP environment missing. EMULEX card or UCP environment missing
Have you run StartUCP before stx4? If yes, you miss the EMULEX card or it is switched on the wrong page.
80 UCP error. LC is already used. UCP error. Channel is already assigned
You probably try to run twice the same application, or you have another application running on your PC, which use the same channel.
81 UCP error. LC name does not exist. UCP error.
Channel name does not exist please check your configuration.
82 UCP error.
LC not started. Check it.
83 UCP error.
Invalid parameter. Check it.
84 UCP error.
RID/IA duplication. Check it.
85 Slide cannot be created before initcbl() is done.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
86 Slide heap overflow.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.
87 Slide created but not inside heap! Very strange.
Reboot the PC, if the problem still exist, report the problem to the support team. Don't forget to describe the situation when the problem occurs.


9 On my gateway I regularly see error- and result codes. What are they?

In the gateway under Traces/Errors you can find a list of the errors the gateway has encountered. They are in the format:
ERROR CODERCMISC INFO
5108path
The error codes are explained in the 'Sitatex 4 LAN installation and administration guide' but the return codes are not. They are:
Return CodeMeaning
1ER_NO_FILE : File not found
2ER_NO_PATH : Path not found
3ER_ACCESS : Bad access or path already assigned.
4ER_DISKFULL : Disk full
5ER_WRITEPROT : Media is write protected
6ER_NOT_READY : Drive not ready
7ER_EXIST : File already exist
8ER_BLOCKED : File still blocked after all the retry.
9ER_SEEK : Error on seek
0x100ER_OTHER : Prefix for the other DOS errors.
Logical disk access (Non-DOS errors):
0x400ER_SIGN : Bad file signature
0x401ER_READ : Error reading too much data
0x402ER_MATCH : Data not found in the file
0x403ER_UNZIP : Unzip problem
0x404ER_NORAM : No more memory
0x405ER_GARBLED : File garbled


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

Yes. First install the LAN version and use the USERCONF directory to make sure the Sitatex software uses the local drive for it's history file, address books, folder files etc. Then install the PSTN/X28 version on the same local drive and configure that.

Now you can start either STX from the local drive for the PSTN/X28 version or \STX4GW\STX from the LAN drive for the LAN version.

Note that with the V4 LAN version the gateway controls the session with the MSS, not the workstation so if you switch off the workstation the messages will still be delivered to the gateway and will not be queued in the MSS until PSTN/X28 version makes a session.

In order to make this work you have to run the CLOSE utility from the STX4LAN directory every time you stop using the LAN version and run the CLOSE utility again before you start using the LAN version again. This will ensure that the MSS sends or stores the messages whenever one of the two is needed.


11 My existing station can send but not receive messages.

This can be because of a corrupted message in the output queue. When you send a message a file named QUEMOUT gets created in the \STX4\Q_OUT directory of your PC. The gateway then will rename that file into CURMOUT and try to send the messages in the file. If for whatever reasons the message in the file is corrupted the rename takes place but nothing else happens. Therefore, if you see a CURMOUT and a QUEMOUT file while at the same no messages are being sent it is most likely this problem.

The only reason to solve it is to take out the CURMOUT file, which creates the problem. You can do this by renaming the file, moving it to another location or by deleting it.

The messages in that file are lost to Sitatex but you can try to load the file into a text editor, which at least enables you to read the messages.


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

Yes, all versions of Sitatex V4 will run ok under Windows 95/98. All versions using a persyst card will not work under Windows NT as this OS does not recognize a persyst card. Note that you might have to run NLTSR, which is a little TSR to allow Windows and STX to communicate together.

Also, when you want to be able to minimize Sitatex or run it in the background you have to go into the properties of the program and enable background processing.


13 I can hear messages coming in but do not see them in my in/out box

This is most probably due to the fact that you have a filter activated. You can see this in the top righthand corner of the screen.


14 When trying to rebuild a folder my STX hangs with critical error 49.

You do not have rights to write in the current directory. Either change the directory or get the needed access rights


15 When trying to print a message, it does not get printed until I exit Sitatex.

This is most probably due to the fact that you are trying to print to a LAN printer. You have to set the time-out for the print capturing. The way to do this is dependant on the type of LAN so consult your network manager for more information.


16 My mouse works under Windows but not in Sitatex.

This is due to the mouse driver in Windows. Try switching to another mouse driver.


17 Sitatex on a WIN95 station gives a 'Path not found' error when trying to send a message.

This due to an obscure way of non-cooperation between Novell and Windows95. You can solve it by upgrading to the latest version of Sitatex V4 which has been modified to overcome this but. The alternative is to switch the Novell LAN requester used in Windows 95.


18 When starting STX4 sync it immediately gives an error 2, in Get_in_queue

This is due to a bug in the SMARTDRV.EXE program from DOS 5.There is no solution to this but to change the DOS version.


19 I get an error 1025 in function Get_in_queue

This is due to a garbled message in the Q_IN directory. Once that is removed the problem should be solved.


20 I get an error 344 in function Get_in_queue

Often with this error you are using a LAN version and the access to the LAN has disappeared. When you log in again it should be solved.


21 I get an error 260 in function Get_in_queue, followed by DOS error 4

There can be two reasons for this, either the harddisk is full or there are lost cluster swhich can be solve dby running CHKDSK/F


22 I get an error 1029 from 'input history management' in function Get_in_queue.

The CURINPUT file is most probably garbled. The only way to solve this is by renaming/deleting the file and restarting. If the messages in the file have to be recovered please contact your local SX who can have that arranged.


In Sitatex V4 there are only a few different versions: Async Dialup, X28 dialup, Synchronous and LAN. The ASYNC dialup has been discontinued quite some time and you should not encounter that version anymore.

The main screen is almost the same for all versions, this is the one for the X28 dialup version:


And this is the screen for the Synchronous (P1024C) version:


Note that the DIAL button changes into COMMUNICATION. Please be aware that in the LAN version there is no button there.

If you choose the DIAL option you will get the following screen:

If you would have a synchronous station and you choose COMMUNICATION you would see this:

This screen will allow you to always check the status of the connection and, in case of a problem, show you were that problem is.