Mac OS 9 was the ninth major release of Apple's classic Mac OS operating system which was succeeded by OS X.Introduced on October 23, 1999, it was promoted by Apple as 'The Best Internet Operating System Ever', highlighting Sherlock 2's Internet search capabilities, integration with Apple's free online services known as iTools and improved Open Transport networking. Mac OS X Internal Edition - (Download #1) Mac OS X Public Beta System clock must be set before May 2001. Mac OS X Cheetah 10.0 - (Download #2 - #5) 10.0? In 2001, Apple released Mac OS X, a modern Unix-based operating system which was later rebranded to simply OS X in 2012, and then macOS in 2016. Its final version was macOS Catalina, as Apple went on to release macOS 11 in 2020. The current version is macOS Big Sur, first released on November 12, 2020.
2001 – Your Mac was so darn fast when you bought it. It was a top-of-the-line and state-of-the-art computer, but it suddenly seems older than you. You have the impression that with all its power, it could deliver the goods in much less time than it does now.
- Description: Modifying the system to make it faster
Difficulty level: Easy
System version: System 7 to Mac OS 9
Required: A bit of patience
You are absolutely right. Here are a few tips to give some life back to your Macintosh and preserve its power in the future.
Memory
Your memory, in the form of your RAM and hard drive, is one of the keys to your Mac’s speed. If you manage it correctly, you are more likely to use all its power at maximum speed.
Disk Cache
The disk cache is very important for your overall performance. The first tip is to avoid giving it less memory than its default setting. It can be tempting to see the disk cache as a RAM hog, but if you decrease the amount of allocated memory, you will find out quickly that your Mac will choke on even the least demanding tasks, Web browsing included. Make sure to give it at least its default setting – and if you have some spare RAM, increase the caches memory by 1-2 megabytes.
Virtual Memory
I already talked about this in iBasics. The virtual memory (VM) setting is simple: Turn it off. Your RAM is the fastest memory available on your Mac, and that is why it is the most expensive per megabyte. By turning VM off, you reduce hard drive accesses and allow your RAM to take over a few things that your hard disk used to do. As long as you are not tight on RAM, you can afford to turn virtual memory off. VM can be useful for file mapping, but it will slow you down.
RAM Disk
What about the RAM Disk in the control panel? Refer to a Speed Up Internet Explorer on the Classic Mac OS to learn how to use it, and remember that it can be used for any file that you use frequently.
Memory Usage
The way you use your Mac will impact your use of memory. When you launch and quit applications all the time, you abuse your system greatly. The memory structure of the Classic Mac OS (before Mac OS X) is a bit outdated and does not handle application memory as well as a modern operating system, such as Mac OS X. Don’t abuse it by repetitive application launching and quitting unless you are tight on RAM. If you launched Internet Explorer, keep it open, since you know you may use it in a few minutes anyway.
Avoid having everything open at the same time. If you are short on RAM (less than 5 megabytes available) when you are working on your Mac, you will see a serious speed hit. Your desktop picture or background will seem messed up, and switching between applications will be a pain. Turn off a couple of applications when this happens; you will regain speed.
Restarts
Speaking of memory management, a great way to wipe everything clean and start over is to restart when you notice a speed decrease. When you launch applications and work with files, your RAM collects and loads libraries as well as data. Your clipboard will contain the last bit of information you copied and pasted.
All of this takes RAM space and forces your Mac to carry more weight around when you execute other tasks. A restart will refresh your Mac’s memory by eliminating all the stored information that you will not use later in your session. It cleans up everything.
Desktop Pictures
Ah, that sunset at the mountain was dazzling when you shot the picture during your last vacation! Cat part.i(o) mac os. But it slows down your Mac when it is in the background. If you need a temporary speed boost, or if you simply think that you can live without the sunset picture, turn it off and replace it with a desktop pattern. Whenever I want a speed increase, I just revert to an entirely black desktop pattern. It is dark, but it works and is easy on the eye.
Networking
Whenever your Mac does network operations, it executes pauses, even if they are not always perceptible. The pauses are greater if you use network protocols such as Web sharing, File Sharing, and AppleTalk. Those are useful features, but they can really slow down your Mac when they are turned on and in use.
Unless you need them 100% of the time, turn them off until you need to use them. Go to the control strip (above) and turn off AppleTalk. Go to the Web Sharing control panel and make sure to turn it off by clicking on Stop. Do the same in the File Sharing control panel.
Manage Extensions
The best way to improve your performance is to manage your extensions with the Extensions Manager control panel. Turn off all the extensions that you do not need – or turn them off until you need to use them. Whenever you install software, you get an installation report that tells you what has been installed and where. Referring to such files is an excellent way to find out what extension is used with what software. Otherwise, you can click on the arrow besides Show Item Information to figure things out.
If you wish to have an “everything loaded” configuration, keep it as a set. You can rename it by choosing Rename Set in the File menu. Then click on Duplicate Set to create a set where you turn off extensions and control panels that you do not use all the time. Name that set. When you have multiple sets, all you have to do to switch between them is to click on the popup menu called Selected Set (see screen shot) and select one, then click on Restart.
In all the available sets, the best one to use for maximum speed is Mac OS All. The other set (Mac OS Base) is not a very appropriate extension set, since its prime use is troubleshooting.
In the Extensions Manager, the Startup Items are easily visible. Those are useful if you want the same item to launch at every startup, but you will quickly note that it slows you down during startup when you arrive on the desktop. This can get annoying. Make sure not to put anything in Startup Items unless the items in question are essential to your use.
Here are a couple of extensions and control panels that create a speed hit when activated: Kaleidoscope, StuffIt Deluxe’s True Finder Integration, Timbuktu Extension, and anything that adds something directly to the Finder and its menu bar.
Rebuild the Desktop
The desktop files store all the icons that you have seen on your screen since the latest rebuild. If you are one to download icon sets from the Web or to use CD-ROMs often, the number of unused icons stored in your desktop files can be scary.
Define melanie mac os. Wipe everything clean by restarting and holdin downg the Command and Option keys. When you get an alert about rebuilding your volumes’ desktop, click on OK each time you get the alert. You will notice a speed boost after the rebuilding process.
Beware of Upgrades
Always be careful with software updates and upgrades. Get them only if they fix bugs or add features that you cannot live without. Software always grows bigger and adds more hardware requirements. The upgrade cycle can make a new Mac look very old within two years, while conservative upgrading behavior will make your Mac shine for years to come.
That’s it for this week. Enjoy your faster Mac. Hibernation (audrith) mac os.
Links
Keywords: #classicmacos #diskcache #virtualmemory #ramdisk
Short link: http://goo.gl/L6NahP
Learning to live with Mac OS X Mac OS X's Finder: love it or loathe it, the two points that unite almost everyone who has used Apple's next-generation operating system are that it's not up to scratch and that Apple's reason to write it using OS X's Carbon API is the chief reason why.
![Park (2001) Mac OS Park (2001) Mac OS](https://www.versionmuseum.com/images/operating-systems/mac-os-x/mac-os-x^2001^10.0-about-mac.jpg)
No, say so many observers, Apple should have written Finder using OS X's other API, Cocoa. But is that really the case? Certainly Carbon seems to be getting all the bad press, while Cocoa is being held up as some sort of shining beacon lighting the way to 'true' Mac OS X native apps.
Bollocks, says one ex-Apple software engineer of our acquaintance who has no small knowledge of the beast. 'Carbon is at the same level as Cocoa, and they are both built on the same underlying foundation. They are absolutely true peers of each other,' he says. 'One can do things that the other can do and vice versa, but there's no reason why a well written Carbon app can't be just as good as a well written Cocoa app.
'Rewriting the Finder in Cocoa is not the answer.'
Apple of my API
Carbon and Cocoa are OS X's two Application Programming Interfaces (APIs). Both are frameworks around which coders can weave applications and utilities that are able to take full advantage of the new operating system. Cocoa's origins lie in NeXT's NeXTSTEP operating system, later reborn as a cross-platform programming framework called OpenStep. It's an object-oriented framework programmed in Objective C or, since Apple bought NeXT, Java.
With almost all of Apple's senior software staffers ex-NeXT, it's nor surprising that Cocoa has gained a reputation as the way of producing native OS X applications.
Carbon, on the other hand, has often been portrayed as Cocoa's lesser sibling. Carbon was only developed because some of the biggest Mac software developers balked at being forced to rewrite their code from scratch. That's what they would have had to do under Apple's original next-gen operating system plan: rewrite their apps to work with Cocoa, then called Yellow Box, or leave them as classic Mac OS apps but have the run without any of the benefits the new, Unix-based OS brings.
No wonder, then, that Carbon has always seemed little more than a kludge to shoehorn OS 9.x code into OS X, done to allow software vendors to port their apps over quickly with just a few modifications.
Carbon ain't no kludge
That's the wrong way to look at it, says our correspondent: 'The Carbon engineers have done an amazing job. The fact that you can run the same application on both OS 9 and OS X is a really amazing thing that should be celebrated, not called a kludge.'
Digging into the details of both Carbon and Cocoa and you can soon see what he means. If you're interested, check out O'Reilly's Learning Carbon and Learning Cocoa. Written by Apple, they're not the most friendly of programming manuals (what I want is a Carbon-specific answer to Jim Heid's great but now very dated Programming Starter Kit for Macintosh) but right now they're the best there is and the certainly provide a good introduction to the two APIs.
Cocoa provides a solid development framework, particularly when supported by the developer tools Apple ships with Mac OS X. Getting your head around object-orientation isn't easy. But if you've spent some time with RealSoftware's RealBasic, which works broadly like Apple's Project Builder but operates in a much more intuitive way, you'll have a good idea how it works.
OOPs upside your head
Object orientation programming (OOP) is an approach to coding that essentially breaks applications down into self-contained modules that contain not only data but the code to manipulate that information. A Mac OS window is ultimately just data (size, position, style, content, etc.), but in a OOP world, it's an self-contained object that knows not only what it looks like (the data) but how to behave - how to close, how to hide, that kind of thing.
Actually, a lot of Mac OS apps are already built around an OOP framework, Metrowerks' PowerPlant and written using C++, like Java and Objective C another object-oriented programming language.
PowerPlant was, of course, designed for the Toolbox, the classic Mac OS' own API, adding an object-oriented layer to Toolbox's traditional, linear framework. Since PowerPlant now supports Carbon coding it's perfectly possible to do build object-oriented Carbon apps. And Carbon is essentially just a modified version of the Toolbox API, it's immediately familiar to anyone who has written Toolbox apps in C.
And, as our correspondent points out, 'Carbon is evolving'. Toolbox was developed for systems running one application at once. Multifinder and later kludges to allow multiple apps to run alongside each other aside, that's essential what Toolbox is: a one-app-at-time system.
Event horizons
OS X isn't. Based on Unix, it expects to have to support umpteen processes running in parallel, often for multiple users working on the system at the same time. That requires a very different approach to interacting with the user, one where apps don't look out for your clicks and key presses but wait for the OS to tell them what the user has done.
Park (2001) Mac Os Catalina
Carbon can work with both of these 'event models', but to get the most from it code needs to be written with the OS X event model in mind. 'The new Carbon Events API is very powerful and as applications adopt it, rather than just doing straight ports of their old apps, we'll see very nimble applications appearing,' says our correspondent.
'What you should be pushing developers to do is not to throw away their existing apps and rewrite them in Cocoa, but to get them to embrace the modern Carbon APIs. It doesn't make any financial or engineering sense to start again from the beginning when they are 90 per cent of the way there already.
'The key thing is, Carbon is designed to be a compromise on OS 9, not a compromise on OS X. It's designed for OS X first, and then things are brought back to OS 9 and made to work the best they can.'
Carbon and Cocoa: peer to peer
So much for Carbon being unequal to Cocoa. Actually, the reverse may be true, whatever the ex-NeXTers may think. 'I've used both, and I've found I'm much more productive writing code using Carbon and CodeWarrior rather than Cocoa and Project Builder.'
In short, if there's a problem with Finder, it's not that it's written using Carbon. No, it's that it needs tuning and optimising. And, credit to Apple, that was the company's key message at last May's Worldwide Developers Conference. Recompiling an application to support Carbon is only the first step - next comes the real work: reworking it to support OS X's design philosophy and thus making at true Carbon - and a true Mac OS X - application. ®
To be continued..
Park (2001) Mac Os X
Related Links
O'Reilly's Mac books site
RealSoftware's RealBasic homepage
RealSoftware's RealBasic homepage
Earlier Episodes
3. Windows XP hits where Apple's Aqua misses?
2. Mac OS X crashes: Radeon not guilty
1. Mac OS X: Reg box stable - at last..
2. Mac OS X crashes: Radeon not guilty
1. Mac OS X: Reg box stable - at last..
Park (2001) Mac Os Download
Get ourTech Resources