Installation instructions for WordNet 1.6 database package. 1. Manifest When the WordNet database package is unbundled you should have the following files and subdirectories in the subdirectory "wnpcinst": CHANGES.txt changes to WordNet since version 1.5 INSTALL.txt this file LICENSE.txt WordNet copyright and license agreement README.txt README file for WordNet system README.ml information about the user mailing list READMENT.txt README file for Windows NT users only setup.exe installation program for all versions of Windows install.exe installation program for DOS w32s130.exe Win32s system extensions needed for use with Windows 3.x, installed automatically by setup.exe if needed msvcrt40.dll Win32s support file vbrun300.dll setup.exe support file _setupb.exe self-extracting archive of precompiled PC binaries, source code, and documentation, unarchived automatically by the installer _setupd.exe self-extracting archive of WordNet 1.6 database, unarchived automatically by the installer 2. WordNet Installation 2.1 Installing the FTP Package The WordNet 1.6 database package for the PC is distributed for FTP as a self-extracting archive. The package can be downloaded as one 14.5MB file (wn16pc.exe) or as a series of 512K files (wn16pcm.exe, wn16pcm.r00, ..., wn16pcm.r26). Executing the downloaded package, "wn16pc.exe" or "wn16pcm.exe" , unbundles the installation programs and package archives into the directory "wnpcinst", containing the files and directories listed above. 2.2 Installing from CD-ROM Installing from the WordNet CD-ROM does not require the previous step. The directory "wnpcinst" contains the files and directories listed above. 2.3 Running the WordNet Installation Program To install the WordNet database, precompiled browsers, source code, library, header files and documentation, you must use the installation program that is appropriate for your system. The installation programs are located in the "wnpcinst" directory ***** Do not attempt to run both installers ***** Windows 3.x, Windows 95, Windows NT setup.exe DOS install.exe After WordNet installation, Windows users will have access to both the WordNet window-based browser and command line interface. DOS users will have access to only the command line interface. Both of these installation programs will prompt you for installation information, such as where to install the package. If you are installing from the WordNet CD-ROM, you can choose to install the package on your hard drive or leave it on the CD-ROM. Once you have answered all the questions, the program will complete the WordNet installation. Please note that the installation directory name specified should be no longer than 8 characters. If you do not use the default location, and specify a directory name longer than 8 characters, it will automatically be truncated to 8 characters. After installing WordNet you must reboot your system before running the browser. 3. Troubleshooting There are three potential problems that are known to apply to the WordNet 1.6 installation process for DOS and Windows. Problem 1: Not enough DOS environment space Your computer may show an error message like this when you reboot at the end of the installation process. If it does, you will have to edit your C:\CONFIG.SYS file. You can do this with EDIT.EXE that comes with DOS, or with Notepad under Windows. Under Windows 95, Notepad may not display CONFIG.SYS in the file open box directory listing, but it is there anyway, and will come up if you type its name. Look for a line that starts with "shell=". At the end of the line, you should add the text " /e:1024". If there is already a "/e" option, then you should increase the number it shows rather than adding a second "/e". If there is no line that says "shell=", add a new line to the end of the file saying "shell=c:\command.com c:\ /p /e:1024". After editing the file, be sure to save. WordNet should be ready to run as soon as you reboot your computer. Problem 2: Not enough disk space WordNet 1.6 is a large package, so it is possible that it requires more space than is available on your hard drive. If that is the case, there are several ways that you can clean up your hard drive so as to make more free space for WordNet. If you are installing WordNet from the FTP package and were able to run the "wn16pc.exe" (or "wn16pcm.exe") self-extracting archive without errors, you can now delete that file and work directly from the "wnpcinst" subdirectory it created. Second, you can empty your recycle bin (Windows 95 or NT) by right clicking on its icon and selecting the "empty" option. If these actions fail to free enough space for the WordNet installer to work, you can consider deleting older installations of WordNet, if applicable, or other software packages you no longer need. If you are installing WordNet from the CD-ROM, you can choose to run WordNet off the CD-ROM instead of installing it on your hard drive. In this case, WordNet will not use any disk space on your system. Problem 3: Potential conflict with Plug-and-Play boards Note that most systems have no conflict with WordNet, so you should not worry about this unless you actually observe a problem. The WordNet installer adds WordNet specific information to the end of your C:\AUTOEXEC.BAT file. We have observed that certain Sound Blaster installations generate AUTOEXEC.BAT file information when the system is booted, and that this information must be at the end of the file. When the WordNet section is at the end of the file, it gets deleted when the system is rebooted. When the WordNet section precedes the Sound Blaster information, everything works fine. If, after installing WordNet and rebooting your system, WordNet cannot find the database files, you should examine your C:\AUTOEXEC.BAT file to see if a WordNet section of this sort is present: REM --- begin WordNet 1.6 modifications --- SET WNHOME=C:\wn16 SET WNHOMEUX=C:/wn16 SET TCL_LIBRARY=%WNHOME%\LIB\TCL7.6 SET TK_LIBRARY=%WNHOME%\LIB\TK4.2 REM --- end WordNet 1.6 modifications --- If this section is missing, you should add it before the Sound Blaster information. The Sound Blaster commands are lines that start with "set SOUND=", "set BLASTER=", and "set MIDI=". What should be in the AUTOEXEC.BAT file differs depending on whether you chose to install WordNet on your hard drive or not. Select the appropriate set of lines for your installation and edit them as needed. For a default run-from-CD-ROM installation.... REM --- begin WordNet 1.6 modifications --- SET WNHOME=D:\wn16pc SET WNHOMEUX=D:/wn16pc SET TCL_LIBRARY=%WNHOME%\LIB\TCL7.6 SET TK_LIBRARY=%WNHOME%\LIB\TK4.2 REM --- end WordNet 1.6 modifications --- For a default copy-to-hard-disk installation... REM --- begin WordNet 1.6 modifications --- SET WNHOME=C:\wn16 SET WNHOMEUX=C:/wn16 SET TCL_LIBRARY=%WNHOME%\LIB\TCL7.6 SET TK_LIBRARY=%WNHOME%\LIB\TK4.2 REM --- end WordNet 1.6 modifications --- After editing the file, be sure to save. WordNet should be ready to run after you reboot your system. 4. Using WordNet 4.1 Running the Window-based Browser The window-based browser interface is run by selecting its icon from the Start menu (Windows 95) or the Program Manager (Windows 3.x). See the manual page 'wnb' or the browser's help menu for details. 4.2 Running the Command Line Interface The command 'wn' runs the command line interface. This is usually used from other applications or shell scripts, or by DOS users who do not have access to a windowing system. See the manual page 'wn' for details on using the command 'wn'. The WordNet installation program does not change your PATH setting. Before using the 'wn' command you should 'cd' to C:%WHNHOME%/bin, where the command exists. If you are running from the CD-ROM, it must be in the CD-ROM drive. (The installation program sets %WNHOME% in the AUTOEXEC.BAT file based on the information you provide.) 5. Cleaning Up 5.1 Removing the Installation Files If you downloaded WordNet by FTP rather than using a CD-ROM, we strongly recommend that you delete the files used by the installer once you have successfully completed the installation. This will let you recover quite a bit of disk space. As an example, if you downloaded the WordNet installation package to "c:\downloads\" then type: del c:\downloads\wn16pc.exe (or del c:\downloads\wn16pcm.exe) del c:\downloads\wn16pc\*.* rd c:\downloads\wn16pc Note that you might have removed wn16pc.exe earlier (see Troubleshooting, above). 5.2 Saving Disk Space If disk space is at a premium, and you are not doing research or development using WordNet, you can remove the files "index.sense" and "index.gloss" from the database installation directory (the default location is C:\wn16\dict. These files are quite large, and are not used by the WordNet browsers. Please be careful not to remove any other files. All the other database files must be present for the Wordnet browsers to run. 6. Documentation WordNet documentation is provided in the form of Unix-style man pages in following formats: File Format Directory ======================================== nroff source C:\wn16\man ASCII text files C:\wn16\man\cat HTML files C:\wn16\man\html PostScript files C:\wn16\man\ps Substitute your installation location if you did not install in the default location. 7. Compiling the WordNet Source Code Note that compiling the WordNet source code is not for the faint of heart. Sample Makefiles are provided, but they may not work on your system unless your development environment exactly matches ours. On the other hand, the directory structure is fairly straight-forward, and clean. Please refer to the man pages binsrch, morph, wnintro, wnsearch and wnutil for information about the WordNet library. The DOS version of the WordNet library and command line interface are set up to build using the free DOS port of the GNU development environment called DJGPP. It is available from Delorie software at "http://www.delorie.com/djgpp/". The Windows version of the WordNet library and visual browser interface are set up to build using Microsoft Visual C++ 4.0. They also require the complete source distribution of Tcl/Tk, a toolkit which is freely available from Sun Microsystems at "ftp://ftp.sunlabs.com/pub/tcl". You need to download and install Tcl version 7.6p2 and Tk version 4.2p2. Because the DJGPP and MSVC development environments cannot run at the same time, WordNet for the PC does not come with a single top-level Makefile. Instead, each individual piece (wn, wnb, and the DOS and Windows versions of the library) has its own Makefile within respective subdirectories of %WNHOME%\src.