Hellocan someone tell me if there are any special tricks at hand t set up Solaris 10 on a Enterprise 3500? I`ve tried with different cd`s, burnt on different speeds, and also with bought one`s. All give the same result after boot cdrom, it starts but freezes right after the license message.And really freezes....stop-a doesnt work anymore neither. Solaris 8 sets up beautifully, and maybe a 3500 cant handle 10? Please help me ?

The Sun page for the Enterprise 3500 shows Solaris 10 is supported. A quick search of the Web shows that people have successfuly loaded Solaris 10 on Enterprise 10 systems.

So something else is going on ...

Is your dvd/cdrom drive ok?
Can probe it at the ok prompt first successfully?
Set auto-boot to false, diag-level to min and diag-switch to false. At the ok prompt, do printenv and copy the output somewhere. Then do set-defaults and reset-all command at the ok prompt.
Off/on the server. Insert the OS cd into the drive.
At the ok prompt, type boot cdrom -v
Try booting from the cd with minimal configuration on the server, meaning, remove unused PCI cards etc, so to isolate where the problem is.
This is the kind of step I would take...

Yes, so I figured, I have moved the processorboards around, tried with only one processorboard, changed disks and placements of them, changed fibercables, changed cdrom, tried with dvdroms, tried to install to scsidisk, all the same.........with Solaris 10 disks working perfectly on other systems, the installation dies after the License message.
I suppose it must be something "setenved" wrong but I cant think of what it could be.My machine has 4 cpus 8 gig memory and to keep it simple , now one 146 gig fiberdisk.
Ive added a framebuffercard from a sparcstation20 and Im using a sun monitor and keyboard/mouse.
Could it be I have to install with a serial cable and no monitor attached,weird..........
Help !!!!

Yes, use serial connection.. DId you do set-defaults as instructed..?
Do that and try, boot cdrom -v and post the output, only can be done by serialling in using your notebook. The monitor attached wont be able to capture and it will go blank for a long time before you scren come up with the boot message as what you see now.
If time allows, set the diag-level and diag-switch to max and true respectively and capture the POST output from your notebook. It will be easyto find from there, if your system pased all devices or had any h/w failure or not..

And the system previously uses any licensed items, such as Veritas Volume Manager? Cos it would be tied with the EEPROM (NVRAM) chip on board.. Just FYI

Here is the output with diag-level =min, diag-switch? =false and auto-boot =false.