![]() |
Installing Bitstream FaceLift 1.5 For WP On A |
The information in this document applies to:
WordPerfect® 5.1 for DOS
Problem
Solutions: Installing Facelift v.1.5 on a Network FaceLift 1.5 allows network users to print documents with Bitstream typefaces on dot-matrix, inkjet and laser printers connected to a network. Users can install up to seven printers to which FaceLift can send output. FaceLift 1.5 works on these networks: 3COM LANtastic Novell NetWare The versions specifically tested with FaceLift 1.5 are Novell NetWare 386 3.01b, and Novell 286 with NetWare 2.15. The Spool command for older versions of NetWare is not supported; however, some customers have had success with running NetWare 2.01A which does employ Spool. The user needs to have Spool active, and should set the port mapping table in FLSETUP as LPTx to Direct. The LANtastic version tested was 3.03 and 3COM version 3+. NOTE: FaceLift 1.5 may work on other networks; however, FaceLift has not been tested on networks other than those listed above. NOTE: For additional information refer to the "Installing FaceLift 1.5 On a Network" pamphlet. Upgrading from FaceLift 1.0 When upgrading to FaceLift 1.5 it is important to delete the .ALL file(s), for example WPHP1.ALL. Then reinstall the .ALL files(s) using the WordPerfect installation disks or if using WordPerfect 5.0, copy the .ALL file directly into the WordPerfect directory. Users also need to delete the .PRS file(s) in WP, then reinstall them. Installation The documentation recommends installing the FaceLift program files in separate user directories on the network. (The typeface directory, typically called BTFONTS, may be shared by all users on the network.) If each user has his or her own FLWP configuration file, there is less of a chance of mapping to an incorrect printer and less of a chance for a user to change or alter the .PRS files. However, running separate installations of FaceLift on very large networks is impractical. Certainly it is possible to run one installation of FaceLift for all users on the network, if they are all printing to the same combination of a maximum of seven printers, or if the Capture command is typically run on the network. Whichever method is chosen, it is important to keep in mind that FaceLift must be executed from the directory where FLWP.EXE resides. A limitation of FaceLift is that it does not recognize search mappings; if you attempt to start FaceLift from a search mapped drive, usually typing FLWP will provide a "Scanning Fonts" message, and the fonts may be selected from the base fonts listing, but they will print in a resident printer font, ordinarily Courier. Workarounds to this limitation may include running either the DOS APPEND command or Novell's SMODE command in the AUTOEXEC.BAT or login script. Consult the DOS user guide or NetWare documentation for more information on these commands. Before the installation, users must have all access rights to the directory containing the WordPerfect .ALL files and to create the directory for installing the Bitstream scalable typefaces (typically, \BTFONTS). A comprehensive listing of required rights is shown below: FaceLift program: Install: Read, Write, Create, Parental Runtime: Read, Write, Shareable Printer drivers: Install: Read, Write, Create, Parental Runtime: Read, Write, Shareable Typeface files: Install: Write, Create, Parental Runtime: Read, Shareable To install FaceLift on a network, users must use the FLSETUP /N command. The first thing users are prompted for is a directory to store the FaceLift program files. This is the primary way in which installing with the /N switch differs from stand-alone installation, which simply places the FaceLift program files in the WordPerfect directory. If users don't have specific user directories, they can create a directory with a unique name to store the FaceLift files. The first thing FaceLift looks for during the installation is the WordPerfect environment file, WP{WP}.ENV. This file lets the system manager define WordPerfect startup commands in a single location for all users on the network. This file must be located in the WordPerfect program directory. It includes only two startup options: the network type (NT) and the personal setup file directory (PS). The /PS option identifies a common directory that is accessible by each network user to store his or her personal WPxxx.SET file, where xxx represents the user's initials. WordPerfect .SET files are used to define the initial settings that the WP program will use, such as printer selections, display attributes, backup options, and dictionary/thesaurus locations. There are two types of setup files: a master setup file and personal setup files. The master setup file provide the default WordPerfect settings for the entire network. Personal setup files are defined by the individual user and override the master file for that user only. FaceLift looks for the master setup file which is WP{WP}.SET. So, in the WP{WP}.ENV file it is important for the /PS to point to the directory where this WP{WP}.SET file is located. If the path is pointing to an individual .SET file, FaceLift will give a message: "Can't Find WP{WP}.SET Or Wrong Version." FaceLift looks at the WP{WP}.SET file to find the version of WordPerfect that is running and the default printer port. Once the installation of FaceLift is completed, FaceLift no longer needs the WP{WP}.SET file, except when FLSETUP is executed to alter FaceLift's configuration. On a peer-to-peer LAN such as LANtastic, users have the ability to read directories and files on others' workstations. For example, WordPerfect and FaceLift may be installed on the C: drive of one workstation, but another workstation references that first PC's C: drive as D:. Executing FLWP from D:\WP51 on the second workstation may result in either error messages of the "Can't Find Filename" variety, and/or Courier output. What the user will need to do is run a separate installation of FaceLift on the second workstation, specifying a separate directory for the FaceLift program files, and designating the WordPerfect program directory as D:\WP51\WP.EXE. Printing on a Network Printing on the network works the same way as printing from a stand-alone, in that FaceLift intercepts the information on what font the user chose in WordPerfect, creates the font information and sends it to the printer. In order to accomplish this the user must tell FaceLift to watch the same port that WordPerfect is printing to. Users must also tell FaceLift where to send the document once it has inserted the fonts needed for the document. The port that WordPerfect is printing to, and FaceLift is monitoring, must be one of LPT1 through LPT3 or COM1 through COM4. This can be a local printer port or a network printer queue. FaceLift can intercept information sent to a local printer port that isn't on the user's computer. FaceLift can do this because it intercepts the information before WordPerfect finds there is no port. Of course FaceLift still must send it's output to an actual printer or network queue. If the user tells WordPerfect to print to a port that FaceLift is not monitoring then fonts won't be substituted into the document, and the output will be garbled or print in Courier. If users correctly set up WordPerfect but tell FaceLift to print to the wrong port, then nothing will come out of the printer. There are five options to choose from when setting the printer port redirection in FaceLift on the Network: 1. DIRECT (Refers to interrupt request 21H) 2. LPTx (LPT1, LPT2, LPT3 or COM1, COM2, COM3, COM4; refers to interrupt request 17H) 3. Print queuename (not longer than 12 characters) 4. (blank) For ports that FaceLift should not monitor 5. (filename) See p. 36 for more information on printing to a file. For single-user systems, or systems where the printer is directly connected to the computer, people should use DIRECT. This option means that you are using your computer's BIOS to print, giving FaceLift the most control over checking when the printer is busy and also it makes editing while printing more responsive. This is the part of DOS that communicates with the computer's peripherals (the BIOS). The BIOS gives programs a standard way to communicate with these peripherals and to control them. Another choice is to use a DOS device driver (LPT1-LPT3 or COM1-COM4). For network users, people can either use the LPTx or COMx device driver, or DIRECT, or a Novell queue name, depending on how the network is setup. On Novell systems, using the queue name in FLSETUP is preferable because usually it will give better performance, and there should not be problems with premature end-of-job. On Novell systems using the Capture command, which some users will need to continue to use because it is required by other applications, use DIRECT. When using Capture, the NT (No Tabs) flag is vital because of the way NetWare interprets escape sequences. Omission of NT results in the incorrect font being printed. If Capture is enabled and the user specifies a queuename in FLSETUP, FLSETUP should take precedence. However, customers have frequently experienced the situation of blank pages ejecting from the printer when both are active: FaceLift and Capture are fighting for control of the print job. For this reason WPCorp recommends using either the queuename in FLSETUP or Capture /NT on the DOS level, not both. On non-Novell networks, customers have observed that usually the LPTx device driver works best. Since the device driver is opened at the start of the job, and closed at the end, the network can more reliably determine when the print job starts and stops for queuing. Using the LPTx device driver may also improve speed. There is, however, no hard and fast rule as to when to specify LPTx versus DIRECT; WPCorp has found that even on the same brand of network, depending on the version of the network operating system or whether WP 5.0 or 5.1 is being used, that the correct choice may be either LPTx or DIRECT. The user should initially set up the port mapping table using LPTx and if the resulting print job does not use the correct FaceLift font, the user should try DIRECT instead. Another critical item WPCorp has discovered necessary in setting FaceLift up for non-Novell networks, especially LANtastic and 3COM, is setting the "Network Printer?" option of WordPerfect to No. This is important because WordPerfect is merely handing the print job off to FaceLift, which has the ultimate control. This setting is found in the Select Printer: Edit menu, after you reselect the port, Shift-F7, S, E, 2 for Port, choose the appropriate port, then answer No if the query "Network Printer?" appears. |
Answer:
Details:
Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER. |