<?xml version="1.0" encoding="iso-8859-1"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>macosxhints.com Classic tips</title>
<link>http://www.macosxhints.com/index.php?topic=classic</link>
<description>Tips and tricks for using Classic (OS 9) in OS X.</description>
<managingEditor>webteam@macosxhints.com</managingEditor>
<webMaster>webteam@macosxhints.com</webMaster>
<copyright>Copyright 2010 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Mon, 08 Mar 2010 06:37:30 -0800</pubDate>
<language>en-gb</language>
<atom:link href="http://www.macosxhints.com/backend/hintsclassic.rss" rel="self" type="application/rss+xml" />
<item>
<title>Convert SWF files to QuickTime movies using Classic</title>
<link>http://www.macosxhints.com/article.php?story=20080211145226583</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20080211145226583</guid>
<pubDate>Tue, 19 Feb 2008 07:30:00 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20080211145226583#comments</comments>
<dc:subject>Classic</dc:subject>
<description>Recent versions of QuickTime haven't been able to open &lt;a href=&quot;http://en.wikipedia.org/wiki/SWF&quot;&gt;SWF&lt;/a&gt; files. For days, I've been searching for a way to convert a SWF animation to a QuickTime movie without having to downgrade QuickTime. Then I remembered -- I already have an old version of QuickTime on my system in Classic! Sure enough, the Classic version of QuickTime both opened the SWF and converted it into a QuickTime movie.
&lt;br&gt;&lt;br&gt;
You'll need to have Quicktime Pro in Classic to make it work, and newer versions of Flash are probably not compatible with the older version of QuickTime.</description>
</item>
<item>
<title>A fix for Outlook 2001 and daylight savings time</title>
<link>http://www.macosxhints.com/article.php?story=20070313155815194</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20070313155815194</guid>
<pubDate>Thu, 15 Mar 2007 07:30:02 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20070313155815194#comments</comments>
<dc:subject>Classic</dc:subject>
<description>So, I'm an IT admin, and this may have very limited use, but reading this site everyday has made my job easier many times. In the hopes that I can do the same for someone else...
&lt;br&gt;&lt;br&gt;
Outlook 2001 running under Classic with Exchange Server (devilish setup, I know, but common on Microsoft networks) does not respect the Daylight Savings change, even though OS 9 does. The &lt;a href=&quot;http://www.mactcp.org.nz/daylight.html&quot;&gt;Daylight Savings Editor&lt;/a&gt; will allow you to edit the time zones on OS 9 so that Outlook 2001 has the proper time.</description>
</item>
<item>
<title>Use MacOS 9 Finder in OS X</title>
<link>http://www.macosxhints.com/article.php?story=20061024112009845</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20061024112009845</guid>
<pubDate>Mon, 30 Oct 2006 07:30:00 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20061024112009845#comments</comments>
<dc:subject>Classic</dc:subject>
<description>I hear folks complain about missing the old classic Finder from OS 9 after upgrading to OS X. Well, as it turns out, you &lt;i&gt;can&lt;/i&gt; use the old Finder in OS X. What you need to do is change the type and creator codes of the Finder and it will launch just like a normal application. I used good ole ResEdit for this task, but you can use any program capable of modifying this setting. 
&lt;br&gt;&lt;br&gt;

Make a copy of the classic Finder. Get info on the classic Finder via ResEdit (or use your favorite program). Change the TYPE code to 'APPL' and the CREATOR code to something else (I used 'Sys9'). Save the file and you're done. 
&lt;br&gt;&lt;br&gt;

To avoid a generic icon on our launchable Finder, I copied the Finder icon out of the system finder (resources icl8, icl4, icn#, ics8, ics4, ics# if you're using ResEdit) and pasted them into the Finder's resource fork. I created a BNDL resource and matched the APPL icon to the Finder icon. You must also check &quot;Has BNDL&quot; in the info window for the icon to work....</description>
</item>
<item>
<title>Move mail from OS 9 Outlook Express to an Intel Mac</title>
<link>http://www.macosxhints.com/article.php?story=20061012031813924</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20061012031813924</guid>
<pubDate>Wed, 18 Oct 2006 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20061012031813924#comments</comments>
<dc:subject>Classic</dc:subject>
<description>&lt;b&gt;The problem:&lt;/b&gt;&lt;br&gt;
A friend has all his emails in Outlook Express on a G3 iMac running only Mac OS 9, and he wants to move them to his new Intel iMac. Unfortunately, Mail's import feature requires Outlook Express to be running. Thusly you need Classic, but Intel Macs don't have Classic.
&lt;br&gt;&lt;br&gt;
&lt;b&gt; The solution: &lt;/b&gt;
&lt;br&gt;
Part 1: Import from Outlook to Mail
&lt;ol&gt;
&lt;li&gt;On a PowerPC Mac with Mac OS X, create a new user account, &lt;i&gt;ImportUser&lt;/i&gt;, with admin privileges (System Preferences -&amp;gt; Accounts -&amp;gt; + button). Login as this user. After the importing, we will delete this account.&lt;/li&gt;
&lt;li&gt;Run Outlook Express in Classic (found in /Applications (Mac OS 9) -&amp;gt; Outlook Express 5.02 Folder -&amp;gt; Outlook Express) under this new user account to set up its initial directories, then quit Outlook.&lt;/li&gt;
&lt;li&gt;Copy the contents of /Documents -&amp;gt; Microsoft User Data from the Mac OS 9 computer to /Users -&amp;gt; ImportUser -&amp;gt; Documents -&amp;gt; Microsoft User Data on the PowerPC Mac OS X...</description>
</item>
<item>
<title>10.4: Automate 'print to file' printing from Classic</title>
<link>http://www.macosxhints.com/article.php?story=20060927134522963</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20060927134522963</guid>
<pubDate>Fri, 06 Oct 2006 07:30:03 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20060927134522963#comments</comments>
<dc:subject>Classic</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/tigerx2a.jpg&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;When I recently changed my workplace printers, I couldn't install the new printers in Classic. Since I print very seldom from Classic (but I do have one program that I have to use), I just used the Print to File option, and then printed the &lt;tt&gt;.ps&lt;/tt&gt; file with Preview.app in OS X. Then I realised that I could simplify things with the help of a LaunchAgent and a QueueDirectory.
&lt;br&gt;&lt;br&gt;
To achieve this, I started by making a small script that prints all files in a directory and removes them:


&lt;pre&gt;&lt;code&gt;#!/bin/bash

# Script to be called by launchd that prints all files 
# in the folder ~/classicprint/ and then deletes them

sleep 30
lp ~/classicprint/*
rm ~/classicprint/*
&lt;/code&gt;&lt;/pre&gt;


I saved the script as &lt;tt&gt;classicprint.sh&lt;/tt&gt;, and put it in my home directory and made it executable with &lt;tt&gt;chmod a+x ~/classicprint.sh&lt;/tt&gt;. I also made a new directory in my home drectory and ...</description>
</item>
<item>
<title>The Apple-approved method of removing Classic</title>
<link>http://www.macosxhints.com/article.php?story=2006090904090456</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2006090904090456</guid>
<pubDate>Tue, 12 Sep 2006 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2006090904090456#comments</comments>
<dc:subject>Classic</dc:subject>
<description>There are older tips on removing Classic, such as &lt;a href=&quot;http://www.macosxhints.com/article.php?story=20050430120117382&quot;&gt;this one&lt;/a&gt;, but I've found the official (Apple sanctioned) way to remove Classic (which is different from prior hints). I found the following method in the Tiger Security Configuration Guide (&lt;a href=&quot;http://images.apple.com/server/pdfs/Tiger_Security_Config.pdf&quot;&gt;3MB PDF&lt;/a&gt;) -- and the rest of the document is also quite interesting.
&lt;br&gt;&lt;br&gt;
Read on for Apple's recommend procedure for removing Classic...
This is taken verbatim (except for some formatting changes) from page 32 of the above-linked PDF...
&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Warning: Incorrectly entering any of the commands described in this task can erase critical data. Pay particular attention to correctly entering single quotes. Misplacing these single quotes can result in the removal of Mac OS X or applications.&lt;/strong&gt;
&lt;br&gt;&lt;br&gt;
To remove Mac OS 9 and Mac OS 9 applications and files:
&lt;ol&gt;
&lt;li&gt;Log in to Mac OS ...</description>
</item>
<item>
<title>Fix 'broken Classic apps after new Mac migration</title>
<link>http://www.macosxhints.com/article.php?story=20060719072306358</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20060719072306358</guid>
<pubDate>Fri, 21 Jul 2006 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20060719072306358#comments</comments>
<dc:subject>Classic</dc:subject>
<description>I recently upgraded from a G4 tower to a spanking new G5 Quad, and since my old computer was in tip-top shape I thought I'd save myself some setup time by choosing to &quot;migrate&quot; all the data from the old computer to the new one. 
&lt;br&gt;&lt;br&gt;
Everything seemed to go well...I fired up the new G5 and was pleased to see it basically looked and felt like my old system, with all my folders and apps where I expected to find them. I noticed, however, that some 'migrated' folders had the tag &lt;em&gt;(from old Mac)&lt;/em&gt; added to their names. Very helpful, I thought, that the migration process tagged these folders this way lest I lose track of what was old and what was new on my computer.
&lt;br&gt;&lt;br&gt;
The problem this seems to cause, however, is that a few of my Classic apps (I know, I know ... a G5 Quad and I'm still running Classic. I am merely a prisoner of the slow-to-upgrade corporate environment in which I work!) lost track of where they could find extensions, plug-ins, etc. that they needed to func...</description>
</item>
<item>
<title>How to run Classic (pre OS X) apps on Intel Macs</title>
<link>http://www.macosxhints.com/article.php?story=20060509180914879</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20060509180914879</guid>
<pubDate>Tue, 16 May 2006 08:00:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20060509180914879#comments</comments>
<dc:subject>Classic</dc:subject>
<description>Do you use an Intel-based Mac but still have a few essential Classic (pre-OS X) Mac applications you want to run? Recent universal compiles allow you to use &lt;a href=&quot;http://www.gibix.net/dokuwiki/en:projects:sheepshaver&quot;&gt;SheepShaver&lt;/a&gt; (SS) or  &lt;a href=&quot;http://www.gibix.net/dokuwiki/en:projects:basilisk2&quot;&gt;Basilisk II&lt;/a&gt; (B2) to run Classic software in emulation on Intel Macs under Mac OS X directly -- or under Windows via dual-boot or &lt;a href=&quot;http://www.parallels.com/en/products/workstation/mac/&quot;&gt;Parallels&lt;/a&gt; virtualization. B2 emulates an old 68K Macintosh, while SS emulates a PowerPC Mac.
&lt;br&gt;&lt;br&gt;
&lt;b&gt;What you need:&lt;/b&gt;
&lt;ol&gt;
&lt;li&gt;An old Mac OS (up to OS 8.1 for B2, or OS 7.5.2 through 9.0.4 for SS). You can  &lt;a href=&quot;http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/Older_System/System_7.5_Version_7.5.3/&quot;&gt;get OS 7.5.3 for free&lt;/a&gt; from Apple. E-Maculation has a downloadable OS 7.5.3 starter disk already prepared ( ...</description>
</item>
<item>
<title>Print from Pagemaker in Classic to PDF</title>
<link>http://www.macosxhints.com/article.php?story=20060330133446978</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20060330133446978</guid>
<pubDate>Wed, 05 Apr 2006 05:55:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20060330133446978#comments</comments>
<dc:subject>Classic</dc:subject>
<description>When you are running Classic, you have switched to the Adobe printer in the Chooser, and you try to File/Export a Pagemaker document to PDF, Pagemaker works for a few seconds, and then opens Acrobat Distiller. Distiller then works for a few seconds, but then stops with an error message.
&lt;br&gt;&lt;br&gt;
To work around this, click the Pause button which shows in Distiller as soon as it opens. In the same folder with your original file (which, of course, should be a copy of your real original), you will find a temporary file called &lt;tt&gt;myfile.ps&lt;/tt&gt;. Now open this PostScript file with Preview, and Preview will automatically convert it to a PDF. Save it now and unpause Distiller. The PostScript file disappears, but you are left with the PDF.</description>
</item>
<item>
<title>10.4: Avoid Spotlight issues when adding Classic</title>
<link>http://www.macosxhints.com/article.php?story=2005092917445498</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2005092917445498</guid>
<pubDate>Tue, 04 Oct 2005 05:44:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2005092917445498#comments</comments>
<dc:subject>Classic</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/tigerx2a.jpg&quot; alt=&quot;Tiger only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Here's a little heads-up concerning Classic. Do &lt;em&gt;not&lt;/em&gt; move an OS 9.2.2 System folder from another computer to a 10.4 Mac. This will confuse Spotlight (it will crash trying to index the other non-extistent computer). Also, in the Advanced section of the Classic preferences panel, check the 'Use Mac OS 9 preferences from your home folder' box. Install a new System folder from an OS 9.2.2 install disk, and you'll be good to go.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; I can't confirm this glitch, as I no longer have Classic installed on any of my machines. If someone can confirm or deny, I'd appreciate it.]</description>
</item>
<item>
<title>Pause Classic when not in use</title>
<link>http://www.macosxhints.com/article.php?story=20050712175556873</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20050712175556873</guid>
<pubDate>Wed, 20 Jul 2005 08:55:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20050712175556873#comments</comments>
<dc:subject>Classic</dc:subject>
<description>Occasionally, I still need to run some apps in Classic. When I do, it's annoying that Classic uses a good chunk of my CPU (30%-60%) even when it's in the background doing nothing. One fix for this is to pause Classic by sending the TruBlueEnvironment process a stop signal, like so:

&lt;pre&gt;&lt;code&gt;killall -STOP TruBlueEnvironment&lt;/code&gt;&lt;/pre&gt;

This will pause Classic so that it doesn't eat your CPU. When you're ready to use Classic again, unpause it by doing this:

&lt;pre&gt;&lt;code&gt;sudo killall -CONT TruBlueEnvironment&lt;/code&gt;&lt;/pre&gt;

You have to use &lt;tt&gt;sudo&lt;/tt&gt; because attempting to restart the process as a regular user will result in an &quot;Operation not permitted&quot; error. I haven't yet been able to figure out why this is.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; You can use this technique to pause any process, as explained in &lt;a href=&quot;http://www.macosxhints.com/article.php?story=2002083005465815&quot;&gt;this hint&lt;/a&gt;.]</description>
</item>
<item>
<title>10.4: Use older Sherlock to search by filename</title>
<link>http://www.macosxhints.com/article.php?story=20050622204527771</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20050622204527771</guid>
<pubDate>Wed, 06 Jul 2005 08:45:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20050622204527771#comments</comments>
<dc:subject>Classic</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/tigerx2a.jpg&quot; alt=&quot;Tiger only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Sometimes one needs to just search for a certain filename (like it was possible in 10.3 and before) without indexing the volume first. People have tried the strangest setups to achieve this, but there is actually a much easier way -- without installing any third party utilities: Sherlock 2!
&lt;br&gt;&lt;br&gt;
Never used before (at least by the submitter), suddenly it now seems like a great app. Select the &quot;find file&quot; mode, enter the filename and search away, super fast. Beware: Needs Classic!
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; I no longer have any Classic apps installed, so I can't easily test this one...]</description>
</item>
<item>
<title>10.4: A fix for certain Classic apps not starting</title>
<link>http://www.macosxhints.com/article.php?story=2005060607254295</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2005060607254295</guid>
<pubDate>Tue, 21 Jun 2005 09:39:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2005060607254295#comments</comments>
<dc:subject>Classic</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/tigerx2a.jpg&quot; alt=&quot;Tiger only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;I had a couple of Classic applications that had been refusing to open since an Archive &amp; Install upgrade to Tiger. They would show up as only an &quot;application&quot; in the Get Info window, and would also say that they were set to Open with Script Editor. Double clicking on them would result in Script Editor launching and complaining about being unable to load the dictionary.
&lt;br&gt;&lt;br&gt;
I did a search on the Apple discussions areas a couple of weeks ago with no luck -- the same search tonight turned up &lt;a href=&quot;http://discussions.info.apple.com/webx?14@781.x9I1a7ac197.490217@.68af6176&quot;&gt;this thread&lt;/a&gt; in which the suggested fix was to add a &quot;.app&quot; extension to the offending program(s). This did work, but it got me thinking that maybe the problem was related to file extension interpretation.
&lt;br&gt;&lt;br&gt;
When I looked at the names of all the programs affected, I saw that they al...</description>
</item>
<item>
<title>Remove Classic cleanly</title>
<link>http://www.macosxhints.com/article.php?story=20050430120117382</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20050430120117382</guid>
<pubDate>Thu, 05 May 2005 14:45:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20050430120117382#comments</comments>
<dc:subject>Classic</dc:subject>
<description>When I updated to 10.4, I realized I hadn't used Classic for a very long time. I wanted to remove it, and prevent the Classic System Preferences pane from appearing. Lots of hints describe messing with the system parts to do this, but it felt pretty untidy to me, so here's what I did.
&lt;br&gt;&lt;br&gt;
You can't simply trash the &lt;tt&gt;System Folder&lt;/tt&gt; that is used for OS 9, as a booted OS X won't let you -- it says it's in use. I rebooted in single user mode (hold Command-S at startup), mounted the drive writable and removed it that way. Once at the singleuser prompt, do

&lt;pre&gt;&lt;code&gt;&amp;#36; mount -uw /
&amp;#36; cd /
&amp;#36; rm -rf 'System Folder'
&lt;/code&gt;&lt;/pre&gt;

&lt;b&gt;Be &lt;em&gt;very&lt;/em&gt; careful with your spaces and escapes, or it's bye-bye to the &lt;tt&gt;/System&lt;/tt&gt; folder (the actual OS X folder!), which would be very bad.&lt;/b&gt;
&lt;br&gt;&lt;br&gt;
That's the system taken care of.
Now you can reboot and remove &lt;tt&gt;/Applications (Mac OS 9)&lt;/tt&gt; from your disk -- the Finder lets you do this just fine. Now to fix things u...</description>
</item>
<item>
<title>Print from Classic using native OS X printer drivers</title>
<link>http://www.macosxhints.com/article.php?story=2005030316173578</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=2005030316173578</guid>
<pubDate>Fri, 04 Mar 2005 08:14:00 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=2005030316173578#comments</comments>
<dc:subject>Classic</dc:subject>
<description>There have been a few other hints posted describing how to send jobs directly to CUPS via the command line. At the school where I work (with over 500 Macs), we've been using our own version of this idea since September, with great results.
&lt;br&gt;&lt;br&gt;
Since most of our printers are on our network, rather than being connected locally, handing off print jobs from Classic to OS X allows us to:

&lt;ol&gt;&lt;li&gt;Eliminate all Classic printer drivers except for LaserWriter 8&lt;/li&gt;
&lt;li&gt;Print from Classic via TCP/IP easily&lt;/li&gt;
&lt;li&gt;Make clear to our users which printer they're printing to&lt;/li&gt;&lt;/ol&gt;

This helps keep our administrative overhead down by letting us ignore Classic printing specifics, eliminate the Chooser, and keep AppleTalk (which never worked very well in OS X) turned off. The big difference between our method and those that have already been published is that we get feedback about our printing jobs through the regular Panther interface (i.e., the Printer Setup Utility and the printer pro...</description>
</item>
<item>
<title>Printing to any printer from Classic</title>
<link>http://www.macosxhints.com/article.php?story=20041007072143915</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20041007072143915</guid>
<pubDate>Tue, 12 Oct 2004 09:44:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20041007072143915#comments</comments>
<dc:subject>Classic</dc:subject>
<description>I still use WordPerfect and Freehand 9** on a regular basis; both are non-Carbonized applications, and run under Classic. This is all well and good until it's time to print. For Freehand, since I'm usually printing weird paper sizes, I have to plug my USB DeskJet printer into my laptop and print directly. But if I'm printing standard letter size, I really wanted to be able to print to the old PCL laser printer connected to the house server. But printer sharing only works from OS X. What to do?
&lt;BR&gt;&lt;BR&gt;
Simple. Set up a Folder Action. It works like this: in Classic, I choose the LaserWriter8 (or some other PostScript printer driver) in the Chooser. Then I &quot;print&quot; to a file, not the printer, and save the resulting file to a folder (that I've already bookmarked for convenience) that I call &quot;Printing Box.&quot; I usually save it as PDF, but that might be an option I have just because I have full Adobe Acrobat installed. I modified my script so that you don't need Acrobat to make this hint wo...</description>
</item>
<item>
<title>Consistent app launching from 9 to X</title>
<link>http://www.macosxhints.com/article.php?story=20040910224942554</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20040910224942554</guid>
<pubDate>Mon, 13 Sep 2004 09:58:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20040910224942554#comments</comments>
<dc:subject>Classic</dc:subject>
<description>This one is for users, like me, who need access to OS 9 applications (WordPerfect and games) now and then. It's actally kind of lame, but I haven't seen it anywhere else -- maybe it will help someone.
&lt;BR&gt;&lt;BR&gt;
Apple did a fantastic job with Classic, but there's kind of a culture shock associated with going back and forth between Classic and OS X. One of my biggest problems was the inconsistency between applications available from OS 9 and OS X. I've come up with the following configuration that seems to cover all the bases.
&lt;BR&gt;&lt;BR&gt;
The main consideration is whether or not you have Classic configured to use preferences from the global Classic environment or from your Home account (this is in the Advanced tab of the Classic preferences panel). If you are running preferences from home, make sure you have the folder ~/Library -&gt; Classic -&gt; Launcher Items. If you don't, you may have to do a little finagling -- this might include launching Launcher (from Control Panels) and/or copying /S...</description>
</item>
<item>
<title>Print from Classic and OS X with an HP Laserjet 1012</title>
<link>http://www.macosxhints.com/article.php?story=20040904000442505</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20040904000442505</guid>
<pubDate>Tue, 07 Sep 2004 08:52:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20040904000442505#comments</comments>
<dc:subject>Classic</dc:subject>
<description>After my trusty Personal LaserWriter 300 finally died, I bought an HP LaserJet 1012, in no small part because of the heavily-advertised Apple compatibility.  Let's just say I found HP's Apple support leaving me with something to be desired (*cough* like support *cough*). I finally got the printer to work under OS X, but could never get it to work with applications running in the Classic environment.  As a workaround, I would save documents as Postscript files and then use Preview to convert to PDF before printing.  A relatively simple workaround, but not an optimal solution.
&lt;p&gt;After searching everywhere (including HP's website) for a solution, I decided to check &lt;a href=&quot;http://www.macupdate.com&quot;&gt;MacUpdate&lt;/a&gt; for updated printer drivers.  I didn't find one for the LaserJet 1012, but I did find &lt;a href=&quot;http://www.macupdate.com/info.php/id/5680&quot;&gt;this one&lt;/a&gt; for the color LaserJet (version 1.52).  I decided to try it despite poor reviews on MacUpdate.
&lt;p&gt; The installer said it was ...</description>
</item>
<item>
<title>An OS 9 / Classic fix for unmountable FireWire drives</title>
<link>http://www.macosxhints.com/article.php?story=20040827005041917</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20040827005041917</guid>
<pubDate>Fri, 27 Aug 2004 10:07:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20040827005041917#comments</comments>
<dc:subject>Classic</dc:subject>
<description>I have had a ongoing problem with miscellaneous FireWire drives that won't mount. Clicking on the grayed-out drive in the Disk Utility only creates an endless beachball. After trying DiskWarrior, Data Rescue, and other various tools that were no help, I tried booting into OS 9 (sorry newer Mac owners) and the drive immediately showed up on the desktop. When I booted back to OS X, all was well and the disk just worked.
&lt;BR&gt;&lt;BR&gt;
Next time it happened, I just started Classic and the drive came right up. I don't know how or why it happens, but it has worked with other clients' computers, as well.</description>
</item>
<item>
<title>Access recent Classic documents from the dock</title>
<link>http://www.macosxhints.com/article.php?story=20040715225528340</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20040715225528340</guid>
<pubDate>Tue, 20 Jul 2004 08:51:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20040715225528340#comments</comments>
<dc:subject>Classic</dc:subject>
<description>As someone who still used a bunch of Classic apps -- sometimes with no choice, like QuarkXpress, sometime just becuase I like to use fast old apps when appropriate (Photoshop 3.0 is FAST for simple things), I am often frustrated that my recent documents don't show up in the OSX 'recent item' option in the apple menu. I used to keep the Chooser, or some other control panel (the Classic Calculator works, too) in the dock, just to have a lightweight application launch to give me the Classic Apple menu, with its Recent Docs and Recent Apps options.
&lt;BR&gt;&lt;BR&gt;
But then I remembered that those Classic menu options reference a directory on the hard drive, so I just put that folder in the dock. To find it, just go to the Classic Apple menu, choose Recent Documents and let go without choosing a document. You'll see the folder opened in the Finder. Use Command-3 to see column view and drag the Recent Documents folder to the dock. I love having the click-and-hold access to the list of documents ...</description>
</item>
</channel>
</rss>
