Andrew,
> Also what Jeff just posted about one of hardware, firmware, or OS needing > to change, I personally tend to agree with .. unless there still is an actual > hardware fault that the hardware test is not picking up. This is just a personal experience. Some people who attended the Witango Dev Con last year may remember this, but I received a brand new TiBook G4 667 a few days before I left Australia. The machine had everything I needed installed and running except periodically the machine would reboot by itself, kernel panic (in the middle of a presentation) or simply just not start up. It too passed all the Apple HW tests and norton utilities could not find anything wrong. When I spoke to a few people at the conference they also told me that they had also had to return TiBooks which had exhibited bizarre behaviour, but when I asked Apple they denied any knowledge of it. When I returned to Australia, the Apple repair guys could not find a fault with it with any of their diag tools either. I convinced them to use the machine for several days and finally it started to do its tricks intermittently. They replaced the logic board on my insistence, left my original HD in the machine and it has run fine ever since. If you are on good terms with the local Apple repair shop and they have a spare board, they may swap it over to see if it makes a difference. > though the Apple guy didn't > really right come out and say it, he very much insinuated that the 3rd > party developer would have to figure out how to work around any OS issues. > (or work it out with Apple through developer channels.. but if they're as > much help as he was...) Over a year ago we logged a bug throught the developer channel where we found strftime wasn't thread-safe in 10.2.x. strftime is a STL call to format a time struct into a specified human readable time format. No prize for guessing where this would be used in the server. This is the response we received a week or so ago (over 12 months after it was logged): "Thank you for your bug report against Libc. Our engineering team has tested against your report and they are unable to reproduce the issue with Mac OS X version 10.3, Developer Preview (code name Panther) that was distributed at the Worldwide Developers Conference (WWDC) 2003." This is great news - they have fixed it ... in 10.3. No mention of the fact that we found the problem in 10.2, reported the problem against 10.2 and everyone is running 10.2 and 10.3 will not be available for 6 months. We also received the same types of response when we were logging bugs against 10.1. So even if we did find a bug in the OS, I do not think it will get a high priority, especially now they are working on the 10.3 release, but you might want to test it on 10.3 developer preview to see if it makes a difference. Phil ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
