ray1941 |
Vendredi 5 September 2014 à 19:57
|
ray1941
|
I need to install Excel Viewer 2003. It is in the supported programs list.
I tried to install it from the playonlinx program and it downloads not an English version but Italian.
I am in Houston, Texas and I don't read Italian. ;) There is no language option the installer is localized for Italian from the start.
Also, the link to the install file playonlinux://www.playonlinux.com/repository/download.php?id=1267 is not beng interpreted by firefox correctly. It generates a 404 error instead of opening playonlinux. How do I set the file associations? Playonlinux is not listed in the possible file associations list within Firefox.
The system is a new install Linux Mint 17 XFCE 32-bit build, 2GB RAM, Athlon 64 CPU.
I'm using the default FireFox 32 for Mint which says it is up to date. No plug-ins ,but what it comes with.
How do I download the English version of Excel Viewer 2003 which is what I want?
Henry
|
booman |
Mercredi 10 September 2014 à 22:57
|
booman
|
You may want to do a manual installation instead. Just download Excel Viewer 2003 and then click "install" in PlayOnLinux
At the bottom in red, click "install a non-listed program"
You may have to do some research on what packages are needed to run Excel Viewer because you have to install them yourself.
This is what the PlayOnLinux scripts do for you automatically. So you will have to install Wine, Packages (Windows DLL's/Libraries) yourself in a new virtual drive.
I was researching on WineHQ's and they don't mention any specific libraries like dotnet, or vcrun... so just try it with typical packages:
- POL_Install_corefonts
- POL_Install_vcrun2005
- POL_Install_tahoma
|
Ronin DUSETTE |
Jeudi 11 September 2014 à 2:52
|
Ronin DUSETTE
|
No. No manual install. I JUST fixed this earlier today. Hit the "refresh" button in the Install window.
http://www.playonmac.com/en/app-1267-Microsoft_Excel_Viewer_2003.html
It downloads the English version now. For sure. Considering how old this post is, if only a few days, they probably got it straightened out, but it is worth noting that it is always a good idea to check to see if scripts have been updated. But yeah. this should be fixed now. Microsoft just changed their URL layout.
Just curious, what does being in Houston have to do with being fluent in Italian? lol. I am from California and speak Spanish, and am currently learning French, and can also read a bit of Hebrew. For instance, this whole project, except for me, are all based in France, and they speak fluent English. :) Just food for thought. hahaha.
EDIT: To be clear, I am not being a jerk. hahahahaha. Just being semi-flippant. In either case, it is corrected, and the English version should be the default download now.
Edité par RoninDusette
|
booman |
Jeudi 11 September 2014 à 19:13
|
booman
|
I think he was just making a joke...
How can I check if a script has been updated?
|
Ronin DUSETTE |
Jeudi 11 September 2014 à 19:39
|
Ronin DUSETTE
|
I know that he was attempting to make a joke. I am not getting into that on here, though. hahahaha. I have a, well, "thing", about "jokes" like that.
Well, there really is no automated way to check it, but if you go to supported software, and click on the entry for that script, whatever recent updates will be near the top of the contributions. That is how I check, anyway.
|
booman |
Jeudi 11 September 2014 à 19:41
|
booman
|
gotcha... I think I have google searched for a game and "script"
I somehow ended up at a PlayOnLinux page with updates/comments on a game and its script.
Most people "in general" won't really know what it means, but I have found them usefull for my manual installations.
|
Ronin DUSETTE |
Jeudi 11 September 2014 à 20:30
|
Ronin DUSETTE
|
Well, as I have said for a while, there is absolutely nothing that a manual install can do that a script cannot do. I still think it is better to turn the manual installs into scripts, than to dedicate so much effort to doing something that can be automated. lol.
If a script does not work, and someone has to do a manual install to get it to work, then a bug report should be opened for that script and updated to reflect what has been done in the manual install, so that non-technical people don't have to go through 5-20 steps to install something that can be done automatically. I do manual installs all of the time, and I love looking at other scripts for insight, but I only do manual installs until the script works, and then I only use that. haha. Of co7urse, if the script breaks, I use manual installs to figure it out, and then update the script to make sure it stays as automated as possible. Time is money. lol.
But yeah; to find the script, just go to Supported Software and look up the installer from there. It is actually quite robust now.
Edité par RoninDusette
|
booman |
Jeudi 11 September 2014 à 20:39
|
booman
|
Thanks DJ, I think we'll just have to agree to disagree on this subject.
Sorry for being off-topic.
|
Ronin DUSETTE |
Vendredi 12 September 2014 à 3:14
|
Ronin DUSETTE
|
It's ok. That is why there are both options, but I would love to have a public discussion as to why manual installs are more preferred by some, even though a properly maintained script could do the same exact thing as a manual install automatically with more robust error-catching. :) We should have a google hangout and post it one of these days. haha. Neither one is bad, but if people only use manual installs, then why should we bother writing scripts anymore? That was my point. lol.
If anything, a video discussion of the pro's and con's of both would for sure be useful for those that like to tinker with POL (which is what brought me to it to begin with. lol.). A large part of how POL works is undocumented (that is changing very soon though. hehehe.), so this will just lead to that much more insight on the matter. If you are down to do the hangout, hit me up on G+ and we will work out a time/date to do it (plus we can discuss KDE a bit, too).
Sorry for being off-topic, as well.
Edité par RoninDusette
|