Since Apple released Mac OS X, even the PC industry trade publications have raved about its quality, design, and features. PC Magazine even gave Mac OS X 'Panther' a 5-star rating in October 2003. Perhaps it was because Macs could now seamlessly fit into the Windows- dominated marketplace and satisfy Mac users refusing to relinquish their trusty systems and corporate IT staffs wanting to cut down on tech support calls. Whatever the reason, Mac OS X has proven itself as a worthy operating system for both consumers and business alike.
To change the display resolution on your Mac, click the Apple menu → click System Preferences → click Display → click the Scaled option → select the resolution or display scaling you want to use. Click the Apple menu. This is located in. Though it's generally recommended to use the ‘Default for display' screen resolution option, Mac users who connect their computer to an external display or TV may find it helpful to be able to see, access, and use all possible display resolutions for a particular screen. This can be particularly useful if a display Mis either showing at. 15 Responses to 'Random green pixels on my Mac display' Joe Says: July 31st, 2008 at 12:18 am. Run a Google search on 'purple pixels'it may be a similar situation and you need to talk to Apple about it. The resolution (in pixels by pixels) of your Mac's display determines how much information you can fit on screen and how sharp the image is, so it's important to know. If you run a full-screen game or application at native resolution, the image will look its best, so here's how to find out what it is.
Of course, as with all operating systems, Mac OS X has had its share of technical problems and even a few major security vulnerabilities. Nearly all were quickly resolved by Apple via a downloaded patch or OS update. But in general, Mac OS X is solid, secure, and perhaps the most trustworthy mainstream computing environment available today. As a result, Mac users are generally immune to the incessant security problems plaguing their Windows counterparts, and that somehow bothers PC Magazine columnist Lance Ulanoff.
In a December 11 column [1] that epitomizes the concept of yellow journalism, he's 'happy' that Mac OS X is vulnerable to a new and quite significant security vulnerability. The article was based on a security advisory by researcher William Carrel regarding a DHCP vulnerability in Mac OS X. Carrel reported the vulnerability to Apple in mid-October and, through responsible disclosure practices, waited for a prolonged period before releasing the exploit information publicly since Apple was slow in responding to Carrel's report (a common problem with all big software vendors.) Accordingly, Lance took this as a green light to launch into a snide tirade about how 'Mac OS is just as vulnerable as Microsoft Windows' while penning paragraph after paragraph saying 'I told you so' and calling anyone who disagrees with him a 'Mac zealot.'
In other words, you're either with him or with the 'zealots.' Where have we seen this narrow-minded extremist view before?
More to the point, his article is replete with factual errors. Had he done his homework instead of rushing to smear the Mac security community and fuel his Windows-based envy, he'd have known that not only did Apple tell Carrel on November 19 that a technical fix for the problem would be released in its December Mac OS X update, but that Apple released easy-to-read guidance (complete with screenshots) for users to mitigate this problem on November 26. Somehow he missed that.
Since he's obviously neither a technologist (despite writing for a technology magazine) nor a security expert, let's examine a few differences between Mac and Windows to see why Macintosh systems are, despite his crowing, whining, and wishing, inherently more secure than Windows systems.
The real security wisdom of Mac OS lies in its internal architecture and how the operating system works and interacts with applications. It's also something Microsoft unfortunately can't accomplish without a complete re-write of the Windows software -- starting with ripping out the bug-riddled Internet Explorer that serves as the Windows version of 'Finder.' (That alone would seriously improve Windows security, methinks.)
At the very least, from the all-important network perspective, unlike Windows, Mac OS X ships with nearly all internet services turned off by default. Place an out-of-the-box Mac OS X installation on a network, and an attacker doesn't have much to target in trying to compromise your system. A default installation of Windows, on the other hand, shows up like a big red bulls-eye on a network with numerous network services enabled and running.* And, unlike Windows, with Mac OS X, there's no hard-to-disable (for average users afraid to tweak things unfamiliar to them, that is) 'Messaging Services' that results in spam-like advertisements coming into the system by way of Windows-based pop-up message boxes. And, the Unix-based Mac OS X system firewall – simple enough protection for most users -- is enabled by default (in Mac OSX Server) and easy to find and configure in Mac OS X Client software (not that there's much that users need to worry about out-of-the-box anyway) -- something that Microsoft only recently realized was a good idea and acknowledged should be done in Windows clients as well. I guess Lance didn't hear about that, either.
Then there's the stuff contributing to what I call 'truly trustworthy computing.'
When I install an application, such as a word processor, I want to know with certainty that it will not modify my system internals. Similarly, when I remove the application, I want to know that when I remove it (by either the uninstaller or manually) it's gone, and nothing of it remains on or has modified my system. Applications installed on Mac OS X don't modify the system internals – the Mac version of the Windows/System directory stays pretty intact. However, install nearly any program in Windows, and chances are it will (for example) place a different .DLL file in the Windows/System directory or even replace existing ones with its own version in what system administrators of earlier Windows versions grudgingly called 'DLL Hell.' Want to remove the application? You've got two choices: completely remove the application (going beyond the software uninstaller to manually remove things like a power user) and risk breaking Windows or remove the application (via the software uninstaller) and let whatever it added or modified in Windows/System to remain, thus presenting you a newly-but-unofficially patched version of your operating system that may cause problems down the road. To make matters worse, Windows patches or updates often re-enable something you've previously turned off or deleted (such as VBScript or Internet Explorer) or reconfigures parts of your system (such as network shares) without your knowledge and potentially places you at risk of other security problems or future downtime. Apparently, Lance doesn't see this as a major security concern.
Further, as seen in recent years, Microsoft used the guise of a critical security fix for its Media Player to forcibly inject controversial Digital Rights Management (DRM) into customer systems.[2] Users were free to not run the patch and avoid DRM on their systems, but if they wanted to be secure, they had to accept monopoly-enforcing DRM technologies and allow Microsoft to update such systems at any time in the future. How can we trust that our systems are secure and configured the way we expect them to be (enterprise change management comes to mind) with such subtle vendor trickery being forced upon us? Sounds like blackmail to me. (Incidentally, Lance believes the ability of a user to 'hack' their own system to circumvent the Apple iTunes DRM makes the Macintosh a bigger 'hack target' for the purposes of his article.. apparently, he's not familiar with the many nuances of the terms 'hack' and 'hackers' or knows that power-users often 'hack' their own systems for fun.) Were Apple to do such a thing, Mac users would likely revolt, and Apple's credibility would be seriously damaged.
What does that say about trusting an operating system's ability to perform in a stable and secure manner? Windows users should wonder who's really in control of their systems these days. But Lance is oblivious to this, and happy to exist in such an untrustworthy computing environment.
On the matter of malicious code, Lance reports being 'driven crazy' when Mac users grin at not falling victim to another Windows virus or malicious code attack. He's free to rebuild his machine after each new attack if he wants, and needs to know that Mac users are grinning at not having to worry about such things getting in the way of being productive. You see, because of how Mac OS X was originally designed, the chance of a user suffering from a malicious code attack - such as those nasty e-mail worms - is extremely low. Granted, Mac users may transmit copies of a Word Macro Virus if they receive an infected file (and use Microsoft Word) but it's not likely that – again, due to Mac OS X's internal design – a piece of malicious code could wreak the same kind of havoc that it does repeatedly on Windows. Applications and the operating system just don't have the same level of trusted interdependencies in Mac OS X that they do on Windows, making it much more difficult for most forms of malicious code to work against a Macintosh.
Unlike Windows, Mac OS X requires an administrator password to change certain configurations, run the system updater, and when installing new software. From a security perspective, this is another example of how Apple takes a proactive approach to system-level security. If a virus, remote hacker, or co-worker tries to install or reconfigure something on the system, they're stymied without knowing the administrator's password stored in the hardened System Keychain. (Incidentally, this password is not the same as the Unix 'root' account password of the system's FreeBSD foundation, something that further enhances security.) In some ways, this can be seen as Mac OS X protecting a careless user from themself as well as others.
Lance also fails to recognize that Windows and Mac OS are different not just by vendor and market share, but by the fundamental way that they're designed, developed, tested, and supported. By integrating Internet Explorer, Media Player, and any number of other 'extras' (such as VB Script and ActiveX) into the operating system to lock out competitors, Microsoft knowingly inflicts many of its security vulnerabilities onto itself. As a result, its desire to achieve marketplace dominance over all facets of a user's system has created a situation that's anything but trustworthy or conducive to stable, secure computing. Mac users are free to use whatever browser, e-mail client, or media player they want, and the system accepts (and more importantly, remembers!) their choice.
Contrary to his article, the small market segment held by Apple doesn't automatically make the Mac OS less vulnerable to attack or exploitation. Any competent security professional will tell you that 'security through obscurity' - what Lance is referring to toward the end of his article - doesn't work. In other words, if, as he suggests, Mac OS was the dominant operating system, its users would still enjoy an inherently more secure and trustworthy computing environment even if the number of attacks against it increased. That's because unlike Windows, Mac OS was designed from the ground up with security in mind. Is it totally secure? Nothing will ever be totally secure. But when compared to Windows, Mac OS is proving to be a significantly more reliable and (exponentially) more secure computing environment for today's users, including this security professional.
If Lance is sleeping well believing that he's on an equal level with the Mac regarding system security, he can crow about not being overly embarrassed while working on the only mainstream operating system that, among other high-profile incidents over the years, facilitated remote system exploitation through a word processor's clip art function! [3]
Trustworthy computing must be more than a catchy marketing phrase. Ironically, despite a few hiccups along the way, it's becoming clear that Mac OS, not Windows, epitomizes Microsoft's new mantra of 'secure by design, default, and deployment.'
Who's crowing now?
[1] Eureka! Macs Are Not Invulnerable
[2] Microsoft Makes An Offer You Can't Refuse
[3] Buffer Overflow in Clipart Gallery (MS00-015)
© 2003 by Author. All Rights Reserved. Permission granted to redistribute this article in its entirety with credit to author.
Richard Forno is a security technologist, author, and the former Chief Security Officer at Network Solutions (now owned by VeriSign.) His home in cyberspace is infowarrior.org.
* Shortly after Richard Forno wrote this piece, Microsoft issued a bulletin warning consumers what they should do before connecting their new PC to the Internet. So there - Reg editors
Question or issue on macOS:
Pixels In Hell Mac Os 11
I wish I would find an answer for this. I have searched and searched and couldn't the right answer. Here is my situation:
In a Mac OS Cocoa Application, I want to draw a pixel (actually a few pixels) onto a dedicated area on my application window. I figured, it would be nicer to have a NSImageView placed there (I did so with IB and connected the outlet to my app delegate) and draw on that instead of my NSWindow.
Pixels In Hell Mac Os Catalina
How in the world can I do that? Mac OS seems to offer NSBezierPath as the most basic drawing tool — is that true? This is completely shocking to me. I come from a long history of Windows programming and drawing a pixel onto a canvas is the most simple thing, typically.
I do not want to use OpenGL and I am not sure to what extent Quartz is involved in this.
All I want is some help on how I can pull off this pseudocode in real Objective-C/Cocoa:
I would love to hear your answers on this and I am sure this will help a lot of people starting with Cocoa.
Thanks!
How to solve this problem?
Solution no. 1:
NSBezierPath is the only tool available in Cocoa for drawing most primitive shapes, and for many complex shapes.
Detail description you can find here:
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CocoaDrawingGuide/Paths/Paths.html%23//apple_ref/doc/uid/TP40003290-CH206-BBCHFJJG
http://en.wikibooks.org/wiki/Programming_Mac_OS_X_with_Cocoa_for_Beginners/Graphics_-_Drawing_with_Quartz
Solution no. 2:
What you are asking for is either of these two methods:
Pixels In Hell Mac Os 11
I wish I would find an answer for this. I have searched and searched and couldn't the right answer. Here is my situation:
In a Mac OS Cocoa Application, I want to draw a pixel (actually a few pixels) onto a dedicated area on my application window. I figured, it would be nicer to have a NSImageView placed there (I did so with IB and connected the outlet to my app delegate) and draw on that instead of my NSWindow.
Pixels In Hell Mac Os Catalina
How in the world can I do that? Mac OS seems to offer NSBezierPath as the most basic drawing tool — is that true? This is completely shocking to me. I come from a long history of Windows programming and drawing a pixel onto a canvas is the most simple thing, typically.
I do not want to use OpenGL and I am not sure to what extent Quartz is involved in this.
All I want is some help on how I can pull off this pseudocode in real Objective-C/Cocoa:
I would love to hear your answers on this and I am sure this will help a lot of people starting with Cocoa.
Thanks!
How to solve this problem?
Solution no. 1:
NSBezierPath is the only tool available in Cocoa for drawing most primitive shapes, and for many complex shapes.
Detail description you can find here:
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CocoaDrawingGuide/Paths/Paths.html%23//apple_ref/doc/uid/TP40003290-CH206-BBCHFJJG
http://en.wikibooks.org/wiki/Programming_Mac_OS_X_with_Cocoa_for_Beginners/Graphics_-_Drawing_with_Quartz
Solution no. 2:
What you are asking for is either of these two methods:
Chess 3d ultimate mac os. NSBitmapRep setColor:atX:y: Changes the color of the pixel at the specified coordinates.
NSBitmapRep setPixel:atX:y: Sets the receiver's pixel at the specified coordinates to the specified raw pixel values.
Note that these aren't available on iOS. On iOS, it appears that the way to do this is to create a raw buffer of pixel data for a given colorspace (likely RGB), fill that with color data (write a little setPixel method to do this) and then call CGImageCreate() like so:
Lastly, you might be wanting to manipulate pixels in an image you've already loaded into a CGImage. There is sample code for doing that in an Apple Technical Q&A titled QA1509 Getting the pixel data from a CGImage object.
Solution no. 3:
Cocoa's low-level drawing API is Core Graphics (Quartz). You obtain a drawing context and issue commands to draw onto that context. The API is designed to be device-independent (you use the same commands to draw onto the screen as you would to draw onto paper, when printing). Therefore, there are no commands for filling in individual pixels, because there's no such thing as a pixel on paper. Even on the screen, your view may have been transformed in some way so that a single point doesn't map to a single device pixel.
If you want to draw a single pixel, you need to specify a rectangle that is the size of a single pixel, then fill it in. For the pixel at (x,y), you would want a rectangle with origin of (x-0.5,y-0.5) and a size of (1,1).
Manitcle mac os. You can do that with NSBezierPath, or you can get a Core Graphics context (CGContextRef) from [[NSGraphicsContext currentContext] graphicsPort] and use functions like CGContextFillRect().
This obviously won't be very fast if you are drawing a lot of pixels; that's not what the API is designed for. If that's what you need to do, consider creating a buffer with malloc and writing your pixel data to that, then using Core Graphics to convert it into a CGImageRef, which can be drawn to the screen.
Solution no. 4:
For drawing pixels as you describe, there's no need to create a path or resort to the Quartz 2D or OpenGL API.
See NSRectFill() and related functions like NSRectFillList() and NSRectFillUsingOperation().
If you're drawing a lot of individual pixels, NSRectFillList() is about as fast as you can do it without resorting to rolling your own image buffers.
Solution no. 5:
Maybe I am misunderstanding the question, but Quartz has the ability to fill rectangles: Michios death drive mac os.
Solution no. 6:
Here's a quick way to draw pixels on OS X:
Solution no. 7:
I found your question here a bit late because I have the same problem. Perhaps Apples developer documentation can help you here. I have not tested it myself, but take a look at this document:
Roughly in the center of the document you will find the section 'Creating a Bitmap'. It tells you different ways of creating pixel data.
Solution no. 8:
Hope this helps!
