Impatient readers can skip to the last line of this message. In my ongoing quest for a non-MS word-processing package that can handle such mundane issues as image placement, page numbers, and browser-like navigation, I dragged a Staroffice 6.0 CD out of storage and installed it on a legacy W98SE box. That's not the source of my problem.
I then got greedy (wouldn't it be nice to have the same application running on both the legacy Win98SE box and my debian (sarge) box). I noticed that there was an uninformative message about "glibc ver: 2.3.2" in my Terminal window just after I started the install as root. The install went OK until I tried to install the Java Runtime Environment apparently highly desired by the Install engine. That failed ... I pressed on. Once the Staroffice install seemed to be finished, I restarted the 'puter and attempted actually to run Staroffice. The installation process started again, trying to load about a hundred files of the form, libctl641li.so, libimpreg.so, libdbi641li.so ... I chose "ignore" for the first 40 or so, but I grew weary of writing down their names for later retrieval, and clicked "cancel" for the next 60. Eventually, Install seemed happy, so I restarted the "puter yet again, only to be faced with a similar re-run of the installation engine, except that this time it wanted to incorporate various address lists (of which I keep none of which I know). I picked one, and the installation process promptly froze. I remembered that libmozab2.so was among the files that couldn't be found, so I aborted this final installation attempt. After Googling both the Sun and debian sites as well as the 'Net in general, I have decided to throw in the towel and be satisfied with a Win99SE version of Staroffice 6.0. Sun gives me until some time in 2010 to get it installed correctly, so I might manage to get used to it by then. My question is: How do I uninstall the Staroffice mess from sarge? Thanks, George Langford -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
