Existing users, log in.  New users, create a free account.  Lost password?

  |    |    |  Beware moving your fonts to a new computer

Version:  

   [ Views: 493 ]

Beware moving your fonts to a new computer

Feedback Type:  Review

Contributed by: eduweb Sunday, September 26 2004 @ 02:53 PM PDT

Product Platform: MacOSX

Used Product For: 6-12 months

If you upgrade to a new machine, even if you use the Apple System Migration tool, you have to re-import all of your fonts on the new machine! That's right, say goodbye to your old sets and libraries. This is confirmed by Insider's tech support. If you just move all your old files to a new machine (even if they are placed in the same directories on the new machine), you'll be able to read your current fonts but not add any new ones to your library.<P>Insider just says that this is what you have to do and makes no apologies or promise they'll fix it in a future release.<p>Something else you can't do is allow multiple users of the same Mac to use the same library. How come? Because when you set up FAP for each user, you have to import fonts to your library -- you can't just say, "Here are my fonts, now put them in the database." It has to copy them into the new font library folders. So be prepared for duplicates in each user account if you have multiple users on one machine (even though you can share fonts between machines).<p>Overall the program is fairly easy to use and as others say, latest version is more stable and faster. It is more attractive and less messy than ancient old Font Reserve, and seems to cause less trouble than Suitcase. It's just a major PITA to set up when you move machines or have to rebuild your system.   
Overall Rating:

Ease of Use:

Support:

Features:

Quality / Stability:

Price:

1 of 1 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

1 comments |

Beware moving your fonts to a new computer - Welles Goodrich

I've moved my system to a new hard drive via cloning, always had a cloned external backup which works just fine and upgraded twice via archive and install without having the problem you describe. I will be cautious with a new computer now, though. Thanks for the warning.

Reply to This

Sunday, October 10 2004 @ 05:15 AM PDT