Date: Sat, 2 Jan 1999 11:19:06 -0600 From: Richard Seaman <dick@tar.com> To: Doug Rabson <dfr@nlsystems.com> Cc: Brian Feldman <green@unixhelp.org>, Wiliam Woods <wwoods@cybcon.com>, "Kevin G. Eliuk" <kevin_eliuk@sunshine.net>, current@FreeBSD.ORG Subject: Re: Trouble with Staroffice5.0 Message-ID: <19990102111905.I2862@tar.com> In-Reply-To: <Pine.BSF.4.01.9901021117300.391-100000@herring.nlsystems.com>; from Doug Rabson on Sat, Jan 02, 1999 at 11:18:26AM %2B0000 References: <Pine.BSF.4.05.9901012002090.12539-100000@janus.syracuse.net> <Pine.BSF.4.01.9901021117300.391-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 02, 1999 at 11:18:26AM +0000, Doug Rabson wrote: > > I finally got it up and running too, but I had to do a lot voodoo :] It > > won't work, as it errs in the middle of its BASIC registration script. Does > > anyone have a registration code they can share, or some other way to get one? > > I had that. From the newsgroups, this is a common failure. Try running > setup again and telling it to repair your installation. Failing that, try > uninstalling and reinstalling. Worked for me, YMMV. When I had problems with registration, I unistalled, reinstalled, and then set the default PATH to include the Office50/bin directory. I had assumed that the reason it worked the second time was that I managed to set the PATH variable. But, maybe the deinstall/reinstall did something too. I'm also interested in a message you posted a few days ago, that SO50 runs on an SMP machine without threads. I guess I (and others) had assumed the reason SO50 hadn't worked before was because it needed a functioning linux_clone and the rest of the linux threads emulation to work. Perhaps this wasn't true. In working on the linux threads emulation, and also on SO50, a bug in linux_pipe was discovered and fixed. Perhaps this was all that kept SO50 from running? Maybe it just needs the fixed linux_pipe and thats all? I haven't tried SO50 without the linux threads patches, but it might be interesting for someone to try it with the linux_pipe patches (included by default in -current sources after about Dec 10) but without any of the other linux threads patches enabled (ie. compiled without COMPAT_LINUX_THREADS). Presumably you would still need the proc cmdline patches. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990102111905.I2862>