HDTenEightyP/NetNews huggingface dataset:
From: tmcconne@sedona.intel.com (Tom McConnell)
Newsgroups: fj.mail-lists.x-window
Subject: Re: .login not read???
Date: 28 Aug 92 01:25:13 GMT
Distribution: fj
Organization: Intel Corporation

Date: 27 Aug 92 18:08:08 GMT
Message-Id: <1992Aug27.180808.9782@ichips.intel.com>
Newsgroups: comp.windows.x


In article <1992Aug27.153007.6715@aio.jsc.nasa.gov>, tim@ial7.jsc.nasa.gov (Tim Sullivan) writes:
> 
> The .login file is not read when I start up X on my Silicon Graphics 
> using the 4.0.2 operating system running under X11R4.  This is not read
> on any of the Silicon Graphics we have.  The .xsession is read, but no 
> .login,  What am I doing wrong??? or what do I need to do???
> 
> 		Thanks for your help
> 
> 				tim@ial7.jsc.nasa.gov

  A matter of long discussion :)

From the FAQ:

----------------------------------------------------------------------
Subject:  36)  Why isn't my PATH set when xdm runs my .xsession file?

        When xdm runs your .xsession it doesn't source your .cshrc or .login
files. You can set the path explicitly as you normally could for any SH script;
or you can place all environment-setting statements in a separate file and
source it from both the .xsession file and your shell configuration file; or,
if you set your PATH in your .cshrc file, the normal place, you can make your
.xsession have PATH set simply by making it a csh script, i.e. by starting
your .xsession file off with "#!/bin/csh".
        If this doesn't work, also try starting off with:
                #!/bin/sh
                # Reset path:
                PATH=`csh -c 'echo $PATH'` ; export PATH
----------------------------------------------------------------------

  To be sure what happens, you should look at the file xdm runs when starting a
session, something like /usr/lib/X11/xdm/Xsession.

    Cheers,

    Tom McConnell
-- 
 Tom McConnell          |     Internet: tmcconne@sedona.intel.com
 Intel, Corp. C3-21     |     Phone: (602)-554-8229
 5000 W. Chandler Blvd. | The opinions expressed are my own. No one in 
 Chandler, AZ  85226    | their right mind would claim them.
From: bjst@sth.frontec.se (Bjorn Stenberg)
Newsgroups: fj.mail-lists.x-window
Subject: Re: GUIs Considered Harmful
Date: 2 Sep 92 09:10:17 GMT
Distribution: fj
Organization: IDK / Frontec, Sweden

Date: 2 Sep 92 04:40:20 GMT
Message-Id: <1992Sep2.044020.23032@sth.frontec.se>
Newsgroups: alt.religion.computers,comp.windows.misc,comp.windows.news,comp.windows.x

In article <NEERI.92Sep1141334@iis.ethz.ch> neeri@iis.ethz.ch (Matthias Neeracher) writes:

[..on the subject of using keyboard instead of mouse..]

> If you have normal command of your
>hands, however, you will be hopelessly slower that by using the mouse.

What is "normal" in that case?
In those applications where the keyboard interface has been worked on as much
as the mouse interface, I mostly gain at least 150% from using the keys 
instead of the mouse.
The primary gain is that you don't have to move around looking for/opening
menus, dialog boxes etc. You just press a key and ZZAP, it's done.

This, of course, requires that I have worked with the tool for a while, 
during which a combined mouse/keyboard interface helps me to find those
comfortable fastkeys so I won't have to move the mouse around so much...

>There are also extensions to assign menu selections and mouse
>clicks to any desired key combination (QuicKeys, for example).

Well, yes. There are ways of getting menu controlled MS-DOS command lines too.
I hardly think of such hacks as arguments _for_ the UI, though... :-)

>The medium and high level user usually knows how to extend the user interface
>to his/her liking. 

I think the original poster was defining "high level user" as someone who 
knows how to use a keyboard *AND* a mouse efficiently, and also wants to do so
whatever the computer/UI in question might be.

At least I do.

>I don't wnat to offend anybody, but I think most of the
>complaints about the fixed nature of the Mac UI are made by people who are
>power users of other machines, but casual users of the Mac.

Naturally.

When I've learned my applications inside out I don't mind a poor interface,
since I've learnt all the dirty tricks to get the application to act as I want.

The casual user doesn't know all those tricks, and is therefore depending more
on a well designed user interface.

	-- Bjorn
      ///  Bjorn Stenberg, Stockholm, Sweden         bjst@sth.frontec.se
     ///  main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}
\\\ ///  "- Your documentation no longer confuses me, old version!"
 \\X//                                              -- Lord Vadic, Dec Wars
From: lee@sq.sq.com (Liam R. E. Quin)
Newsgroups: fj.mail-lists.x-window
Subject: Re: What's new in R6?
Date: 30 Aug 92 02:14:27 GMT
Distribution: fj
Organization: SoftQuad Inc., Toronto, Canada

Date: Sat, 29 Aug 92 23:43:40 GMT
Message-Id: <1992Aug29.234340.11026@sq.sq.com>
Newsgroups: comp.windows.x

worthen@nosc.mil (Richard H. Worthen) writes:
>What will be in X11R6? When will it be available?

I don't know, but there is an article by Bob Scheifler in Issue 2 of The
X Resource, available from O'Reilly or (I presume) a bookshop.

(my notes are in [brackets])

The main areas he covers are:
X protocol extensions
low bandwidth X [NCD X/Remote?]
multi-threaded server
multithreaded xlib (already available, I think)
x test suite (already pre-released)
PEX upward compatible changes (5.1) in the near future;
PEX incompatible protocol changes will probably be made later
PEXlib changes being discussed
Mult-buffering and Stereo [3d, not HiFi] extension
X Image extension
Synchronisation extension
better typography - kerning, scaling, rotation, sub-pixel metrics, outlines,
	multiple-master fonts, greyscale fonts are all possible features
2D graphics
    downloadable fonts
    PostScript-style paths
    stencilFill
    splies
Internationalisation
c++ toolkit
icccm changes

You'll have to buy the book for the details :-)

Lee

-- 
Liam Quin, lee@sq.com, SoftQuad, Toronto, 416 239-4801; the barefoot programmer
  lq-text (Unix text retrieval package) mailing list: lq-text-request@sq.com
  latest released version: 1.10; ftp: ftp.cs.toronto.edu in directory: pub
  If Adultery is for Adults, is Juvenal for Juveniles?
From: envbvs@epb9.lbl.gov (Brian V. Smith)
Newsgroups: fj.mail-lists.x-window
Subject: Re: xterm popup menu strangeness
Date: 27 Aug 92 05:26:21 GMT
Distribution: fj
Organization: lbl

Date: 26 Aug 92 21:06:57 GMT
Message-Id: <25788@dog.ee.lbl.gov>
Newsgroups: comp.windows.x

In article <21104@optima.cs.arizona.edu>, azhao@cs.arizona.edu (Qiang Alex Zhao) writes:
|> In article <1992Aug26.172950.1002@cbnewsj.cb.att.com>, dbw@cbnewsj.cb.att.com (david.b.wood) writes:
|> |> On my xterm (direct from the X11R5 distribution) the popup menus don't
|> |> work correctly.  All I get with ctrl-leftbutton is a little box big
|> |> enough for the "Main" title, and nothing else.  The other two popups
|> |> do the same thing, except no text at all.
|> 
|> I met the same kind of problem except only those xterm's started from
|> .xinitrc have the problem, and those started from afterwards (either
|> from an old xterm, or opened by the window manager) don't have the
|> problem.
|> 
|> Any information may be helpful -- thanks.

From the FAQ:

Subject:  29)  Why are my xterm menus so small?

        You are probably setting the geometry small accidentally. If you give 
a resource specification like this:
                xterm*geometry: 80x24
then you are asking for all widgets under xterm to have their geometry set to
80x24. For the main window, this is OK, as it uses characters for its size. 
But its popup menus don't; they are in pixels and show up small. To set only
the terminal widget to have the specified geometry, name it explicitly:
                xterm*VT100.geometry: 80x24


-- 
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL; they don't pay me enough for that.
From: billr@saab.cna.tek.com (Bill Randle;923-4422)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Xnlock -- bug -- where's its author?
Date: 29 Aug 92 06:41:41 GMT
Distribution: fj
Organization: Tektronix, Inc., Redmond, OR

Date: 28 Aug 92 19:48:28 GMT
Message-Id: <3472@master.CNA.TEK.COM>
Newsgroups: comp.windows.x

Dan's current address is: argv@z-code.z-code.com .

-- 
	-Bill Randle
	Tektronix, Inc.
	billr@saab.CNA.TEK.COM
From: mark@trident.datasys.swri.edu (Mark D. Collier)
Newsgroups: fj.mail-lists.x-window
Subject: Using GUI builders (TeleUse in particular)
Date: 27 Aug 92 11:43:55 GMT
Distribution: fj
Organization: Southwest Research Institute, San Antonio, Texas

Date: 26 Aug 92 22:00:27 GMT
Message-Id: <121@trident.datasys.swri.edu>
Newsgroups: comp.windows.x,comp.windows.x.motif

I am planning to develop a very sophisticated, highly interactive
Motif application. I have been using X/Motif for several years and
have been using internal tools to simplify user interface develop-
ment. For this new project, I am being strongly encouraged to use
TeleUse. My questions are:

     1) How well do these GUI builders really work in terms of
        developing a non-prototype product?

     2) Can I really divide the user interface, application code,
        and yet make them talk together in an elegant fashion?

     3) How is TeleUse as compared to other GUI builders. Does
        its billing as a UIMS (as opposed to a VDT) really mean
        anything?

     4) Would you use TeleUse to develop TeleUse? My application
        is a display/GUI builder which focuses on output-driven
        COTS/custom widget (like DataViews, SAMMI, SL-GMS, etc).

All opinions are welcome and encouraged. If I get enough input I
will summarize the responses.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark D. Collier                      Southwest Research Institute
Senior Research Analyst              Automation and Data Systems Division
Voice: (512) 522-3437                Data Systems Department
FAX:   (512) 522-5499                Software Engineering Section
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: mahan@tgv.com (Patrick L. Mahan)
Newsgroups: fj.mail-lists.x-window
Subject: RE: how to implement slow calback routines ?
Date: 27 Aug 92 19:06:46 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date:    Thu, 27 Aug 92 10:49:53 PDT
Message-Id: <920827104953.21000150@TGV.COM>
X-St-Vmsmail-To: ST%"xpert@expo.lcs.mit.edu"

#
#My problem is the following :
#
#In several applications we add a callback routine to a pushbutton, let us say 
#that foo is this callback routine.
#In foo, we have to access large numbers of pieces of equipment;this operation
#may take up to 30 seconds. Therefore, we pop up an a XmMessageBox telling the
#user that the task in currently running.
#The problem is that after the creation of the messagebox we do not return to
#the XtMainLoop() and the messagebox is not managed on the screen, even if we
#call XFlush().
#

You need to register a Work Proc inside of the button callback to acutally
do the work for you.  This will allow 1) the message box to actually show
up and 2) let you complete your task.

Patrick L. Mahan

--- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------

Waking a person unnecessarily should not be considered  - Lazarus Long
a capital crime.  For a first offense, that is            From the Notebooks of
							  Lazarus Long
From: dan@watson.ibm.com (Walt Daniels)
Newsgroups: fj.mail-lists.x-window
Subject: Shared Libraries lose under AIX3.1/X11R5
Date: 27 Aug 92 18:01:45 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: 27 Aug 1992 12:01:40 EDT
Phone: 914-784/863-6736
Message-Id: <082792.120140.dan@watson.ibm.com>

I assume you used the standard build process from MIT.  If so one of
the lines in ibm.cf is #define ProjectRoot.  That is where stuff will
be put when you do a make install. Have you done a make install?

The path to the libaries is built into the executables. You can also
specify where they are in a LIBPATH environment variable.
Currently the builtin paths are to the ProjectRoot and to the build
tree (the later is bogus except for testing). It will go away at some
point in the public patches.
From: tim@xvt.com (Tim Beres)
Newsgroups: fj.mail-lists.x-window
Subject: Re: OPEN INTERFACE ?
Date: 28 Aug 92 07:59:46 GMT
Distribution: fj
Organization: XVT Software Inc.

Date: 27 Aug 92 21:40:31 GMT
Message-Id: <1992Aug27.214031.24224@xvt.com>
Newsgroups: comp.windows.x.motif,comp.windows.x


In article <r65eetw@Unify.Com> grp@Unify.com (Greg Pasquariello) writes:
>
>In article <1992Aug25.161416.27216@mr.med.ge.com>, pandey@mr.med.ge.com (Arvind Pandey 4-6847 MRCE) writes:
>> 
>> Has anyone outhere used a product "OPEN INTERFACE"
>> from Neuron Data (Palo Alto CA ).
>> 

>As far as I know, at this time there are two toolkits like this available.
>OI is one of them, the other is Galaxy by Visix.  Both of these toolkits
>are FAR superior to XT based toolkits IMHO.  

Disclaimer:  I know XVT, XVT is a client of mine, OI is no XVT.  (-:
             [Really, I consult for XVT, take me with Salt]

There are others, as well.  The company I do some consulting for,
XVT Software, also ships a toolkit that is used to develop
multi-platform portable GUI's.  Right now they are shipping 
release 3.0 of their toolkit.  They've been shipping a portability
toolkit for 4 years.  Motif/OLIT/Windows/Mac/CH(Unix&DOS)/PM are
all supported.  Call them at 303/443-4223 to get literature.

I have developed several *large* applications in XVT before coming
aboard as a consultant.  It does what they say it does.  It's portable,
offers an easier programming paradigm and has a companion GUI
builder product.

If you really want some in-depth analysis on the various toolkits,
check out the recent Byte comparison.  XVT does well.  There are
many, many other comparitive reviews in magazines.  Do yourself
a favor and check them out.

Yes, there are pros and cons of XVT, as well as the others.  Best
to bone up on them all and then ask some in-depth questions.

My favorite question:  Is toolkit XXXXX a least common denominator
approach?  

Answer:  Don't you mean greatest common factor, er, subset?  

-------------------------------------------------------------------
Tim Beres tim@xvt.com       
XVT lets me use their computer to read news and send email.  They 
do not condone or embrace my views or tell me what to read or write.
From: peter@ferranti.com (peter da silva)
Newsgroups: fj.mail-lists.x-window
Subject: Re: GUIs Considered Harmful
Date: 29 Aug 92 13:58:37 GMT
Distribution: fj
Organization: Xenix Support, FICC

Date: Fri, 28 Aug 1992 16:22:15 GMT
Message-Id: <id.4ERS.FIG@ferranti.com>
Newsgroups: alt.religion.computers,comp.windows.misc,comp.windows.news,comp.windows.x,comp.human-factors

In article <NEERI.92Aug25180329@iis.ethz.ch> neeri@iis.ethz.ch (Matthias Neeracher) writes:
> Gee, if even *Amiga* users start complaining about chrome, maybe it's time for
> Apple to cut back :-)

Hey, the Amiga GUI is about as low-chrome as you can get and still have it be
a graphic user interface.

Well, no, that's not actually true. The 3b1 User Agent, the Blit, 8 1/2, and
so on have a little less chrome. But it's still pretty spare.
-- 
Peter da Silva                                               `-_-'
$ EDIT/TECO LOVE                                              'U` 
%TECO-W-OLDJOKE Not war?                        Have you hugged your wolf today?
Ferranti Intl. Ctls. Corp.      Sugar Land, TX  77487-5012       +1 713 274 5180
From: hrt@utne.aosg.gsf.dec.com (Henry R. Tumblin AOSG)
Newsgroups: fj.mail-lists.x-window
Subject: Re: XDM configuration question
Date: 26 Aug 92 15:43:44 GMT
Distribution: fj
Organization: AOSG

Date: Wed, 26 Aug 1992 13:12:12 GMT
Message-Id: <1992Aug26.131212.4145@aosg.gsf.dec.com>
Newsgroups: comp.windows.x

> Can anybody tell me whether the xdm-config file gets passed through cpp or not.
> In particular, I would like to make parts of it conditional on the hostname of the
> current system. Our configuration files are NFS exported to some workstations, and
> I would like to conserve that part of the configuration while having the possibility
> to adjust some xdm configuration settings per host.

Why not just wrap a script around xdm and specify a different config file to
xdm dependant upon the hostname?

/Henry
--
Henry R. Tumblin                        Alpha Open Systems Group
From: poorman@convex.com (Peter Poorman)
Newsgroups: fj.mail-lists.x-window
Subject: Re: xterm popup menu strangeness
Date: 28 Aug 92 01:11:27 GMT
Distribution: fj
Organization: CONVEX Computer Corporation, Richardson, Tx., USA

Date: Thu, 27 Aug 1992 18:59:07 GMT
Message-Id: <poorman.714941947@convex.convex.com>
Newsgroups: comp.windows.x

In article <1992Aug26.172950.1002@cbnewsj.cb.att.com>, dbw@cbnewsj.cb.att.com (david.b.wood) writes:
> On my xterm (direct from the X11R5 distribution) the popup menus don't
> work correctly.  All I get with ctrl-leftbutton is a little box big
> enough for the "Main" title, and nothing else.  The other two popups
> do the same thing, except no text at all.

In <2232@fnnews.fnal.gov> shah@fnsony.fnal.gov (Hemant Shah) writes:

>I had similar problem with xterm. I turned out that I had set the size of
>xterm in my .Xdefaults file 
>Example:
>      XTerm*geometry:                80x40

>when I removed this line from my .Xdefaults file and added '-geometry' option
>on command line the problem was gone.

You're on the right track.

When you say "xterm*geometry" you're changing the geometry of EVERYTHING
in xterm, including the pop-up menus.  Since the sizes of the popups are
in pixels, not characters, they end up very small.

The fix is to specify the geometry for the vt100 widget, rather than a 
global xterm geometry.  For example:

	XTerm*vt100.geometry: 80x40

This leaves the rest of xterm with the default geometry.

-- Pete Poorman
   poorman@convex.com
From: johnston@hplabsz.hpl.hp.com (Michael J. Johnston)
Newsgroups: fj.mail-lists.x-window
Subject: Drawing Networks
Date: 24 Aug 92 23:35:33 GMT
Distribution: fj
Organization: Hewlett-Packard Laboratories Palo Alto,CA

Date: 24 Aug 92 18:06:45 GMT
Message-Id: <1992Aug24.180645.2407@hplabsz.hpl.hp.com>
Newsgroups: comp.windows.x

Does anyone know of a package that would run under X-windows
which will provide a graphical representation of finite state
networks? I am looking for something that will take as input
a series of specifications of labelled nodes and labelled
arcs between those nodes and generate a graphical representation.

Michael Johnston
UCSC
johnstn@ling.ucsc.edu
From: tom@bim.itc.univie.ac.at (Tom Kovar)
Newsgroups: fj.mail-lists.x-window
Subject: Re: X authority file utility: xauth  <-- mistery solved!
Date: 27 Aug 92 12:19:40 GMT
Distribution: fj
Organization: Inst.of Theor.Chemistry,Univ.of Vienna,Austria

Date: Thu, 27 Aug 1992 07:41:38 GMT
Message-Id: <1992Aug27.074138.5374@newssrv.edvz.univie.ac.at>
Newsgroups: comp.windows.x

rll@fatima.mitre.org (Roberto L. Landrau) writes:
: I just need to start the X server with the -auth $HOME/.Xauthority
: switch in order to enable the protocol.
: 
: Thanks for all the answers, especially Vivek Khera <khera@cs.duke.edu>
: (the first one to provide the information about the -auth argument).

  Actually the first one who mentions it is the Xserver, Xsecurity and
xdm manpage :-)
							Tom
From: aardvark@nt1l.krl.com (Donald Koch)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Sun Widget Set
Date: 29 Aug 92 20:33:41 GMT
Distribution: fj
Organization: Koch Research Labs

Date: Sat, 29 Aug 1992 06:59:05 GMT
Message-Id: <1992Aug29.025905@nt1l.krl.com>
Newsgroups: comp.windows.x

In article <9208281250.AA28212@expo.lcs.mit.edu>, HART@uv2.Eglin.AF.MIL ("DENNIS L HART") writes:
[...]
> Does anyone know of a "widget set" for Sun workstations that is layered upon
> Xlib and Xt?  We are looking at developing an interactive data visualization
> tool tailored to some special-purpose analysis requirements, and a "widget set"
> would reduce development time.  

Something wrong with the Athena widget set (Xaw) that comes with X?  (Of course,
there's also Motif, Xview and countable others.)

-- 
Don Koch
aardvark@nt1l.krl.com
From: neil@cadreor.cadre.com (Neil W. Van Dyke)
Newsgroups: fj.mail-lists.x-window
Subject: Re: GUIs Considered Harmful
Date: 4 Sep 92 00:26:34 GMT
Distribution: fj
Organization: Cadre Technologies, Inc., Portland Operation

Date: 3 Sep 92 18:22:15 GMT
Message-Id: <1992Sep3.182215.1813@cadreor.cadre.com>
Newsgroups: alt.religion.computers,comp.windows.misc,comp.windows.news,comp.windows.x,comp.human-factors

In my humble opinion, this thread has overstayed its welcome in
"comp.human-factors".  Could it please be taken somewhere else?  Thanks.
From: chip@xvt.com (Chip Atkinson)
Newsgroups: fj.mail-lists.x-window
Subject: olwm gives X Error: BadWindow, causes problems... Help!
Date: 4 Sep 92 10:08:24 GMT
Distribution: fj
Organization: XVT Software Inc.

Date: Thu, 3 Sep 1992 19:23:33 GMT
Message-Id: <1992Sep3.192333.29935@xvt.com>
Newsgroups: comp.windows.x,comp.windows.open-look,comp.x


(This posting appears in comp.windows.x, 
                         comp.windows.open-look
                         comp.x)
													9/3/92
Greetings,

We are having trouble with the OpenWindows window manager, olwm.  
Although this trouble is intermittent, it is readily reproducible.
The problem is that, occasionally, upon exiting a window we get a 
stream of X errors in the console window.  The only way that we 
have found of stopping the constant stream of errors is by killing 
the window manager.  The error message output comes so fast, that 
it is difficult, if not impossible to log in to the machine to 
kill anything.  Furthermore, a customer of ours encountered this 
problem in a pre-release version of our product.  The customer 
reported that the machine that he was on started sending out such 
a volume of ethernet packets that the network crashed.

The question and reason for posting this is: Has anyone
encountered this or a similar problem, and how did you deal with
it?  Do you know what is causing it?

Here is a copy of the error message:
(Bogus control characters cleaned up:)

olwm: Warning, X Error: BadWindow (invalid Window parameter)
  Request Major code: 40
  Request Minor code: 0
  ResourceId 80002fb
olwm: Warning, X Error: BadWindow (invalid Window parameter)
  Request Major code: 40
  Request Minor code: 0
  ResourceId 800030
olwm: Warning, X Error: BadWindow (invalid Window parameter)
  Request Major code: 40
  Request Minor code: 0
  ResourceId 800030
olwm: Warning, X Error: BadWindow (invalid Window parameter)
  Request Major code: 40
  Request Minor code: 0
  ResourceId 800030

ad nauseum....

At one point we were able to get a stack trace with the following
functions: 

ErrorHandler
etext
etext
etext
InstallPointerColormap
dispatchEvent 

(Sorry about the lack of info on the stack trace)

Any help would be appreciated.

Chip Atkinson

chip@xvt.com
From: samborn@lynchpin.mtkgc.com (Kevin Samborn)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Why is initial screen I/O so slow? (=NeWS!)
Date: 21 Aug 92 19:10:39 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: Mon, 17 Aug 92 13:28:03 EDT
Message-Id: <9208171728.AA00857@lynchpin.mtkgc.com>
Newsgroups: comp.sys.sun.misc,comp.windows.news,comp.windows.x

/\/\ On Thu, 13 Aug 1992 20:51:30 GMT, Philippe Grant said:

   Liam> You can get a small speed-up by disabling the "OpenWinsow 3"
   Liam> banner at startup.

   Philippe> ...and would you share the wealth?  How would a common
   Philippe> mortal go about disabling this banner?

Put the following in your ~/.startup.ps file

shareddict /PaintRootDict get begin
    
   %
   % the following line deletes the banner from startup
   %
   /InitPaintRoot { } def

end



--
kevin samborn
Sakura Global Capital
samborn@mtkgc.com