PlaneShift
Support => Mac OSX Specific Issues => Topic started by: HavePatience on November 07, 2005, 12:40:50 am
-
Hello, everyone. Thank you very much to ChaOs and dfryer for sacrificing much of their time to what amounts to a free experience.
I have followed the instructions in the guide to the letter, however, when I try and run the java updater, it doesn\'t work. It will load up, say update started at this specific time, but then goes no further. As of this posting I\'ve waited over forty-five minutes and haven\'t seen any change in the program. I am not sure why this is, or what can be done to fix it. In searching, it seems that few people have had problems with the java updaters.
My specs:
factory iBook G4: 1.33 ghz
512 MB ram
ATI Radeon 9550 32 MB
I\'m not sure what to do. Later tonight, I might delete all progress made and start over completely from the instructions in the guide. Maybe the second time\'s the charm?
Thank you very much.
-HP
-
What output do you get in the Updater window?
-
\"Unofficial Planeshift Updater.
The author of this program is not liable for any results of installing and/or using this program.
Use at your own risk.
By using this program you agree not to take any legal action against the author for any reason relating to this program.
Update started at 11/06/2005: 18:02:41\"
And that\'s it. over an hour later, nothing.
I really have no idea.
Thanks for your timely reply!
-
Silly question but have you tried to run it again the server was down but up now. :))
-
run what? psclient, or the java updater? psclient still crashes, even though I went through terminal to allow it permission. Java updater does exactly what I said above. It runs, sure, but doesn\'t do anything after saying \"update started\"
answers? advice? suggestions? barbs and insults?
-HP
-
What OS do you have and what is the output of typing \"java -version\" in Terminal?
EDIT: nevermind, nevermind. There was a little bug (stupid null pointers) which is now fixed. Redownload and update at your pleasure. *bows*
-
A note, unless you update the mirros as per dfryer\'s suggestions, Cha0s\'s updater will still hang.
Hi all, the obnoxious one is back. Missed you. Missed me?
-
Something for the developer (Chaos or whoever)....
The updater.app uses about 70% of the CPU capacity on my iMac G5 while downloading updates, which I deem a bit too much considering it\'s a fast processor and you are just downloading stuff... and even if it was compiling... 70%??? Since the recent G5 iMacs autoadjust the fan speed to the cpu use/ temperature your fan is kinda lifting off while using the app.
Anyhoo, just FYI. Keep up the good work.
---------------------------------------------------------------------------
iMac G5, 1.8 Ghz PowerMac(8,2), 1 GB DDR SDRam, ATI Radeon 9600 128VRam, Mac Os X 10.4.3
java version \"1.4.2_09\"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-232)
Java HotSpot(TM) Client VM (build 1.4.2-54, mixed mode)
-
The updater.app is not the Java updater, but instead the standard Planeshift updater. The reason it pegs the CPU is because it is actually running a 3D engine at full speed (Hah!) while updating. Quite wasteful, actually. Some changes have been made to make it less hard on the processor, but I actually had to remove them on the mac, since they interfered with the GUI actually working.
Sorry bout that, I\'m hoping to have a better fix in the future.
-
Yeah, I figure the app wasn\'t the java updater, but I thought it kinda fits into this thread (didn\'t want to start another thread). I just wanted to mention it. I know it\'s quite frustrating to get stuff to work.
-
Edit:
Never mind. I fixed the problem.
-
buddha: not anymore. See the post above yours. I fixed it. ;)
-
Cha0s, baby, you rock, BUT I tried using the updated Updater.jar, the one you pointed to. When I changed the mirrors to the ones dfryer recommended, it started to work perfectly. (Much better than the updater.app)
Thanks for all your work, you jam.
b
-
Hrmmm... thought I had that fixed... try it without any updaterconfig.xml file (i.e. just trash it) and see if that works. If not, you need to download again. If so, I need to do more debugging. :P
-
Could the mirror usage please be removed from Updater.jar until the mirrors are reliably updated? It seems that different mirrors have different versions, and my files are often overwritten (probably often with older versions!) every time I run the updater and it happens to use a different mirror than the last one. So the updater is basically going in circles, which is incredibly painful when using a 56kbps modem.
Failing that, does anyone know which of the mirror(s) actually contain the latest files? At least the updater says which mirror it\'s accessing (even if it\'s just a number and not the domain name), so I can just kill the update if it tries to access a bad one.
I still don\'t seem to be able to launch the client anyway, but I\'m at least trying to keep my files up to date for the day when that\'s finally fixed.
cheers,
Wayne
-
At the moment I believe the mirrors are all in sync. You shouldn\'t be having any trouble. Make sure you get the full update.
Tip: To make it always use Laanx, remove the text between and in updaterconfig.xml and lock updaterconfig.xml. Laanx is not the fastest mirror, however, I don\'t think it will matter if you\'re on 56k.
-
Are you absolutely sure they\'re all the same? I just re-tested and \"mirror 1\" gives consistently different component file sizes to mirrors 2 & 4, and they overwrite each other. Maybe I\'m just not understanding...
For a simple, quick illustration, I ran the updater multiple times in a row, but terminated each update as soon as it began on deathrealm.zip. But files up to that point should at least have been updated. What\'s important is the file sizes...
If it uses \"mirror 3\", it downloads the zipped repository, attempts to unzip it and then consistently says \"Error getting zip entries from file.\" It\'s been doing this for days. So that\'s as far as I can test that particular mirror.
If it uses mirror 1, after previously having used mirror 2 or 4, I get:
Updating root(5816 bytes of data)...Done
Updating data(14369 bytes of data)...Done
Updating docs(0 bytes of data)...Done
Updating support(0 bytes of data)...Done
Updating art(8750032 bytes of data)...AR: art/world/deathrealm.zip
If I restart and it then uses mirrors 2 or 4, I get:
Updating root(6034 bytes of data)...Done
Updating data(14592 bytes of data)...Done
Updating docs(0 bytes of data)...Done
Updating support(0 bytes of data)...Done
Updating art(18030634 bytes of data)...AR: art/world/deathrealm.zip
These file sizes are consistent between attempts, when an incompatible mirror has been run just previously. So it really looks like mirrors 2 & 4 are carrying different data to mirror 1 (and mirror 3 is totally screwed up).
If I use the same mirror twice in a row, or mirrors 2 and 4 one after the other, it doesn\'t find anything new to update before it reaches deathrealm.zip (which I never let finish, so it\'ll always want to be updated). So the updates for the one mirror are consistent.
I would assume that mirrors 2 & 4, having the larger file sizes, are more likely to be the up-to-date ones, but of course I can\'t be certain of that.
-
No, you\'re right, the Death Realm got a huge update, so that file should be bigger. And I wasn\'t aware of the mirror 1 issue (I actually did know about the mirror 3 issue, but I forgot ;) ). If you want to remove mirror 1 from the list of mirrors, just remove it from updaterconfig.xml and lock the file. I\'m interested to see what Laanx has, though I\'d hope it is up to date...