From: matija@avalon.physik.unizh.ch (Matija Milostnik)
Subject: Re: 2.05 installation question
Summary: User-Startup to place your preferred programms
Keywords: User-Startup, Startup-Sequence
Organization: Informatik Club d. Universitaet, Zuerich
Distribution: usa
Date: Thu, 8 Oct 1992 18:22:40 GMT


Bottom line at first: When will people learn to use the 
User-Startup and let Startup-Sequence unchanged?
They change Startup-Sequcne and end having problems they could avoid
reading the manual and changing ONLY User-Startup (or putting programs
in WBStartup).


In article <1992Oct8.94953.15258@ms.uky.edu> kherron@ms.uky.edu (Kenneth Herron) writes:
>This is on an A1000 running 2.05, booting from a hard disk.  In a 
>nutshell, the problem is this:
>
>Some of the config changes made by Iprefs require closing/reopening
>the workbench screen; if an external program is running you get this
>requestor asking you to exit it first. 

The new setting could require a screen with dimensions such as an 
already opened window couldnt live. e.g to small. Since Workbench
has no mean to tell the already running application to resize the
window, it asks you to restart it.

> Iprefs is run out of Startup-
>Sequence, so the initial CLI is still running when the changes start
>being applied, and I get several of these requestors.  Further, if I
>start up something like clock in User-Startup (or via the WBStartup
>drawer), it'll start before all of the changes are made, so I have
                      ^^^^^^
                      WRONG
>to kill the program to get the last couple of items.  This prevents
>automatically starting anything which opens a window.

This is flame time:-)
In the original Startup-Sequence all programs that have some output
are redireced to NIL:. The programs in the WBStartup drawer are
executed on LoadWB time. IPrefs is started long before this happens
and had performed all required changes.
So you did change the original Startup-sequence and have problem now.
Isnt that a chance to flame you? :-)

>It seems like what I need is to be able to save the final config in
>system-configuration so that Iprefs won't have any work to do, but
>there doesn't seem to be anything to write system-configuration
>any more. 

IPrefs and all other Prefs-programs save their data in ENV: for
the session wide use and in ENVARC: for use in a later session, e.g.
the next day, after power up. ENV: lives in RAM: and will be erased
after reboot. ENVARC: should live on disk and will be copyed on
ENV: on Startup-time. This is also done in the original Startup-
Sequence.


> Putting pauses in Startup-Sequence or User-Startup wouldn't
>help because the CLI window will still be present during those times.
>And that just about exhausts my list of ideas.

The User-Startup is meant to be started after all initialisation
are done in Startup-Sequence and before LoadWB (and all WBStartup
programs) is executed, thus avoiding all problems you are telling
us.

>I get the feeling I'm missing something obvious.  How does everyone
>else handle this?

first: RTFM  (F=fine)
second: Get your original Startup-Sequence
Third: Place whatever you want IN User-Startup for CLI programs
        and IN WBStartup for programs that dont need a CLI.
        (You may want to set the DONOTWAIT tooltype if appropiate)
Forth: Remember the bottom line at the start of this article :-)
Fifth: IF you have som more question, feel free to ask, we are here
       to help you...

Bye
 Matija
>Kenneth Herron                                   kherron@ms.uky.edu
-- 
Best regards from Matija Milostinik           : matija@avalon.ifi.unizh.ch  
                                              : matija@amiga.physik.unizh.ch
Therefore, use local labels in the procedures as often as possible. 
Save the environment!  Recycle!  ;-)                 (Bjoern Reese)
Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.hardware