Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!think!ames!amdahl!oliveb!sun!david From: david@sun.uucp (David DiGiacomo) Newsgroups: comp.windows.news Subject: Re: Non-dying psterm's for non-root users? ; screen dumps Message-ID: <35228@sun.uucp> Date: Tue, 1-Dec-87 18:57:59 EST Article-I.D.: sun.35228 Posted: Tue Dec 1 18:57:59 1987 Date-Received: Sat, 5-Dec-87 04:14:19 EST References: <8712011210.AA02315@mahendo.Jpl.Nasa.Gov> Organization: Sun Microsystems, Inc. - Mtn View, CA Lines: 38 In article <8712011210.AA02315@mahendo.Jpl.Nasa.Gov> earle@MAHENDO.JPL.NASA.GOV (Greg Earle) writes: >I wrote a shell script called >`dumpscreen' that would do `screendump', pass it to `rasfilter8to1' (anyone >notice that the 3.4 version of this does not match the manual page? Try >the `choose dithering' option) This is a known bug in the 3.4 upgrade script. To fix it: cd /usr/bin foreach i (clear_colormap rasfilter8to1 rastrepl screenload) rm $i ln -s screendump $i end > if `/dev/cgtwo0' exists, then pass it to the >TranScript `pssun' with various option tweaks to get it almost full size (and >Landscape) on a LaserWriter. On the color machines, it becomes hit or miss >whether the end product will be correct, and this has happened under all three >window systems. Sometimes the symptoms are a `censored' all-black bar (or >bars) across certain parts of the output; other times in addition to the above >I get little replicated squished versions of the whole screen peppered across >the top of the `normal' screendump (along with the `censored' bars). RTFM screendump(1) !!! SCREENDUMP(1) USER COMMANDS SCREENDUMP(1) BUGS The output file or the screen may be corrupted if the frame buffer contents are modified while the dump is in progress. Sun Release 3.4 Last change: 16 January 1987 2 Make sure nothing touches the frame buffer while the screendump is running (e.g. no clocks). -- David DiGiacomo, Sun Microsystems, Mt. View, CA sun!david david@sun.com