ottomeister@my-deja.com (Ottomeister) wrote in message news:<ddc8b54b.0410221323.56abcd94@posting.google. com>...
> "Thomas Dehn" <thomas-usenet@arcor.de> wrote:
> > "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > > "Thomas Dehn" <thomas-usenet@arcor.de> wrote:
> > > > "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > > > > ./utresdef -a -c TEST 1024x576 TESTNAME
> > > > > results in:
> > > > > "This option is not yet available"
> > > >
> > > > Last time I asked, I was told that the message is correct.
> > >
> > > Does that mean that I am not able to create a new resolution?
> >
> > I think so. There is an undocumented, complex method
> > to change the fallback resolution, but thats all I know.
>
> In SRSS 2.0 there's an experimental mechanism called "altdispconfig" that
> will let you define new monitor timings. It's not documented because it's
> not intended to be a permanent part of the product, it will go away in the
> release after 3.0. Your Sun SE should be able to get information on
> altdispconfig if you need it. If you provide details of what you're
> trying to do (including monitor specs or model ID) then your SE might be
> also able to get a timing definition for you.
>
> In SRSS 3.0 the utresef command does allow you to create new timings.
> This went into 3.0 after the documentation cutoff so the information isn't
> in the man page or the docs. As with altdispconfig, your SE should be able
> to get the details for you.
>
> OttoM.
Thank you Otto!

Currently we are using altdispconf at our customer with SRSS 1.2.
We are going to port to 2.0.
My SE told me to use the new commands in 2.0. So I have to wait for
the undocumented informations from Sun :-(
So the question might be to use 2.0 or 3.0. But our customer will not be happy
to using a beta software.

Does anybody have experiences with performance issues on 3.0?

Thorsten