Installation manual.

Chapter 1 : 'LAN' concept overview.

If you plan to use WinDi Translation Help in your LAN, please read this chapter first.

Before starting the installation of this application, you must respect the following concept : for a correct working of WinDi Translation Help and to get entire satisfaction from the first installation, you must declare to your LAN the presence of a virtual MS/DOS disk which is accessible to all LAN users under the same resource name, for example the W: drive (our functions cannot be reached via different disks or mappings at the user level). We strongly advise you to start the installation of WinDi on your LAN from a LAN station of your choice (do NOT install WinDi directly into your server!).

The virtual disk, that you will have defined according to your possibilities can, of course, be an already existing resource, already reached by each user for other applications. In this virtual disk, the WinDi Translation Help application will need all access rights (during and after the installation). After having completely installed the software, we advise you to protect the subdirectory created at the installation (...\LANGFILE and ...\CONJUG directories) against all other access types that could alter the good working of the WinDi programs (WRITE, DELETE,...) Beware : if you intend to add new words into WinDi by means of the WinDi Tools - Encoding program, the remarks here above must not be taken into account for the LANGFILE directory.

For further information concerning what is mentioned above, and regarding the configuration of your network, please refer to the installation manual of your LAN.

Remark : to have WinDi Translation Help correctly working from your LAN, the Language Dynamics programs must be able to read the various application files on the server; which is also the case for all networks on the market. WinDi Translation Help is compatible with the networks belonging to the NOVELL type (3.1X, 4.X, 5.X), LAN MANAGER, LAN SERVER, PATHWORKS, TCP/IP, NFS, PC-Support, LANTASTIC, etc. Please refer to Chap. 4.1 (WinDi Translation Help installed in a network) where the possible problems of 'Sharing violation' are mentioned.

Chapter 2 : General information on the installation.

- The installation time for WinDi Translation Help will directly depend on the power of the PC where the installation is made. Concerning LAN installations, the server's performance is very important : it shortens or lengthens the installation time.

- Concerning stand-alone installations, we strongly advise the use (if applicable) of the 'SMARTDRIVE' program, which enables to reduce to the minimum the physical access to the local disk. Thanks to this program, you will save a considerable amount of time!

- To be installed, WinDi Translation Help needs a space of approximately 60 Mbytes on the Hard Disk.

Our installation tests on various machines and environments have shown up that the full WinDi Translation Help package can be installed within a delay of +-10 minutes up to 1 hour, depending on the performances of the hardware.

Chapter 3 : Installation of WinDi Translation Help.

3.1 How to install WINDI-UP.EXE.

We suggest to follow the steps explained here below in order to download and install the WINDI-UP.EXE program.

However, carefully read Chap. 6 and Chap. 7 of this manual in order to avoid problems during the installation!

First of all, go to our WEB site at http://www.windi7.com/dwnupdem.htm. You must respect the following steps for a correct working of WinDi and to get entire satisfaction from the first installation!

1.You must 'save' WINDI-UP.EXE when you start the download with your browser!

2. Put it in a directory of your choice (ex: C:\TEMP).

3. After your download, you will be able to install WinDi in demonstration mode (for evaluation DURING 24 HOURS only!) or, if you already own your upgrade kit (allowing you to complete the WinDi installation) you will be able to continue the installation and reach the level of a full version.

4. If you want to use WinDi Browser, you have to install Microsoft Internet Explorer (Version 5.0 minimum) before installing WinDi, otherwise this feature WON'T work! However, all other WinDi modules will be operational without Internet Explorer 5.0. The choice is yours...

5. The WinDi installation runs under Windows. To start the installation, go to the directory where WINDI-UP.EXE is located by using Windows Explorer for example and click on the WINDI-UP icon, the installation will start. Then, follow the instructions on screen. If you select a directory different from the default one (C:\WINDI), please use ONLY directory name with 8 characters maximum. Please note that you can install this WinDi version on a 'virtual' drive (LAN/Workgroup drive). This way you are able to evaluate WinDi in a Stand-Alone or Network environment.

6. After the WINDI-UP.EXE installation, take your installation kit if you have it (you will receive it by mail after your order, see our Price List on our WEB site for more information) and follow the installation instructions you have received with the kit. Please note that you can immediately evaluate WinDi in demonstration mode, DURING 24 HOURS, even if you haven't ordered your upgrade kit. ATTENTION: This WinDi version is NOT a FreeWare or a ShareWare ! You are allowed to use this demonstration for evaluation purposes only (this implies that you will get 'DEMONSTRATION' messages on screen)! Use of this software in all other context is a violation of Language Dynamics' Copyright !

7. In the event of downloading problems, you can try to download WinDi again by using the same process.

Concerning the installation path, drive C: is suggested by default for stand-alone versions (you can indicate another hard disk, as long as it is a 'physical' one, ie. local). For a LAN version, you can install the program on a server disk, as long as it is a virtual one (see Chap. 1, LAN concept overview.)

The installation directory suggested by default is \WINDI\. You can change it according to your preferences. Please respect the syntax required by MS/DOS for the definition of directories. However, we advise you to keep the name of the \WINDI\ directory so that, if necessary, we can easily help you in case of problem.

For a LAN version, the installation program declares a 'Private Directory' where the applications will save the different configuration files. The C:\WINDI directory is automatically defined. Generally, each LAN user has a local hard disk C: Otherwise, you can indicate (after installation) a 'Private Directory' depending on the user's 'Login name' for this parameter. For instance, in the case of NOVELL, each user usually receives a part of the server disk for himself (private directory). That directory is located in a place depending on the user's 'Login name'. You certainly can exploit this resource in the WinDi applications, but it must be defined under the same name for all users (for example, drive U: being also for example the ...\USERS\xxx directory). For further information on this subject, please read the manual of your network.

In order to modify the 'Private Directory' for a LAN user of WinDi, you can change (after installation) the first line of the WINDI.INI file (placed in the WinDi installation directory). The second line of this file indicates where the WinDi Dictionaries are placed. Here is an example of this file:

C:\WINDI\

W:\WINDI\LANGFILE

In this file, the first line is the 'Private Directory' path. For example, you can replace this first line by:

U:\USERS\YOUR_LOGIN_NAME\ or D:\TEMP\

REMARK: YOU MUST PLACE A '\' AT THE END OF THIS PATH / FIRST LINE.

Please note that the 'Private Directory' is automatically created by the WINDI.EXE program when this application is running for the first time.

Chapter 4 : WinDi Translation Help configured for Windows in a network.

For a LAN station, you must run the WINDI.EXE program (after the installation of WINDI-UP.EXE) in order to allow the use of this application on this PC.

The installation processes described above must be made on each PC having to gain access to the application. Moreover, we recommend the reading of the TNU.USR file describing the possibility to allow one 'login name' per user to access the WinDi Project Manager application.

Please note that there is no limitation to the number of users who wish to use the applications in a network.

4.1 WinDi Translation Help installed in a LAN.

In certain cases (namely certain 'Peer to Peer' networks), the server does not allow the same program to be used by several users at the same time, because Windows permanently keeps an open program in reading, in order to find its resources and its modules. You can get a 'Sharing violation' error.

To solve this problem, please refer to the manual of your network for an optimization of the server.

If you didn't succeed in finding a solution, you can copy the directory of the WinDi programs (see the Installation Path, Chap. 3.1) to the C: drive of each user of your LAN, for instance, by using the command :

COPY [DRIVE]:\[PATH]\*.* C:\[PATH]

where :[DRIVE] = server disk where WinDi Translation Help is installed (ex. : F:)

[PATH] = directory where WinDi Translation Help will be installed (ex. : WINDI)

If you want to copy the WinDi programs onto a personal disk, you must tell Windows to use WinDi on the right disk (C:\WINDI for example).

The 'sharing violation' problem will disappear.

These optimizations are particularly recommended when your server is a mainframe (under UNIX for example) that can be overloaded.

Chapter 5 : From the development team.

We keep on extending the possibilities of the WinDi applications. On that subject, we will appreciate your possible remarks and ideas in order to make our programs even more comfortable to use.

Your remarks will be carefully analysed and, if possible, integrated in the future versions of these programs. So, don't hesitate to write us! If you encountered a problem during the installation or use of WinDi, let us know about it and provide us with an accurate description of your problem, in order to allow us to reproduce it in our test laboratory.

Send us an E-Mail in case of any problem at support@windi7.com !

Chapter 6 : How to install WinDi Translation Help on a PC using Stacker or Double Space.

Some PCs use drivers as Stacker or Double Space to increase the capacity of their local hard disk. The data compression procedures of these programs do not allow to decrease the size of the WinDi database files. The ratio after compression remains more or less at 1:1. In that case, if Windows using a disk compression driver declares having for example 50 MBytes free disk space, but with a ratio of more or less 1:2 (capacity uncompressed : 25 up to 30 MBytes real), WinDi Translation Help will not have enough space disk at its disposal (because our application needs 50 MBytes real during the installation, for all languages).

In order to avoid this problem, please note that, if you are using a disk compressor, you need at least +-100 MB of available disk space before starting the WinDi installation in all 7 languages. The installation will then occur without any problem. Please note that WinDi uses its own compression algorithm. For example, the conjugation algorithm takes +- 2.6 MBytes of database on your hard disk. In fact, the conjugation in seven languages is a database counting more than 300 MBytes before the compression by our algorithms!

 Chapter 7 : How to install WinDi Translation Help on a PC using Virus Protection.

Some virus detection programs detect, during the installation of WinDi, events that they assimilate to viruses. This is not true at all in the case of the installation of WinDi. In fact, during this installation, WinDi creates many files (more than 150 files for all languages) and sorts them one by one very quickly. The 7 conjugation files are created very quickly. These events seem to launch the above-mentioned programs, and the installation of WinDi cannot happen normally. In order to avoid this problem, do not enable these programs during the installation of WinDi, but check WINDI-UP.EXE before the installation if you wish so. Afterwards, disable your protection and install WinDi. Finally, enable your protection again when the installation is through.

Chapter 8 : System requirements.

You should have at least a 386 PC (Pentium advised) to run WinDi correctly, and 8MB RAM (32 MB advised). If you have 8 MB RAM, avoid using the '7 languages' function in WinDi Direct Translation, because it will be very slow. WinDi is Windows 3.1x / 9x / NT 4 / 2000 compatible (Note: WinDi Browser and Voice for WinDi are not compatible with Windows 3.1x). WinDi requires more or less 50 Mbytes of disk space after installation.

Chapter 9 : Installation under Linux, OS2 (WinOS2) or other O.S.

In order to install WinDi on another OS than Windows, the OS on which WinDi is installed must emulate Windows (ex.: OS2, PowerMac or Linux).

_________________________________________________________________

Logo

Visit our Web site: http://www.windi7.com