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.5.2 Not Quite Ready Yet (9C30 Seeded)
- Thread starter MacRumors
- Start date
- Sort by reaction score
"It just works" has been accurate for me.
Any system as complex as a computer can have issues. To expect Apple to create perfectly flawless products is stupid.
My MBP has been 98% flawless, at least as far as how I use it. So for me, "It just works" rings true enough.
For those with wireless dropouts, if you're using an Airport base station, then yes, Apple should have fixed it quickly. If you're using a 3rd party wireless router like I am, then the problem could be with either end. I lucked out and am thankful.
Any system as complex as a computer can have issues. To expect Apple to create perfectly flawless products is stupid.
My MBP has been 98% flawless, at least as far as how I use it. So for me, "It just works" rings true enough.
For those with wireless dropouts, if you're using an Airport base station, then yes, Apple should have fixed it quickly. If you're using a 3rd party wireless router like I am, then the problem could be with either end. I lucked out and am thankful.
When I got my 12" PB in November 2005 I was in awe of the build quality. And, being a "switcher" at that time I was also very impressed with Tiger.
Leopard did make the PB seem a bit "snappier", but I've had problems I never had with Tiger. The biggest problems are Mail and Airport. Mail sometimes has a mind of its own. The wireless is definitely a Leopard problem. I run a third-party router (D-Link DGL-4300) and I NEVER had problems connecting to my network. It is configured with WPA2, MAC address filtering, and a non-broadcast SSID. It's always been configured as such. With Leopard, upon waking from sleep my PB frequently reports that my wireless nework cannot be found, and would I like to join a different one. And every time this has happened, the PB was located no more than 12 feet from the wireless router.
Leopard somehow (at least on my PB) has trouble re-connecting to a network with a non-broadcast SSID. As an interim fix, I had to enable the SSID broadcast (after much troubleshooting), but that's unacceptable to me. I like having a three-tiered security layer on my wireless router (MAC address filter, SSID, and WPA2). On Tiger, I NEVER had a problem. From the day I brought it home and gave it the SSID and password, I never ever had trouble connecting.
Count me in among thousands who are disappointed with certain underpinnings of Leopard and hoping that 10.5.2 rises Leopard above the perceived status of "RC-2".
Leopard did make the PB seem a bit "snappier", but I've had problems I never had with Tiger. The biggest problems are Mail and Airport. Mail sometimes has a mind of its own. The wireless is definitely a Leopard problem. I run a third-party router (D-Link DGL-4300) and I NEVER had problems connecting to my network. It is configured with WPA2, MAC address filtering, and a non-broadcast SSID. It's always been configured as such. With Leopard, upon waking from sleep my PB frequently reports that my wireless nework cannot be found, and would I like to join a different one. And every time this has happened, the PB was located no more than 12 feet from the wireless router.
Leopard somehow (at least on my PB) has trouble re-connecting to a network with a non-broadcast SSID. As an interim fix, I had to enable the SSID broadcast (after much troubleshooting), but that's unacceptable to me. I like having a three-tiered security layer on my wireless router (MAC address filter, SSID, and WPA2). On Tiger, I NEVER had a problem. From the day I brought it home and gave it the SSID and password, I never ever had trouble connecting.
Count me in among thousands who are disappointed with certain underpinnings of Leopard and hoping that 10.5.2 rises Leopard above the perceived status of "RC-2".
not sure
after reading some of the quotes I feel anoyed at some of the comments that people make about how long or not apple are taking to produce a highly detail piece of software being a patch or whole program as we are yet to find out in 10.5.2
my personal opinion, and thats all it is, if you can do better then please do so, if not stop telling one of the top IT companies on this little planet of ours that they should hurry up.
At least they keep us people informed that there is some progress going on if you happen to look at the developer site, not like many others
http://developer.apple.com/leopard/devcenter/
Mark
after reading some of the quotes I feel anoyed at some of the comments that people make about how long or not apple are taking to produce a highly detail piece of software being a patch or whole program as we are yet to find out in 10.5.2
my personal opinion, and thats all it is, if you can do better then please do so, if not stop telling one of the top IT companies on this little planet of ours that they should hurry up.
At least they keep us people informed that there is some progress going on if you happen to look at the developer site, not like many others
http://developer.apple.com/leopard/devcenter/
Mark
<Sarcasm>
I'm not seeing where they say they will release CoreImage with D300/D3 support. Also, I don't see a list of bugs they are working on.
</Sarcasm>
I'm sorry if we complain, but Apple wouldn't let us complain this much on their web site. Also, some of us bought into Apple as a vendor of choice. Apple hasn't always lived up to the potential that it could. We feel cheated by the iPhone/iTouch/MBA, not that they aren't great products. We just feel they took resources from our problems, after they took our money. From a professional stand point, Apple still needs some work. Releasing 10.5.2 would be a good start.
P6
But Tiger was already at 10.4.3 when you bought your PowerBook.
Some people started using Tiger when it had already been out for a while and gone through a number of updates, and they're now using an early version of Leopard and expecting the same stability.
Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 6.9) VZW:SCH-i760 PPC 240x320)
Yes, but I've got the the safer bet.
If even one person reports a problem with 10.5.2 - then it's not "flawless" and you look like a silly fanboi.
Sure, but whiny anti-fanboy complaints don't count, ok?
I'm wondering if there will be another build before being released to the general public, bearing in mind that Apple states the absence of "known issues" with the last builds seeded to developers.
With 9 areas of testing at the moment I think there will be another 2 if not 3 builds before going public.
At the earliest I would expect it late next week but more likely the following week. But then again I am rubbish with predictions.
True, it was at 10.4.3 and it was the "last" revision 12" Powerbook. However, through 10.4.3 - 10.4.11 I never had one single issue with the wireless connection.
With Leopard, wireless performance (or connection ability in my example) regressed. One would not expect a regression in this area, especially if the point of Leopard was to "improve upon Tiger".
Let's not forget that, along with the Leopard wireless problem, 10.5.0 shipped with the firewall in the "off" position, and in my and MANY others' opinion, severely downgraded the firewall from what was in Tiger.
But I do acknowledge your point that my purchased PB was ahead of the game with 10.4.3.
Here's hoping that 10.5.2 shows a marked improvement in Leopard. With the six extra months they had to finish Leopard (stupid iPhone), let's hope Leopard receives a well-deserved course-correction.
We are a tough audience to please, but that's good !
One thing has become clear from Apple forums: Apple product users expect good products, and that's a good thing !
Windows users feel like "Can I have some more soup, please sir?"
One thing has become clear from Apple forums: Apple product users expect good products, and that's a good thing !
Windows users feel like "Can I have some more soup, please sir?"
... but it's ok for Apple to criticise Microsoft about releasing things slowly and not fixing issues.
I can't make an OS, but Apple claims to have "The Most Advanced Operating System in the world" and backs that up with near-childish jibes at other companies.
As such, they deserve to have a critical eye on them from their customers.
If I claimed to have such a wonderful product and had the sun shining out of my a** I'd work extra hard to prove that.
"All" the key issues being addressed is known only to Apple and Dev seeds.
At least that's the way it's supposed to be.
During the MacWorld SF, Apple has quietly seeded to developers a new build of the Mac OS X Leopard 10.5.2 update numbered 9C16. The seed-note lists an endless list of enhancements in almost any part of the system.
According to the seed-note, the update "focuses" (if we may call this focusing) on, Active Directory/Directory Services, AirPort, AppKit, Application, Firewall, Audio, Automator, Back To My Mac, Chinese Input Methods, CoreData, CoreFoundation, Dashboard Widgets, Data Detectors, Directory Services, Dock, Finder, Foundation, Grammar Checking, Graphics Drivers, High Level Toolbox, iCal, iChat, iDisk, Keyboard Layouts, Mail, Networking, Parental Controls, Podcast Producer, Printing/CUPS, Quick Look, Rosetta, Safari, SMB, Spotlight, SQLite, Terminal, Time Machine, X11.
New issues fixed in this seed, as listed on the seed-note, are the following:
- Border now draws correctly when 2-up printing
- Preview Image and scrolling horizontally with keys
- CFNetwork and Proxy error messages
- NTFS Volume and System UIServer fix
- DVDPlayback and second display hookup
- Preview PDF and Mail Document fix
- Resolved tabbing issue with PDFView
- Fixed issue with Time Machine Preferences
- Icon Services and file attachments
- Time Machine and resumed backups
- Images captured in tethered mode fixed
- CoreAudio Toolbox and EstAudioFileRead
- ImageCapture and file creation
- SharedFileLists and SMB guest issue resolved
- BackupCore and backup preparation
- Japanese localization and CUPS
- NSTextView and scroll bar thumb scrolling direction
- SMB File Server and name resolving order
- CFNetwork and Windows proxy ISA server fix
- Fixed deinterlacing issue with DVDPlayback
In previous seeds, the following fixes had been made:
- CoreData Framework and NSFetchRequest
- AD DS Plug-in
- HLTB Menus
- Memory leak with Rosetta
- X11.app and customized menu commands
- AirPort shared printer fix
- Disk Utility and FAT32
- HFS and allocated space
- Fix to Process Manager and VISE
- NSNavigationServices and NavServices from a Cocoa application fix
- Reprinting Hold jobs and CUPS
- Fixed issue with Text Input Sources
- Mail Message Body Display issues with certain font types
- DAVKit and iCal redirects
- Calendar Store Framework and CalRecurrenceRule fix
- CoreText Font and PUA unicode characters now work correctly
- rsh jobs no longer waits for backgrounded processes to complete
- Fixed issue HLTB and Finder
- Fixed issue with AppleEvents
- ImageIO preiew issue in Finder fixed
- HIClock now accepts user entries
- smb now handles "%" in password field
- Fixed issue with CUPS and reverse page ordering
- NSTableView and special keys now works correctly
- AF_UNSPEC& null address Networking issue fixed
- Resolved issue with Xquartz and CPU cycles
- Fixed exception issue with KeyChainAccess
- Quartz Composer no longer brings up an error when saving a composition
- Fixed ScreenCapture issue
- Addressed issue with Web Content Filter and Parental Controls
- CUPS no longer prints a blank page when 2-up print setting is selected
- CoreData Framework fix to XML data creation
- Fixed Quick Look plug-in loading issue
- Mail to iCal Data Detectors now work correctly
- Fixed issue with Finder and column view
- Core Audio fix now allows empty m4a files to behave correctly
- Fixed horizontal scroll issue with Finder and Spotlight
- Fixed iChat audio issue with fast user switching
- Core Data apps now save correctly when no document changes have been made
- Fixed issue with Firewall customization settings
- Fixed Active Directory binding issue
- NSTable View -selectAll setting now works correctly
- HLTB Dyhmanic Menus now behave correctly
- Resolved issue with HIImageView
- Fixed issue with ATSCreateFontQueryRunLoopSource
- Mail now treats flags correctly
- Fixed day selection issue with NSDatePicker
- Invalid RR queries problem now resolved
- Input issue with NSTokenField fixed
- Archive & Install problem with Sync Services Translators resolved
- Fixed Spotlight issue with arithmetic expressions
- Fixed problem with Podcast Producer and Wiki running via SSL
- HLTB ApplyTHemeBackground memory leak fixed
- Fixed Numbers printing issue with CoreGraphics
- Fixed permissions problem with NFS
- NSManagedObject now implements dictionaryWithValuesForKeys correctly
- Fixed memory leak in CoreData Framework
- Bitmap-only fonts now work correctly in QuickDraw
- Issue with MusicSequenceSaveSMFData fixed
- SMB File Server reboot issue resolved
- Fixed issue where running a MAC application from a NTFS volume may not work correctly
- NSXMLNSNumberTransformerName now handles NSDecimalNumbers correctly
- Addressed issue with ToDo recurrences and iCal Synchronization
- Issue with NSNavigationServices and kNavCBTerminate resolved
- Fix to AppKit and popup menus
- CTFontCreateCopyWithFamily() now works correctly
- Fixed issue with Tamil IM
- Networking issue with records over sockets fixed
- HIShape symbols in HLTB fixed
- Fixed window flicker issue with PrintManager
- NSArrayController and Lazy Fetching issue resolved
- Save PDF to Web Receipts Folder now works correctly when there's a / in the title
- Fixed issue with "Find Next" and the spelling panel
- Issue with NSTreeController resolved
- Resolved issue with local SOCKS proxy and iChat
- Logged iChats now open quickly
This clearly represents by far the most significant revision update Apple has ever made on any of its operating systems with nearly 40 Applications involved and 100 bugs fixed. The only bad news is that the update weights as much as, hold your breathe... over 400MB, a record size which could even grow further in the final build.
Two known issues only are listed, they are related to Applications default locations updating and hangs during PDF scrolling on certain machines. This is a sign that the update shouldn't take long to arrive through our Software Update utility.
(got this from mac-bb.org)
I agree, little problems here with my C2D iMac, so not sure what others problem is.
I'd like Safari to be a bit more conservative with memory use, but other then that, no problems here.
Oh edit, also Windows shared computers seem to pop in and out of the shared portion of the Finder (despite it being on 24/7)