RE: [wpmac] WP/Mac on Intel-based Macs
- Thanks, Randy. It looks complicated, but there's hope. And some swear that 8.1 was the last decent pre-X OS (personally, I thought 8.6 should have had that title). So MacIntel machines aren't the end of my access to my old files. WPWin using Parallels for new stuff and
Basilisk for the old stuff. Does anyone know if there's a WP for Linux (Parallels can run that OS, too) and if it's more or less like WPMac than WPWin?
From: firstname.lastname@example.org on behalf of Randy B. Singer
Sent: Mon 5/8/2006 7:09 PM
To: email@example.com; WP-L@...
Subject: [wpmac] WP/Mac on Intel-based Macs
I know that a lot of Mac users have been hoping for a way to run Classic
on the new Intel-based Macs so that they can purchase a new Mac and
continue to use WordPerfect/Mac.
There is now a workable emulator for Classic for Intel-based Macintoshes.
The emulator is free (and open source) but it requires that you have a
ROM image from a 680x0 Macintosh, and since that ROM image is copyrighted
software, you can't download it from anywhere, you have to have an old
Macintosh that you can "capture" a ROM image from. The good news is that
old working Macs can often be found for free, in the closets of Mac user
group members, or for just a few bucks via a classified ad or in thrift
Basilisk II for OS X (free)
In order to make Basilisk II work, you need three things:
* The Basilisk II application. Since it's open source, it can be
* A copy of an older Mac operating system. Apple has made operating
system versions up to System 7.5.5 freely downloadable. You can find
links for a wide range of older Mac operating system versions on Low End
Mac's Classic Mac OS Downloads and Updates page:
Apple included 680x0 support in operating system versions up to Mac OS
8.1, so that's the last version that Basilisk II can run.
* An image file of the ROM from a 680x0 Mac. In general, you'll get
best performance from a more recent 68040 model. Apple retains copyright
on their ROM code, so you can't legally download these. Instead, if you
find a working older Mac, you can "capture" a ROM image (see Capturing a
Mac ROM Image)
Please let the rest of us know how this works for you.
Randy B. Singer
Co-Author of: The Macintosh Bible (4th, 5th and 6th editions)
Routine OS X Maintenance and Generic Troubleshooting
Yahoo! Groups Links
It's confusing, but not as bad in practice:
1) If you want to use it in a Classic Application, it has to be in
System Folder| Fonts. Equally, it has to be a Mac Font. In OSX,
Windows fonts work, too.
2) Don't do anything with the folder System| Library| Fonts. Leave it alone.
3) If you are the only user of your Mac, whether you use Library|
Fonts or ~| Library| Fonts is irrelevant. If you share it, fonts in
your Home Folder Library are only available to you.
4) In practice, WP has a very limited set of fonts while I have over
400 available under OSX applications spread around all four font
>--- In firstname.lastname@example.org, "Don V. Zahniser" <irntooth@...> wrote:
>> See <http://www.lowendmac.com/musings/06/0509.html>
>> for a potential problem relating to duplicate fonts.
>There are fonts all over the place on my machine. The
>standard OSX install has put them in four places:
>Library/Fonts (108 files)
>System (Mac OS 9)/Library/Fonts (17)
>System Folder/Fonts (54, some of which I added)
>The last is what we know as the classic System Folder.
>Fonts in the newer dfont file format are OSX-only I think,
>but otherwise I wonder why there are so many font folders,
>which takes priority when there are duplicates, and which
>folder you should add fonts to. The lowendmac.com article
>describes finding and disabling a duplicate but doesn't go
>further than that.
>Yahoo! Groups Links