Copy the text from between the ...... lines below to a .reg file, and Merge it:

............................................................................

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\AllFileSystemObjects\shellex\ContextMenuHandlers]

[HKEY_CLASSES_ROOT\AllFileSystemObjects\shellex\ContextMenuHandlers\Copy To]

@="{C2FBB630-2971-11D1-A18C-00C04FD75D13}"

[HKEY_CLASSES_ROOT\AllFileSystemObjects\shellex\ContextMenuHandlers\Move To]

@="{C2FBB631-2971-11D1-A18C-00C04FD75D13}"

............................................................................

Windows Management Instrumentation (WMI) is an implementation of Distributed Management Task Force's (DMTF) Web-Based Enterprise Management (WBEM).  WBEM is a set of open, industry-defined specifications that unify and extend the management of enterprise-computing environment.  The central part of WMI is the CIMOM (Common Interface Model Object Manager) which is an interface to the CIM (Common Information Model) which actually is a data container.  CMI makes it possible for drivers, services, applications to return information in form of data or events into the CIM.  This data can be extracted and analyzed by System Managers to provide information about how to better manage, troubleshoot, and tune their systems.  An example of a program used to extract such data is WBEMTEST.EXE.  This continuous logging to the file CIM.REC causes extra I/O overhead and defragmentation.  To disable it, go to the Registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM

These sub-keys control logging:

’EnableEvents’, Data Type: REG_SZ, Value: 0 to disable, default is 1

‘Logging’, Data Type: REG_SZ, Value: 0 to disable, default is 1

To change the locations of the data containers:

‘Logging Directory’, Data Type: REG_EXPAND_SZ, Default Value: C:\WINNT\System32\WBEM\Logs

‘Working Directory’, Data Type: REG_EXPAND_SZ, Default Value: C:\WINNT\System32\WBEM

One can also change the Logging and/or Working Directory to a RAM-drive to increase speed.

To remove the Shortcut Overlay, browse to:

HKEY_CLASSES_ROOT\Lnkfile

Select the ‘IsShortcut’ sub-key in the right-hand pane and delete it.  You must Logoff/Logon to see the change.

ExCtrLst.exe provides information on the performance counter dynamic-link libraries (DLLs) that have been installed on a computer running Microsoft Windows 2000.  You can use ExCtrLst to display the services and applications that provide performance information and to disable a specific counter DLL if needed.  You might want to disable a counter DLL if errors occur (these may be logged in Event Viewer).

When ExCtrLst is started, it scans the Registry on your system to see which applications, devices, and Services have registered performance counter libraries.  These libraries are listed in the list box of the display along with the corresponding Service or application.  It is possible for a single performance counter library to provide performance information for several Services or devices, or it may provide data for a single application.

NOTE:  Counter DLL’s that are loaded using WBEMPERF can be managed using ExCtrLst;  however, native WMI/WBEM counter providers cannot.

Tlist.exe, a command-line tool, displays a list of tasks, or processes, currently running on the local computer.  For each process it shows the process ID number, process name, and if the process has a window, the title of that window. 

Task List Viewer syntax:

tlist [pid] [pattern] [-m pattern] [-p processname] [-s] [-t]

Parameters:

tlist

Without arguments, lists running processes with their process ID, process name, and window title (if any).

pid

Lists detailed module information for the task specified by pid (process ID).

pattern

Lists detailed module information for the processes whose task names and the window titles match pattern;  pattern (for example, A*) can be a complete task name or a regular expression.

-m pattern

Lists all tasks that have DLL modules loaded in them matching the given pattern name.  The pattern (for example, A*) can be a complete task name or a regular expression.  TList matches this pattern against the task names and the window titles.

-p processname

Returns the PID of the specified process or -1 if this process doesn't exist.  If multiple instances of the process are running, only the instance with the first PID value is returned.

-s

Shows services active in each process.

-t

Prints task tree.  This switch displays output based on which processes are children/parents of which other processes.

Tlist.exe can be found on your Windows 2000 CD, the SUPPORT\TOOL folder, in the SUPPORT.CAB file.

Microsoft has released a command-line tool named QChain.exe that gives system administrators the ability to safely chain hotfixes together.  Hotfix chaining involves installing multiple hotfixes without rebooting between each installation.  Without this tool, the only supported method is to reboot after each hotfix installation.

When you choose the backup media device in Windows 2000 Backup, you can't choose a device that RSM (Remote Storage Management) doesn't recognize as backup pool media.

NOTE:  Adding these media types in RSM doesn't solve the problem.

NOTE:  RSM considers these devices to be read-only.

If you have dimished vision, the Magnifier tool can make the screen more readable.  The Magnifier tool can be started from Start | Programs | Accessories | Accessibility | Magnifier.  With Magnifier, you can:

=  Change the magnification level

=  Change the size of the magnification window

=  Change the position of the magnification window on your desktop

=  Invert the screen colors

=  Use a high-contrast setting

=  Follow the mouse pointer as it moves on your screen

=  Follow the keyboard focus that centers on the location of the insertion point

The Utility Manager can be started at Start | Programs | Accessories | Accessibility | Utility Manager or by pressing the Windows Logo key and typing U.  The Utility Manager provides access to Magnifier and Narrator.  You can add the On-Screen Keyboard by pressing ‘Add to Utility Manager’ from the On-Screen Keyboard File menu.  Narrator starts automatically with Utility Manager.

You can also use Utility Manager to automatically start Magnifier when Windows 2000 starts.

In Windows 2000, all drives on your computer, such as drive C or D, are automatically shared using the name drive letter$, such as C$ or D$.  These drives are not shown with the hand icon that indicates sharing in My Computer or Windows Explorer, and they are also hidden when users connect to your computer remotely.

However, any user can gain access to your computer over a network or the Internet if the user knows your computer name, and the user name and password of a user who is a member of the Administrators, Backup Operators, or Server Operators group.  A user who gains access to your drive over the network or Internet can view all folders and files on that drive, even those that are protected using NTFS permissions, provided the NTFS permissions allow access to members of the Administrators, Backup Operators, or Server Operators group.

To keep your drives secure, you should:

=  Create a difficult password for the Administrator account.  Many people leave this password blank, which leaves the computer vulnerable to security breaches because any user can log on as the Administrator using a blank password.  It is also a good idea to rename the Administrator account using the Local Users and Groups snap-in.

If for some reason you must leave your Administrator password blank, you can disable sharing by doing one of the following:

=  Disable the Server service.  Disabling this service removes the ability to share folders on your computer.  No user will be able to connect to any drive or folder on your computer.  However, you can still access shared folders on other computers.  When you disable the Server service, under Startup, be sure to click Manual or Disabled or else the service will start the next time the computer is restarted.

=  Uninstall File and Printer Sharing for Microsoft Networks.  This option appears when you view the properties of any connection in Network and Dial-up Connections.  Click the Uninstall button to remove this component; simply clearing the File and Printer Sharing for Microsoft Networks check box will not work.

NOTE:  To stop sharing a drive temporarily, right-click it, click Sharing, and then click Do not share this folder.  However, keep in mind that Windows 2000 will share the drive again once the computer is restarted.

When a window that doesn't have the focus (i.e.; is in the background) is updated by its program, Windows 2000 by default prevents it from becoming the topmost (foreground) window.  Instead it flashes the taskbar button.  This is governed in the Registry entry:

HKEY_CURRENT_USER\Control Panel\Desktop

by the following REG_DWORD Values:

<  ForegroundLockTimeout:

<  Value 200000 [Decimal]:  background window not allowed to grab the focus (default behaviour).

<  Value 0 [Decimal]:  allows the background window to grab the focus (become topmost/foreground)

<  ForegroundFlashCount:

<  Value 0 [Decimal]: taskbar flashes until clicked.

<  Value x [Decimal]: taskbar flashes x times (default is 3).

Under normal circumstances, when you try to rename a System File in Windows 2000 Explorer, you receive an error indicating that the file is being used by windows.

For Example:  If you attempt to rename the file Kernel32.dll, you will receive:

“Cannot rename Kernel32.dll:  The specified file is being used by Windows”

To work around this behavior, do the following:

1.  Open a CMD prompt.

2.  Switch (CD) to the folder that contains the file you wish to rename.

3.  Use the REN command:

REN kernel32.dll kernel32.old

If you do not have an MS-DOS boot disk, you can build one if you have a Windows 2000 CD:

1.  Insert the Windows 2000 CD-ROM in your CD-ROM drive

2.  Open a CMD prompt and type:

cd /d <CD-ROM Drive Letter>:\VALUEADD\3RDPARTY\CA_ANTIV

3.  Insert a 1.44 Diskette in your diskette drive (A:) and type:   Makedisk.bat

4.  After the diskette is created, edit the A:\autoexec.bat file and remove all the lines.

5.  Delete the old anti-virus files, leaving only:

A:\AUTOEXEC.BAT

A:\COMMAND.COM

A:\DRVSPACE.BIN

A:\HIMEM.SYS

A:\IO.SYS

A:\MSDOS.SYS

This will create a Win95/MS-DOS 7 boot disk.  When you wish to boot to MS-DOS, shutdown Windows 2000 and restart with the boot disk in the diskette drive.

If a line begins with a semicolon (;), it is considered a comment.  For Example:

---------------------------------------------------------

Windows Registry Editor Version 5.00

; These are Command Processor Values

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor]

"AutoRun"=""

"CompletionChar"=dword:00000040

"DefaultColor"=dword:00000000

"EnableExtensions"=dword:00000001

"PathCompletionChar"=dword:00000040

---------------------------------------------------------

Compatibility mode provides an environment for running programs that more closely reflects the behavior of either Microsoft Windows 95 or Microsoft Windows NT 4.0.  These modes resolve several of the most common issues that prohibit older programs from working correctly with Windows 2000.  Programs that experience issues after migration may benefit from being started in one of these compatibility environments.  To install Compatibility-mode properties:

1.  Log on as Administrator.

2.  Click Start, and then click Run.

3.  In the Open box, type the following command, and then click OK, where %SystemRoot% is the drive and folder in which Windows 2000 is installed:

regsvr32 %systemroot%\apppatch\slayerui.dll

Administrators can use a program shortcut to set the compatibility mode for a target program.  This requires that the Compatibility-mode properties be correctly installed and registered on the computer by using the previous steps.  To enable Compatibility mode by using a program shortcut:

1.  Log on as Administrator.

2.  Right-click the shortcut, and then click Properties.

3.  Click the “Compatibility” tab.  This tab appears only if the Compatibility-mode interface has been properly enabled on the computer (as described above).

4.  Click to select the “Run in Compatibility Mode” check box to enable Compatibility-mode support for the program.

5.  Click either “Windows 95” or “Windows NT 4.0” compatibility mode in the drop-down box.

6.  Click OK to save the changes.

7.  Double-click the shortcut to run the program.

NOTE:  Be careful if you use Compatibility mode to bypass version warnings in Setup or installation programs.  Some programs are designed for a specific operating system and intentionally prohibit use on future versions.  These are most often system-level programs that run at a very low level and have the potential to cause serious problems if installed.

How to Disable Compatibility Mode

Because you enable Compatibility mode independent of the Windows 2000 Service Pack 2 installation process, uninstalling Windows 2000 Service Pack 2 does not remove Compatibility mode.  To uninstall Compatibility mode:

1.  Log on as Administrator.

2.  Click Start, and then click Run.

3.  In the Open box, type the following command, and then click OK , where %SystemRoot% is the drive and folder in which Windows 2000 is installed:

regsvr32 /u %systemroot%\apppatch\slayerui.dll

How would you like to have Service Pack 2 integrated in your Win2K install files?  No more installing Win2K, then applying the latest Service Pack.  When you install Win2K, you will be installing the latest Service Pack right along with it!  Well here's how to do it:

First, get out your Win2K CD and copy all the files to a directory on your hard drive (I'll assume you're copying all the files to:  C:\win2k).  You only HAVE to have the files in the i386 directory, but it's best to copy all the files since you're probably going to burn a CD and you want a fully functional CD. 

Randomly, do some icons in My Computer, Windows Explorer, in your Quick Launch toolbar, or on your desktop, change?  To work around this behavior:

1.  Open a CMD prompt and type:  attrib -h "%windir%\shelliconcache"

2.  Use Windows Explorer to delete the ShellIconCache file in your %Windir% folder.

3.  Use Regedt32 to navigate to:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer

4.  On the Edit menu, Add Value name ‘Max Cached Icons’ as a String (REG_SZ) data type.

5.  Set the string to a number between 100 and 2000.  I prefer 2000.  The default is 500.

6.  Restart your computer.

If you receive:

Event Type:      Error

Event Source:    WinMgmt

Event Category:  None

Event ID:        37

Date:            2/7/2000

Time:            10:05:55 AM

User:            N/A

Computer:        [machinename]

Description:     WMI ADAP was unable to load the PERFPROC.DLL performance library due to an unknown problem within the library: 0x0

The Performance Library Dredger thinks that the library is invalid, even though the counter works properly.  To resolve the issue, open a CMD prompt and type:

winmgmt /clearadap

or

winmgmt /resyncperf -p <processID>

where <processID> is the processID of the running WINMGMT process.

If your Application Event log contains the following after every restart:

Event Type: Error

Event Source: perfctrs

Event Category: None

Event ID: 3101

Date: boot_date

Time: boot_time

User: N/A

Computer: SYSTEM

Description: Unable to read IO control information from NBT device.

Windows 2000 TCP/IP performance counters are trying to get I/O control information from your network device (NIC, modem, ...), but the devices do not exist.  To fix the problem:

By default, Windows 2000 is set to collect physical drive data.  Most home users don't need this.  To disable the disk performance counters click on:

Start
Programs
Command Prompt
diskperf –n

To remove the  "Find: On the Internet..."  and/or  "Find: People..."  items from the Start menu, run Regedit and go to:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FindExtensions\Static

Once there, delete the following Value name(s):  "InetFind" (removes "Find: On the Internet...") and/or "WabFind" (removes "Find: People...").

FIRST:  From the Regedit menu, backup (Export) the entire "FindExtensions" key to a REG file, to be able to restore it in the future by double-clicking on (merging) the REG file back into the Registry.

The Windows 2000 Safe Boot has options to load various minimal drivers and services, so you can get around some issues that are preventing a normal startup.  To use Safe Boot, press F8 when the boot menu is displayed.  This presents you with an Advanced Options menu that allows you to select the Safe Mode option that you want, and then select the O/S instance that you wish to boot.

NOTE:  DO NOT select an Windows NT instance.

NOTE:  Safe Mode is prominently displayed.  After selecting an option, press Enter to select the O/S instance.

NOTE:  When booted in Safe Mode, the %Safeboot_Option% variable will contain either Network or Minimal.

The Safe Boot options are:

Safe Mode (Safeboot_Option=Minimal):  A minimal set of device drivers and services will be loaded.

Safe Mode with Networking (Safeboot_Option=Network):  Same as above, plus networking drivers.

Safe Mode with Command Prompt (Safeboot_Option=Minimal):  Safe mode is started but with a CMD.EXE shell.

Enable VGA Mode:  Windows 2000 starts in VGA mode, so your video driver is not loaded.

Last Known Good Configuration:  Start with the previous good configuration.

Directory Service Restore Mode:  For Domain controllers only.

Debug Mode:  Debugging information is transmitted on COM2, to a computer that is running a debugger.

Enable Boot Logging:  Boot normally, but log the load of devices/services in %SystemRoot%\ntbtlog.txt.

Boot Normally:  Change you mind and boot the Default instance.

NOTE:  All Safe Mode boots will log (except Last Known Good).

The drivers and services that a minimal Safe Boot (i.e., Safe Mode or Safe Mode with Command Prompt) will start can be viewed by inspecting the Registry sub-keys at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot\Minimal.

The drivers and services that Safe Mode with Networking will start can be viewed by inspecting the sub-keys at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot\Network.

F1:  Repeats the letters of the last command line, one by one

F2:  Displays a dialog asking user to "enter the char to copy up to" of the last command line

F3:  Repeats the last command line

F4:  Displays a dialog asking user to "enter the char to delete up to" of the last command line

F5:  Goes back one command line

F6:  Enters the traditional CTRL+Z (^z)

F7:  Displays a menu with the command line history

F8:  Cycles back through previous command lines (beginning with most recent)

F9:  Displays a dialog asking user to enter a command number, where 0 is for first command line entered

NOTE:  The buffer (default) allows a maximum of 50 command lines.  After this number is reached, the first line will be replaced in sequence.

If you can't find your normal WinIPcfg.exe file that you relied upon in Windows 98, it would be very helpful to know that in Windows 2000 the file is now called IPconfig.exe, and it isn't based on a GUI anymore.  Run it from the command prompt and you'll have all of your TCP/IP network info.

NOTE:  IPCONFIG is a very handy utility.  For usage information, type "IPCONFIG /?" at a command prompt.  This tip works on both Windows 2000 Server and Professional.

The Recovery Console allows System Administrators to access the file system of a Windows 2000 computer—even if the hard disk is formatted using NTFS—by using the Windows 2000 Setup CD.  This allows support professionals to fix even a non-booting Windows 2000 system.  Since the Recovery Console has batch support, it is even possible for System Administrators to create batch files to fix common scenarios and distribute those batch files for users to run on their systems.

It's a good idea to install Recovery Console on all of your Windows 2000 Server computers, as well as Windows 2000 Professional computers that are more at risk, such as those used by developers, software testers, or fearless power users.

To install the Recovery Console on your system:

winnt32 /cmdcons

To install the Recovery Console unattended (you can script this as part of a setup):

winnt32 /cmdcons /unattend

Cool use of the Recovery Console:

Fix the Master Boot Record (MBR) in case it was corrupted by a virus or another problem.  Previously, this might have involved using DOS FDISK (fdisk /mbr).  The command is:  fixmbr.

Create a batch file for recovery commands to automate common recovery tasks:

For example, you can automate the disabling of several services (e.g., Telnet, Server, Telephony, Messenger) simultaneously, or automate replacement of the registry.  The command is:

batch<nameofbatchfile> <file to contain output of batchfile>

One limitation is that a batch file cannot contain another batch file.  This is a really neat scenario for an IT manager:  having batch files that solve common problems that may require a lot of steps.

Enable all paths for the Recovery Console:

Use the Security & Configuration Analysis Snap-in or the Group Policy Editor to enable the SET Command.  This allows you to copy files to removable media and gives you access to all paths.  You can also enable Auto-Logon for the Console, using the Group Policy or the Security Configuration and Analysis MMC snap-in.

Partition and format a disk:

Use the diskpart and the format commands to partition and format a disk NTFS, FAT, or FAT32.  Incidentally, this can be scripted.  See the Recovery Console Help.

Expand a file out of the driver.cab:

Since the Windows 2000 driver files are in a .cab file, you can use the console's Expand command to view and extract a file out of a CAB.

There are two ways to start the Recovery Console:

1.  If you are unable to start your computer, you can run the Recovery Console from your Windows 2000 Setup disks, or from the Windows 2000 Professional CD (if you can start your computer from your CD drive).

2.  You can install the Recovery Console on your computer to make it available in case you are unable to restart Windows 2000.  You can then select the Recovery Console option from the list of available operating systems at initial boot.

If you frequently use Start|Run|program or URL|OK, and want a better way to accomplish this task, Window 2000 allows you to add an Address toolbar to your Taskbar:

1.  Right-click an empty area on the Taskbar and press Toolbars and Address.

2.  Use your mouse to drag the vertical separator to the right, resizing the Address toolbar.

Now, instead of pressing Start|Run|Program or URL|OK, you can type (or select) the program or URL into the Address toolbar and press Enter on your keyboard or press Go with your mouse.

If you want quick access to all the commands you can run with Windows2000, execute the following command line:

hh.exe mk:@MSITStore:C:\WINNT\Help\windows.chm::/ntcmds.htm

To have NumLock turned on for each user:

1.  Start Regedit and navigate to:

HKEY_CURRENT_USER\Control Panel\Keyboard\InitialKeyboardIndicators

2.  Change the value from 0  to  2.

3.  Turn NumLock on manually.

4.  Log off and back on again.

5.  For all users, make the same change to:

HKEY_USERS\.DEFAULT\Control Panel\Keyboard\InitialKeyboardIndicators

To increase the amount of memory Windows will save for locked I/O operations:

1.  Start Regedit and go to:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

2.  Edit the Value name:  ‘IoPageLockLimit’, Data Type: REG_DWORD, set Value to:

4096  - 32megs of memory or less
8192  - 32+ megs of memory
16384 - 64+ megs of memory
32768 - 128+ megs of memory
65536 - 256+ megs of memory

Dr. Watson is a program error debugger that detects and diagnoses program errors and creates User.dmp and DrWtsn32.log files to contain the diagnostic data.  In Windows NT these files are stored in the %systemroot% folder.  In Windows 2000, these files are stored in the
%systemdrive%\Documents and Settings\All Users\Documents\DrWatson  folder.  The DrWtsn32.log file is appended each time a program error occurs;  the User.dmp file is overwritten each time.

To turn off the Dr. Watson debugger, go to the following Registry key:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug

Set the Value name:  ‘Auto’, Data Type: REG_DWORD, Value: 0 to disable  or  Value: 1 to enable.

To re-enable Dr. Watson, you can change ‘Auto’ back to 1 or from a Command line type:  drwtsn –i

To change the folder for log files, go to the following Registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson

Change or add the Value name:  ‘LogFilePath’, Data Type: REG_SZ

That Registry key contains most of the values for Dr. Watson including:  ‘AppendToLogFile’, ‘CrashDumpFile’ (change from default name user.dmp), ‘CreateCrashDump’, ‘MaximumCrashes’, ‘SoundNotification’, ‘VisualNotification’, and ‘Wavefile’.

The ‘AppendToLogFile’ value controls whether Dr. Watson creates a new log file or appends data to the old log file for each application error that occurs.  Change or add the Value name: 
‘AppendToLogFile’, Data Type: REG_DWORD, Value: 0 new file  or  Value: 1 append to file.

The ‘CrashDumpFile’ value controls the path and filename to use when creating a crash dump file.
Change or add the Value name:  ‘CrashDumpFile’, Data Type: REG_EXPAND_SZ

The ‘CreateCrashDump’ value controls whether Dr. Watson creates a crash dump file after an application crash has occured.  Change or add the Value name: 
‘CreateCrashDump’, Data Type: REG_DWORD, Value:  0 to disable  or  Value: 1 to enable.

The ‘DumpAllThreads’ value controls whether Dr. Watson should dump the contents of all threads during an application error.  Change or add the Value name: 
‘DumpAllThreads’, Data Type: REG_DWORD, Value:  0 disable  or  Value: 1 enable.

The ‘DumpSymbols’ value controls whether Dr. Watson should dump the contents of the symbol tables during an application error.  Change or add the Value name: 
‘DumpSymbols’, Data Type: REG_DWORD, Value:  0 disable  or  Value: 1 enable.

The ‘SoundNotification’ value controls whether Dr. Watson plays a wav file when an application error occurs.  Change or add the Value name: 
‘SoundNotification’, Data Type: REG_DWORD, Value:  0 disable  or  Value: 1 enable.

The ‘WaveFile’ value specifies the path and filename of the wave file to be played during an application error.  Change or add the Value name:  ‘WaveFile’, Data Type: REG_EXPAND_SZ

The ‘VisualNotification’ value controls whether Dr. Watson displays a popup message box when it encounters an application error.  Change or add the Value name: 
‘VisualNotification’, Data Type: REG_DWORD, Value:  0 disable  or  Value: 1 enable.

There are various debugger utilities besides Dr. Watson.  Lotus Notes, for example, replaces Dr. Watson with its debugger.  To switch back to Dr. Watson, should another debugger be enabled, go to the following Registry key:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug

Change or add the Value name:  ‘Debugger’, Data Type: REG_SZ, Value:  drwtsn32 ‑p %ld ‑e %ld ‑g

When you clear the Add new documents to Documents on Start Menu box in TweakUI, Windows 2000 Logo-compliant programs no longer display the most recently used (MRU) file list, including the MRUs in the File, Save, and Open dialogs.  Windows 2000 Logo-compliant programs must honor the Do not keep history of recently opened documents Group Policy at User Configuration\AdministrativeTemplates\Start Menu & Taskbar.

To resolve the problem, either check the Add new documents to Documents on Start Menu box in TweakUI, or use Regedit and go to:

HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

Change the Value name:  ‘NoRecentDocsHistory’, Data Type REG_BINARY, to:  00 00 00 00.

NOTE:  TweakUI enables the policy by setting ‘NoRecentDocsHistory’ to:  01 00 00 00.

When you convert a Windows 2000 disk from basic to dynamic, all of the partition information is stored in a private database at the end of the disk.  The MBR (Master Boot Record) contains one type 0x42 partition table entry.  When a disk contains the System or Boot partition, the process, called ”rooting”, is different.

The entries in the partition table are kept intact, but the File System IDs are changed to 0x42 to indicated that they are dynamic.  This allows the BIOS to load the kernel and other files required to start the drivers needed to read the dynamic volume.  An entry is added for any unallocated space on the volume.