ERD Commander 2003

Users Guide
Winternals Software LP 3101 Bee Caves Road, Suite 150 Austin, Texas 78746 (512) 330-9130 (512) 330-9131 Fax www.winternals.com
Copyright 2003 Winternals Software LP

Table of Contents

1 Introduction...1
1.1 1.2 Overview of Use... 2 Sample Screen... 6
ERD Commander 2003 Setup..7
2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 System Requirements... 7 Booting with ERD Commander 2003... 8 License.... 9 Password Protection... 10 Selecting the Installed Applications.. 11 Adding OEM SCSI Drivers.. 12 Adding OEM Network Drivers.. 13 Adding Files to the CD-ROM Image... 14 Image Location... 15 Burning the ERD Commander 2003 CD-ROM.. 16
Using ERD Commander 2003...17
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 Logon.... 19 Windowing Shell... 22 System Information... 23 Explorer.... 24 Volume Properties... 26 Folder Properties... 27 Resetting Permissions... 28 Mapping Network Drives... 29 Adding a Domain... 30 Using File Search... 31 Using FileRestore... 33 Command Prompt... 35 Chkdsk... 44 Diskpart.... 45 Regsvr32.... 46 Notepad.... 47 Regedit... 48 Using Service and Driver Manager.. 50 Using Event Log Viewer... 52 Filtering Events.... 53 Using TCP/IP Configuration... 54 Using Disk Management... 56 Locksmith... 58 File Sharing... 59

Winternals Software

Page i
3.25 System Restore.... 61 3.26 System Compare... 63 3.27 Running External Commands.. 64

Disk Commander...66

4.1 4.2 4.3 4.4 4.5 4.6 Selecting a Drive Letter to Recover... 66 Selecting a Target Disk... 68 Lost Volume Scan... 68 Partition Table Backup... 69 Volume Recovery... 70 Salvaging Files... 72
Frequently Asked Questions..75 Sales...77 Technical Support...78 Index...79

Page ii

Introduction
When your Windows NT, Windows 2000, Windows XP or Server 2003 system becomes unbootable and youve exhausted the recovery options available with the operating system, you can rely on ERD Commander 2003 to provide full access to your dead system with a familiar Windows-like environment. ERD Commander 2003 provides the tools you need to help you quickly diagnose and repair the problem that is preventing your system from booting. Like the Recovery Console of Windows 2000 and Windows XP, as well as the previous versions of ERD Commander, ERD Commander 2003 makes any Windows NT/2000/XP/Server 2003 file system accessible, including FAT, NTFS and CDFS. Unlike those other utilities, ERD Commander 2003 offers both a graphical windowing environment and a command-line console. In addition, ERD Commander 2003 includes a service and driver manager, Registry editor, Explorer-like file system browser, Notepad-like text editor, Event Viewer, and local password changer so that you can gain access to accounts to locked accounts. And when you need to save files to another system on the network or to copy files from another system as part of the repair process, ERD Commander 2003 gives you full access to network file shares. With ERD Commander 2003, repairing your dead systems has never been easier or more intuitive.

Page 1

Overview of Use
ERD Commanders built-in tools allow you to perform many different types of system diagnosis and repair. A few of the ways that ERD Commander 2003 helps you solve problems include: Removing or Replacing Buggy Drivers You can use ERD Commander 2003 to delete or replace the image files of drivers or services that, because of a bug or misconfiguration, prevent Windows NT/2000 from booting. Updating Out-of-Date System Files Incorrectly applying service packs or system software updates can cause system DLLs to become out of sync with each other. In many cases this can prevent Windows NT/2000 from booting successfully. ERD Commander 2003 can copy up-to-date versions of old files from floppy disks, CD-ROMs, or other computers on your network. Correcting Misconfigured NTFS or Registry Security If excessively restrictive security attributes are applied to certain system files or directories on NTFS boot drives, or to some Registry keys, Windows will become unbootable. Using ERD Commander 2003s Explorer and Regedit you can reset permissions on files, directories and Registry keys to regain access. Updating Locked Files Once Windows NT/2000/XP/Server 2003 is up and running many system files cannot be replaced because the system keeps them locked. ERD Commander 2003 makes it possible to update such files because it runs when Windows NT/2000/XP/Server 2003 is off-line and the files are not open.

Page 2

Correcting Registry Problems A significant number of Windows NT/2000/XP/Server 2003 boot problems are the result of misconfigured Registry values. The ERD Commander 2003 Registry editor has all the capabilities and the same interface as the Windows NT/2000/XP/Server 2003 Registry editor, making it easy for you to inspect and change Registry settings. Recovering Deleted Files ERD Commander 2003 includes FileRestore, a utility that you can use to find and restore deleted files from any supported Windows NT/2000/XP/Server 2003 file system format, including FAT, FAT32, and NTFS. Copying Important Files off of a Dead System ERD Commander 2003 enables you to access files on a Windows NT/2000/XP/Server 2003 system that fails to boot. You can copy files to removable media such as floppy disks, Zip drives, or Jaz drives, or use ERD Commander 2003s network capabilities to copy them to another system on your network. Regaining Access to a System That You've Been Locked Out Of ERD Commander 2003s Locksmith utility allows you to list the accounts for a Windows NT/2000/XP/Server 2003 system and to change their passwords, including Administrator accounts. Viewing Event Logs Since the Event Logs of a system often contain clues that can help you diagnose a boot problem, ERD Commander 2003 includes an Event Log Viewer with the same interface as the Windows 2000/XP Event Log Viewer MMC snap-in, allowing you to inspect logs for relevant records.

Page 3

Running CHKDSK on Corrupt Drives ERD Commander 2003 will let you check the consistency of hard drives. Enabling and Disabling Services and Drivers You can list and modify the start types of a system's drivers and services with ERD Commander 2003s Service and Driver Manager utility. The utility implements an interface similar to the Windows 2000/XP Services MMC snap-in, which makes it easy to identify services and drivers and to disable those that are preventing a system from booting. Restoring Windows XP Restore Points Windows XPs Restore Point feature periodically creates snapshots of a systems state that includes system files and Registry data. Overcoming a deficiency of Windows XPs Restore Point functionality, ERD Commander 2003 allows you to restore unbootable systems to a previous Restore Point. Comparing a Working System with a Dead System ERD Commander 2003s System Compare utility lets you compare service and driver configuration and the system files of a dead system with that of a live system or a Windows installation media to which you direct it. This enables you to identify differences between working systems and one that doesnt boot in order to guide your repair process. Partitioning and Formatting Disks The Disk Management MMC snap-in that ERD Commander 2003 includes in its Computer Management utility has many of the features of the Windows 2000/XP Disk Management MMC snap-in, allowing you to delete, format, and create partitions and volumes. If you prefer a command-line environment you can use the corresponding command-line tool, DiskPart, to accomplish the same tasks.

Page 4

Scanning a Dead System for Viruses With ERD Commander 2003 you can share the drives of a system on the network so that you can access them from another computer. This allows you to use tools installed on other systems to aid in the repair process. For example, if you suspect a virus has attacked a computer you can shut it down, boot into ERD Commander 2003, share its drives, and then run a virus scanner on the drives from a different system. Registering COM/DCOM Server DLLs A system may become unstable if COM or DCOM registration information is corrupted or deleted. The standard Windows COM/DCOM server DLL registration utility, Regsvr32, requires that you be logged into a system into which you are registering DLLs, but ERD Commander 2003s Regsvr32 utility enables you to register COM/DCOM server DLLs into an installation thats offline.

Page 5

Sample Screen
This screenshot demonstrates a typical session using ERD Commander 2003 to access the Registry and service configuration of an unbootable system.

Page 6

ERD Commander 2003 Setup

System Requirements

ERD Commander 2003 requires that the target system have a bootable CDROM, and one of the following operating systems:
Windows NT 4 Windows 2000 Windows XP Windows Server 2003
Regardless of operating system, ERD Commander 2003 requires a minimum of 64MB of system memory and an x86 233MHz processor. Note that ERD Commander 2003 also gives you access to the drives of Windows 95, 98 and Me systems, although many utilities, such as the password changer, Registry editor and Event Log viewer do not function when accessing installations of those operating systems. The ERD Commander 2003 Boot CD-ROM Wizard runs on Windows 95, 98, Me, NT, 2000, XP and Server 2003.

Page 7

Booting with ERD Commander 2003
There are two delivery methods for ERD Commander 2003: as a Boot-CD Wizard and as a bootable CD-ROM. You receive the Boot CD-ROM Wizard as an executable file when you download ERD Commander 2003 after an online purchase; the version of ERD Commander 2003 that ships as physical media is a bootable image that also includes an installer for the Boot-CD Wizard. Use the Boot CD-ROM Wizard to create a bootable CD-ROM ISO image. A CD-ROM ISO image is a file that represents the raw contents of a CD-ROM that you can burn onto a writable CD-ROM with most popular CD-ROM burning software. You will need several items in addition to successfully create a bootable CD-ROM from the ISO image the Boot CD-ROM Wizard creates:

Page 15

2.10 Burning the ERD Commander 2003 CD-ROM
Most popular CD-ROM burning applications offer the option to write a CDROM from a CD-ROM ISO file. Check with your softwares documentation for information on how to do this. For additional tips, please check the Winternals Product Knowledge Base: http://www.winternals.com/support/kbfiles/ISOtoCD.pdf

Page 16

Using ERD Commander 2003
Once ERD Commander 2003 boots, a stripped-down version of Windows XP will start and run the ERD Commander 2003 windowing environment. Its important to keep in mind that, although this graphical environment looks like Windows and even has similar utilities, it is not Windows code and therefore behaves slightly differently. Also note that your end-user license agreement prohibits use of ERD Commander 2003 as a general-purpose operating system, and the environment is designed to reboot automatically 24 hours after starting. NOTE: it is important that you do not remove the ERD Commander 2003 CDROM from the system while ERD Commander 2003 is running. Doing so could result in a lock-up of ERD Commander 2003, requiring a reboot. The ERD Commander 2003 environment provides a number of powerful utilities that help you identify and repair problems that are preventing a system from booting. These include:
Logon Windowing Shell System Information Explorer File Search FileRestore Command Prompt Chkdsk Regsvr32 Notepad Regedit

Page 17

Service and Driver Manager Event Log Viewer TCP/IP Configuration Disk Management Locksmith File Sharing System Restore System Compare Disk Commander (available if ERD Commander 2003 is purchased as part of the Administrators Pak)
This section describes the functionality and use of each of these tools. In addition, you can execute Win32 applications other than those that are part of the ERD Commander 2003 environment.

Page 18

When ERD Commander 2003 boots it executes the Winternals Logon application. The first step performed by the Logon application is to start the networking services. These services assume that a DHCP server is present on your network and attempt to obtain an IP address. If your network uses static IP addresses rather than DHCP you can use the TCP/IP Configuration utility after logging in to specify a static IP address. If the ERD Commander 2003 CD was generated by the Boot CD-ROM Wizard, the Logon application next displays the licensing information entered during execution of the wizard. Otherwise it will prompt you to enter ERD Commander 2003 license text or specify a file containing an ERD Commander 2003 license. Next, the Logon application scans the systems hard-disk volumes for Windows NT, 2000, XP, and Server 2003 installations. It displays the system root directory of located installations, the type of operating system installed, and service pack information. It also allows you to specify the language layout of your keyboard. The default language selection is the one specified by the operating system installation entered in the edit box of the Logon application.

Page 19

If the system you wish to repair is not in the list or the operating system is displayed as "unknown", then some or all of the Registry hives for that installation are damaged, missing, or have restrictive permissions that do not allow the System account access. Registry hives are the Registrys on-disk storage files and are stored under \SystemRoot\System32\Config (where SystemRoot is the system root directory of a Windows NT, 2000, XP, or Server 2003 installation). Choose the installation you wish to repair from the list, by manually entering the system root path, or by browsing to the system root directory. When you make a selection the Logon application validates the SYSTEM, SOFTWARE, SAM and SECURITY Registry hives and notifies you if any of them are corrupt or missing. Note that in this event the corresponding portions of the Registry will be inaccessible by the Winternals Registry editor and other ERD Commander 2003 utilities also have limited functionality.

Page 20

The Logon application allows you to choose a keyboard layout and time zone using the drop down controls. The default selections for keyboard layout and time zone are taken from the installation you have currently entered into the installation selection field if the Registry of that installation is accessible. Clicking the OK button selects the specified installation and starts the ERD Commander 2003 Windowing Shell, described in the next section. After you have completed work on an installation and log off the Windowing Shell you return to this Logon dialog. Clicking the Reboot button performs a clean shutdown and reboot of the computer.

Page 21

Windowing Shell
The ERD Commander 2003 Windowing Shell closely resembles Microsoft's Explorer shell. It has a task bar, Start menu, and desktop shortcuts. However, you cannot move the Windowing Shells task bar, edit the items on the Start Menu, move or modify existing desktop shortcuts, or create new desktop shortcuts. The Windowing Shell provides the familiar desktop motif and allows you to easily access ERD Commander 2003 applications and manage multiple running applications with taskbar buttons. NOTE: a limitation in the ERD Commander 2003 operating environment prevents concurrent execution of more than approximately 4 applications. ERD Commander 2003 will inform you when starting another application might exceed the limit.

Page 22

System Information
The ERD Commander 2003 System Information utility is accessed via the Administrative Tools folder of the Start menu. The utility reports extensive information about the system you are repairing, including the operating system version, service pack, hotfixes, registered owner and organization and more. It also displays the installations computer name as well as the computer name (listed as the "Real computer name") that ERD Commander 2003 randomly assigns while it is running. The value of the System root, which represents the root folder of the installation, can be useful to determine where key system files, such as service and driver files and Registry hives, reside.

Page 23

Explorer
ERD Commander 2003 Explorer, which is accessible from the Start menu, allows you to browse the systems volumes as well as the NetBIOS network neighborhood. Active Directory browsing is not supported. The Explorer window has a tree view on the left and a list view on the right that displays the contents of the folder selected in the tree view. The My Computer and Network Neighborhood desktop shortcuts open instances of Explorer that select the associated folder. ERD Commander 2003 Explorer supports many of the operations supported by the Windows Explorer, including drag-and-drop, the up-directory button, in-place rename, new-folder creation, delete, and property viewing for most items. It also provides for mapping file shares exported by other systems on the network to local drive letters, and includes built-in support for cabinet (.CAB) and ZIP files. ERD Commander 2003 Explorer obtains icon information for file extensions from the Software Registry hive of the system you are repairing. If the Software hive is corrupt or missing Explorer displays only basic icons. Note that, unlike the default behavior of Windows Explorer, ERD Commander 2003 Explorer displays hidden folders and files (those with the hidden attribute set), displaying them with faded icons. Also unlike Windows Explorer, you cannot drag-and-drop items between different Explorer windows; use the Copy To button on the toolbar for this purpose. The following sections describe the Property dialogs associated with different items, as well as how to map network shares to local drive letters.

Page 24

Page 25

Volume Properties

Selecting Properties from a volumes context menu (accessible by rightclicking on a volume) or selecting Properties from the File menu launches a dialog that displays information about a volume, including statistics on total size and free space. See section 3.7, Resetting Permissions, for a description of the Reset Permissions button.

Page 26

Folder Properties
You can view detailed information about a folder by choosing Properties from the folders context menu or selecting Properties from the File menu when the folder selected. The Map Network Drive button enables when you select a folder that represents a network share, allowing you to map the share to a local drive letter. Find more information in section 3.8, Mapping Network Drives. See section 3.7, Resetting Permissions, for a description of the Reset Permissions button. Editing a folders name in the Properties dialog and then applying the change renames the folder. Similarly, you can change the attributes of the folder in the Attributes area of the dialog, and use the Set Child Attributes to apply a set of attributes to all of the files and folders contained within the selected folder.

Page 27

Resetting Permissions
A system can become unbootable if permissions are set on NTFS folders or directories that prevent the operating system from accessing the files required for the boot process. The Reset Permissions button on a volume or folder Properties dialog changes the permissions on the volume folder, and optionally on child folders, to a security descriptor that gives the Everyone group (all users) full access.

Copy Move View properties Explore (opens an instance of ERD Commander 2003 Explorer with the target location opened) Open (opens documents and executes executable images)
Double-clicking on a result also displays the properties file or folder for that item.

Page 31

Page 32

3.11 Using FileRestore

Use ERD Commanders FileRestore utility to recover deleted files from the system you are repairing. Its interface, like that of ERD Commander 2003 File Search, is similar to that of the Windows 2000 File Search utility. The search pattern you enter can contain any subset of the file or path names for which you wish to search, and can include the asterisk (*) wild-card character. Optionally, you can modify your search to only include results with modifications within a certain time period, or of a particular size. When you Click the Search button FileRestore searches the locations you specified and displays found items in the right pane of its window. FileRestore attempts to determine whether each deleted file is recoverable and reports the result in the Recoverability column. If a file is marked Likely it means that none of the file's data is known to be overwritten by other files. However, this is only an estimate of the files condition, and it is possible that even a file marked Likely will contain corrupt data. In general the longer the time since a file has been deleted the less likely that it can be recovered. When searching for files on FAT or FAT32 volumes the first letter of the file name cannot always be retrieved. For this reason FileRestore displays files that match all characters entered in Search for files named, as well as those matching all characters but the first. Whenever the first letter cannot be retrieved it is replaced by the question mark character (?) when displayed and by an underscore (_) when the file is copied to a new location. If a file is found but it cannot be determined which directory it belongs to (usually because the parent directory is also deleted) then it is placed in a directory labeled.Unknown Folder #. It is possible for there to be multiple orphan directories, each corresponding to a different directory that no longer exists.

Page 33

NOTE: To reduce the possibility of overwriting data that you may wish to recover, whenever practical you should restore files to a location other than the source volume.

Page 34

3.12 Command Prompt
ERD Commander 2003 Command Prompt presents a subset of the functionality implemented by the Windows XP command-prompt that includes most built-in commands, the ability to execute external applications, and batch file capabilities. This section serves as reference for the Command Prompts built-in commands.

3.12.12

Exits the command prompt

3.12.13

Provides Help information for ERD Commander 2003 built-in Command Prompt commands.
HELP [command] Command Displays specific information on the specified command.

Page 39

3.12.14
Displays drive letter to partition mappings. This command displays the drive letter assignments made by ERD Commander 2003. For each drive you will see the device name, volume label, file system type and drive size. If the System account or Administrators group is denied access to an NTFS drive because of the security settings applied to the drive's root directory, the file system type will be <?>. Use the Volume Properties dialog for the volume to unlock the drive. An example mapping is shown below:
Mapped drive letters: A: C: WINXP NTFS D: DEV NTFS E: SRC NTFS F: MSDN NTFS G: GAMES NTFS H: I: Audio CD CDFS \Device\Floppy0 \Device\HarddiskVolume2 \Device\HarddiskVolume3 \Device\HarddiskVolume4 \Device\HarddiskVolume5 \Device\HarddiskVolume6 \Device\CdRom0 \Device\CdRom1
7.81 10.69 4.48 2.41 8.50

GB GB GB GB GB

0.00 MB

3.12.15

Mkdir/Md

Creates a directory.

MKDIR [drive:]path MD [drive:]path
MKDIR creates any intermediate directories in the path, if needed. For example, assume \a does not exist then:
mkdir \a\b\c is the same as: mkdir \a mkdir \a\b mkdir \a\b\c

Page 40

3.12.16
Moves or renames a file or directory.
MOVE Source [Target] Source Target Specifies the path and name of the file(s) to move. Specifies the path and name to move file(s) to.

3.12.17

Rmdir/Rd
Removes (deletes) a directory.
RMDIR [/S] [/Q] [drive:]path RD [/S] [/Q] [drive:]path /S Removes all directories and files in the specified directory in addition to the directory itself. Used to remove a directory tree. Quiet mode, do not ask if ok to remove a directory tree with /S

3.12.18

Screen
Sets console screen information.
SCREEN [width height] width height Specifies width of the console window. Specifies height of the console window.

3.12.19

Displays, sets, or removes command prompt environment variables.
SET [variable=[string]] variable string Specifies the environment-variable name. Specifies a series of characters to assign to the variable.
Type SET without parameters to display the current environment variables.

Page 41

3.12.20
Starts a program in a new command prompt window.
START [program] [parameters] program parameters Specifies the program. Specifies the parameters for the program.

3.12.21

Displays the current time.

Page 49

3.18 Using Service and Driver Manager
The ERD Commander 2003 Service and Driver Manager, accessible in the Administrative Tools folder of the Start menu, is an ERD Commander 2003 Computer Management utility snap-in. The Service and Driver Manager is actually an interface to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services part of the Registry where service and driver configuration subkeys are located for the system you are repairing. Every service and driver has a subkey that includes values that specify its start type, and an optional description and display name. The Service and Driver Manager shows this information and allows you to edit the start type when you view the properties of a selected service or driver. You can access the Properties dialog by selecting the service or driver and double-clicking, or by choosing Properties from the Action menu or from the context menu that appears when you right-click. Typical repair operations involve disabling a service or driver that is preventing a system from booting, or replacing a corrupt service or driver file. To disable a service or driver, display its properties and change the startup type to Disabled. The Properties dialog also reports the path to the service or drivers executable image.

Page 50

Page 51
3.19 Using Event Log Viewer
ERD Commander 2003 Event Log Viewer enables you to examine the System, Application, and Security event logs of the system you are repairing. It functions like the Windows Event Viewer, allowing you to look for entries that might help you diagnose a problem that is preventing a system from booting. Examples include blue-screen crash errors and errors or warnings that indicate problems with particular services or drivers. Event Log Viewer is a snap-in to the ERD Commander 2003 Computer Management utility that you access via the Administrative Tools folder in the Start menu. The three event logs displayed by ERD Commander 2003 Event Log Viewer are stored in the system's SystemRoot\System32\Config folder. If any of these files are missing or corrupt, you will see no entries in the corresponding node. To view detailed information about the entry, choose Properties from the Action menu or an event log entrys context menu, or double-click on the entry. Use the up and down arrows in the Properties dialog to move between different event entries.

Page 52

3.20 Filtering Events
You can filter the events that you want to see by selecting the Filter menu entry from the Action menu of Computer Management. The Filter dialog, shown below, allows you to filter based on the event severity, source, category, date, and other attributes.

By selecting a drive letter here you advance straight to the Salvaging Files screen.

Page 67

Selecting a Target Disk
If the volume you are interested in was not assigned a drive letter, or you elected not to use the letter assigned, then you must help Disk Commander to locate the volume. Select which physical hard disk that contains the volume you need to recover files from.

Lost Volume Scan

The next page in the wizard gives you the opportunity to scan for lost volumes. Disk Commander will always look at the partitions defined in the partition table for the disk you have selected, but it can also perform an exhaustive scan of your disk attempting to locate volumes that do not appear in your partition table. The exhaustive scan takes a long time to perform and is usually not necessary to recover your data. You may want to skip the scan initially and

Page 68

see if Disk Commander can locate your volume without it. If it cannot then back up and perform the scan. After you perform a scan Disk Commander will save the results in a file so you do not have to perform the scan again, even if you exit and restart the program.

Partition Table Backup

Because Disk Commander allows you to modify your partition table, you may want to create a back up of the information stored there. Disk Commander allows you to back up the partition table entries, as well as the boot sectors of each of your partitions, and save them to a file. The backup file can be stored in the Disk Commander installation directory (if running from a floppy disk it will be stored on the floppy disk) or on a floppy disk you designate.

Page 69

You can use the back up to restore your partition table and boot sectors in the event that your changes cause additional problems with your system.

Volume Recovery

The Recover Volume screen is the main screen for analyzing and modifying your disk. The screen displays information about your disk in several ways. The top most pane shows the layout of partitions on your disk. Every disk starts with a Master Boot Record (MBR) shown in red, followed by one or more partitions and extended partitions. NTFS volumes are shown in blue, while FAT volumes are shown in green. Extended boot records (used to delineate logical volumes) are shown in yellow. The middle pane shows volumes that were discovered by Disk Commander while scanning your disk. (If you elected not to perform a disk scan on the Lost Volume Scan screen then this area will not be shown.) Some of the

Page 70

volumes in this area may overlap your regular volumes; these may be remnants of volumes created and then deleted at some point in the past. You may also see volumes that seem to be identical to existing volumes, but there is a slight difference: these volumes are shown because they can be mounted using an alternate boot sector. If the regular boot sector for a volume has been corrupted you can use this backup version of the partition to repair or salvage data in the original. The bottom pane provides a summary of all the displayed volumes. It first lists the regular volumes, followed by lost volumes. Clicking an entry in the top or middle pane will automatically select the corresponding entry in the bottom pane, and vice versa. You can select a volume and click the Details button to obtain additional information about the volume youve selected.

Page 74

Frequently Asked Questions
Why do I get access denied errors when I try to replace a system's Registry hives? If you are running a utility that accesses the Registry of the system being repaired you will be unable to replace the Registry hives. Utilities that access the Registry include Regedit, Explorer, Service and Driver Manager, System Information, and Event Log Viewer. Why didnt you use the Windows versions of the tools instead of writing your own? ERD Commander 2003 includes special versions of several utilities to comply with Microsoft licensing requirements, and to provide interfaces that are intuitive in its repair environment. For example, the Windows Regedit utility would only allow you to edit the ERD Commander 2003 Registry, whereas ERD Commander 2003 Regedit allows you to edit the Registry of the installation that you wish to repair. Why cant I have more than 4 applications active at the same time? This limit results from the restricted environment in which ERD Commander 2003 executes. Why are some Registry keys empty when I know I should see subkeys? When you use Regedit, ERD Commander 2003 attempts to load the Registry hives (files) that make up the Registry keys that you are familiar with. The Logon application informs you if it cannot load a hive, and those that it cannot load result in empty Registry keys within Regedit and possibly limitations to the functionality of other ERD Commander 2003 applications. Registry hives reside in

Page 75

%systemroot%\system32\config and cannot be loaded if they are either missing or corrupt. The correspondence between hives and their Registry keys is as follows:
Hive Name SAM SECURITY SOFTWARE SYSTEM Registry Key(s) HKLM\SAM HKLM\SECURITY HKLM\SOFTWARE HKLM\SYSTEM, HKCR
Why does ERD Commander 2003 freeze when I eject the ERD Commander 2003 CD-ROM? Individual ERD Commander 2003 applications are loaded into memory on demand. If you remove the ERD Commander 2003 CD the system cannot read any items not already in memory, potentially causing a fatal error within the ERD Commander 2003 environment. In this event the system must be rebooted to continue running ERD Commander 2003. Why does my application behave strangely or fail to execute when I run it inside of ERD Commander 2003? The ERD Commander 2003 environment is a stripped-down version of the standard Windows XP environment and is missing many noncore system files, services, and run-time support.

Page 76

Order Winternals products online at www.winternals.com, or by fax, phone or email: Phone: Fax: Email: (800) 408-8415 (512) 330-9130 (512) 330-9131 sales@winternals.com

Winternals Software LP 3101 Bee Caves Road Suite 150 Austin, TX 78746 USA

Page 77

Technical Support
To view Online Help, press F1 or select Help from the ERD Commander 2003 Start Menu. To access the ERD Commander 2003 Support Knowledge Base, visit our support web site at: www.winternals.com/support You may also request help by email for issues not covered in the Online Help or Support Knowledge Base. Please visit: www.winternals.com/support/getsupport.asp or send email to: support@winternals.com Customers who have purchased Product Assurance may receive phone support by calling 512-330-9861. Before contacting support, please determine if the problem is reproducible, and if so, record the steps necessary to reproduce it. In addition, please have the following information about your system ready:
Windows version (including Service Pack) of the system being repaired, Memory size, disk types, and file system types Version of ERD Commander 2003 The License Number shown on the lower right of your ERD Commander 2003 desktop

Page 78

delete, 2, 6, 25, 43, 65, 71 desktop shortcuts, 23, 25 DHCP server, 20, 63 DIR, 39, 44 directories, 2, 29, 30, 37, 42, 46, 48, 50, 71, 82, 83, 85 Disabling a driver, 58 Disconnect Network Drive, 31 Disk Commander, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85 Disk Management, 6, 19, 52, 65, 66 DiskPart, 6, 52, 65, 66 DISKPART command, 39 DLL, 2, 6, 40, 53 DNS, 31, 63 DOS, 77 Drag-and-drop, 25 drivers, 2, 5, 13, 14, 60 ECHO command, 39, 44 ERASE command, 39, 43 Event Log viewer, 1, 4, 8, 19, 51, 60, 86 EXIT command, 39, 44 Explorer, 1, 2, 18, 23, 25, 31, 33, 34, 51, 82, 86 FAT, 1, 3, 36, 80 FAT32, 3, 36, 77 File Search, 18, 34, 36 File Sharing, 19, 63, 69 file system, 1, 3, 46, 51, 89 FileRestore, 3, 18, 36 Files, salvaging, 76 Filtering Events, 61 floppy disks, 2, 3 Folder Properties, 28 HELP command, 39, 44 HKEY_, 55, 58 Image files, 2 Image Location, 16 Installed Applications, 12 IP address, 20, 63 ISO image, 9, 10, 15, 16 JAZ drives, 3 Keyboard layout, 22 Language selection, 20 License, 10, 89 License agreement, 18 licensing, 10, 20, 66, 86 Locksmith, 19, 67 Logon, 18, 20, 21, 22, 87
Active Directory, 25 Adding a domain, 33 Adding Files to the CD-ROM Image, 15 Adding OEM Network Drivers, 14 Adding OEM SCSI Drivers, 13 Administrative tools, 24, 58, 60, 63, 65, 67, 69, 71 Administrator account, 4 AllowExternalCommand, 75 ATTRIB command, 38, 42 Attributes, 28, 44 blue-screen, 60 Boot CD-ROM Wizard, 8, 9, 10, 11, 15, 16, 20 boot drives, 2 bootable CD-ROM, 8, 9, 10 Boot-CD Wizard, 9 Booting, 9 BUFFER command, 38, 42 Built-in tools, 2 CALL command, 38, 42 CD command, 9, 10, 11, 12, 15, 16, 17, 18, 20, 38, 42, 46, 51, 73, 74, 87 CDFS, 1, 46 CDR, 9 CD-ROM burner, 9 CD-ROM, burning, 9, 16 CD-ROMs, 9 CDRW, 9 CHDIR command, 38, 42 CHKDSK, 18, 51, 66 CHKDSK command, 5, 39 CLS command, 39, 43 COM, 6, 40, 53, 71 Command Prompt, 18, 38, 39, 40, 44, 48, 49, 51, 74, 75 command-line, 1, 6, 42, 51, 52, 65 Computer Management utility, 6, 52, 58, 60, 65 computer name, 24, 69, 73 context menu, 27, 28, 31, 34, 58, 60, 73 Copy, 1, 2, 3, 34, 43, 50, 82, 83, 84 COPY command, 39, 43 Copy To, 25 Date Command, 39, 43 DCOM, 6, 40, 53 DEL command, 39, 43

Re: ERD Floppy for SBS 2003
Source: http://www.techarchive.net/Archive/Windows/microsoft.public.windows.server.sbs/200505/msg07230.html
From: "sbs2003" <sbs2002@xxxxxxxxxx> Date: Mon, 30 May 2005 20:15:48 GMT More specifically, does anyone use Winternal's ERD Commander 2002 with Windows Small Business Server 2003? ERD Commander 2002 is part of the Winternals Administrator Pak version 3.0. I know that the current version of ERD Commander is 2005 but don't know if spending $300 on it gives me anything that I need that I don't already have in the 2002 version. I am just looking to create a bootable CD to bring me to the Winternals recovery console on the SBS 2003 machine. Thank you. "sbs2003" <sbs2002@xxxxxxxxxx> wrote in message news:afKme.4920$Lb.1717@xxxxxxxxxxx > Does anyone happen to know if Winternals Administrator Pak version 3.0 > works with Small Business Server 2003? > I used it with Windows NT 4 Server and it creates a much more useful set > of recovery disks than RDisk ever did. bringing you to a command prompt > that lets you replace incorrect raid drivers for instance. Thank you. > > "Steve Foster [SBS MVP]" <steve.foster@xxxxxxxxxxxxx> wrote in message > news:xn0e2vh341ihfz000@xxxxxxxxxxxxxxxxxxxxxxx >> Dave F wrote: >> >>> I have not found a way to create an ERD for my SBS 2003 server. The old >>> standby RDISK /S does not work. Does anyone know how to generate the >> ERD? >>> >>> Thanks, >>> Dave >> >> ERDs have been replaced by ASR disks. Create them with NTBackup. >> >> >> Steve Foster [SBS MVP] >> >> MVPs do not work for Microsoft. Please reply only to the newsgroups. > >
Re: ERD Floppy for SBS 2003.
References: ERD Floppy for SBS 2003 From: Dave F Re: ERD Floppy for SBS 2003 From: Steve Foster [SBS MVP] Re: ERD Floppy for SBS 2003 From: sbs2003 Prev by Date: Fax pending Next by Date: Re: Disk Space on C: Previous by thread: Re: ERD Floppy for SBS 2003 Next by thread: Strange RWW problem Index(es): Date Thread