Tools en Utilities

home *** CD-ROM | disk | FTP | other *** search

/ Tools en Utilities / CDASS_5.ISO / shell / file / docmkr33.arj / DOCMAKER.DOC next >

Wrap

Text File | 1992-11-12 | 38.4 KB | 796 lines

--------------------------------------------------- -- -- -- DOCMAKER Version 3.0 -- -- -- -- (C) 1991, 1992 -- -- Prometheus Systems Incorporated -- -- -- -- DOCMAKER User's manual -- -- -- --------------------------------------------------- For Starters. ------------- First of all, I'd like to state that this text is written by the author of the program, I'm Belgian and my English isn't perfect. I did my best on this manual, don't blame me if you find any grammatical/spelling errors. I would appreciate it if you would point out any. Introduction. ------------- The DOCMAKER is a program which provides you with an easy to use system to show texts and pictures, in a nice user-friendly interface. All texts and pictures are incorporated in a single file. What's the purpose. ------------------- Originally, the DOCMAKER & DOC-Interpreter were developed to fill up a hole in the PC software market. The idea comes from the Amiga, where a lot of (mostly underground) computer groups/clubs bring out a so called DOC DISK, a disk with a lot of manuals, solutions, hints and cheat/hack-tips about games and sometimes even business software (there even was a DOC DISK with the entire manual of Deluxe Paint IV, over 700 pages of text). Although the DOCMAKER was intended to bring such DOC DISKs to the PC, it's quite possible you have another use intended. The most likely use of the DOCMAKER is to release a magazine-on-a-disk. DOCMAKER Vocabulary. -------------------- Throughout the DOCMAKER document files, following words will be used : Crunching : A method of reducing the size of data without loss of data. To use the data, it has to be decrunched first. Decrunching : The process of returning crunched data to its original format. Encrypting : Transforming into unreadable. Decrypting : Transforming back into it's original format. DOC-Interpreter : The program used to display/print the texts and/or pictures. A DOC-Interpreter can not run stand-alone, it has to be incorporated in a DOCs file. DOCMAKER : The program used to create the DOCs DOCs file : The combination of the DOC-Interpreter and DOCs. This is in fact an EXE (executable) DOS program file, all texts and/or pictures are incorporated within this EXE file. You thus have a single program, which does not make use of any other files. DOCs (data) : The data part of a DOCs file. It consists of a list of all menu entries and the entries themselves. These entries can be either text, pictures (or both) or a program. The texts/pictures are crunched and encrypted. CRC : Cyclic Redundancy Check. This is a very simple but effective method to check if a block of bytes has got errors. It's a lot beter than parity checks or checksums. Internal file format : The way the DOCMAKER stores its information. The internal file format can change from version to version, the external file format should never change. P.S. The one exception is version 3.0 of the DOCMAKER, the external file format of the text files has changed due to the new features in the DOCMAKER. Version 3.0 text files are not compatible with previous versions. Future versions should be compatible with 3.0 though. External file format : The way the DOCMAKER expects the files to be when they are to be added to the DOCs file. Features. --------- DOCMAKER : - Easy to use UI (User Interface). - Support of standard ASCII files, or the more appropriate Text files (see later). - Support of graphics-files, available in two resolutions : 640*200 : CGA resolution 640*350 : EGA resolution All pictures are 2 colors. Or PCX Files. - The possibility to have small pictures within text. - Built-in crunching of all files (except programs) to be used with the DOC interpreter. - Built-in 32-Bit CRC checking. - Up to 76 texts and/or pictures per DOCs file. - Unlimited size of DOCs file (Whatever the size of the DOCs file, the DOC-Interpreter only needs about 256 Kb of free memory to run). - Making DOCs from scriptfiles. This allows you to test out different versions without repeatedly typing the same things. - Built In Virus Infection Checking (BIVIC (tm)) (for both DOCMAKER and DOC-Interpreter. You get following message displayed on screen : EXE file is corrupt. Check for Virus Infection. DOC-Interpreter : - Support for the major graphics boards (CGA, EGA, VGA, Hercules) - Support for following printers : - Epson FX 80 - Epson LQ 24 - HP DeskJet - HP LaserJet - NEC Pinwriter 2200 - IBM Graphics printer Most printers support/emulate one or more of these printers. - Supports LPT1 through LPT4. - Easy to use (graphical) user interface - Built in 32-Bit CRC checking. - BIVIC (tm). - Small (Only 21Kb in size, needs 256Kb when running, 40Kb resident when running a program set up in the menu). Why use the DOCMAKER. --------------------- You've got a small users group and want to release a club magazine every month or so. You could just distribute a set of textfiles and/or picture files hooked together in a batchfile (or something like that). With the major problem being : One file missing could screw up the entire setup. Suppose you have a few text and/or graphics files you want to show to other people (Let's say the solution to some very hard adventure). Because you have spent several hours playing the adventure and some more hours typing the text/drawing the pictures, you want everybody to know you made the text/pictures, so you write down your name in every one of those files. You copy the files to a disk and give it to your friends or you make an archive and upload it to a BBS. Several weeks later 'X' (could be a computer group/club or an individual) distributes the solution to the same adventure. Well in fact he used your solution and changed your name into his. The solution is simple, the DOCMAKER. Because all files stored in the DOC interpreter (Created by the DOCMAKER) are encrypted AND crunched you have a first level of security that your name won't be changed and that the end-user has got *ALL* the files. It also takes considerably less disk space since all files are crunched and decrunched at run-time. P.S.I. does NOT provide ANYBODY with the internal file formats or methods of decrypting and crunching/decrunching. Therefor, nobody will be able to decrunch and decrypt the files to their original format. Of course it will still be possible for everyone to retype your text or redraw your picture, but there's no EASY/FAST way. There are other ways to show texts and pictures (GRASP for instance), but the DOCMAKER & DOC Interpreter have a lot more to offer for this particular kind of presentation. - Small : The DOC Interpreter is only 22Kb in size. - Fast : I've spent over 200 hours just on optimizing the code. (i.e. the graphics routines, crunching). - Built-in crunching/decrunching. - Built-in printer support for the most used printers. - Built-in 32-Bit CRC checking. - Point & shoot menu system (also in graphics mode). - Automatically makes best use of the features of your screen. - Up to 76 entries. --------------------------------------------------- - - - The DOCMAKER - - - --------------------------------------------------- After typing DOCMAKER at the DOS prompt you are presented with the main screen. The main screen is made up of four parts, the top part contains the program name, version number and copyright notice. The bottom part is currently empty and will be used to accept user entry. The middle left part is the menu. The middle right part is the info box and currently holds the P.S.I. logo. The DOCMAKER : MENU ------------------- The menu is a point & shoot menu system, The active selection is white on a blue background (reverse video for monochrome systems) The menu has following options : Create new DOCs file Activate an existing DOCs file Change Title Add to a DOCs file Create a DOCs file from script Quit DOCMAKER ! Throughout the DOCMAKER program, pressing the Escape key will either return you to the menu, or back up one step. Whenever you've made a mistake just press Escape. There is no 'undo' function however, and overwriting or adding to a file can not be undone, in that case, you'll have to start over. ! Whenever a question has to be answered with 'Yes' or 'No', the docmaker will display a box displaying a question. Just position the highlighted bar over the correct answer and press Enter. The question can not be stopped by pressing Escape. ! Whenever a file has to be specified (other than a DOCS file) you can either type the full name (and path), or just type a wildcard (ex. *.PCX). A file-pick list will be shown, just use the cursor keys to select the correct file. ! If the filename of a picture has 'PCX' as extension, it is assumed to be a standard PCX picture (as defined by ZSoft), and is processed as such. Other extensions are assumed to be raw data files. Create a new DOCs file. ----------------------- Make a new (empty) DOCs file. After you've created a DOCs file, you will be able to add texts/pictures. You will need to provide following info : 1) The name of the DOCs file. Do not provide a drive or path, also do not add an extension (.EXE will be added automatically). 2) The title of the DOCs file, this title will be displayed at the top of the menu in the DOCs file. The DOCMAKER will now create the DOCs file. This will take a few seconds. 3) The DOCMAKER now asks if you would like an intro page. Just choose 'Yes' or 'No'. If you chose 'Yes' you will need to provide the name of the intropage. ! An intropage is a 200 lines picture (see later), it will be displayed after you've selected the correct graphics and printer in the DOCs file. After pressing a key the menu is displayed. ! This intropage can not be printed. Activate an existing DOCs file. ------------------------------- If you have previously created a DOCs file, and want to add some more entries, you can do so by first activating that file. Just type the name of the DOCs file to activate. ! The active DOCs file is displayed on screen and all transactions are done on that file. You don't need to reactivate the same DOCs file over and over to add more entries. Change title ------------ If you made a mistake typing the title or want another title, just type the new title. Add to a DOCs file. ------------------- Adding entries to a DOCs file. 1) Choose the type of entry you want to add : (ASCII, Text, Program, 200 lines picture, 350 lines picture). 2) Provide the name of the file to add. 3) Type the name for the DOCs file menu. 4) If the type of entry is a 200 lines picture or a 350 lines picture, type the colour of pixels to print (see later) 5) When viewing ASCII or TEXT files, you can choose whether you want the user of the DOCs file to be able to write the entry to a file. This can be a very nice feature if you are distributing source codes or info forms the user needs to fill in. !! When enabling this feature, you can not include pictures in the text. Wait while the DOCs file is updated. Create a DOCs file from script. ------------------------------- Creating and adding entries to a DOCs file in one go. You will need to create a script file first with an editor. Type the name of the script file to use. Relax, have some coffee (or whatever) and wait while the DOCMAKER is processing the script file. Quit DOCMAKER. -------------- Guess what this one does ! --------------------------------------------------- - - - The DOC-Interpreter - - - --------------------------------------------------- The DOC-Interpreter really doesn't need much explaining. The DOC interpreter is a program which has some data (the DOCs file) attached to it. After you start the program (it works always, even if the program isn't in the current directory), a small menu is shown which requires you to select your machine equipment (Graphics display type, Printer & Printer port and pagelength). Once you have done that, just press <Enter> and the show begins. ! You may rename the program file at any time, this will not effect the running of the DOC-Interpreter. If there's an intro page it will be displayed, now the DOC- Interpreter waits until you press a key. It may be a good idea to put a short text somewhere in that picture telling the user to press a key. The menu system is simple, just use the cursor keys to select the correct entry then press enter, the DOCs file will be read and the file decrunched. ! A note about pagelength. Pagelength is a new feature of version 3.0. In previous versions, the creator of the DOCs file had to decide what pagelength to use. From V3.0 and on, the user can specify the number of lines his printer can print on one page, or even specify to print continuously on listing paper. --------------------------------------------------- - - - File Formats - - - --------------------------------------------------- ! A note on Paragraphs. From version 3.0 on the DOCMAKER supports variable pagelength (see above). To make this possible, the creator of the DOCs file has to specify where a pagebreak may occur. This may seem difficult, but it isn't, just keep reading. ASCII files. ------------ ASCII files will be treated as unformatted texts, a pagebreak can occur in between any two subsequent lines. ASCII files are the files you create with any editor, as long as the files abide by some rules they can be used directly in the DOCMAKER. 1) Maximum length of a line = 80 2) The lines must be separated with a "Carriage return/Line feed". Most editors do this fine, there are some editors though which work slightly different. There are some who use a "Line feed/Carriage return" or even just a "Carriage return" or a "Line feed". How to know ? Try it out, if it doesn't look right, your editor probably does it wrong. 3) No Control-characters (Characters below the space in the ASCII chart). Remember the 'TAB' character is a control character, you will need to 'de-tab' your ASCII file, this is a built in feature in most good editors. 4) Maximum size about 64Kb (depending on the contents of the text larger texts are possible). If you have texts which are longer, you'll have to split them and use two (or more) menu entries. Text files. ----------- Text files are ASCII files with paragraph formatting. First of all text files must obey the same rules of standard ASCII files. The creator of the file must specify where a pagebreak may occur. This makes it possible to keep blocks of text together on the same line, especially when it's a picture made up of the line drawing ASCII codes this can be very usefull. You tell the DOCMAKER where a pagebreak may occur by inserting a formatting character (default is '*') ON THE FIRST POSITION OF THE LINE. You *INSERT* a formatting character, not overwrite the first character on the line. The largest possible paragraph is 20 lines. So you have to add a formatting character at least every 20 lines. If a paragraph is larger, the DOCMAKER will return an error when processing the text. Here's an example : (The '|' signifies the left border of the screen). | This is an important | piece of text, these | five lines must be | printed on the same | page. |* |* !!!!!!!!!!!!!!!!!!!!!!!!! | !! Beware of the dog !! | !!!!!!!!!!!!!!!!!!!!!!!!! |* |* This is the start of a new paragraph. Note that in the 'Beware of the dog' box, the first line is shifted to the right by 1 position, just think of the formatting character as a not printed character in the DOC Interpreter. Commands : You can have several commands in your textfile. A command starts with the '@' as *FIRST* character on a line. The following commands are available : @! : Remark. The rest of the line is ignored. @FormatChar= : Overrides the standard formatting character of '*'. You must place the formatting character immediately after the = sign, no space in between. @Picture= : Allows you to add a picture in the text. You specify the filename and which picture lines to include in the text. Example : @Picture= MAZE.PCX,0,100 This will insert line 0 through line 100 in the text. You will have 101 lines of the picture in your text. A maximum of 160 lines can be inserted at one time, altough you can have multiple pictures with a total of over 160 lines. When printing the pictures from the DOC Interpreter, the black pixels are printed. The picture will look the same as on screen. The pictures are show on screen and printed as if they were 200-lines pictures. !! Do not include pictures if you want to have texts that can be writen to a file. !! There's one exception to the rule that the command must start on the first position of a line. That exception is a formatting character. A formatting character may precede the command on the same line. The only real use for this is with the picture command. You can start a new paragraph with a picture. The command to do this is, is : *@Picture=test.PCX,0,100 Replace the asterix with the chosen formating character. You WILL need to do this to have a picture of over 152 lines in size. Altough the other commands may have a formatting character, there's really no use to do so since a formatting character is not needed. Some tips for the text files, some of the rules also apply for ASCII files : - Set your editor for a left and a right margin. The texts look a lot better if they don't start at the leftmost edge of the paper. - Do not set your editor to proportional (aligned right margins). This is done by inserting spaces, it looks lousy, especially when printing on the LaserJet wich a non-courier font selected. - The best result for formatting is to put a formatting character on each line in between paragraphs, and the first line of each new paragraph. - Insert a formatting character as often as possible. This will allow for better use of the screen and/or paper. - Since the picture is displayed and printed at the same resolution of the 200-lines pictures, the picture may seem to be stretched some what if it was made at 350-lines resolution. To avoid this problem, draw the pictures in 200-lines (CGA) resolution. - Pictures consume a lot of memory, every line of picture takes 80 bytes. Having many big pictures can easily fill the 64Kb you have available for the text. - Do not stack up the pictures. The pictures are not meant to be used as a very big picture. If you have 2 or more pictures one after the other, it's not assured they will be printed one after the other, there may be a few lines in between. The pictures are meant to be used to enlighten some of the text, or to avoid using very rough pictures using the ASCII set. - Do not make any assumptions on the horizontal dimensions of the printed picture. You could make a picture and then use text arrows to point to a certain part of the picture. Since the picture is printed in somwhat different aspect ratios on different pictures, this will not work correctly. - Since the BLACK pixels are printed, the picture looks the same on screen as on paper. To avoid problems, draw you picture in black pixels on a white background. - The commands are as shown above, they are case insensitive (@picture= is exactly the same as @PICTURE=), but do be carefull with adding spaces. the command is @Picture=, not @Picture =. You can insert spaces in between parameters on the command lines though, exception is the @FormatChar= command, the formatting character must immediately follow the equal sign. - Do not add extra characters after the commands. They may work with the current version of the DOCMAKER, but they may not in new releases. Pictures. --------- The DOCMAKER uses two kinds of pictures, 200-lines (CGA resolution) and 350-lines (EGA resolution) pictures. Since both kinds of picture fill the entire screen the pixels in 200-lines pictures are somewhat taller. Both pictures have 640 pixels horizontally, and 200 or 350 pixels vertically For those who know a little Pascal. Here's the record definition of both types of pictures. TYPE Linedata = ARRAY [0..79] OF BYTE; Picture200 = ARRAY [0..199] OF Linedata; Picture350 = ARRAY [0..349] OF Linedata; As of this writing the DOCMAKER accepts two types of files as pictures. These are : - Raw data files which are in fact pictures with the pixel data for each line in sequence (as the record definition above dictates). Raw data files are the ones created with the old DOCMAKER utilities (after conversion). From DOCMAKER 3.0 and on however, the screen capture utilities have all been replaced with SAVEPCX, a screen capture utility which saves PCX files, since most drawing programs allow loading PCX files, I have decided to stop incorporating Raw datafiles. You can load the PCX files in your favourite drawing package and change the pictures before adding them to the DOCs file. - PCX Pictures. These are pictures which conform to the PCX picture file format as defined by ZSoft in their PC Paintbrush program. If the file extension is PCX, the DOCMAKER will assume it's a PCX picture and load the picture as such. Only pictures with 1 bit per pixel are allowed. These include, all monochrome (2 color) pictures and EGA/VGA 16 color pictures. 4 color CGA pictures have 2 bits per pixel and 256 color MCGA/VGA pictures have 8 bits per pixel and can not be used. If you're using a color PCX picture, only the high order plane is used (On 16 color pictures all pictures with the intensity bit set (bright colors assuming standard palette) are converted to white pixels, the rest are converted to black. If you don't quite understand, try loading some pictures into the DOCMAKER. I'm working on some more types of pictures, I strongly suggest using PCX pictures, they use less diskspace and are easier to modify (most drawing programs allow loading PCX pictures). If you have the older screen capture programs and convert program, you can still use the Raw datafiles. Some tips for the picture files (some rules also apply for pictures to be incorporated in texts) : - When adding pictures, the DOCMAKER asks if it has to print the Black or White pixels. When specifying black pixels, the picture will be printed as it is shown on screen. If you specify white pixels, the picture will be printed as a negative of what's shown on screen. Because some pictures (especially scanned ones) look very weird when inverted, I suggest always drawing the picture in black on a white background (Standard in DeluxePaint). - Printer ribbon is expensive and wears out fast when printing graphics. Don't use very large areas of black. Don't use a border around the picture. If you need black area's try using a pattern (gray level). - Since the pictures in the DOCMAKER will be Black/White, draw the pictures in Black/White. - If the picture is in color, try dithering (color to black/white) the picture. A good program is Graphics Workshop (It's ShareWare too, you can find it on BBS's under the name GWSnnn.ZIP, nnn is the version number). It does a great job at converting pictures from one format to another too. - Pictures can have a higher resolution than the size in the DOCMAKER. A 800x600 PCX picture can be used as a 350-line (or even a 200-line) picture. Keep in mind that only the top left window with specified (640x350 or 640x200) width and height is used, the rest is ignored. - Pictures can't be smaller than the target size. A picture with 320x200 resolution is not accepted. Keep in mind that the Hercules has a 720x348 resolution, and can not be used as a 350 lines picture. - The CGA-screen has only 200 lines, showing the 200-lines pictures is no problem, the 350-lines pictures is a bit harder. The DOC interpreter can show the 350-lines pictures on the CGA but with a significant loss of detail. 3 out of 7 lines aren't displayed. The pictures are printed as 350-lines pictures however and will come out fine. - The Hercules screen has 348 lines, to show 350-lines pictures the first and last lines aren't displayed. Again, when printing everything works fine. - To show 200-lines pictures on the EGA and Hercules, 3 out of 4 lines are doubled, the picture comes out fine on screen. This method makes sure the entire screen is used and that screen ratios aren't changed too much. Script Files. ------------- The DOCMAKER Scriptfile is a standard ASCII file which has the commands needed to create a DOCs file. Each line starting with a ';' is regarded as a remark and the rest of the line is ignored. Valid commands are : CREATE <filename> <title> INTROPICTURE <filename> ASCII <filename> <menutext> ASCIISAVE <filename> <menutext> TEXT <filename> <menutext> TEXTSAVE <filename> <menutext> PROGRAM <filename> <menutext> PICTURE200 <filename> <B/W> <menutext> PICTURE350 <filename> <B/W> <menutext> where <filename> The name of the file to add, on the create line. Do not add a file extension nor a pathname. <title> The title of the DOCs file. <menutext> The text to place in the menu. <B/W> Either the letter 'B' or 'W' (print White or Black pixels). CREATE : Create a new DOCSfile, this must be the first type of command in the Scriptfile. Remarks are allowed to prepend this command. INTROPICTURE : A 200 lines picture, to be used as intro picture. This line must follow the CREATE command no other commands in between, remarks are allowed. ASCII : An unformatted ASCII file. ASCIISAVE : An unformatted ASCII file. Which can be written to a file by the user of the DOCs file. TEXT : A formatted text file (see above). TEXTSAVE : A formatted text file (see above). Which can be written to a file by the user of the DOCs file. PROGRAM : the name of a program (if you supply a path it is stripped off so only the program name remains). PICTURE200 : A 200 lines picture. (see above) PICTURE350 : A 350 lines picture. (see above) !! DO NOT add a remark at the end of a command line, it will be regarded as part of the menutext. !! if the menutext is too long it will be clipped, there is no warning that the DOCMAKER has clipped of the text, you have to run the DOCs file to see if it has been clipped (the menutext can be up to 36 characters long). Scriptfile example. ; ************************* ; ** DOCMAKER Scriptfile ** ; ************************* CREATE PSI-MAG PSI Magazine 1 (C) 1992 by PSI ; We have an intro picture. INTROPICTURE PSIMAG.PCX TEXT GRAPHICS.TXT How to program the EGA/VGA Card ; 350 lines (EGA resolution) picture with drawings of ; Read & Write modes on the EGA/VGA PICTURE350 RWMODES.PCX B Read and Write mode picture PROGRAM SCROLLS.EXE EGA/VGA demo with 4 scrolls & Panning TEXT FREE-USR.TXT Win A USR Dual Standard Program incompatibilities. ---------------------------- - Central Point Anti-Virus Because of their built-in virus infection cheking (BIVIC) the DOCMaker and DOC Interpreter have some conflicts with the VSAFE program. If you remove the Program Protection flag (Alt-V, 8), everything's OK. Also the CPAV program allows to make any program self-checking. Do NOT add this on the DOCMAKER or the DOC Interpreter. - Virus Scanners Some scanners add extra bytes at the end of the programs that have been scanned. Next time the scanning is performed, only those bytes are checked resulting in faster execution of the scanning. I did not have a chance to test all scanners, but just in case, disable adding those bytes to both the DOCMAKER and the DOC Interpreter (other programs have no built-in virus checking). - Multi-Taskers Because of their nature of taking over a lot of system resources, the DOCMAKER and DOC Interpreter will not work under certain circumstances. OS/2 2.0 however gave no problem whatsoever. The main problem is when printing under a multitasker. Be sure no printing jobs are active when selecting to print an entry from the DOCs file. Thank you. ---------- I'd like to thank the following people who helped me making the DOCMAKER & DOC interpreter. - Peter Cloet, Marc De Witte, Karim Djillali, Jimmy King, Randal Neirynck : Thanks for Testing. - Official Version for testing the DOCMAKER since version 1.0 and helping to make the DOCMAKER popular, and for the many useful idea's. Special thanks to Tasmaniac of Official Version for giving some hints on making a beter product and designing some of the code. - Randal Neirynck : Thanks for lending your printer book (NEC P2200) and testing the NEC P2200 (Epson LQ24) driver. - Jimmy King : Thanks for lending your printer book (HP Deskjet Plus) and testing the HP driver. - Marc De Witte and Karim Djillali : Thanks for testing and re-testing the Epson FX80 driver. - Thanks to Borland for providing an outstanding Pascal Compiler and blazing fast assembler. Trademarks ---------- PSI, DOCMAKER, DOC Interpreter, DOCs file and BIVIC are trademarks of Prometheus Systems Incorporated. IBM, PC, XT, AT, Color Graphics Adapter, Enhanced Graphics Adapter, Video Graphics Array & PC-DOS are registered trademarks of International Business Machines. Hercules Graphics Card is either a trademark or a registered trademark of Hercules Inc. AdLib & AdLib Visual Composer are trademarks of AdLib Inc. SoundBlaster, SoundBlaster Pro are either trademarks or registered trademarks of Creative Labs Incorporated. MS-DOS and Microsoft are registered trademarks of Microsoft Corporation. Amiga is either a trademark or a registered trademark of Commodore Business Machines. Deluxe Paint is either trademark or a registered trademark of Electronic Arts. PC Paintbrush is a registered trademark of ZSoft Corporation. Epson is either a trademark or a registered trademark of Seiko Epson Corporation. NEC & Pinwriter are either trademarks or registered trademarks of Nippon Electronics Corporation. Hewlett Packard, DeskJet & LaserJet are either trademarks or registered trademarks of Hewlett Packard. Turbo Pascal & Turbo Assembler are registered trademarks of Borland International. Leisure Suit Larry is a trademark of Sierra On-Line Inc. Sierra is a registered trademark of Sierra On-Line Inc. Disclaimer ---------- The software, diskettes, and documentation are provided "AS IS". There is no warranty of merchantability, no warranty of fitness for a particular use, and no warranty of any kind, either expressed or implied regarding the software, diskettes, or documentation. Accordingly, the entire risk as to the use, results and performance of the software and documentation is assumed by you. In no event will Prometheus Systems Incorporated be liable to you or any one else for any consequential, special, or indirect damages resulting from possession, use, or malfunction of this product, including without limitation, damage to property and, to the extent permitted by law, damage for personal injury, even if Prometheus Systems Incorporated has been advised of such damages or loss. Some Countries (states) do no allow limitations on the duration of implied warranties and/or the exclusion or limitation of incidental or consequential damages, and thus the preceding limitation and/or exclusions and limitations may not apply to you. This warranty gives you specific legal rights, and you may have other rights depending on the laws in your country (state). You agree that the liability of Prometheus Systems Incorporated arising out of any kind of legal claim (whether in contract, tort, or otherwise) will not exceed the amount you originally paid for the use of this product.