On Mon, 03 Apr 2000, you wrote:

Right before the wpo-full-dlx should be fine. It shouldn't actually matter very much though.

Well, I didn't know how quickly you'd respond so I took a guess and decided to install it right after wpo-full-dlx. BUT, I didn't get to install wpo-minimal-dlx because, unlike the first install attempt, when I installed wpo-full-dlx I got a script error just at the conclusion of the install (Kpackage's gas gauge was at 100% and the install script was finishing up when the script error occured) which immediately canceled the wpo-full-dlx install. No combinations of parameters would overide the script error. Since the install without wpo-full-dlx is a waste of time, I uninstalled all rpms, removed the directories the uninstall could not removed, rebuilt the rpm data base and did an updatedb. I also cleaned up any detritis left in the root home directory (.wine, in particular), and the fonttastic subdirectory under /var. I mention this cleanup process because it is the same process I used to remove the WPO rpms after the first install attempt. I have no idea of what could have been left behind from the first install that would block a second attempt. The error about "Unable to find user build....using root" etc., also occured again during the second install of the wpo-full rpm. I don't know if this is having a negative effect on the installation of the package or not. One side note. On both the first and second install attempts I was unable to unmount the cdrom. The reason was that even though I had uninstalled ALL the rpms for WPO2000, none of the scripts removed the fontfs server. It remained running until I use ktop to kill it, and only then would the umount command allow the /cdrom to be unmounted. This situation is not too nice unless the setupWPO2000 has the code in it to terminate the fontfs server at the end of the install process. I would assume that during the normal operation of WPO2000 the fontfs server is started when WPO2000 is started and shuts down when WPO2000 shuts down. Avi Schwartz devised a method of using a wrapper on rpm to bypass the glibc version check but pass all other calls to rpm. I am going to avoid such tricks. What I would expect of a commerical package is that it should require me to merely insert the install cd into the cdrom, as root, and run a setup program to install the app without problems. But, even with all of his trickery, he was unable to prevent wine from crashing, and he is still unable to run WPO. So, I am back to square one. If the situation hasn't been resolved and I will have to rethink my plans. I have four choices: 1) Stay with SuSE, get a refund on wpo, and wait for KOffice, or, 2) Stay with SuSE and wait for Corel to create a set of CD's that actually will work correctly on SuSE 6.3 without a lot of putzing around, or. 3) Stay with SuSE and hope that SuSE will change it's packaging of glibc to conform with other distros so my copy wpo will install, or, 4) Install RH 6.2 and hope WPO will install on it without problems. Option 4 is out. I've run two version of RH. Two is enough. Option 2 assumes the Corel will do such a thing. I doubt it. The 'minimal' installation might install but I haven't tried the 'minimal' install because I bought the delux version so I could drive the Cadillac. I would have stayed with my purchased version of WP8 if I wanted to drive a Honda. Anyway, I'm coming to the conclusion that the software on my CD set of WPO is defective, considering that setupWPO2000 wouldn't even install unless you took a package from the minimal list, and it looks for a user called 'builder' and a group by the same name. It just don't work as advertized on my box. Option 3 assumes SuSE would modify it's packaging of glibc for a single product. SuSE has no obligation to do that. Seeing that I have installed literally HUNDREDS of glibc packages and only WPO has a problem with the way SuSE packages glibc suggests that WPO should try a different method of detection. HOWEVER, Corel claimed that WPO was compatible with SuSE and that assumes they had actually installed and run WPO on a SuSE box running glibc (from shlibs). Based on my and Avi's experience this claim is long in the tooth, if not suspect. Thanks for your efforts, Gavriel, but after staring at my choices for the last hour I've decided not to pay to beta test WPO any longer. That is one of the major reasons I left the WinXX world behind. So, I will formally request that Chumbo.com give me an RMA so that I can return WPO2000 Delux. A step I sincerely regret taking because I was really looking forward to using WPO 2000. JLK An aside - I beta tested for a company which was converting a very successful DOS based rdms to the Win3.1 environment. The CEO kept pushing and pushing to meet a deadline that he called the 'drop dead date'. As each beta version was released many serious bugs noted in the previous version were found to be unfixed. One serious bug was a limit of the number of columns that a grid bound to a table could display, only twelve! I discovered that particular bug, because I was beta testing by actually converting a client's DOS project to the GUI version, on my own time, and gave the bug a 'show stopper' rating when I reported it. When the package was released I discovered that grid column bug still present. It would be no supprise to learn that the release was a flop and the GUI version never grew wings. It was a real suprise to lean that the reason the CEO pushed for the release date that he forced the developers to meet was that he got a BIG bonus for releasing before the deadline date, even though it meant the death of the product. You may have heard of the DOS product. The Win3.1 product was called Open xxxx but was quickly renamed, by the developers on the developers mail list, as Open EyeSore. I hope the CEO's of Corel haven't made the same mistake.

-Gav

Jerry L Kreps wrote:

...

I forgot to ask: At what point in the sequence of rpm files do I insert the wpo2000-minimal-dlx ? JLK

On Wed, 03 May 2000, you wrote:

...

Answering support related email doesn't count as working. 8-) My real job is development.

Anyhow, as I posted on the newsgroup, it appears that your problem on the install side is that the readme.htm file left out the wpo2000-minimal-dlx package in the required packages list for a manual RPM install. Add that back to your system, edit the /usr/lib/corel/bin/setupWPO2000 file as described in the newsgroups, and you should be fine.

-Gav

Jerry L Kreps wrote:

...

Wow, Gavriel, Working on Sunday? I hope you are taking at least two days out of seven off! I've got a 30 refund option which is putting a timeline on my decision to stay with WPO2000. I hope your packaging team can find and post a solution before May 30th. Jerry

On Sun, 02 Apr 2000, you wrote:

...

Hi guys,

I've forwarded the description below to our packaging team - I'm honestly not familiar enough with the packaging issues to help beyond this point.

I do know that a web page is being prepared with detailed install info for SUSE, Caldera, and a few other distributions, so hopefully that will solve the problems below.

The RPM packages are converted from debian .debs, btw, as you noticed.

-Gav

Avi Schwartz wrote:

...

That was my experience as well as I told Gavriel in an earlier message. To get the bin directory you need to install the minimal packages as well. Someone screwed up big time in the packaging department. Somehow I get the feeling the product was rushed to the market. It is not ready for prime time.

Avi

Jerry L Kreps wrote: > > Gavriel, > > Here is the process I tried: > > I logged in as root. > > Mounted the cdrom with execute permission > > Ran KDE > > Ran Kpackage, KDE's visual front end to RPM. > > Then I proceeded to install each file from the cd redhat distribution > directory in the sequence given in the WPO installation html, using > the Update and Replace package option. (-Uvh) After each file was > updated I looked at the file list to see how many there were in each > package and where they were being installed. > > After 10% of 'wpo2000-full' was installed I got a message > dialog, repeating the following two lines till the dialog disappeared > off the bottom of the screen: > "user builder doesn't exist - using root > group builder doesn't exist - using root" > I clicked ok and the dialog disappeared and the remaining 90% of the > files in the wpo2000-full package installed. Then I clicked the > files tab to see what files were giving the trouble. Immediately > another message dialog appeared, with a title of "file attributes > don't match', listing files in the order they were in the rpm > package in front of each file was the phrase: > ".....UG. /usr/lib/corel....<name of the file> > ..... etc..." > I don't know what this means. > > I continued installing the other rpms in the order required by the > installation document. When I was finished I was ready to edit the > file: /usr/lib/corel/bin/setupWPO2000 according to your instructions > BUT, it wasn't there!!!! In fact, the entire bin subdirectory had > only one file and a subdirectory in it. > > An interesting note: All the WPO2000 rpm packages installed in the > rpm database under a branch entitled 'Debian'. !! All of the files > had the source identified as a conversion from Debian. > > I used Kpackage to uninstall all of the WPO2000 packages and then > deleted manually the files and directories that Kpackage couldn't > remove. I then rebuilt the rpm database, to complete the clean off. > Back to square one. > Jerry > > On Sat, > 01 Apr 2000, you wrote: > > > Jerry, > > > > Instead of patching the script I got run-parts from a Mandrake rpm (I > > attached it, just put it in /usr/bin), all it is, is just a script. But > > wine still crashes on me immediately upon startup. If you got CO2K to > > work, then I'll know I have to look at my system and see what > > incompatibility may cause the crash. If you have the same problem, > > well, then it is a whole new ball game. > > > > Avi > > > > Jerry L Kreps wrote: > > > > > > Did you read the latest email from Gavriel where she says that the > > > code patch she gave me wasn't a 'real' patch, but I could use it to > > > manually remove lines marked with '-' and add lines marked with '+'. > > > I am getting ready to try an install in a few minutes. I'll let you > > > know what happens. > > > JLK > > > > > > On Sat, 01 Apr 2000, you wrote: > > > > It still doesn't work for me. How about you, more luck? > > > > > > > > Avi > > > > > > > > Jerry L Kreps wrote: > > > > > > > > > > ---------- Forwarded Message ---------- > > > > > Subject: Solutions for Install issues on SUSE, Caldera > > > > > Date: Sat, 01 Apr 2000 01:39:30 -0500 > > > > > From: "Gavriel State" <gavriels@corel.com> > > > > > > > > > > JerryKreps@AllTel.Net wrote: > > > > > > > > > > > > When I cd to the package directory and issue the ./setup command I get an error message > > > > > > saying that 'glic 2 cannot be found', and the > > > > > > an error say that glibc2 cannot be found. SuSE 6.3 is supposed to be > > > > > > glibc2 and I can nm /lib/ld-linux.so.2 and it responds with > > > > > > > > > > SUSE & the GUI Setup: > > > > > ===================== > > > > > > > > > > You are correct - this issue was noticed after the final CD went to manufacturing. I > > > > > believe that there will be a web page up about this shortly. The setup tool is doing > > > > > an 'rpm -qi glibc | grep Version' to get the version of glibc you're running, but SUSE > > > > > (unlike other RPM based distros) puts the C libraries into a different package (shlibs). > > > > > There's a simple workaround with a symlink, but I've forgotten exactly where, and I > > > > > don't have a SUSE system in front of me. > > > > > > > > > > For now the easiest thing to do is to simply rpm -i all the packages except the > > > > > glibc 2.0 versions of FontTastic and Wine. > > > > > > > > > > Distros without run-parts > > > > > ========================= > > > > > > > > > > After installing the packages, su and apply the following patch to the > > > > > /usr/lib/corel/bin/setupWPO2000 file: > > > > > > > > > > ----------- > > > > > @@ -47,5 +47,11 @@ > > > > > # run the setup sub scripts that have been installed. > > > > > if [ -d /usr/lib/corel/bin/per-user-setup ] > > > > > then > > > > > - run-parts /usr/lib/corel/bin/per-user-setup > > > > > + for candidate in /usr/lib/corel/bin/per-user-setup/* > > > > > + do > > > > > + if [ -x $candidate ] > > > > > + then > > > > > + $candidate > > > > > + fi > > > > > + done > > > > > fi > > > > > ----------- > > > > > > > > > > glibc2.1.3 based distros > > > > > ======================== > > > > > > > > > > There is a bug in glibc 2.1.3 that will cause an immediate crash on startup in WINE. > > > > > You need to run the following command before launching the applications: > > > > > > > > > > $ export LC_ALL=en > > > > > > > > > > You can edit the wpolauncher script to always do this if you like, of course. > > > > > > > > > > -Gav > > > > > > > > > > -- > > > > > Gavriel State > > > > > Engineering Architect - Linux Development > > > > > Corel Corp > > > > > gavriels@corel.com

-- Avi Schwartz Get a Life avi@CFFtechnologies.com Get Linux

-- Gavriel State Engineering Architect - Linux Development Corel Corp gavriels@corel.com -- __ _

/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *

/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*

/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!

-- Gavriel State Engineering Architect - Linux Development Corel Corp gavriels@corel.com -- __ _

/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *

/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*

/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!

-- Gavriel State Engineering Architect - Linux Development Corel Corp gavriels@corel.com

-- __ _ / / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable * / /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day* /____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/