Guralp Systems Limited
MAN-SWA-0001 Issue M - Scream User's Guide
Section Index: 16.1 Command line options 16.2 The calvals.txt file 16.3 File and directory locations 16.4  Common issues

Chapter 16. Inside Scream!

16.1 Command line options

Options can be prefixed with either a hyphen - or a forward slash / in both Windows and Linux versions. The option names are case insensitive.

-view filespec [filespec…] : Launch in data viewer mode. The files or directories specified are scanned and displayed in a single WaveView window. Whilst Scream! is scanning the files, a small window displays the progress and estimated completion time.

A WaveView window in data viewer mode is identical to a real-time WaveView window, except that

Everything on the command line after -view is treated as a file specifier. If you need to issue other options, place them before -view.

-i:configuration-file : Use configuration-file instead of scream.ini to load Scream!'s settings.

-FlashLED : Flash the Scroll Lock keyboard LED each time a block is received.

-NoSplash : Do not display Scream!'s splash-screen at startup.

-V31 : Force network packets to be in Scream! 3.1 format. Since Scream! 4.n is backwards compatible with Scream! 3.1, you should not need to use this option.

-disknn:image-file : Treat the file image-file as a raw DFD disk, attached to port nn.

-noaspi : On Windows 98, 95 and ME, Scream! uses the Adaptec ASPI drivers provided with the operating system to control SCSI devices. On other operating systems, the ASPI drivers are not available, so Scream! controls the devices directly. Use this switch to force Scream! to control devices directly even if the ASPI drivers are present.

16.2 The calvals.txt file

If a file named calvals.txt exists in the same directory as Scream!'s executable (scream.exe), Scream! will look there for suitable calibration values.

Caution: If you do not have write permission on the directory where the executable is located (which is normal), Windows may silently redirect any file access to the virtual store instead. Please see the Microsoft documentation for information about the virtual store.

Note: If an alternative location has been specified for calvals.txt by use of a parametersfile=path declaration in the [CUSTOM] section of scream.ini and a file exists in that location, Scream! will use that file and not look further. If no such declaration exists, Scream! will look in the current working directory for a file named calvals.txt. If it finds one, it will use that in preference to the one in the same directory as Scream!'s executable. Neither of these techniques are recommended because none of the supplied MATLAB® extension scripts will look anywhere other than in the standard location.

Each stream has its own section in the file, identified by its System ID and Serial Number (as described in section 5.3.1) in the format


Scream! and its extension scripts check to see if the streams being received match any of the instruments in the file. If they do, the software will apply the correct values for your sensor automatically.

You can edit the section of the calvals.txt file appropriate to any particular digitiser within Scream! by either:

The second method is the only method possible when in View mode.

The format of each section is given in section 5.7.

16.3 File and directory locations

16.3.1  Windows version

Scream! creates or uses the following files and directories

16.3.2  Linux version

The default installation directory - scream-directory - for the Linux version of Scream is /usr/lib/scream-4.6. The following files and directories are used:

16.4  Common issues

A number of configuration or operational issues can produce error messages. The most common are described below.

Unable to detect configuration

Scream! has not been able to retrieve the current configuration from a digitiser. This can happen because

It is recommended that you wait for data to be received from the digitiser before you attempt to configure it.

Unable to save program status

The Scream.ini file could not be opened for writing. This can happen because

Another application (possibly another instance of Scream) is using the setup file “<filename>”

An instance of Scream! is already running on your system, and is using the referenced ini file for it's configuration. You cannot run two instances of Scream! using the same configuration file. You should either return to the running instance, or if you intended to start a second instance of Scream, you need to specify a different configuration file. See the -i option in section 16.1.