Re: Installing MS Office gives error in installer
actually i did manage to get it work work from the cd, you have to explicitly specify the -o unhide command when you run mount or put the unhide command in your /etc/fstab... as for the files not getting written, i had the same problem, it is the .lnk files (that i assume go in the start menu on windows)...i am thinking that they aren't being properly converted to .desktop files or something. I will try installing with crossover office tonight and post the results tomorrow -Dustin --- Rizsanyi Zsolt <rizsanyi(a)myrealbox.com> wrote: On Wednesday 17 April 2002 21:42, Speeddymon wrote:
I just recently installed wine-20020411 (as you may have noticed from my patch) I haven't tried installing Office 2000 on previous versions, but heard that it worked, so I decided to try it. First I tried it in Crossover Office (since i just recently got that also) and the Office 2000 installer complained that it couldnt find a package to install on the installation media. So I tried it in wine and it did the same thing... There were no debug messages or anything (in the console).
If anyone knows of a way around this, please let me know... If it has been mentioned before please point me to the right wine-devel archive so I can find it...
I have also dared to try to install office2k, and had the same problem. But I have found a workaround... When the installation fails, the MSI installer is already copied to your windows directory (I think its name is installmsi.exe or something like that - I dont have it at hand). So I have tried to invoke it with the msi file in the root of the CD (the data1.msi or something like that - the other msi is something else). This way the installation started. The configuration of what programs to install worked perfectly, but when copying the files the installer broke, and said that it can't write a file. I dont know what was the problem. I had enough space, the persmissions were ok, and so on.
I have tried again, and the installer broke again but now with a different file. So I give up, since I don't really need it to install, just I wanted to see what the people are talking about... But if you find a solution (or submit a patch :), then I will be interested...
Best regards, Zsolt Rizsanyi
__________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/
On Monday 22 April 2002 23:01, Speeddymon wrote:
actually i did manage to get it work work from the cd, you have to explicitly specify the -o unhide command when you run mount or put the unhide command in your /etc/fstab...
as for the files not getting written, i had the same problem, it is the .lnk files (that i assume go in the start menu on windows)...i am thinking that they aren't being properly converted to .desktop files or something. I will try installing with crossover office tonight and post the results tomorrow
-Dustin
Those .lnk files (you probably mean .kdelnk files) suppose to appear on your K menu if you're using KDE. If you still don't see them after a minute or two then run manually: kbuildsycoca Thanks, Hetz
no, in the installer its the .lnk files (windows link files) that aren't being copied from the cd (or being converted to .desktop files) or something at any rate tho, they never showed up in my kde menu or on my desktop... so theres probably a problem in wine somewhere. I will try crossover office tonight to see if it installs the files or not... and post back tomorrow --- Hetz Ben Hamo <hetz(a)kde.org> wrote:
On Monday 22 April 2002 23:01, Speeddymon wrote:
actually i did manage to get it work work from the cd, you have to explicitly specify the -o unhide command when you run mount or put the unhide command in your /etc/fstab...
as for the files not getting written, i had the same problem, it is the .lnk files (that i assume go in the start menu on windows)...i am thinking that they aren't being properly converted to .desktop files or something. I will try installing with crossover office tonight and post the results tomorrow
-Dustin
Those .lnk files (you probably mean .kdelnk files) suppose to appear on your K menu if you're using KDE. If you still don't see them after a minute or two then run manually: kbuildsycoca
Thanks, Hetz
__________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/
On Monday 22 April 2002 23:48, Speeddymon wrote:
no, in the installer its the .lnk files (windows link files) that aren't being copied from the cd (or being converted to .desktop files) or something at any rate tho, they never showed up in my kde menu or on my desktop... so theres probably a problem in wine somewhere. I will try crossover office tonight to see if it installs the files or not... and post back tomorrow
Check it on your .kde directory - they should be there. I'm running crossover office and they're appearing quite well. Thanks, Hetz
Well, I did use crossover office last night and everything turned out beautifully. Hell when I used that it also helped me (indirectly) to find the icon for loki's port of unreal tournament, so i now have that in my kde menu. what i was saying before though was that the windows link files (.lnk extension) weren't being put into the kde menu, i believe it is a bug/problem in 20020411 wine mainly due to that fact that that wine wouldn't install the icons but crossover office wine would...who knows, all is well now on my computer though. thanks for the help guys. --- Hetz Ben Hamo <hetz(a)kde.org> wrote:
On Monday 22 April 2002 23:48, Speeddymon wrote:
no, in the installer its the .lnk files (windows link files) that aren't being copied from the cd (or being converted to .desktop files) or something at any rate tho, they never showed up in my kde menu or on my desktop... so theres probably a problem in wine somewhere. I will try crossover office tonight to see if it installs the files or not... and post back tomorrow
Check it on your .kde directory - they should be there. I'm running crossover office and they're appearing quite well.
Thanks, Hetz
__________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/
On Tuesday 23 April 2002 19:51, Speeddymon wrote:
what i was saying before though was that the windows link files (.lnk extension) weren't being put into the kde menu, i believe it is a bug/problem in 20020411 wine mainly due to that fact that that wine wouldn't install the icons but crossover office wine would...who knows, all is well now on my computer though. thanks for the help guys.
The wineshelllink (the script responsible for installing the lnk files in the desktop menu) in the cvs wine assumes, that if you have a .kde directory in your home, then you have kde 1.x installed. And install kde 2.x files only if you have a .kde2 directory in your home folder. But on some systems (eg. RedHat), the kde config files are in .kde in home directory. That is the reason why the .desktop files are not installed on some systems. I have fixed wineshelllink in my cvs copy of wine, but never submitted it, because, I'm not really sure how to fix it to work on all the systems (I dont know how the other packagers do it). But if somebody needs, it I'm attaching the patch... Best regards Zsolt Rizsanyi
--- Rizsanyi Zsolt <rizsanyi(a)myrealbox.com> wrote:
On Tuesday 23 April 2002 19:51, Speeddymon wrote:
what i was saying before though was that the windows link files (.lnk extension) weren't being put into the kde menu, i believe it is a bug/problem in 20020411 wine mainly due to that fact that that wine wouldn't install the icons but crossover office wine would...who knows, all is well now on my computer though. thanks for the help guys.
The wineshelllink (the script responsible for installing the lnk files in the desktop menu) in the cvs wine assumes, that if you have a .kde directory in your home, then you have kde 1.x installed. And install kde 2.x files only if you have a .kde2 directory in your home folder. But on some systems (eg. RedHat), the kde config files are in .kde in home directory. That is the reason why the .desktop files are not installed on some systems.
I have fixed wineshelllink in my cvs copy of wine, but never submitted it, because, I'm not really sure how to fix it to work on all the systems (I dont know how the other packagers do it). But if somebody needs, it I'm attaching the patch...
Best regards Zsolt Rizsanyi
hmm that has me wondering... i will take a look at that tonight as i will have more time then (just gonna run home to get my zip disk right now) and see what I can come up with in terms of having wineshelllink finding the correct version..... we may need to remove the direcory checking stuff altogether... i have a couple ideas... 1) explicitly ask them for their kde version the first time wineshelllink is run (but then they would have to manually change the version number if they upgrade it) 2) always ask what the version # is... 3) read a file created by kde that has the version # in it (if one exists) 4) run some kde command with the --version arg and use it's output to get the kde version if possible 1 and 2 could be implemented directly in bash but then you have the problem of what if it doesn't get run in a terminal, so you could also have someone make a gtk/tk program that asks and is called from wineshelllink or you could do both and have 1 run if $display is set and the other one run if it isn't... just some thoughts... -Dustin __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/
On Wednesday 24 April 2002 19:31, Speeddymon wrote:
--- Rizsanyi Zsolt <rizsanyi(a)myrealbox.com> wrote:
On Tuesday 23 April 2002 19:51, Speeddymon wrote:
what i was saying before though was that the
windows
link files (.lnk extension) weren't being put into
the
kde menu, i believe it is a bug/problem in
20020411
wine mainly due to that fact that that wine
wouldn't
install the icons but crossover office wine would...who knows, all is well now on my computer though. thanks for the help guys.
The wineshelllink (the script responsible for installing the lnk files in the desktop menu) in the cvs wine assumes, that if you have a .kde directory in your home, then you have kde 1.x installed. And install kde 2.x files only if you have a .kde2 directory in your home folder. But on some systems (eg. RedHat), the kde config files are in .kde in home directory. That is the reason why the .desktop files are not installed on some systems.
I have fixed wineshelllink in my cvs copy of wine, but never submitted it, because, I'm not really sure how to fix it to work on all the systems (I dont know how the other packagers do it). But if somebody needs, it I'm attaching the patch...
Best regards Zsolt Rizsanyi
hmm that has me wondering... i will take a look at that tonight as i will have more time then (just gonna run home to get my zip disk right now) and see what I can come up with in terms of having wineshelllink finding the correct version..... we may need to remove the direcory checking stuff altogether... i have a couple ideas... 1) explicitly ask them for their kde version the first time wineshelllink is run (but then they would have to manually change the version number if they upgrade it) 2) always ask what the version # is... 3) read a file created by kde that has the version # in it (if one exists) 4) run some kde command with the --version arg and use it's output to get the kde version if possible
1 and 2 could be implemented directly in bash but then you have the problem of what if it doesn't get run in a terminal, so you could also have someone make a gtk/tk program that asks and is called from wineshelllink or you could do both and have 1 run if $display is set and the other one run if it isn't...
just some thoughts...
I dont think you should go by asking the user. You cant be sure, if he knows it right. The question is not only about its kde version, but also the directory of his config files... Besides, this script is not intended to ask for user input. You will be better of, if you just fix my patch, to not copy to .kde by default, but check if there exists a .kde2 and in that case to copy there. You should not make that script to cope with every possible setup. That would be an overkill. You should just make it to work with all the major distros. Other distros, and individuals with special setup should change the wineshelllink before installing or packaging. At most you could make tools/wineinstall ask for the needed info and generate wineshellink according to it. I like this idea... Best regards Zsolt Rizsanyi
I dont think you should go by asking the user. You> cant be sure, if he knows > it right. The question is not only about its kde> version, but also the > directory of his config files...which config files would you be referring to?> > Besides, this script is not intended to ask for user> input.> > You will be better of, if you just fix my patch, to> not copy to .kde by > default, but check if there exists a .kde2 and in> that case to copy there.> Actually I decided not to ask for the user input after all, instead it runs kded -v (if kded exists since i wasn't sure if kde 1.x had it or not) and greps the output for KDE: and sed's that to remove the KDE: (so that just the version number is there) and then writes that to /tmp/kdeverif /tmp/kdever doesn't exist then it proceeds like it would have before my patchif it does, it sed's the number in there for the first part of that number (1 or 2) and uses that to determine if you are running kde1 or kde2if you are running kde1 then it proceeds with the kde1 install, if you are running kde2 with the .kde dir it proceeds with kde2 install and if you are running kde2 with .kde2 dir it also proceeds with kde2 installi also figured out why things weren't being added to the k menu in mandrake...if you use the mandrake-style the k menu (as opposed to the default style) it stores the menu config files in /usr/share/menu instead of ~/.menu so i fixed it so that the menu configs are copied to both locations and everything seems to work well now. my only concern is if the 1st part of the fix (the one mentioned in the previous paragraph) will work on redhat or not, seeing as i dont know whether the menu configs are stored in ~/.menu or /usr/share/menu. Anyone that cares to test it out and let me know, feel free..> You should not make that script to cope with every> possible setup. That would > be an overkill.> You should just make it to work with all the major> distros.> Other distros, and individuals with special setup> should change the > wineshelllink before installing or packaging.> see response above> At most you could make tools/wineinstall ask for the> needed info and generate > wineshellink according to it. I like this idea...that may or may not be needed, depending on the outcome of a redhat tester> > Best regards> Zsolt Rizsanyithanks, and you too :)the patch is in the next message
--------------------------------- Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more
On Thursday 25 April 2002 03:45, Speeddymon wrote:
en it proceeds with the kde1 install, if you are running kde2 with the .kde dir it proceeds with kde2 install and if you are running kde2 with .kde2 dir it also proceeds with kde2 installi also figured out why things weren't being added to the k menu in mandrake...if you use the mandrake-style the k menu (as opposed to the default style) it stores the menu config files in /usr/share/menu instead of ~/.menu so i fixed it so that the menu configs are copied to both locations and everything seems to work well now. my only concern is if the 1st part of the fix (the one mentioned in the previous paragraph) will work on redhat or not, seeing as i dont know whether the menu configs are stored in ~/.menu or /usr/share/menu. Anyone that cares to test it out and let me know, feel free..> You should not make that script to cope with every> possible setup. That would > be an overkill.> You should just make it to work with all the major> distros.> Other distros, and individuals with sp! ecial setup> should change the > wineshelllink before installing or packaging.> see response above> At most you could make tools/wineinstall ask for the> needed info and generate > wineshellink according to it. I like this idea...that may or may not be needed, depending on the outcome of a redhat tester> > Best regards> Zsolt Rizsanyithanks, and you too :)the patch is in the next message
I'm running redhat. (v7.2) Here the applinks (*.desktop files) are in /etc/X11/applnk/. Or if it is a kde specific one then in /usr/share/applnk/ But I think wine should go in /etc/X11/applnk Of course this only holds if the user who runs the installer in wine is root. If it is a simple user then you have to install to ~/.kde/share/applnk/ as it is already done in the wineshelllink... Zsolt Rizsanyi
participants (3)
-
Hetz Ben Hamo -
Rizsanyi Zsolt -
Speeddymon