From owner-freebsd-current Sat Jan 2 09:20:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04417 for freebsd-current-outgoing; Sat, 2 Jan 1999 09:20:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04390 for ; Sat, 2 Jan 1999 09:20:01 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id LAA18017; Sat, 2 Jan 1999 11:19:06 -0600 (CST) (envelope-from dick) Date: Sat, 2 Jan 1999 11:19:06 -0600 From: Richard Seaman To: Doug Rabson Cc: Brian Feldman , Wiliam Woods , "Kevin G. Eliuk" , current@FreeBSD.ORG Subject: Re: Trouble with Staroffice5.0 Message-ID: <19990102111905.I2862@tar.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Doug Rabson on Sat, Jan 02, 1999 at 11:18:26AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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