Phoenix Technologies Ltd. Custom.txt - WinPhlash 1.3 build 46 ----------------------------------- The "OEM Only" directory contains executable files that are required for WinPhlash. The following ten files are included in this directory: - Custom.txt This text file - Phlash.ini Configuration Settings file - Phlash9x.vxd Virtual Device Driver for Windows 98 and ME - PhlashLc.dll English Dynamic linked library for WinPhlash resources - language/*/PhlashLc.dll Languages other than english Dynamic linked library for WinPhlash resources - PhlashNT.sys Virtual Device Driver for Windows NT, 2000, and XP - WinPhlash.exe WinPhlash executable file - WinPhlash.hlp English Specific Standard WinPhlash Help - Help/ADV/*/WinPhlash.hlp Language Specific Standard WinPhlash Help - Help/STD/*/WinPhlash.hlp Language Specific Advanced WinPhlash Help - Wp.ico Bitmap file for WinPhlash Logo - PhComp.exe Program to compress the BIOS image. It is recommended that the OEM provide a PHLASH.INI file containing updated options as well as a BIOS image file for flashing. Three additional files are included in the "OEM Only" directory. These system files may also need to be loaded into the system directory: - MSVCRT.DLL - MSVCP60.DLL - MFC42.DLL IMPORTANT NOTES: A - The method of providing WinPhlash and any related files (BIOS image and flash settings) to their customers is the decision and responsibility of the OEM. A BIOS image file compressed with PhComp can be used with WinPhlash exactly the same way as a normal BIOS is. The change is transparent to the end-user. B - It is important to also make sure that the necessary system files (DLL's) be loaded into the appropriate directory. The name and path of this directory depends on both what operating system has been installed and where the user may have selected to install the operating system. Care should be taken not to use a hard coded directory path name for this installation. C - It is also important to make sure that newer versions of these files (DLL's) that have already been installed on the target system, are not lost by copying an older version over them. Version numbers and dates should be chacked and the user consulted before possibly losing newer versions. If they are to be copied over, the original versions should be saved in a known location, with the original name. The user should be advised of this information so that they can restore the originals if necessary. D - Various third-party utilities such as InstallShield, are available which greatly ease these tasks. It is the responsibility of the OEM to consider use of such a utility to develop a sophisticated installation package. E - A simpler alternative is to create a batch file to copy the appropriate files to known locations. Again, care must be taken to observe all of the above notes.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.