Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!unmvax!uokmax!drtiller
From: drtiller@uokmax.ecn.uoknor.edu (Donald Richard Tillery Jr)
Newsgroups: comp.sys.amiga.misc
Subject: Re: HELP! Prefs-Problems under Wb 2.0
Keywords: HELP
Message-ID: <1991Jun24.210441.21208@uokmax.ecn.uoknor.edu>
Date: 24 Jun 91 21:04:41 GMT
References: <1991Jun19.132820.19300@informatik.uni-erlangen.de> <1991Jun21.214824.4995@comspec.uucp>
Organization: Engineering Computer Network, University of Oklahoma, Norman, OK
Lines: 15

2.0 doesn't open up the actual screen during boot-up until it absolutely has
to.  If you have commands in your startup-sequence that must (or could
potentially) send output to the CLI, it is opened at that time.  If this is
before the iprefs command, you get the stock size (640x200|256|400|512) until
iprefs is run.  Then the CLI is opened so iprefs must wait for it to close to
change the screen (why I don't know, CLIs and Shells can be sized and have the
text autoroute, I don't know why they couldn't do that same thing after the
screen was re-sized). 

Just make sure that any command you have in your startup-sequence that could
send output to the CLI before the iprefs call is re-directed to NIL: (i.e.
cpu >nil: nofastrom burst cache) and the CLI won't be opened until the
screen size is what you desire.

Rick Tillery (drtiller@uokmax.ecn.uoknor.edu)