Moon Software Forum
Moon Software Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 Knowledge Base
 Font Xplorer
 KB: Access violation in module FXplorer.exe
 Forum Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ahto/Moon Software
Developer

Estonia
1137 Posts

Posted - 29 August 2005 :  12:32:45  Show Profile  Visit Ahto/Moon Software's Homepage
Sometimes it may happen that when browsing fonts from a disk folder you see cryptic "Access violation at address NNNNNNNN in module FXplorer.exe" error message. This usually happens when one or more fonts in that folder are invalid or non-standard. This document provides information about how to solve this problem. Also, we are very interested to get access to the fonts that cause this kind of unhandled errors so we can improve the program to handle all kinds of invalid fonts better. Please take this additional step and send the bad fonts you found to us for investigation, along with your system information (Help | Copy System Info) and short description of the problem.

If this error message is displayed when browsing a folder then your only option is to try to sort out what font exactly causes this problem. It is unlikely that all fonts in that folder are problematic, usually just a few. This job may be time consuming, depending on how many fonts you have in that folder -- the more fonts the more time it takes to find the one that causes the problem.

General idea to find the bad font(s) is to just test all the fonts in that folder one by one or in batches. You can do it that way:

1) Copy all fonts in the folder that is problematic to another location, like X:\Fonts. You'll need to do this copy funciton because later we will delete them from that new folder, one by one. Use Windows Explorer to copy the fonts because you had problem with Font Xplorer.
2) Make 2 new folders named X:\FontsTest and X:\FontsBad.
3) Open 2 Windows Explorer windows for X:\Fonts and X:\FontsTest folders, move them side by side so you can see the contents of both folder. The first one should show your fonts and another is currently empty.
4) Open Font Xplorer and browse to X:\FontsTest folder. No fonts are displayed since the folder is currently empty. Now you are ready to perform the actual testing to find out which font from your X:\Fonts folder is invalid.
5) Now, using the mouse, drag first font from your X:\Fonts folder to the X:\FontsTest folder. This will move the font from one folder to another.
6) Switch to Font Xplorer and press F5 key (or choose View | Refresh command), that will refresh the font list. Now there is 2 possibilities, the font will show up in Font Xplorer list or you'll see an error message instead:
a) If you see the font proprly in Font Xplorer list and no error messages were displayed, then this font is OK. Continue to step 7.
b) If you see the "Access violation at address NNNNNNNN in module FXplorer.exe" error message or any other Font Xplorer error message about problem loading fonts, you have found a problematic font. Move the font, using Windows Explorer, from X:\FontsTest folder to X:\FontsBad folder. If it is not possible to move the font (Access denied error etc), you may need to temporarily point Font Xplorer to another folder, while moving the font. Continue to step 8.
7) We now delete the font to keep our X:\FontsTest folder clean. In Font Xplorer list, select the font and press Del key (or choose Font | Delete from the menu). Note that when trying to delete the font from Windwos Explorer you'll get "Access denied" error, because the font is loaded by Font Xplorer, so use Font Xplorer to delete it, not Windows Explorer.
8) Now you have processed 1 font, but will need to continue with the next one the same way from step 5. This action sure seems very slow first, but after processing a few fonts you notice it become semi-automated as your brain has focused to the task. It is also possible to speed up the work by using batches of, say 10 fonts at time, instead of 1. However, then some additional work is required to find which fonts from a batch are the bad ones.

If you now have processed all your fonts from the source folder, I hope you have catched the problematic ones and moved them to X:\FontsBad folder. If so, please see the contact section of our web site on how to contact us by e-mail and send us all the problematic fonts you found. That way we can improve Font Xplorer to process them better, without showing you these frustrating errors.

Note: As you see from this time consuming filtering process, the more fonts you have in one folder, the more work you will need to do. So, be smart and keep number of fonts in one folder reasonable, so it is easy to do troubleshooting, if required.
  Previous Topic Topic Next Topic  
 Forum Locked
 Printer Friendly
Jump To:
Moon Software Forum © Copyright 1996-2011 Moon Software Go To Top Of Page
Snitz Forums 2000