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 7W72 Seeded
- Thread starter MacRumors
- Start date
- Sort by reaction score
swissmann said:
Its called Software. Computers want perfection and humans are not perfect.
Bugs will be fixed and bugs will be introduced - x steps forward, y steps backwards. Hopefully x > y
No version of OSX ( or any other software ) will be 100% perfect - well, using current development methods anyway.
Just be glad that Apple are still fixing bugs in Panther despite that Tiger is less than 6 months away.
raggedjimmi said:wowthe grammar game
nice to see people so interested in what numbers OSX will reach too. it shows you care
Hopefully it means there are a lot of people in the same situation as I am. I had no problem with 10.3.4 which my Mac shipped with, I have had no problems with 10.3.5, 10.3.6, 10.3.7 or 10.3.8, either.
On second thought, I did once have a problem connecting an external USB hard drive that a co-worker brought with him. Maybe that could be fixed with 10.3.9.
Panther most probably benefit from some Tiger based fixups
Look at the Darwin kernel version apparently included in 10.3.9 (info easily found on the Net) and compare to the one Tiger is based on (also easily found on the Net)...
More or less. As Tiger approaches its releasable state, there are obviously some details that can be (and are) retrofitted to Panther. Some kind of bugs fixed during Tiger development, drivers updates and the like.MagnaPalam said:
Look at the Darwin kernel version apparently included in 10.3.9 (info easily found on the Net) and compare to the one Tiger is based on (also easily found on the Net)...
sjpetry said:
But what is Tiger going to really do for us?
A whole new round of bug fixing. Beyond that?
Money in Apple's pocket, sure that's good.
But what has Tiger really got to offer that is so great.
Spotlight - Doesn't impress me. Just more overhead and a security hole.
Dashboard - A boring gimmick. We've already got that functionality.
.Mac & Sync improvements - Yuk - I don't like .Mac - it is over priced, under powered and not terribly useful.
Automator - I just hope it is a lot better than QuickKeys and AppleScript.
VoiceOver - I don't like to talk to the computer. Typing & mousing/trackpading is so much faster and easier. This also doesn't justify a new OS.
Parental Controls - 1) they won't get it right, 2) kids will hack it and 3) kids should be world ready because you'll never make the world safe. Oh, or maybe this is protection for the parents?!
iChat (ugh), Safari & Mail enhancements? Well, maybe but we don't need a new OS for that, just upgrade and fix the existing applications.
Version numbering system (Major Build/Minor Build/Patch)
I saw this post on another website that explains the version numbering system: (quote is from this link http://forums.applenova.com/archive/index.php/t-712.html)
Post #1
"Well, logically, 10.4 is "ten point forty". If they went to 10.9 ("ten point ninety") and went to 10.10, it's the same number as 10.1"
Post #2 (reply to post #1)
No, no, no, no, NO.
You're not getting it.
THESE ARE NOT DECIMAL NUMBERS.
Otherwise, 10.3.4 would be *MEANINGLESS*.
(This needs to be in a FAQ, dammit.)
Build numbers are of the form: Major Build, Minor Build, Patch.
10.3.4 = Major Build 10, Minor Build 3, Patch 4.
The 47th minor build of major build 1 would be 1.47 and would come *AFTER* 1.5.
THESE ARE NOT DECIMAL NUMBERS.
The use of the period to delineate the pieces of the build number is perhaps unfortunate... one could use *any* character.
10,3,4 or 10-3-4, or 10/3/4 mean exactly the same thing as 10.3.4.
So, given that... 10.10 comes after 10.9, and before 10.11, and has *NOTHING* to do with 10.1. Got it?
DTphonehome said:
I saw this post on another website that explains the version numbering system: (quote is from this link http://forums.applenova.com/archive/index.php/t-712.html)
Post #1
"Well, logically, 10.4 is "ten point forty". If they went to 10.9 ("ten point ninety") and went to 10.10, it's the same number as 10.1"
Post #2 (reply to post #1)
No, no, no, no, NO.
You're not getting it.
THESE ARE NOT DECIMAL NUMBERS.
Otherwise, 10.3.4 would be *MEANINGLESS*.
(This needs to be in a FAQ, dammit.)
Build numbers are of the form: Major Build, Minor Build, Patch.
10.3.4 = Major Build 10, Minor Build 3, Patch 4.
The 47th minor build of major build 1 would be 1.47 and would come *AFTER* 1.5.
THESE ARE NOT DECIMAL NUMBERS.
The use of the period to delineate the pieces of the build number is perhaps unfortunate... one could use *any* character.
10,3,4 or 10-3-4, or 10/3/4 mean exactly the same thing as 10.3.4.
So, given that... 10.10 comes after 10.9, and before 10.11, and has *NOTHING* to do with 10.1. Got it?
I am just suprised as heck that there's not a story about Jeff Raskin passing away (cancer). Jeff Raskin pioneered the Macintosh. It's a sad day indeed.
http://apple.slashdot.org/article.pl?sid=05/02/27/1835231&tid=3
In any case, I am anxious for tiger too....and even this 10.3.9....one thing I have noticed is the Mac does not seem to degrade the WiFi signal properly. If there's not enough signal for a full 72 Mbps connection, it just dies....in fact, as of late, I have had to bounce my switch to get the damn thing to connect again. Thats the only device on the network affected. My PDA and work laptop are just peachy.
http://apple.slashdot.org/article.pl?sid=05/02/27/1835231&tid=3
In any case, I am anxious for tiger too....and even this 10.3.9....one thing I have noticed is the Mac does not seem to degrade the WiFi signal properly. If there's not enough signal for a full 72 Mbps connection, it just dies....in fact, as of late, I have had to bounce my switch to get the damn thing to connect again. Thats the only device on the network affected. My PDA and work laptop are just peachy.
Macrumors said:
Maybe they will finally fix the dang network device driver in this update....
The current one has been broken forever. It has vlan tag queing problems(causes networking to go to sleep)and has problems with jumbo frames...
I guess we can always hope....
i agree. there have been (i think) 2 updates since they started seeding 1.3 to developers, and i was so anxious to get my hands on it. firefox has been killing safari with its page rendering speed. but i can't stand using it compared to safari's interface. camino is good too, but i still always go back to safari whenever i want to do some rumor browsing. it almost feels as though apple is going to make us pay for safari 1.3 with tiger's safari 2.0.Damien said:
i've also still had problems with screensavers on my powerbook even with 10.3.8. it simply goes into a screensaver fade out and never comes back till i do a hard power off. display sleeping is my only option. 
Where did all the nerds go?
Obviously, I will win the geeky award by pointing out that hexadecimal numbering is the way Apple will release the tenth installment of 10.3... so,
10.3 (they never put the 0)
10.3.1
10.3.2
10.3.3
10.3.4
10.3.5
10.3.6
10.3.7
10.3.8
10.3.9
10.3.A
10.3.B
10.3.C
(of course, I have not forgotten that it starts with a base 10 version of "10", but OS A.3 would not have sounded as cool as OS 10.3)
Obviously, I will win the geeky award by pointing out that hexadecimal numbering is the way Apple will release the tenth installment of 10.3... so,
10.3 (they never put the 0)
10.3.1
10.3.2
10.3.3
10.3.4
10.3.5
10.3.6
10.3.7
10.3.8
10.3.9
10.3.A
10.3.B
10.3.C
(of course, I have not forgotten that it starts with a base 10 version of "10", but OS A.3 would not have sounded as cool as OS 10.3)
Stella said:
Actually I am very glad they are still fixing bugs for 10.3 because their are still plenty to fix.
While most people wont even notice them but in my case there are some that have been very debilitating. Namely we were having tons of kernel panics on our servers until we got 10.3.7 and a custom ethernet driver.
There is still a very nagging kernel problem where the kvm reads bad address. You can see an example of this by doing a netstat -rn which will finish with a seg fault error.
There is a bug with NFS where sometimes files and directories just disapear(They are still there but you cant access them over the NFS mount)
Then if you copy or create them a second time they will show up)
Or if you delete them... and they are really deleted... then they will show up with ls
I could make a very long list of unresolved problems with Panther
So for me I would be very disapointed if they were not still fixing bugs and making updates.
Xapplimatic said:Obviously, I will win the geeky award by pointing out that hexadecimal numbering is the way Apple will release the tenth installment of 10.3... so,
10.3 (they never put the 0)
10.3.1
10.3.2
10.3.3
10.3.4
10.3.5
10.3.6
10.3.7
10.3.8
10.3.9
10.3.A
10.3.B
10.3.C
(of course, I have not forgotten that it starts with a base 10 version of "10", but OS A.3 would not have sounded as cool as OS 10.3)
They will be the only ones who do it that way then....
Because everyone else would increment 10.3.9 ... 10.3.10....10.3.11 etc
~loserman~ said:
Who is everyone else? I don't think anyone would have thought that there would be so many updates to Panther when it was released.
Version numbers not decimal (or hexadecimal)
This has to be the last release before Tiger because version numbers are stored in binary-coded decimal (BCD) format.
http://developer.apple.com/technotes/tn/tn1132.html
The version number of this release would be 0x1039.
The high byte for the Major version = 10.
The high nibble of the lower byte for the minor version = 3.
The low nibble of the lower byte for the bug fix = 9.
For Apple to break this and go hexadecimal with a release of 0x103A or 0x103B would break any application that was checking the system version for the last 21 years.
Do I win the geek award?
--Sebastian
This has to be the last release before Tiger because version numbers are stored in binary-coded decimal (BCD) format.
http://developer.apple.com/technotes/tn/tn1132.html
The version number of this release would be 0x1039.
The high byte for the Major version = 10.
The high nibble of the lower byte for the minor version = 3.
The low nibble of the lower byte for the bug fix = 9.
For Apple to break this and go hexadecimal with a release of 0x103A or 0x103B would break any application that was checking the system version for the last 21 years.
Do I win the geek award?
--Sebastian
jared_kipe said:
Well lets see...
SGI increments IRIX the way I said
IBM increments AIX that way
HP increments HP-UX that way
LINUX increments the kernel that way
BSD increments that way.
SUN increments Solaris that way.
Heck Even Microsoft increments Windows that way
So like I said everyone
I've had that problem for a year with every update
I have had the problem where my 12" Powerbook does not find my D-Link Wireless G Router upon waking from sleep with every iteration of 10.3.x. I have to turn Airport off and wait for 5-10 seconds and then turn it back on before it reconnects. This doesn't happen all of the time - just some of the time. It is the only major problem I've had.
My other big complaint with 10.3.x on all machines I have (that 10.2. x and 10.1.x didn't have) Is that quicktime move previews in the finder no longer play sound, and the video is choppy. I have >> 1 Gigabyte RAM and no crashes of any kind with any software. It just seems like the preview and sometimes even Quicktime playback sucks since going to 10.3 (clean install, and new machines using MANY different files, all of which did work consistently on 10.2.x.
Mitthrawnuruodo said:
I have had the problem where my 12" Powerbook does not find my D-Link Wireless G Router upon waking from sleep with every iteration of 10.3.x. I have to turn Airport off and wait for 5-10 seconds and then turn it back on before it reconnects. This doesn't happen all of the time - just some of the time. It is the only major problem I've had.
My other big complaint with 10.3.x on all machines I have (that 10.2. x and 10.1.x didn't have) Is that quicktime move previews in the finder no longer play sound, and the video is choppy. I have >> 1 Gigabyte RAM and no crashes of any kind with any software. It just seems like the preview and sometimes even Quicktime playback sucks since going to 10.3 (clean install, and new machines using MANY different files, all of which did work consistently on 10.2.x.
Jeffsters said:Duh! You're all wrong! It's like Star Trek!
10.3.9-A
10.3.9-B
10.3.9-C
10.3.9-D
10.3.9-E
etc...
seriously, 10.3.A 10.3.B wouldn't be that bad. at least we get 26 updates (which would never happen) without having this conversation.
pubwvj said:
I do have to agree with you.
We have had a lot of bugs with 10.3 Server....
Very many things are just plain janky.
Apple has been telling us in several cases that the fixes for those things will be in 10.4 server...
Which to me is a copout....
When we identify bugs with a current OS those bugs should be fixed in the current OS...
As for 10.4 .... I'm willing to bet it wont be stable enough for us until at least 10.4.5 or 10.4.6 maybe even later...
That is if 10.3 is used as an example, because we were having more than 25 kernel panics a day on our 1835 xserves until 10.3.7(plus a new ethernet driver)
We have been testing every seeded release of the beta and it is very very very unstable so far.
Glad to see that Apple is acting like a real software company-- new releases mean new features, not the promise of fixing old ones. If what you've already released isn't living up to it's promise (and many users would prefer getting access to features before the product is perfect), keep working on it until it does.
Drives me nuts when every new Windows release lists "improved stability" as a headline feature. NO! Maybe if you made the last version work, I'd be willing to shell out for a new version-- but a company shouldn't be encouraged to write flakey software by rewarding them with more revenue to fix what you've already bought.
An OS is an incredibly complicated piece of software, especially when you start rolling in non-OS features like web browsers and DVD players and IM clients. I don't expect that any company will ever "finish" a release, but I do expect them to put in a good effort. The fact that Apple still has resources finalizing the last revision this close to Tiger coming out says a lot about the company.
Drives me nuts when every new Windows release lists "improved stability" as a headline feature. NO! Maybe if you made the last version work, I'd be willing to shell out for a new version-- but a company shouldn't be encouraged to write flakey software by rewarding them with more revenue to fix what you've already bought.
An OS is an incredibly complicated piece of software, especially when you start rolling in non-OS features like web browsers and DVD players and IM clients. I don't expect that any company will ever "finish" a release, but I do expect them to put in a good effort. The fact that Apple still has resources finalizing the last revision this close to Tiger coming out says a lot about the company.
pot - kettle: black
That's funny, since "improved stability" is listed multiple times on every Apple release....
Analog Kid said:
That's funny, since "improved stability" is listed multiple times on every Apple release....