FILE NAME:          W V 2 - F I X .R E F

Original DATE:      June 6, 1995

REVISE   DATE:      August 2, 1999

FROM:               Artic Technologies Help Center

                    Artic Technologies
                    1000 John R. Road
                    Suite 108
                    Troy, MI  48083.

                    (248) 588-7370 Extension 11 Sales
                    (248) 588-2650 Fax
                    (248) 588-1425 Help Center

                    www.artictech.com InterNet WEB Site

                    sales@artictech.com InterNet E-Mail Sales

                    help@artictech.com  InterNet E-Mail Help


TO:                 All Artic Users

Subject:            WinVision 2/Solo, WV2.INI and *.WVB files Fix.
                    By Joseph S. Roeder.

                     * * * MEMORANDUM * * *

DATE: June 6, 1995

TO:   WinVision users
FROM: Joseph S. Roeder
SUBJ: WinVision WVB files


A problem has been uncovered concerning the saving of settings
files for WinVision.  This memo describes the problem and details
steps necessary to fix the problem.

As I understand it, when you save the settings in a local file,
WinVision requests the name of the program icon from MS/WINDOWS
and uses this name to create a settings file with a ".WVB"
extension.  Reference data to this file is also put in the
WV2.INI file.

Apparently, MS/WINDOWS sometimes returns a blank for the icon
name.  When this happens, WinVision fails to update WV2.INI
properly, resulting in a corrupted file.  Subsequent attempts to
save settings may then be unsuccessful.  That is right- if you
have run into this bug, you may now have corrupted some files.

The fix for this is in version 2.04 of Winvision which is now
being beta tested.  In the meantime, if you want to repair your
corrupted files, which are in the subdirectory holding your
MS/WINDOWS program files, you have two choices:

The easiest thing to do is to erase the files with the ".WVB"
extensions and the WINVIS.INI file and reinstall WinVision2 from
your distribution disk.  You will then have to re-do and re-save
all the global and local settings.

The other choice is a bit more complicated, but you can retrieve
your local settings files.  Here is what to do:

     1. From with in your WINDOWS directory, temporarily rename all the files 
with ".WVB" extensions to ".WVX" files,

     2. delete the WINVIS.INI file and re-install it from the
     distribution disk,

     3. go into WinVision; set and save your global settings,

     4. For each application which had specific Icons named, go in and name one 
Icon per-application.    This step will create new ".WVB" files and update the 
WV2.INI     file.

     5. From with in your WINDOWS directory, delete all the "WVB" files that 
have corresponding "WVX"     files,

     6. rename the "WVX" files back to "WVB" files.


Whichever of these approaches you take, make a back up of the new
".WVB" files and the WV2.INI file.  If these files get
corrupted again, you can just restore them.  When version 2.04 of
WinVis2 is released, you won't need to do this anymore.