FontLab Forum
December 03, 2008, 06:57:32 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: SMF - Just Installed!
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Can't get Fontographer to start up  (Read 829 times)
1940LaSalle
Newbie
*

Karma: +0/-0
Posts: 1


View Profile
« on: July 20, 2008, 09:17:27 PM »

Hi, everyone.  I've seen this software used and it looks great, but I can't get past one problem despite repeated uninstall/reinstall attempts.  Whenever I fire it up, I get an error message telling me there's not sufficient memory to load, along with a cryptic "Code = -30202" notation.  That strikes me as odd, since my machine has 2GB of memory, and can run far more demanding software (e.g., AutoCAD).

Anyone know how to deal with this?  Thanks.
Logged
Alex Petrov
Global Moderator
Jr. Member
*****

Karma: +1/-0
Posts: 56


View Profile WWW Email
« Reply #1 on: July 22, 2008, 12:32:57 PM »

"Code = -30202" notation. 

Fontographer FAQ: http://www.fontlab.com/contact-and-support/product-faqs/faq-fontographer.html
Logged

Alex Petrov
lev
Newbie
*

Karma: +0/-0
Posts: 1


View Profile
« Reply #2 on: August 01, 2008, 01:54:01 PM »

I was not able to start Fontographer on WinXP too and the mentioned FAQ didn't help me, but finally I found Metacreations Fix which had solved this problem.
Logged
Hairius
Newbie
*

Karma: +0/-0
Posts: 3


View Profile Email
« Reply #3 on: August 04, 2008, 06:40:19 PM »

Since FOG won't install on a system with more than 512 megs of memory because it thinks there isn't enough memory if you have more than that, another solution in addition to tweaking the virtual memory before installation is to tweak the memory itself by turning off your computer and taking out enough memory sticks to give yourself only 512 megs.  Then turn on the computer, install FOG, turn the computer back off, and put the rest of the memory back on the motherboard.  (Of course, this is only going to work if you have memory modules of 512 megs each; if you've got modules of 1G each, this isn't going to work...)
Logged
Der FontMeister
Jr. Member
**

Karma: +1/-0
Posts: 84


View Profile
« Reply #4 on: August 06, 2008, 02:10:14 PM »

Yep -this is the answer

--> Fontographer FAQ: http://www.fontlab.com/contact-and-support/product-faqs/faq-fontographer.html

Jimmy G.
Logged
Kazzz
Newbie
*

Karma: +0/-0
Posts: 1


View Profile Email
« Reply #5 on: August 18, 2008, 02:10:53 PM »

I use a program called "Resplendent Resolver"   http://www.resplendence.com/resolver

Using this program, Fontographer works fine. 

The settings I used are on my home computer, but I think I set the memory to 300k.  If you want me to look it up send an email to Kazzz@Rocketmail.com
Logged
Der FontMeister
Jr. Member
**

Karma: +1/-0
Posts: 84


View Profile
« Reply #6 on: August 19, 2008, 12:46:34 PM »

Issue
Fontographer crashes with a -30202 error in Windows NT or Windows 2000
Reason
There have been a few reports of this error which we have not been able to reproduce. The only
evidence that has surfaced is that the error is related to an internal problem with the operating system.
The -30202 error is listed among Microsoft's error messages as "an invalid 16 bit application is installed.
The Vdd registry entry is invalid." Fontographer is a 32 bit application and there is nothing 16 bit that Fontographer is installing.
The error message is bogus. In reality, the problem seems to be a RAM allocation issue.

Solution 1
Our suggestion is that you edit the Virtual Memory settings in order to function with Fontographer's older memory management.
Macromedia cannot offer tech support on how to set Virtual Memory for your machine. For detailed instructions on Virtual Memory settings see Microsoft tech note Q259184.
Use Microsoft's tech note to navigate to Settings > Control Panel > System > Advanced and then select the Performance Options button and then the Change button under the Virtual Memory group. Most users have been successful while using settings of 500mb for Initial and 500mb for Maximum. The most likely reason is that Fontographer was written before the large memory models used today were available.
Set the Initial and Maximum sizes both to the same value. It is recommended that you select a
partitioned drive, if one is available and has sufficient free disk space..
Be sure to click on the Set button to apply the new settings.
Restart your machine and attempt to run Fontographer. If Fontographer runs, your next challenge will be to see if the smaller Virtual memory setting affects the performance of other applications. If this is the case, you will need to use the new settings when using Fontographer and create a Hardware Profile to restart the machine with the old settings for running your system normally.
If you still get the -30202 error, try Solution 2 as listed below.

Solution 2
Some users who have reinstalled Windows and then reinstalled Fontographer in Safe Mode or NT VGA mode have been able to work around this problem.
Try reinstalling Fontographer in Safe Mode.
1. Start > Settings > Control Panel > Add/Remove - use this control panel to remove Fontographer - do NOT drag Fontographer to the trash. If there is a message stating that "not all items could be removed", the Windows Registry has trash in it which must be removed. All occurrences of Fontographer items in the Registry must be deleted. FontLab Ltd. cannot be responsible for editing which users make to the Registry.
2. Insert the Fontographer CD and drag the Fontographer setup.exe installer to the C: drive
3. Restart the machine in Safe mode - i.e., holding down F8 while restarting. Or select NT VGA mode when restarting NT.
4. Double-click the setup.exe installer
5. Restart in normal mode
If this doesn't work, reinstalling Windows has worked for some users. After the software has successfully installed, reboot the system again. Launch Fontographer (you'll need to reenter the serial number) and try working with Fontographer again, to see if the issue has been resolved.

Solution 2
Here's a technique which has worked for some people...

Editing BOOT.INI to add a second WinXP configuration with /MAXMEM=1024,
to limit the available physical memory to 1GB - in conjunction with the 500MB Virtual Memory setting.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.4 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!