ok, clarification:
probe-scsi
probe-scsi-all
probe-ide
will show you ALL HW attached;
if you can not see it there, you NEVER will see it under OS.
Therefore, if the result at boot-prompt is not as desired,
forget boot -r, it won't find the device.
So, first check probe-xxxxx
if it is not there...
Close, but do not be fooled by the "9954":
'ST118273FSUN18G' says it is a 18GB Seagate
:-)
If You use Solaris 8 (newer than 10/01) you can
do the following without reboot:
devfsadm -C
to throw out all your not used drivers and then try
devfsadm [Options]
to re-attach all drivers for...
Thank You bryanbayfield !
Using Vars is definitely theright way to go.
But, alas, about the "ThisWorkbook"-thingy:
We did tests for whatever I wrote before I wrote it.
I did testing again, and the result is still the same:
You can use
Application.Workbooks.....
Workbooks.....
or just...
well, more testing, all said above again verified:
Application.ActiveWorkbook
Application.ThisWorkbook
Applicatio.Workbooks....
etc. all change around while switching between XLA and XLS.
Workaround:
Dim AWB as Workbook 'ActiveWorkbook = Data
Dim TWB as Workbook 'ThisWorkbook = Reference...
Thank You! fast response.
Your line of thought was exactly what we tried: ActiveWorkbook, ThisWorkbook and such, but:
VB-Help, Index, "project" select one of the first lines which read something like "add-in ....." and there it is: "you can not reference other workbooks...
question about navigating workbooks / add-ins:
we have a couple of subs distributing a 6000-line list (input-sheet) from one worksheet onto about 30 new sheets (output-sheets), which will be created in this process according to another worksheet (reference-sheet). The input-sheet and the newly...
well, thinking about it, mirroring all and then a slice of the same disk could be defined as "overlap"
why it does not show up in your first post?
Either mirror the whole disk ( :-(
or mirror each slice as usual, and skip "backup" (s2)
see whether that works
matt
PATH variable is set to ?
echo $PATH
PATH=/sbin:/usr/bin:/usr/sbin:/usr/openwin/bin .....
besides MANPATH, PS1, LD_LIBRARY_PATH
export PATH and so on
seems .profile or .login Files are missing
matt
Rough example:
a-phys[root]$ more /.profile
#
# @(#)local.profile 1.3 93/03/24 SMI
#
stty...
seems time for a faq / how-to
I volunteer, but I can not promise immediate delivery
:-)
if you lay out the FS like described above, the rest can be done without re-installing the system, I think;
for SDS always keep 20-30 MB on slice 7 free
for Veritas keep two slices (6&7) free and 50 MB or...
post the output :-)
ssd, instance #14
System software properties:
name <sd_retry_on_reservation_conflict> length <4>
value <0x00000000>.
Driver properties:
name <pm-components> length <30>
value 'NAME=spindle-motor' + '0=off' + '1=on'
name <pm-hardware-state>...
hmmm, next thing would be to check typing and such;
I had the problem that a newly installed machine always needed assitance, while a already installed machine did everything automatically; as far as I recall I had a typo or a line missing .... and no empty lines or "tab" in places...
well, I would say, you definitely do not want a disk to be set up this way :-(
there are many "philisophies" how to do it right, so asking three people, you will get four opinions; nevertheless a few comments from my side:
a 37 GB disk gives you plenty of space
Part 0 root (starting at...
who told you this?
format
select disk
p
p
q
q
or
format
select disk
verify
quit
all those things you can do; just avoid to type label!!
and that is exactly the point, this "labeling"
matt
julianbarnett: yup, perfectly agree with you; that's why the result of "format - verify" would have been useful and might be, still.
Still wondering it is working now, because the solution he described does not fit the problem; really would like to understand this.
Using the wrong...
maybe this makes you happy again:
take a 100+ MB zip file and unzip it on your PC and on the SUN; assuming you have Sol8 installed you should get convincing results :-)
as comtec17 said: Sun is good as server, I/O, DB ...
PC is good as a GUI.
matt
hmmm, but not correct order of commands does not result in that error; making both disks look identical
probably resulted in both disks being "unlabeled";
SDS might be happy now, but might cause some problems later.
Could it be the disk has been used by Veritas VM?
The order...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.