The Disaster-Free Upgrade to Mac OS 10.1
Pages: 1, 2
Updating Classic to 9.2.1
Now that you have Mac OS 10.1 up and running, you'll want to upgrade your Classic environment to OS 9.2.1. Why spend the time to upgrade this too since you already have 9.1 installed and running fine? There are two reasons: 1) Many non-Carbonized applications will run better in 9.2.1, and 2) 9.2.1 is faster. For example, in a very non-scientific test on my Pismo, OS 9.2.1 launched as Classic in 1 minute and 30 seconds. But it took OS 9.1 a full 2 minutes, 40 seconds to launch in Classic mode. And believe me, that 1 minute, 10 second difference feels like a lifetime when you're waiting to go back to work.
So now that I've talked you into updating your Classic environment, insert the 9.2.1 update disc, and read the "Update to Mac OS 9.2.1" PDF file. Then open the folder of the language of your choice (English, in my case), and double-click the updater icon.
Your Mac will launch Classic if it isn't already running, then verify the 9.2.1 updater to make sure everything is in order. Be patient because the verification takes a couple minutes.
After verification has completed, you'll notice that nothing seems to happen, and you might even start to wonder if something has gone out of whack. Fear not! Go back and look on your Mac OS X desktop, you'll see a Mac OS 9.2.1 Update volume sitting there. Double-click it and a window appears containing the Before You Install ReadMe file and the actual updater (plus Utilities and Software Installers folders that you really don't need to be concerned about at this point).
After scanning the ReadMe file, double-click on the "Mac OS Install" icon. You'll be greeted with the standard OS 9 sequence of install screens. The first one of consequence is the "Select Destination" screen. If you have a partitioned drive, as I recommended in the earlier Disaster-Free Upgrade articles, you actually have two System 9 folders on your computer -- one on the Mac OS X partition, and one on your other partition, which is your old OS 9 environment.
For now, I recommend that you leave your old environment alone. After all, the whole point of having it occupy half of your hard drive is to always have a stable fallback system in case you run into an incompatibility with these new system upgrades.
So for this update, choose "Mac OS X" as your destination disk.
Finally, you're presented with the "Install Software" screen. Unless you have a special situation, simply click the Start button and let the installer do all the work. If you need to adjust an aspect of the install for a specific reason, click the "Customize" button and make your changes before proceeding.
Once the update has finished, you only have one more step to complete. Go back to Mac OS X, open the System Preferences panel, and click on the Classic icon. If you have two System 9 volumes listed, as do those who have partitioned hard drives ala Disaster-Free recommendations, make sure that the Mac OS X volume is highlighted for Classic startup.
By doing this, you've instructed your Mac to launch the new 9.2.1 operating system on your Mac OS X partition instead of the older, slower 9.1 system on the other partition. Now you have the best Classic environment available.
Clean-up your dock
Your new 10.1 operating system has many enhancements and a couple application upgrades. It adds files to your various folders and to the menu bar at the top of the screen, but it doesn't necessarily update the icons on your Dock. Now it's time to do a little Dock housecleaning.
For example, I was using iTunes 1.1.1 with system 10.0.4. Great application. But I had seen in 10.1 demos that there were new iTunes controls available directly from the Dock icon. Much to my initial disappointment, I didn't see any of those enhancements when I launched iTunes after my upgrade.
Little did I know that 10.1 also installs a new version of iTunes, 1.1.2, in my Applications folder. But it didn't update the icon on my Dock. So I removed the old iTunes icon from the Dock, launched the new iTunes from the Applications folder, and added the new icon where the old one had resided. Now I have all the new iTunes features available to me via the Dock. I went on to check my other Dock icons and removed a number of outdated ones.
After you finish cleaning up your Dock, you might want to go through your Applications folder and trash the older versions of duplicate programs still in there.
Add new applications
If you haven't checked recently, there are lots of new applications available for Mac OS X users. One place you can see what's happening is on Apple's Mac OS X web page. Another terrific resource is the Software folder on your iDisk (you have signed up for iDisk, right?). I just checked my Mac OS X folder there and found lots of great applications waiting for me to play with.
You won't always find the exact application you're accustomed to using in OS 9, but there are many alternatives appearing that will work nicely and allow you to stay in Mac OS X as much as possible. Here are a few of my current favorites:
BBEdit 6.1 for text editing and HTML coding (full version).
OmniWeb 4 for web browsing (full version).
Internet Explorer 5.1 for web browsing (full version included with 10.1).
Graphic Converter 4.0.7 for image editing (full version).
Canvas 8 for web graphics and image editing (preview edition).
Microsoft Word for Mac OS X for word processing (preview edition).
iTunes 1.1.2 for music listening and cataloging (full version included with 10.1).
Acrobat Reader 5.0 for PDF file reading (full version).
AOL Instant Messenger 4.5.7 for instant messaging (full version).
DVD Player 3.0 for DVD movie playback (full version included with 10.1).
iMovie 2.1.1 for DV movie editing and production (full version included with 10.1).
Mail 1.1 for email sending, receiving, and storing (full version included with 10.1).
QuickTime Pro 5.0.2 for QuickTime movie, image, and audio playback and authoring (upgraded full version)
VirtualPC Test Drive 4.0.5 for working in the Windows PC environment (preview edition).
All of these applications allow me to stay in the Mac OS X environment without having to switch to Classic mode, or worse yet, reboot to my OS 9.1 partition. And we'll see this list grow considerably in the coming months.
A few words about performance
Apple promised improved performance in 10.1, and they delivered. Most of my applications now open within 2 to 4 bounces; this is a tremendous improvement over the 6 to 8 bounces I was enduring with Mac OS 10.0.4. Window behavior is also snappier, as is mousing and application controls.
|
I ran a little DVD performance test on my Pismo where I moved the DVD playback screen around the desktop while the movie was playing. I had seen this test on a dual-processor G4, and no frames or audio were dropped. Even though my Pismo didn't fare quite as well at the G4, I was impressed with how the movie kept playing even as I harassed the application.
I did get some hesitation when I minimized a QuickTime movie during playback. The window did retreat to the Dock, but it did so with a little jerkiness, although it continued to play even after residing in the Dock.
All in all, not bad for an "old" G3 laptop.
I did find a way to make the operating system freak out, and that was by messing with the network settings while it is working online. But certainly, if I'm crazy enough to do that, I deserve what I get.
So, overall, I think Mac OS 10.1 is a thoughtful, well-executed upgrade. I feel comfortable recommending it to many more Mac users than previous versions of Mac OS X. If Apple continues to show this level of skill and commitment to their new operating system, I think it is well on its way to becoming the premier Unix desktop environment.
Derrick Story is the author of The Photoshop CS4 Companion for Photographers, The Digital Photography Companion, and Digital Photography Hacks, and coauthor of iPhoto: The Missing Manual, with David Pogue. You can follow him on Twitter or visit www.thedigitalstory.com.
Return to the Mac DevCenter.
You must be logged in to the O'Reilly Network to post a talkback.
Showing messages 1 through 17 of 17.
-
I need help with v. 10.0.03
2004-01-26 11:24:45 hcenac1 [Reply | View]
I found a disk in my computer desk for OS X v. 10.0.03 from 2001. I installed it fine, but a lot of the programs I use often only have downloads for 10.2 or higher or 9.1 and lower. Classic environment freezes my computer, and I want to either uninstall or update the OS X version I have without spending a lot of money. What can I do? Also, where can I find administrator information? Because I can't seem to uninstall OS X v. 10.0.03 without it. Help!
-
Upgrade Help.
2003-10-27 08:54:56 anonymous2 [Reply | View]
is there a way to upgrade from 9.2 to os x without paying mucho $$$??
Broke student w/ a g3 powerbook 500 mhz laptop, running os 9.2. looking to jump onto jaguar or panther and not lose my existing info.
I do not have a method of copying ot ripping anything off my machine except by e-mailing it to my yahoo. DVD/CD drive with no writeable cpabilities...
What can I do??
on_any_sunday @ Yahoo dot com needs help!!
Sunday
-
randy munden
2003-08-31 13:24:23 anonymous2 [Reply | View]
loves his apple hes got apple titanium and a imac ones wireless and the other is hard wires i will never go back to ibm computers RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY RANDY MUNDEN MUNDEN MUNDEN MUNDEN RANDY RANDY RANDY
-
Apple Laptop Keyboards Unsuitable for Unix Users
2002-09-18 01:55:45 anonymous2 [Reply | View]
I am a long-time Unix user. That means I need to have the Ctrl key to the left of the A key. This is a genuine need, not merely a want; it is based upon ergonomics. The Ctrl key is heavily used in unix, and it must be easily accessable. It cannot be off in the lower left corner of the keyboard where it is difficult to get at, and where it distorts the position of your left hand such that you can't easily type other keys while holding the Ctrl key down.
Apple desktop keyboards are now all USB. They are all OK. The CapsLock key can be re-mapped into a Ctrl key.
Unfortunately, even in this modern age, all Apple laptops have built-in ADB keyboards. The ADB keyboard is broken-by-design. It is, in general, not possible to remap the CapsLock key into a Ctrl key.
There are some exceptions, but they are horrible kludges. They are
horrible kludges because the original design of the ADB keyboard was a horrible kludge. The correct solution would be for Apple to re-design their laptop motherboards to use built-in USB keyboards. This hasn't happened yet. If you run Linux, use Debian's solution. For Mac OS X users, uControl works. There are no solutions (that I know of) for either NetBSD or OpenBSD. Please note once again that the "solutions" above are in fact kludges, because of the original bad design of the ADB keyboard.
Apple is (currently) ignoring Unix users! This is not merely speculation on my part. In an on-going email exchange I am having with an Apple employee (whom I won't name) in their marketing department, the Apple marketing person directly stated to me that Apple was catering to their historic Mac customers, and is purposely ignoring the Unix market. He also claimed that Apple would soon start paying more attention to the Unix market. I won't hold my breath. Apple has been ignoring Unix users for more than 10 years. I expect that trend to continue. (Also note that my Apple contact indicated that Macs would never ship with a 3-button mouse, even though Apple intended to port almost all X-window software and deliver it either on a CD/DVD or installed directly on each Mac's hard drive. How Unix friendly is a 1-button mouse with X programs that often require 3 buttons?)
Apple has now lost two opportunities to sell me hardware. I really wanted an Apple laptop for their superior battery life, and for the PowerPC with Altivec CPU. (The Altivec is vastly superior to the x86 line for DSP.) Because I can't live with the broken-by-design built-in ADB keyboard in all Apple laptops, Sony and IBM sold me laptops instead. If Apple fixes this problem, they will sell me a PowerBook next year; if they don't, I'll still be running OpenBSD on x86 hardware, and wishing I could use a Mac.
-
Apple Laptop Keyboards Unsuitable for Unix Users
2003-04-18 17:53:25 anonymous2 [Reply | View]
I am in total agreement. The Apple keyboards are terrible with regard to ergonomics of the modifer keys such as the control key.
So, does anyone have a solution in the form of a replacement keyboard? If so please send me a clue, at <sv_commuter@yahoo.com>.
Thanks!
-
It's here - now what? No Backup System...
2001-10-15 07:38:44 sneex [Reply | View]
Hi All :-)
Below is an example of how to *really* backup a Mac OS X system. The normal Unix tools which come internal to OSX *do not* work - try them if you don't believe me. They don't work simply because Apple *forgot* to make them HFS+ and MacOS 9 *fork* aware. Which is not a good thing if you still use Mac OS 9x applications...
Based upon the work of others - I just want credit for using their work in a more portable manner (the other methods required that you had more than one HD inside your system - this is somewhat difficult if the system is an OSX Laptop. Hence why I had to modify the standard methods.) :)
HTH;
-Sx- :]
# The method I am using -
# WARNING - You may need to fix formatting errors caused by this posting...
# I am on a G4 laptop, so make sure we
# have mounting points...
/usr/bin/hdiutil eject disk1
/usr/bin/hdiutil eject disk2
# Make a place to backup to...
# Optionally you want to access
# something like a Firewire drv...
/usr/bin/sudo /bin/mkdir /BackUps
/usr/bin/sudo /usr/sbin/chown sneex /BackUps
/usr/bin/hdiutil create -megabytes 1000 /BackUps/backupImage.dmg
/usr/bin/hdid -nomount /BackUps/backupImage.dmg
/usr/bin/sudo /sbin/newfs_hfs -v myBackupDir /dev/disk1
/usr/bin/hdiutil eject disk1
/usr/bin/hdid /BackUps/backupImage.dmg
# You will need hsfpax from the iTools site...
/usr/bin/hfspax -r -w -v -Y -Z /Users/sneex /Volumes/myBackupDir
clear
echo Done...
exit
Notes & Typical Uses (much from the hfspax README doc(s)):
The following examples illustrate some common ways in which you can use hfspax
from a command shell (Terminal). In each command, we include the v option which
makes hfspax's output verbose. If you do not wish to see all the files listed
in detail, omit the v character from the commands given below.
Backing up
To create an archive of the folder thisfolder under the name thisfolder.pax,
type in the command
hfspax -wv -f thisfolder.pax -x cpio thisfolder
If thisfolder is not in the current path, you can either change your working
directory with a command like
cd /Users/Documents/
and then use the above command, or you can use a command like
hfspax -wv -f thisfolder.pax -x cpio /Users/Documents/thisfolder
The effect of these differs significantly when you come to unpack the archive:
if you used cd to change directory, the unpacked archive will be reconstructed
relative to your current working directory. If you used the full path name in
the command as given immediately above, then the old directory will be
completely reconstructed in its original location. It is important that you
appreciate this fundamental difference: when unpacking, hfspax (like pax) will
restore files to the path shown when you list the contents of the archive,
relative to the current working directory (in the command shell).
Listing archive contents
To list the contents of the archive thisfolder.pax, type in the command
hfspax -v -f thisfolder.pax
Restoring
To restore the files contained in the archive thisfolder.pax to their original
locations, type in the command
hfspax -rv -f thisfolder.pax
Note how you can control whether the original directory is reconstructed,
according to how you specify its original path name (see above).
Volume backup
To make a full backup of your active Mac OS X volume, you will need to create a
series of pax archives to cover each of the folders. If you do not have
Mac OS 9.x on the same volume, you can achieve this using the following commands
(which assume that you are creating the archives at the top level of another
volume called backvol):
hfspax -wv -f /Volumes/backvol/Applications.pax -x cpio Applications
hfspax -wv -f /Volumes/backvol/Library.pax -x cpio Library
hfspax -wv -f /Volumes/backvol/Network.pax -x cpio Network
hfspax -wv -f /Volumes/backvol/System.pax -x cpio System
hfspax -wv -f /Volumes/backvol/Users.pax -x cpio Users
hfspax -wv -f /Volumes/backvol/bin.pax -x cpio bin
hfspax -wv -f /Volumes/backvol/private.pax -x cpio private
hfspax -wv -f /Volumes/backvol/sbin.pax -x cpio sbin
hfspax -wv -f /Volumes/backvol/usr.pax -x cpio usr
hfspax -wv -f /Volumes/backvol/mach.pax -x cpio mach*
Note how you access the other volume through its named entry in the /Volumes
path: this is the standard UNIX way of accessing volumes other than the root
(which appears at /). The final command backs up the Mach kernel files, which
remain at the root level of the startup volume. You may also need to run the
following line if you have the developer tools installed:
hfspax -wv -f /Volumes/backvol/Developer.pax -x cpio Developer
You may find it useful to back up the /dev folder. However, this may not be
useful, or it may result in many errors, because of its special nature. If you
do want to try backing it up, use something like:
hfspax -wv -f /Volumes/backvol/dev.pax -x cpio dev
Volume restore
To restore a totally trashed Mac OS X startup volume, restart from another
Mac OS X volume, initialise the disk, and allow the Mac OS X Install CD-ROM to
install OS X 10.x. Then, make sure that hfspax is installed on the
reconstruction disk, restart from it, and simply restore each of the .pax
backups using a command like
hfspax -rv -f /Volumes/backvol/Applications.pax
Note that you have to do this from the disk to which you are restoring, or each
archive will replace the files on the active or 'root' Mac OS X disk. You can
work around this by creating the archives from within each directory, but this
starts to get fairly complex. You can also use this sequence of commands to
create a mirror of your Mac OS X startup volume on another hard disk, although
you will need to recreate some links at the root level.
Moving to a new Mac
When you need to move all your work from one Mac to another, the easiest thing
to do is a full backup (see above) onto an external disk, such as a FireWire
hard disk. Put all the pax files there, and move the disk over to your new
Mac. You will then want to select which files you want to install: a simple way
of doing this is to cd to your Documents folder
cd ~/Documents
and then unpack each archive in turn into that location, using commands
of the form
sudo hfspax -rv -f /Volumes/backvol/Applications.pax
(Note the use of sudo, see below.) You can then change the owner of folders
as necessary, using something like
sudo chown -R mynewusername Applications
as appropriate. Then using the Finder (recall that command line cp will not
preserve resource forks), drag the applications, folders, etc. into their
new locations .
Working incrementally
You can use hfspax's command options to perform incremental backups and restore
incrementally. To create an archive with just files modified since
year 2001 month 08 date 10 hour 07 minutes 30, use
hfspax -wv -f archive.pax -x cpio -T 0108100730/m foldertoarchive
When you want to append those same files to the existing archive called
archive.pax, use the -a option thus:
hfspax -wv -a -f archive.pax -x cpio -T 0108100730/m foldertoarchive
You can also use the -T option with a date given in the above format
(yymmddhhmm, for details see the man page) to select those files to
unpack with hfspax -r. If you want to unpack files into existing folders,
then you should use the -k option, or hfspax will happily trash the existing
files for you, and replace them with those it unpacks. You can combine the
-k and -T (and other options) to produce quite powerful and selective commands,
such as
hfspax -rv -f archive.pax -k -T 0108100730/m
which will unpack only those files modified after the given date from
archive.pax, into the current working folder, but will not over-write
existing files.
sudo or su
Mac OS X has many features of Unix, including strict limitations on privileges
for users. Depending on whether the current user has admin powers, and the
permissions set for folders and files, you may need to assume additional powers
as a 'super user' before you can read or write them. Thus, you may find that you
need to preface any or all of the above commands with the sudo command. You can
also become the super-user ('root') with the su command. You should be extremely
cautious about doing so, because you can rapidly cause all sorts of problems and
damage unless you really – really – know what you are doing. If you do not know
how to use sudo, then you should read the relevant section of a good Unix guide,
and its man pages (man sudo).
File naming: an important issue
Mac OS X using an HFS+ volume has to cope with both Mac OS 9 and Unix file naming
conventions. When an operating system refers to a file using its full path name
(as hfspax has to do), it uses a separator character between each element in the
full path name. For instance,
/Users/me/Documents/test.rtf
specifies the file test.rtf in the path /Users/me/Documents. Unix uses the '/'
character as its separator, whilst Mac OS 9 uses the ':' character, e.g.
HacHardDisk:Users:me:Documents:test.rtf
If you create or keep files that include a separator in their name, this will
confuse tools such as pax, as the name will be seen to contain part of the
pathname as well. In OS X, this can happen if you use '/' or ':' characters
in file names. This will cause hfspax to break, and its behaviour will then
be unpredictable, and it will corrupt files. Currently, we do not know of a
workaround to help this unfortunate situation.
-
OS 10.1? Yes!
2001-10-13 15:39:12 mcamille [Reply | View]
I have been an OS X user since the beta release. I have an older iMac (333) with 256MB ram and I recently bought a G4 Powerbook (400) with 384 MB ram. I have been pleased with OS X since the official release, more pleased as it was revised and it matured.
As a recent (2 1/2 years only) Mac user and against the framework of extensive Windows and Unix experience, I can say that OS X won me over because of its stability, its Unix core, and Apple's artful GUI design.
I have never had trouble loading OS X , a fact best seen against my migration history: OS 8.6 -->OS 9-->OS 10 beta-->OS 10.xx-->OS 10.1. I did not create separate partitions. I just overwrote the old and kept going!
Yes, Classic has been too slow to load, no doubt about it. But that's a relatively minor inconvenience. Furthermore, I must add that my Office 98 apps have been fine against all these changes. This is important to me as I use Office 2000 at work and need to be able to move files around with no glitches between my Windows Office apps and my Mac Office apps.
Now why not ask me how much trouble I had loading NT 4.O -- both server and work station--when I needed to load those?
In fairness, Windows 2000 Professional is fairly easy to get up and running. And I would rate Win2000 Pro and OS X about the same in regards to ease of upgrading from their respective ancestors.
My only regret is that I must continue to use Office 98 in classic. I really like Office 98 and consider it a better suite than its Windows equivalent (I don't have a need for Access). And I think the Office for X is going to be too pricey. I will add here that I also just bought Appleworks 6.1, upgraded it for OS X and am absolutely delighted that it reads and saves Word and Excel files in Windows format. I don't have too much experience with the file conversions yet, but so far I am very pleased.
Complaints: only that Apple doesn't bundle with every new Mac and OS X CD a USB to serial conversion cable and the software to trick these USB machines into thinking they have serial com ports. I have not yet figured out how I am going to use my PowerBook to configure Cisco routers and switches via their console ports. But then again, that's not a problem most Mac users are faced with.
-
10.1 Fixed Classic
2001-10-04 10:37:04 stableos [Reply | View]
I couldn't get classic mode to start within OS X even after all of the updates to it and OS 9. Once 9.2.1 and 10.1 were installed, not only was OS X faster, classic mode worked like a charm.
-
Dev Tools back at ADC
2001-10-03 13:08:24 brickman [Reply | View]
Just after I post that, the Dev Tools for 10.1 are available at ADC. I now stand corrected by myself.
-
Dev Tools Die
2001-10-02 16:08:27 brickman [Reply | View]
One thing O'Reilly reads would most likely want to know is that the upgrade kills your installed Dev Tools.
I was able to reinstall the Dev Tools from ADC (still the old version), but I understand Apple has a new set they send out with the $19 upgrade (and I assume the $129 full version).
I have not fully tested the reinstalled Dev Tools too thoroughly, but it did compile a simple C++ and simple Java app.
-
Is your wallstreet playing dvd's
2001-10-02 13:46:22 zarembo [Reply | View]
Someone told me that DVD hardware is not supported in OS 10.1 Do you know if this is true? If so, have your heard whether Apple intends to support our DVD hardware pcmcia cards? Thanks.
-
9.2.1 Only Upgrades 9.1 or Later
2001-09-29 10:16:30 Derrick Story |
[Reply | View]
I want to clarify that the 9.2.1 CD included in the 10.1 upgrade package will only update Classic system 9.1 or later. This shouldn't be an issue if you've been using the standard Mac OS X install packages. But if you wanted to use the 9.2.1 CD to update other Macs at home, remember that they have to be 9.1 or later. -
Great Article...
2001-10-08 19:23:23 tjcrebs [Reply | View]
Derrick,
I used your Disaster-Free articles to install 10.1 on my Pismo. a few problems I encountered were:
1) getting DVD to run on my Pismo (Firewire PowerBook). DVD worked fine until I upgraded 9.1-Classic to 9.2.1--then the dreaded "Not configured error"--my fix was to reinstall OS-X-10.1. Runs fine now.
2) I recommend each time you install 9.2.1 or your backed up 9.1 System--restart from each OS-9 System after each installation to handle the networking and queries. I apparently crashed a couple OSX-10.1installations because I didn't .
3) Took me 4 installs to get OSX-10.1 to work great. Yup, I learn best from FUs.
Thanx again for the fine "Disaster-Free" articles.
Regards,
T. J. Crebs
Lakewood, CO USA
P.S. AOL 16B Beta works great undr 10.1.
-
Disaster-Free upgrade to OS 10.1
2001-09-29 01:45:55 maximus [Reply | View]
Hi there,
just wanted to add that the upgrade has been extremely successful even with a 'bubble' machine: PowerBook G3 Wallstreet, no USB, no FireWire. Originally a 266 MHz upgraded to 466MHz with Newer Technology, 192 MB memory.
Not even a single glitch! Apple really did a great job. Moreover, if you are into Unix you are going to love even more your Mac. I have installed XFree86 with XDarwin rootless and to me it is now like having a Unix portable workstation! With the GNU compiler 2.95.2 I installed Unix applications without any effort.
A truly traditional Apple drooling experience.
Thanks Apple,
forever yours!






