xristy
Jun 6, 2008, 08:23 PM
I know that often people write in that have problems and usually don't write in when all is going swimmingly. I have generally a high tolerance for the occasional software defect in any product including Mac OS X 10.x; however, I am really pretty much ready to throw a beautifully engineered SR MacBook Pro out the window.
I am running 10.5.3 and have gotten absolutely no relief what-so-ever for a variety of problems any one of which an arbitrary user might run across but all of which afflict me and with one exception have been around since 10.5.0:
1) Bluetooth GSM/EDGE cell phone as modem support - the dreaded "connecting" or "disconnecting" forever that can't be cleared except by a reboot.
2) USB dial-up modem freezing the computer - for some only on the usb port nearest the power port; for others the farthest one; for others either one.
3) Bluetooth access to Nokia N73 - works on "older" firmware but since 10.5 the iSync fails on N73s with firmware from September 2007.
These are all problems that have been there since 10.5.0 and haven't gotten fixed as of 10.5.3 some may have changed complexion somewhat but it's hard to tell.
I hesitate to mention the next one because as far as I know it's actually an OS X Server problem:
4) sshd instances will go into some sort of loop that consumes as much CPU as you can throw at them. As people log in (if they can at all since the sshd goes autistic during the login procedure itself) more and more of these hung sshd processes consume more and more server cpu cycles.
Now except for 3) the other problems are quite generic and I included 3) because I am bitten by it and it is a communication problem.
My question is whether there is something generally wrong with Apple's ability to deliver and support the core functionality of Mac OS X??
I like Spaces and Time Machine and most everything Mac but I don't like what to me are basic communication functions not working.
On the whole everything above works flawlessly under 10.4:
1) no problem
2) no problem
3) latest N73 F/W works great with iSync
4) sshd solid as a rock - like it should be on a *nix-like platform
I can "rationalize" that:
1) isn't where Apple wants things going since they don't even support iPhone as a GSM/EDGE modem for Mac OS X :cool:
2) who cares about dial-up any way unless you're out in the boondocks of most of the planet where dial-up is actually the only meaningful way of getting on the internet. I know that most tech saavy people live in modern cities but most of the planet doesn't
3) I don't have the slightest idea what the bluetooth advances are that Apple engineering is upto in 10.5 versus whatever ideas Nokia is up to so I guess that's a gimme as just an unfortunate interface glitch between two behemoth corporations engineering staffs who don't really care much about each others products in all likelihood :confused:
4) Apple Remote Desktop and WEB DAV are obviously the only way that anyone should ever interact with a server ;)
As I say, I am generally not one to complain but there seems to be a trend in a really bad direction since 10.5 and I don't see it getting covered in the tech press.
X
I am running 10.5.3 and have gotten absolutely no relief what-so-ever for a variety of problems any one of which an arbitrary user might run across but all of which afflict me and with one exception have been around since 10.5.0:
1) Bluetooth GSM/EDGE cell phone as modem support - the dreaded "connecting" or "disconnecting" forever that can't be cleared except by a reboot.
2) USB dial-up modem freezing the computer - for some only on the usb port nearest the power port; for others the farthest one; for others either one.
3) Bluetooth access to Nokia N73 - works on "older" firmware but since 10.5 the iSync fails on N73s with firmware from September 2007.
These are all problems that have been there since 10.5.0 and haven't gotten fixed as of 10.5.3 some may have changed complexion somewhat but it's hard to tell.
I hesitate to mention the next one because as far as I know it's actually an OS X Server problem:
4) sshd instances will go into some sort of loop that consumes as much CPU as you can throw at them. As people log in (if they can at all since the sshd goes autistic during the login procedure itself) more and more of these hung sshd processes consume more and more server cpu cycles.
Now except for 3) the other problems are quite generic and I included 3) because I am bitten by it and it is a communication problem.
My question is whether there is something generally wrong with Apple's ability to deliver and support the core functionality of Mac OS X??
I like Spaces and Time Machine and most everything Mac but I don't like what to me are basic communication functions not working.
On the whole everything above works flawlessly under 10.4:
1) no problem
2) no problem
3) latest N73 F/W works great with iSync
4) sshd solid as a rock - like it should be on a *nix-like platform
I can "rationalize" that:
1) isn't where Apple wants things going since they don't even support iPhone as a GSM/EDGE modem for Mac OS X :cool:
2) who cares about dial-up any way unless you're out in the boondocks of most of the planet where dial-up is actually the only meaningful way of getting on the internet. I know that most tech saavy people live in modern cities but most of the planet doesn't
3) I don't have the slightest idea what the bluetooth advances are that Apple engineering is upto in 10.5 versus whatever ideas Nokia is up to so I guess that's a gimme as just an unfortunate interface glitch between two behemoth corporations engineering staffs who don't really care much about each others products in all likelihood :confused:
4) Apple Remote Desktop and WEB DAV are obviously the only way that anyone should ever interact with a server ;)
As I say, I am generally not one to complain but there seems to be a trend in a really bad direction since 10.5 and I don't see it getting covered in the tech press.
X
