Will Fontographer install into Vista? 64-bit Vista?

[Ted Harrison (FontLab)]

The new FOG5 (to be released in September, hopefully) will install and run on Win Vista and Win 7 without problems.

[Shanafeg]

I'll be looking forward to it.  And despite the requests for all sorts of new features such as Open Type support, I'll be perfectly happy if the program is just like it is now except that it will run on the 64-bit systems.  Actually, what worries me about upgrades is that in "improving" one thing, the programmers screw up or delete some other feature that was fine just as it was.  So, please be careful...

[ddennis]

Okay, how do I do step 2? Don't want anything to blow up.

Thanks
DD

Fontographer runs on WinXP.
Problem is a memory management of this old program.

You have 2 options:
1. Remove DIMM(s) to reduce amount of virtual memory to <2GB
2. Patch the function ASI_SetMemoryLimits() in FONTG410.dll file to set the limit in software.
Patch offset =  0x000812E8
Old data  = 00 00 00 00
New data = FF FF FF 7F

May be in next version of fontographer this function will be called on start up and limit set in more human way. 

[aniesaron]

I wanna know , Will Fontographer install into windows 7?

[Alex Petrov (FontLab)]

Yes, Fontographer 4.1.5 installs and runs perfectly on Windows 7? You must run it as administrator for the first time to serialize.

[Alex Petrov (FontLab)]

Okay, how do I do step 2? Don't want anything to blow up.

Thanks
DD

Here is the file for you to update FOG:
FOG415MemoryPatch.zip

[Malibu]

I tried the patch and it says my 4.1.5 version is already done and nothing to do.

I know I have never patched anything and have always had the problem unless I lower the RAM amount.

Does anyone have just the dll file that is needed???

[Shanafeg]

This is strange.  I installed the original FOG DLL on my system, and FOG failed to run because of too much memory.  Then, I ran the patch on it.  After that, when I reran FOG, FOG ran as normal -- the patch worked.  Then, I ran the patch installer on the patched version of the file and got the same error you report.  But FOG on your system still doesn't work?  Two questions:

1. How much memory do you have?
2. Are you running the 32-bit or 64-bit version of Windows?  The patch fixes the problem if you have more memory in your system than FOG originally expected, but it does not allow FOG to run in a 64-bit environment.

[Malibu]

I have 2 gig Ram and Windows XP 32bit Service Pack 2.

I have been using another fix which has worked well.

http://dev.depeuter.org/metacreations_fix_30.php?print=all

Appears several older programs have the plagued "memory" problem.  Several have reported back that it works well on Fontographer and I concur.

The nice thing about this fix is you can undue the fix as easy as applying the fix.

Hope this helps!

[Shanafeg]

Good to hear that you've got FOG working, though I still don't understand why the patch didn't do the trick for you.  I've got XP with 3 gig and Service Pack 3 and FOG works great!  The only problem is that I'm too busy with other things to work on any new fonts at the moment...

[Matchfonts]

Dear Mauzeris,

This seems great, but could you be so kind to indicate which program must be used to proceed with this patch ?

TIA

Fontographer runs on WinXP.
Problem is a memory management of this old program.

You have 2 options:
1. Remove DIMM(s) to reduce amount of virtual memory to <2GB
2. Patch the function ASI_SetMemoryLimits() in FONTG410.dll file to set the limit in software.
Patch offset =  0x000812E8
Old data  = 00 00 00 00
New data = FF FF FF 7F

May be in next version of fontographer this function will be called on start up and limit set in more human way. 

[mauzeris]

Look 5 posts above for FOG415MemoryPatch.zip

[IslayJohn]

Yes, Fontographer 4.1.5 installs and runs perfectly on Windows 7? You must run it as administrator for the first time to serialize.

Hi.  I realise that it's a long time since that post, and my words may just get lost in the ether, but I'd like to ask for a bit more detail, please, Alex (or anyone else who knows the answer).  Are you saying that under Windows 7, Fontographer does not give the memory problems that have been reported with earlier OSs, and does not suffer from the DLL conflict that arose with even earlier OSs?  I have just resurrected my old machine running ME specifically to use Fontographer, but the workarounds appear to have stopped working altogether, so I need to find a way to move on.  I'm not keen to invest in Fontographer 5 as my usage is very occasional and v.4.1.5 does everything I need to do - when I can get it to work.  My main PC runs Vista 32-bit, and I can't see anything in the posts that suggests there is any way to get v.4.1.5 working with that - or am I missing something?

[Alex Petrov (FontLab)]

Have you tried to use the patch?:
FOG415MemoryPatch.zip

[IslayJohn]

Have you tried to use the patch?:
FOG415MemoryPatch.zip

Hi Alex.  Thanks for your reply.  Yes, I have tried to use the patch, but like Malibu 7 posts above I received a message that the patch has already been applied and there is nothing to do, which is not true.  Just in case the patch was applied in spite of this message I tried to run Fontographer again and still got error 30202.  In desperation I have now resorted to a hex editor to edit fontg410.dll using the parameters which one of your contributors posted earlier, and Fontographer now appears to work.  Thanks for putting me on the right trail, and thanks to your contributor (I think it was Mauzeris) for coming up with the code.

[Tags:]

Jump to: Please select a destination: ----------------------------- News and announcements ----------------------------- => Announcements from the forum’s moderators => News from the font industry ----------------------------- Type design and font technology ----------------------------- => Principles of type design => OpenType Layout feature development => Hinting => Font Formats and OpenType => Web font embedding => Font licensing ===> Electronic EULA Abstract (EEULAA) ----------------------------- Education and collaboration ----------------------------- => Work: Offers => Work: Looking for => Education: Offers => Education: Looking for => Typographic Events and Conferences ----------------------------- FontLab products ----------------------------- => News from FontLab => FontLab Studio ===> FontLab Studio Problems ===> FontLab Studio Tips and Tricks ===> FontLab Studio Wish List ===> FontLab Studio Public Preview => Fontographer ===> Fontographer Problems ===> Fontographer Wish List => TypeTool => AsiaFont Studio => TransType => ScanFont => SigMaker => Other Products ----------------------------- Photofont products ----------------------------- => BitFonter => Photofont WebReady => Photofont Start => Photofont ID => Photofont QX => The Photofont technology ----------------------------- Adobe Type products ----------------------------- => Adobe FDK for OpenType (AFDKO) ----------------------------- Apple Font products ----------------------------- => Apple Font Tools ----------------------------- Microsoft Typography products ----------------------------- => Microsoft Font Validator => Microsoft Visual OpenType Layout Tool (VOLT) => Microsoft Web Embedding Fonts Tool (WEFT) => Microsoft Visual TrueType (VTT) ----------------------------- Other products and Python scripting ----------------------------- => Python scripting => FontTools/TTX => Other font-related tools ----------------------------- Special interest groups ----------------------------- => SBL Fonts ===> SBL Hebrew ===> SBL Greek ===> SBL BibLit ----------------------------- FAQ and TechNotes ----------------------------- => OpenType Layout feature development FAQ and TechNotes => Hinting FAQ and TechNotes => Font Formats and OpenType FAQ and TechNotes => Web font embedding FAQ and TechNotes => Font licensing FAQ and TechNotes => FontLab Studio FAQ and TechNotes => Fontographer FAQ and TechNotes => TypeTool FAQ and TechNotes => AsiaFont Studio FAQ and TechNotes => TransType FAQ and TechNotes => ScanFont FAQ and TechNotes => SigMaker FAQ and TechNotes => BitFonter FAQ and TechNotes => Photofont WebReady FAQ and TechNotes => Photofont Start FAQ and TechNotes => Photofont ID FAQ and TechNotes => Photofont QX FAQ and TechNotes ----------------------------- Archive (MSN Groups) ----------------------------- => Archive: Old FontLab forum ===> Archive: FontLab Tips and Tricks ===> Archive: FontLab Bugs and Problems ===> Archive: FontLab Wish List ===> Archive: FontLab Announcements => Archive: Old Microsoft Font Validator group => Archive: Old Microsoft VOLT group => Archive: Old Microsoft VTT group ===> Archive: VTT Downloads ===> Archive: VTT Support ===> Archive: VTT Suggestions => Archive: Old Microsoft WEFT group ===> Archive: WEFT III ===> Archive: EOT for Email => Archive: Old SBL Fonts group ===> Archive: SBL Hebrew ===> Archive: SBL Greek ----------------------------- Various ----------------------------- => fontlab.com — the FontLab website => forum.fontlab.com — this forum => Other Topics