"Gérard Henry" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Which button are your users pressing? The one labelled "Auto" will > > produce a dialogue that says "Not Available". > > > > The button labelled "Menu" should offer a whole range of setup > > choices. The up/down arrows on their own (when the Menu is not > > active) should adjust the brightness directly. If these buttons > > don't work then that's a very serious bug.
I was wrong, this is incorrect. It only works this way on early prototype units like mine. On production Sun Ray 170s the Menu button does not work (it shows "Not Available") when the signal source for the panel is the Sun Ray input. The Up- and Down-arrows can be used to change the brightness of the display but the Menu can not be used. The Menu is available only when the signal source is the external VGA input and a signal is being driven into that input. The reason for this is that the Menu selections control the analogue circuitry associated with the VGA input. Since the Sun Ray signals are pure digital signals they bypass this analogue circuitry and so are not affected by the Menu settings. The panel engineers decided that it would be confusing to show the Menu when the Sun Ray is the signal source because any adjustments made in the Menu would have no effect on the image. I can see their point, but I think they could have used a better message than "Not Available" to explain what was happening. (My guess is that they used it because it was already defined for the Auto button.) And it's not really true that nothing in the Menu affects the Sun Ray input, the message language setting is one thing that applies regardless of the signal source. I think it's a bug that that can't be changed when the Sun Ray is the signal source but I don't expect that it will get fixed unless customers complain about it. Anyway, it sounds as though your units are working as expected, assuming that the Up- and Down-arrow buttons do let you adjust the brightness. It's even supposed to be documented although I can't find the 170 manual to confirm that. > i'm using SRSS3.0 on sparc/solaris9, but i'm also using special > firmware you sent me weeks ago to solve problems with wheel mouse. > In log file, i saw: > /var/opt/SUNWut/log/messages.2:Jul 19 09:12:47 > [192.168.128.146.2.2] 0x0.0x7237 8:0:20:c1:64:f0 Application: > make_listener: software Version mismatch -- DHCP version > (CoronaP1-3.0_51,REV=2004.11.10.16.18) booted > (CoronaP1-ottom.gate.200501211259) > > Do you think i have to reinstall original firmware? The buttons on the 170's bezel are managed by a dedicated microcontroller. The button processing is totally independent of whatever Sun Ray firmware the unit happens to be running. If you'd like to get back to using supported firmware then you should be able to use the official 3.0 patch. The 3.0 patch firmware includes fixes for several mice, including yours, that did not work correctly with the 3.0 FCS firmware. However, this will have no effect on the button behaviour. (It would be helpful if you could try the 3.1 firmware and see whether it works correctly with your mice. 3.1 has a new algorithm for detecting and configuring scroll wheels so it should work automatically with all wheelmice. If it doesn't work then the sooner we find out, the sooner we can work on fixing the problem.) > i opened a case since 2 days (case 37424423) without response The case history says that the support centre sent email on Friday after they couldn't reach you by phone. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
