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
The data is not held in memory. When you change the displayed time range by zooming in or out, panning, or resizing the window, Scream! re-reads the data for the new time range.
The advantage of this approach is that you can view files in data viewer mode which are larger than the amount of memory available. Real-time Scream can only draw blocks which are kept in its memory buffer (see Section 4.4, page 47.)
You cannot return to the main window by clicking on the stream identifier in the context menu.
You cannot drag streams from one WaveView window in data viewer mode to another one, or to a real-time Scream! application.
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 is backwards compatible with Scream! 3.1, you should not need to use this option.
-nettx : Display a Transmit Data from Network check box in the My Server pane of the Network Control window. When checked, packets received by Scream! over the network will be forwarded on to network clients together with any local data, if they are not already in Scream!'s stream buffer. Warning: there is no way a client can tell if a copy of Scream! is forwarding network packets—instruments will incorrectly appear under the server's serial port icons. You will not be able to configure these instruments, or access their consoles.
-disknn:image-file : Treat the file image-file as a raw SAM/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.
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.
Each stream has its own section in the file, headed by the line [instrument-id]. The instrument-id is the string which identifies the digitizer in the left-hand pane, e.g. GURALP-DEMO. It is formed of up to 6 characters (the system identifier) followed by a dash, then up to 4 characters (the serial number.) 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 computer will apply the correct values for your sensor automatically.
You can edit sections of the calvals.txt file within Scream! by right-clicking on a digitizer icon and selecting Calvals....
The format of each section is given in Section 3.8, page 22.
Scream! creates or uses the following files and directories
scream-directory\scream.exe : The program itself.
windows-directory\scream.ini (e.g. C:\WINDOWS\scream.ini) : The configuration file for Scream!. To restore the application to its factory settings, close down all running copies of Scream! and delete this file.
system-directory\qtintf70.dll (e.g. C:\WINDOWS\SYSTEM32\qtintf70.dll) : The Qt shared library which Scream! requires to run.
scream-directory\calvals.txt : The sensor and digitizer calibration information file.
scream-directory\autoload\ : The directory to take auto-load GCF files from (see Section 9.4, page 113.)
scream-directory\data\ : The default directory for recording data (you can change this: see Chapter 9, page 97.)
scream-directory\html\ : The default directory for Scream!'s online help.
settings-directory\Temp\ : (e.g. C:\Documents and Settings\Administrator\Local Settings\Temp\) : The default directory for log files. You can change this: see Chapter 11, page 121.
scream-directory/scream : The program itself.
scream-directory/scream.ini : The configuration file for Scream!. To restore the application to its factory settings, close down all running copies of Scream! and delete this file.
library-directory/libborqt-6.9.0-qt2.3.so : The Qt shared library which Scream! requires to run.
scream-directory/calvals.txt : The sensor and digitizer calibration information file.
scream-directory/autoload/ : The directory to take auto-load GCF files from: see Section 9.4, page 113.
scream-directory/data/ : The default directory for recording data (you can change this: see Chapter 9, page 97.
scream-directory/html/ : The default directory for Scream!'s online help.
scream-directory/ : The default directory for log files. You can change this: see Chapter 11, page 121.
Unable to detect configuration
Scream! has not been able to retrieve the current configuration from a digitizer. This can happen because
The device is not connected.
The communications link is one-way (simplex). Scream! needs reliable two-way communications to discover the digitizer's setup. However, you can still receive data over a simplex link.
The device is heavily loaded, and Scream! times out waiting for a response from it.
The network between Scream! and the computer hosting the device is slow or unreachable. You can check this using the standard command ping ip-address to check that the remote computer is responding.
If your computer is on the same network as the remote device, it must be on the same subnet as that device, or it will need to connect through a gateway machine.
It is recommended that you wait for data to be received from the digitizer 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
The file or disk are write-protected.
You do not have the right privileges to change the file.
The file is in use by another program.
Unable to write to stream
An error occurred when Scream! tried to write a data block to the disk. This can happen because
The disk is full.
The disk or directory is write-protected.
Another program is using the same file, or you are replaying it in Scream!.
You have used an ambiguous Filename format, which means two streams share a filename.
When this error occurs, Scream! disables recording for that stream. To resume recording, first remove the cause of the error, then enable recording again.
If you have Auto Record-Enable for data streams selected, and you replay a recorded file, Scream! will suppress this error message.