FP1: Errors Caused by Image Map Circular Hot Spot w/ No URL

• Microsoft FrontPage for Windows, versions 1.0, 1.0a
• Microsoft FrontPage Personal Web Server, versions 1.0, 1.0a

SYMPTOMS

When you insert an image map and define a circular hot spot, but do not associate the hot spot to a Uniform Resource Locator (URL) or a file, you get one or more of the following errors when you reopen the file in the FrontPage Editor:

• Internal application error.
• An unexpected exception occurred.
• This program has performed an illegal operation and will be shut down.

  If the problem persists, contact the program vendor.

   Fpeditor caused an invalid page fault in module Msvcrt20.dll at
   0137:7fd81dc3.

   Kernel32.dll
   Mfc30.dll
   Fpeditor.exe

RESOLUTION

When you add an image map and define a circular hot spot, identify the URL or local file to be accessed when the hot spot is selected.

To correct a page that contains an image map that does not identify a URL for a circular hot spot, do the following:

NOTE: If the file is located on a remote server, copy the web to your local machine before you complete the following steps.

1. Using a text editor, such as Notepad, click Open on the File menu.

2. Locate and select the Content\<webname>\_VTI_SHM folder, where <webname> represents the folder that contains your web content.

   NOTE: The _VTI_SHM folder contains files of the same name as those in the <webname> folder.

3. Select the HyperText Markup Language (HTML) file of the same name as the file you added the image map to. For example, if you added the image map to the default page, Index.htm, select the Index.htm file, and then click OK or Open.

4. Locate the line that looks like this:

         Circle=" (xxx,yyy) zzz   "
   
      where xxx, yyy, and zzz are coordinates for the hot spot.
   
      NOTE: If this line identifies a URL, ignore it and search for another
      line that does not specify a URL.
   
   

5. Modify the line so that it looks like this:

         Circle=" (xxx,yyy) zzz index.htm"
   

6. Save and close the file.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft FrontPage for Windows, version 1.1.