Oh i know a hardware problem! I have an iSub and the @!#$% thing never works right anymore (stupid USB-connecting iSub)
I had the Rev A Aluminum PB, and it was sweet. I had to sell it because I live in NYC. IN NYC, sometimes you Gotta choose between selling that PB, or selling that A$$> Maybe I made the wrong choice.Blue Velvet said:Which is what some of us were warning about when it was released... I don't feel at all sorry for those who rushed out, installed it right away and had problems. Cold and heartless perhaps, but that's just the way I feel.
My motto: Never install .0 or buy Rev A of anything.
I'd got further and get rid of that "almost".SiliconAddict said:System crashes are unacceptable. App crashes. Fine. As long as they are limited but the OS should almost NEVER crash.
That's the idea of a microkernel, right? Unfortunately in practice, most microkernels are crap for performance. OSX uses a hybrid micro/modular kernel and it is still said that it takes a huge performance hit for that very reason. The HAL helps to keep apps from making a wrong call directly to hardware (if the app developer decided to code to the HAL, and not some unpublished kernel API), but really has nothing to do with a badly written driver.shamino said:Given how much modern operating systems depend on things like hardware abstraction layers and virtual machines and microkernels, it should be possible for an OS to trap a crashed driver and remove or restart it.
Considering how much CPU power everybody wastes on eye candy, I would find it hard to believe that this is at all a factor.jim. said:That's the idea of a microkernel, right? Unfortunately in practice, most microkernels are crap for performance. OSX uses a hybrid micro/modular kernel and it is still said that it takes a huge performance hit for that very reason.
Moore's law. CPUs are always getting faster. If performance takes too much of a hit now, it will be just fine in a few months.jim. said:I don't know if we can have properly jailed drivers and still expect a lean, quick OS. At least, I don't think we can expect this yet...
One would think, but the microkernel design has been plagued by this performance problem on desktops for nearly 20 years. I think it is easy to have a redundant, and nearly crash proof kernel if your specifications for use are clearly outlined (Embedded systems, for example). Part of the problem with desktop use is, for every advancement in hardware, there is a corresponding change in paradigm as to what should be done on a computer. There is no one set use, and these new programs and hardware need to perform hacks directly on the kernel, or in hardware, sometimes to perform desired functions.shamino said:Considering how much CPU power everybody wastes on eye candy, I would find it hard to believe that this is at all a factor.
I'd much rather give up all the gratuitous GUI effects and have a crash-proof kernel. I'm sure apps would end up at about the same speed they run at now.
Moore's law. CPUs are always getting faster. If performance takes too much of a hit now, it will be just fine in a few months.
Microsoft uses this logic to justify the ever-increasing amount of bloatware in their OS and applications. Ditto for a lot of the popular games.
So why can't this argument be used to make a kernel change that will make systems virtually crash-proof?
I can only assume that people just don't care all that much for stability, no matter what they tell themselves.
shamino said:Moore's law. CPUs are always getting faster. If performance takes too much of a hit now, it will be just fine in a few months.
mynameisjesse said:i truely think that how tiger is right now is up there with windows xp. i have atleast 1 problem a day that makes me have to reboot. my friend who just bought a 17" g5 imac cant even use tiger because the whole system will freeze after a few minutes of use. i have more friends that have tried tiger and went back to panther because of all the problems. honestly, i thought i moved to apple to get away from this. without stability os x is just a pretty looking operating system.
SiliconAddict said:System crashes are unacceptable. App crashes. Fine. As long as they are limited but the OS should almost NEVER crash. I'm sorry but at least MS has somewhat of an excuse considering how much hardware they have to support.
Apple rolls their own hardware and OS. There is zero excuse for a kernal panic IMHO. No application should be able to get that close to the OS to cause a system to tank and if it isn't the software then its the OS itself and well...No excuses. Flame me all you want but I call it like I read it.
I really think its time that Apple starts seriously considering a public beta program where they give out time expired copies of their next OS to general users. Let the developer copies out way early but 6 months before an OS is released blow, say 12,000 copies out to the average user. OK prob no so average user since who in their right mind runs beta software other then geeks. *shrugs* Its a thought.
A microkernel is not a problem, but a kind of system design.bernardb said:I don't understand what these "microkernal" problems are and whatnot you tech experts are talking about.
MacsRgr8 said:This question has been asked before:
Have those people with big issues running Tiger done an upgrade from Panther, or an "erase 'n install"?
wdlove said:Is anyone aware of any updated information about 10.4.3? Does early October seem possible for a release?
AppleMatt said: