Power PlugIn v1.05 for WinAmp and ModPlug
=========================================
This program is a Visualization-Plugin for WinAmp or ModPlug (or any
other program supporting plugins of that type) with the ability of
supporting user-definable skins and animations.
It has been designed for Win95/98/NT or later.
You are not allowed to change this file nor any of the files
delivered with the Power PlugIn package.
For a description how to make your own skins, read the file "pwrp-sdk.txt"
in the directory "powerp".
If you want to offer your own skin(s) to the public, you MUST READ
THE SECTION "HOW TO DELIVER YOUR SKIN(S)" at the bottom of
this file.
This software is freeware. You may copy and redistribute this program as long
as all copyright notices remain intact and the files and product materials
delivered with this software package are not sold, disassembled,
reverse-engineered or modified in any way without the author's explicit
written permission.
To view the version of Power PlugIn, use the about button in the configuration,
or do the following without needing to start the music-player:
In the Explorer click with the right mouse button on the main Power
PlugIn's file "powerp.dll" and choose Properties in the popup menu.
A properties dialog will appear. Choose the Version tab and you will
see the number of your version of Power PlugIn.
If you are interrested in the Povray-3.0 scene files I used to generate
the images for the skin "HiFi-X", please send me an email.
Contents:
---------
Installation
Files contained in this Power PlugIn package:
Some Features
Configuration Options
SOME HINTS
MAKING YOUR OWN SKINS FOR POWER PLUGIN
DISCLAIMER
How To Contact The Author
Donations
Thanks to
Some Notes
Known Bugs
HOW TO DELIVER YOUR SKIN(S)
History
Installation
============
1/ If you install the package only for one Music-Player:
Just copy the files into your player's plugin directory
retaining the directory structure stored in the archive file.
If you do not want the Power PlugIn's skins to be stored in
the predefined path, simply move them to another location
(but *without* changing the structure of its sub-directories).
When starting your Music-Player you should then configure
Power PlugIn and select the skin-path according to the new location.
2/ If you install the package for more than just one Music-Player
(ie. for WinAmp and ModPlug):
I recommend to install Power PlugIn's skins into one specific
location of your desire (as described in section 1/ above).
But Power PlugIn's main file "powerp.dll" itself (and its readme
"readme_powerp.txt") you should copy into each music-player's
plugin directory seperately.
This will allow each music-player to store its own settings of
Power PlugIn without effecting the settings for the other
music-players.
When starting a music-player you should then first configure
Power PlugIn and select your specific skin-directory where you
have placed Power PlugIn's skins.
This will allow all copies of Power PlugIn to use the same
skin-directory. This will save disk space because only one copy
of each skin need to be stored.
Example:
Imagine WinAmp is installed on "C:\Program Files\WinAmp" with
its plugins stored in "C:\Program Files\WinAmp\Plugins".
Furthermore imagine ModPlug installed on "C:\Program Files\ModPlug"
and its plugins to be stored in "C:\Program Files\ModPlug\Plugins".
Now imagine you would want to store Power PlugIn's skins in WinAmp's
plugin directory.
For this, you would extract the Power PlugIn archive file into
"C:\Program Files\WinAmp\Plugins" so that the "powerp.dll" (and
"readme_powerp.txt") are extracted in there and the skins are
extracted into "C:\Program Files\WinAmp\Plugins\powerp\Skins".
The installation for WinAmp now is ready. You even do not need to
configure Power PlugIn and change the skin-directory setting
because the default directory "powerp\Skins" is used as skin location.
For ModPlug, you just need to copy the files "powerp.dll" and
"readme_powerp.txt" into its plugin directory
"C:\Program Files\ModPlug\Plugins".
Then start ModPlug and open the configuration of Power PlugIn.
Select "C:\Program Files\WinAmp\Plugins\powerp\Skins" as location
for Power PlugIn's skins.
I M P O R T A N T :
-----------------------
ModPlug is able to use any plugin directory of your desire.
So it would be possible to select WinAmp's plugin directory
"C:\Program Files\WinAmp\Plugins" for ModPlug, too.
For this, you would not need to copy "powerp.dll" and "readme_powerp.txt"
into a seperate plugin directory (like "C:\Program Files\ModPlug\Plugins")
for ModPlug.
But the DISADVANTAGE of this would be that the settings of Power PlugIn
(which are stored in the file "plugin.ini" placed in the same
location where "powerp.dll" is placed) would be the same for
both WinAmp and ModPlug.
So if you adjust the settings of Power PlugIn for WinAmp, it will
change them for ModPlug as well.
That is the reason, why I did implement the possibility of choosing
the skin directory for Power PlugIn, because with using a seperate
copy of "powerp.dll" for each music-player, the Power PlugIn-settings
for one player will not affect the settings for other players, but
all can use the same Power PlugIn-skin-directory.
Files contained in this Power PlugIn package:
=============================================
Following is a list of files (with path names) contained in the
original Power PlugIn package.
powerp.dll The main DLL file, it is the Power PlugIn
readme_powerp.txt this file
powerp\pwrp-sdk.txt file explaining how to make own skins
powerp\Skins\HiFi-X\readme.txt readme to HiFi-X skin
powerp\Skins\HiFi-X\skin.txt actual skin definition file for HiFi-X skin
powerp\Skins\HiFi-X\full_skin.txt skin definition file for the full HiFi-X skin package
powerp\Skins\HiFi-X\small_skin.txt skin definition file for the small HiFi-X skin package
Following is the list of image files belonging to skin "HiFi-X":
powerp\Skins\HiFi-X\116\boxes.pcx
powerp\Skins\HiFi-X\116\boxesm.bmp
powerp\Skins\HiFi-X\116\org.pcx
powerp\Skins\HiFi-X\116\org_m.bmp
powerp\Skins\HiFi-X\116\org_mask.bmp
powerp\Skins\HiFi-X\116\slidlamp.bmp
powerp\Skins\HiFi-X\116\spk_big.pcx
powerp\Skins\HiFi-X\116\spk_bigm.bmp
powerp\Skins\HiFi-X\116\spk_md.pcx
powerp\Skins\HiFi-X\116\spk_mdm.bmp
powerp\Skins\HiFi-X\116\spk_sub.pcx
powerp\Skins\HiFi-X\116\spk_subm.bmp
powerp\Skins\HiFi-X\116\spk_tw.pcx
powerp\Skins\HiFi-X\116\spk_twm.bmp
powerp\Skins\HiFi-X\116\spk_wf.pcx
powerp\Skins\HiFi-X\116\spk_wfm.bmp
powerp\Skins\HiFi-X\116\subwf.pcx
powerp\Skins\HiFi-X\116\subwfm.bmp
powerp\Skins\HiFi-X\116\vlamps_l.bmp
powerp\Skins\HiFi-X\116\vlamps_r.bmp
powerp\Skins\HiFi-X\126\boxes.pcx
powerp\Skins\HiFi-X\126\boxesm.bmp
powerp\Skins\HiFi-X\126\org.pcx
powerp\Skins\HiFi-X\126\org_m.bmp
powerp\Skins\HiFi-X\126\org_mask.bmp
powerp\Skins\HiFi-X\126\slidlamp.bmp
powerp\Skins\HiFi-X\126\spk_big.pcx
powerp\Skins\HiFi-X\126\spk_bigm.bmp
powerp\Skins\HiFi-X\126\spk_md.pcx
powerp\Skins\HiFi-X\126\spk_mdm.bmp
powerp\Skins\HiFi-X\126\spk_sub.pcx
powerp\Skins\HiFi-X\126\spk_subm.bmp
powerp\Skins\HiFi-X\126\spk_tw.pcx
powerp\Skins\HiFi-X\126\spk_twm.bmp
powerp\Skins\HiFi-X\126\spk_wf.pcx
powerp\Skins\HiFi-X\126\spk_wfm.bmp
powerp\Skins\HiFi-X\126\subwf.pcx
powerp\Skins\HiFi-X\126\subwfm.bmp
powerp\Skins\HiFi-X\126\vlamps_l.bmp
powerp\Skins\HiFi-X\126\vlamps_r.bmp
powerp\Skins\HiFi-X\232\boxes.pcx
powerp\Skins\HiFi-X\232\boxesm.bmp
powerp\Skins\HiFi-X\232\org.pcx
powerp\Skins\HiFi-X\232\org_m.bmp
powerp\Skins\HiFi-X\232\org_mask.bmp
powerp\Skins\HiFi-X\232\slidlamp.bmp
powerp\Skins\HiFi-X\232\spk_big.pcx
powerp\Skins\HiFi-X\232\spk_bigm.bmp
powerp\Skins\HiFi-X\232\spk_md.pcx
powerp\Skins\HiFi-X\232\spk_mdm.bmp
powerp\Skins\HiFi-X\232\spk_sub.pcx
powerp\Skins\HiFi-X\232\spk_subm.bmp
powerp\Skins\HiFi-X\232\spk_tw.pcx
powerp\Skins\HiFi-X\232\spk_twm.bmp
powerp\Skins\HiFi-X\232\spk_wf.pcx
powerp\Skins\HiFi-X\232\spk_wfm.bmp
powerp\Skins\HiFi-X\232\subwf.pcx
powerp\Skins\HiFi-X\232\subwfm.bmp
powerp\Skins\HiFi-X\232\vlamps_l.bmp
powerp\Skins\HiFi-X\232\vlamps_r.bmp
Note: The images in the paths "126" and "232" will be included only
in the full version of the Power PlugIn package which you can
download from my website.
Some Features:
==============
- A Visualization-Plugin supporting Add-On-Window- and In-Window Plugin-windows.
Add-On-Window Plugin-windows are aligned to one side of the music-player window.
In-Window Plugin-windows will be positioned somewhere inside the music-player window.
- Designed for Win95/98/NT.
- Supports user-defineable skins.
- Supports any number of plugin-windows at any size and position.
- Supports non-rectangular windows by defining mask images.
- Supports different sizes of the Music-Player.
This is necessary ie. for WinAmp which can have 4 different sizes: normal size,
double size, windowshade size and windowshade double size.
- Supports animations with images or drawings.
Drawings will be made of lines, circles, ellipses, rectangles filled or non-filled,
etc.
- Supports blur and alpha-blending for animations with drawings.
- When Power PlugIn is started and loads a skin-design, it will analyse
and optimize the skin's images for speed where possible.
This can take a while (some seconds for loading and optimization).
- If a plugin-window is not visible (ie. when it is completely overlapped
by other windows), the animations for this window will not be calculated
any more as long as it stays completely invisible.
This will reduce CPU-usage ie. if you are working on a full-screen window
in foreground while playing music in the background.
- Power PlugIn will look good only if you use non-palettized screen resolutions.
So your screen-color depth should be 15 bits (32768 colors) or higher.
Sorry, but with 256 colors, Power PlugIn will look like crap.
- Dragging of the plugin's windows to move them to your desired positions.
Configuration Options
=====================
- Skin:
> Skin-Path: If your Power PlugIn's Skins are on a different location than
the default location ("powerp\Skins"), enter the correct
location in here.
Please notice, if the path is a relative path (which means it
does not start with a drive letter), then the path will
be relative to the location where Power PlugIn ("powerp.dll")
itself is located for that music-player.
In that case, the full path (which is an absolute path because
it starts with a drive letter) will be displayed below
the skin-path field.
If you did select a correct Skin-Path, the the fields "Skin" *and* "Design"
below will display the currently selected Skin and one of its Designs
currently chosen.
> Skin: If you the "Skin-Path" field contains a valid Power PlugIn's Skin path,
then in here the currently selected skin will be displayed.
In here, you can select the skin to use.
When you select a different skin, the field "Design" below will contain
the list of possible designs for that skin.
If the "Design" field is empty, then the currently selected skin does
not seem to be a valid skin. Choose anotherone instead.
> Design: If the "Skin-Path" field contains a valid Power PlugIn's Skin path
and the "Skin" field contains a valid skin,
then in the "Design" field the currently selected Design will
be displayed.
A Skin will contain one or more Designs. Each Design will act or
look differently although they all belong to the same skin.
Multiple Designs for the same Skin make sense to be used different
music-player types.
Ie. there can be a design for WinAmp and anotherone for ModPlug.
The main difference mostly will be the size of the images since
WinAmp has a smaller window than ModPlug.
Note: When selecting a different skin-path, skin or design, the plugin-windows will
be moved back to their default positions the next time Power PlugIn is
started (of course only if the plugin-windows have been moved away from
their default positions by dragging them with the mouse).
- Sensitivity:
In here you can adjust the sensitivity of Power PlugIn according to
bass and treble values.
Ie. imagine you did select a Skin where 3 speakers are displayed: a bass,
a band and a treble speaker. If you change the bass sensitivity, the
bass will react more or less sensitive while the treble will not. The band
speaker will be affected by both, the bass- and treble-sensitivity.
For each sensitivity, you have a large and a small slider.
The large one will change the sensitivity in steps of 25 units.
The small one is intended for fine tuning.
When changing sensitivity, the new sensitivity value will be displayed in
the field below the sliders.
The higher the sensitivity, the easier Power PlugIn will react on sounds.
For songs with low sound volume, you will want to increase sensitivity.
Or for songs with loud bass you will want to decrease bass sensitivity.
The reset button will set both sensitivities back to zero (the default).
- Options:
> Reverse Stereo Audio Channels:
If this is checked, Power PlugIn will swap the left and right audio
channels (but only for displaying, of course).
But the sound you are hearing will not be affected (of course,
because Power PlugIn cannot influence the music-player).
I recommend *not* to check this option, since this is the normal
situation. But if you have swapped you sound-speakers (I mean your
real ones connected to your soundcard), you can check this option.
Note:
Of course, this will affect only Power PlugIn. If your music-player
displays left and right sound information seperately as well (like
ModPlug's spectrum-analyzer), then this one will not swap its
sound channels.
> Automatically close start message dialog (if present):
If you have installed e.g. the small version of Power PlugIn, a startup
message will appear. (Such a startup message also can appear depending on
the skin definition for Power PlugIn used).
With this option, the dialog will automatically disappear. You will not
have to explicitely push the close button.
> Allow dragging of plugin-windows:
If enabled, the plugin-windows can be dragged using the mouse.
By right-clicking a plugin-window, the current offset position of the
plugin-window will be displayed. By double right-clicking, the
plugin-window will be moved back to its default position.
I recommend to enable this option, then drag the plugin-windows (if
necessary) to your desired positions. Then disable this option again
so the plugin-windows cannot be moved any more away from your desired
positions.
Please notice: By selecting a different skin or design, or by en/disabling
the "Move plugin-windows with the player's main window" option, all the
plugin-windows will be set back to their default positions.
> Move plugin-windows with the player's main window:
If enabled, the plugin-windows will be moved together with the player's
main window.
If disabled, the plugin-windows will be created on some default positions
on the screen (which will not fit your wishes). You can drag them away
(the "Allow dragging of plugin-windows" option must be enabled for this)
to your desired positions on the screen.
> Scheme to use:
Normally this should be "*choose automatically*" which will cause Power PlugIn
to check which scheme should be used (depending on the size of the player's
main window). At the moment, "Normal Size", "Double Size", "WindowShade Size"
and "WindowShade Double Size" are available.
If you explicitely use one of the specified schemes, then this scheme will
be used regardless of the size of the player's main window.
I recommend to select one specific scheme if the "Move plugin-windows with
the player's main window" option is disabled.
> Display tray icon:
When this is enabled, an icon will be displayed in the system tray when
Power PlugIn is running.
By clicking on the tray-icon, a properties dialog will be opened which allows
to manipulate some of the properties of each plugin-window (like their
visibility state).
> Test Power PlugIn optimization:
If checked, the images which Power PlugIn did optimize successfully will
have red or green borders. This will look as if Power PlugIn had a bug,
but it is intended only for a skin designer to see if he/she did design
the skin most effectively.
Red borders mean that the image has been optimized during pass 1.
Green borders (or if an image has red and green borders) mean that
the image has been optimized also during pass 2.
- About:
The about button will display version and copyright information concerning
Power PlugIn.
SOME HINTS
==========
When you are using ModPlug, Power PlugIn will react on the currently selected
spectrum. So it is important if you have the fast-specturm option enabled.
Also Power PlugIn will react on the left and right sound channel differently
only if you have enabled the stereo-spectrum option.
This is necessary even if ModPlug's spectrum is not displayed.
If you see some images of animations of Power PlugIn having red or green
borders, check if the test-optimization-option is enabled in the
Power PlugIn configuration.
MAKING YOUR OWN SKINS FOR POWER PLUGIN
======================================
Read the file "pwrp-sdk.txt" in the directory "powerp".
It should have been included in the Power PlugIn package.
DISCLAIMER
==========
THE AUTHOR OF THIS SOFTWARE DISCLAIMS ALL WARRANTIES,
EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE PRODUCT.
AS WELL THE AUTHOR ACCEPTS NO RESPONSIBILITY FOR DAMAGES
THAT ARE CAUSED BY THIS PROGRAM AND YOU, ITS USER, ASSUME
THE ENTIRE RISK WHEN YOU USE IT.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU, ITS USER,
ASSUME THE RISK OF PAYING THE ENTIRE COST OF ALL
NECESSARY SERVICING, REPAIR, OR CORRECTION AND ANY
INCIDENTAL OR CONSEQUENTIAL DAMAGES. IN NO EVENT THE
AUTHOR WILL BE LIABLE FOR ANY DAMAGES WHATSOEVER
(INCLUDING WITHOUT LIMITATION DAMAGES FOR LOSS OF
BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION AND THE LIKE) ARISING OUT OF THE USE OR THE
INABILITY TO USE THIS PRODUCT EVEN IF THE AUTHOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Use of this product for any period of time constitutes
your acceptance of this agreement and subjects you to its
contents.
How To Contact The Author
=========================
Bug reports, improvements, ideas, suggestions, wishes or questions
please send to
Roman Komary
email: romank@xoommail.com
WebSite: http://members.xoom.com/romank/index.html
Copyright (c) 1998 Roman Komary
Donations
=========
Although Power Plugin is freeware I would be very greatful
for any kind of donations, because this would encourage me to
develop new versions of Power PlugIn based upon your ideas.
Thanks to
=========
the programmers of WinAmp and ModPlug for writing such
wonderful tools for the ultimate sound experience.
Some Notes
==========
If you write your own skins, it would be nice of you to tell me
about it and/or where I can download it (if possible) because
I am interrested in how far Power PlugIn will spread.
But please, do *NOT* send me your skin-package since my
internet-account does not allow me to receive too large emails.
The more poeple make skins for Power PlugIn, the more I will be
encouraged to do new versions of Power PlugIn.
If you write your own skins, you will find a description in
"pwrp-sdk.txt" how to do so. It should have been included with the
Power PlugIn package.
If you want to offer your own skin(s) to the public, you must read
the section "HOW TO DELIVER YOUR SKIN(S)" at the bottom of
this file.
Sorry for long loading times of a Power PlugIn skin, but the analysation
and optimization process can take a while.
Known Bugs
==========
Sorry you WinAmp users, but when Power PlugIn is running, moving or
sizing WinAmp will result in very slow movement execution.
This seem to happen only with WinAmp because with ModPlug
there are not happening such problems.
With 256 color screen resolution Power PlugIn will look like crap.
Sorry about this. Maybe I will solve it in future.
If you see some images of animations of Power PlugIn having red or green
borders, check if the test-optimization-option is enabled in the
Power PlugIn configuration.
HOW TO DELIVER YOUR SKIN(S):
============================
If you want ot offer your own skin(s) to the public, you must accept
and follow all of the following terms:
- You must include a "readme.txt" file for each skin which must be in
the same location as your "skin.txt" file.
You must include a readme.txt file for each skin seperately you are
making, even if you include more than one skin in the archive file.
In that readme you can write your text whatever you want, but with
the following restrictions:
> The readme must contain a note where Power PlugIn can be
retrieved (web-address).
> and it must contain my name (the author of Power PlugIn) and
the email address and a copyright notice saying I (the author
of Power PlugIn) have copyright on Power PlugIn.
> you must not claim that Power PlugIn is your creation.
But you may include a copyright on your own skin(s).
Example:
About Power PlugIn:
-------------------
Power PlugIn is written and copyright by
Roman Komary
romank@xoommail.com
You can find it at
http://members.xoom.com/romank/index.html
See "readme_powerp.txt" which should have been delivered with
the Power PlugIn package.
The easiest way will be to take the example above and copy it
into your skin's readme(s).
Of course you may include also other readme files in other locations
if you want to, but you must not claim that Power PlugIn is
your product and you must not set your copyright on Power PlugIn.
- If you want to include the "powerp.dll" (the main file of Power PlugIn)
in your skin(s) package, you must do this the following way:
> You must create an archive file named "powerp" (the filename extension
depends of the archive format you are using, mostly this will
be ".zip").
This archive must contain the "powerp.dll" and the "readme_powerp.txt"
file (you must not change these names).
You may also include the "pwrp-sdk.txt" file in the "powerp" archive
file (but it is not required). If you do this, store it in the a
directory named "powerp" in the archive whereas the "powerp.dll" and
"readme_powerp.txt" must not be placed in a directory (these 2 files
should be placed on root of the archive file's directory structure).
The "powerp.dll", the "readme_powerp.txt" and the "pwrp-sdk.txt" file
must be from the same Power PlugIn version package. You must not mix
them from different versions of Power PlugIn packages.
You may then include the "powerp.???" archive file (the ".???" stands
for the archive type extension you are using) in your own skin-archive
file.
It is *not* required to include Power PlugIn (the "powerp.???"
archive file) in your skin-package.
I even recommend not to include it since your archive file will be
smaller and the user, who installs your skin(s), can read in the
readme.txt file included in your skin(s) where to retrieve the
newest Power PlugIn package.
- You are not allowed to include even one of my (the auther of Power PlugIn)
skins in your skin package. You also must not claim that one of my
(the auther of Power PlugIn) skins is copyright on you.
- If you sell your skin(s), no matter which form of payment this may
include, you must not sell the Power PlugIn package, if you include it
in your skin(s)'s package(s).
Even any file contained in any version of a Power PlugIn package may
not be sold no matter if you bundle it together with other files or not.
But you may sell your skin(s) and all the necessary files for your
skin(s).
As well you may be payed for the delivering and the transportation
medium of a package.
Following are some notes which I recommend to do, but they
are not required:
- The directory structure in the archive should have a root directory
which shall be the root directory of the skin (containing the "skin.txt"
file, the "readme.txt" file and your image files and additional
files that you did include). This directory should have the skin's name.
If you include more than one skin in the archive, the archive should
contain a seperate directory for each skin and each directory should
have the corresponding skin's name.
If you will not do this, it will be difficult for the user to
install your skin(s), since he will not know the skin's names, and
in addition, he will not know where to create which directory and
where to copy/extract which file to.
History:
========
v1.05
- Improved handling for dragging a plugin's window:
The mouse cursor changes if dragging is enabled in the settings.
One single right-click and holding the button will display a dialog
telling the position of the plugin's window relative to its default position.
- Added docking support of plugin-windows when being moved.
Holding the Ctrl key while dragging will disable the docking support as
long as the key is being pressed.
- Added the possibility to switch each plugin-window on or off seperately and
independently. The visibility state of a plugin-window will be stored
seperately for each size of the player window (e.g. normal size, double size,
windowshade size and windowshade double size).
The visiblity can be changed in the properties.
To open the properties dialog, you must have enabled the tray-icon (which
you can do in the configuration of Power PlugIn).
By clicking once on the tray-icon, the properties dialog will be opened.
- Added the possibility of en/disabling the movement of plugin-windows
when the player's main window is being moved.
- Added the possiblity to select a specific scheme rather than letting
Power PlugIn choose the best matching scheme.
- Solved some bugs (like the error message "no skin selected" when trying
to configure Power PlugIn).
- A simple installation procedure: The zip file now contains a self-extracting
zip file. It will only ask for the music-player's plugins directory.
v1.04
- Added possibility to move a plugin's window by dragging it with the mouse.
Double right clicking on a plugin's window will move it to its default position.
The ability of moving the plugin's windows can be en/disabled in the settings.
v1.03
- resolved some minor bugs
- included support for displaying a startup message.
v1.02
- solved the slow movement of the WinAmp player when Power PlugIn
is running.
v1.01
- added "maximum" string option to option "Channel"
V1.0
my first version
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.