                                
                                  
                           
                                       
                                  
  Ronk 1, slo 3                                         4 Prosinec 1993

    DA(M)NNEWS jsou (c) DANNET, Daniel Doekal, Praha, esk republika
    DA(M)NNEWS are (c) DANNET, Daniel Docekal, Prague, Czech Republik

     Bezplatn elektronick noviny a magazn Regionu 42 FidoNet st.
    FREE electronic newspaper magazine of Region 42 of Fidonet network.


       Vydvno nepravideln (velice), vydavatel 2:420/20.6@FidoNet.
         Published unregural (very), publisher 2:420/20.6@FidoNet.


                    |================================|


                                     Obsah

1.  FidoNet,Internet,Komunikace  ...........................................  1
    D'Bridge 1.51 technical information  ...................................  1
2.  St  .................................................................. 12
    Novell zamen otzky a odpovdi  ..................................... 12
3.  CLIPPER  ............................................................... 18
    Testing for dbCommit() debate  ......................................... 18
    WARPLINK, Clipper Linker  .............................................. 27
4.  Hardware  .............................................................. 30
    FUJITSU, Model M2611S/SA/SB nastaven  ................................. 30
    MICROPOLIS Model 1373A, nastaven  ..................................... 31
    Seagate ST 125N, parametry  ............................................ 32
5.  Software  .............................................................. 34
    TLIB verze 5 a MultiEdit  .............................................. 34
    Automatick tisk pchozch fax pomoc GCL  ........................... 35
6.  OS/2  .................................................................. 36
    Oekvan OS/2 knihy  .................................................. 36
    OS/2 Klub zaloen na PRODIGY  .......................................... 39
7.  SHAREWARE  ............................................................. 40
    SHAREWARE LIBRARY  ..................................................... 40
8.  Inzerce  ............................................................... 42
    VTDATA, notebooky  ..................................................... 42
9.  Legrace a legrcky  .................................................... 44
    Nkter ast zkratky a symboly  ....................................... 44
    Jako za starch as  .................................................. 45

                                   - - - - -
DA(m)N NEWS 1-03                   Str. 1                    4 Dec 1993


===============================================================================
                          FidoNet,Internet,Komunikace
===============================================================================


D'Bridge 1.51 Technical Information                            28 December 1992
-------------------------------------------------------------------------------


      1.0  SYSTEM FILES
      -----------------

      D'Bridge is a complex program that uses quite a few control, storage
      and history files to store system information.  This document lists
      these file structures so that programmers may access them in utility
      programs.

      Structures will be listed in the following sections, but here is a brief
      summary of all files used directly by D'Bridge:


      Filename          Description
      -------------------------------------------------------------------------

      AREAS.BBS         Requestable file descriptions
      AREAS.TXT         ECHOmail area name file (user-supplied)
      BADECHO     <dir> Fido-style bad/duplicate ECHOmail directory (default)
      BADPWD.TXT        Text file to send after bad password notice
      CALLER.INF        Function-request caller information file
      COMM.CFG          D'Bridge communication parameters
      COSTBASE.DB1      Costing data file
      COSTBASE.DB2      Costing index file
      COSTING.XDC       Automatically exported accounting/translation data
      DATA        <dir> Database files directory (default)
      DB.EXE            D'Bridge mailer (executable)
      DB-151.DOC    Installation instructions
      DB-AUS.TXT        Australian dealers / order form
      DB-EUR.TXT        European dealers / order form
      DB-IO.LOG         Communication log file (C:\DB-IO.LOG, if activated)
      DB-LIC.TXT        D'Bridge software license agreement
      DB-USA.TXT        American dealers / order form
      DB01.151    D'Bridge mailer task
      DB02.151    FTSC mailer list
      DB03.151    D'Bridge mailer overlay
      DB04.151    D'Bridge editor task
      DB05.151    D'Bridge editor overlay
      DBCONFIG.ZIP      Backup configuration archive (7 day history)
      DBEDIT.DRO        Memory "swap file" for DBEDIT
      DBEDIT.FND        Last search string for DBEDIT
      DBHELP.IDX        D'Bridge help index
      DBHELP.TXT        D'Bridge help file
      DBINS.CTL         Installation country/area code definition file
      DBNET.290         DBNET nodelist for support network (15 Oct 92 vsn)
      DBNL.AUT          D'Bridge automatic nodelist
      DBRIDGE.ADF       Local/ECHOmail area definition file
      DBRIDGE.AFF       AREAFIX request queue file
DA(m)N NEWS 1-03                   Str. 2                    4 Dec 1993


      DBRIDGE.AFQ       AREAFIX request queue file
      DBRIDGE.AUT       Automatic exported configuration
      DBRIDGE.CON       Keeps track of what systems were called during an event
      DBRIDGE.DL1       Inbound EMAIL history file
      DBRIDGE.DL2       Outbound EMAIL history file
      DBRIDGE.DL3       Received ECHOmail history file
      DBRIDGE.DL4       AREAFIX history file
      DBRIDGE.DRO       Memory "swap file" for DBMAILER
      DBRIDGE.DSI       System information file
      DBRIDGE.DUP       QuickBBS ECHOmail duplicate-prevention file
      DBRIDGE.EMW       ECHOmail waiting flag file
      DBRIDGE.ERR       Status-line error display text file
      DBRIDGE.FCN       Forced nodelist compile activation file
      DBRIDGE.FRS       File-request limit file  (Stores 24-hour limits)
      DBRIDGE.HIS       Outbound XMAIL control file (tracks filenames)
      DBRIDGE.INS       Installation pathname default file
      DBRIDGE.LOG       D'Bridge system log file (default)
      DBRIDGE.LRQ       QuickBBS lastread pointers (for DBEDIT)
      DBRIDGE.MAR       NETmail "mark/delete" pointers
      DBRIDGE.MEH       Mail-event queue progress file
      DBRIDGE.NMW       NETmail waiting flag file
      DBRIDGE.PRM       D'Bridge parameter file
      DBRIDGE.PTR       QuickBBS EMAIL pointer file
      DBRIDGE.R$$       Received files (internal control file)
      DBRIDGE.REE       AREAFIX rescan queue file
      DBRIDGE.REG       D'Bridge registration data
      DBRIDGE.RII       Automatic nodelist temporary file
      DBRIDGE.RSE       ECHOmail scan activation file
      DBRIDGE.RSN       NETmail scan activation file
      DBRIDGE.TCN       Test/compile nodelist activation file
      DBRIDGE.TRM       Terminal-mode parameter file
      DBRIDGE.UEH       UN-EVENT queue progress file
      DBRIDGE.UFM       Unpack/forward mail activation file
      DBRIDGE.XCF       ECHOmail cycle delay control file
      DBRIDGE.XMA       Outbound XMAIL control file (tracks outbound packets)
      DBRIDGE.WIS       Wisdom display control file
      DBUTIL.EXE        D'Bridge utilities (executable)
      DFB         <dir> D'Bridge FileBase directory (default)
      ECHOMAIL.CTL      ECHOmail scan control file
      FILEBASE.DB1      FILEBASE data file
      FILEBASE.DB2      FILEBASE index file
      FILES       <dir> Inbound files directory (default)
      FREQ.TXT          Text file to send after file-request report
      INBOUND.REQ       Inbound file-request (erased before each call)
      INTERCOM.LOG      Intercom conversation log
      LASTEMSI.DAT      Last EMSI data from remote system
      LASTREAD.DBR      D'Bridge/Fido-style lastread pointers (for DBEDIT)
      LASTREAD          SEAdog-style lastread pointers (for compatibility)
      LICENSE.REG       Registration data file
      MCFILES.LST       Modem control file (MCF) list
      MCFILES.ZIP       Modem control file archive
      MESSAGES    <dir> Fido-style NETmail directory (default)
      MSGHDR.BBS        QuickBBS message header file
      MSGIDX.BBS        QuickBBS message index file
      MSGINFO.BBS       QuickBBS message summary file
      MSGTOIDX.BBS      QuickBBS message-to index
DA(m)N NEWS 1-03                   Str. 3                    4 Dec 1993


      MSGTXT.BBS        QuickBBS message text file
      NODEBASE.DB1      NODELIST data file
      NODEBASE.DB2      NODELIST index file
      PACKETS     <dir> Temporary queue path (default)
      PCFILES.LST       Printer control file (PCF) list
      PCFILES.ZIP       Printer control file archive
      QUEUE       <dir> Queue directory (default)
      READ.ME           A message from the author
      RESTART     <dir> ZMODEM receive temporary directory
      SCRIPTS     <dir> Dialing script directory (default)
      TASKQ.DB1         Outbound queue data file
      TASKQ.DB2         Outbound queue index file
      THISCALL.TXT      Post-call activity report
      THISCOMM.TXT      Post-call modem register dump file
      USA-EAST.COS      United states accounting/translation data (default)

      2.0  PARAMETER FILE
      -------------------


      D'Bridge uses a text-file called DBRIDGE.PRM to store its parameters.
      The structure of this file will change in future versions, but this
      is the definition for version 1.51.  When using this chart, make sure
      that you understand that "Line" doesn't really mean the literal line
      of the text file, but the currently processed line.  Fields that have
      an asterisk (*) in the in "Column" field are called LISTS.

      LISTS are fields that contain any number of lines.  The first line of
      a list contains the number of lines in the list.  If a zero is found,
      the list is empty.



      Field                  Line/Column   Description
      -------------------------------------------------------------------------

      PARAMETER FILE VERSION    1   1      Current software version
      NETWORK MAIL STORAGE      2   1      NETmail storage method: F, T or Q
      DBMAILER OVERLAY EMS      2   2      Copy DBMAILER.OVR to EMS?  1 or 0
      DBEDIT OVERLAY EMS        2   3      Copy DBEDIT.OVR to EMS? 1 or 0
      DBMAILER PROGRAM SIZE     2   4      Total memory (in K)
      DBMAILER WORKRAM SIZE     2  11      WorkRAM (in K)
      ECHOMAIL RAM SIZE         2  18      Required amount computer by D'bridge
      NETWORK MAIL DIRECTORY    3   1      Fido-style NETmail directory path
      INBOUND FILES DIRECTORY   4   1      Inbound files directory path
      PACKET DIRECTORY          5   1      Temporary packet directory path
      QUEUE DIRECTORY           6   1      Disk-based queue directory path
      SCRIPT DIRECTORY          7   1      Script file directory path
      BADECHO DIRECTORY         8   1      BADECHO directory path (Fido-style)
      NEWECHO DIRECTORY         9   1      New ECHOmail base directory path
      DFB DIRECTORY            10   1      D'Bridge FileBase directory path
      QUICKBBS DIRECTORY       11   1      QuickBBS directory path
      DOWNLOAD DIRECTORY       12   1      Terminal download directory path
      OUTBOUND MAIL ARCHIVE    13   1      Outbound NETmail archive filename
      NETWORK MAIL ARCHIVE     14   1      NETmail archive filename
      PRIMARY EMAIL ADDRESS    15   1      Primary system address
DA(m)N NEWS 1-03                   Str. 4                    4 Dec 1993


      SYSTEM NAME              16   1      Primary system name
      OPERATOR NAME            17   1      Primary operator name
      DATA PHONE NUMBER        18   1      System telephone number (1-nnn-...)
      SYSTEM FLAGS             19   1      Nodelist flags defined for system
      SYSTEM LOG LEVEL         20   1      0=None, 1=Terse, 2=Verbose, 3=Debug
      LOG DAYS                 20   8      Not used at this time
      HISTORY DAYS             20  15      Days history to keep in DL? files
      FAKE POINTNET            20  36      Fake pointnet address (NET number)
      NETMAIL PURGE            20  43      Days/messages for purge of NETmail
      NETMAIL AREA NUMBER      20  50      QuickBBS NETmail area number
      AREAFIX DAYS             20  57      Areafix cycle timeout days
      XMAIL CYCLE DELAY        20  64      XMAIL processing interval minutes
      ALIAS ADDRESSES          21   *      Alias EMAIL address list
      BACKGROUND COLORS        22   1      Screen/text/brite/highlite/border
      LOG WINDOW COLORS        23   1      "
      ACTIVITY WINDOW COLORS   24   1      "
      QUEUE WINDOW COLORS      25   1      "
      SCHEDULE WINDOW COLORS   26   1      "
      COMMAND WINDOW COLORS    27   1      "
      SPARE WINDOW COLORS      28   1      "
      SPARE WINDOW COLORS      29   1      "
      MODEM PORT 1             30   1      Modem: Port/Address/IRQ/MCF
      MODEM PORT 2             31   1      "
      MODEM PORT 3             32   1      "
      PRINTER PORT             33   1      Printer device/filename
      PRINTER CONTROL FILE     34   1      PCF name
      ANSWERING METHOD         35   1      Hard/Soft/RingMaster/Modem/Disabled
      LINE ASSIGNMENT 1        35   2      1/2/3/Voice
      LINE ASSIGNMENT 2        35   3      "
      LINE ASSIGNMENT 3        35   4      "
      COSTGUARD TIME           35   5      CostGuard time minutes
      COSTGUARD COST           35  15      Costguard cost cents
      AUTO-INIT TIME           35  25      Automatic modem init time minutes
      MAX RINGS                35  35      Maximum rings allowed while dialing
      COLLISION DETECT         35  45      S=ON, 0=OFF
      DIMESAVER                35  46      1=ON, 0=OFF
      BUSY WHEN OFFLINE        35  47      1=YES, 0=NO
      SYSTEM CITY              36   1      City or location of system
      LOG FILENAME             37   1      System log filename
      ABOUT FILENAME           38   1      File-request "ABOUT" filename
      FILES FILENAME           39   1      File-request "FILES" filename
      CONFIG PASSWORD          40   1      Configuration password (XOR 97h)
      POINTLIST                41   1      Pointlist filename
      ADDITIONAL USER FILE     42   1      Additional user filename
      DEFAULT ROUTING          43   1      Direct/Hub/None
      TRANSLATION TABLE 1/14   44   1      Displayed/Stored/Displayed/Stored
      TRANSLATION TABLE 2/15   45   1      "
      TRANSLATION TABLE 3/16   46   1      "
      TRANSLATION TABLE 4/17   47   1      "
      TRANSLATION TABLE 5/18   48   1      "
      TRANSLATION TABLE 6/19   49   1      "
      TRANSLATION TABLE 7/20   50   1      "
      TRANSLATION TABLE 8/21   51   1      "
      TRANSLATION TABLE 9/22   52   1      "
      TRANSLATION TABLE 10/23  53   1      Displayed/Stored/Displayed/Stored
      TRANSLATION TABLE 11/24  54   1      "
DA(m)N NEWS 1-03                   Str. 5                    4 Dec 1993


      TRANSLATION TABLE 12/25  55   1      "
      TRANSLATION TABLE 13/26  56   1      "
      KEYBOARD MACRO ALT-F1    57   *      Editor keyboard macro
      KEYBOARD MACRO ALT-F2    58   *      "
      KEYBOARD MACRO ALT-F3    59   *      "
      KEYBOARD MACRO ALT-F4    60   *      "
      KEYBOARD MACRO ALT-F5    61   *      "
      KEYBOARD MACRO ALT-F6    62   *      "
      KEYBOARD MACRO ALT-F7    63   *      "
      KEYBOARD MACRO ALT-F8    64   *      "
      KEYBOARD MACRO ALT-F9    65   *      "
      KEYBOARD MACRO ALT-F10   66   *      "
      KEYBOARD MACRO CTL-F1    67   *      "
      KEYBOARD MACRO CTL-F2    68   *      "
      KEYBOARD MACRO CTL-F3    69   *      "
      KEYBOARD MACRO CTL-F4    70   *      "
      KEYBOARD MACRO CTL-F5    71   *      "
      KEYBOARD MACRO CTL-F6    72   *      "
      KEYBOARD MACRO CTL-F7    73   *      "
      KEYBOARD MACRO CTL-F8    74   *      "
      KEYBOARD MACRO CTL-F9    75   *      "
      KEYBOARD MACRO CTL-F10   76   *      "
      SESSION PASSWORDS        77   *      Session password list
      AREAFIX INFORMATION      78   *      AREAFIX information list
      USERNAMES                79   *      DBEDIT username list
      ADDRESS SYNONYMS         80   *      Synonym definition list
      FILE-REQUEST PATHS       81   *      File-request directory list
      MAGIC FILENAMES          82   *      MAGIC request filename list
      PHONE NUMBER OVERRIDES   83   *      Phone number override list
      FLAG OVERRIDES           84   *      Flag override list
      ST LOUIS NODELISTS       85   *      St. Louis format nodelist list
      PRIVATE NODELISTS        86   *      Private nodelist list
      DISPLAY TIMEOUT          87   1      Blankout timer minutes
      MAX XMAIL FILE SIZE      87  15      Not used at this time
      MIN BBS BAUD RATE        87  29      Minimum speed for BBS calls
      MAX PACKET SIZE          87  43      Maximum size of XMAIL packets
      CLOCK WARNING THRESHOLD  87  50      Clock warnings minimum minutes
      FREQ TIME LIMIT          87  64      File-request time limit
      FREQ SIZE LIMIT          87  71      File-request size limit
      FREQ FILE LIMIT          87  78      File-request file count limit
      HUMAN CALLER TIMEOUT     87  85      Timeout before passing to BBS
      FREQ MINIMUM BAUD        87  92      Minimum baud rate for file-request
      FAX TONE DIALING         88   1      Not used at this time
      FAX RECEIVE ALLOWED      88   2      "
      FAX INSTALLED            88   3      "
      FAX ANSWER OFFLINE       88   4      "
      FAX DEFAULT RESOLUTION   88   5      "
      FAX DEFAULT FONT         88   6      "
      FAX BOARD TYPE           88   7      "
      FAX RINGS TO ANSWER      88   9      "
      FAX SOFTWARE DIRECTORY   89   1      "
      FAX ID                   90   1      "
      BBS SOFTWARE INSTALLED   91   1      1=YES, 0=NO
      KILL NULL MESSAGES       91   2      "
      ALARMS ACTIVE            91   3      "
      EDITOR SCAN NETMAIL      91   4      "
DA(m)N NEWS 1-03                   Str. 6                    4 Dec 1993


      CREATE USERNAME INDEX    91   5      "
      USE ZONEGATES            91   6      "
      EDITOR SOUND EFFECTS     91   7      "
      REJECT UNAUTH. MAIL      91   8      "
      RENAME UNAUTH. FILES     91   9      "
      TOUCH-TONE DIALING       91  10      "
      DEFAULT PRIVATE          91  11      "
      DEFAULT KILL-SENT        91  12      "
      DEFAULT CRASH            91  13      "
      EDITOR EXEC METHOD       91  14      Not used at this time
      SNOW SUPPRESSION         91  15      1=Enabled, 0=Disabled
      TOP SECRET               91  16      Reserved for D'Bridge security
      DISPLAY TIME DATA        91  17      1=Yes, 0=No
      RING SIGNAL              91  18      "
      ALLOW UNLISTED NODES     91  20      "
      ALLOW UNLISTED FREQS     91  21      "
      ENFORCE LIMIT OVERNIGHT  91  22      "
      CHECK LIMITS BEFORE      91  23      "
      INBOUND MAIL HANDLING    91  24      Automatic/Manual/External/Disabled
      HANG-UP ON VIOLATION     91  25      1=Yes, 0=No
      DEFAULT INSERT           91  26      "
      DEFAULT COMPRESSION FMT  91  27      0-6
      RENAME INCOMING FILES    91  29      1=Yes, 0=No
      KILL IN-TRANSIT MAIL     91  30      "
      DISPLAY QUEUE            91  34      "
      DEFAULT IMMEDIATE        91  35      "
      DEFAULT HOLD             91  36      "
      DEFAULT ARCHIVE-SENT     91  37      "
      DEFAULT XMAIL            91  38      "
      DEFAULT INTL ADDRESSING  91  39      "
      EDITOR SCAN ECHOMAIL     91  40      "
      BBS SCAB ECHOMAIL        91  41      "
      AUTO-ADD ECHOMAIL AREAS  91  42      Fido/QuickBBS/None
      LEAVE SEENBYS            91  43      1=Yes, 0=No
      ACCEPT AREAFIX REQUESTS  91  44      "
      KEEP DUPLICATE MESSAGES  91  46      "
      AUTOMATIC ALIAS          91  47      "
      43-50 LINE MODE          91  49      1=43/50-line mode, 0=25-line mode
      LIMIT NO-COST CALLS      91  50      1=Yes, 0=No
      BLANKOUT GRAPHICS        91  51      "
      IN-TRANSIT RESCAN        91  52      "
      SECURED ECHOMAIL ONLY    91  54      "
      QUOTE SEENBYS            91  55      "
      REMOVE EMPTY PASSTHRUS   91  56      "
      OBSERVE DAYLIGHT TIME    91  59      "
      ADJUST MAIL EVENTS       91  60      Not used at time time
      ADJUST TIMESYNC EVENTS   91  61      "
      ADJUST EXTERNAL EVENTS   91  62      "
      TRANSFER SPEED           91  65      CPS/BPS/KPS
      NODELIST COMPILE MODE    91  66      Midnight/Startup/Never
      THIS LINE BLANK          92   1      Not used at this time
      OUTBOUND GATEWAY         93   1      Outbound gateway address
      COUNTRY CODE             94   1      Country code
      NO-COST PREFIX           95   1      No-cost dialing prefix
      DOMESTIC PREFIX          96   1      Domestic dialing prefix
      INTERNATIONAL PREFIX     97   1      International dialing prefix
DA(m)N NEWS 1-03                   Str. 7                    4 Dec 1993


      PARM FILE SYNC FLAG      98   1      Used for control purposes "DBedit"
      EXTERNAL EDITOR PATH     99   1      Path for external editor
      EMAIL ONLY TEXT         100   1      Text for EMAIL-only operation
      PRESS ESC TEXT          101   1      Text for "Press ESC twice to load"
      LOADING BBS TEXT        102   1      Text displayed before loading BBS
      LOADING BBS FILENAME    103   1      File to display before loading BBS
      PRIMARY SUPPORT PHONE   104   1      Not used at this time
      ZIP COMPRESS COMMAND    105   1      DOS command
      LHA COMPRESS COMMAND    106   1      "
      ARJ COMPRESS COMMAND    107   1      "
      PAK COMPRESS COMMAND    108   1      "
      ARC COMPRESS COMMAND    109   1      "
      ZOO COMPRESS COMMAND    110   1      "
      ZIP DECOMPRESS COMMAND  111   1      "
      LHA DECOMPRESS COMMAND  112   1      "
      ARJ DECOMPRESS COMMAND  113   1      "
      PAK DECOMPRESS COMMAND  114   1      "
      ARC DECOMPRESS COMMAND  115   1      "
      ZOO DECOMPRESS COMMAND  116   1      "
      TOO SLOW FILENAME       117   1      File sent when BBS caller too slow
      AFTER-HOURS FILENAME    118   1      File sent outside defined BBS hours
      BBS FROM                119   1      HHMM starting BBS operation
      BBS TO                  119   5      HHMM ending BBS operation
      ALARM FROM              119   9      HHMM starting alarm operation
      ALARM TO                119  13      HHMM ending alarm operation
      PACKET PRE-PROCESSOR    120   1      Packet pre-processing command
      EXCLUDE NETS            121   *      Nodelist exluded ZONES:NETS
      NET TRANSLATION         122   *      ZONE:NET translations
      SPECIAL ALARMS          123   *      Special alarms for inbound calls
      KEY COMMANDS F1         124   *      Not used at this time
      KEY COMMANDS F2         125   *      DOS commands
      KEY COMMANDS F3         126   *      "
      KEY COMMANDS F4         127   *      "
      KEY COMMANDS F5         128   *      "
      KEY COMMANDS F6         129   *      "
      KEY COMMANDS F7         130   *      "
      KEY COMMANDS F8         131   *      "
      KEY COMMANDS F9         132   *      "
      KEY COMMANDS F10        133   *      "
      KEY COMMANDS ALT-F1     134   *      "
      KEY COMMANDS ALT-F2     135   *      "
      KEY COMMANDS ALT-F3     136   *      "
      KEY COMMANDS ALT-F4     137   *      "
      KEY COMMANDS ALT-F5     138   *      "
      KEY COMMANDS ALT-F6     139   *      "
      KEY COMMANDS ALT-F7     140   *      "
      KEY COMMANDS ALT-F8     141   *      "
      KEY COMMANDS ALT-F9     142   *      "
      KEY COMMANDS ALT-F10    143   *      "
      BBS DOS COMMANDS        144   *      BBS loading DOS commands
      EDITOR DOS COMMANDS     145   *      DOS commands for loading editor
      CLOCK DATA FOR          146   *      Filter for clock data aquisition
      FUNCTION REQUEST        147   *      Function request list
      EXTERNAL RECEIVERS      148   *      External receiver list
      EXTERNAL GATEWAYS       149   *      External gateway list
      ISOLATE DATA FROM       151   *      Not used at this time
DA(m)N NEWS 1-03                   Str. 8                    4 Dec 1993


      ALT COMPRESSION FMTS    151   *      Alternate compression formats
      CLOCKSYNC SYSTEM        152   1      Default ClockSync system
      AUTOMATIC SYNC SYSTEM   153   1      Automatic ClockSync system
      SET CLOCK COMMAND       154   1      DOS command to set XT/Network clock
      OUTBOUND HISTORY FILE   155   1      Outbound history filename
      INBOUND HISTORY FILE    156   1      Inbound history filename
      AREAFIX HISTORY FILE    157   1      AREAFIX history filename
      ECHOMAIL HISTORY FILE   158   1      ECHOmail history filename
      UNLISTED REQUEST HUB    159   1      Blind AREAFIX request hub
      CALL ALARM              160   1      ANSI-music for call alarm
      FLAG DIAL               161   *      Dial strings for specific flags
      SPECIFIC DIAL           162   *      Dial strings for specific systems
      FIDONET FOR             163   *      Filter for Fidonet protocol
      WAZOO FOR               164   *      Filter for WaZOO/ZEDZAP protocol
      FORCED PRIORITIES       165   *      System-specific forced priorities
      FAKE POINTNET FOR       166   *      List of points using fake pointnet
      AUTOMATIC PWD FOR       167   *      Filter for automatic passwords
      ALLOW PWD REQ FROM      168   *      Filter for password requests
      C: DRIVE                169   1      Operation/BBS/Unpack-forward
      D: DRIVE                170   1      "
      E: DRIVE                171   1      "
      F: DRIVE                172   1      "
      G: DRIVE                173   1      "
      H: DRIVE                174   1      "
      STARTING BLOCK SIZE     175   1      300/1200/2400/4800/9600/14400
      MAXIMUM BLOCK SIZE      176   1      "
      RECOVERY BLOCK SIZE     177   1      "
      BLOCK STEP RATE         178   1      "
      DIRECT ZMODEM           179   1      "
      DAYLIGHT TIME STARTS    180   1      YYMMDD starting daylight time
      DAYLIGHT TIME ENDS      180   8      YYMMDD ending daylight time
      DAYLIGHT TIME CHANGES   181   1      HHMM time of daylight time change
      LST ABBREVIATION        182   1      Abbreviation for Standard Time
      LST NAME                182   8      Name of Standard Time
      LDT ABBREVIATION        183   1      Abbreviation for Daylight Time
      LDT NAME                183   8      Name of Daylight Time
      LOG HIGHLIGHT KEYWORDS  184   *      Log viewer highlight keywords
      NUMBER OF EVENTS        185   1      Number of events (excluding UNEVENT)
      EVENT 0                 186   **     Event records as defined below.
      .                       .
      .                       .
      EVENT N


      ** The following fields are contained in each event record:

      Field                  Line/Column   Description
      -------------------------------------------------------------------------
      EVENT TAG/START/END       1   1      Event tag, starting and ending times
      ACTIVE SUNDAY             2   1      1=Active, 0=Inactive
      ACTIVE MONDAY             2   2      "
      ACTIVE TUESDAY            2   3      "
      ACTIVE WEDNESDAY          2   4      "
      ACTIVE THURSDAY           2   5      "
      ACTIVE FRIDAY             2   6      "
      ACTIVE SATURDAY           2   7      "
DA(m)N NEWS 1-03                   Str. 9                    4 Dec 1993


      EVENT CRITICAL            2   8      1=Yes, 0=No
      EVENT ENABLED             2   9      "
      HOST-ROUTE PRIVATES       2  10      "
      EVENT TYPE                2  11      External/ClockSync/DOS/Mail


        IF EXTERNAL EVENT

      Field                  Line/Column   Description
      -------------------------------------------------------------------------

      ERRORLEVEL                3   1      Errorlevel to use for exit


        IF DOS EVENT

      Field                  Line/Column   Description
      -------------------------------------------------------------------------
      DOS COMMANDS              3   *      DOS commands to execute


        IF CLOCKSYNC EVENT

      Field                  Line/Column   Description
      -------------------------------------------------------------------------
      CLOCKSYNC TIMEBASE        3   1      Address of ClockSync TimeBase
      MAX CLOCKSYNC TRIES       4   1      Maximum tries for ClockSync event
      MAX CLOCKSYNC FAILURES    5   1      Maximum failures for ClockSync event


        IF MAIL EVENT

      Field                  Line/Column   Description
      -------------------------------------------------------------------------
      MINIMUM IDLE TIME         3   1      Minimum seconds idle before call
      MAXIMUM IDLE TIME         3   8      Maximum seconds idle before call
      TRIES ALLOWED             3  15      Maximum tries allowed per entry
      SESSIONS ALLOWED          3  22      Maximum sessions allowed per entry
      FAILURES ALLOWED          3  29      Maximum failures allowed per entry
      EVENT DYNAMIC             4   1      1=Yes, 0=No
      PROCESS FILE-REQUESTS     4   2      "
      ACCEPT HUMAN CALLERS      4   3      "
      CM FLAG ACTION            4   4      CM/Non-CM/Both
      ACCEPT EMAIL CALLS        4   5      1=Yes, 0=No
      ACCEPT FAX CALLS          4   6      Not used at this time
      SCAN ECHOMAIL             4   7      1=Yes, 0=No
      ALLOW XMAIL               4   8      "
      PRIORITIES ALLOWED        4   9      NCI
      EVENT ALIAS               5   1      Alias address for event
      PACKETS FOR               6   *      Filter controlling who gets mail
      HOLD FOR                  7   *      Filter for holding mail traffic
      POLL                      8   *      List of systems to poll this event
      PICKUP FROM               9   *      Filter controlling mail pickup
      ALLOW PICKUP FROM        10   *      Filter controlling remote pickup
      ROUTE TO                 11   *      Filter for routing
      FORWARD FOR              12   *      Filter controlling mail forwarding
DA(m)N NEWS 1-03                   Str. 10                   4 Dec 1993


      FORWARD TO               13   *      "
      FAX TO                   14   *      Not used at this time
      INTL FAX FWD FOR         15   *      "
      LOCAL FAX FWD FOR        16   *      "
      FILE FORWARDING FOR      17   *      Filter controlling file forwarding
      FORWARD FILES TO         18   *      "
      FILE ROUTING FOR         19   *      Filter controlling file routing
      DOS COMMANDS             20   *      DOS commands after mail received


      DBRIDGE.PRM must begin and end the same way it began.  Specifically, the
      first and last lines should read:

      Single-line 1.51 / 15 October '92

      If it does not, then you cannot assume that this information is correct.
      This document will be revised as D'Bridge does.  This data is provided
      for your information only.  Do not count on it to remain stable through
      future releases.  This is changed even during the beta cycle; only the
      first 20 fields will never be changed.

      DBRIDGE.AUT is a more stable, but not as timely source of information.
      The import format is easier to read because it is keyword, not position
      sensitive.  Refer to the following section for keyword information.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 11                   4 Dec 1993


Picard: "Captain's Log, Stardate 43539.1.  We have moved into orbit around
  Bre'el IV.  With the assistance of the planet's Emergency Control Center,
  we're investigating a catastrophic threat to the population, from a
  descending asteroidal moon."
--"Deja Q", Stardate 43539.1

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 12                   4 Dec 1993


===============================================================================
                                     St
===============================================================================


Top Issue from June 1992

Q:      How can I make a backup of the files Q_0005.SYS and Q_0005.SRV
        located in my SYS:SYSTEM\05000005.QDR directory?

A:      These files belong to the Novell Queue Management Services and are
        kept open by the system.  They cannot be backed up.

Q:      After installing the NetWare Workstation Kit for DOS/Windows,
        what should  I do if an error occurs stating that Windows 3.1
        could not find NETWARE.DLL?

A:      Under certain conditions, NETWARE.DR_  does not get "expanded"
        (decompressed) properly during installation.  Run the Expand
        utility against this file to decompress NETWARE.DRV.
        It should be 125,712 bytes.  (There is no such file as
        NETWARE.DLL in this kit.)
        Include the statement "Network.drv=NetWare.drv" in the [Boot]
        section of the WIN.INI file.

Q:      I tried deleting some print jobs from the queue with the Q and P
        commands on my NetWare v3.11 file server console, without any luck.
        Does v3.11 support the Q and P commands from the console?

A:      The Q and P commands are not supported on the file server with
        NetWare 3.11.  Use the PSC command from a workstation or use
        PCONSOLE.  (Print Server Information option.)

Q:  How can I disable the Watchdog feature of NetWare v3.11?

A:      Watchdog packets cannot be disabled or turned off, but you can
        increase three SET parameters to their maximum limits.
        This allows for a total of approximately 17 hours before the
        connection is cleared. In the AUTOEXEC.NCF (or at the console
        prompt) type:

    SET Number of Watchdog Packets=100
    SET Delay Between Watchdog Packets=626
    SET Delay Before First Watchdog Packet=1252

    The maximum limits are:
                Number of Watchdog Packets:  100
                Delay Between Watchdog Packets:  10 minutes 26.2 seconds
                Delay Before First Watchdog Packet:  20 minutes 52.3 seconds.

Q:      I cannot run Windows v3.1 in the 386 Enhanced Mode.  Do you
        have any ideas for troubleshooting this problem?

A:      Windows v3.1 provides several startup switches that can be useful
        in troubleshooting when Windows does not start correctly.
        (Type WIN /? for a complete list of startup switches.)
DA(m)N NEWS 1-03                   Str. 13                   4 Dec 1993


    Try the following 3 methods of loading Windows:

1.  WIN /d:x

        The /d:x switch excludes the Upper Memory Blocks (UMB) area from
        the range of memory that Windows scans to find unused address
        space. Typically this area is A000-FFFF.  The search that Windows
        performs can conflict with network adapters that are using the
        same memory area.  If Windows loads successfully in 386 Enhanced
        Mode when you use the /d:x switch, add the following setting to
        the [386Enh] section of the SYSTEM.INI file:

    [386Enh]
    EMMExclude=<paragraph-range>

        Replace <paragraph-range> with the range of memory that is being
        used by a network adapter or other devices.  The range must be
        between A000 and EFFF.  The starting value is rounded down and
        the ending value is rounded up to a multiple of 16K.

        For example, you could set EMMExclude=C800-CFFF to prevent
        Windows from scanning the addresses C800:0000 through CFFF:000F.
        To exclude more than one range, use more than one EMMExclude line.
        Do not leave the range set to A000-FFFF.  This hampers system
        performance.

2.  WIN /d:v

        The /d:v switch specifies that the ROM routine will handle
        interrupts from the hard disk controller.  If Windows loads
        successfully in 386 Enhanced Mode when you use the /d:v switch,
        add the following setting to the [386Enh] section of the
        SYSTEM.INI file:

    [386Enh]
    VirtualHDIRQ=FALSE

3.  WIN /d:s

        The /d:s switch specifies that Windows should not use ROM address
        space between F000:0000 and 1 MB for a break point. If Windows
        loads successfully in 386 Enhanced Mode when you use the /d:s switch,
        add the following setting to the [386Enh] section of the SYSTEM.INI
        file:

    [386Enh]
    SystemROMBreakPoint=FALSE

Q:  Can you share modems with DataClub?

A:  No.

Q:      Can a Macintosh on a DataClub network access printers that are
        attached directly to another Mac on the same DataClub network?

A:  Yes
DA(m)N NEWS 1-03                   Str. 14                   4 Dec 1993


Q:      Can two DataClub users simultaneously access the same file or
        application if it is in the DataClub folder?

A:  No.

Q:  Can you run Packet burst with NetWare v3.1?

A:  No, you must have a v3.11 server to run packet burst.

Q:      I am running PBURST.NLM on my NetWare v3.11 server.
        How can you tell if packet burst is working?

A:      At the file server console, type "set enable packet burst
        statistics screen = on". Toggle into the screen. If packet
        burst is working you should see zeros.

Q:  Does Desqview work with NW Lite?

 A: It works in client mode only.

Q:      Do you need to purchase LAN Support Program from IBM for
        NetWare to run properly?

A:      You don't need it for NetWare but some applications may require
        it (especially if they are written by IBM).  The LAN Support
        Package allows applications to speak directly to the LAN cards.

Q:  Will a single copy of NW MHS service more than one file server?

 A:     The NetWare MHS license agreement allows for a single copy of
        NetWare MHS to be run on a single NetWare file server.  If you
        want messaging services for more than a single server, you must
        purchase additional copies of NetWare MHS.  You cannot legally
        install the same copy of NetWare MHS on multiple file servers.

Q:  Does Lan Workplace for DOS support DDE?

A:      Lan Workplace for DOS takes advantage of DDE internally.
        However, there are no DDE capabilities available to end users
        at this time.

    DR DOS 6.0 Q&A

Q:      Where can I get general and technical information on DR DOS 6.0
        and Multi-user DOS issues?

A:      Technical and general information for DR DOS 6.0 and Multi-user
        DOS can be found on our BBS and Faxback systems.  The Novell
        Desktop Faxback and BBS phone numbers are 1-408-649-2344 and
        1-408-649-3443, respectively.

        The BBS supports X, Y, Z, and Kermit modem protocols.  ZMODEM
        is the best protocol to use because it lets you recover if the
        download gets aborted.  Use the following parameters:

                Parity:         NO
DA(m)N NEWS 1-03                   Str. 15                   4 Dec 1993


                Stopbits:       1
                Databits:       8

        The system will connect for 30-45 minutes (depending on the
        download) to allow other users a chance to log on.

        The Faxback phone system is a completely automated system that
        prompts you to enter information through a touch-tone phone.
        You can request up to four documents per call.  This system is
        an information system only.  It does not receive faxes.
        Customers who need to submit a detailed Fax may send it to DSG
        support at 408-649-8209.

        For both the BBS and Faxback systems, you should start by
        obtaining document 1000, the master index of all tech tips
        available on the system.  Document 1000 is updated every time
        a documents is added or modified.  You can periodically request
        document 1000 to keep abreast of new technical tips.

Q:      The DR DOS diskettes I bought don't fit the A: floppy drive
        of my computer.  How can I install from the B: drive?

A:      DR DOS needs to be loaded at boot-up time to install its own
        system files into memory.  These system files are necessary for
        correct installation.  Most computers are set up in a way to
        allow these system files to be installed only from the A: floppy
        drive.

        Most dealers provide the proper size diskettes with each DR DOS
        package sold.  DR DOS packages are clearly marked on the front
        of the box with the size of diskettes the package contains.  You
        can get a  replacement diskette set in a different size through
        Novell technical support (1-800-NETWARE) for a charge of $14.95.
        The DR DOS LANPack LANINST and periodic business Updates can be
        run from A: or B:.

Q:      Where can I find sample configurations for running Windows,
        Geoworks, QEMM, NetWare, or LIM 4.0 with DR DOS?

A:      Sample configurations for running these products with DR DOS 6.0
        can be found on the last diskette of the original DR DOS diskette
        set in the EXAMPLES directory.  Customers may want to build on
        these to meet their own individual system needs.

Q:      Are multiboot OS/2 version 2.0 and dual-boot OS/2 version 1.3
        compatible with DR DOS 6.0?

A:      Both configurations have been tested and work properly with
        DR DOS 6.0. Documents 1616 (OS/2 Installation) and 1617 (OS/2
        Compatibility) in the Faxback system provide special configuration
        information.

Q:      When I run CHKDSK on my SuperStor drive, the free space available
        differs from what the DIR command shows, often by a few megabytes.
        Why?

DA(m)N NEWS 1-03                   Str. 16                   4 Dec 1993


A:      First, it is important to realize that the total bytes of data a
        SuperStor drive holds varies, depending on the compressibility of
        the files on the disk.  Individual files can vary from a 16:1 to
        a 1:1 compression ratio.  Do not assume that uncompressed data
        will compress at a 2:1 ratio.  Statistics indicating space
        available on a SuperStor drive should be considered an estimate,
        since SuperStor has no way of knowing how compressible a file
        will be until it is actually written to the disk.

        CHKDSK and DIR (or XDIR) report different figures for available
        disk space because they look at different indicators in estimating
        how much more data will fit on the disk. CHKDSK looks at the
        SuperStor allocation table to see how many empty entries are
        available and reports that figure in terms of the number of bytes
        that it represents.  The SuperStor allocation table always assumes
        a 2:1 average compression ratio, and sets up an internal File
        Allocation Table (FAT) with double the entries of the partition's
        original FAT.  Unless the actual average compression ratio is 2:1,
        CHKDSK is not a reliable indicator of available disk space.

        The DIR command does not reference the allocation table.
        It estimates free disk space based on the physical space occupied
        by files on the disk and their average compression ratio.  It then
        projects how much space will be available assuming the remaining
        physical space is occupied by files with this same compression
        ratio.  As a result, the DIR command compensates for the
        compressibility of the files, giving a much better indicator of
        disk space available.  Therefore, DIR and XDIR usually provide a
        estimate of available space than CHKDSK.

        The best and most reliable indicator of free space, both in terms
        of actual physical disk space and in "compressed" space, is the
        SSTOR "statistics."  Refer to Faxback document #1201 for further
        information on this topic.

        NETWARE FOR MACINTOSH

Q:      What are some new features included with v3.011 NetWare for Macintosh?

A:      Print Accounting - Allows network administrators to charge a user's
        account balance based on job size, or monetary amount per page,
        when printing files.

        Printer Logs - Maintains a printer log file for each printer on
        the network, including LaserWriters and ImageWriters.  The printer
        log holds such job information as queue name, job number, job size,
        title, owner and errors.

        Hold and Keep Queues - Allows users or print queue operators to
        place AppleTalk print jobs on hold.  The hold queue offers
        flexibility to users who want to submit their print jobs to a
        queue and have them printed at a later time.  The keep queue
        delays printing, holding the document in the queue, until the
        user decides to print the job.

        Optional Notification - Can be activated to notify users when
DA(m)N NEWS 1-03                   Str. 17                   4 Dec 1993


        print jobs have completed.  Users are informed of print job
        errors if they are logged in to the server, regardless of the
        print configuration selected.

        SNMP Support  - The AppleTalk router included with v3.011
        supports the AppleTalk MIB I specification for SNMP, allowing
        the exchange of management information between network components.

        User Stratification - NetWare for Macintosh v3.011 comes in a
        5-user, 20-user, 100-user and a 200-user version.

Q:      I seem to be having a compatibility problem with system inits
        and extensions and DataClub.  My Macintosh crashes, and I get
        erratic behavior from the system.  What could be the problem?

A:      DataClub works fine with most common software, although there
        are some known init conflicts.  Below are a few of the more
        common ones.  DataClub v2.0 Release Notes include a complete
        list of compatibility considerations.

        SAM Intercept - The v2.x series of SAM needs to be loaded after
        the DataClub extension.  If you do not have an extension loading
        utility (for example, InitPicker), then rename SAM Intercept to
        !SAM Intercept.  Also, the v2.x series should set the SAM
        protection to Basic.  DataClub and SAM v3.0 are compatible
        provided SAM loads before the DataClub extension file.

        Note that under System 7 it is not sufficient to drag the
        SAM Intercept file into the System Folder.  This can lead to
        SAM loading after all the extensions, leaving your system less
        protected.  Under System 7, the SAM Intercept file must be placed
        in the Extensions Folder and an alias created in the Control
        Panels Folder.

        RasterOps Extensions - DataClub is not compatible with the
        RasterOps Extensions.  These are optional when using the
        RasterOps screen and should be disabled.

        Now Utilities - DataClub shows erratic behavior with the Now
        Utilities Startup Manager.  Uncheck the "Show invisible folders"
        in the Control Panel.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 18                   4 Dec 1993


===============================================================================
                                    CLIPPER
===============================================================================


                          Testing for dbCommit() debate.

Grettings fellow Clipper programmers.  As I'm sure everyone has noticed, there
has frequently been a debate as to whether or not a dbCommit() is necessary
on a network when databases are opened in shared mode.  The discussion usually
goes into specifics about Novell, but is open to all networks in general.  The
two sides usually taken are that 1) dbCommit() is needed to flush out the CACHE
BUFFERS at the workstation level to guarentee that the write will reach the
server before the dbUnlock() request, or 2) dbCommit() is not needed since no
caching of files opened in FO_DENYNONE mode are cached by the latest NETX and
that dbCommit() only serves to strain the server forcing it to write the cache
buffers on the server to the server's hard disk.

We assume that the work station in question is using latest NETX, and that
CACHE BUFFERS in the NET.CFG is set to a number greater than 0 (the Default).

To understand further the debate, we must look at what each side believes the
following sequence does:

Sequence 1.
    1.  Use DATABASE Shared New
    2.  rlock()
    3.  DATABASE->field := 5
    4.  dbUnlock()

Description 1 of Sequence 1.
    1.  Here it is said that the USE statement will open up the database in
        DENYNONE mode, telling the NOS shell not to cache any reads or writes
        to this file.

    2.  The rLock() function will obtain a lock on byte 1000000001 in the file
        DATABASE.DBF.  It then will reread the record into Clipper's internal
        buffer.

    3.  Updates the record in Clipper's internal buffer and sets a flag telling
        Clipper that this record has pending writes.

    4.  Sees that pending writes for this record are present, sends them to the
        NOS, then sends a request to unlock byte 1000000001.  The write will
        reach the server first since no caching of writes will take place in
        the CACHE BUFFERS.

Description 2 of Sequence 1.
    1.  Here it is said that the USE statement will open up the database in
        DENYNONE mode, but the NOS will still cache the writes unless the file
        was flagged as SHAREABLE.

    2.  No change.

    3.  No change.

DA(m)N NEWS 1-03                   Str. 19                   4 Dec 1993


    4.  Sees that pending writes for this record are present, sends them to the
        NOS, then sends a request to unlock byte 1000000001.  The write MAY
        reach the server before the unlock, but might not.  It is believed
        that the unlock might reach the server first since the unlock will not
        be cached by the NOS but that the write might.



How is it we have these two views?  Description 1 would be the obvious way
things must happen on a network for things to work properly.  This also is
the way that Novell has documented the current shell.  However, a number of
us have noticed data corruption, and by adding a dbCommit() (described below
in Sequence 2), the corruption has gone away.  Thus, description 2 has come
about by those who believe the problem is the shell caching the write.
Although Novell documents the current shell behaving like description 1, it
has been shown that previous shells have had bugs in them.

Sequence 2.
    1.  Use DATABASE Shared New
    2.  rlock()
    3.  DATABASE->field := 5
    4.  dbCommit()
    5.  dbUnlock()

Description 1 of Sequence 2.
    1.  Here it is said that the USE statement will open up the database in
        DENYNONE mode.  The NOS will still cache the writes unless the file
        has been flagged as SHAREABLE.

    2.  The rLock() function will obtain a lock on byte 1000000001 in the file
        DATABASE.DBF.  It then will reread the record into Clipper's internal
        buffer.

    3.  Updates the record in Clipper's internal buffer and sets a flag telling
        Clipper that this record has pending writes.

    4.  Sees that pending writes are present for this record and flushes them
        to the NOS.  It then will request the NOS to flush them from the local
        CACHE BUFFERS to the server (from there it may or may not be flushed
        to the server's hard disk).

    5.  Sends a request to unlock byte 1000000001.


Sequence 2 above is what has been proposed under the belief that Description 2
of Sequence 1 is correct.  This is also the way my own applications are
currently coded.

Which side of the fence do I stand?  Before I started some Sniffer experiments
over the weekend, I sat on Description 2 firmly.  I have seen corruption go
away with a dbCommit() as others have too.  I now have to side to Description 1
of Sequence 1 based on some preliminary testing.  I will get into this in
detail later as well as provide the exact tests and exact output from the
Sniffer.

How do we find out what is really going on?  Someone once suggested that a
DA(m)N NEWS 1-03                   Str. 20                   4 Dec 1993


simple test of opening a file, then writing 1 byte in a loop about 1000 times
would prove/disprove caching.  If caching is present, the NOS will not waste
the overhead of an entire packet for 1 measly byte write, and will optimize
the packets.  If no caching is present, then it will, thus maintaining the
integrity of the file (logical choice).

I decided to perform the above test.  To check the results, I have used the
Expert Sniffer from Network General.  The Sniffer is a portable computer with
a network card configured NOT to actually obtain a connection to the server.
The Sniffer acts as a stethoscope, allowing one to listen in to the
conversations being held on the network backbone.  The Expert Sniffer I used
also will decode the packet communication between a work station and the
server.  I have included this decoded output as well.

I did the tests on a NEC Powermate SX/20i workstation with a Western Digital
network card.  The backbone is Ethernet, and the NOS is Novell 3.11 with the
work station shell being NETX v 3.26.  CACHE BUFFERS in the NET.CFG were set
to 40.  DOS buffers at 8, FAST disk cacher was loaded to cache drive C:.  All
programs were run from a local drive to not cause any network traffic to
filter through.  The data was created/accessed on the server.

The zip file contains a list for additional zip files.  Each additional zip
file contains the output data from the sniffer.  The file name corresponse
with the test number performed.  Within each zip is two files.  For example,
TEST1.ZIP contains TEST.PRN and TESTD.PRN.  TEST.PRN is a summary listing of
packest transmitted.  TESTD.PRN is a detailed listing that shows in English
the break down of each packet, as well as the hex representation of each
packet.  This "D" files are quite large.  It is interesting to look at for
those interested in seeing what an Ethernet packet looks like.  I would not
print them out unless you want to explicitly look at the physical information
transmitted though.  In most cases, looking at the summary prints should be
enough when compared line by line to the source code.

I performed the above test, using Clipper's low level file IO functions.  I
included the program in this ZIP, but I did not include the output.  The output
did simply show 1 byte write requests.  This showed that at a low level, there
was no caching of the files.  The remaining test were are done through
Clipper's database functions.

****************************************************************************
TEST1:  Build a database for remaining tests.  Watch how the file is built.

This program is run several times, the first time was just to watch the
creation, but it was run later without capturing the data to rebuilt the test
data set for tests that involved indexing.

The first test added in around 100 records.  Tests 14 and 15 used only 10
records.

This test showed that an append makes the following requests from the OS.
    Lock byte 1 billion (header)
    Get current file size
    Lock byte 1 billion + record number to be appended
    Write RecSize() # of spaces
    Unlock byte 1 billion (header)
    write to Clipper's internal buffer
DA(m)N NEWS 1-03                   Str. 21                   4 Dec 1993


    Write updated record (even if just append blank -- no changes)
    unlock byte 1 billion + record number appended

It also showed that when a database is closed, a commit is issued first.
I could also determine that the database was opened in DENYNONE mode, and that
the appends were not buffered.

It is important to know the header of the database was NOT updated during
the appends.  The first 32 bytes of the header contain important information
regarding LAST UPDATE DATE and the NUMBER OF RECORDS.  This did not get changed
until the file was closed, just before the commit.

****************************************************************************
TEST2:  Randomly update database records using only the unlock.

This showed that Lastrec() does not look at the number of records stored in
the header, but will instead determine the size of the database W/O locking the
header to prevent any appends from taking place.

It also showed that the a write to a database using lock(), write, unlock does:
    Lock byte 1 billion + recno
    read record to buffer
    write to Clipper's buffer
    write buffer
    unlock byte 1 billion + recno

No buffering of the write took place.  These are the actual requests sent to
the server.

****************************************************************************
TEST3:  Same as TEST2, but use a commit BEFORE the unlock.

The lock, write, commit, unlock did the following:
    Lock byte 1 billion + recno
    read record to buffer
    write to Clipper's buffer
    write buffer
    lock byte 1 billion (header)
    get current file size
    write new header
    unlock byte 1 billion (header)
    issue DOS Commit
    unlock byte 1 billion + recno

It showed that not only does Clipper do a DOS commit command, but it also will
do additional locking of the header, and update the number of records.  This
can help account for why dbCommitting takes longer than a regular unlock.  We
also see that the dbCommit() will first issue the write for the record, and
that dbUnlock() will only write the record if it needs to be.  Thus, Clipper
has a way of determining of a record in memory has pending writes and will
flush them.

****************************************************************************
TEST4:  Same as TEST2, but use a commit AFTER the unlock.

The lock, write, unlock, commit did the following.
DA(m)N NEWS 1-03                   Str. 22                   4 Dec 1993


    lock byte 1 billion + recno
    read record
    write to Clipper's buffer
    write buffer
    unlock byte 1 billion + recno
    lock byte 1 billion (header)
    get current file size
    write new header
    unlock byte 1 billion (header)

This showed that even after an unlock, when Clipper performs the dbCommit()
function, it still knows that everything is not out to disk, and does
additional processing beyond the unlock command.

****************************************************************************
TEST5:  Here was a simple test to check on goto's and reads.

This test left an indication that Clipper is very selective when it reads
in a record.  In this case, only one read was issued, even though the database
is opened and record 1 is automatically selected, a goto record 3 was issued,
and the field there was printed twice with a commit inbetween.

This showed that dbCommit() will do nothing if no changes need to go out.  It
also hints that a record is only read into Clipper when an operation is
attempting to access that record, but never before.  The next test looked into
this further.

****************************************************************************
TEST6:  Issue a series of dbGotos.

This test showed that all the dbGotos in the world won't cause Clipper to
automatically read the records in.  But instead, it hints that Clipper keeps
track if the record in the Clipper buffer is up-to-date, and every access to
this buffer first checks to see if the record needs to be refreshed.  If it
does, Clipper will read the buffer first, then perform the action.  This
translates into Clipper keeping a logical BUFFER_CLEAN as well as a
BUFFER_RECNO.  When a dbGoto is issued, BUFFER_RECNO is changed, and
BUFFER_CLEAN is set to false.  Next time someone will try to read or write to
this buffer, BUFFER_CLEAN will be checked, Clipper will see it's false, read
in the record number contained within BUFFER_RECNO, set BUFFER_CLEAN to true,
then continue on with the operation.

This also hints that an rlock() will not actually read in the new record, only
obtain the record lock, then set the BUFFER_CLEAN flag to false.  All the
committing above also shows that a HEADER_CLEAN flag must be kept somewhere,
and that this flag is checked ONLY by the dbCommit() function, but is set false
whenever a write to the BUFFER is performed.

By not reading the record after every goto, Clipper is effectively lowering
the amount of traffic on a network.  If every goto automatically read in the
record, the subsequent rlock() would then have to read the record again.  By
delaying that reading action until the absolute latest, Clipper keeps from
making unnecessary reads.

****************************************************************************
TEST7:  Same as TEST2, but the database will be opened EXCLUSIVELY.
DA(m)N NEWS 1-03                   Str. 23                   4 Dec 1993


This test proved that buffering will take place when a file is not shared
on the network.

This also showed that, at least in this test, Clipper will allocate memory
for buffers of EXCLUSIVE files in 512 byte increments.  It also showed that
Clipper wrote the entire buffer, even if it goes past the end of the file,
then will come back and truncate the file to the proper length.

It also showed that if a database is opened exclusively, Clipper will
ignore all requests for locking and unlocking automatically.

****************************************************************************
TEST8: Same as TEST3, but the database will be opened EXCLUSIVLY.

This test showed that a dbCommit() does major writing to the file.  It showed
that Clipper will write out the ENTIRE BUFFER, even if you only modified the
current record, it will write out everything.  Clipper has no way of knowing
what parts have changed, thus each commit will do a write of the entire buffer,
1024 bytes in this case for a 6 byte change, then truncate the file if
necessary, write out the header information, the issue the DOS commit.

****************************************************************************
TEST9:  Check how dbSkip(0) and dbGoto() perform with and w/o the DELETED
        flag being on.


This test was inconclusive.  It did not show if the deleted() caused the
read, or if the dbSkip(0) or dbGoto( recno() ) caused the read.  This will
become very clear later.  To interpret the test, we need to know what a
plain open will do with and w/o DELETED ON.  We also need to perform some
action to the buffer to have Clipper read it in if it thinks it needs to.

This test did at least show in combination with TEST12, that the dbSkip(0)
and dbGoto() don't ever automatically read the record, no matter what the
DELETED setting is.

****************************************************************************
TEST10:  To look into it further, I traced what an open looks like.

An open will not read anything into Clipper's buffer, but will set the
BUFFER_CLEAN flag to false and set the BUFFER_RECNO to 1.

****************************************************************************
TEST11:  Check open when DELETED is ON.

In this case, Clipper will perform the read to make sure the record we are
on is not deleted at the time of the open.  Here Clipper will read each record
until it has found one that is not deleted.  When it has, it puts that record
number into the BUFFER_RECNO and sets the BUFFER_CLEAN to true.

****************************************************************************
TEST12:  This will show that dbSkip(0) or dbGoto() is sufficeint to cause
        Clipper to set the BUFFER_CLEAN flag to false.


The chart below shows that the dbSkip() or dbGoto() will cause Clipper to
DA(m)N NEWS 1-03                   Str. 24                   4 Dec 1993


reread the record in the next time the buffer is accessed (See also test9).
It is important to note that the buffer will only be up to date at that instant
it was read, and that changes made after the read by other users will not be
shown.  Thus, this method will be good to refresh the buffers if needed in
a tbrowse of casual data, but that if you need to any checking for conditions
against a record, you should lock the record first to ensure you are looking
at what is really there.

                    DELETED OFF      DELETED ON
-----------------+----------------+-----------------
dbSkip(    0    )|     YES        |     YES        |
-----------------+----------------+-----------------
dbGoto( RecNo() )|     YES        |     YES        |
-----------------+----------------+-----------------

****************************************************************************
TEST13:  Check on subsequent access to the same buffer.

This was a quick test to show that Clipper will use the buffer instead of
rereading the record whenever possible.  (Obvious I know, but demonstrating
everything).

****************************************************************************
TEST14:  Try TEST2 over, but with an index this time.

This test was done with less records than in previous attempts.  First
TEST1 is run with 10 records, then the program INDEX is used to create
the index for the tests.

This test showed that the lock, write, unlock sequence on an indexed
database (1 index) does the following:
    lock byte 1 billion + recno
    read record
    write to Clipper's buffer
    lock byte 1 billion in index (general locking byte)
    read index page
    write updated index page
    unlock byte 1 billion in index file (general locking byte)
    write updated record to database
    unlock byte 1 billion + recno

****************************************************************************
TEST15:  Try TEST3 over, but with an index this time.

This test also rebuilt the test data set with 10 records, then the index
was recreated.

This test showed that the lock, write, commit, unlock sequence on an indexed
database (1 index) does the following:
    lock byte 1 billion + recno
    read record
    write to Clipper's buffer
    lock byte 1 billion in index (general locking byte)
    read index page
    write updated index page
    unlock byte 1 billion in index file (general locking byte)
DA(m)N NEWS 1-03                   Str. 25                   4 Dec 1993


    write updated record to database
    lock byte 1 billion (database header)
    write updated database header info
    unlock byte 1 billion (database header)
    commit index
    commit database
    unlock byte 1 billion + recno

This showed that the index is updated before the record.  It also showed
that the dbCommit() does not do any additional processing to the index as it
does to the database.

****************************************************************************
TEST16:  Simple check of what an open looks like with an index.

This shows that if the index is opened, Clipper will do the following:
    Open database
    read database structure
    open index
    read index
    get index file size
    lock index
    read index page
    read second index packet
    unlock index
    close index
    commit database
    close database

Notice here that the the index file was not committed before closing, while
Clipper will automatically commit the database before closing.  This is
inconsistent.

****************************************************************************
TEST17:  Same as TEST16, but with DELETED ON.


This shows that if the index is opened and DELETED ON, Clipper does:
    Open database
    read database structure
    read first record to see if deleted
    open index
    read index
    get index file size
    lock index
    read index page
    read second index packet
    read top record in database according to index order
    unlock index
    close index
    commit database
    close database

Basically the same, except the reads are done automatically.


DA(m)N NEWS 1-03                   Str. 26                   4 Dec 1993


****************************************************************************
Where does this leave us?

As I have stated above, I can no longer believe that the NOS is caching so
long as the latest NETX is used.  I did not do any testing with other shells
or networks.  These other nets are hopefully well behaved and will perform
the same.

We have seen by the above that the NOS did not do any caching.  Is this the
end all/be all test though?  I don't think so.  This only watched what went
across the line between the server and the work station.  We do not know
internally who the Server handled the packets, but we can guess in sequence
without any problems.  This test did not contain large record numbers, nor
record sizes that would necessitate multiple packets for one write (like a
2k record size).  This test was only done on an Ethernet network.  No
contention came from any other stations.  These tests only involved the
DBFNTX RDD driver (not the enhanced conditional index one either).

We are left knowing that the commit does more than just issue the DOS commit
command.  We know it will also write out updated header info.

We also know that the index file is not committed before closing.  This I
think should be happening.  Is this the problem?  I don't know.

We also know that Clipper doesn't arbitrarily read in records.  One thing
that would help would be to know at a source code level EXACTLY what the
dbCommit() function does from start to finish.  I have not done extensive
testing with the indexes and when pages are read in either.

We need to develop some GOOD testing programs to check on concurrency with
and without committing.  The tests I performed always only had me in the
files.  SAMES has mentioned writing a program that randomly updates records
in a database.  I will be modifying one of my test programs to run
continuously, increase the complexity of the index expresion, increase the
width of the records, and run it on multiple machines and see if any 1210
errors occur.  I will do this test within the next few weeks.

There also remains the possibility that Clipper may be the culprit.  That the
dbCommit() also performs some internal flagging that does not get done by the
unlock function.  Our corruption seen, at least in my case, was 1210 errors.
These errors may have been generated, but perhaps no actual physical corruption
was taking place.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 27                   4 Dec 1993


                              WARPLINK
                    Lean, mean, linking machine.

WarpLink Is the linker you always wanted. It's fast. It's powerful.  It's
easy to use.  And it gives you state of the art linking technology in any
language.  All for $249.95.

hyperkinetix, inc. brings you WarpLink, a DOS-compatible linker for use
with any language compiler.  WarpLink speeds your development time with
faster linking and full dynamic overlays by eliminating costly static
overlay design time.  WarpLink replaces your old linker entirely.  It has
been extensively tested with all popular language compilers.

True dynamic overlays
Overlays let you break a program into manageable pieces.  Instead of trying
to shoehorn your entire application into memory at once, overlays let you
leave pieces of your program on disk and pull in routines on demand.  While
some overlay managers force you to use only one level of overlay (meaning
some overlay routines can't call others), WarpLink lets any code call any
overlay code, nesting to any level.  Normally, overlays must be carefully
planned and their order arranged at compile time, sharply limiting their
flexibility.  WarpLink's dynamic overlays, on the other hand, let your
program configure itself to available memory at runtime.  So if one user's
machine has only 348K, but another's has a full megabyte, your program will
run to the full capabilities of each.  Automatically.  Command line options
let you fine-tune WarpLink's speed and memory usage for overlays. You can
set the maximum number of overlays, reserve or allocate memory, set warning
levels, etc.

Overlayable D-format Dynamic Link Libraries
WarpLink allows you to store collections of often used functions into
libraries that are callable by every application you write.  This saves
massive duplication of these functions on disk, but that's just the
beginning.  Revolutionary technology in WarpLink's overlay manager and core
linker allow you to dynamically overlay these libraries.  This ability
reduces memory requirements and disk access time, increasing your
application's flexibility.  Simply put, this is the largest breakthrough in
linking technology to date.

For Clipper users: More speed, more memory, and more control
WarpLink can link Clipper code incrementally, meaning that small changes to
your program can be patched directly into the .EXE or overlay file.
Relinking can take less than a second!

Shrink that .EXE: SymPacWL, the revolutionary symbol table cruncher for
Clipper applications, eliminates duplicate variable and procedure names
from any Clipper (Summer '87 or 5.0) generated .EXE.  You'll slim down RAM
requirements, disk storage space, and load time--typical applications shed
40K of unnecessary bulk.

To squeeze every last byte of memory out of your Clipper programs, WarpLink
contains Clipper-usable routines licensed directly from Integrated
Development Corporation, the SmartMem people: h_free_mem() to get total
heap free memory; h_graph() to show a graph of the pool; h_graphs() to
returns h_graph display as a string; h_maxblock() to get size of biggest
heap block; h_memory0() to get free memory down to block size; h_pack() to
DA(m)N NEWS 1-03                   Str. 28                   4 Dec 1993


defragment Clipper's free memory pool; h_rept() to list memory blocks win
Clipper's heap; h_tot_mem() to get total heap memory; h_used_mem() to get
total of used heap memory; h_walk() to traverse heap memory.

Using WarpLink with Clipper 5.0 you can now overlay portions of CLIPPER.LIB
automatically.  One simple command line switch automatically separates
those functions in CLIPPER.LIB that can be dynamically overlaid, puts them
in the overlay, and places the balance in the root where they belong.

Linker compatibility
WarpLink is a true MS-DOS compatible linker that's been tested with all the
popular language compilers.  WarpLink fully conforms to Microsoft
specifications, reads extended library information in Microsoft LIB format,
and accepts the LIB, OBJ, and TMP environment variables.

Speed and better memory management with EMS / XMS support
WarpLink cuts link times dramatically by supporting extended and expanded
memory during the link.  If you're still taking that link-time coffee break
then you really need to see what WarpLink can do for you.  WarpLink also
lets you load your overlay file in expanded memory at runtime to increase
your memory management efficiency.

WarpSpeed profiling
WarpLink'd applications can be quickly and thoroughly analyzed by the
powerful WarpSpeed profiler.  You can now optimize routines, analyze the
use of each function in your application, and directly improve the
operation of any program you create.  All of this quickly and painlessly,
without embedding your application with profiling calls.

User driven command line options
Allow you to:  reset the maximum program allocation space; create a .COM
file; overlay Clarion code; incrementally link Clipper; use DOSSEG segment
ordering; use extended Microsoft .LIB format; create a map file; create an
expanded map file; disable the search for default .LIBs; change the overlay
class name; keep overlays inside the .EXE file; set the overlay maximum
load count; change the overlay filename; set the overlay pool size; set the
overlay internal stack size; reload active overlays swapped out upon
return; set case sensitivity; set program stack size.

The extras
WarpLink's manual includes detailed tutorials for Clipper, Borland C++, and
Microsoft MASM. WarpLink's error handling not only tells you what went
wrong, but offers a diagnosis of the problem and a suggested solution.
Detailed map information gives programmers much needed help in debugging.
Its /C option creates a .COM file directly, so you can forget EXE2BIN. A
special $$_COM_END value lets your .COM files determine their size at
runtime to deallocate memory properly.  The manual comes with a full index,
hints on how to use your linker better, and a glossary.

WarpMod: Another slick trick to trim link time is the WarpMod Utility.  You
can change linking parameters in the .EXE without relinking.  Change the
overlay stack size, the overlay pool size, the maximum overlay count, the
program stack size, the reload option (required for Clipper Users), the
overlay file spec, the maximum allocation requested, and the date and time
of the original .EXE file.

DA(m)N NEWS 1-03                   Str. 29                   4 Dec 1993


WarpHog: Sometimes you need to simulate low-memory conditions to test your
application in a similar environment to the target machine. The WarpHog TSR
lets you do just that.

Norton Guides:  On-line Norton Guides help for WarpLink will cut your
learning curve to nothing.  You'll be up and running in less time than it
used to take to compile!

The hyperkinetix difference
Free telephone, CompuServe, electronic BBS technical support.  30 day
satisfaction money-back guarantee.

System Requirements
IBM PC or compatible with 256K * Any language producing MS LINK-compatible
object files * One floppy drive (package has both 3.5" and 5.25" diskettes)
* DOS 2.0 or greater.  Download the WarpLink demonstration from our BBS
(714)935-0832.

         hyperkinetix, inc.   615 North Poplar, Orange, CA  92667
         Telephone (800)873-9993  (714)935-0823  FAX (714)935-0831

    The last linker you'll ever buy, and the only one you'll ever use.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 30                   4 Dec 1993


===============================================================================
                                   Hardware
===============================================================================


                                    FUJITSU
                              MODEL M2611S/SA/SB
                                JUMPER SETTINGS

    Ŀ
                                                 CNH-1         Ŀ   
                                                 ڿ             S    
                        (Terminator    11 ͵             C    
                             power)        10 ͵             S    
                                            9 ͵             I    
                                            8 ͵            I/F   
                                          7 ͵             C    
                      (Synchronous      6 ͵             O    
                       transfer mode)       5 ͵             N    
                                          4 ͵             N    
                    (SCSI bus parity)   3 ͵             E    
                                            2 ͵             C    
                                          1 ͵             T    
                                                              O    
                                                                R    
                                          CNH-2                   
                 (Write protection)     (SCSI ID)                      
                                       ڿ                             
                       (motor control)  9 Ŀ                   
                      Ŀ Ŀ        8     ID-3              
       CNH-4                         7                    
      ڿ              1 2 3 4 5 6        6 Ŀ                   
       1 Ŀ                  5     ID-2         \
       2       п       4                O  
       3 Ĵ           3 Ŀ                  
                                      2     ID-1          O  
                                        1                   
    (Self-diagnostic switch)                                     O  
                                                         (Power       
                                                      connector)   O  
    /

Jumpers:                                  CNH-3 Motor Control
CNH-1 SCSI bus parity                           Started by
      Enabled     1 2   x                       power on      4 5  x
      Disabled    2 3                           Started by
                                                command       5 6
CNH-1 Synchronous transfer mode           CNH-2 SCSI ID
      Enabled     4 5   x                       Bit-0 Enable  1 2
      Disabled    5 6                                 Disable 2 3  x
                                                Bit-1 Enable  4 5
CNH-3 Write protection                                Disable 5 6  x
      Enable      2 3                           Bit-2 Enable  7 8
      Disable     1 2   x                             Disable 8 9  x
CNH-4 Self-Diagnostic Mode
      Self-Test mode    1 2   x
DA(m)N NEWS 1-03                   Str. 31                   4 Dec 1993


      Normal mode       2 3
Terminator Power should be supplied from the Bus unless otherwise specified.

-------------------------------------------------------------------------------


                                  MICROPOLIS
                                  Model 1373A
                                JUMPER SETTINGS

   Ŀ  Ŀ  Ŀ
  Ŀ                                                  
  J2                                                          
                                                              
                                                              
  == W9 BUS Parity Check Option                               
  == W3 Spindle Control    Ŀ        
  == ID2Ŀ                  SCSI ID  ID2 ID1 ID0         
  == ID1 SCSI ID         ͵        
  == ID0                   *  0    out out out         
  ͵                            1    out out  in         
  S                            2    out  in out         
  C    Ŀ                      3    out  in  in         
  S                           4     in out out         
  I                            5     in out  in         
                              6     in  in out         
  C     Interface          7     in  in  in         
  O        Terminators           
  N                       W3 Spindle Control                 
  N                         in = Wait for start command     
  E                     * out = Spin on power-on           
  C                                                          
  T                        W9 BUS Parity Check                
  O  Ŀ                     in = NO Parity                 
  R    Ŀ__ W2          * out = Parity Enabled            
       Ĵ__ W1 *                                          
            (Circuit Board component side)            
                    Ŀ                    Ŀ          
       

   Ŀ
                      (back view)                              
                                                               
          J3                                                   
       /\                                               
       o o o oĿ                                        
            Pin 1
    (power connector)                                        
                                                             
      Ŀ                                     
                 Ŀ 
                   SCSI CONNECTOR        J1        
         
            J2                                                 
   

DA(m)N NEWS 1-03                   Str. 32                   4 Dec 1993


* = FACTORY DEFAULT SETTINGS

                              23 25 27
                           Ŀ
                                                   
                     J2                            
                           
                              24 26 28

      Jumper J2 pins 23 - 28 are used to interface the drive to a user-
supplied operator panel.
    Ŀ
     Pin    FUNCTION                                       
    ͵
     23         Logic Ground                               
     24         Not Used                                   
     25         Write Protect input.  Logic ground         
                disables writing and lights the Write      
                protect LED.                               
     26         Ready Output.  Logic ground indicates the  
                drive is Ready and lights the READY LED.   
     27         +5V source for the LEDs                    
     28         Power Fail Detector input (from host       
                system).  Logic ground warns the drive of  
                a pending power loss.  The drive will      
                attempt to terminate operations before the 
                power loss occurs.                         
                                                           
    

-------------------------------------------------------------------------------


                              ST - 125N

       UNFORMATTED CAPACITY (MB) ________________N/A
       FORMATTED CAPACITY (26 SECTORS) (MB) _____21.5
       ACTUATOR TYPE ____________________________STEPPER
       TRACKS ___________________________________1,628
       CYLINDERS ________________________________407
       HEADS ____________________________________4
       DISCS ____________________________________2
       MEDIA TYPE _______________________________THIN FILM
       RECORDING METHOD _________________________RLL
       TRANSFER RATE (mbits/sec) ________________7.5
       INTERFACE ________________________________SCSI
       TPI (TRACKS PER INCH) ____________________824
       BPI (BITS PER INCH) ______________________16,546
       AVERAGE ACCESS (ms) ______________________40/28*
       SINGLE TRACK SEEK (ms) ___________________8
       MTBF (power-on hours) ____________________70,000
       POWER REQUIREMENTS: +12V START-UP (amps) _2.0
                           +12V TYPICAL (amps) __0.35
                           +5V TYPICAL (amps) ___0.9
                           TYPICAL (watts) ______9
                           MAXIMUM (watts) ______29
DA(m)N NEWS 1-03                   Str. 33                   4 Dec 1993


       BUFFERED STEP PULSE RATE (micro sec) _____3-200
       WRITE PRECOMP (cyl) ______________________N/A (408)
       REDUCED WRITE CURRENT (cyl) ______________N/A (408)
       LANDING ZONE (cyl)________________________AUTO PARK
       IBM AT DRIVE TYPE ________________________N/A

       *ST125-0/ST125-1

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 34                   4 Dec 1993


===============================================================================
                                   Software
===============================================================================


                  UPDATING VCS TO SUPPORT TLIB VERSION 5

Version 5 of TLIB has a different command set than version 4.12.  There
are 2 ways you can make Multi-Edit's VCS support compatible:

1. You can configure TLIB version 5 to understand version 4 commands.
   The new TLIBCONF will allow you to configure this automatically.

2. You can change your commands in the VCS SETUP dialog box as shown
   below (NOTE: The options above the Commands section do not need to
   be changed):

   VCS SETUPķ
   VCS Type:  TLIB                User ID.. TR
   Library Options:                                             
    Extension ??!                 LOK Ext.. ??#                 
    Path..... G:\TLIB\VCS\<EXT>
   Change Comment                 Options:   [ ] Change Support 
    Start.... $Change:             [X] Delete Source  
    End...... $             [X] Run VCMPR      
    Commands ͺ
    Get... TLIB.EXE CP <LPATH> E0 <NAME>.<EXT>
    Put... TLIB.EXE CP <LPATH> U0 <FILE>.<EXT> @<COMNT>
    Log... TLIB.EXE CP <LPATH> L0 <FILE>.<EXT>
    Diff.. TLIB.EXE C0 "TRACK N" CP <LPATH> EB <%TMP>\<NAME>.<EX
    Create TLIB.EXE CP <LPATH> N0 <FILE>.<EXT> @<COMNT>
    Browse TLIB.EXE CP <LPATH> EB <NAME>.<EXT>
    Lock.. TLIB.EXE CP <LPATH> ER <FILE>.<EXT>
    Unlock TLIB.EXE CP <LPATH> UD <FILE>.<EXT>
                                                                
                 OK<ENTER> Cancel<ESC> Help<F1>              
                                    
   ͼ
     

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 35                   4 Dec 1993


AUTOMATICALLY PRINTING RECEIVED FAXES USING GCL

--Make sure that the Queue Manager is ON, so that any incoming faxes
will be received in the background.

--Create a script file that will check for received faxes and print them
out, similar to the one below:

    $COUNTER 1 0
    REMARK ENTER A CONTINUOUS LOOP
    DOWHILE $COUNTER 1 == 0
        REM WHILE THERE ARE ANY RECORDS IN THE RECEIVED LOG,
        REM GET THE RECORD, CHECK FOR ANY ERRORS, AND PRINT IT
        DOWHILE GET RECECIVE == 0
            IF @SA == 0
                EXECUTE FAXC -e -f0 @RF FAX001.TIF
                EXECUTE FAXP -M3 FAX001.TIF
                REM CHECK THE REFERENCE MANUAL TO PUT THE CORRECT
                REM PARAMETER IN THE -MX OPTION; THIS DEFINES THE
                REM TYPE OF PRINTER YOU HAVE
                IF INQERROR==0
                   DELETE
                   REM THIS DELETES THE CURRENT RECORD IN GCL
                ENDIF
            ENDIF
            WAIT 30
        ENDDO
        WAIT 30
    ENDDO


--The "-MX" option for the FAXP command indicates the type of printer
which will be used to print the faxes.  Please note that you need to
replace the "X" in the above program to reflect your configuration when
you create the file.  Information on these option values is in Chapter 8
of the GammaFax Reference Manual.  Depending upon how often you anticipate
incoming faxes, you may want to increase the wait periods in the program.

--From your FAX subdirectory, type "GCL filename", where "filename"
is the script file you created.  This will begin the program's execution.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 36                   4 Dec 1993


===============================================================================
                                     OS/2
===============================================================================


                           Oekvan OS/2 knihy


Ji vydno
----------

Advanced OS/2 Presentation Manager Programming   John Wiley & Sons
The Art of OS/2 C Programming                    QED
Designing OS/2 Applications                      John Wiley & Sons
Dvorak's Guide to OS/2                           Random House
Easy OS/2                                        Que
Learn OS/2 in a Day                              Wordware Publishing
The Little Book of OS/2                          Peachpit Press
Micro Focus CICS Option 3.0: Developing CICS     QED
  Applications on the PC
Micro Focus COBOL/2 Workbench for the            QED
  Application Developer
OS/2 2.1 Complete                                Abacus
OS/2 2.1 Programming                             Osborne / Mc-Graw Hill
OS/2 2.1 Unleashed                               Sams
The OS/2 2.1 User's Bible                        Abacus
OS/2 2.X Notebook: Best of OS/2 Developer        Van Nostrand Reinhold
OS/2 Extra                                       TAB / McGraw-Hill
OS/2 for Dummies (2.1)                           IDG
OS/2 for Non-Nerds                               New Riders
OS/2 Inside & Out (2.1)                          Osborne / McGraw-Hill
OS/2 Instant Reference Book                      Sybex
OS/2 Secrets and Solutions                       Sybex
PC Learning Labs Teaches OS/2                    Ziff-Davis
Quick Reference Guide for OS/2 2.1               DDC
Real-World Programming for OS/2 2.1              Sams
The Shell Collection: OS/2 2.1 Utilities         Van Nostrand Reinhold
Stepping Up to OS/2 2.1                          Abacus
Teach Yourself OS/2 2.1                          MIS Press
Teach Yourself OS/2 in 1 Week                    Sams
10-Minute Guide to OS/2 2.1                      Alpha
Thinking Person's Guide to OS/2 2.1              QED
Using OS/2 2.1 Special Edition                   Que
Using Workplace OS/2: Power User's Guide         Van Nostrand Reinhold
Van Wolverton's Guide to OS/2                    Random House
Writing OS/2 Device Drivers in C, Third Edition  Van Nostrand Reinhold
Your OS/2 2.1 Consultant                         Sams

z
----

Inside OS/2 2.1                                  New Riders
The OS/2 2.1 Corporate Programmer's Handbook     Van Nostrand Reinhold

jen
-----
DA(m)N NEWS 1-03                   Str. 37                   4 Dec 1993


Instant OS/2                                     TAB / McGraw-Hill
The OS/2 2.1 REXX Handbook                       Van Nostrand Reinhold
OS/2 2.1 Workplace Shell Programming             Random House

listopad
--------

OS/2 Batch Files to Go                           TAB / McGraw-Hill

prosinec
--------

OS/2 2.1 Quick Reference Guide for End Users     QED
OS/2 2.1 Red Book for Developers                 Que
OS/2 2.1 Red Book for Power Users                Que
OS/2 and Networking                              QED
OS/2 Presentation Manager Programming            Ziff-Davis
OS/2 Presentation Manager Programming with       QED
  IBM C++
REXX Programming Under OS/2                      QED
The Ultimate OS/2 Programmer's Manual            TAB
Windows and OS/2: The GUI OOUI War               Van Nostrand Reinhold

leden 1994
----------

The Design of OS/2 2.1                           Addison-Wesley
The OS/2 2.1 Application Developer's Guide       Van Nostrand Reinhold
OS/2 Database Manager's Handbook                 QED
OS/2 V2 PM Programming in C++ Using the User     Van Nostrand Reinhold
  Interface Class Library

nor 1994
---------

Objective Thinking for OS/2                      Van Nostrand Reinhold
Objects for OS/2 2.1                             Van Nostrand Reinhold

bezen 1994
-----------

OS/2 2.1 and NetWare Programming                 Van Nostrand Reinhold
Rightsizing to OS/2 2.1                          New Riders


1995
----

OS/2 for the Impatient (January 1995)            Addison-Wesley
OS/2 Connectivity (early 1995)                   Wordware

Neurit datum
--------------

Advanced OS/2 Workplace Shell                    QED
Independent Platform Coding                      IBM / McGraw-Hill
DA(m)N NEWS 1-03                   Str. 38                   4 Dec 1993


Inside OS/2 2.1, Third Edition                   New Riders
Object Vision for OS/2 2.1                       QED
OS/2 2.1 Developing, Porting, and Testing        QED
   Applications
OS/2 Communications Manager 2.0                  QED
OS/2 Connectivity                                QED
OS/2 Demystified                                 TAB
OS/2 in the Fast Lane (2.1 edition)              New Riders
OS/2 User's Guide to Installation,               QED
   Configuration, and Use
Voodoo OS/2                                      Ventana

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 39                   4 Dec 1993


                       OS/2 Klub zaloen na PRODIGY

IBM zaloilo OS/2 Club na PRODIGY, kter je dostupn bez dodatenhc
plateb pro vchny leny PRODIGY a nabz nsledujc servis:

o  Aktuln novinky a informace o OS/2
o  Databzi otzek a odpovd obsahujc odpovdi na mnoho z asto se
   vyskytujcch otzek o OS/2
o  Seznam dostupnch OS/2 aplikac, jmen firem a telefonnch sel
o  OS/2 Exchange frum ve kterm je mon umstit poznmky a odpovdt
   na otzky ostatnch o mnoha OS/2 zleitostech. IBM OS/2 Support
   bude t zodpovdat otzky v tomto fru.
o  E-mail pro posln zprv, chybovch hlen i otzek pmo na
   OS/2 support pedstavitele v IBM.
o  Download monost pro IBM a ne-IBM soubory kter zahrnuj oznmen,
   adie, opravn soubory, hry, demonstrace, shareware, ukzkov aplikace,
   a mnohem vce

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 40                   4 Dec 1993


===============================================================================
                                   SHAREWARE
===============================================================================


DDJ11A92.ARJ    003     DR. DOBBS JOURNAL C PROGRAMMING NEWSLETTER MAGAZINE

                        Dr.Dobbs Journal, DDJ11A92 contains:
                        GUIXVT
                        GUIISL
                        GUIAUT
                        GUIWNX   SIZING UP GUI TOOLKITS
                        PIEMENU  PIE MENUS FOR WINDOWS
                        DIALOG   DYNAMIC DIALOG BOXES IN C++
                        GARBAGE  GARBAGE COLLECTION FOR C PROGRAMS
                        EXPWIN   Examining Turbo Pascal for Windows
                        PORT_UI  DESIGNING PORTABLE USER INTERFACES
                        UNDITH   CONVERTING DITHERED IMAGES BACK TO GRAY SCALE
                        TVTIME   EXTENDING TURBO VISION
                        RTDEBUG  DESIGNING A REAL-TIME DEBUGGER
                        WIDGET   DEBUGGING MOTIFF WIDGETS
                        CPPLIB   DEVELOPING A PORTABLE C++ GUI CLASS LIBRARY
                        DFLT14   PROGRAMMING COLUMN, D-Flat
                        CPROG    C PROGRAMMING COLUMN, D-Flat++
                        HCALC2   STRUCTURED PROGRAMMING COLUMN, HCALC.PAS
                        GRPPROG  GRAPHICS PROGRAMMING COLUMN, line drawing
                        XSHRP21  GRAPHICS PROGRAMMING COLUMN, X-Sharp

DDJ0992.ARJ     003     DR. DOBBS JOURNAL C PROGRAMMING NEWSLETTER MAGAZINE

                        Dr.Dobbs Journal, DDJ0992 contains:
                        POST     POSTMORTEM DEBUGGING, Windows, GPI
                        CORONER  POSTMORTEM DEBUGGING, reporting
                        WIN386   AN EXCEPTION HANDLER FOR WINDOWS 3
                        DB       YOUR OWN PROTECTED-MODE DEBUGGER
                        HRT      HIGH-RESOLUTION TIMING
                        CLISP    AN IMPROVED LISP-STYLE LIBRARY FOR C
                        REAL     DEBUGGING REAL-TIME SYSTEMS
                        TRACE    CRASH TRACEBACKS IN UNIX
                        UNLOAD   WINDOWS TOOLHELP, remove DLLs or programs
                        TDVIDEO  VIDEO-COMPATIBILITY INTERFACE FOR TD
                        DFLT14   C PROGRAMMING COLUMN, D-Flat
                        CPROG    C PROGRAMMING COLUMN, D-Flat HelpBox
                        GRPPROG  GRAPHICS PROGRAMMING COLUMN, texture mapping
                        XSHRP21  GRAPHICS PROGRAMMING COLUMN, X-Sharp
                        HCALC    Structured Programming Column, HCALC. PAS

G2V299B4.AJR    002     VIRUS ANTIVIRUS GOBBLER DOS

                        Beta version (2.99) of Anti-Virus Package called
                        Gobbler. OS/2 is probably disliked environment,
                        hangs in the session.

INTELML.ZIP     002     COMPUSERVE INTEL E-MAIL CIS HELP

                        How to e-mail messages from CIS to Intel's corporate
DA(m)N NEWS 1-03                   Str. 41                   4 Dec 1993


                        mail system. Intel uses X.400 adressing.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 42                   4 Dec 1993


===============================================================================
                                    Inzerce
===============================================================================


Ŀ
                   TM            * VT data spol. s r.o. *      
                             U skldky 3/958     Fgnerova 4/I  
                       PRAHA 9-Libe       VYSOK MTO    
                     190 00              566 01         
                                FIDO 2:423/82.3     FIDO 2:423/82       
   AUTHORIZED DISTRIBUTOR                                               
Ĵ
Pha:              tel./fax 02/828455, tel.: 02/828510                    
VM :     tel./fax 0468/21861, tel.0468/22324, BBS 0468/22527             


                                  vbr z

     MALOOBCHODNHO CENKU                             LISTOPAD '93
     ---------------------                             ------------
                             ceny bez DPH 23%

                      notebooky NoteStar ady NP 700
                      ______________________________

NP 740           486SX/25, 4 MB RAM, mono                        39 750,-
NP 741           486SX/33, 4 MB RAM, mono                        44 980,-
NP 743           486DX/33, 4 MB RAM, mono                        47 250,-
NP 743 S                             STND color ( DualScan )     69 980,-
NP 746           486DX2/66, 4 MB RAM mono                        55 980,-
NP 746 S                             STND color ( DualScan )     79 980,-

                     vymniteln HDD pro serii NP 700
                     --------------------------------
HDD 80 MByte                                                      8 420,-
HDD 120 MByte                                                    10 190,-
HDD 200 MByte                                                    14 190,-
HDD 340 MByte                                                    24 540,-
HDD 120 MB/100 G       odolnost proti nrazu 100 G               12 140,-
HDD 200 MB/100 G       odolnost proti nrazu 100 G               17 140

Mono dokoupit k NP 900, NP 700 a sestavm PC :
MS DOS v6.0 + Windows 3.1 ( instalovno na HDD )                    750,-
MS DOS v6.0 + Windows 3.1 LAN    --"--                            1 110,-

V cen : tot jako u NP 900
Roziujc moduly : Modem, Faxmodem, Ethernet PCMCIA, CAR adapter, extern
                     baterie, intern  baterie, dodaten nap.  zdroj, 4 MB
                     RAM modul, 8 MB RAM modul, intern 8 MB RAM modul


Dle nabzme : zkladn sestavy pota, disky, mechaniky, karty, adie,
                koprocesory
                monitory,  myi,  snmae   r.kdu,  tablety,  streamery,
                fax-mod. karty, nap. zdroje
DA(m)N NEWS 1-03                   Str. 43                   4 Dec 1993


                tiskrny SEIKOSHA, STAR, EPSON, CANON, HP, TI, CITIZEN
                potaov st
                dal produkty Hewlett-Packard
                faxy, telefonn pstroje,  zznamnky, telefonn stedny,
                koprky a dal kancelskou techniku


                            ! HLEDME DEALERY !

          ~~   Dealerm nabzme velmi vhodn podmnky !!!    ~~


     Dal  informace  (  obshlej  seznam  prodejc  )  viz nae reklama
v asopisech  COMPUTERWORLD,  CHIP  a  dalch,  nebo  na  tel. 0468/22324,
02/828510.
     Dotazy  NETMAILEM na  2:423/82.3 -  Jackie point.  Na podn  nechm
poslat cenk, proti zavoln i velkoobchodn. A ten je velmi zajmav !!

     Cenk mono sthnout i na na BBS - 0468/22527 !!!

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 44                   4 Dec 1993


===============================================================================
                              Legrace a legrcky
===============================================================================


                             Zkratky a symboly

BRB         Be right back (hned zptky)
BTW         By the way (mimochodem)
B4N         Bye for Now (prozatm nashle)
CIS         Compuserve Information System
CU          See you (na vidnou)
CUL8R       See you later (na vidnou pozdji)
DL or D/L   Download, transmit to yo
FURTB      Full up ready to burst (about hard disk drives!)
FWIW        For what it's worth (pro to za co to stoj)
FYI         For your information (na vdomost se dv)
GIGO        Garbage in, Garbage Out (bordel dovnit, bordel ven)
GLGH        Good Luck and Good Hunting (hodn tst a dobr lov)
IAE         In any event (kdykoliv)
IMO         In my opinion (dle mho nzoru)
IMHO        In my humble opinion (dle mho skromnho/uctivho nzoru)
IOW         In other words (jinak eeno)
MLA         Multiple Letter Acronym (vceznakov zkratka)
OIC         Oh, I see (aha)
OTOH        On the other hand (jinak)
PITA        Pain in the ... (bolest v...) (mm ho pln zuby)
PMFBI       Pardon Me for butting in (pardon pro vskoen do debaty)
ROF,L       Rolling on floor, laughing (valce se na zemi, smjce se)
RSN         Real soon now (opravdu brzy)
RTFM        Read the f...ing manual (or message) (st zasran manul)
SNAFU       Situation normal, all "fixed" up (vechno OK, vechno spraveno)
SWMBO       She who must be obeyed (ta co j musm poslouchat) (moje star)
TIA         Thanks in advance (dky pedem)
TLA         Three Letter Acronym (now surpassed by MLA) (t pismenn zkratka)
TTL4N       Thats the lot for now (to je dost pro te)
UL or U/L   Upload, send to the BBS
WOFTAM      Waste of Flaming time and money (koda nadvek a penz)
WYSIWYG     What you see is what you get (co vid je co dostane)
WYSBYGI     What you see before you get it (co vid ne to dostane)
WYGIWYPF    What you get is what you pay for (dostane co jsi zaplatil)

<g> or <grin>   To mark a joke or sarcastic comment (vtip) (ironie)
<sigh>

^^      happiness (tst, spokojenost)
^^;     embarrasment (pobaven, div)
;;      sadness (smutek)

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 45                   4 Dec 1993


                           Jako za starch as
                        (Pouze opt dal parodie)

st III


Stih na:  Stejn podivn obn drha jako posledn. Fanfrovit hudba
Stih :  Interir, mstnost porad.

Spock:  Po prohldce historickch daj Enterprise, vm e jsem schopen
        nyn pochopit jak to Q udlal e jsme zde. Nejvce dleit je fakt
        podivnho chovn Data.

Data:   Snail jsem se snad o nahrazen jmna "Wilbur" pro "Wesley"?

Spock:  Spolu s ostatnmi vcmi. Zjistil jsem pravidelnost ve zvltnosti va
        ei. Tyto pravidelnosti maj vysok stupe souvislosti s televiznmi
        poady v posledn sti pozemskho dvactho druhho stolet.

Scotty: Ale pane Spock, jak tohle objasuje varovn Q o naem objeven se
        zde?

Spock:  Vypad to e Q vyuil vhody shod mezi starou a novou sri.
        Napklad, ob maj polovinho cizince a velice inteligentn
        postavu bez emoc.  Nkter ze starch pbh byly oiveny v
        rannch misch tto lodi, zejmna zklamav pepracovni "Naked
        Time". Obvody velitele Data jsou zejmna citliv na rozruchy tohoto
        druhu.  Pouvn ostatnich hesel a fakt je zpsobeno veobecn
        mizernm zpsobem prolnn televiznch program.

Picard: Ale nai lid pracuj na oddlen se od starch sri. My jsme
        daleko mn nsilnit a mme pleitost pro mn konflikt mezi
        bnmi postavami.

Spock:  Pravda, ale nae dvoj obsazen zjevn existuje dky zajmav form
        pitahovn mezi sebou, podobn jako dv hvzdy obhajc se
        navzjem.  Potejte tak s uskutennmi pokusy vytvoit vkonnho
        dstojnka napodobujcho Kirkv hyperensk komplex. (Riker se
        oije, vdn e se mu alespo podailo odstranit plnovous). A
        tak, kdykoliv toto obsazen se jev jako na cest vytvoen vlastn
        identity, v tom okamiku se objevuje star obsazen. Sledujte
        napklad, objeven Whorfova pedka pi posledn cest kapitna
        Kirka a pemnu Starfleet diskutovanu pi mrovm vyjednvn s
        Klingonskm csastvm.

LaForge:Take vlastn kte e jsme si natolik podobn, e Q byl schopen
        kombinovat nae dva svty?

Spock:  Pesn.  Nastavil nae pbhov linky na zniujc katastrofick kurs
        kter dn z obsazen nejspe nepeije.

Kirk:   Jedin...pokud se nm poda se opt oddlit jedni od druhho.

Spock:  Mme mlo asu. Odhadl jsem e pokud se nm nepoda se oddlit
        zpt na dv samostatn literrn entity brzy, n vskyt v tomto
        prosted bude nezvratn. Jakkoliv akce konan kmkoliv z ns mus
DA(m)N NEWS 1-03                   Str. 46                   4 Dec 1993


        bt provedeny s ohledem na akce ostatnho obsazen . Sloitost prce
        tohoto druhu se velice brzy stane pli pro vesmr k unesen a
        svt jak jej znme se pibl ke konci.

Data:   Jak dost asu mme k formulaci een pro tento problm?

Spock:  Jsme nuceni akceptovat podivn subjektivn strukturu asu, periody
        mezi msi nazvanm "komern pestvky:. Nkter se ji uskutenily.
        Pokud se uskuten dal dv i vce bez nalezen een, nae dva
        svty se neodvratn slou.

Picard: Ve je tedy jasn. Je zejm e naveme kontakt s obyvateli Taos
        IV a zskme novou djovou linku od nich.

(podivn zvuky z komuniktoru)

Uhura (z komuniktoru):
        Kapitne....

Picard a Kirk:  Ano?  (zraj jeden na druhho)

Uhura (komuniktor):
        Zachytili jsme prv penos z Taos IV na Ferengi lo.

Kirk:   Co je v nm?

(rvakovit zvuky z komuniktoru)

Whorf (komuniktor):
        Taos IV prv akceptoval vlun kontrakt ohledn zsoben
        Ferengi povdkami o burzovnch maklch.

Picard: Sakra. Budeme na mstku bhem chvle.

Stih:  Mstek.  Vichni tam kde byli posledn, pouze Scotty je na
        strojovm stanoviti a Dr. Crusher stoj vedle kapitnova kesla
        (Kirk pobl, pochopiteln). Komunikan panel je obklopen pytli
        psku a Uhura a Worf maj na hlav helmu.

Picard: Jak Ferengi zskali kontakt?

Whorf:  Nabdli sex, drogy a rock&roll. Kontrola naich potaovch
        zznamu ukazuje e toto zbo je nejastji pouito k zskni
        pozornosti umlc.

Kirk:   Jakkoliv ance pout tut taktiku?

Uhura:  Ne, pane. Taos IV ji podepsal vlun kontrakt s Ferengi. Takovto
        kontrakt by musel bt poruen abychom mohli zahjit vyjednvn.
        Budeme muset jednat pmo s Ferengi.

Kirk:   Slyeli jsme nco od nich?

Uhura:  Pouze katalogov objednac list pane. Odmtaj prodvat upraven
        djove linky bez uritho vyjednvn.

DA(m)N NEWS 1-03                   Str. 47                   4 Dec 1993


Picard: Jak dlouho tohle me trvat?

Whorf:  Nejmn dva tdny. pane.

Kirk:   Spock?

Spock (drbe se na hlav):
        Podle mch propot, jsme velice blzko konern pestvky. Mlo by
        k tomu dojt kdesi v ptch deseti dcch a bude uvedena
        dramatickm akordem.

Riker:  Take jsem odsouzeni k strven zbytku naich pbh dohromady.

Picard: Meme ale ziskat njak ten as pokud nebudeme dodvat dialogy.
        Nikdo nic nekat, Pane Whorf, dejte m na komuniktor, Kad dka
        je te dleit.

Whorf:  Ano pane...pardon, promite pane.

(zvuk, Picard si upravuje uniformu, Kirk pzuje)

Picard: Zde mluv kapitn.

Kirk:   Ne, ZDE mluv kapitn.

(oba na sebe zraj)

Picard: Nae zsoba dialogu je ponkud omezen......

Kirk:   take vichni lenov posdky se budou stranit nedleit konverzace.
        To je vechno (ukazuje konec komunikace)

(vstupuje Wesley)

Wesley: au, nazdar hoi!

Vichni:Zklapni, Wesley!

(dramatick fanfry)

Chekov:  Sakra.

Stih na premira Klause....

-------------------------------------------------------------------------------
DA(m)N NEWS 1-03                   Str. 48                   4 Dec 1993


DA(M)NNEWS, elektronick obasnk


Vydvno nepravideln , neperiodicky a bez zruk (zpravidla msn a 
tdenn), pspvky jsou neplacen a neznamenaj nutn tot co nzor 
vydavatele, odpovdnost za zveejnn materily je pln na autorovi, 
zveejnn materily zstvaj majetkem autora. Ppadn petisky i 
pouit zveejnnch materil je mon pouze po zskn souhlasu autora.  
Petisky a pouit vech materil oznaench .DD. je explicitn povoleno 
pokud nepjde o komern vyuit i komern prosted.

en DA(M)NNEWS je bezplatn a jednotliv slo m stanovenu pevnou cenu 
0.00 K (+ 0.00 K DPH). Cenu doporuenou nezavdme, protoe se j stejn 
nikdo nedr. O cen maximln ani nemluv. Je vslovn zakzno it 
DA(M)NNEWS v jakmkoliv komernm prosted bez svolen vydavatele (pod 
pojmem komern prosted me bt zahrnuto i vydn CD-ROM, shareware 
kolekce na disketch, CompuServe Information Service, zcela placen BBS a 
ostatn komern aktivity). 


-------------------------------------------------------------------------------
