Kllrnohj wrote:
comicIDIOT wrote:
Regarding the brightness, it does. If you plug it in the brightness bumps up, but I believe that's an option under "Energy Saver" within "System Preferences." Also, it does switch between the two modes. My monitor shuts off after a minute of inactivity when unplugged and the computer itself sleeps after 15. While plugged in, both settings are set to never. It works. Try setting the settings to something other then "Never."
Been there done that. It doesn't work. Plugging/unplugging it in doesn't change the brightness.
How long the display stays on works fine, brightness doesn't though.
Maybe a visual representation will help?
Quote:
Quote:
Then you're using it wrong or you received a defective MBP. I've only experienced a hardlock once or twice since I got my MB in the Summer of 2008.
Ah, yes, when an Apple product misbehaves clearly it's the user's fault.
Quote:
Quote:
You're letting you're negative views limit what you think about the Mac. Regarding hard locks, again, you either have a defective product or you're using your MBP with programs that aren't coded right or just have to many things running and wanting the same resources.
Of course I'm letting my negative views limit what I think, what kind of idiotically pointless statement is that?
Quote:
Also, I *hate* the way AirPort works (or should I say doesn't work). If an AP you have saved becomes available after you've resumed, Windows will connect to it, OS X doesn't. If you are looking at the list of APs and hit refresh, and one you've previously connected to shows up, Windows will connect to it, OS X doesn't. No, OS X instead makes me do that instead. Airport also doesn't always resume correctly.
The bold text above, I'm not getting it. I'm connected to every *available* access point at school, and I've had plenty of cases where I walked from access point to another and OS X was able to connect. Not seamlessly, but it connected to the other after searching for other available and known points.
Quote:
Quote:
What are you doing, and how many background tasks do you have running, when the MBP hard locks?
I have Chrome or Safari running, that is about it. The most demanding thing I'm asking OS X to handle is web surfing. Today I tried to compile the Android source code on it, it promptly locked up because make tried to make like 12 threads. Apparently OS X can't handle that many threads, freaked the hell out, and locked up. Re-running make with -j3 built just fine.
Well, that's your problem. Apparently Chrome creates 36 threads and Make (capitalized, since it's a Proper Noun in this case) requires 12 threads. As far as I understand by what I've been told by you and several others, one core can handle one thread. Hyper-threading allows two threads to run on a single core.
Now, the MBP uses an Intel Core 2 Duo. Which can either be an i5 or i7. Again, as far as I understand the i7 is the only hyper-threading capable of the series so far. So, even if you were to have an i7 in that MBP of yours, you'd only be able to manage 4 threads. So, on Windows you try running 36+ threads through a Dual Core i7 and tell me if Windows doesn't lock up.
Quote:
Nevermind the host of usability issues, like "back" not actually meaning "back" in finder, the maximize button being utterly useless (how the hell did they screw that up?), the window's menu is at the top of the screen (that *IS* a broken and wrong design), you are required to learn a bunch of shortcuts just for basic use (oh, you want to go up a directory? Well, since back is broken and takes you to a random folder instead, you'll need to do apple-shift-up or something retarded like that because a button that takes you up a level would be way too confusing). The more I use OS X, the more I hate it. Which is probably why I barely use it now.
I've never had any issues when using the back button. Besides, why use the back button when you have Column View; which is way more efficient as you can jump back 2 or 3 folders (on the small monitors) at a time, or look at the files in a folder while also viewing the folders/files in that folders parent folder (/Parent/Folder/ & /Parent/, respectively)
I'm sure it's because the cursor is rendered differently than the rest of the screen, mostly because I think I saw on their site that they're trying to find an appropriate fix or workaround. 
