Learn Windows XP Professional in 15 Minutes a Week: Troubleshooting the Windows XP Professional Setup

Learn Windows XP Professional in 15 Minutes a Week: Troubleshooting the Windows XP Professional Setup


May 15, 2002

by Jason Zandri
www.2000trainers.com

Welcome to this week's installment of Learn Windows XP Professional in 15 minutes a week, the fifth in the series. This article covers Troubleshooting the Windows XP Professional Setup.


Troubleshooting the Windows XP Professional Setup

Usually when you are going about your Windows XP Professional installation, you will not run into any issues, particularly if you are sure that the installed system hardware meets the minimum Windows XP Professional hardware requirements by verifying all of the hardware is on the Hardware Compatibility List (HCL) at the Microsoft Website.

Windows XP Professional supports only the devices listed in the HCL. If your hardware isn't listed, contact the hardware manufacturer and request a Windows XP Professional driver or replace the hardware to avoid potential issues.

Support means that while the operating system may load and run on unsupported hardware and software, any issues that come up with the system will not be covered (i.e. supported) by Microsoft Technical Support if you should need to engage them.

If this has been done beforehand and issues do arise, there are a couple of "textbook" events that can be looked at first that will cover some of the more common problems you might encounter during installation and these will generally be what is at issue most of the time.


Common Installation Problems and Troubleshooting Tips


Media errors - When you are installing Windows XP Professional from a CD-ROM and run into problems, the quickest way to try to resolve the issue is to use a different CD-ROM. Even if the CD-ROM you are using has worked a dozen times before, the drive it is in at the time of the error may have trouble reading it or the disk itself may have been newly damaged by a fall or some other issue. You can attempt to clean a fingerprint-laced CD-ROM as a troubleshoot point as well. If you should need to request a replacement CD-ROM, you can contact Microsoft or your point of purchase.

You can also try using a different computer and CD-ROM drive. If you can read the CD-ROM on a different computer, you can perform an over-the-network installation if that option is available to you.

If one of your Setup disks is not working, download a different set of Setup disks. (The ability to directly create setup floppies has been dropped from Windows XP. Setup boot disks are available only by download from Microsoft.) The Setup boot disks are available so that you can run Setup on computers that do not support a bootable CD-ROM. There are six Windows XP Setup boot floppy disks. These disks contain the files and drivers that are required to access the CD-ROM drive through generic PCI drivers and begin the Setup process.

You may also find that the Windows XP Professional setup program is unable to copy files from the CD-ROM. In this event, it may be possible to either replace the drive with a supported drive (as this is usually the issue), or you can attempt your installation via a different method such as installing over the network (as mentioned above) or by copying the files to the local drive first, outside of the installation program, as sometimes the copy failure only crops up after the Windows XP Professional setup program is running.


Insufficient disk space errors - The current minimum hardware requirements for Windows XP Professional at the time of this writing is as follows:

  • 300MHZ or higher processor clock speed recommended (233 MHz minimum required, can be single or dual processor system) Intel Pentium/Celeron family, or AMD K6/Athlon/Duron family, or compatible processor recommended

  • 128MB of RAM or higher recommended (64MB minimum supported; may limit performance and some features)

  • 1.5GB of available hard disk space

  • Super VGA (800 W 600) or higher-resolution video adapter and monitor

  • CD-ROM or DVD drive

  • Keyboard and Microsoft Mouse or compatible pointing device

If you do not have 1.5GB of available hard disk space on a single partition, you will not be able to complete the installation in most cases.

You can use the setup program to create additional partitions that are large enough for the installation if there is enough space on the drive, or you can elect to delete existing data on the current partition to make enough room for the installation.


Troubleshooting using Setup Logs

Windows XP Professional generates a number of log files during the setup routine that contain information that was logged during installation that will assist you when you are attempting to resolve problems that may have occurred during the setup.

Action Log (SETUPACT.LOG) - The action log records the actions that the Setup program performs in chronological order and is saved as SETUPACT.LOG.

The setup log that I have available from my system is 165KB in size and too large to post here in its entirety, but I have cut a few sections out so that you can see what some of the entries look like.

(The SETUPACT.LOG can be found in the <DRIVE LETTER>\Windows directory in a default Windows XP Professional installation)

GUI mode Setup has started.
SXS Installation Succeed for J:\I386\asms
J:\I386\NT5INF.CA_ was copied to H:\WINDOWS\system32\dllcache\NT5INF.CAT.
J:\I386\NT5.CA_ was copied to H:\WINDOWS\system32\dllcache\NT5.CAT.
J:\I386\NTPRINT.CAT was copied to H:\WINDOWS\system32\dllcache\NTPRINT.CAT.
J:\I386\NT5IIS.CA_ was copied to H:\WINDOWS\system32\dllcache\NT5IIS.CAT.
J:\I386\MAPIMIG.CA_ was copied to H:\WINDOWS\system32\dllcache\MAPIMIG.CAT. H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\System32\storprop.dll.
J:\i386\AUTOEXEC.NT_ was copied to H:\WINDOWS\System32\AUTOEXEC.TMP.

The external program RUNDLL32 shell32,Control_RunDLL intl.cpl,,/f:"H:\WINDOWS\System32\$winnt$.inf" /s:"J:\I386" returned exit code 0.

NetSetup: SetupMode: 0x1, ProductType: 0x0, OperationFlags: 0x8000
H:\WINDOWS\System32\usbhub.sys was not deleted because of the following error:
The system cannot find the file specified.

H:\WINDOWS\System32\openhci.sys was not deleted because of the following error:
The system cannot find the file specified.

H:\WINDOWS\System32\usbohci.sys was not deleted because of the following error:
The system cannot find the file specified.

H:\WINDOWS\System32\usbport.sys was not deleted because of the following error:
The system cannot find the file specified.

H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\system32\drivers\drmk.sys.
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\system32\drivers\es1371mp.sys.
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\System32\ksproxy.ax.
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\System32\ksuser.dll.
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\system32\drivers\portcls.sys.
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\System32\DRIVERS\el90xnd5.sys.
NetSetup: Status of InitFromAnswerFile: 0x0
desk.cpl: Returning 0xe000020e for function 0x17 and device PCI\VEN_1002&DEV_5144&SUBSYS_00081002&REV_00\4&15C4952B&0&0008
desk.cpl: Returning 0xe000020e for function 0x18 and device PCI\VEN_1002&DEV_5144&SUBSYS_00081002&REV_00\4&15C4952B&0&0008
desk.cpl: Returning 0xe000020e for function 0x15
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\System32\atidvag.dll.
H:\WINDOWS\Driver Cache\i386\driver.cab was copied to H:\WINDOWS\System32\DRIVERS\atimtag.sys.
desk.cpl: Returning 0xe000020e for function 0x22
desk.cpl: Returning 0xe000020e for function 0x20
desk.cpl: Disabled 0 legacy devices in 1 tries
desk.cpl: Returning 0x00000000 for function 0x2 and device PCI\VEN_1002&DEV_5144&SUBSYS_00081002&REV_00\4&15C4952B&0&0008
desk.cpl: Returning 0xe000020e for function 0x1e
Input Install: Quiet install requested.
H:\WINDOWS\System32\propext.inf was not deleted because of the following error:
The system cannot find the file specified.

J:\i386\lcltechy.xm_ was copied to H:\WINDOWS\srchasst\mui\0409\lcltechy.xml.
The external program RUNONCE -r returned exit code 1.
SetUpVirtualMemory: ENTER
BuildVolumeFreeSpaceList: C:\, spc=8, bps=512, freeclus=1703364, totalclus=2096474
BuildVolumeFreeSpaceList: C:\, FreeSpace = 12682011648
BuildVolumeFreeSpaceList: C:\ had 120586240 byte pagefile, new FreeSpace = 12802597888
BuildVolumeFreeSpaceList: Free space on C:\ is 6768 MB
BuildVolumeFreeSpaceList: D:\, spc=8, bps=512, freeclus=4194189, totalclus=4445179
BuildVolumeFreeSpaceList: D:\, FreeSpace = 34294496256
BuildVolumeFreeSpaceList: Free space on D:\ is 16383 MB
BuildVolumeFreeSpaceList: E:\, spc=8, bps=512, freeclus=226773, totalclus=4445179
BuildVolumeFreeSpaceList: E:\, FreeSpace = 0928862208
BuildVolumeFreeSpaceList: Free space on E:\ is 885 MB
BuildVolumeFreeSpaceList: F:\, spc=8, bps=512, freeclus=253703, totalclus=4445179
BuildVolumeFreeSpaceList: F:\, FreeSpace = 01039167488
BuildVolumeFreeSpaceList: Free space on F:\ is 991 MB
BuildVolumeFreeSpaceList: G:\, spc=8, bps=512, freeclus=2085301, totalclus=2096482
BuildVolumeFreeSpaceList: G:\, FreeSpace = 14246425600
BuildVolumeFreeSpaceList: Free space on G:\ is 8145 MB
BuildVolumeFreeSpaceList: H:\, spc=8, bps=512, freeclus=1901387, totalclus=2096482
BuildVolumeFreeSpaceList: H:\, FreeSpace = 13493113856
BuildVolumeFreeSpaceList: H:\ had 41943040 byte pagefile, new FreeSpace = 13535056896
BuildVolumeFreeSpaceList: Free space on H:\ is 7467 MB
BuildVolumeFreeSpaceList: I:\, spc=8, bps=512, freeclus=8165262, totalclus=13247600
BuildVolumeFreeSpaceList: I:\, FreeSpace = 73380142080
BuildVolumeFreeSpaceList: Free space on I:\ is 31895 MB
SetUpVirtualMemory: loc 1
Setup configured the system to place a 768 MB pagefile on drive H:.
Crashdump was enabled.
SetUpVirtualMemory: EXIT (1)
Setup invoked the external program shmgrate.exe Fix-HTML-Help.
GUI mode Setup has finished.


As I mentioned before, the log file is much larger and has a lot more to it, but this cross section should give you a better idea of what is there.


Additional Logs for Troubleshooting

Error Log (SETUPERR.LOG) - The error log shows any errors that occurred during setup and their severity level. If errors do occur, the log viewer displays the error log at the end of setup.

(The SETUPERR.LOG can be found in the <DRIVE LETTER>\Windows directory in a default Windows XP Professional installation)

The log will be created even if no errors occur. (I do not have anything available to show you from the error log as mine is empty. Sorry.)

Setup also creates a number of additional logs during setup.

<DRIVE LETTER>\Windows\comsetup.log - Outlines installation for Optional Component Manager and COM+ components. A subsection of mine is below.

COM+[11:31:52]: ********************************************************************************
COM+[11:31:52]: Setup started - [DATE:01,07,2002 TIME: 11:31 pm]
COM+[11:31:52]: ********************************************************************************
COM+[11:31:52]: Start OC_INIT_COMPONENT Component = com
COM+[11:31:52]: INF VERSION (com) = 2001,12,4414,42
COM+[11:31:52]: Instantiating CMasterNT5Wks
COM+[11:31:52]: Memory usage for setup process...
COM+[11:31:52]: PeakWorkingSetSize: 26336 Kb, WorkingSetSize: 23308 Kb
COM+[11:31:52]: QuotaPeakPagedPoolUsage: 53 Kb, QuotaPagedPoolUsage: 52 Kb
COM+[11:31:52]: PeakPagefileUsage: 18664 Kb, PagefileUsage: 17796 Kb
COM+[11:31:52]: MTSS: Answer File =
COM+[11:31:52]: Calling SetupOpenInfFile.
COM+[11:31:52]: Unable to open Answer File!!
COM+[11:31:52]: DRID-39104 -> Path: H:\WINDOWS\Java\Trustlib\
COM+[11:31:52]: Installed COM product version = 0.0.0.0
COM+[11:31:52]: SETUP VERSION = 3.0.0.4414
COM+[11:31:52]: Installation Mode = FRESH
COM+[11:31:52]: Setup Mode = CUSTOM
COM+[11:31:52]: DRID-39103 -> Path: H:\Program Files\Common Files\ODBC\Data Sources\
COM+[11:31:52]: End OC_INIT_COMPONENT Return Value = 0
COM+[11:31:53]: Start OC_QUERY_STATEComponent = com Subcomponent = com
COM+[11:31:53]: Subcomponent com state: O-,C-,R-
COM+[11:31:53]: End OC_QUERY_STATE Return Value = 0
COM+[11:39:18]: Start OC_QUERY_STATEComponent = com Subcomponent = com
COM+[11:39:18]: End OC_QUERY_STATE Return Value = 1
COM+[11:39:18]: Start OC_CALC_DISK_SPACE Component = com Subcomponent = com
COM+[11:39:18]: End OC_CALC_DISK_SPACE Return Value = 0
COM+[1:0:25]: Start OC_QUEUE_FILE_OPS Component = com Subcomponent =
COM+[1:0:25]: End OC_QUEUE_FILE_OPS Return Value = 0
COM+[1:0:25]: Start OC_QUEUE_FILE_OPS Component = com Subcomponent = com
COM+[1:0:25]: Subcomponent com state: O-,C+,R-
COM+[1:0:25]: Reading persistent registry values
COM+[1:0:25]: Finished reading persistent registry values, retval = 0x0
COM+[1:0:25]: Queuing file ops for component com, Section Name: com_install
COM+[1:0:25]: The following files will be copied:
COM+[1:0:25]: H:\WINDOWS\System32\clbcatq.dll
COM+[1:0:25]: H:\WINDOWS\System32\comsnap.dll
COM+[1:0:25]: H:\WINDOWS\System32\comuid.dll
COM+[1:0:25]: H:\WINDOWS\System32\comsvcs.dll
COM+[1:0:25]: H:\WINDOWS\System32\catsrv.dll
COM+[1:0:25]: H:\WINDOWS\System32\catsrvut.dll

COM+[1:0:25]: The following files will be deleted:
COM+[1:0:25]: Nuke registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\Setup.
COM+[1:0:25]: DRID-39105 -> Path: H:\Documents and Settings\All Users\Start Menu\Programs\
COM+[1:0:25]: End OC_QUEUE_FILE_OPS Return Value = 0
COM+[1:0:26]: Start OC_QUERY_STEP_COUNT Component = com Subcomponent =
COM+[1:0:26]: End OC_QUERY_STEP_COUNT Return Value = 0
COM+[1:0:26]: Start OC_QUERY_STEP_COUNT Component = com Subcomponent = com
COM+[1:0:26]: End OC_QUERY_STEP_COUNT Return Value = 120
COM+[1:0:26]: Start OC_ABOUT_TO_COMMIT_QUEUE Component = com Subcomponent =
COM+[1:0:26]: No PendingFileRenameOperations
COM+[1:0:26]: End OC_ABOUT_TO_COMMIT_QUEUE Return Value = 0
COM+[1:0:27]: Start OC_ABOUT_TO_COMMIT_QUEUE Component = com Subcomponent = com
COM+[1:0:27]: Subcomponent com state: O-,C+,R-
COM+[1:0:27]: Stopping service ComSysApp...
COM+[1:0:27]: Stopping service ComLB...
COM+[1:0:27]: Stopping service SENS...
COM+[1:0:27]: Stopping service EventSystem...
COM+[1:0:27]: Stopping service SENS...
COM+[1:0:27]: Stopping service fax...
COM+[1:0:27]: Stopping service w3svc...
COM+[1:0:27]: Stopping service smtpsvc...
COM+[1:0:27]: Stopping service iisadmin...
COM+[1:0:27]: End OC_ABOUT_TO_COMMIT_QUEUE Return Value = 0
COM+[1:1:4]: Start OC_COMPLETE_INSTALLATION Component = com Subcomponent =
COM+[1:1:4]: No PendingFileRenameOperations
COM+[1:1:4]: End OC_COMPLETE_INSTALLATION Return Value = 0
COM+[1:1:16]: Start OC_COMPLETE_INSTALLATION Component = com Subcomponent = com


<DRIVE LETTER>\Windows\setupapi.log - Receives an entry each time a line from an .inf file is implemented. If an error occurs, this log describes the failure. A subsection of mine is below. (The full size was 245KB)

[SetupAPI Log]
OS Version = 5.1.2600
Platform ID = 2 (NT)
Service Pack = 0.0
Suite = 0x0000
Product Type = 1
Architecture = x86
[2002/01/07 23:31:25 284.10]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "1394" {6BDD1FC1-810F-11D0-BEC7-08002BE2092F}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.12]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "1394Debug" {66f250d6-7801-4a64-b139-eea80a450b24}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.13]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "61883" {7EBEFBC0-3200-11d2-B4C2-00A0C9697D07}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.14]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Avc" {C06FF265-AE09-48f0-812C-16753D7CBA83}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.15]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Battery" {72631e54-78a4-11d0-bcf7-00aa00b7b32a}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.17]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "CDROM" {4D36E965-E325-11CE-BFC1-08002BE10318}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.19]
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Processor" {50127DC3-0F36-415e-A6CC-4CB3BE910B65}.
#I141 Class install completed with no errors.
[2002/01/07 23:31:26 284.20]

#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I022 Found "PCI\VEN_1274&DEV_5880" in H:\WINDOWS\inf\wdma_ens.inf; Device: "Creative AudioPCI (ES1371,ES1373) (WDM)";
Driver: "Creative AudioPCI (ES1371,ES1373) (WDM)"; Provider: "Microsoft"; Mfg: "Creative Technology Ltd."; Section name: "ES1371".
#I023 Actual install section: [ES1371.NTx86]. Rank: 0x00002001. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ES1371] in "h:\windows\inf\wdma_ens.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1274&DEV_5880&SUBSYS_A0001458&REV_02\4&21E63D15&0&28F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ES1371.NTx86.Interfaces] from "h:\windows\inf\wdma_ens.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1274&DEV_5880&SUBSYS_A0001458&REV_02\4&21E63D15&0&28F0".
#I121 Device install of "PCI\VEN_1274&DEV_5880&SUBSYS_A0001458&REV_02\4&21E63D15&0&28F0" finished successfully.
[2002/01/07 23:33:19 284.1045 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_10b7&dev_9050&subsys_00000000&rev_00,pci\ven_10b7&dev_9050&subsys_00000000,
pci\ven_10b7&dev_9050&rev_00,pci\ven_10b7&dev_9050,pci\ven_10b7&dev_9050&cc_020000,pci\ven_10b7&dev_9050&cc_0200
#-018 Searching for compatible ID(s): pci\ven_10b7&cc_020000,pci\ven_10b7&cc_0200,pci\ven_10b7,pci\cc_020000,pci\cc_0200
#-199 Executing "H:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I022 Found "PCI\VEN_10b7&DEV_9050" in H:\WINDOWS\inf\netel90a.inf; Device: "3Com 3C905TX-based Ethernet Adapter (Generic)";
Driver: "3Com 3C905TX-based Ethernet Adapter (Generic)"; Provider: "Microsoft"; Mfg: "3Com"; Section name: "EL90X.905TX.NDI".
#I023 Actual install section: [EL90X.905TX.NDI]. Rank: 0x00000003. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [EL90X.905TX.NDI] in "h:\windows\inf\netel90a.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_10B7&DEV_9050&SUBSYS_00000000&REV_00\4&21E63D15&0&20F0".

<DRIVE LETTER>\Windows\debug\NetSetup.log Logs activity when computers join domains or workgroups. (This entire log was only 7KB, so I copied all of it)

01/07 23:40:03 -----------------------------------------------------------------
01/07 23:40:03 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name 'WORKGROUP' is valid for type 2
01/07 23:40:03 -----------------------------------------------------------------
01/07 23:40:03 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name 'WORKGROUP' is valid for type 2
01/07 23:40:03 -----------------------------------------------------------------
01/07 23:40:03 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name 'WORKGROUP' is valid for type 2
01/07 23:40:03 -----------------------------------------------------------------
01/07 23:40:03 NetpDoDomainJoin
01/07 23:40:03 NetpMachineValidToJoin: 'P42GH'
01/07 23:40:03 NetpGetLsaPrimaryDomain: status: 0x0
01/07 23:40:03 NetpMachineValidToJoin: status: 0x0
01/07 23:40:03 NetpJoinWorkgroup: joining computer 'P42GH' to workgroup 'WORKGROUP'
01/07 23:40:03 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
01/07 23:40:03 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
01/07 23:40:03 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x858
01/07 23:40:03 NetpValidateName: name 'WORKGROUP' is valid for type 2
01/07 23:40:03 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
01/07 23:40:03 NetpControlServices: open service 'NETLOGON' failed: 0x424
01/07 23:40:03 NetpJoinWorkgroup: status: 0x0
01/07 23:40:03 NetpDoDomainJoin: status: 0x0
01/07 23:40:46 -----------------------------------------------------------------
01/07 23:40:46 NetpValidateName: checking to see if 'P42GH' is valid as type 1 name
01/07 23:40:46 NetpCheckNetBiosNameNotInUse for 'P42GH' [MACHINE] returned 0x0
01/07 23:40:46 NetpValidateName: name 'P42GH' is valid for type 1
01/08 01:00:12 -----------------------------------------------------------------
01/08 01:00:12 NetpValidateName: checking to see if 'DRINKOFTEN' is valid as type 2 name
01/08 01:00:15 NetpCheckNetBiosNameNotInUse for 'DRINKOFTEN' [ Workgroup as MACHINE] returned 0x0
01/08 01:00:15 NetpValidateName: name 'DRINKOFTEN' is valid for type 2
01/08 01:00:15 -----------------------------------------------------------------
01/08 01:00:15 NetpValidateName: checking to see if 'DRINKOFTEN' is valid as type 2 name
01/08 01:00:18 NetpCheckNetBiosNameNotInUse for 'DRINKOFTEN' [ Workgroup as MACHINE] returned 0x0
01/08 01:00:18 NetpValidateName: name 'DRINKOFTEN' is valid for type 2
01/08 01:00:18 -----------------------------------------------------------------
01/08 01:00:18 NetpValidateName: checking to see if 'DRINKOFTEN' is valid as type 2 name
01/08 01:00:21 NetpCheckNetBiosNameNotInUse for 'DRINKOFTEN' [ Workgroup as MACHINE] returned 0x0
01/08 01:00:21 NetpValidateName: name 'DRINKOFTEN' is valid for type 2
01/08 01:00:21 -----------------------------------------------------------------
01/08 01:00:21 NetpDoDomainJoin
01/08 01:00:21 NetpMachineValidToJoin: 'P42GH'
01/08 01:00:21 NetpGetLsaPrimaryDomain: status: 0x0
01/08 01:00:21 NetpMachineValidToJoin: status: 0x0
01/08 01:00:21 NetpJoinWorkgroup: joining computer 'P42GH' to workgroup 'DRINKOFTEN'
01/08 01:00:21 NetpValidateName: checking to see if 'DRINKOFTEN' is valid as type 2 name
01/08 01:00:24 NetpCheckNetBiosNameNotInUse for 'DRINKOFTEN' [ Workgroup as MACHINE] returned 0x0
01/08 01:00:24 NetpValidateName: name 'DRINKOFTEN' is valid for type 2
01/08 01:00:24 NetpSetLsaPrimaryDomain: for 'DRINKOFTEN' status: 0x0
01/08 01:00:24 NetpJoinWorkgroup: status: 0x0
01/08 01:00:24 NetpDoDomainJoin: status: 0x0
01/26 09:14:56 -----------------------------------------------------------------
01/26 09:14:56 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
01/26 09:14:59 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x0
01/26 09:14:59 NetpValidateName: name 'WORKGROUP' is valid for type 2
01/26 09:14:59 -----------------------------------------------------------------
01/26 09:14:59 NetpDoDomainJoin
01/26 09:14:59 NetpMachineValidToJoin: 'P42GH'
01/26 09:14:59 NetpGetLsaPrimaryDomain: status: 0x0
01/26 09:14:59 NetpMachineValidToJoin: status: 0x0
01/26 09:14:59 NetpJoinWorkgroup: joining computer 'P42GH' to workgroup 'WORKGROUP'
01/26 09:14:59 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
01/26 09:15:02 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x0
01/26 09:15:02 NetpValidateName: name 'WORKGROUP' is valid for type 2
01/26 09:15:02 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
01/26 09:15:02 NetpJoinWorkgroup: status: 0x0
01/26 09:15:02 NetpDoDomainJoin: status: 0x0
01/26 09:15:28 -----------------------------------------------------------------
01/26 09:15:28 NetpValidateName: checking to see if 'DRINKOFTEN' is valid as type 2 name
01/26 09:15:31 NetpCheckNetBiosNameNotInUse for 'DRINKOFTEN' [ Workgroup as MACHINE] returned 0x0
01/26 09:15:31 NetpValidateName: name 'DRINKOFTEN' is valid for type 2
01/26 09:15:31 -----------------------------------------------------------------
01/26 09:15:31 NetpDoDomainJoin
01/26 09:15:31 NetpMachineValidToJoin: 'P42GH'
01/26 09:15:31 NetpGetLsaPrimaryDomain: status: 0x0
01/26 09:15:31 NetpMachineValidToJoin: status: 0x0
01/26 09:15:31 NetpJoinWorkgroup: joining computer 'P42GH' to workgroup 'DRINKOFTEN'
01/26 09:15:31 NetpValidateName: checking to see if 'DRINKOFTEN' is valid as type 2 name
01/26 09:15:34 NetpCheckNetBiosNameNotInUse for 'DRINKOFTEN' [ Workgroup as MACHINE] returned 0x0
01/26 09:15:34 NetpValidateName: name 'DRINKOFTEN' is valid for type 2
01/26 09:15:35 NetpSetLsaPrimaryDomain: for 'DRINKOFTEN' status: 0x0
01/26 09:15:35 NetpJoinWorkgroup: status: 0x0
01/26 09:15:35 NetpDoDomainJoin: status: 0x0
01/26 09:16:30 -----------------------------------------------------------------
01/26 09:16:30 NetpValidateName: checking to see if 'P42GHZ' is valid as type 1 name
01/26 09:16:33 NetpCheckNetBiosNameNotInUse for 'P42GHZ' [MACHINE] returned 0x0
01/26 09:16:33 NetpValidateName: name 'P42GHZ' is valid for type 1
01/26 09:16:33 -----------------------------------------------------------------
01/26 09:16:33 NetpValidateName: checking to see if 'P42GHZ.' is valid as type 5 name
01/26 09:16:33 NetpValidateName: name 'P42GHZ.' is valid for type 5


<DRIVE LETTER>\Windows\repair\setup.log Provides information that is used by the Recovery Console. A subsection of mine is below. (The full size was 204KB)

[Paths]
TargetDirectory = "\WINDOWS"
TargetDevice = "\Device\Harddisk0\Partition3"
SystemPartitionDirectory = "\"
SystemPartition = "\Device\Harddisk0\Partition1"
[Signature]
Version = "WinNt5.1"
[Files.SystemPartition]
NTDETECT.COM = "NTDETECT.COM","b28f"
ntldr = "ntldr","3a7b2"
[Files.WinNt]
\WINDOWS\system32\drivers\kbdclass.sys = "kbdclass.sys","e756"
\WINDOWS\system32\drivers\mouclass.sys = "mouclass.sys","8cd9"
\WINDOWS\system32\drivers\usbuhci.sys = "usbuhci.sys","11ded"
\WINDOWS\system32\drivers\usbport.sys = "usbport.sys","22ffd"
\WINDOWS\system32\drivers\usbd.sys = "usbd.sys","40af"
\WINDOWS\system32\drivers\hidparse.sys = "hidparse.sys","acd7"
\WINDOWS\system32\drivers\hidclass.sys = "hidclass.sys","88de"
\WINDOWS\system32\drivers\usbhub.sys = "usbhub.sys","ee45"
\WINDOWS\system32\drivers\intelide.sys = "intelide.sys","dec0"
\WINDOWS\system32\drivers\pci.sys = "pci.sys","1a257"
\WINDOWS\system32\drivers\oprghdlr.sys = "oprghdlr.sys","b001"


(The whole remainder of the file looked as it does above, detailing drivers and path information for the whole system).

Well, that's a wrap for this week.

In next week's installment I will begin focusing the weekly articles on the next section of material which centers on Implementing and Conducting Administration of Resources of Windows XP Professional, the first of which will cover monitoring, managing, and troubleshooting access to files and folders.

Until then, best of luck in your studies and please feel free to contact me with any questions on my column, and remember,

"Weak passwords trump strong security."


Jason Zandri
Jason@Zandri.net

www.2000trainers.com