Hi Arnor,
> What are the chances of implementing something like this in SB? It would
> take out the possibility of running into command line limitations and it
> helps a bit with debugging too as you can then refer to the file for what
> exactly was being passed into SB to determine on which side problem with
> passed data is.
It's already possible to handle this with some hand-coding in the script
editor (processing a "response file" for non-interactive installations).
But I like your idea. I'll give it some thoughts on how to add this as a
built-in feature (with no coding required).
Friedrich