Top Navigational Bar

.SET File Changed To Read-Only Status Changes
DocumentID: 652747
Revision Date: 29-Feb-96 8:29:18 PM

The information in this document applies to:
WordPerfect® 5.1 for DOS

Problem

Symptoms: Why is it that when you flag or ATTRIB the .SET file Read-Only, that only the selected printer shows up on the list and changes made to Initial Codes do not take effect? Is this the way the program is designed? This is causing problems for network administrators who want to flag the .SET file RO so that users can't enter WordPerfect as {WP and make changes to the master .SET file. Solutions: The reason that WordPerfect does not work the same and perform the same when the personal .SET file is given a Read-Only attribute is because when the user types WP to start the program it reads the .SET file. The routine used to read the .SET file is called PFSYS.PFSYS which always opens the .SET file with Read/Write attributes. The .SET packets read by SYSREAD in WPSTRT are read incorrectly if the .SET file is Read-Only. Packets read BYPFSYS when the file is not changed to Read-Only and this includes monitor attributes, printer packets, and Setup Initial Codes.

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.