Hi, starting with OOo 2.0.4 you can use the parameter -nofirststartwizard to, guess what... suppress the startup wizard.
HTH, Kai. DeCouto, Douglas wrote: > Hi, > > My goal is to use OOo to run in a server process, with multiple > instances running separately, processing documents driven by a pyUno > script. > > I am trying to get OOo to automatically setup its user installation > files, so that I can create each instance on the fly for soffice when it > runs. I've tried using -headless when starting soffice, as shown in > this message: > > http://api.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=14253 > > e.g.: > > soffice -env:UserInstallation=file:///tmp/xxx -headless > '-accept=socket,host=localhost,port=3051;urp;' > > However, when the user install files do not already exist, office exits > without any error message after creating the directory /tmp/xxx and > populating it with some files. If I run the same command again, soffice > also exits without any error. > > However, if I run _without_ -headless, fill out the registration > screens, exit, and rerun _with_ -headless, soffice runs successfully. > > Any hints on how to get around this? I know I can copy a working user > installation directory, but I want to avoid keeping a template user > installation directory around if possible. > > Thanks, > > Doug > -- > Douglas S. J. De Couto [EMAIL PROTECTED] > > *** > This e-mail, including attachments, may contain information that is > privileged, proprietary, non-public, confidential > or exempt from disclosure and is intended to be conveyed only to the > designated recipient(s). If you are not an > intended recipient, please delete this e-mail, including attachments, and do > not disseminate, distribute or copy this > communication, by e-mail or otherwise. The unauthorized use, dissemination, > distribution or reproduction of this > e-mail, including attachments, is prohibited and may be unlawful. We reserve > the right to monitor and review the > content of all messages sent to or from this e-mail address. > > We use digital certificates on email where appropriate to protect sensitive > information and to identify our employees. > > To validate our digital signatures, please use this quick update from > security authority Quovadis(http://www.quovadis.bm/root.asp). > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
