User Tip of the Week

"What happens to a lawyer who jumps out of a plane at 35,000 feet with no parachute ?

Who cares ?"

-anonymous death row inmate

Frequently Asked Questions

  1. My file naming convention on the current survey is to use the sailline number as the last part of each files name. This reduces typing a bit, but I sometimes have to type the sailline as many as 3 times in one control file. Is there a way around all this typing?

    Answer: Yes, build and use control file templates. The on line help refers to these as smart control files. You can find this help under General and then Building Control files. There are also 3 examples of templates under FTP at this web site.

  2. I do not like the default answers for the 2D Displays parameter window. Is there any way to change the defaults for these parameters ?

    Answer: Yes, in the gqcdefaults file (the section starting with *DISPLAY2), there are keywords for each of the default answers in the parameter window. The keywords match the questions in the parameter window, but if there is a particular question for which you cannot find the keyword send us an email or call and we will look it up.

  3. I’m on a ship and the sea sometimes gets rough. It is sometimes hard to keep the mouse inside a log view window, and it is even harder to keep it in the scrollbar. I sometimes have to bring up the log view window 5 times before I can get to the part of the log I need to read. What can I do?

    Answer: Set the gqcdefaults parameter GOAWAY (under *EXTRA_UNIX) to 0 (zero). Doing this will cause the log view windows to stay up until you press the Close button or close it with the window manager.

  4. I built a control file with 2 KILL processors in it. No matter what ranges I select, the job either dies because all traces were killed or it completes with only the ranges in the second KILL. Is this a bug or what?

    Answer: It is just due to the way the user interface saves the KILL ranges. Unless the ranges for each of the KILL processors in a control file are saved to a different ASCII file, then only one range is used. The defaults response to saving KILL ranges is to save them to an ASCII file named after the control file with an "_kil" at the end and placed in the prospect scratch directory. The way to avoid this default action is to first toggle the button for "Select Ranges for Action in Spreadsheet" to "From ASCII file". Then click on Select KILL RANGES file to use", and enter a new file name or at least a name which is different from any other KILL processors in your control file. It is not mandatory, but it is recommended that you stick with the _kil at the end of any KILL RANGES file name. Another thing to remember is that in the other processes Mute, TAR Scaling, NMO, etc where a spreadsheet is used for entering ranges or a function, the user interface default action for saving the spreadsheet is the same and the same technique for avoiding problems will work.

  5. I recently upgraded AIX to 4.2, and now I cannot see the text strips in pop-up windows and I cannot see the trace header keywords in the trace header selection window. What can I do?

    Answer: You will need to change your .Xdefaults file. After making these changes, you will need to exit your Common Desktop session and log back in before the changes will take effect. Add a font definition for each of the 3 dialog types as follows;

    TQC*TQCdialog.Label.font: 5x8

    TQC*TQCTdialog.Label.font: 5x8

    TQC*TQCMdialog.Label.font: 5x8

    Add a shadowWidth and decrease the current shadowWidth in several places as follows;

    TQC*TQCFlabel.shadowWidth: 1

    TQC*TQCFbutton.shadowWidth: 1

    TQC*Command*shadowWidth: 3

    TQC*Label*shadowWidth: 1

    TQC*TQCMbutton.shadowWidth: 2

    TQC*TQCscroll.shadowWidth: 1

    Change the 3 places with font definitions of 9x15 as follows;

    TQC*TQCFXlabel.font: 6x13

    TQC*LargeFixedFont: 6x13

    TQC*TQCMlabel.font: 6x13

  6. Is Seisnav Resolve™ Year 2000 compliant ?

    Answer: Yes.

On-Line Documentation

The Seisnav Resolve™ manual is written in Microsoft Word. Use following links to download the Word documents by chapter. If you do not own Microsoft Word, you can download a free viewer at:

Chapter 1 - Installation and Package Configuration

Chapter 2 - General Help

Chapter 3 - Prospects

Chapter 4 - Input

Chapter 5 - Processes

Chapter 6 - Displays

Chapter 7 - Workshops

Chapter 8 - UNIX Commands

Chapter 9 - TAPE Commands

Chapter 10 - Utilities