Xmarks in Firefox: Can't sync tabs!

Tab sync is generally reliable, but there a couple of gotchas that can cause problems when you're first getting started.

Can't see your tabs?

If you have enabled tab sync in a browser but can't see your tabs in the Open Tabs window, the most likely culprit is your having earlier copied your Firefox profile from one computer to another. Xmarks relies on a unique identifier stored in your FIrefox profile to know which tabs are on which computer, and if those identifiers aren't actually unique, tab data from one computer will overwrite tab data from another. Further, if you have two browsers with the same id, you might not see any data at all because a browser never shows its own tab data.

The fix for this problem is simple: go to the browser whose data you wish to unhide and reset its identifier. Xmarks will automatically create a new one for you. Do this one time only:

1. Enter about:config in the Firefox address bar.
2. Find the item extensions.xmarks.machineId.
Right-click (control-click on the Mac) and select reset.

The next time you sync, your tabs should also be synced and be visible elsewhere.

Internet Explorer warning running swf locally

When previewing files locally on your hard drive that contain active content (for example, JavaScript or Flash), the following security message appears in internet explorer's yellow Information Bar:
"To help protect your security, internet explorer has restricted this file from showing active content that could access your computer. Click here for options ..."

You can resolve this by checking:
Tools -> Internet Options -> Advanced -> Allow active content to run in files on My Computer
(Located in the "Security Section", second line)

Windows: How to enable user environment debug logging in retail builds of Windows

View products that this article applies to.

Article ID	:	221833
Last Review	:	October 11, 2007
Revision	:	11.4

This article was previously published under Q221833

SUMMARY

The versions of Microsoft Windows that are listed in the "Applies to" section let you modify the registry to turn on debug logging of the user profile and the Windows system policy processes. You can also use this logging to track down problems that are related to the start of Desktop Standard PolicyMaker client-side extensions (CSEs). Debug logging functionality is also available in Microsoft Windows NT 4.0. However, in Windows NT 4.0, this functionality requires a checked (debug) build of the Userenv.dll file.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

154120 (http://support.microsoft.com/kb/154120/) Debugging user profiles and system policies in Windows NT 4.0

You can use debug logging output to troubleshoot problems with user profiles and Group Policy processing.

MORE INFORMATION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows

Use Registry Editor to add or to modify the following registry entry:

Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Entry: UserEnvDebugLevel
Type: REG_DWORD
Value data: 10002 (Hexadecimal)

UserEnvDebugLevel can have the following values:

NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000

The default value is NORMAL|LOGFILE (0x00010001).

Note To disable logging, select NONE (0x00000000).

You can combine these values. For example, you can combine VERBOSE 0x00000002 and LOGFILE 0x00010000 to get 0x00010002. Therefore, if UserEnvDebugLevel is given a value of 0x00010002, LOGFILE and VERBOSE are both turned on. Combining these values is the same as using an OR statement.

0x00010000 OR 0x00000002 = 0x00010002

Note If you set UserEnvDebugLevel to 0x00030002, the most verbose details are logged in the Userenv.log file.

The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file. If the Userenv.log file is larger than 300 KB, the file is renamed Userenv.bak, and a new Userenv.log file is created. This action occurs when a user logs on locally or by using Terminal Services, and the Winlogon process starts. However, because the size check only occurs when a user logs on, the Userenv.log file may grow beyond the 300 KB limit.

The 300 KB limit cannot be modified.

Windows: How to disable security warning ("Не удается проверить издателя")

How to disable security warning ("Не удается проверить издателя"):
gpedit.msc
User Configuration->Administrative Templates->Windows Component->Attacment Manager->Inclusion list for moderate risk file types
прописываем там расширения, для которых не выводить предупреждения (exe, jpg, etc)