|
 |
|
a;lkfj;alk
Q.
I have many files, some large, that will not fit onto one floppy disk.
How can I save these files onto multiple floppies?
A.
Using the Compression, Tape Archive and Split utilities, you can accomplish
this task with the following procedure.
- Create a directory to contain the files and then copy the files into the
directory.
% mkdir copy_dir
% cd copy_dir
% cp /usr/home/vcs/random/data/large_file1 .
% cp /usr/home/vcs/random/data/large_file2 .
- Archive and compress the files.
% tar cvf - . | compress -v > out_file.tar.Z
- Split the compressed file into 1.1 megabyte files that each can be copied
onto a single floppy. The files are named 'xaa', 'xab', 'xac' and so on.
% split -b 1100k out_file.tar.Z
- To recover the original large files, copy the 'xaa' and other files into
the same directory. Combine them with the 'cat' command and then uncompress
and unarchive.
% cat xaa xab xac ... > new_out_file.tar.Z
% zcat new_out_file.tar.Z | tar xvvf -
Back to FAQs
Q.
In the year 2000, will my Sun computer show the date correctly?
(the 'Y2K' problem)
A.
Sun has a major effort underway to make their products 'Year 2000
Compliant'. You can view their results at the following web site.
http://www.sun.com/y2000/index.html.
Solaris 2.6 is 'Year 2000 Compliant' AND Solaris 2.6 is able to be overlayed
onto either Solaris 2.5 or Solaris 2.5.1 systems with a simple 'Upgrade' process.
This process does not delete or modify any of your existing test or data
files.
Spectral Dynamics recommends an upgrade to Solaris 2.6.
If you are running under Solaris 1.1, you will be unable to set the
proper year with the 'date' command. Therefore, before the millennium,
you should reset the date to 10 or 20 years earlier (1989 or 1979) and
then be aware of the incorrect year. To accomplish this new date setting,
before leaving for your millennium holiday, enter the following commands
in an Xterm window:
% su
# date 7912291645
Sat Dec 29, 16:45:00PM PDT 1979
Of course, an upgrade to Solaris 2.6 could save this headache.
Back to FAQs
Q.
How can I determine the CPU speed of my Sun computer?
A.
You can find your CPU speed by entering the following
command into an Xterm window at the '%' prompt.
Each of the lines that is returned will have a number preceding
the units 'MHz'. This number is the clock speed in MHz.
Back to FAQs
Q.
How much memory has my Sun computer?
A.
You can determine the amount of CPU memory by entering the
following command into an Xterm window at the '%' prompt.
The memory size is shown on a line that has the text "available mem =".
Usually this number is printer in kilobytes such as "24576K", which
means "24 megabytes".
Back to FAQs
Q.
I have a color printer and the default for the 'Print'
button is always the 'Monochrome' selection. Is there a way to
change the default selection to 'Color' so I can just click on
the 'Print' button to get my color plot?
A.
Yes, all pull down menus have a changeable default selection.
Just click the right (menu) mouse button on the desired screen
button. A drop-down menu appears with the default selection circled.
Now, move the mouse pointer to the selection that you wish to
be the new default and press the Control key and the left (select)
mouse button together. The drop-down menu disappears with the
new default selection. To verify that the new default selection
is in effect, click the right (menu) mouse button on the screen
button and notice that the drop-down menu now has the new default
selection circled.
Back to FAQs
Q.
At the login prompt, I cannot login and the message "Write
Failed, File System Full" is displayed. What should I do
now?
A.
Your hard disk space has become filled with
parameter and data files. You must delete some files to allow room for
temporary administrative login files to be created. To accomplish
this removal:
- Login to the account 'root'
- Use the File Manager to drag (remove) some parameter or data
files to the Wastebasket.
- OR -
- Use the UNIX command '# rm <file> to remove some parameter
or data files.
- For Solaris 1.1 systems, the parameter files are located in
the directory '/home/vcs/<application>/test' and the
data files are located in directory '/home/vcs/<application>/data'
- For Solaris 2.5 systems, the parameter files are located in
the directory '/usr/home/vcs/<application>/test' and the data
files are located in directory '/usr/home/vcs/<application>/data'
- Logout of the 'root' account by selecting Workspace -> Exit…
- Login to your 'vcs' account and remove more files, if necessary.
Back to FAQs
Q.
How can I change the colors on the graphs that are printed
to my color printer?
A.
With any graph showing on the screen, place the mouse
pointer inside the grid and press Control-Q from the keyboard
(press the "Control" key and the "Q" key
at the same time). A "Print Colors" window appears
that allows you to change the various colors on the graph. Notice
that under "Chose Color", you may select many areas
of the graph, such as Trace1, Trace2, …, Grid, Text, …,
and Abort. There is also a color box that shows the printed color
for the mix of Red, Green and Blue for each selection. A mix
of Red=0, Green=0 and Blue=0 is black, like the 'Text' selection.
A mix of Red=255, Green =255 and Blue=255 is white, which, of
course, will not print well on white paper but will show on blue
paper. Try moving the color sliders and watch the resulting mixture
change.
When you exit the "Print Colors" window, the color changes
are temporarily in effect until you release the application.
To make these changes permanent, press the Save Screen button
before releasing the application. Re-installing the application
will restore the original colors scheme.
Back to FAQs
Q.
In Solaris 1.x, the floppy drive was mounted as '/fd'.
In Solaris 2.5, the floppy drive is mounted as '/floppy/floppy0'.
Is there a way to shorten the description of the floppy drive?
A.
Yes, you can use an environmental variable as a substitute
for the floppy drive mount point. This variable can be of fewer
characters. With a floppy disk inserted into the drive, open an
Xterm window an enter the following commands. These commands
show the current method.
| % su |
|
| # volcheck |
(this command mounts the floppy disk) |
| # ls /floppy/floppy0 |
(this command gives a listing of all the files on the floppy) |
| # . . . . |
(other commands accessing the floppy using '/floppy/floppy0') |
| # eject |
(this command ejects the floppy disk from the drive) |
Now, we will use an environment variable to shorten the number of
characters.
| % su |
|
| # volcheck |
(this command mounts the floppy disk) |
| % setenv FD /floppy/floppy0 |
(this command creates an environmental variable 'FD' that can
be substituted for the text string '/floppy/floppy0') |
% ls $FD
(Note the '$' character! You must precede the environment variable
with this '$' character) |
(this command uses the environmental variable FD to show a
directory listing of the files on the floppy) |
| % . . . . |
(other commands accessing the floppy use the text string
'$FD') |
| % eject |
(this command ejects the floppy disk from the drive) |
Note that this change is not permanent but is temporary only in the current
Xterm window!
Now, by entering the 'setenv' command into the text file ./vcs/.xinitrc,
this change will be permanent for any Xterm window.
Back to FAQs
Q.
After I finish running a Windows application, such as Excel, and then
leave the WABI window, my floppy drive cannot be mounted from either the
File Manager or using the "volcheck" UNIX command.
A.
Unfortunately, WABI leaves the floppy drive unmountable until a
command is given that re-enables the floppy. In an Xterm window, enter
the following commands:
% su
# /opt/SUNWwabi/lib/vold.switch -enable
#
The floppy drive should now be enabled.
Back to FAQs
Q.
I know that Random allows interior slopes to the Reference
Breakpoint Table, but the exact method of entering the parameters
is confusing. Could you give some examples?
A.
The interior slope calculation protects you from the
laborious computations involved in finding the crossover frequency
between segments in the Reference Table.
- Example 1, suppose your reference test specification read:
"… a breakpoint at 100 Hz and 0.0125 g2/Hz, then sloping
at 3 dB/oct to 0.025 g2/Hz, then a breakpoint at 500 Hz and 0.025
g2/Hz…"
You would enter the following values into the Reference Table:
Frequency
|
Value
|
Slope
|
100
500
|
0.0125
0.025
0.025
|
3
|
then press the 'Apply' button. The program will calculate the
missing crossover frequency as 200.48 Hz. The parentheses indicate a
calculated value instead of an operator entered value.
Frequency
|
Value
|
Slope
|
100
(200.48)
500
|
0.0125
0.025
0.025
|
3
|
- Example 2, suppose your reference test specification read:
"… a breakpoint at 100 Hz and 0.0125 g2/Hz, then sloping
at 3 dB/oct to 200.48 Hz, then a breakpoint at 500 Hz and 0.025
g2/Hz…"
You would enter the following values into the Reference Table:
Frequency
|
Value
|
Slope
|
100
200.48
500
|
0.0125
0.025
|
3
|
then press the 'Apply' button. The program will calculate the
missing crossover
level as 0.02941 g2/Hz. The parentheses indicate a calculated
value instead of an operator entered value.
Frequency
|
Value
|
Slope
|
100
200.48
500
|
0.0125
(0.024941)
0.025
|
3
|
Back to FAQs
Q.
While running a test, the auxiliary spectrum stops updating and
remains stationary until I start another test. What is happening?
A.
The averaging mode for both the auxiliary channels and the
monitor spectrum is set to 'Linear'. When this setting is active,
the auxiliary channels are averaged until the DOF (Degrees of Freedom)
value is reached. At this time no further averaging occurs until a
new test. You may press the 'Reset' button to start another accumulation.
You may also change the DOF to restart the averaging. In any of these
cases, the averaging will stop when the DOF value is reached.
To cause the auxiliary channel display to keep averaging through the test,
select 'Exponential' as the Averaging Mode.
To cause the exponential averaging selection to be automatically active
when you run your next test, press the SAVE 'Screen' button.
Back to FAQs
Q.
"When I run either Resonance Dwell tests or Single Frequency Dwell tests,
there is no data trace on the grid."
A.
Usually, the display trace connects measured points that occur
during a sweep with a 'line' vector. However, during a dwell, there
is no sweep and, therefore, no other point with which to connect.
The dwell data value can be shown on the grid by selecting the
'Properties...' button. Inside the Display Properties window, change the
'Texture' selection from 'Line' to 'Bar'. A vertical bar between the
frequency axis and the data point will visually show the data.
Use the 'Bar' Texture for Data Review plots, also.
Remember to press 'SAVE Screen' to cause the selections to be remembered.
Back to FAQs
Q.
"I can't reach full test level. The message 'Maxium Drive Level Reached'
occurs at -3.45 dB and only 1.23 Vrms."
A.
This situation can happen when the sine tones are significantly larger than
the broadband random background.
You can modify the algorithm that sums the sine tones and the broadband
random with a selection in the Control Parameters window. The value
for 'Sine/Random RMS Ratio' is normally set to 6. Change to a value of 3
and determine if full level can be reached. If not, try a value of 1.5 or
less.
This value can be set as low as 0.1. However, be aware that the sine tones
may not be controlled to their respective reference levels with very low
values for the 'Sine/Random RMS Ratio'.
Back to FAQs
|
|
