Microsoft Windows NT, Beta March 1993
Patch for LocalBus Systems Containing an UltraStor 34F Unable to Access the 
Floppy Drive


The Microsoft Windows NT product group has recently identified a floppy 
drive problem with the March Beta release of Windows NT.  If you have 
installed the March Beta release from CD-ROM or using WINNT.EXE and your 
system contains an UltraStor 34F (LocalBus) SCSI controller, you may 
encounter a problem accessing your floppy disk drive when attempting to 
make the Emergency Repair Disk as well as after the installation is 
complete. 

If the error occurs at the point in installation when Setup prompts you to 
create the Emergency Repair Disk, but cannot access the floppy drive to do 
so, elect to not create the disk by selecting OK without a floppy disk in 
the disk drive, then OK again to complete the installation.  Your floppy 
drive may remain inaccessible.  

If you encounter this problem, please take the following steps to remedy 
this behavior.  We appreciate your efforts in reporting problem areas and
encourage you to continue working with us to improve the product. 
We apologize for any inconvenience this may have caused.  

__________________________________________________________________________


To retrieve the corrected files from the WINNT CompuServe forum:

    Connect to the WINNT CompuServe forum, Library 2 where you will find 
    WNT008.ZIP.  This file was created using the PKZIP file compression 
    utility.  You will need the PKUNZIP utility to extract the files to
    a directory on your hard drive.  PKUNZIP can be found as PKZ110.EXE 
    in Library 2 of the IBMCOM forum.  Download PKZ110.EXE and execute 
    the file to extract the PKUNZIP.EXE utility.  Create a directory on
    your hard disk where the extracted files can be placed.  For example, 
    C:\WNT008.  To extract the WNT008.ZIP file, type: 
	PKUNZIP WNT008.ZIP C:\WNT008
    to decompress the files into the directory.  The following files can 
    now be seen:

	HAL.DLL
	HAL486C.DLL
	README.TXT
____________________________________________________________________________

Instructions to resolve the problem behavior:


1.      First, on another system upload the files on the patch diskette to
a network location the failing system can access (or boot an alternate 
operating system and simply replace the file as outlined below). 
  

2.	Logon to Windows NT.    

3.      Execute the MS-DOS Command Prompt from the Program Manager.  Locate
HAL.DLL on your hard drive in the Windows NT system path.  For example, 
CD \WIN31\SYSTEM32 or change directories to the appropriate system directory 
for your Windows NT installation where HAL.DLL is located.  

4.	Verify the size and date of the existing HAL.DLL on your hard drive.  
It will be either:

		HAL.DLL 	67584K	3-1-93
		HAL.DLL 	65536K	3-1-93

It is important to specifically note the size of HAL.DLL your system is 
using.

5.	Rename this file by typing, RENAME HAL.DLL HAL.OLD at the command 
line. 

6.      Connect to the network location where the patch files can be found 
or insert the patch disk in the floppy drive of your computer.  Note the 
two binaries present: 

		HAL.DLL		67584K	3-30-93
		HAL486C.DLL 	65536K	3-30-93

Match the size of the new file with the size of HAL.DLL you noted in Step 4.  
Copy the appropriate file to replace the failing one.  For example, at the 
network share (or from the patch disk if you have booted a previous 
operating system) type, COPY HAL486C.DLL C:\WIN31\SYSTEM32\HAL.DLL.  
Note: if your system uses the file size associated with HAL486C.DLL, it 
must be copied to the Windows NT system path as HAL.DLL.  

7.      Exit Program Manager and shutdown from Windows NT by pressing 
CTRL-ALT-DEL, and select Shutdown, then OK.  You may now log back on and 
proceed as normal.