This is a discussion on Crossover/Word97 install problem. It's Slack's fault says CW. within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> I bought and installed Codeweaver Crossover Office. Install went fine. I then installed MS Word 97. I got a ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I bought and installed Codeweaver Crossover Office. Install went fine. I then installed MS Word 97. I got a "Word Install failed" message. However, Word 97 seems to run fine. I wrote CW saying that they need to take a look at the "false failure" message. They replied saying: ------ I have seen these false failure messages in the past and yes it can be a pain sometimes. The issue in your case could be related to the slackware install. We have a few problems on Slackware due to its lack of a multi-threaded libperl. ------ I have no reason (i.e. don't know enough) to doubt the CW engineers, but thought I'd run it by some of you guys for verification. ANC |
| |||
| (Clue for the clueful: "f'up"...) A-B C. <acanton@adams-blake.com> says... > >I bought and installed Codeweaver Crossover Office. Install went >fine. I then installed MS Word 97. I got a "Word Install failed" >message. However, Word 97 seems to run fine. I wrote CW saying >that they need to take a look at the "false failure" message. >They replied saying: > >------ >I have seen these false failure messages in the past and yes it >can be a pain sometimes. The issue in your case could be related >to the Slackware install. >We have a few problems on Slackware due to its lack of a multi-threaded >libperl. >------ > >I have no reason (i.e. don't know enough) to doubt the CW engineers, but >thought I'd run it by some of you guys for verification. I had the exact same error message when I installed Codeweaver Crossover Office and Microsoft Word. I keep notes on everything I install, so let me check... <short pause> ... O.K. here it is. After doing a fair amount of research and experimentation, I found that the answer is .... something that I am not willing to share with someone who has consistently abused every newsgroup participant who has helped him. It's a shame, really. Here I am sitting at my computer with my text editor open to a document that has the answer you need. All I have to do is to cut and paste it into this reply, but your childish namecalling ("I don't think you CAN be a 'true Slacker' without being an arrogant asshole") and admission that you post specious arguments for the express purpose of angering other newsgroup participants ("Thus my tirade ... is mainly for the dialectic... and because it drives some of you arrogant SOB know-it-alls crazy.") makes me unwilling to give you the help that I would freely give to a total stranger. You are on your own with this, and with all future technical problems. Why should I give you free help only to be rewarded with abuse from you? Why would anyone? Here are some links to Paid/Commercial Linux Support. The free ride is over. The free lunch counter is closed. No more free support for you. If you want help, pay for it. Paid/Commercial Linux Support ***************************** Linuxcare Technical Support Contracts http://www.linuxcare.com/serv-supp/index.html Linux Unlimited Support Plan http://www.linuxunlimited.com/support.html Cybersource Commercial Linux and Unix Support http://www.cyber.com.au/cyber/support/rh-support.html The Linux Box: proactive, system-management contracts http://www.linuxbox.com/BUSINESS/business.php#support Computer Assistant: Computer Support Specialists that come to you http://www.computerassistant.com/index.asp Sine Nomine Associates Linux Support http://sinenomine.net/linuxsupport.php How to Set Up a Linux Support Contract http://www4.gartner.com/DisplayDocument?doc_cd=116768 |
| |||
| > We have a few problems on Slackware due to its lack of a > multi-threaded libperl. > ------ > > I have no reason (i.e. don't know enough) to doubt the CW engineers, but > thought I'd run it by some of you guys for verification. Well, its true that slackware's Perl is not multithreaded - at least it appears so from the output of 'ldd /usr/bin/perl' (no /lib/libpthread.so.0) -- дамјан There's no place like ~ |
| |||
| On Fri, 25 Jun 2004 03:56:31 -0700, Guy Macon <> wrote: > I had the exact same error message when I installed Codeweaver Crossover > Office and Microsoft Word. I keep notes on everything I install, so > let me check... <short pause> ... O.K. here it is. After doing a fair > amount of research and experimentation, I found that the answer is > ... something that I am not willing to share with someone who has > consistently abused every newsgroup participant who has helped him. > > ... > Dammit, you made me spray coffee on my keyboard ! THat's friggin' hilarious. You get an A+ for that post, GM. Keep up the good work! -- /\_][+--+ /\_)(_ pkw \_ | +--+][_/ )( \ _ | | \/ / _][_/ \_][_(+----> +--+ \_/ |
| |||
| Дамјан Георгиевски wrote: >>We have a few problems on Slackware due to its lack of a >>multi-threaded libperl. >>------ >> >>I have no reason (i.e. don't know enough) to doubt the CW engineers, but >>thought I'd run it by some of you guys for verification. > > > Well, its true that slackware's Perl is not multithreaded - at least it > appears so from the output of 'ldd /usr/bin/perl' (no /lib/libpthread.so.0) > > > Yes... but it is easy to build it with threading enabled if you desire. Having a threaded perl may or may not break other things. DB |
| |||
| paul wisehart <wise@lupulin.net> says... > >Guy Macon <http://www.guymacon.com> wrote: > >> I had the exact same error message when I installed Codeweaver Crossover >> Office and Microsoft Word. I keep notes on everything I install, so >> let me check... <short pause> ... O.K. here it is. After doing a fair >> amount of research and experimentation, I found that the answer is >> ... something that I am not willing to share with someone who has >> consistently abused every newsgroup participant who has helped him. >> >> ... >> > >Dammit, you made me spray coffee on my keyboard ! >THat's friggin' hilarious. > >You get an A+ for that post, GM. >Keep up the good work! Thanks! He really has abused every newsgroup participant who has helped him, so I figure that as long as I am going to be abused no matter what I do, I might as well leave the abuser twisting in the wind without an answer. I did get it working, and it certainly was *not* "Slack's fault." |
| |||
| Guy Macon <http://www.guymacon.com> wrote: > ... something that I am not willing to share with someone who has > consistently abused every newsgroup participant who has helped him. > > It What you're saying.... is that you really don't know.... but you want us all to THINK you do. They have a saying for guys like you in Texas: "Big hat.... no cattle." Guy, your anger, your insecurity, and your intelligence are wasted in computers. You could have written this, Guy. It could have been from you. It sure as hell sounds like you! http://www.people.virginia.edu/~jng2.../howl/howl.htm ANC |
| |||
| Guy Macon <http://www.guymacon.com> wrote: > >I have no reason (i.e. don't know enough) to doubt the CW > >engineers, but thought I'd run it by some of you guys for > >verification. > I had the exact same error message when I installed Codeweaver > Crossover Office and Microsoft Word. I keep notes on everything > I install, so let me check... <short pause> ... O.K. here it is. > After doing a fair amount of research and experimentation, I > found that the answer is ... something that I am not willing to > share with someone who has consistently abused every newsgroup > participant who has helped him. You're full of shit fatboy. You never installed Codeweaver Crossover or Microsoft Word. > It's a shame, really. Here I am sitting at my computer with my text > editor open to a document that has the answer you need. So why would you bother looking for it if you aren't going to share? You're full of shit, fatboy. > You are on your own with this, and with all future technical problems. Har. As if you speak for all AOLS posters. You're full of shit, fatboy. cordially, as always, rm |
| |||
| Realto Margarino wrote: > Guy Macon <http://www.guymacon.com> wrote: > > - - - - < snip > - - - - - - > > So why would you bother looking for it if you aren't going to > share? You're full of shit, fatboy. > > >>You are on your own with this, and with all future technical problems. > > > Har. As if you speak for all AOLS posters. > > You're full of shit, fatboy. > > cordially, as always, > > rm Oxymoronic sig...... 'cordially,..' & 'fatboy' Realto: don't bother replying to this, I am ignoring you. -- humjohn AT aerosurf DOT net |
| ||||
| On Fri, 25 Jun 2004 13:40:02 +0200, ?????? ??????????? <me@here.there.nowhere> wrote: > > Well, its true that slackware's Perl is not multithreaded - at least it > appears so from the output of 'ldd /usr/bin/perl' (no /lib/libpthread.so.0) I came to the same conclusion when I did: perl -V | grep thread -- Mark Hill <mrhill@gmail.com> |
| Thread Tools | |
| Display Modes | |
|
|