Thank you, Gavriel, I will try that this evening! I hope you do get paid, though! 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" > > > > > > 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! -- 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/