*************************
VISIO 2.0 README.TXT FILE
*************************
This file contains important, late-breaking information about Visio. 
We recommend you read this file and keep a printed copy with your Visio 
documentation.  For important network-specific information, be sure to 
read (and print) the NETWORK.TXT file in the Visio directory.

Tip: If necessary, choose Word Wrap from the Notepad Edit menu to wrap 
the text within the document window.


----------------------------------
REPLACING VISIO 1.0 WITH VISIO 2.0
----------------------------------
When you install Visio 2.0 on top of Visio 1.0, copies of the Visio 1.0 
templates and stencils can be saved in a separate subdirectory.


---------------------------------------
OPENING VISIO 2.0 FILES WITH VISIO 1.0
---------------------------------------
You cannot use Visio 1.0 to open files created using Visio 2.0. If you try 
to open a Visio 2.0 file by using the Open command from the Visio 1.0 File 
menu, Visio displays a message that says you're using the wrong version of 
Visio. If you try to open a Visio 2.0 file by double-clicking the filename 
in the Windows File Manager, Visio 1.0 displays an internal error message, 
which does not describe the problem. If you get this message and suspect 
the file you're trying to open was created in Visio 2.0, you can confirm 
it by trying to open the file using the Open command from the File menu.


-------------------------
VISIO 2.0 INSTALLED FILES
-------------------------
The following lists show the files copied to your hard drive if you 
install the complete version of Visio in the default location:

Setup copies these program and text files to the Visio directory:
NETWORK.TXT
PROGREF.HLP
README.TXT
VISIO.EXE
VISIO.HLP
VISIOLIB.DLL

Setup copies these import and export filter files to the Filters subdirectory:
EBBMP9.FLT
EBBMP9.INI
EBPCX9.FLT
EBPCX9.INI
EBTIF9.FLT
EBTIF9.INI
EMCGM9.FLT
EMCGM9.INI
EMDXF9.FLT
EMDXF9.INI
EMPCT9.FLT
EMPCT9.INI
EMPS_9.FLT
EMPS_9.INI
IMCGM9.FLT
IMCGM9.INI
IMDXF9.FLT
IMDXF9.INI
IMPCT9.FLT
IMPCT9.INI
IMPS_9.FLT
IMPS_9.INI
IMWMF9.FLT
IMWMF9.INI
IRPCX9.FLT
IRTIF9.FLT
ISGDI9.DLL
ISGDI9.INI

Setup copies these sample drawing files, which use shapes from the stencils 
that come with Visio, to the Samples subdirectory:
BLOCK.VSD
FLOWCHRT.VSD
NETWORK.VSD
ORGCHART.VSD

Setup copies these template (.VST) and stencil (.VSS) files to the 
Template subdirectory:
BASIC.VSS
BASIC.VST
BLOCK.VSS
BLOCK.VST
BORDER.VSS
CALLOUT.VSS
CHART.VSS
CHART.VST
CLIPART.VSS
CONNECT.VSS
EE_BASIC.VSS
EE_BASIC.VST
EUROPE.VSS
FLOWCHRT.VSS
FLOWCHRT.VST
FORMS.VSS
FORMS.VST
MAP.VSS
MAP.VST
NETWORK.VSS
NETWORK.VST
ORGCHART.VSS
ORGCHART.VST
PRACTICE.VSS
PRACTICE.VST
PROJMGT.VSS
PROJMGT.VST
SPACEPLN.VSS
SPACEPLN.VST
STATES.VSS
SYMBOLS.VSS
WORLD.VSS

Setup copies these DLL files to the Windows\System subdirectory:
COMPOBJ.DLL
OLE2.DLL
OLE2PROX.DLL
OLE2DISP.DLL
OLE2NLS.DLL
OLE2.REG
STORAGE.DLL
VBOA300.DLL
VBRUN300.DLL

Setup copies this quick tour file to the Tutorial subdirectory:
VISTUTOR.EXE

Setup copies these files to the Add-ons subdirectory and to the Library 
and Stndoc subdirectories within the Add-ons subdirectory:
INVNTRY.HLP
INVNTRY.VSL
MAIN.BAS
PROGRESS.FRM
REPORT.FRM
SELLOOK.FRM
SELSTENC.FRM
STNDOC.EXE
STNDOC.ICO
STNDOC.MAK
STNDOC.VST
VISCONST.BAS
VISREG.BAS

The Visio setup program also creates a Drawings subdirectory (a place 
to store your drawings).


----------------------------
VISIO AND OLE 2.01 DLL FILES
----------------------------
If you have trouble running Visio, make sure all the OLE 2.0-related DLL 
files are installed in the correct location and are dated 11/16/93 or later. 
All of the following files must be installed in the Windows\System 
subdirectory to run Visio:

File            Version Number          File Date       File Size
-------------   -------------------     ------------    --------------
COMPOBJ.DLL     0002.0001.0100.0014     11/16/93        102400  bytes
OLE2.DLL        0002.0001.0100.0014     11/16/93        313344  bytes
OLE2DISP.DLL    0002.0001.0100.0013     11/16/93         90144  bytes
OLE2NLS.DLL     0002.0001.0100.0013     11/16/93         99200  bytes
OLE2PROX.DLL    0002.0001.0100.0014     11/16/93         55808  bytes
STORAGE.DLL     0002.0001.0100.0014     11/16/93        157184  bytes

If any of these files are missing, reinstall Visio. If you're running 
Visio from a network server, see your system administrator and see 
NETWORK.TXT.

If you have further trouble, make sure there is only one copy of these 
files on your hard disk in a location where Windows can find them. If 
you have multiple copies, either delete the extra copies or move them 
to a location where Windows can't find them. (Windows looks in your drive 
path, the application subdirectories, the Windows directory, and the 
Windows\System subdirectory.)


----------------------------------
VISIO 2.0 AND WINDOWS REGISTRATION
----------------------------------
At the end of the installation process, the Visio setup program displays 
a dialog box asking if you want to run Visio. To ensure that Visio is 
correctly registered in the Windows REG.DAT file (a file that contains 
information about the capabilities of each application), we recommend 
that you run Visio by choosing Run VISIO Now in the dialog box.

If you suspect that Visio is not properly registered (for example, if 
Windows displays an error message saying it cannot find the source 
application when you double-click an embedded Visio object in another 
application), you can force the registration process by choosing Run 
from the Windows Program Manager File menu and typing the Visio path 
followed by /r. For example:

	c:\visio\visio.exe /r

If Visio displays error messages saying OLE2 is improperly registered, 
you can register it manually by using the Microsoft Registration 
Information Editor:

1.  Choose Run from the File menu in Program Manager or File Manager and 
type "regedit" at the prompt to launch the Microsoft Registration 
Information Editor.

2.  Choose Merge Registration File from the File menu.

3.  Choose the OLE2.REG file from your Windows\System directory and choose 
OK.

4.  Choose Exit from the File menu to exit regedit.

Please see NETWORK.TXT if you are doing a network installation.


-------------------------------------
DECOMPRESSING INDIVIDUAL FILES
-------------------------------------
For users of DOS 6.0 and higher, you can use the expand utility in your 
DOS directory to decompress individual files from a Visio installation disk.  For example, from DOS type:

	c:\dos\expand a:\basic.vs_ c:\visio\template\basic.vss

Or, you can run Setup with the following command line:

	setup /z a:\basic.vs_ c:\visio\template\basic.vss


-------------------------------------
SCREEN IMAGES AND IMPORTED EPS FILES
-------------------------------------
EPS files have two parts: The PostScript code used to print the image 
and an optional screen image used to display the image on the screen.  
When exporting EPS files, most graphics applications either automatically 
include a screen image or give you the option to include one. If you are 
given the option and you plan to use the EPS file in a Visio drawing, you 
should  include the screen image (which is sometimes referred to as the 
TIFF preview). Otherwise, the EPS image may not be correctly displayed in 
or printed from Visio.


----------------------------------------
DISPLAYING AND INSTALLING TRUETYPE FONTS
----------------------------------------
If fonts in a dialog box don't display properly, check to see that TrueType 
fonts are installed in the Control Panel.

To check for TrueType fonts:
1.  Open the Main program group in the Windows Program Manager.
2.  Double-click the Control Panel icon.
3.  Double-click the Fonts icon.
4.  Make sure that (at a minimum) all the TrueType fonts that ship with the 
latest version of Windows appear in the list of installed fonts.

To add TrueType fonts:
1.  Choose the Add button.
2.  If no fonts are displayed, locate the Windows\System subdirectory (from 
the Windows main directory).  A list of TrueType fonts appears.
3.  Highlight the TrueType font(s) to be added and choose OK.


------------------------
ATI ULTRA PRO VIDEO CARD
------------------------
When using the Ultra Pro/Mach 32 video card and the driver (dated April 1993) 
made by ATI Technologies, objects with fills may print as black. Version 2.2 
of the driver solves this problem.  To get the driver, call ATI Customer 
Support at 416-882-2626, or download a copy from CompuServe. (Type GO 
ATITECH at the ! prompt.)


---------------------
PRINTING ROTATED TEXT
---------------------
On HP LaserJet III and other PCL printers, if rotated text does not print 
where you expect it to, try printing with Print TrueType as Graphics enabled. 
To enable this setting, choose Print Setup from the File menu, choose 
Options, make sure the Graphics Mode option is set to Raster, then check 
the Print TrueType as Graphics option. If this solves the problem, you may 
want to make this change permanently using the Windows Control Panel.


--------------------------------------------------
USING THE MICROSOFT(R) WINDOWS(TM) PRINTING SYSTEM
--------------------------------------------------
If you have trouble printing rotated text using the Microsoft
Windows Printing System product, use Notepad or another text 
editor to add the following line to the [Application] section 
of your VISIO.INI file:

     TextBaselineAlignment=0

Unless you are running VISIO over a network, the VISIO.INI file
can be found in the same directory as your VISIO.EXE file, usually
\VISIO. When running VISIO from the network, VISIO.INI is placed
in your Windows directory, usually \WINDOWS.


---------------------------------------------------
PRINTING ON HP LASERJET III and LASERJET 4 PRINTERS
---------------------------------------------------
If you use an HP LaserJet III or 4, be sure to use the latest version 
of the printer driver from Microsoft or Hewlett-Packard. The original 
drivers released with Windows 3.1 were version 31.1.89 for LaserJet III 
and 31.1.03 for LaserJet 4. The current versions, as of this writing, 
are version 2.1 for the LaserJet III used with the Universal Printer 
driver version 3.1.2, and version 31.V1.26 for LaserJet 4.

If you receive Error 21 (Print Overrun) messages when you print to the 
HP LaserJet 4, try these workarounds:

*  Use the Windows Control Panel to verify that you are using the 31.V1.26  
printer driver or later. Updates to the LaserJet 4 driver can be obtained 
in the CompuServe (HPPERI forum) or through HP.

*  Set the correct amount of printer memory in the Control Panel. This 
should match what you actually have on your printer. Please refer to the 
printer documentation for information on how much memory you need.

*  Set the graphics mode to Raster rather than HP-GL/2. Although the HP-GL/2 
mode is faster, often you can print more complicated pages using the Raster 
mode.

*  Try using the Page Protect feature for the paper size you're using. 
Please refer to the documentation that came with your printer for 
additional information on the Page Protect feature.

*  Try printing at 300 dpi rather than 600 dpi.

*  If none of the above options help, install the HP LaserJet III driver 
in addition to the HP LaserJet 4 driver.  Use the HP LaserJet III driver 
to print at 300 dpi to the HP LaserJet 4 printer.


--------------------------------------------
PRINTING ON HP DESKJET 500C or 550C PRINTERS
--------------------------------------------
When you print in Color mode on an HP DeskJet 500C or 550C with a version 
3.0 or 3.1 printer driver, TrueType text prints as long bands. To fix this 
problem, set your dithering to anything other than Standard (the default). 
To change this setting in Visio, choose Print Setup from the File menu, 
choose the DeskJet printer (if it is not already selected), choose Options, 
choose More, then choose any Dithering option but Standard. To make this 
change permanent, set it using the Windows Control Panel.

Note that after you print using one of these printers, Visio is no longer 
the active application. To bring Visio back to the foreground, type 
Ctrl+Esc to open the Windows Task List dialog box, choose Visio from the 
applications list, and then choose Switch To to make Visio the active 
application.

Note:  Use the method described above to make Visio the active 
application. Do not double-click the Visio icon.  Double-clicking the 
icon opens another instance of Visio.


-----------------------------
PRINTING FROM WORDPERFECT 5.2
-----------------------------
When you print a Visio drawing in WordPerfect, it might look significantly 
different from the way it looks when you print it in Visio. This might be 
related to the printer driver you are using with WordPerfect. Visio created 
your drawing with a reference to the printer driver selected in the Print 
Setup dialog box in Visio. To make the printed drawings look more similar, 
use the same printer driver in WordPerfect that you use with Visio.

Although you may be printing to the same printer from both applications, 
in WordPerfect you have the option of using either the WordPerfect 
printer driver or the Windows printer driver. If you have been using 
the WordPerfect printer driver to print Visio drawings from WordPerfect, 
try choosing the Windows printer driver in the WordPerfect Select Printer 
dialog box.


------------------------------------------
ZEOS 486-33 CPU & FLOATING POINT EXCEPTION
------------------------------------------
The Award BIOS 3.10, 452-005-01, found in some ZEOS 486-33 machines 
(and possibly in other computer makes and models), does not handle 
floating point errors correctly.  Floating point errors cause these 
machines to hang (stop responding). Floating point exceptions are most 
likely to result from using the Union or Fragment commands. If Visio 
displays an error message telling you that a floating point exception 
has occurred, try to save your work (if possible), then close Visio and 
Windows and restart your computer.

To correct this problem, you need an updated BIOS.  ZEOS owners can 
contact ZEOS Technical Support at 612-633-7337 voice, 800-228-5390 
toll-free, or 612-633-4607 FAX.  Owners of other machines can contact 
the manufacturer of their machine. 


--------------------------------------------------------------
USING VISUAL BASIC'S OLE AUTOMATION FEATURES TO CONTROL VISIO
--------------------------------------------------------------
The following information describes workarounds for problems we have 
found using the OLE Automation features of Visual Basic.

1. Don't use complex expressions as parameters to methods. If you chain 
several methods together in an expression and then pass that expression 
as the parameter to another method call, Visual Basic allocates 
temporary storage for the expression and never releases it. If you do 
this enough times, Visual Basic eventually crashes. For example, the 
following code causes an Application Error in Visual Basic:

	Dim visio As Object     ' Visio application object
	Dim wins As Object      ' Window collection

	Set visio = GetObject( , "visio.application")
	Set wins = visio.Windows
	For i = 1 To 1000
		k = wins.Item(wins.Count).Index
	Next

To work around the problem, replace the body of the loop with:

	For i = 1 To 1000
		cnt = wins.Count
		k = wins.Item(cnt).Index
	Next

2. You must use square brackets around the method names that conflict 
with Visual Basic keywords:

	Arrange
	Close
	Delete
	Print

For example,

	visio.Windows.[Arrange]

If you don't use square brackets, Visual Basic displays the following 
message:

	"Method not applicable for this object"

3. Visio generates unique run-time error codes for different types 
of OLE Automation errors. Visual Basic, however, ignores these error 
codes and converts them all to a generic OLE Automation error--Error 440. 
This is a Visual Basic 3.0 issue that should be resolved in the next 
release.

4. Be careful when using default properties. Visual Basic calls the 
default property for an object even after an exception has occurred. 
This generally results in an Application Error in OLEDISP.DLL. For 
example, in some circumstances the following statement generates an 
Application Error:

	Set page = doc.Pages(1)

In this example, Item is the default property for collections. If 
calling the Pages method generates an exception for whatever reason, 
the previous statement will cause an Application Error.

To work around the problem, replace the previous statement with:

	Set page = doc.Pages.Item(1)

