Solaris 8 can't open root

Solaris 8
It gets as far as reading the hostname on boot and then spits out /dev/dsk/c0d0s1: no such device or address (this is swap). Then it trieds to check / but complains it can't open it (/dev/rdsk/c0d0s0). It wants me to repair it manually. I try to do that, but then it says it can't open /dev/rdsk/c0d0s0 All my data appears to be intact, it's just mounted as readonly. This is the second time I've had an issue like this. Last time I gave up and reformatted. I'm really not interested in doing that this time. I tried booting off the CDROM, but it paniced and rebooted. Ugh, any any any advice is appreciated.
mailto:[email protected]

Are the device links there: /dev/rdsk/c0d0*, /dev/dsk/c0d0*
(should be symbolic links pointing to something like
../../devices/... ?
Are the real device nodes there under /devices? Something like
/devices/pci@0,0/pci-ide@4,1/ide@0/cmdk* (your exact device names
my be different)
If you run "format", does it list your harddisc in the initial
disc menu? (Press CTRL-D to leave format without selecting a disc)
If the /devices device nodes and the /dev symlinks are present,
what error do you get when you open a harddisc device, using
"dd if=/dev/rdsk/c0d0p0 of=/dev/null count=1"
If the device nodes / dev links are missing, you may be able to
restore them by:
<pre>
mount -o remount,rw / (mount the root filesystem "read/write")
drvconfig (probe for hardware, build /devices tree)
disks (install symbolic links under /dev)
</pre>

Similar Messages

Solaris 10 x86 SunUpdateManager errors: Can't open default CCR

I have a V20z running Solaris 10 (6/06 I believe) which has been registered successfully
with the Sun Update Connection and it has, until recently, been getting and applying
patches successfully.
After the last set of patches was applied (involving a reboot), the machine has taken to
generating an error message which confuses me .
The machine is continually saying:
CNS Transport[3135]: Can't open default CCR. Be sure you are running as root.
CNS Transport[3135]: Could not send message from queue: /var/tmp/cc-transport/CCTQueueStore/store/queues/REGISTRATION/registration
Could someone please tell me what on earth could have gone wrong for this to start
happening?
David Wiseman/David Martin
UWO Computer Science

The transport is used for the optional web feature of the SunUC software. The errors you are getting could suggest a number of problems from a failure to connect to a malformed entry in the queuestore.
In the first instance i'd verify that the transport can connect -
# /usr/lib/cc-cfw/platform/transport/bin/cctrunner -p
Then review the error logs (if they exist) -
* /var/log/swupas/swupas.log
* /var/log/swupas/swupas.error.log
And if they show no problem i'd clear the existing queuestore to ensure there are no problems -
# /etc/init.d/cctransport stop
# rm -rf /var/tmp/cc-transport/*
# /etc/init.d/cctransport start
And then re-test the cctransport process can connect ok -
# /usr/lib/cc-cfw/platform/transport/bin/cctrunner -p

Unable to open templates from server input form folder and server root folder from some system while the same can be open from others system

Hi,
I am unable to open input scheduled from server root folder and also from input form folder on some system while they can be open from others system.
Please advice.
Thanks in advance

Hi Hengye,
While opening , it dont give any error. When I try to open it , it takes some time to load then nothing happen.However I can open it on other system but not on mine my collegue and user system.
Please advice.
Thanks.

"Can't open boot device" mesage when installing Solaris 10 by cdrom

I am getting the following error message when I try to install Solaris 10 from cdrom:
"Can't open boot device."
The system I am trying to install to is a SunFire v100.
The boot command I am using is:
ok boot cdrom - nowin
I have used this cd to successfully install several other v100s without any trouble. I have tried another cd and get the same behavior. I have also tried installing another v100 and get the same error.
Any help on this would be greatly appreciated.

Please check the "cdrom" alias.
-g.

Error : "Can't open boot_archive"

Hello, I am having an issue with a SUN FIRE V240 (SOLARIS 10).
The server doesn't boot, normally , first we had a file system error (bellow) and now we have an other error message "Can't open boot_archive"
====================+FIRST ERROR MESSAGES+===================================================
Unable to repair the / filesystem. Run fsck manually
(fsck -F ufs /dev/md/rdsk/d400).
====================================================================================
1) i tried to repair manually the disc with "fsck -F ufs /dev/md/rdsk/d400" , but I wasn't able to run fsck
2) I decided to boot the server with the solaris dvd
"boot cdrom -s" to try to repair the mirror "fsck -F ufs /dev/rdsk/c0t0d0s0" but I couldn't.
3) So I have decided to restore the root from the most recent backup tape that I have
4)I have mounted the root and all the other partitions from /a/etc/vfstab & /a/etc/system"
5) I have tried to update the boot archive but it didn't work and I had this error message *"not a boot archive based Solaris instance"*
6) Then I have reboot the server and since I see this two errors *"Can't open boot_archive" et "The file just loaded does not appear to be executable"*
=================the error that I see everytime the server boot===============================================
*"Can't open boot_archive" et "The file just loaded does not appear to be executable"*
I would appreciate any help

Have you tried to boot the system from OBP with the following command: boot -F failsafe

Lucreate error on Solaris 10 10/09 root ZFS

Hi guys,
I got some errors while trying out live upgrade on Solaris 10 10/09 root ZFS x86 environment.
I do intent to do this in the SPARC environment but not comfortable with the experience so far.
First of all, I have a separate zpool dataset - "rpool/opt".
Not sure if this is causing the error below.
Anyone can help to advice? TIA
bash-3.00# lucreate -c zfsBE -n new-zfsBE
Checking GRUB menu...
Analyzing system configuration.
No name for current boot environment.
Current boot environment is named <zfsBE>.
Creating initial configuration for primary boot environment <zfsBE>.
The device </dev/dsk/c1t0d0s0> is not a root device for any boot environment; cannot get BE ID.
PBE configuration successful: PBE name <zfsBE> PBE Boot Device </dev/dsk/c1t0d0s0>.
Comparing source boot environment <zfsBE> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <new-zfsBE>.
Source boot environment is <zfsBE>.
Creating boot environment <new-zfsBE>.
Cloning file systems from boot environment <zfsBE> to create boot environment <new-zfsBE>.
Creating snapshot for <rpool/ROOT/s10x_u8wos_08a> on <rpool/ROOT/s10x_u8wos_08a@new-zfsBE>.
Creating clone for <rpool/ROOT/s10x_u8wos_08a@new-zfsBE> on <rpool/ROOT/new-zfsBE>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/new-zfsBE>.
ERROR: cannot open ' ': dataset does not exist
ERROR: cannot mount mount point </.alt.tmp.b-UB.mnt/opt> device < >
ERROR: failed to mount file system < > on </.alt.tmp.b-UB.mnt/opt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to mount ABE <new-zfsBE>
ERROR: Unable to clone the existing file systems from boot environment <zfsBE> to create boot environment <new-zfsBE>.
ERROR: Cannot make file systems for boot environment <new-zfsBE>.
bash-3.00#
bash-3.00# df -h
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10x_u8wos_08a
 9.8G 3.2G 5.0G 40% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 613M 384K 613M 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap1.so.1
 8.1G 3.2G 5.0G 40% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
swap 613M 40K 613M 1% /tmp
swap 613M 32K 613M 1% /var/run
rpool/opt 3.0G 409M 2.6G 14% /opt
rpool 9.8G 34K 5.0G 1% /rpool
/hgfs 16G 4.0M 16G 1% /hgfs
rpool/ROOT/new-zfsBE 9.8G 3.2G 5.0G 40% /.alt.tmp.b-UB.mnt
bash-3.00#
bash-3.00# ludelete new-zfsBE
WARNING: Boot environment <new-zfsBE> has one or more file systems mounted at </.alt.tmp.b-UB.mnt>.
Checking if last BE on any disk...
cat: cannot open /tmp/.lulib.luclb.dsk.1801.new-zfsBE
BE <new-zfsBE> is not the last BE on any disk.
No entry for BE <new-zfsBE> in GRUB menu
ERROR: Unable to unmount file systems for boot environment <new-zfsBE>.
Unable to delete boot environment.
bash-3.00#

I had the exact same problem.
I found that by simply renaming rpool/opt to rpool/ROOT/s10x_u6wos_07b/opt seemed to fix this problem:
$ umount -f /opt
$ zfs rename rpool/opt rpool/ROOT/s10x_u6wos_07b/opt
$ zfs set canmount=noauto rpool/ROOT/s10x_u6wos_07b/opt
$ zfs mount rpool/ROOT/s10x_u6wos_07b/opt
$ lucreate -n test
Analyzing system configuration.
Comparing source boot environment <s10x_u6wos_07b> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <test>.
Source boot environment is <s10x_u6wos_07b>.
Creating boot environment <test>.
Cloning file systems from boot environment <s10x_u6wos_07b> to create boot environment <test>.
Creating snapshot for <rpool/ROOT/s10x_u6wos_07b> on <rpool/ROOT/s10x_u6wos_07b@test>.
Creating clone for <rpool/ROOT/s10x_u6wos_07b@test> on <rpool/ROOT/test>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/test>.
Creating snapshot for <rpool/ROOT/s10x_u6wos_07b/opt> on <rpool/ROOT/s10x_u6wos_07b/opt@test>.
Creating clone for <rpool/ROOT/s10x_u6wos_07b/opt@test> on <rpool/ROOT/test/opt>.
Setting canmount=noauto for </opt> in zone <global> on <rpool/ROOT/test/opt>.
Creating snapshot for <rpool/ROOT/s10x_u6wos_07b/var> on <rpool/ROOT/s10x_u6wos_07b/var@test>.
Creating clone for <rpool/ROOT/s10x_u6wos_07b/var@test> on <rpool/ROOT/test/var>.
Setting canmount=noauto for </var> in zone <global> on <rpool/ROOT/test/var>.
WARNING: split filesystem </> file system type <zfs> cannot inherit
mount point options <-> from parent filesystem </> file
type <-> because the two file systems have different types.
Population of boot environment <test> successful.
Creation of boot environment <test> successful.Don't know what the downstream implications of doing this will be, but it seems to work.

Can't open display

hi.
I can't open xwindows with another user than root, under my solaris 10 x86.
I checked the config, tried lots of things (set a display for my user, put /usr/openwin/bin in PATH,etc), but still the same:
Xlib: connection to localhost: 0.0 refused by server
Xlib: no protocol specified
Error: can't open display
Please help me :)

That s ok I found.
You just need to do as follows:
root@localhost: xhost + localhost
root@localhost: su - myUser
myUser@localhost: export DISPLAY=localhost:0
myUser@localhost: xclock &
:)

Cluster fails: Can't open /etc/cluster/nodeid

Error:
NOTICE: Can't open /etc/cluster/nodeid
NOTICE: BOOTING IN NON CLUSTER MODEWe've already tried the workaround
the following workaround should be done before rebooting the cluster
node after scinstall.
Add "etc/cluster/nodeid" to "/boot/solaris/filelist.ramdisk"
# bootadm update-archive
#rebootExcept the problem being that we don't even have a /boot partition/folder in root.
/etc/cluster/nodeid doesn't even exist
Everything was working fine then we rebooted today because one system froze and now this is what happens.

The workaround only applied to x86 machines - as far as I remember. You have probably got a different problem. I would check to see what services are not starting. Use:
# svcs -x
You'll probably find the root cause of the problem that way. Also check /var/adm/messages
Regards,
Tim
---

Error can't open display after reboot

Hi,
I encounter this problem :
I just install SSGD 4.2 on Solaris 10 01/06 T2000 server. After installation I can connect to the SSGD using browser from my notebook, and can try the various demo (dtterm, xclock etc)
I reboot the Solaris 10 OS.
After reboot I tried to login again via browser in my notebook and try to run the various demo.
I can login, but almost all the demo failed to execute, the X applications give error "can't open display:" with no hostname following the error.
The only demo still runs is the vt420 demo
Anybody can help me to point out what causes the problem ? I am trying to demo this SSGD software to a customer.
Regards
Adrianus B. Kurnadi

I've noticed this as well, under Solaris 10 FCS, Solaris 10 U1, and Solaris Express nv_39.
However, I have tried it out under S8 02/04, and S9 09/04 and I do not have this problem after rebooting the host at all.
For the hell of it, I (rather badly) converted the S89/S90 startup scripts to be SMF manifests with S90Tarantella having a dependancy on tS89TarantellaWebServer as I thought perhaps there was a strange issue with the tta process starting before the web service had fully started (beats me why it would matter, ends up it didn't) - as my test S10 host is a slow Netra T1.
I'd be interested to know what the difference is between it being started up via an rc2.d script and the root user logging into the system console running /opt/tarantella/bin/tarantella start. I haven't even bothered starting to try to observe the environment differences between startup via SMF in S10 and init.d in S8.
</2.2c>
Andrew

Improper message coming on console " ftpd[16809]: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_unix_session.so.1"

Hi All,
I am using solaris 10u10 on Sun Fire platform. I am getting below message on cosole.
ftpd[16809]: [ID 776383 auth.error] open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
ftpd[16809]: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_unix_session.so.1
ftpd[16810]: [ID 776383 auth.error] open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
ftpd[16810]: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_unix_session.so.1
ftpd[16815]: [ID 776383 auth.error] open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
ftpd[16815]: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_unix_session.so.1
ftpd[16816]: [ID 776383 auth.error] open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
ftpd[16816]: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_unix_session.so.1
ftpd[16817]: [ID 776383 auth.error] open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
ftpd[16817]: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_unix_session.so.1
Also the file is present on the server
root@atrcx1454/var/adm> ls -lrt /usr/lib/security/pam_unix_session.so.1
-rwxr-xr-x 1 root bin 20652 Mar 19 2008 /usr/lib/security/pam_unix_session.so.1
Can anyone help why above message is coming on console

Is the ftp daemon that you use provided by the Solaris media ? If this is not the case, then would recommend to contact the software maintainer for more help.
And regarding chroot, please check this URL to know what it is : Sandbox (computer security) - Wikipedia, the free encyclopedia
Depending how this environment is configured, the library is maybe not present in this one.

"can't open - no hsfs VTOC"??!

I have downloaded the three solaris 8 CD images from sun.com and duplicate them into 3 blank CDRs.
I also created the Solaris 8 Device Configuration Assistant into my blank diskette using dd.
When I boot from the diskette to install solaris 8, I encountered the following error when I choose CD at the Boot Solaris Screen,
Unable to mount a Solaris root file system from the device:
CD:(*)Target 0, NEC CD-ROM DRIVE:28C 3.02
on Bus Mastering IDE controller on Board PCI bus 0, at Dev 7, Func 1
Error message from mount:
/pci@0,0/pci-ide@7,1/ide@1/sd@0,0:a: can't open - no hsfs VTOC
Press Enter to Continue.
1) Why can't the system mount the CD-ROM drive?
2) What does "hsfs VTOC" mean?
3) I have put the Solaris install CD into the cd-rom drive, so why the system cannot read from that cd image?
4) The installation image we download from sun.com, is it bootable by itself? I try not to use the Solaris 8 Device Configuration Assistant bootdisk, but the system refuse to boot from the installation CD. I had already set the BIOS to boot from CD.
5) How can I resolve the problem?
Thanks and Regards.

I have downloaded the three solaris 8 CD images from
sun.com and duplicate them into 3 blank CDRs.Did you unzip the images before burning them to CDR?
Did you follow the instructions on the solaris download page?
http://www.sun.com/software/solaris/binaries/download.html
Error message from mount:
/pci@0,0/pci-ide@7,1/ide@1/sd@0,0:a: can't open - no
hsfs VTOC
1) Why can't the system mount the CD-ROM drive?Because the solaris boot system does not recognize the
format of the CDROM. It's mounted as a filesystem type
"hsfs" (high-sierra filesystem, but actually the solaris
hsfs filesystem also supports the later ISO9660 and
ISO9660+rockridge formats).
2) What does "hsfs VTOC" mean?VTOC is the "volume table of contents" on a ISO9660
filesystem. (disk block 16++)
3) I have put the Solaris install CD into the cd-rom
drive, so why the system cannot read from that cd
image?Probably because you somehow messed up burning the
solaris 8 images to CDR (for example by not unziping
the CD images first, or by generating a new filesystem
around the CDR image, or whatever). You should unzip
the downloaded files, and write each unziped file
bit-for-bit to a CDR ("Create CD from CD Image").
The "Installation" CDROM and the "Software 1 OF 2"
CDROM are bootable (ISO9660 + El-Torito)!
4) The installation image we download from sun.com, is
it bootable by itself? I try not to use the Solaris 8
Device Configuration Assistant bootdisk, but the
system refuse to boot from the installation CD. I had
already set the BIOS to boot from CD.Yes, two of them are bootable. See above.
5) How can I resolve the problem?Carefully follow the procedure given on sun's website:
http://www.sun.com/software/solaris/binaries/download.html

Vi error on nfs mount; E212: Can't open file for writing

Hi all,
I've setup a umask of 0 for testing on both NFS client (Centos 5.2) and NFS server (OSX 10.5.5 server).
I can create files as one user and edit/save out as another user w/o issue when directly logged into the server via ARD.
However, when I attempt the same from an NFS mount on a client machine, even as root I get the following error using vi;
"file" E212: Can't open file for writing
Looking at the system.log file on the server, I see;
kernel[0]: add_fsevent: no name hard-link! dropping the event. (event 2 vp == 0xa5db510 (-UNKNOWN-FILE)).
This baffles me. My umask is 0 meaning files I create and attempt to edit as other users are 777, but I cannot save out edits unless I do a wq! in vi. At that point, the owner of the file changes to whomever did the vi.
This isn't just a vi issue as it happens using any editor, but I like to use vi.
Any help is greatly appreciated. Hey, beer is on me!

Hi all,
Thanks for the replies
I've narrowed it down to a Centos client issue.
Everything works fine using other Linux based OS's as clients.
Since we have such a huge investment in Centos, I must figure out a workaround. Apple support wasn't much help as usual however they were very nice.
There usual response is "its unsupported".
If Apple really wants to play in the enterprise of business space, they really need to change there philosophy. I mean telling me that I shouldn't mount home directories via NFS is completely rediculus.
What am I supposed to use then, Samba of AFP? No, I don't think so. No offense to Microsoft but why would I use a Windows based file sharing protocol to mount network shares in a Nix env???

Can not open Camera Raw in Bridge CS4, or see thumbnails

MacBook Pro
OS 10.5.5
Photo Shop CS4 version 11
Camera Raw 5.2.0.65
I had another version of Camera Raw from PS3. When I bought the Canon EOS 5D Mark II, I deleted the old camera raw plug in, so as to not conflict with the new camera raw plug in.
When I open PS4, click Photoshop, click about plug in, ONLY one version of Camera Raw comes up.
In OS 10, when I click GO at the top, then applications, then Adobe Photoshop CS4, then Plug Ins, then File Formats, I get two Camera Raw icons: a blue lego like icon that says "Camera Raw.plugin" and another icon that looks like the Macintosh HD icon, but is labeled "CameraProfiles.dmg"
The problem is that I can't open files in Camera Raw when in Bridge CS4, nor can I see the little photo thumbnails either.
Can someone please help?
Desperate in NYC.

The Photoshop folder is NOT the correct location for the Camera Raw plug-in, since several versions of Photoshop.
The correct location, is, as described in the readme and in the FAQ of this very forum [hint]:
Mac: [root of your hard disk, NOT your user folder's library]/Library/Application Support/Adobe/Plug-ins/CS4/File Formats/

Can't open RAW files in CS3 or Bridge

I am using PowerMac G4 running OS 10.4.10, one gig RAM, with an Nvidia Geforce 4 MX graphics card. Adobe Updated notified me the new Camera RAW plugin was available so I said yes to install it. The installer hung half way through and I had to force quit it. Since then I can't open RAW (Nikon NEF) files in Bridge or CS3. I get generic raw file thumbnails in Bridge and the error "Could Not complete your request because Photoshop does not recognize this file type" when trying to open one into ACR from Bridge or Photoshop. I tried d'loading the plug-in and manually putting it in the proper folder, still no good. I have reinstalled the program from the install disk, purged the main and folder cache in Bridge, deleted the PS preferences (command+alt+ shift when opening PS), repaired OS permissions, and the like, all to no avail. Photoshop or Bridge just don't see the plug-in when opening NEF files, though it does show in the "Bout P, which is in the proper place- root/library/application support/adobe/plug-ins/CS3/file formats/camera RAW Plugin
How can I fix it?

Greetings! I am having the same problem.
I'm a graphic designer (not a photographer), working on Mac 10.4.11, CS3 (ps is 10.0.1, bridge is 2.1.1.9) with the latest ACR plug-in (4.3.1) and the latest DNG Converter. Our photo library is on a server, accessed by multiple computers.
We can preview .CR2 in Bridge, open .CR2 in PS.
6However, we cannot preview or open .CRW files. We have tested on three machines, all with the same problem. In the past (before CS3) we were able to open and process these files.
Tried opening .CR2 files in CS2 and couldn't. Couldn't open them with DNG Converter or Graphix Converter.
Have tried all the standards fixes:
1. Correctly updated the most recent Camera Raw plug-in, following Adobes very explicit instructions as to where the plug-in goes (checked it three times).
2. Removed a copy of the Camera Raw plugin from a secondary folder, hoping that might have caused conflict.
3. Reset my preferences in Photoshop and Bridge to default.
4. Purged the cache in Bridge (via TOOLS, not in preferences) and refreshed AND told Bridge to build new thumbnails/caches
5. Closed/reopened Bridge.
6. Repaired permissions
7. Restarted my computer
We are going to try to find a disc with original RAW photos that have never been placed on the server to see if it's a server issue. However I'm thinking that's not the problem.
Any ideas as to why we can no longer open these CRW files?
I have two problems I need to solve:
1. For future photoshoots: does turning OFF sRAW setting help prevent this problem?
2. Is there anyway to convert the .CR2 files without using Photoshop CS3/2 or DNG Converter? We're hoping to try to salvage the photos we have.
I did see Elev Man's comment about the problem being corrupt files...disk failure/problem fixed with Disk Warrior. I'll also check that out.
Thanks!

Can't open Cannon CR2 Raw image in Photoshop CS2

I've tried everything I can think of.
I downloaded/installed Camera_Raw_5.2 and still can't open any of the 2 DVDs full of images.
I'm not the best with the technical side of Adobe Products. Can anyone guide me a bit?

No, not in the application plug-ins folder. It goes in the File Formats folder, starting the path in your Root Level LIBRARY folder.
 
 

There are explicit, straight and strict instructions on the download page. Follow them to the letter.

 
 Check also the FAQs of the Camera Raw forum.
 
 c
<a target="new" href="http://www.adobeforums.com/cgi-bin/webx?13@@.3bb6a869">


Adobe Camera Raw Forum [CLICK HERE]


</a>
 
 If still in doubt, post over there and we'll pick it up there.
 
 You should have only ONE copy of the ACR plug-in, so you have to delete the old one that resides there AND any others you may have put there, such as the incompatible ACR 5.2 you mentioned early.
 
 c This screen shot shows the path for both CS2 and CS3.
 c The red arrows go all the way to the folder for CS3, but you can see the CS2 folder right above that, so you'll be able to figure it out.
 
 c
<a href="http://www.pixentral.com/show.php?picture=1lRlHcg6UKE7Egu9xihWadHisvlW5o" /></a>
<img alt="Picture hosted by Pixentral" src="http://www.pixentral.com/hosted/1lRlHcg6UKE7Egu9xihWadHisvlW5o_thumb.jpg" border="0" />
 c Click on thumbnail for full-size picture, then scroll horizontally.

Solaris 8 can't open root

Similar Messages

Maybe you are looking for