OS X 10.3.7 Development Underway?

[Chupa Chupa]

The FW bug only affected enclosures with the Initio chip. If your enclosure uses the Oxford chip you should be fine. If you have the Initio you need to update the firmware on a non 10.3.5 machine.

That said I can't wait to see what 10.3.7 breaks.

 

[cb911]

well... updates are always good... and this is good news as well... it means they're not holding out on new features or updated features for 10.4. by releasing this update now, they're pretty much guaranteeing that 10.4 will be even more kick-ass than this.

about the FW bug - i don't know what you guys are talking about? 10.3.6 actaully fixed one slight problem i had with an external HD. perhaps you just need a re-install or something?

Safari bugs? such as? i just run a tight system i guess.

 

[maya]

Hey- They should stop development and start FIXING The previous problems with firewire and with safari, before even persuing any advanced features. What use is new features and small updates if all the other stuff is broken and not working properly??

Any why is 10.3.6 Causing more firewire problems??

Those guys over there at apple should stop tinkering around with set standards and use stuff that works so they should not pissoff their users.

And why the hell is G5's burning up hubs for??!! geez, Stop Tinkering! Obey the standards! I've stopped upgrading so all my previous work on my HD's are not in jeopardy of being corrupted.

Notice to all-- read,read,read before upgrading to the next update, or else you might lose out on precious data!!!!!

ROTF.....

I believe the programmers at apple need to SLEEP and not keep awake by drinking pop and coffee. maybe once they have had a good night rest they mind and fingers will co-function and fix what was broken and not rebuild something that was already fixed.

 

[maya]

The FW bug only affected enclosures with the Initio chip. If your enclosure uses the Oxford chip you should be fine. If you have the Initio you need to update the firmware on a non 10.3.5 machine.

That said I can't wait to see what 10.3.7 breaks.

Checked the LaCie site that firmware update is for the big, bigger, and so on disks with the FW 400 and 800 ports.

I have the d2 FW 400 (thing is riddled with problems) <-- LaCie is not going to see anymore of my money anymore

 

[maya]

well... updates are always good... and this is good news as well... it means they're not holding out on new features or updated features for 10.4. by releasing this update now, they're pretty much guaranteeing that 10.4 will be even more kick-ass than this.

about the FW bug - i don't know what you guys are talking about? 10.3.6 actaully fixed one slight problem i had with an external HD. perhaps you just need a re-install or something?

Safari bugs? such as? i just run a tight system i guess.

Panther has never really played nice with external FW HDD since its release. I hope Tiger takes care of this issue its rather important considering many mac people work with video and images and the external is a great device to move a lot of data from point A to B fast without burning optical.

 

[wrldwzrd89]

You do know you can fill in the track info on the CD first, then rip the CD right? And you can even submit the tracks to the CDDB database so that others like you won't have to face that problem in the future .

Regarding point 1, yes I knew about that - but it makes no difference in the end. The end result is a tagged Apple Lossless file, whichever order you do it in.
Regarding point 2, um...they aren't from CD anyway, so CDDB is going to be of no use whatsoever. It's video game music (or VGM for short) that I'm converting from its original format (SPC, PSF, etc.) to WAV, then converting the WAV to Apple Lossless before tagging it using the information inside the SPC/PSF/etc. If there aren't any tags, I tag them myself.

 

[Rincewind42]

Regarding point 1, yes I knew about that - but it makes no difference in the end. The end result is a tagged Apple Lossless file, whichever order you do it in.
Regarding point 2, um...they aren't from CD anyway, so CDDB is going to be of no use whatsoever. It's video game music (or VGM for short) that I'm converting from its original format (SPC, PSF, etc.) to WAV, then converting the WAV to Apple Lossless before tagging it using the information inside the SPC/PSF/etc. If there aren't any tags, I tag them myself.

What program are you using to rip them? I've been out of that scene for way too long, so I don't know what Mac programs would be useful for that anymore. Personally, I've been spending bits and pieces of time here and there trying to get at least SPC & NSF into an audio decoder...

 

[wrldwzrd89]

What program are you using to rip them? I've been out of that scene for way too long, so I don't know what Mac programs would be useful for that anymore. Personally, I've been spending bits and pieces of time here and there trying to get at least SPC & NSF into an audio decoder...

Mac? Forget about it. Winamp (for Windows) is the ONLY way to go - Audio Overload just doesn't cut it here. That's why I have a Windows machine too (see my website - link in my signature).

 

[ClimbingTheLog]

Oxford 911/922 Data Loss

If your enclosure uses the Oxford chip you should be fine.

I thought so too, until I read this on AppleInsider:

Although there have been wide-spread reports that the recently released Mac OS X 10.3.6 Update has re-introduced data loss bugs for users with external Firewire drives, the Mac OS X 10.3.7 Update shows no signs of an immediate fix. Withal, Apple is reportedly working on a solution to this problem, which appears to be affecting FireWire drives based on the Oxford 922 and 911 chipsets.

You wouldn't guess that Apple invented the bloody standard. I'm using my drives in USB2 mode now. I think Apple's lead Firewire Driver developer got fired between Jaguar and Panther. Maybe when they acquired Zayante.

 

[maya]

I thought so too, until I read this on AppleInsider:


You wouldn't guess that Apple invented the bloody standard. I'm using my drives in USB2 mode now. I think Apple's lead Firewire Driver developer got fired between Jaguar and Panther. Maybe when they acquired Zayante.

I was using the OXFORD 911 chip and still failed. Dam you FW developer at Apple, obtain some knowledge about FW

 

[Rincewind42]

Mac? Forget about it. Winamp (for Windows) is the ONLY way to go - Audio Overload just doesn't cut it here. That's why I have a Windows machine too (see my website - link in my signature).

Pretty much what I figured... guess my (increadibly slow) efforts haven't been going to waste then!

 

[Fukui]

I thought so too, until I read this on AppleInsider:


You wouldn't guess that Apple invented the bloody standard. I'm using my drives in USB2 mode now. I think Apple's lead Firewire Driver developer got fired between Jaguar and Panther. Maybe when they acquired Zayante.

Actually, 10.3 drivers actually just exploit a bug in the Firmware. Thats why they say "to prevent data loss, upgrade to the newest firmware." Thats also why they point the finger at apple, and apple points the finger at them...

 

[ClimbingTheLog]

Actually, 10.3 drivers actually just exploit a bug in the Firmware. Thats why they say "to prevent data loss, upgrade to the newest firmware." Thats also why they point the finger at apple, and apple points the finger at them...

That's a fine excuse for 10.3.0 - I understand and almost accept it.

But to reintroduce the problem in 10.3.6? Do they have a QA lab? You'd think they'd have a test for the #1 complaint with the particular OS and catch these things before shipping.

 

[kettle]

Firmware development

Is there anything that points towards extra cost in developing firmware to cover the full feature set of Firewire?

For example, would it just be cheaper to manufacture drives that just work rather than comply to the ip over Firewire feature set.

Is there an over lap as to how compatible drives would be if they respected the entire Firewire standard?

 

[Mac-Xpert]

You wouldn't guess that Apple invented the bloody standard. I'm using my drives in USB2 mode now. I think Apple's lead Firewire Driver developer got fired between Jaguar and Panther. Maybe when they acquired Zayante.

So does this mean that in the current build of Tiger the same firewire problem exits as well?

Are there any developers with a recent build of Tiger that could confirm the existence of this bug in Tiger or if it was fixed?

 

[hayesk]

Makes you wonder if there could ever be an update where they say, "All is fixed all is well" and never update again. It seems to me that no matter how hard they try there are bugs old or new. If they could get it completely right that would make me happy. (I know a bit to idealistic but still something to wish for).

How many years would you wait for an OS update then? It would take years, and then they would still find bugs because Apple can never test under all circumstances.

In short, it's impossible - software has become too complex to expect no bugs at all.

 

[lssmit02]

Can you describe the memory leak...

Actually, considering the memory leak I've seen since 10.3.6, I could not recommend it.

What do you mean exactly? I ask, because I noticed a weird memory situation after my upgrade to 10.3.6: my used memory creeps up over time, and does not go down, even after I exit programs. I have 2 gigs ran on my G5, run folding in the background and nothing else, as far as I know, which should only use up ~350 megs (that's what it's at after a restart). But after a few days, my used memory listed in Activity monitor is running at 1.6 gigs. That doesn't make sense--I though OS X was good at releasing memory when a program is exited.

 

[bousozoku]

What do you mean exactly? I ask, because I noticed a weird memory situation after my upgrade to 10.3.6: my used memory creeps up over time, and does not go down, even after I exit programs. I have 2 gigs ran on my G5, run folding in the background and nothing else, as far as I know, which should only use up ~350 megs (that's what it's at after a restart). But after a few days, my used memory listed in Activity monitor is running at 1.6 gigs. That doesn't make sense--I though OS X was good at releasing memory when a program is exited.

I'm frequently at the limits of my 1.5 GB when normally, I would have only half that much in use. Since this update, I've actually noticed virtual memory accessing the hard drive and the accompanying slowdown.

Mac OS X does not quickly release memory unless there is a vital need from the system. Apple even changed the way Mac OS 9 cached applications to provide a quicker startup all but the first time. Unfortunately, with this update, they've tried to speedup application launch the first time and they succeeded in producing a system that doesn't purge the virtual memory cache soon enough. While I'd like to set a flag saying which applications I use most to determine what stays in the cache longest, I suppose it's impractical to give any user that control.

 

[fatbarstard]

werid things in 10.3.6

Never had a problem with an update until now... it buggered up my printer drivers - so had to do celan intsall of all of them...

The system logs me out after 30 minutes of no use - kills everything - no matter what the power and screen saver settings are - and it resets the screen saver setting to zero... mightly miffed at this as it is screwing up my folding@home stuff....

Apple - this update sucks. Its no wonder that 10.3.7 has appeared so quickly - to fix all the bugs introduced in 10.3.6 - I hope someone got fired for this....

 

[wrldwzrd89]

What do you mean exactly? I ask, because I noticed a weird memory situation after my upgrade to 10.3.6: my used memory creeps up over time, and does not go down, even after I exit programs. I have 2 gigs ran on my G5, run folding in the background and nothing else, as far as I know, which should only use up ~350 megs (that's what it's at after a restart). But after a few days, my used memory listed in Activity monitor is running at 1.6 gigs. That doesn't make sense--I though OS X was good at releasing memory when a program is exited.

Mine doesn't do that. I watched it for a while, and while stuff was running it crept up slowly, but once I quit some apps the free memory jumped quite a bit higher. All seems normal here. I've had no other troubles with 10.3.6 either.

 

[wdlove]

Never had a problem with an update until now... it buggered up my printer drivers - so had to do clean install of all of them...

Apple - this update sucks. Its no wonder that 10.3.7 has appeared so quickly - to fix all the bugs introduced in 10.3.6 - I hope someone got fired for this....

I doubt that anyone got fired, overall its not that serious. Looking at what hayesk had to say rings so true, software has become a complex interrelation so it is very hard to fix all bugs.

 

[FFTT]

I've been jumping around the rumor mills just hoping to catch
some sort of indication of what new hardware we might be seeing
in January. ( OTHER THAN iPods )
What I was hoping to see in the OS updates would be "any" indication
of PM dual core QUADRA support??? <">

 

[UnixMac]

I doubt that anyone got fired, overall its not that serious. Looking at what hayesk had to say rings so true, software has become a complex interrelation so it is very hard to fix all bugs.

It's almost (I stress almost) becoming a bit like the wold of PC and Windows with all of the conflicts.. No wonder Apple likes to keep such tight control over their stuff... quality control.

Frankly.. I think we've gotten to a time with computers being so complicated that on a system like mine (which was basically a supercomputer 5 years ago), it's normal to have at least one or two ongoing problems/issues with the installation of the OS. It's been a while since I've had a completely flawless week on my mac.

I guess if I never added any software (or freeware) it would be easier.

 

[Fukui]

It's almost (I stress almost) becoming a bit like the wold of PC and Windows with all of the conflicts.. No wonder Apple likes to keep such tight control over their stuff... quality control.

Frankly.. I think we've gotten to a time with computers being so complicated that on a system like mine (which was basically a supercomputer 5 years ago), it's normal to have at least one or two ongoing problems/issues with the installation of the OS. It's been a while since I've had a completely flawless week on my mac.

Well, not only that but think about what the OS lives on: a volitile magnetic disk where your not really ever 100% guaranteed that every single bit will be perfectly copied in the first place! So even if apple fixed a bug here or there, you never know what might of happened to your system at the disk level, bad sectors, corrupted data etc... to say nothing about apps that install stuff with the wrong permissions that can screw things up...

 

[UnixMac]

Well, not only that but think about what the OS lives on: a volitile magnetic disk where your not really ever 100% guaranteed that every single bit will be perfectly copied in the first place! So even if apple fixed a bug here or there, you never know what might of happened to your system at the disk level, bad sectors, corrupted data etc... to say nothing about apps that install stuff with the wrong permissions that can screw things up...

frankly it is nothing short of amazing that todays HD's can be so fast, store so much info so accurately... I use Diskwarrior regularly for health of my disk, but guys can go years without any kind of repair and never experience a problem.