SuperMemo error: Font registry access error
From SuperMemopedia
From:
Country:
Sent: Wednesday, April 20, 2011 4:05 PM
Subject: SuperMemo error: Font registry access error!
Contents |
[edit] Question
Font registry access error! Accessing registry member that does not exist Position=1 Highest position=0
--------------------DETAILS-------------------- SuperMemo 2006 (Build 13.16d, Sep 22, 2008) Time: Apr 20, 2011, 22:04
--------------------SYSTEM DATA Windows Vista 6.1 (Build 7600) Internet Explorer 7.0 (0) Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; GTB6.6; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; eSobiSubscriber 2.0.4.16; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; .NET4.0C) User language: English (en-au) System language: English (en-au) Browser language: English (US) Memory Used: 2.05 MB Active Code Page: 1252 OEM Code Page: 850 Network installed
File : Repair collection does not seem to solve the problem
[edit] Similar error
Similar problem may occur in style registry for the exactly same reason:
Style registry access error! Accessing registry member that does not exist Position=2 Highest position=0"
[edit] Hint
- It is not enough if you run basic checkup (choose File : Repair collection, and click OK, you need to check Rebuild registries in the Repair Options dialog box.
- Alternatively, go to the element that throws this error, right-click your mouse over each text component that used to feature this font, and choose Text : Font : Default font from the component menu.
- Alternatively, add a font to the registry (it will be used in place of the old font that has been deleted). As this is Position=1, you need to add only one font. However, for higher positions, you may need to add more fonts for this to work
[edit] Answer
The most frequent reason for Accessing registry member that does not exist is a situation in which the user deletes a registry member in the registry, while the member is still in use. Some registries automatically reset all use pointers, however, other registries may not do it for performance reasons. For example, if a user deletes a font or a stylesheet from the registry, while the font or style is in use by some elements, those elements will display the above message. Rebuilding the registry at Repair collection resets links from components to non-existent registry members, however, there are exceptions where an accidental reset due to an accidental delete would do more damage than leaving a link to a member that can always be restored back in the registry (unless massive deletes make it hard).
