Google Chrome Scroll Anchoring

Scroll Anchoring is a new feature of Google Chrome 51 and newer that prevents visible jumps of the active page when offscreen content changes.

You may have experienced the following situation when using a browser like Google Chrome: you load a page and some text is loaded quickly. You begin to read the text and scroll a bit or a lot, and suddenly the page begins to scroll automatically as other elements, images or media, are added to the page.

You lose sight of the position you were at when that happens. This scroll jumping can be confusing, as you need to locate the position on the page when things started to jump around to continue reading.

These visible jumps, when you start to scroll while a page is loading, is problematic on the desktop, and maybe even more so on mobile devices.

Scroll Anchoring

google-chrome-scroll-anchoring

Scroll Anchoring has been designed to prevent these visible jumps from happening in Chrome. Basically, what the feature does is adjust the page in the background without jumping away from the part that is visible on the screen.

The feature is not enabled by default but part of the browser’s experimental flags. These features are not yet ready for prime time, or need further testing, before Google makes a decision whether to integrate it natively in Chrome or remove it again.

To enable scroll anchoring in Google Chrome, do the following:

  1. Make sure you are running at least Google Chrome 51. Easiest way to find out is to load chrome://version/ and check the version that is displayed.
  2. If that is the case, load chrome://flags/#enable-scroll-anchoring to jump directly to the preference.
  3. On mobile, you may find it easier to load chrome://flags and use the built-in search to find anchor to jump to it instead.
  4. Switch it to enabled to turn it on.
  5. Restart google Chrome to complete the change.

The feature is available for all desktop versions of Google Chrome, for Chrome OS and for Chrome on Android.

To turn it off again, repeat the process outlined above but switch the preference to disabled this time to do so.

Source: http://www.ghacks.net/

Advertisements

Your First Month as a Systems Administrator

Congratulations on getting that systems administration job that you’ve worked hard for!  Now, it’s time to get both feet wet and get after it.

sysadmin-noob

What to focus on during your first month:

As with any job, there are two general areas that you should excel in when you first become a sysadmin.  One is the work itself.  You should be able to function well as the systems admin and get a grasp on what you are doing overall.  And two, you should work on your people skills because you’re not going to be working exclusively with machines, the network, software and programming.  A large part of what you will be doing involved interacting with people.

So what do you tackle in month one?  Here are some considerations. Continue reading

Mailbox Size Limits Are Not Enforced in a Reasonable Period of Time

This issue occurs because the Microsoft Exchange Information Store service uses the cached mailbox configuration to enforce mailbox size limits. The configuration change does not take effect until the cache is refreshed. The default interval for refreshing the cached mailbox information is two hours.

To resolve this problem, you can change the refresh interval for the mailbox information cache by modifying the Reread Logon Quotas Interval value in the registry for the Microsoft Exchange Information Store service. The Reread Logon Quotas Interval value depends on the Directory Service Access (DSAccess) cache and the mailbox information cache. Therefore, you must configure the CacheTTLUser and Mailbox Cache Age Limit values as well.

Continue reading

Remotely Enabling Remote Desktop .VBS script

What if you’ve deployed a Windows Server 2003 box in a remote location but forgot to enable Remote Desktop on it so you can administer it remotely?

This script should help in remotely enabling Remote Desktop Connection.

Continue reading

Fully remove device drivers from your machine

Follow these steps to view and remove unnecessary device drivers:

  • Press [Windows]+[Break] to bring up the System Properties dialog box.
  • Select the Advanced tab and click the Environment Variables button.
  • Click the New button below the System Variables panel.
  • In the New System Variable dialog box, type devmgr_show_nonpresent_devices in the Variable Name text box and 1 in the Variable Value text box.
  • Click OK to return to the System Properties dialog box and then click OK again.
  • Select the Hardware tab and click the Device Manager button.
  • In Device Manager, go to View | Show Hidden Devices.
  • Expand the various branches in the device tree and look for the washed out icons, which indicate unused device drivers.
  • To remove an unused device driver, right-click the icon and select Uninstall.

Find out your restart time

Open notepad.exe and paste the following:

Option Explicit
On Error Resume Next
Dim Wsh, Time1, Time2, Result, PathFile, MsgResult, MsgA, AppName, KeyA, KeyB, TimeDiff
MsgA = “Please close all running applications and click on OK.”
KeyA = “HKEY_CURRENT_USER\Software\RestartTime\”
KeyB = “HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\RestartTime”
AppName = “Restart-Time”
Set Wsh = CreateObject(“WScript.Shell”)
PathFile = “””” & WScript.ScriptFullName & “”””
Result = wsh.RegRead(KeyA & “Times”)
if Result = “” then
MsgResult = Msgbox (MsgA, vbOKCancel, AppName)
If MsgResult = vbcancel then WScript.Quit
Wsh.RegWrite KeyA & “Times”, left(Time,8), “REG_SZ”
Wsh.RegWrite KeyB, PathFile, “REG_SZ”
Wsh.Run “cmd /c Shutdown -r -f -t 00”, false, 0
else
Wsh.RegDelete KeyA & “Times”
Wsh.RegDelete KeyA
Wsh.RegDelete KeyB
TimeDiff = DateDiff(“s”,Result,left(Time,8))
MsgBox “Your computer takes ” & TimeDiff & ” seconds to completely restart.”, VbInformation, AppName
end if
wscript.Quit

Save as Restart-Time.vbs and run.

Source: Unknown

Reset Windows 7 Reliability Monitor batch file

Open notepad.exe and paste the following:

:: Created by: Shawn Brink
:: http://www.sevenforums.com
:: Tutorial:  http://www.sevenforums.com/tutorials/20779-reliability-monitor-reset.html

reg set HKLM\SOFTWARE\Microsoft\Reliability Analysis\WMI /v WMIEnable /T REG_DWORD /D 00000001 /F
del /f /S /Q /A “%ProgramData%\Microsoft\RAC\PublishedData\*”
del /f /S /Q /A “%ProgramData%\Microsoft\RAC\StateData\*”
@echo off
FOR /F “tokens=1,2*” %%V IN (‘bcdedit’) DO SET adminTest=%%V
IF (%adminTest%)==(Access) goto noAdmin
for /F “tokens=*” %%G in (‘wevtutil.exe el’) DO (call :do_clear “%%G”)
echo.
echo goto theEnd
:do_clear
echo clearing %1
wevtutil.exe cl %1
goto :eof
:noAdmin
exit

Save as Reset_Reliability_Monitor.bat and run.

Source: http://www.sevenforums.com