terryc |
Thursday 24 October 2013 at 14:32
|
terryc
|
I have the Battle chest version of WoW, which is one DVD + TBC expansion. Is there install script for this version? I can only find the 4 or 5 CD version.
Alternatively, can someone direct me to steps on how to get a working version copied off my windows 2000 system going. I keeping get crashes about "invalid/???" memory references and can only random install packages to try and fix this. I haven't been able to find any POL instructions.
Thanks.
|
Ronin DUSETTE |
Thursday 24 October 2013 at 16:26
|
Ronin DUSETTE
|
You cannot copy directly off of your computer. Thats why there is no documentation, and thats why it crashes. That is not how POL (or Windows, for that matter) works. There are registry entries, dependencies, etc.. Im not sure if there is a patch for it, but you can attempt a manual install. Or try running one of the 3 WoW scripts that are in POL, and try using that, and installing the the disc as such. Really, until someone writes a script for that particular version, then you will have do a manual install. There is a lot of documentation we have about writing scripts, and its really not hard. We are always looking for contributors. Here are a few links. http://www.playonmac.com/en/documentation.html http://www.playonmac.com/en/topic-10187-Standards_for_script_publishing.html
|
terryc |
Friday 25 October 2013 at 0:51
|
terryc
|
Thanks DJYoshaBYD
In the great "ask it of the ether" method of problem solving I found the single DVD install option soon after. I don't knowif it has turned up since original install or from some updating or why it is there now when I don't remember it from before. Sigh, could also be NBK.
After upgrade to PoL 4.2.1 it is complaining about not seeing the 32bit libaries(all possible installed) so I'm chasing that atm.
|
Ronin DUSETTE |
Friday 25 October 2013 at 0:57
|
Ronin DUSETTE
|
Post up your computer specs and Ill tell you how to fix that. Its super easy most of the time. POL should do that, as games without 32-bit libs installed wont work. Im sure the script was there, but there are a couple of different ones, and each script you can have options to choose from Steam installs, file on drive, or a disc, depending on how the scripter wrote it. but yeah. Get them computer specs up there, including make/model of your graphics card, and we will get that fixed. Its usually a simple thing.
|
Ronin DUSETTE |
Friday 25 October 2013 at 0:58
|
Ronin DUSETTE
|
*MOVING TO PLAYONLINUX FORUM* This particular area is strictly for posting up scripts. No worries. Its in the PlayOnLinux section now.
|
terryc |
Sunday 27 October 2013 at 13:53
|
terryc
|
I'm not sure what specs you want/need. Mobo is AMD 970-D3P, witj AMD FX 6300 6 core , with 16Gb Ramm. Runs Debin 7.1/Wheezy on AMD64 kernel ( 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux)
Graphics card is AMD(Gigabyte) Radeon HD7790 2G/dual head running the proprietary driver specifically for the 7790. None of the other fglrx drivers(prop & open source) recognise it.*
I've carried out the multi-arch thing and loaded the i386 libraries, plus every other i386/32 bit library that PoL has complained about in my various fiddlings, ...
plus I've tried to load the equivalent 32bit glxLib for every 64 bit I have, bar two, which are an either/or situation.
The output from glxinfo is all fine and recognises the AMD7790. Note, I can not also load glxinfo32. Possible undr Fedora apparently, but not Debian.
*Something I've just read that posted within the last two days suggested the latest catalyst/fglrxc beta will work on it, but I'm yet to test it.
|
terryc |
Monday 28 October 2013 at 1:10
|
terryc
|
Udate, I unload mesa-utils(glxinfo) and loaded mesa-utils:i386) and then ran glxinfo(32bit) and it said there was No direct render, so I think that is the problem.
The output also listed setting LIBGL_DEBUG=verbose, which MAY provide further information, but that may no difference to the output(no extra detail).
At least I now have something to work on as a likely cause of the problem.
|
terryc |
Tuesday 29 October 2013 at 2:58
|
terryc
|
I have now actually "fixed" the 32bit & 64 bit problem. A post on devgurus.amd.com listed how someone had managed to do the same on his AMD HD 7790 card. Basically, a bit of foo and install driver, remove driver and install driver again and I now have both 32bit and 64 bit.
I guess the unload of the 64bit driver, remade/made missing links in the 32bit libraries that remained when the 64 bit driver was reinstalled.
Also, when I had mesa-utils:i386 loaded, I copied glxinfo to glxinfo32 and the reinstalled mesa-utils(64bit) and now have both 32bit and 64bit versions.
|
terryc |
Tuesday 29 October 2013 at 2:59
|
terryc
|
Almost forgot, but I'm not able to get the supplied one dvd script to work, but that is anoher issue.
|
Ronin DUSETTE |
Tuesday 29 October 2013 at 3:27
|
Ronin DUSETTE
|
You are doing far too much. You shouldnt have to do any of that to get the 32 bit libs installed on a modern system. Dont over-think it. If you are running a 64 bit system, then there is more than likely either a default repo or a meta-package that adds 32-bit libs WITH 64 bit libs as they are installed. They tie them together like dependencies. For instance, "multiarch-support" on Ubuntu/Mint. Alas, this is not a PlayOnLinux or Wine issue, when it comes to your graphics cards. Thats something that is out of scope for us. You need to consult the forums for your distro to get those drivers installed correctly. We have no control over that. Really, when you install the proprietary AMD drivers, it asks if you want to install the 32-bit libs. If that didnt work, then you need to use your google-fu or request support in your distros forums. Ya know those posts that are at the top of the forum? The ones that say "READ BEFORE POSTING"? Yeah..... We need you to read those, so you know to post the debug output of playonlinux. They are not there for posterity, and were written to help all. Please read those and the POL forum rules, and gives us the debug output as specified, otherwise we are just guessing at what the issue is.
|