Just in case someone runs into the 'hang' issue, here is the work around for it:
Computer Stops Responding (Hangs) During Setup, Installing Updates, or Adding New Hardware
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Windows Millennium Edition
Microsoft Internet Explorer version 5.5 Service Pack 1 for Windows Millennium Edition
Microsoft Office 2000 Standard
Microsoft Office 2000 Professional
Microsoft Office 2000 Premium
Microsoft Internet Explorer version 6 for Windows Millennium Edition
--------------------------------------------------------------------------------
SYMPTOMS
When you try to upgrade your computer to Windows Millennium Edition (Me), your computer may stop responding (hang) during Setup or you may see the following behavior after you upgrade your Windows Me computer:
When you attempt to install Internet Explorer 5.5 Service Pack 1 (SP1) or Internet Explorer 6, Setup may stop responding (hang) when it reaches 70 percent completion, or you may receive the following error message:
Error 52: Setup could not finish opening a file on your destination disc.
The Add New Hardware wizard may stop responding, or upon starting, your computer may stop responding when Plug and Play detects that a new device is installed or attached to your computer.
When you install critical updates from the Windows Update Web site, your computer may stop responding.
When you install the Virtual Machine update, your computer may stop responding.
When you install DirectX 8.0, your computer may stop responding.
CAUSE
The OEMx.INF files can be created by Windows Update, Internet Explorer Setup and any other program that uses the Microsoft Setup API's, if a disk utility program currently has a volume lock on the drive. Microsoft and third party utililty programs such as ScanDisk, defragment programs, and other system utilities are required to get a volume lock on the drive in order to control access by other processes to the volume.
RESOLUTION
To resolve this issue, apply the fix referenced in the following Microsoft Knowledge Base article:
Q301540 CreateFile Improperly Returns ERROR_ALREADY_EXISTS if the Drive Is Locked and the File Did Not Exist
To work around this issue, delete all Oem*.inf files in the Windows\Inf folder that are 0 KB in size.
To delete all of the 0 KB files, follow these steps:
Set Windows to show all files. To do so, open Windows Explorer, on the Tools menu, click Folder Options, click the View tab, and then select the Show hidden files and folders option.
Click Start, point to Search, and then click For Files or Folders.
In the Search for files or folders named box, type oem*.inf.
Verify that the Look in box shows C:\Windows\Inf.
Click Search Now.
In the Search Results window, sort the files by size by clicking on the header of the Size column. If you cannot see the Size column, maximize the Search Results window.
Select all of the 0 KB files:
Click the first 0 KB Oem.*inf file to highlight it.
Scroll down <font color=red>(use the down arrow key)</font color=red> the list to the last 0 KB Oem.*inf file, and while holding down the SHIFT key, click to highlight it.
Press the DELETE key. <font color=red>Be PATIENT!</font color=red>
Click Yes when you are prompted to confirm the deletion.
Close Windows Explorer.
Disable all disk utility programs while installing the Windows Me updates.
--------------------------------------------------------------------------------
Be SURE to be all inclusive with the files having 0KB! If not, then they will propogate themselves, leaving many,many more to try and clean out. Don't worry, the ONLY other file will be an OEMCMP.INF (or some such) with 3KB in its size column....and its usually right up at the top.
The addins with red type are my suggestions to you when you do this....some of the deletes can take several minutes to clean out several thousand files.
<P ID="edit"><FONT SIZE=-1>
Edited by scruffy on 08/29/01 06:43 PM (server time).</FONT></P>
