                VisSim Readme File

Thank you for purchasing VisSim. We have done our best to ensure that 
VisSim runs quickly and reliably. If you run across any problems or 
have some suggestions about how we might make VisSim better, please fill
out the Bug and Suggestion report form at the end of this document.
If you encounter any problems during installation, please call our
tech support line at 508-692-5499, or FAX us at 508-692-3102, or send
us email via internet at "tech@vissol.com". If you want to upgrade VisSim,
or want to know about the latest products from Visual Solutions, give us
a call on our direct sales line at 508-392-0100.


*********************************
	VSDK Info

To compile and link your demo DLL files, just type "nmake" if you use
Microsoft compilers.  If you are unfamiliar with the make utility,
read the makefile tutorial that follows.

The VSDK development directory includes sample C (nnet), FORTRAN (fuser),
and Pascal (testpdll) userFunction blocks.


                        MAKEFILE TUTORIAL
                ------------------------------------

  For those unfamiliar with "make", a brief tutorial...
Make is a program build utility first developed at Bell Labs to run
on the Unix system.  It takes a program description file called "makefile"
and determines the least amount of work to do in order to build an up-to-date
version of your program.  It does this by comparing file dates of source files
to object files and compiling any source files that are newer than their
corresponding objects.  It then compares the file dates of your programs with
the dates of its constituent object files and will re-link your program
if any objects are newer than your program.  In this way, all rules for 
program build can be embodied in one file, and only the minimal actions 
necessary to build your program are done.
  Though "make" utilities available under the MS/DOS operating system are
relatively faithful reproductions of their Unix ancestors, there is one
maddening limitation of the DOS variety: DOS only allows 127 characters on a
command line.  You typically run into this limitation when you have long
link commands with many object files.  You will not run into this unless you
add more file names for your user blocks. If you do, the first line of
defense is to use short file names to try and squeeze the line in.
Another approach is to use "lib" to create a small library of your additional
objects and put the library in the object position on the link command line.
The last resort is to use a "response" file which is documented in your
compiler utilities programming guide.



VisSim Bug and Suggestion Form
------------------------------

How can we reach you?

Name:    _________________________________________________
Company: _________________________________________________
Address: _________________________________________________
         _________________________________________________
         _________________________________________________
Phone:   ________________________
Fax:     ________________________
E-mail:  ________________________

What Visual Solutions products are you using?

        Product                        Version                Serial number
________________________            _____________          ___________________
________________________            _____________          ___________________
________________________            _____________          ___________________
________________________            _____________          ___________________

Tell us about your system:

Meg RAM:          ___________________
Processor:        ___________________
Operating System: ___________________               Version: _________________
GUI:              ___________________               Version: _________________
Co-processor:     ___________________
Printer:          ___________________
Printer Driver:   ___________________               Version: _________________

Please describe your bug or suggestion:

Severity(Circle one):      Showstopper     Problem     Nuisance     Suggestion

Synopsis:_____________________________________________________________________

Details: _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________
         _____________________________________________________________________


If applicable, please send a .vsm file to illustrate the problem.
(Be sure to include all supporting .map and .dat files for each .vsm file.)
