HOME

  0. Internet
  1. Text
  2. Graphics
  3. System
  4. File
  5. Misc
  6. Palm
  7. OS X

BLOG

DOCS

FAQ

RSS (?)

"Could not reconnect all network drives" #
is an all-too-common startup error in Windows. I used to work around it with a simple script:

   REM **MAP DRIVE X: ON STARTUP**
   REM delay execution for 10 seconds (wait for networking to load)
   REM see http://www.robvanderwoude.com/wait.php#PING for more info
   ping 127.0.0.1 -n 11 >NUL 
   REM disconnect all existing mapped drives
   net use * /delete /yes
   REM map x: drive to \\server\share
   net use x: \\server\share

saved to the All Users Startup folder as map_x.bat or what have you (it can also be launched via Task Scheduler).

Recently, I've taken to using the "Always wait for the network at computer startup and logon" policy instead:

Requirements:
At least Windows XP Professional or Windows Server 2003 family

Description:

This policy setting determines whether Group Policy processing is synchronous (that is, whether computers wait for the network to be fully initialized during computer startup and user logon). By default, on client computers, Group Policy processing is not synchronous; client computers typically do not wait for the network to be fully initialized at startup and logon. Existing users are logged on using cached credentials, which results in shorter logon times. Group Policy is applied in the background after the network becomes available.

Note that because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. To be able to operate safely, these extensions require that no users be logged on. Therefore, they must be processed in the foreground before users are actively using the computer. In addition, changes that are made to the user object, such as adding a roaming profile path, home directory, or user object logon script, may take up to two logons to be detected.

If a user with a roaming profile, home directory, or user object logon script logs on to a computer, computers always wait for the network to be initialized before logging the user on. If a user has never logged on to this computer before, computers always wait for the network to be initialized.

If you enable this policy setting, computers wait for the network to be fully initialized before users are logged on. Group Policy is applied in the foreground, synchronously.

On servers running Windows Server 2008 or later, this policy setting is ignored during Group Policy processing at computer startup and Group Policy processing will be synchronous (these servers wait for the network to be initialized during computer startup).

If the server is configured as follows, this policy setting takes effect during Group Policy processing at user logon:
· The server is configured as a terminal server (that is, the Terminal Server role service is installed and configured on the server); and
· The "Allow asynchronous user Group Policy processing when logging on through Terminal Services" policy setting is enabled. This policy setting is located under Computer Configuration\Policies\Administrative templates\System\Group Policy\.
If this configuration is not implemented on the server, this policy setting is ignored. In this case, Group Policy processing at user logon is synchronous (these servers wait for the network to be initialized during user logon).

If you disable or do not configure this policy setting and users log on to a client computer or a server running Windows Server 2008 or later and that is configured as described earlier, the computer typically does not wait for the network to be fully initialized. In this case, users are logged on with cached credentials. Group Policy is applied asynchronously in the background.

Notes:
If you want to guarantee the application of Folder Redirection, Software Installation, or roaming user profile settings in just one logon, enable this policy setting to ensure that Windows waits for the network to be available before applying policy.
If Folder Redirection policy will apply during the next logon, security policies will be applied asynchronously during the next update cycle, if network connectivity is available.

Enable it here:

gpedit.msc > Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon

If your Windows version does not include Group Policy Editor, use regedit to create or edit the following value name:

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\WinLogon\SyncForegroundPolicy

and set the value data to 1:

Speaking of the Windows Registry, sometimes it's not clear if a path is referencing a key or a value, as Jerry Honeycutt points out in his Microsoft Windows Registry Guide:

When looking at a key's fully qualified path, you have to figure out whether the path includes a value or not. Usually, the text is clear about whether the path is to a key or includes a value, but sometimes it isn't. For example, does HKCR\txtfile\EditFlags refer to a key or a value? In this case, it refers to a value, and I prefer to use explicit language, such as "the value HKCR\txtfile\EditFlags," to make the reference clear. Sometimes, paths that don't include a value name end with a backslash (\). If there is no backslash, pay particular attention to the context to make sure you know whether the path is just a key or includes a value. Sometimes a bit of common sense is all you need.

/windows | May 11, 2012

Fix Word 2010 line spacing #
Home > Styles > Change Styles > Style Set > Word 2003 > Change Styles > Set as Default

/windows | May 11, 2012

Minimal Windows XP installs #
Remember Micro95 (Windows 95 in 4.47MB) and nano98 (Windows 98 in 4.38MB)? reboot.pro hosts two similar projects for Windows XP: XPSP1 with full commandline and NTFS below 10 MB and MiniXP.

/windows | May 08, 2012

Two tiny image browsers #
imv(stb) "is an extremely lightweight and fast image viewer/browser ... Inspired by vjpeg, imv(stb) offers a very simple, no-frills image viewer with a minimal interface." (via Mike Mills)

/windows | Apr 24, 2012

Windows and boot disks larger than 2TB #
Windows' Support for Disks with Capacity Greater than 2TB:

In order for a system to fully support capacities greater than 2TB, the device must be initialized using the GPT partitioning scheme to support addressing the full range of capacity. If the user is intending to boot from one of these large disks, there is an additional requirement that the system's base firmware interface must be using UEFI and not BIOS.

Windows and GPT FAQ:

Q. Can Windows 7, Windows Vista, and Windows Server 2008 read, write, and boot from GPT disks?
A. Yes, all versions can use GPT partitioned disks for data. Booting is only supported for 64-bit editions on UEFI-based systems.

So to create bootable partitions larger than 2TB for Windows-based OSes:

UEFI instead of BIOS
GUID Partition Table (GPT) instead of Master Boot Record (MBR)
64-bit version of Windows Vista, 7, or 2008

It may be possible to non-destructively convert or migrate a Windows boot disk from MBR to GPT:

GPT fdisk can "convert an MBR disk to GPT format without data loss ... although doing so will require you to re-install your boot loader (if it's a boot disk). Do not attempt to convert a Windows boot disk from MBR to GPT form unless you're an expert!"
Gptgen "is a tool to non-destructively convert hard disks partitioned in the common, 'MSDOS-style' MBR scheme (including extended partitions) to use a GUID partition table (GPT)." Walkthru
Macrium Reflect can apparently clone an MBR disk to a GPT disk.

Rod Smith, the author of GPT fdisk, offers detailed GPT documentation, including:

/windows | Apr 22, 2012

Windows cannot connect to the printer #
Windows Vista workstation had been happily sharing a USB printer with a Windows 7 guest for months. Suddenly the Windows 7 guest started displaying "Windows cannot connect to the printer" error messages. Resolved by going to Devices and Printers > Add a printer > Add a local printer > Create a new Port > Local Port > Next, entering the share path as the port name (e.g., \\computername\printername), and completing the printer wizard.

/windows | Apr 22, 2012

Resolving post-malware problems #
BleepingComputer.com member Farbar has created two incredibly useful tools for resolving post-malware issues:

Farbar Service Scanner helps restore network access after a malware infection.
Farbar Recovery Scan Tool (x32 | x64) helps resolve blue screens following malware removal (it can be run from Advanced Boot Options > Repair your computer > Command Prompt).

As with most BleepingComputer tools, there is very little information available about them (hence the direct download links above), but I've seen both resolve very stubborn problems. Farbar kindly replied to my request for details about the tools by saying only a few BleepingComputer members are granted access to that information. Concern about such secretiveness is largely allayed by BleepingComputer's record of altruism (and reticence), along with the near-miracles I've seen Farbar's tools perform.

/windows | Apr 16, 2012

"A duplicate name exists on the network" #
error messages in Windows XP can be caused by:

two or more computers with the same Computer Name
a Workgroup Name which is identical to the wireless router's SSID
a Workgroup Name which is identical to a Computer Name

/windows | Apr 04, 2012

Converting Windows Registry hex to ASCII text #
Convert REGEDIT4 (ANSI, single-byte) and Windows Registry Editor Version 5.00 (Unicode, double-byte) hex strings to text with hex2text. ImagePath in this ver 4 example

becomes \SystemRoot\system32\drivers\iaStorV.sys and in this ver 5 one
becomes \ S y s t e m R o o t \ s y s t e m 3 2 \ d r i v e r s \ i a S t o r V . s y s.

/windows | Apr 01, 2012

Download just imagex.exe (568k) #
instead of the entire Windows Automated Installation Kit (AIK) for Windows 7 (1,782,580k):

Download and install Bo Brantén's HttpDisk-7
C:\>httpdisk.exe /mount 0 http://download.microsoft.com/download/8/E/9/8E9BBC64-E6F8-457C-9B8D-F6C9A16E6D6A/KB3AIK_EN.iso /cd w:
C:\>expand w:\Neutral.cab /f:F3_imagex c:\
C:\>ren F3_imagex imagex.exe

Notes:

This is a modified and abbreviated version of Icecube's Extract files out of WAIK without downloading whole WAIK first.
F3_imagex is the 64-bit version; use F1_imagex for the 32-bit version.
ImageX is swell for restoring Dell factory images, among other things.
Be sure to check out Claus' excellent introduction to ImageX as well.

/windows | Apr 01, 2012

Categories

/blosxom
/eink
/mac
/misc
/nix
/palm
/windows

Blosxom Archive

2012: 5 4 3 2 1
2011: 12 11 10 9 8 7 6 5 4 3 2 1
2010: 12 11 10 9 8 7 6 5 4 3 2 1
2009: 12 11 10 9 8 7 6 5 4 3 2 1
2008: 12 11 10 9 8 7 6 5 4 3 2 1
2007: 12 11 10 9 8 7 6 5 4 3 2 1
2006: 12 11 10 9 8 7 6 5 4 3 2 1
2005: 12 11 10

Blogger Archive

2005: 10 9 8 7 6 5 4 3 2 1
2004: 12 11 10 9 8 7 6 5 4 3 2 1
2003: 12 11 10 9 8 7 6

Ezine Archive

2004: 4 3 2 1
2003: 12 9 8 7 6 5 4 2 1
2002: 12 10 9 8 7 6 5 3 2 1
2001: 12 11 10