I'm experiencing a lot of application crashes with 10.3.9: iTunes, Mail, AIM, eyeTV to name a few... here's hoping for 10.3.10 (get over it with the number people, geez).
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac OS X 10.3.9 Now Available
- Thread starter MacRumors
- Start date
- Sort by reaction score
I'd rather hope we could figure out your problem and fix it, because I want Apple working on 10.4.1 with new features.fabsgwu said:
Have you looked at crashlogs? Do you have any odd extensions or startup items that might conflict? Is it only apps that connect to the internet?
xsnightclub said:
How about just renaming cut to move when referring to a folder?
Having to always use drag and drop (or the terminal) to move a file/folder is a PITA.
"CUT and Paste CAN'T work, since you would be trying to CUT it before Pasting."
???
I don't think you've ever used cut and paste on a different OS.
Wouldn't it be next-to-trivial to make a "Move File/Folder" Contextual Menu item thatduffman9000 said:
- Saved the path to a file/folder if the Menu Item was invoked on a file/folder
- Pasted the File/Folder if invoked in folderspace.
You might even be able to do this in applescript.
Isn't Limewire made with Java...?robjohn3333 said:
Open terminal and type Java -version
If you get an error you need to follow the Java fix mentioned earlier in the thread (downloading and reinstalling Mac OS Security update 2005-002, as far as I can remember...)
Wonder Boy said:
Yeah, the version is a string, not a float; it could be 10.3.the~end for all it matters.
I don't know if this has been posted here yet so sorry if this is repetitive. Here's a link to David Hyatt's (one of the lead developers for Safari) weblog that gives a little more info about the changes that were made in Safari 1.3
http://weblogs.mozillazine.org/hyatt/index.html
I didn't have any of the crash upon launch issues that some have reported, but I have left Safari alone (no haxies or extensions) since I got my Panther pre-installed eMac over a year ago. I do notice that Safari still has some issues with websites that are both java and javascript heavy and appear to be coded using Microsoft tools. In other words, some beachball appreciation time, then the JVM on the webpage finally loads. Firefox seem to handle those more consistently, but so far in my surfing experience they are very few and far between. Safari stills handles 99.9 percent of what I throw at it without any problems. I did try the security update fix and that appears to have resolved problems with java/javascript sites that started crashing Safari 1.3 that otherwise just beachballed as described earlier in 1.2. Now Safari 1.3 beachballs them just like Safari 1.2
The 10.3.9 update went without problems for me. Seems to have speeded things up a little bit, but speed impressions always tend to be a bit subjective. No major issues have surfaced for me.
Score:
http://weblogs.mozillazine.org/hyatt/index.html
I didn't have any of the crash upon launch issues that some have reported, but I have left Safari alone (no haxies or extensions) since I got my Panther pre-installed eMac over a year ago. I do notice that Safari still has some issues with websites that are both java and javascript heavy and appear to be coded using Microsoft tools. In other words, some beachball appreciation time, then the JVM on the webpage finally loads. Firefox seem to handle those more consistently, but so far in my surfing experience they are very few and far between. Safari stills handles 99.9 percent of what I throw at it without any problems. I did try the security update fix and that appears to have resolved problems with java/javascript sites that started crashing Safari 1.3 that otherwise just beachballed as described earlier in 1.2. Now Safari 1.3 beachballs them just like Safari 1.2
The 10.3.9 update went without problems for me. Seems to have speeded things up a little bit, but speed impressions always tend to be a bit subjective. No major issues have surfaced for me.
Score:
displaced said:I've just glanced over the PithHelmet and SIMBL pages, and there's something that bothers me a little...
(NB: I'm not a user of PithHelmet, or even Safari for that matter)
Shouldn't these tools which patch an existing application state clearly that they are liable to either stop functioning themseleves if the target program is updated, or cause any updated version of the target program to malfunction?
If I were running these kinds of utlities, and the target app started misbehaving, disabling the parasite apps would be the first thing I'd try -- even before posting a complaint on forums.macrumors.com
There should be a quick, easy-to-access toggle which can universally disable runtime patching of applications, simply so that the user can trace the cause of any odd behaviour quickly & easily.
I'm not saying these apps are intrinsically bad. Indeed, apps like PithHelmet make Safari the perfect browser for many people. But doesn't it make sense to ensure the user's fully informed on the possible outcomes of using these apps at critical points such as after updating the system?
Saft is a SIMBL plug-in that I've used for a while now - it warns you when you launch Safari after a Safari update that it may not be compatible and gives you the option to disable it or try to use it anyway. The developer usually has a new version in less than a day from Apple's updates, but it's still nice to know that some developers provide a way to warn you of potential issues.
Stella said:
wow, me too
EDIT: on the second try (no restart, no quit/re-launch, just on the second try to go to the page) it works fine. Very odd.
I also have to say that so far Safari feels noticeably faster. It was very slow at first, right after the update, but seems to have moved past whatever was bothering it ... or this is all in my head. No, I do not run any add-ons/mods to Safari.
duffman9000 said:
I'm not actually sure what he was trying to say there, but...
With every Mac app, choosing Cut will move the selected text onto the clipboard. Pasting will then copy it from the clipboard to the selected area.
Under Windows, most apps behave the same way. But for some reason Windows Explorer's Cut function behaves differently - choosing Cut doesn't move the selected item to the clipboard, it copies it. Then when you Paste, it deletes the original. This is very inconsistent!
Is 10.3.9 causing issue with external firewire drives?
I can't get my external firewire drive to mount, after installing 10.3.9. My external exclosure is also USB. I plug in a USB cable, drive mounts fine. I thought I saw other people are having the same issue?
I can't get my external firewire drive to mount, after installing 10.3.9. My external exclosure is also USB. I plug in a USB cable, drive mounts fine. I thought I saw other people are having the same issue?
Wow, that is easily one of the funniest, and most backwards, things I have ever read. Sure you didn't mix something up there?duffman9000 said:
Jim
Edit: Or I could be missing something. Is he not cutting first? Maybe I'm misreading something.
I just hope Apple keeps on updating Safari for Panther users. It is pleasing to note that Hyatt's blog states that 1.3 and 2.0 (the one in Tiger) are essentially the same in terms of rendering and standards. All that is different is some graphics stuff and of course RSS.
That would be nice if apple keeps Safari Panther fresh with render and standards improvements. RSS and other stuff isn't that necessary for me.
That would be nice if apple keeps Safari Panther fresh with render and standards improvements. RSS and other stuff isn't that necessary for me.
I installed the fresh copy of 10.3.7 on my Ti (erase & install) as I had some issues with 10.3.9. I started from the beginning and ran all those updates including 10.3.9 combo update. I worked. I can use Safari and no other problems so far.
I installed 10.3.9 combo on my 12" PB. That was an update from 10.3.7 to 10.3.9 via combo update via software update in System Preference. Safari worked without installing any additional patches. So far, no problems.
I will install 10.3.9 on my 15" PB soon, as it is still running on 10.3.8. Hope it works as well.
I installed 10.3.9 combo on my 12" PB. That was an update from 10.3.7 to 10.3.9 via combo update via software update in System Preference. Safari worked without installing any additional patches. So far, no problems.
I will install 10.3.9 on my 15" PB soon, as it is still running on 10.3.8. Hope it works as well.
excellt to see improved Safari and Mail reliability... maybe i'll be able to go back to Safari from Firefox. but Firefox does have that neat extension that re-loads any web pages you had open when it quit or crashed...
but i'm thinking i'm not going to bother with this update... should really be concentrating on getting everything backed up ready for a fresh install when Tiger comes.
but Firefox does have that neat extension that re-loads any web pages you had open when it quit or crashed...but i'm thinking i'm not going to bother with this update... should really be concentrating on getting everything backed up ready for a fresh install when Tiger comes.
I haven't read the whole thread, but has anyone else had problems opening PDFs, Mpegs, AVIs in 10.3.9?
Attempting to open the file will launch the assoc. application, but then beachingballing and 100% CPU usage follows. The only way to recover is to force-quit the application.
Is there any way to go back to 10.3.8?
Attempting to open the file will launch the assoc. application, but then beachingballing and 100% CPU usage follows. The only way to recover is to force-quit the application.
Is there any way to go back to 10.3.8?
I was under the impression that updates automatically updated the prebinding. That's what the optimizing part of an install consists ofNermal said:Update prebinding and Java should fix itself
Care to elaborate? Do we need to update manually from the terminal in addition to the update file?
Jim
WebHead said:
Um, duh, exactly. Mathematically, there ain't no such thing as 10.3.1 OR 10.3.10.
We're playing byu software versioning rules here, not gradeschool mathematics. By software versioning rules, each number between decimal points, or before the first or after the last, is a separate, distinct, whole number. "3.1" and "3.10" and "3.100" are vastly different releases.
I could understand the "but "3.1" and "3.10" are the same number!" crap when there's just one decimal point, because then you can at least make the argument that the number makes sense in a decimal counting schema as well as a version numbering schema. HOWEVER, the instant you have multiple periods in there, or dashes anywhere beside the first character, or letters aside perhaps from "e", or anything of that sort, THIS IS NOT A VALID DECIMAL NOTATION NUMBER!!!
Get over it, folks. What comes after 10.3.9? It could be any of three possibilities, barring version-skipping possibilities: "10.3.10" (a bug fix release built on 10.3.9), "10.4.0" (a minor release built on 10.3.x), or "11.0.0" (a major release built on 10.x.y). In Apple's schema, "major release" apparently means something like a ground-up rewrite these days as we've had three releases in a row which normally would have qualified as "major" releases sent out as "minor" releases ... but that's just a minor detail.
Anyways, way too much time spent explaining the obvious.