see http://www.google.com/support/forum/p/Chrome/thread?tid=3b1d41b0663a4d40&hl=en
in a command window:
powercfg -requestsoverride PROCESS chrome.exe awaymode display system
to remove the override:
powercfg -requestsoverride PROCESS chrome.exe
source:
http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/AvailabilityRequests.docx.
more far-reaching fix if you have a 'Pro' version of windows 7 - editing local group policy:
start>Run>gpedit.msc
Computer Configuration>Administrative Templates>System>Power Management>Sleep Settings>
Set
Allow Applications to Prevent Automatic Sleep (On Battery)
and
Allow Applications to Prevent Automatic Sleep (Plugged In)
to disabled.
but this applies to ALL applications, not just chrome.
Wednesday, August 17, 2011
Sunday, January 2, 2011
File System links in Windows Vista/7
MKLINK.exe
no argument: FILE symbolic link (like a shortcut but not stored as a .lnk file)
/D: DIRECTORY symbolic link (like a shortcut but not stored as a .lnk file)
/H: FILE junction (hard link) (think of data deduplication; only one physical FILE but multiple logical locations)
/J: DIRECTORY junction (hard link) (think of data deduplication; only one physical DIRECTORY but multiple logical locations)
I've only ever used /J for directory links.
Directory Linker, a nifty GUI for creating symbolic links: http://dirlinker.codeplex.com/
NOTE: The first two methods use 'symbolic links' which may fail when used across network drive mappings. ("The symbolic link cannot be followed because its type is disabled") In this case, the fsutil utility may need to be used to enable the various symbolic link 'types': R2R, L2L, L2R, R2L.
fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1
"fsutil.exe" can be made to show what arguments it takes by simply running:
fsutil behavior set /?
The symbolic-link resolution behavior is set on the machine that accesses a given link, not the machine that hosts it.
The behavior codes for "fsutil.exe", namely "L2L", "L2R", "R2L", and "R2R", mean the following:
"L" stands for "Local", and "R" for "Remote" (who would've thunk?)
The FIRST "L" or "R" - before the "2" - refers to the location of the link itself (as opposed to its target) relative to the machine ACCESSING the link.
The SECOND "L" or "R" - after the "2" - refers to the location of the link's target relative to the machine where the LINK itself is located.
Thus, for instance, enabling "R2L" means that you can access links located on a remote machine that point to targets on that same remote machine.
More Info:
stackoverflow.com
no argument: FILE symbolic link (like a shortcut but not stored as a .lnk file)
/D: DIRECTORY symbolic link (like a shortcut but not stored as a .lnk file)
/H: FILE junction (hard link) (think of data deduplication; only one physical FILE but multiple logical locations)
/J: DIRECTORY junction (hard link) (think of data deduplication; only one physical DIRECTORY but multiple logical locations)
I've only ever used /J for directory links.
Directory Linker, a nifty GUI for creating symbolic links: http://dirlinker.codeplex.com/
NOTE: The first two methods use 'symbolic links' which may fail when used across network drive mappings. ("The symbolic link cannot be followed because its type is disabled") In this case, the fsutil utility may need to be used to enable the various symbolic link 'types': R2R, L2L, L2R, R2L.
fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1
"fsutil.exe" can be made to show what arguments it takes by simply running:
fsutil behavior set /?
The symbolic-link resolution behavior is set on the machine that accesses a given link, not the machine that hosts it.
The behavior codes for "fsutil.exe", namely "L2L", "L2R", "R2L", and "R2R", mean the following:
"L" stands for "Local", and "R" for "Remote" (who would've thunk?)
The FIRST "L" or "R" - before the "2" - refers to the location of the link itself (as opposed to its target) relative to the machine ACCESSING the link.
The SECOND "L" or "R" - after the "2" - refers to the location of the link's target relative to the machine where the LINK itself is located.
Thus, for instance, enabling "R2L" means that you can access links located on a remote machine that point to targets on that same remote machine.
More Info:
stackoverflow.com
Saturday, July 24, 2010
Wireless Key Registry Location
Windows XP: The wireless keys are stored in the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WZCSVC\Parameters\Interfaces\[Interface Guid].
Windows Vista: The wireless keys are stored in the file system, under c:\ProgramData\Microsoft\Wlansvc\Profiles\Interfaces\[Interface Guid]. The encrypted keys are stored in .xml file.
Windows Vista: The wireless keys are stored in the file system, under c:\ProgramData\Microsoft\Wlansvc\Profiles\Interfaces\[Interface Guid]. The encrypted keys are stored in .xml file.
Tuesday, June 29, 2010
Using ShellRunas to run programs 'as different user' in Windows 7 without shift+right clicking
Download Sysinternals ShellRunas from http://technet.microsoft.com/en-us/sysinternals/cc300361.aspx, save it in C:\Windows\System32 (or %systemroot%\system32), and then prefix the 'Target' field in the application's shortcut with %systemroot%\System32\ShellRunas.exe.
Example:
%systemroot%\System32\ShellRunas.exe "C:\Program Files (x86)\testprogram\test.exe"
alternative method using the old 'runas' command:
runas.exe /user:Domain\Username "C:\Program Files (x86)\testprogram\test.exe"
you can throw /savecred when using runas to save the credentials the first time the shortcut is run, and then to launch using those saved credentials thereafter.
credit: http://social.technet.microsoft.com/Forums/en/w7itproui/thread/bb1480cf-c920-4d83-b889-4654f5713c8f
Example:
%systemroot%\System32\ShellRunas.exe "C:\Program Files (x86)\testprogram\test.exe"
alternative method using the old 'runas' command:
runas.exe /user:Domain\Username "C:\Program Files (x86)\testprogram\test.exe"
you can throw /savecred when using runas to save the credentials the first time the shortcut is run, and then to launch using those saved credentials thereafter.
credit: http://social.technet.microsoft.com/Forums/en/w7itproui/thread/bb1480cf-c920-4d83-b889-4654f5713c8f
Thursday, June 3, 2010
Accessing XP/Server 2003 network shares from Windows 7/Vista
The Windows 7/Vista LAN Manager Authentication Level must be changed to allow communication with the older NT/XP systems.
Start>Run>secpol.msc>Local Policies>Security Options>
set 'Network Security: LAN Manager Authentication level' to 'Sent LM & NTLM - use NTLMv2 session security if negotiated'
This can also be accomplished via the registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"LmCompatibilityLevel"=dword:00000001
Start>Run>secpol.msc>Local Policies>Security Options>
set 'Network Security: LAN Manager Authentication level' to 'Sent LM & NTLM - use NTLMv2 session security if negotiated'
This can also be accomplished via the registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"LmCompatibilityLevel"=dword:00000001
Monday, April 5, 2010
Do not automatically make redirected folders available offline
gpedit.msc>User>Administrative Templates>System>Folder Redirection>Do not automatically make redirected folders available offline>On
Subscribe to:
Posts (Atom)
