> > The only concern - as I noted was that at a couple of critical points
> > it was impossible to see/review any errors that may have occurred so
> > to a large extent I was flying blind.
> 
> The way sysinst works is to clear the screen and go to the next command
> when one succeeded, it only pauses if it detected an error.

That would suggest that the "if you see any errors above - abort now"
message should not be displayed - because by definition (screen had
just cleared) there could not have been any?  As it stands, the
message is _very_ disconcerting.  It implies that something may well
have gone wrong, and the user can clearly see that if anything did -
they have no way of knowing.

> Pasuing between each commands is way too painfull for install on slow
> machines (you have to stay close to it to hit 'return').

I certainly wouldn't advocate that - I hate having to hand-hold
things.  That's why I wrote http://www.quick.com.au/FreeWare/configs.html

I would think it better to let sysinst carry on as it does BUT keep a
log and at the point where sysinst is pausing to say "ok, point of no
return" etc, allow the user to review the log before making up their
mind.

--sjg