I did it again, replied to a message without "replying to all", so I'm
sending it out to everyone, maybe it solves problems for others as well.
Thanks to everyone for the help with the screen resolution using X.. I'm
quite useful with raw Unix details, but with X I'm pretty useless..
Useless, but getting better!!
Thanks again everyone.
Here's my response to storing error messages within scripts:
> I think I can still be of help to you.. I've done a lot of work with C,
>and error handling. Unix however, is even easier to retain error messages,
>and you can even make your own.
> You know of redirection with Unix?
>
>cat < myletter > newletter
>
> This basically receives data from myletter, and redirects output to the
>newletter file.. But in your case, you want to retain the error message if
>say there is no myletter file.
>
>cat nofile 2> myerrors
>
> I guess you've used <, >, << and >> before? Well, they all have default
>values. Basically, there are three byte streams within redirection
>operations, and they are representing by 0 (standard input), 1 (standard
>output), and 2 (standard error). You can change the defaults by simply
>adding the bytestream to the left of the redirection operator.
> The example above sends the error to myerrors file. Likewise, you can
>append to an error file, and maintain a history of errors, like so:
>
>cat nofile 2>> myerrors
>
> I hope this is what you wanted.. Where I lack in knowledge of X and X
>configuration, I make up in command line/scripting knowledge. I have had
>experience with SCO Unix, but I never used a graphic interface extensively.
So I'm a
>bank of knowledge with commands and such..
> I got the sound card working, it was a different approach with Caldera,
>but you definitely pointed me in the right direction. I am forever in your
>debt.. Well, maybe not forever, but I'll give you at least five minutes
:)
