With WPWin6.0a we created two methods of installation. The first is the standard 'complete' installation. It means that the entire product is sent with a full complement of diskettes. This simply replaces in its entirety the package as it was being shipped prior to 6.0a. The second type of installation is the 'update' package. It consists of only those files that have changed between the original release of WPWin6.0 and WPWin6.0a. By packaging it this way we reduce the number of diskettes that must be shipped. There has been some confusion about whether or not the update will work for network installations. It will work just fine. The network installation update proceeds just as expected and updates the files on the network. The only thing to be aware of is that WPWin should be run from the WPCNET Settings icon that is set during network installation. This icon runs WP with the following startup switches: /sa /pn=wpcnet /ni=wp /pi=. Note that it assumes wp is not a legal subdirectory of the current DOS directory. The purpose of running WPCNET Settings prior to workstation install is to ensure the creation of all necessary shared settings in the network binary ini file. In addition to running WPCNET Settings (WPWin stand alone on the network) prior to workstation installation, it may also be a good idea to set any 'override' flags on shared settings. This is done by running BifEd in a way that allows editing of the wpcnet.bif file. To do this requires that WPWin not be running and then start BifEdit20 from the icon labelled 'WPCNET Flagging'. This is really just 'bifed20.exe /pn=wpcnet /pi= /ni=wp'. The workstation install can also be done from the update disks. It should be remembered that this will not update any of the icons on the desktop. In fact, the update will not change the icons on the desktop for the standalone install either. Also remember that a network license limits the user to a specific number of workstations. Receiving the update disks does not change that limitation at all. Only workstations that are properly covered by the network license agreement are allowed to be updated. Furthermore, regardless of license limitations, doing a workstation install from the update disks on a workstation that did not previously have a workstation install done on it will result in appropriate modification of settings files, but no icons to run the product from the Program Manager on the desktop.