home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Professional
/
OS2PRO194.ISO
/
os2
/
progs
/
papyrus
/
papyru.doc
< prev
next >
Wrap
Text File
|
1993-05-17
|
12KB
|
261 lines
paPYrus (tm) Supplemental instructions for BBS users, sysops, network admins
-------------------------------------------------------------------------------
Note: A product summary appears below, enclosed within a box.
Contents: * General instructions
* Special instructions for BBS users
* Special instructions for BBS sysops
* Special instructions for network administrators
----- GENERAL INSTRUCTIONS -----
Contact information:
24 hour, 7 day toll-free voicemail information hotline: 1-800-497-2896
Currently accessible in the U.S.A. and Canada only.
Jon C. Duringer, Crafter
142 N. Milpitas Blvd., #190
Milpitas, CA 95035-4401
USA
Most paPYrus documentation is accessed by opening the paPYrus program object
on your desktop display. If you do not move the mouse or key anything in the
first 10 seconds that paPYrus is completely open, a message will appear that
directs you to the menu which contains the documentation.
paPYrus is distributed within the user community as authors selfpublish their
writings to readers. paPYrus writing is always "cloned" to diskette rather
than printed on paper. The recipient of a paPYrus clone diskette "opens" it
to view the writing. Once this is done, a paPYrus program object will appear
on the desktop, and the recipient has full, permanent access to all paPYrus
functions.
Each paPYrus clone diskette is a complete, self-contained, fully functional
distribution package; no other files or documentation are needed.
----- SPECIAL INSTRUCTIONS FOR BBS USERS -----
paPYrus users ARE supposed to privately distribute entire clone diskettes to
one another, but the following rules and shortcuts can be followed to reduce
file transfer time and to standardize how paPYrus users communicate on BBS's:
1. Do not upload an entire clone diskette image onto a public bulletin
board or network without prior voicemail permission from the crafter.
(An employer bbs or network is ok if it is not open to the public.)
2. If you are granted permission to upload an entire clone diskette, never
upload it in zip'd or arc'd form; always use a self-extracting diskette
image file if compression is needed.
Adhering to the "clone diskette" concept makes paPYrus easier for new
users to understand and eliminates problems related to incorrect manual
reconstruction of the subfolders (subdirectories) used by LEAF
references.
3. If you are granted permission to upload a clone diskette image,
always use the following standard file names and descriptions:
For the self extracting clone diskette image:
+----------------------------------------------------------------------+
| |
| PAPYRU.EXE "paPYrus (tm) --- An editor for the 21'st century!" |
| |
| PAPYRUS HYPERTEXT PUBLISH ROYALTY DRAW PAINT EDITOR WORD WRITE TREE |
| |
| Introducing tree writing, an experimental writing form. Eliminate |
| writers' and readers' block by eliminating paragraphs. Use to read, |
| write, selfpublish. Includes interface to payPERview (sm) reading |
| fee service. |
| |
| Metered shareware. Approx. annual cost of regular use is $40 U.S. |
| plus reading fees (set by authors). No registration; user pays for |
| refills. |
| |
| Req: OS/2 2.0; .6Mb perm + 2Mb temp drive C space; diskette drive. |
| This image requires a 1.44Mb diskette drive. |
| |
+----------------------------------------------------------------------+
The doc file that you are reading should always be named PAPYRU.DOC and
then compressed, e.g. zip'd into PAPYRU.ZIP:
+----------------------------------------------------------------------+
| |
| PAPYRU.ZIP "paPYrus (tm) doc. for BBS users, sysops, network admins" |
| |
| PAPYRUS HYPERTEXT PUBLISH ROYALTY DRAW PAINT EDITOR WORD WRITE TREE |
| |
| Supplemental doc. for BBS users, sysops, and network administrators. |
| Download PAPYRU.EXE to obtain all files needed to use paPYrus (tm). |
| |
+----------------------------------------------------------------------+
4. When uploading your written work, upload only the data file (and leaf
folders (subdirectories), if any), in a single compressed file.
Generally, you should upload into an area set aside for paPYrus (tm) or
for hypertext documents, if available, or into an area reserved for
creative written work. Don't upload into an area that is reserved for
software or for computer support. To upload:
a) CRAFT: Craft your written work.
b) CLONE: Create a clone diskette by selecting "Clone".
c) DESCRIBE: Include a description text file. The following can be
used as an example:
Text file PROS23.DOC:
+----------------------------------------------------------------------+
| |
| PROS01.ZIP "An essay on free trade" |
| |
| PAPYRUS SMITHROBERTO ESSAY TRADE PROTECTIONISM POLITICAL ECONOMY |
| |
| "An essay on the benefits of free trade in software for both |
| developed and developing regions", by Robert O. Smith. |
| |
| Download PAPYRU.EXE and PAPYRU.ZIP to view this document. |
| Cost of one full reading: 6 tree branches. |
| |
| ABSTRACT: Identifies the specific groups likely to benefit or to be |
| harmed by unrestricted free trade in software. Analyzes the overall |
| effect on software production and consumption. |
| |
+----------------------------------------------------------------------+
d) ZIP: Compress ("zip") the "1.TRE" file object on the clone diskette
into a zip file. Include the text description (*.DOC) file. Also
include any leaf folders that appear on the clone diskette, for their
presence indicates that they are referenced in the 1.TRE file.
The following naming convention is suggested: "PiiiNN.ZIP"
where "P" causes all paPYrus documents to sort together, "iii" are
your initials, and "NN" is a serial number or id for your document.
Hopefully, long file names will soon be supported on bbs's, allowing
names such as "papyrus.smith.robert.freetrade.rev1.tre".
d) UPLOAD: Upload only the PiiiNN.ZIP file object.
4. When downloading someone else's written work (a PiiiNN.ZIP file): Your
goal is to recreate, and then open, a clone diskette. You can do this
by:
a) CLONE: Open the paPYrus object on your desktop and clone something
(any branch will do, but an empty branch is best) onto a diskette.
b) DOWNLOAD: Download the PiiiNN.ZIP file and unzip into an empty
temporary folder on your hard drive. Always create any subfolders
(subdirectories) stored in the compressed file; this will usually
not be done for you unless you specify a parameter when unzipping.
c) DELETE: Delete (or move) any *.DOC text files in the temporary
folder after reading them.
d) COPY: Copy the entire contents of this temporary folder, which now
contains a 1.TRE file and might also contain subfolders, to the
\PAPYRUS folder on the clone diskette.
Example command: "xcopy c:\tmp\*.* A:\PAPYRUS /s/e"
e) OPEN: Open the clone diskette in the normal way.
Example command: "A:\PAPYRUS\1"
----- SPECIAL INSTRUCTIONS FOR BBS SYSOPS -----
The above instructions, if followed by many users on your bbs, will result in
a periodic download of the relatively large PAPYRU.EXE self extracting diskette
image by each paPYrus user who wants to update to the latest version of this
application. You will also see much up and down traffic in very small
PiiiNN.ZIP (usually compressed, or zip'd) hypertext files which contain
creative writing. Some of these PiiiNN.ZIP files will be larger because the
hypertext includes simulations, games, and other embedded application programs.
Short file name restrictions will hamper users who want to selfpublish
individual works of creative writing on your BBS. If you start to see an
accumulation of poorly named *.TRE or *.ZIP uploads as writers attempt to find
unique names, please consider the following suggestions:
1. Establish an area reserved for selfpublishing software and a separate
area reserved for individual selfpublishing documents.
2. Once each month, compress all new document uploads into a single file,
perhaps named, e.g. "9305.ZIP".
The above steps should enable a large number of your BBS users to selfpublish
without leaving files in random areas or running out of meaningful file names,
and is general enough to provide for future (competing) software support for
hypertext selfpublishing.
----- SPECIAL INSTRUCTIONS FOR NETWORK ADMINISTRATORS -----
To make paPYrus available to network users:
1. Use paPYrus to write up a cover letter that you want to appear whenever
one of your network users accesses paPYrus for the first time.
2. Clone that cover letter to a diskette.
3. Copy the entire contents of the \papyrus folder, including subfolders
(subdirectories) if any, on the clone diskette to a folder (directory)
on a server drive that is accessible to clients.
To test your installation, go to a client computer and open (run) the 1.EXE
file object that is among the files that you placed onto the server drive. You
can do this from any default drive and directory, i.e. you don't need to change
drives or directories.
That client should behave just as if you had received a physical clone
diskette; a paPYrus folder will be created on drive C, a paPYrus program object
will appear on the desktop, and your cover letter will appear on the screen.
To make a paPYrus update available to your network users:
1. Open the clone diskette that has the new version, so that your computer
is updated.
2. Follow the steps listed above, replacing the folder that you are using
on the server.
3. Have each client open the 1.EXE file object that is on the server disk.
This should result in your cover letter appearing on each client's display,
explaining that they now have a more recent version of paPYrus and explaining
which of the new features might be of special interest to your organization.
----- THE END -----