OttoM, > The '<< EOF' on the command line means (to most shells) "read > from standard input until you see the string EOF at the start of > a line, and feed everything you've read up to that point into the > command's standard input". The problem here is that your EOF > is not at the start of the line, it's indented, so the shell doesn't > recognise it as the end-of-input marker.
Ah ha. > You can feed the timing definition (the lines from 'htotal' to 'hz' > inclusive) into 'utresdef' in whatever way is most convenient. > If the '<<' thing (called a "here document") is too weird then you > could put those lines into a file and feed the contents of that > file into 'utresdef' by using a '<' redirection, or you could use > 'cat' to pipe the file contents into utresdef, or you could just run > 'utresdef' and then type (or copy+paste) the lines followed by > a Control+D to indicate end-of-input. I had tried using a file but still used << instead of < with that change it worked fine. >> One thing seems strange which is "utresdef -o" outputs nothing. > > That's a solid indication that 'utresdef' has not yet accepted any > timing definitions. And now oit is there and the monitor works great (after I did the utreadm bits. Many thanks. >> PS I am considering an upgrade to SRSS 4.0 soon, would that help? > > Yes, it would. SRSS 4.0 has a [EMAIL PROTECTED] timing baked > into its firmware. A SR1g, SR2 or SR2FS unit running 4.0 > firmware should automatically drive this monitor at 1680x1050. Ok, I have it working now, nice to know it will be easier after an upgrade. Thanks for the help Dave _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
