                                
                                  
                           
                                       
                                  
  Ronk 1, slo 5                                        18 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  ...................................................................  5
   Novell NetWare otzky a odpovdi, duben 1993  ...........................  5
3. CLIPPER  ................................................................ 11
   Clipper User Groups recognized by CA  ................................... 11
   CLIPPER 5.x pole, pole a zase pole  ..................................... 17
4. Hardware  ............................................................... 20
   FUJITSU Model M2611S/SA/SB Nastaven  ................................... 20
   Seagate ST 138N, parametry  ............................................. 21
   Maxtor LXT-200S nastaven  .............................................. 21
5. OS/2  ................................................................... 23
   Novell NetWare, OS/2 a IBM TCP/IP - vechno dohromady  .................. 23
   OS/2 2.1 co je novho?  ................................................. 28
   OS/2 a HRY!!!!!!!!!!!! st 1  .......................................... 32
6. DOS (Dumb Operating System)  ............................................ 39
   MS DOS 6.0, DoubleSpace, ACR a ECR  ..................................... 39
7. Legrace a legrcky  ..................................................... 41

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


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


D'Bridge 1.51 technical information

      6.0  DISK-BASED QUEUE
      ---------------------


      D'Bridge has a disk-based queue for XMAIL, file-transfer and AREAFIX
      requests.  This queue works independently of the NETmail area and may
      be accessed by user-written programs.  All queue entries reside as files
      in the specified "queue" directory; the address is encoded in the file-
      name as base-36 numbers.


      The filenames of queue entries use the following format:

         t-zzzNNN.nnn           H-00102X.00G
             -or-                   -or-
         t-POINT-ppp            H-POINT.005


      Where: t     is the entry type (A/B/C/H/I/N/Q)
             zzz   is the base-36 ZONE address
             NNN   is the base-36 NET address
             nnn   is the base-36 NODE address
             ppp   is the base-36 POINT address



      Base-36 numbers use the digits 0-Z to represent the numbers.  You will
      notice from the structure that the address is either 3-dimensional (ZONE,
      NET and NODE) or a POINT-address.  It is impossible to have a queue entry
      for a point of another system.


      The following queue entry-types are currently defined:


         A - AREAFIX request packet

         An "A" queue entry is an outbound AREAFIX request; this is a NETmail
         message that is destined for the specified system.  It must always be
         associated with a "Q" entry-type that designates the packet priority.
         This packet is generated by using the REQUEST ECHOMAIL LINK, ALT-R
         option of D'Bridge.

         B - Inbound AREAFIX request/New ECHOmail link control file

         The "B" queue entry indicates either an inbound AREAFIX request or
         a request issued using the NEW ECHOMAIL LINK, ALT-N command.  These
         requests are usually processed immediately, but if there is a hold
         on ECHOmail forwarding because of a disk-space limit, these files may
DA(m)N NEWS 1-05                   Str. 2                   18 Dec 1993


         accumulate.  The "B" queue entries are text files in the following
         format:

            <priority><rescan><area listing><manual override>
            <area name>
            .
            .
            <area name>


            <priority>         is either N, I, C or H
            <rescan>           Should the area be rescanned?  Y or N
            <area listing>     Should an area listing be sent?  Y or N
            <manual override>  Is this a manual (ALT-N) entry?  Y or N
            <area name>        Either + or - then the ECHOmail tags to add
                               or remove from your LOCAL/ECHOMAIL AREAS screen.

         "B" queue entries are processed when an ECHOmail scan is done; any
         external program may add entries to the disk-based queue.


         C - Crash priority XMAIL

         "C" queue entries are XMAIL (compressed mail) packets with CRASH
         priority.  These will be sent during any event including the UNEVENT
         to the specified system.  This file contains any number of outbound
         mail packets.


         H - Hold priority XMAIL

         "H" queue entries are XMAIL packets with HOLD priority.  These will
         never be sent unless there is a forced priority override or the
         operator uses the VIEW/MODIFY QUEUE command to force D'Bridge to call
         the specified system.  Typically, HOLD priority XMAIL is picked up
         by a "poll" from the destination system.

         I - Immediate priority XMAIL

         "I" queue entries are XMAIL packets with IMMEDIATE priority.  These
         will be sent immediately during any event; this priority overrides
         crash and all immediate queue entries will be sent before any other
         outbound traffic.



         N - Normal priority XMAIL

         "N" queue entries are XMAIL packets with NORMAL priority.  They will
         never be transmitted during the UNEVENT unless a forced priority has
         been specified or the operator uses the VIEW/MODIFY QUEUE command to
         force it to send.



         Q - General purpose outbound queue
DA(m)N NEWS 1-05                   Str. 3                   18 Dec 1993


         A "Q" queue entry is a text file that contains any number of lines,
         each of which contains one of the following formats:


            <priority> P

            A "P" entry indicates a "poll" with the specified priority.


            <priority> T <file path> <transmit filename>

            A "T" entry indicates an outbound file transmission.   Wildcards
            are not allowed here; all entries must specify full filenames and
            whatever programs add entries to the queue must do the wildcard
            expansion themselves.  This queue structure requires that both the
            full path of the file be specified as well as the transmitted file-
            name; this allows files to be transmitted different filenames than
            they have on disk.


            <priority> F <filename>

            A "F" entry indicates a file request.  Filenames may include a
            path, but the file will be received into the inbound files
            directory unless you are requesting from a SEAdog or "Bark-style"
            system.  If the file exists in the specified path, an update-
            request will be generated, only receiving the file if a newer
            version exists.

            <priority> R <packet path> <transmit packet name>

            An "R" entry indicates an outbound AREAFIX request.  This is always
            associated with an "A" queue entry which contains an actual NETmail
            packet.




         The disk-based queue was designed to allow user-written programs to
         transmit files and XMAIL easily without using the DBUTIL program.
         Following is a sample routine to generate the queue entry filenames
         based on kind, ZONE, NET, NODE and POINT:


           function qname(kind : char;
                          zone,
                          net,
                          node,
                          point : integer) : string;

           function base36(n : integer) : maxstring;
           var d36 : string[36];
           i,j,k : integer;
           begin
             d36:='0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ';
             i:=n div 1296;
DA(m)N NEWS 1-05                   Str. 4                   18 Dec 1993


             j:=n mod 1296;
             k:=n mod 36;
             j:=j div 36;
             base36:=d36[i+1]+d36[j+1]+d36[k+1]
           end;

           begin
             if point<>0 then
               qname:=kind+'-POINT.'+base36(point)
             else
               qname:=kind+'-'+base36(zone)+base36(net)+'.'+base36(node)
           end;

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 5                   18 Dec 1993


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


               Novell NetWare, Otzky a odpovdi duben 1993

SUNNYVALE

Q:   Can I use a 486 machine with Access Server?

A:   Yes.  Many 486 machines have been tested and certified.  End users
     have also reported successful installations on 486/50 and 486/66
     machines.

Q:   Can the Access Server be installed on a machine with a built-in Super
     VGA?

A:   No.  Access Server does not support Super VGA.  Either disable the
     Super VGA mode or substitute another video adapter.

Q:   After I started running NACS 3 (or NetWare for SAA v1.3), my NetWare
     v3.11 server occasionally abends.  Is there a connection?

A:   Yes.  The SPXFIX NLM, required for both NACS 3 and NetWare for SAA
     v1.3, which ships with the two products, may cause server abends.
     SPXFIX2, contained in STRTLI.ZIP found on NetWire NOVLIB 9, resolves
     the issue.  STRTLI.ZIP also contains other files that need to be used
     with SPXFIX2.

Q:   I am using the Novell Synchronous Adapter for SAA with NetWare for SAA
     v1.3.  When R3SDLC is loaded, the following message is displayed:

          DLCI Error: Unable to Attach Logical Board.

     What am I doing wrong?

A:   NetWare for SAA v1.3 requires the use of a logical board name.  When a
     host connection is configured in CSCON, one of the parameters (for
     Ethernet, Token Ring, and SDLC) is the Logical Adapter Name.  This
     Logical Adapter Name should match the NAME= statement in the "LOAD
     <driver>" statement in the AUTOEXEC.NCF.  For example, if the LOAD
     statement in the AUTOEXEC.NCF is "LOAD R3SDLC NAME=BOARD_NAME," then
     BOARD_NAME would be entered in CSCON as the Logical Adapter Name.

Q:   I am trying to use the LU6.2 API that ships with the NetWare 3270 LAN
     Workstation; however, am confused about what APIs are available.  What
     is the difference between CPI-C and APPC?

A:   NetWare 3270 Workstation's and NetWare for SAA implement two LU6.2 API
     interfaces: CPI-C and APPC.  Both of these APIs have been implemented
     on NetWare for SAA and WSLAN (both DOS and Windows).

     NetWare for SAA, supports both API interfaces in PU2.0 and PU2.1
     profiles.

DA(m)N NEWS 1-05                   Str. 6                   18 Dec 1993


     Which API to use and where to load it depends on the Application
     Program Interface (API) your application is written to and where that
     application is run.  For example, if the application is written for
     CPI-C and runs on DOS, then the CPI-C interface needs to be loaded
     under DOS (CPIC_SAA.NLM is not required).

     The CPI-C API runs on top of the APPC/LU6.2 protocol boundary.
     Therefore, to run a CPI-C application, the APPC/LU6.2 interface is the
     required.

     To set up the CPI-C interface, run the SIUTIL.EXE to configure a Side
     Information File.  This file is needed by the CPI-C Application
     Subsystem to negotiate an LU6.2 session.

Q:   I want to use the OS/2 2.0 Communication Manager to provide 3270
     terminal emulation to my OS/2 2.0 workstation's.  I have heard that
     NetWare for SAA v1.3 can be configured to support these clients as
     downstream PUs (DSPUs).  How is this configured?

A:   Currently, only downstream PUs with the following topologies are
     supported: LLC8022 over Token Ring, Ethernet, and QLLC over X.25.  For
     downstream PU support, only one card of the three listed above can be
     used.

     One Netware for SAA profile performs all SNA communications through
     one adapter only.  The upstream system and any downstream PUs to be
     supported by this profile must be accessible by NetWare for SAA
     through that one adapter.  Boards and protocols cannot be mixed.

     For example, if NetWare for SAA is attached to the upstream
     system through QLLC, all downstream PUs may only be attached
     through QLLC.  NetWare for SAA also must be able to
     communicate with both the upstream system and downstream PUs
     using the same X.25 adapter.

     This information is discussed on pages 4 and 5 in the SAA 1.3
     Planning Guide.

PRODUCT INFORMATION

Q:   Will LAN WorkPlace for DOS do IP Tunneling through PPP to an IP router
     and on to a NetWare v3.11 server?

A:   Yes.  When using ODI, however, the first LAN driver needs to bind to
     PPP and the second to IP Tunneling.  Burstmode is recommended for this
     configuration.

Q:   What is the maximum password length in NetWare v3.11?

A:   127 characters.

Q:   I cannot upgrade from Link/X.25 to WAN/Links.  Why?

A:   The boards used with Link/X.25 do not work with WAN/Links.

Q:   Can Multi-drop modems be used with WAN/Links?
DA(m)N NEWS 1-05                   Str. 7                   18 Dec 1993


A:   No.  Multi-drop modems use multi-drop lines, which is not
     supported in WAN/Links.

Q:   Does NetWare SFT III v3.11 support NetWare Global MHS?

A:   Yes.

Q:   What is the maximum number of volumes that can be mounted with
     NFS Client?

A:   The maximum number of volumes that can be mounted with NFS Client is
     26.  However, because each volume must be mapped to a drive, this
     maximum is dependent on what is already mapped.

     For example, if A:, B:, and C: drives are mapped to local drives, and
     F:, G:, and H: drives are mapped to network drives, 20 drive letters
     are left.  Therefore, 20 volumes may be mounted.

Q:   What Tape Backup units are compatible with DataClub (Classic
     and Elite)?

A:   Anything that is AppleTalk Filing Protocol (AFP) compliant.

Q:   Can a Macintosh user access a plotter on the network?

A:   No.  Drivers are not available to allow a Macintosh user to
     see the plotter.  A plotter must be directly connected to the
     machine for the user to access it.

Q:   Will LAN Workplace for Macintosh v1.3 recognize a Quadra's
     built-in Ethernet card?

A:   Yes.

Q:   In LAN WorkGroup are the user connections concurrent or
     defined?

A:   IP addresses are assigned to the hardware and not to the users.
     Addresses are assigned in LWGcon and during the first login bootP
     assigns the machine the first available IP address.  Each time after
     the first login, the machine is given the same address whenever it
     requests IP services.  Remove the users name from LWGcon when needed
     to free up the address so it can be reassigned by BootP.

Q:   Can a Null Modem be used to connect to a file server running
     Novell's messaging products?

A:   Yes.  During the installation of MHS, Null Modem is an
     available menu option when configuring communications between
     boxes.

Q:   In NetWare v3.11, print job configurations created in PRINTCON are
     stored in each users' mail directory.  Where are these print job
     configurations stored in NetWare 4.0?

A:   This information is stored in the users' object as part of the
DA(m)N NEWS 1-05                   Str. 8                   18 Dec 1993


     Directory Services database.  A print job configuration can be created
     for an OU container object and will be used by default for any user
     object contained in the OU.

Q:   Has the accounting feature of printing in NetWare 4.0 been enhanced to
     allow for charging a user on a per page printed basis?

A:   No.

NETWARE LITE

Q:   Separate copies of NetWare Lite are installed on each machine;
     however, I am still getting a software violation message.  Why?

A:   This can be caused by one of two things:

     1.   Additional copies of SERVER.EXE or CLIENT.EXE are located
          outside the NWLITE directory.

     2.   The same copy of NetWare Lite is installed on more than
          one computer.

     This can be resolved by doing the following:

     1.   Type "tree server.exe" from the root to locate additional
          copies of SERVER.EXE on the system.  Repeat this for
          CLIENT.EXE.

          If more than one copy of either SERVER.EXE or CLIENT.EXE
          are found, delete any copies residing outside the NWLITE
          directory.

     2.   If only one copy of each of these files is found, use DOS
          compare to verify unique NetWare Lite copies on each
          machine displaying the error.

          a.   Place the NetWare Lite installation disk in the
               floppy drive.

          b.   Execute the following at the command line for the
               SERVER.EXE file (if the floppy diskette is in the
               A: drive):

                    comp a:\server.exe c:\nwlite\server.exe

          c.   Repeat Step b for the CLIENT.EXE file.

          If the files are unique, there will be a 4 byte
          difference in the message returned by the compare
          command.  If the files are the same, check the other
          machine by following steps a through c above.  There
          should be a match.  Find a copy that does not match any
          systems, and reinstall that copy on one of the offending
          systems.

Q:   The message "Can't print to LPT1" continues to appear when
DA(m)N NEWS 1-05                   Str. 9                   18 Dec 1993


     printing.  What should I do?

A:   Apply GETATRIB.PAT from L11U03.ZIP found on NetWire NOVLIB 10.

Q:   A print job was sent to the printer but never printed.  The
     NetWare Lite print queue was also empty.  What should I do?

A:   Apply LPTSTAT.PAT from L11U03.ZIP found on NetWire NOVLIB 10.

Q:   While using a database program, the client machine locks.  Now when
     the program is run I get a "file already open" error.  What should I
     do?

A:   Apply CLOSEFIL.PAT from L11U03.ZIP found on NetWire NOVLIB 10.

Q:   I have printing problems where either the print job does not
     print correctly or my machine locks.  What can I do to resolve
     this problem?

A:   Apply INT28FIX.PAT from L11P03.ZIP and CLPRINTR.PAT from
     L11U03.ZIP found on NetWire NOVLIB 10.

DRDOS

Q:   Is DR DOS 6.0 compatible with QEMM386 and other third-party memory
     managers?

A:   Yes.  DR DOS 6.0 works well QuarterDeck QEMM386, Qualitas 386MAX and
     BlueMAX, and Microsoft HIMEM.  Further details and examples can be
     found in the DR DOS 6.0 Optimization and Configuration Tips booklet,
     page 38-40.  This booklet is shipped with every package of DR DOS 6.0.

Q:   What commands can you get help on?

A:   All of them.  Type in the command as it would appear on the command
     line, but add a /H or /? after it.  This information can also be
     accessed using an electronic version of the manual called DOSbook.
     DOSbook can also provide assistance if you are not certain of how to
     configure your system using SETUP and batch file commands.

Q:   Can the SuperStor compression driver from DR DOS 6.0 be used with
     other versions of DOS?

A:   No.  A DR DOS 6.0 SuperStor compression driver should not be used with
     other versions of DOS, including DR DOS 5.0, MS-DOS 5.0, or MS-DOS
     6.0.  Drive compression is an integral part of DR DOS 6.0, requiring
     built in special awareness of the host operating system.

Q:   Why does the DR DOS FDISK take so much longer than other DOS versions
     to prepare my hard drive?

A:   DR DOS not only tests and prepares the drive for use, but also formats
     the drive.  As with other DOS versions, after using the DR DOS FDISK
     utility on a drive, there is no need to FORMAT the drive.

Q:   Can I change the way the DIR command displays a directory listing?
DA(m)N NEWS 1-05                   Str. 10                  18 Dec 1993


A:   Yes.  There are several DR DOS switches that change the appearance of
     the DIR listing.  For example, /2 displays the listing in double
     column format, /P pauses with each full screen, and /C instructs DR
     DOS to use these parameters as the defaults.  For example, if the
     command "DIR /2PC" is used, every time a DIR is executed, the DIR
     listing will display in double column format and pause with each full
     screen.  If the "DIR /2PC" statement is added to the AUTOEXEC.BAT
     file, the new DIR options will be set on bootup.

Q:   Why does CHKDSK show PENDING DELETE files after DELPURGE *.* is run?

A:   DELPURGE acts only on the current directory if executed without
     additional switches.  To purge all deleted files from the current
     directory and all subdirectories, use the following command from the
     root directory:

          DELPURGE *.* /S

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 11                  18 Dec 1993


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


                     Computer Associates Recognized
                     DOMESTIC CLIPPER USER GROUPS

NEBRASKA                Omaha Clipper User Group
            Coordinator:  Larry Leeds   (402)571-4362
            Box 4518, Omaha, NE  68104
            Meeting Time: Last Wednesday at 6:00 pm


NEW JERSEY              Clipper Club of New Jersey
            Coordinator:  Art Clancy   (908) 753-6575
            P.O. Box 2554
            1009 Kenyon Ave, Plainfield, NJ  07060
            Meeting Time: 3rd Monday at 7:30 pm


NEW MEXICO
            Northern New Mexico Clipper User Group
            Coordinator:  Bill Christison   (505) 983-2883
            Accuracy Consulting, Route 19 - Box 90X,
                          Santa Fe, NM  87505
            Meeting Time: 2nd Monday at 7:00 pm

NEW YORK                PADD - Clipper SIG
            New York Metro Clipper User Group
            Coordinator: James D. Moore 800-676-0038
            GAB Business Services
            Linden Plaza, 9 Compus Drive
            Parsippany, NJ  07054-4476
            Meeting Time: 4th Wednesday at 6:30 pm

            Shearson/American Exp Clipper User Group*
            Coordinator:  Blossom Scheinfeld   (212)341-4674
            Shearson-Lehman, 390 Greenwich, 5 West,
                          New York, NY  10013
            Meeting Time: To be determined

            Software Developers Association of Long Island
            Nassau Chapter (formally - PRO(Clipper)

            Coordinator:  Maria Parisi   (516)  696-2855
            Co-Coordinator:  Bill Krause
            Fax (516) 242-8283
            P.O.Box 305,    Holbrook, NY  11741
            Meeting Time: 4th Thursday  7:30 pm

            Suffolk Chapter(Suffolk County Clipper User Group)
           Coordinator:  James J. Occhiogrosso   (516)567-8494
            P.O. Box 305,  Holbrook, NY  11741
            Meeting Time: 4th Tuesday at 7:30 pm

DA(m)N NEWS 1-05                   Str. 12                  18 Dec 1993


            Capital District Clipper User's Group
            Coordinator:  John Kaufmann   (518)584-0907
            Certified Software, 44 White St, Saratoga Springs,
                         NY  12866
            Meeting Time: 2nd Tuesday at 2:00 pm

            Buffalo Clipper SIG
            Coordinator:  Andy Hay   (716)834-7200
            88 Minden Drive, Orchard Park, NY  14127
            Meeting Time: To be determined

            Clipper User Group of Upstate New York
            Coordinator:  Larry Dysert   (716)722-7115
            270 Quaker Meeting House Rd, Honeoye Falls, NY  14472
            Meeting Time: To be determined


NORTH CAROLINA
            North Carolina Clipper User Group
            Coordinator: Dr. Charles Beattie
            2925 Huntleigh Drive, Suite 201
            Raleigh, NC  27604
            Meeting Time: 2nd Wednesday at 3:00 pm
            Meeting Place:   North Carolina First flight
                                Technology Center, 2 Davis Drive
                     Research Triangle Park, NC



            Charlotte Area Clipper User Group
            Coordinator:  James Jernigan   (704)841-1275
            1519 F. Crescent Lane, Matthews, NC  28105
            Meeting Time: 3rd Thursday at 7:00 pm


OHIO                    Clipper Developer's of Greater Cleveland
            Coordinator:  Craig Howarth (216)656-8960
            3663 Kent Rd., Suite 2
            Stow, OH  44224
            Meeting Time: To be determined

            Dayton Clipper User Group
            Coordinator:  Keith Wire   (419)634-1065
            130 S. Johnson, Ada, OH  45810
            Meeting Time: 2nd Thursday at 6:30 PM


OREGON                  Northwest Database Society, Clipper SIG
            Coordinator:  Eric Lewis (503) 649-8140
            9675 SW 163rd Ave. Portland, OR  97007
            Meeting Time: 2nd Thursday at 7:00 pm

            Salem Clipper User Group
            Coordinator:  Jon Brammeier   (503)378-8303
            4606 12th Place So, Salem, OR  97302
            Meeting Time: 2nd Tuesday at 12:00pm
DA(m)N NEWS 1-05                   Str. 13                  18 Dec 1993


            Eugene Clipper User Group
            Coordinator:  Del Texley   (503) 345-6732
            Business Programming & Systems,
                         2121 Franklin Blvd, #3,
            Eugene, OR  97403
            Meeting Time: 1st Thursday at 7:00 pm


PENNSLYVANIA
            Erie Clipper User Group
            Coordinator:  Fran Mills   (814) 870-2995
            c/o Information Services, Erie Insurance Group,
                         100 Erie Ins. Pl,
            Erie, PA  16530
            Meeting Time: To be determined

            South Eastern Pennsylvania Clipper User
            Coordinator:  Aaron Rorstrom   (215) 254-9972
            P.O. Box 556, Southeastern, PA  19399-0556
            Meeting Time: 2nd Wednesday at 7:30 pm

            Clippers Developers Assoc of Pittsburgh
            Coordinator:  C.W. Kreimer   (412)271-5700
                          Fax: (412) 422-9101
            C.W. Kreimer & Associates, 6557 Bartlett,
                          Pittsburg, PA  15217
            Meeting Time: 4th Thursday at 7:00 PM


            Philadelphia Clipper User Group
            Coordinator:  Joe DiFrancesco   (215)828-4221
            1820 Butler Pike, Conshohoken, PA  19428
            Meeting Time: 2nd Tuesday at 7:00 pm


SOUTH CAROLINA
            Charleston Clipper User Group
            Coordinator:  Mike Jensen   (803) 884-6287
            236 Molasses Lane, Mount Pleasant, SC  29464
            Meeting Time: To be determined

            Greenville - Spartanburg Clipper Group
            Coordinator:  Bob Stribling   (803)877-5106
            116 Valley Forge Dr, Greer, SC  29650
            Meeting Time: 2nd Monday at 7:00 pm


TENNESSEE               Nashville Clipper Developer's Assoc.
            Coordinator:  Alan Ashendorf   (615)662-0322
            Fax: (615)646-7832
            Transformations, Inc., 488 Saddle Dr, Ste. 100,
            Nashville, TN  37221
            Meeting Time: 2nd Monday at 7:00pm

            Chattanooga Clipper User Group
            Coordinator:  Jeff Groover   (615)877-1167
DA(m)N NEWS 1-05                   Str. 14                  18 Dec 1993


            229 Sweetland Dr, Chattanooga, TN  37415
            Meeting Time: 2nd Monday  7:00pm
            Meeting Place:  Nashville Tech State College

            Memphis Clipper User Group
            Coordinator:  Nils Palleson 901-366-9673
            P.O. Box 241756
            Memphis, TN 38124-1756
            Meeting Time: 4th Monday at 7:00 pm


TEXAS                   Clipper User Group of Dallas
            Coordinator:  Allan Cavin   (214)506-3177
            c/o Pro-Sys, 1801 Royal Lane, Ste. 608, Dallas,
                          TX  75229
            Meeting Time: 1st Thursday at 7:00 pm

            Houston Clipper User Group
            Coordinator: David Vukovic
            3615 Durhill
            Houston, TX  77024-4107
            Meeting Time: 1st Wednesday at 7:00 pm
            Meeting Place:  Enterprise Tech Center,
                                         10th Floor, Innova Bldg.
                    20 Greenway Plaza, Houston, TX

            West Texas Clipper User Group
            Coordinator:  Dorman Blackman 915-699-1801
            4410 N. Midkiff Suite E-213
            Midland, TX  79705
            Meeting Time: To be determined


UTAH                    Utah Software Developers Assoc., Clipper SIG
            Coordinator:  Steve Klingler  (801) 484-7744
            c/o IMS Software Corp.
            449 E. 2100 South
            Salt Lake City,  Utah 84115
            Meeting Time:  4th Wed. 7:00 pm


VIRGINIA                Hampton-Roads Clipper User Group
            Coordinator:  Skip Kelley
            1012 Danbury Circle, Virginia Beach, VA  23464
            Meeting Time: 2nd Saturday at 10:00AM

            NARDAC Clipper User Group*
            Coordinator:  Don Neuens   (804)445-4397
            NARDAC - Bldg V-53, Naval Air Station, Norfolk,
                          VA  23511-6497
            Meeting Time: To be determined

            Washington Area Clipper User Group
            President:  Gerald Nelson
            P.O. Box 1303
            Vienna, VA  22183
DA(m)N NEWS 1-05                   Str. 15                  18 Dec 1993


WASHINGTON
            Clipper User Group of Seattle
            Coordinator:  Dr. Dan Lund (206) 328-1300 office
                         (206) 527-1025 home
            6014 Vasser Ave. NE,  Seattle, WA  98155
            Meeting Time: 2nd Thursday at 6:30 pm

            Boeing Clipper User Group*
            Coordinator:  Connie Goss 206-234-1427
            Mailing Address:
            Gary Jones
            2715 NW Pine Cone Dr.
            Issaquah, WA  98027
            Meeting Time: To be determined


WISCONSIN               Milwaukee Area Clipper User Group
            Coordinator:  Dan Lentz 414-274-4132
            c/o Johnson Controls, Inc., 507 E. Michigan St,
            Milwaukee, WI  53201
            Meeting Time: 3rd Wednesday at 6:30 pm

            Capitol City Clipper Club
            Coordinator:  Don Gibbard   (608)836-5075
            6627 Woodcircle East, Middleton, WI  53562
            Meeting Time: 3rd Thursday at 6:30 pm

*NOT OPEN TO THE PUBLIC


INTERNATIONAL CLIPPER USER GROUPS


AUSTRALIA               Clipper User Group of Sydney
            Coordinator:  David Miller   (02)749-1100
            c/o Database Systems, 8 Elizabeth St,
            Berala NSW, 2141  Australia
            Meeting Time: 2nd Tuesday at 6:00 pm

            Tasmania Clipper User Group
            Coordinator:  Brad Francis   02-396193
            PO Box 336, Kingston, 7051  Australia
            Meeting Time: To be determined

            Clipper User Group of Melbourne
            Coordinator:  Steve Forbes (613-553-0938 home)
            24 Highbury Avenue
            Moorabbin Vic 3189, Australia
            Meeting Time: 4th Thursday at 7:30 PM

BRAZIL                  Grupo de Usarios Clipper
            Coordinator:  Gil A. Petri, Jr.   55-11) 287-5865
            Av. Paulista, 509 - CJ. 1211, 01311-Sao Paulo  Brazil
            Meeting Time: Last Friday at 5:00 pm

CANADA                  Ottawa Clipper User Group
DA(m)N NEWS 1-05                   Str. 16                  18 Dec 1993


            Coordinator:  Erik Wynn  (613-256-5665
            638 Corkery Road
            Carp, Ontario
            KOA1L0, Canada
            Meeting Time: 3rd Tuesday at 7:00 PM

            Toronto Clipper User Group
            Coordinator:  Ross Chapel 416-882-6600 work
            60 Granton Dr., Unit 4
            Richmond Hill, Ontario L4B1H7
            Meeting Time: 2nd Tuesday at 7:00pm

            Vancouver Clipper Developers Association
            Coordinator:  Michael Li   (604) 667-4100
                          Fax: (604)685-5671
            P.O. Box 2688, 349 W Georgia St,  604-325-5648 work
            Vancouver, BC. V6B 3W8  Canada
            Meeting Time: 1st Tuesday at 7:00 pm

            Clipper User Group of Winnipeg
            Coordinator:  Brad Semenko   (204) 787-4656
            344 Cumberland Ave, #501, Winnipeg,
            Manitoba R3B 1P3  Canada
            Meeting Time: 3rd Tuesday at 7:00 pm

            Clipper User Group of Montreal
            Coordinator:  Sylvain Larche   (514) 335-5426
            Fax: (514) 335-6909
            IOSYS Technology, 540 Sherbrooke, Lachine,
            Quebec  H8S 1G7  Canada
            Meeting Time: To be determined

            PEI Clipper User Group
            Coordinator:  Derek MacEwen   (902)566-8744
                          FAX 902-566-8351
            1 Duncan Ave, Charlottetown, PE C1B 1L4  Canada
            Meeting Time: To be determined

            Clipper Users Assoc of Central Ontario
            Coordinator:  Eric MacKay   (519) 756-2111x232
            Canada's Conklin Shows, PO Box 31,
            Brantford, Ontario, N3T 5M3  Canada
            Meeting Time: To be determined

            Calgary Clipper Developers Association
            Coordinator:  Stephen Kaltenhauser   (403)297-0348
            317 7th Ave N.E., Calgary, AL, T2E 0N1  Canada
            Meeting Time: To be determined

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 17                  18 Dec 1993


                       CLIPPER 5.x pole, pole a zase pole...

Q:  Is it more efficient to use one multi-dimensional array or
    several single dimension arrays in a program. The array(s)
    would be static and called at the top of the program.

A:  [Don Caton]

    Clipper does not have multi-dimensional arrays. If you're
    thinking about something like aArray[1][2], that is NOT a
    multi-dim array, the first element of 'aArray' just contains
    another array.  This is sometimes referred to as "nested"
    or "ragged" arrays.  Array elements in Clipper can contain
    other arrays, but arrays can never have more than one
    dimension.

    This is not just a semantical difference, this is critically
    important to understanding Clipper arrays.  Given:

         aArray1    := { 1, 2, NIL }
         aArray2    := { 3, 4 }
         aArray1[3] := aArray2

    you can access the first element of aArray2 via 'aArray1[3][1]'
    or 'aArray2[1]'; both expressions will retrieve the same data.
    Likewise, assigning a new value into either expression will affect
    the other, since they are looking at the same piece of data.

    If you're familiar with C, you might think of 'aArray1' and
    'aArray2' as containing pointers to their respective arrays,
    and 'aArray1[3]' and 'aArray2' both contain the same pointer.

    In terms of performance, it is definitely faster to access that
    piece of data as 'aArray2[1]' rather than 'aArray1[3][1]'.  The
    first way only requires a single lookup as the reference
    'aArray2' points to the desired array.  The second way requires
    'aArray1' to be located, then the data in the 3rd element is
    obtained which is the reference to 'aArray2'.  In other words,
    the second method requires an additional indirection before the
    desired data can be located.

    The further "down" the desired array element is from the base
    reference, the more indirections (and overhead) are required
    to retrieve it.  Something like aArray[1][3][5][6] would
    require 3 array retrievals before obtaining the reference to
    the array containing the 6th element you want.  In general, this
    isn't something to be overly concerned with but don't go making
    your arrays unnecessarialy complex.  If you had an array such as
    the one above and you needed access to many of the elements in
    the last array, you should do something like:

         aTemp := aArray[1][3][5]
         xElement := aTemp[6]
         xElement := aTemp[7]
         ... etc.

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


    This retrieves the array reference in aArray[1][3][5] into a
    temporary variable, and eliminates the need for Clipper to
    repeatedly start out at aArray1 and retrieve all the
    intermediate array references.

    As far as an array being STATIC, that has no bearing on
    efficiency of accessing arrays, or any other data type
    for that matter.  STATIC is a visibility and lifetime issue.
    Accessing STATIC (or LOCAL) data will be a bit more efficient
    than something with a storage class of PUBLIC or PRIVATE, but
    that's due to symbol table indirection and has nothing to do
    with array access in particular.

Q:  So which approach is faster:

         aArray[1][5][3][6] := nVal1
         aArray[1][5][3][7] := nVal2
         aArray[1][5][3][8] := nVal3

    or

         aTemp    := aArray[1][5][3]
         aTemp[6] := nVal1
         aTemp[7] := nVal2
         aTemp[8] := nVal3

A:  [Don Caton]

    The second method is always going to be faster, for the simple
    reason that arrays in Clipper are strictly single-dimensional.
    When you access something like 'aArray[1][5][3][6]', internally
    Clipper has to access 4 discrete arrays from the object memory
    system in order to return the desired element.

    The first array is the one referred to by 'aArray'.  When that is
    accessed, the first element is retrieved which also contains an
    array reference.  That array is accessed and its fifth element
    is retrieved which again contains an array reference.  That array
    is accessed and its third element is retrieved which yet again,
    contains an array reference.  Finally, that array is accessed
    and the sixth element is retrieved and assigned into the variable.

    Any or all of those arrays could be in memory, in ems or on disk.
    The worst case would be that all four of those arrays were
    swapped out to disk and each one would have to be brought back in,
    one at a time.

    Just because an array contains references to other arrays,
    they are still completely discrete units of data.  Doing
    something like 'aArray[1][5][3][6]' doesn't access all
    the arrays in one operation, there's simply no way to know
    what any of those elements contain until all the relevant arrays
    and elements are accessed.  Element 3 of the third array might not
    contain an array reference for example, so the expression
    would fail at the fourth internal array access.

DA(m)N NEWS 1-05                   Str. 19                  18 Dec 1993


    If Clipper's arrays were truly multidimensional they would also be
    symmetrical, and any element in any dimension could be accessed
    simply by calculating the proper offset.  For example, in Foxbase
    the array element 'x(2,2)' is actually the fourth element
    in array 'x'.  In Clipper, the absolute location of an element
    in a multi-subscriped array reference cannot be calculated
    in one shot because the expression doesn't refer to a single data
    entity.

    It's always going to be faster therefore to obtain the reference
    to the "lowest" array you need to access and hold on to that
    if you need to access more than one of its elements.

    For similar reasons, it's always faster to assign an object's
    instance variable to a local variable when you need to access
    it more than once.  That way you eliminate the repeated message
    lookup and array retrieval (objects are really arrays at the
    internal level).

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 20                  18 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-05                   Str. 21                  18 Dec 1993


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

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


                              ST - 138N

       UNFORMATTED CAPACITY (MB) ________________N/A
       FORMATTED CAPACITY (26 SECTORS) (MB) _____32.2
       ACTUATOR TYPE ____________________________STEPPER
       TRACKS ___________________________________2,452
       CYLINDERS ________________________________615
       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) ______________________22,430
       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
       BUFFERED STEP PULSE RATE (micro sec) _____3-200
       WRITE PRECOMP (cyl) ______________________N/A (616)
       REDUCED WRITE CURRENT (cyl) ______________N/A (616)
       LANDING ZONE (cyl)________________________AUTO PARK
       IBM AT DRIVE TYPE ________________________N/A

       *ST138R-0/ST138R-1

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


                                    MAXTOR
                              LXT-200S DISK DRIVE
                                JUMPER SETTINGS

        Ŀ
                                                                           
                                                                           
          J3                                                               
                                                  Ŀ            
                 Ŀ                       9 7 5 3 1             
              J6    >                  
          Ŀ                                           
           S   pin 2                              10 8 6 4 2             
           C                                                 
           S       <Ŀ                                              
           I                                                  
DA(m)N NEWS 1-05                   Str. 22                  18 Dec 1993


                                                                     
           C                                      (SCSI ID)            
           O       < terminators                                
           N                                   (MOTOR START             
           N                                     ON COMMAND)             
           E                                                            
           C       <                    (PARITY                       
           T                                 ENABLED)                     
           O                                                               
           R   pin 50 Ŀ                                                  
                                                             
                                                                
              

 Ŀ       J6 pins 7 & 8 (spin with power)
 SCSI PINS   PINS   PINS              out = Wait for START command
  ID  5 & 6  3 & 4  1 & 2              IN = Start when Power Applied
 Ĵ
  0    out    out    out         J6 pins 9 & 10 (parity)
  1    out    out     IN              out = Disables ODD Parity
  2    out     IN    out               IN = Enables ODD Parity
  3    out     IN     IN  
  4     IN    out    out  
  5     IN    out     IN  
  6     IN     IN    out  
  7     IN     IN     IN  
 
 IN = Installed
 out = Not Installed

NOTE: All terminator packs must be oriented with the dot towards J3 for the
disk drive to work properly.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 23                  18 Dec 1993


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


How to get the Novell Netware Requester for OS/2 and IBM TCP/IP to work
together on OS/2, without NTS/2, and without really trying...

This document details how I did it on my system. I'm running the OS/2
2.1 March beta, version 2.01 of the Netware Requester, and IBM TCP/IP
version 1.2.1. I think these instructions will work for other versions
of OS/2. I'm not at all sure they'll work for other versions of the
Netware Requester or TCP/IP. Fortunately, the Netware Requester is
available for FTP from ftp-os2.nmsu.edu, in /pub/os2/2_x/network/novell,
as files wsos21.zip, wsos22.zip, and wsos2d.zip. I also recommend the
UN37938 CSD level of TCP/IP.

It doesn't matter which order you install that Requester and TCP/IP. On
the machine I started from scratch on, I installed the Requester first,
and then TCP/IP, but I've also seen other folks recommend installing
TCP/IP first. In any case, you need to install both, and configure both
as though they were the only thing on your system. Before you go any
further, you need to know the MLID name of your Netware driver; you can
get this by rebooting, and watching the messages as they go by. The
driver will identify itself with somehting like "Novell NE2000 MLID
Driver" and some more text. Note the driver name for later use. You then
need to update three files on your system. One thing I found out the hard
way: Do not reboot your machine from when you start modifying the three
files until you're finished; mine locked up when I did.

The first change is to CONFIG.SYS. You will have a statement that goes
something like
DEVICE=C:\IBMCOM\MACS\NE2000.OS2
(the file name will obviously change if you're using something besides an
NE2000, but it will always be in \IBMCOM\MACS on your boot drive). REMark
out this statement, and add:
DEVICE=D:\NETWARE\ODINSUP.SYS
(change D:\NETWARE to wherever you installed the Requester). This change
removes the IBM-supplied network board driver, and installs the
Novell-supplied communications driver that links the TCP/IP software to
the Novell driver.

Next, you need to update NET.CFG. This file may have been built when you
installed the Requester, or you may be getting along fine without one. If
you don't have one, you'll need to create it; if you do, you'll just need
to update it. Use the Requester's Install program to help build the file,
as it supplies example statements you can cut and paste as needed. Here's
mine, in its entirety (don't key in the comments out to the right!):
Link Support                    <=== this section may or may not be
     MemPool 4096                    necessary...
     Buffers 8 4188
Link Driver NE2000              <=== This section specifies settings for
      INT #1 5                       your hardware and the link driver.
      Frame Ethernet_802.3      <=== Key point: You MUST have all four
      Frame Ethernet_II              of these statements in your file!
      Frame Ethernet_802.2           The ODINSUP driver uses the extra
DA(m)N NEWS 1-05                   Str. 24                  18 Dec 1993


      Frame Ethernet_SNAP            frame types to do its magic.
      Protocol IPX 0 Ethernet_802.3 <=== This statement is needed to set
      Protocol TCPIP 800 Ethernet_II     the default IPX frame type.
Protocol odinsup                <=== These two statements tell ODINSUP
      bind NE2000                    which driver to talk to.
Protocol ipx                    <=== Likewise, these two are for IPX...
      bind NE2000
Protocol TCPIP                  <=== ...and this section is for TCP/IP.
      Bind NE2000                    All of these are set to talk to the
        ip_address      129.106.9.73     NE2000 board.
        ip_router       129.106.1.9
        tcp_sockets     8
        udp_sockets     8
        raw_sockets     1
NETWARE REQUESTER                <=== This section isn't required, just a
   directory services off             performance boost if you're not
                                      running a Netware 4.x file server.

That takes care of two of three; the third is the PROTOCOL.INI file, which
lives in \IBMCOM on your boot drive. The modification here is simple.
There are two sections you're concerned with:

;*----------------------------------------------*
;*------------- PROTOCOL SECTION ---------------*
;*----------------------------------------------*

[TCPIP_nif]
 DriverName = TCPIP$
 Bindings = NE2000                        <=== Note 1

;*----------------------------------------------*
;*--------------- MAC SECTION ------------------*
;*----------------------------------------------*

[NE2000]                                  <=== Note 2
;DriverName = MS2000$
;interrupt = 5
;iobase = 0x320

This is how my file looks after modification. The key is that the Bindings=
statement in the protocol section (note 1) points to a name in square
brackets in the MAC section(note 2); this is how TCP/IP establishes the
connection between the TCP/IP protocol stack and the NDIS driver. You've
already replaced the driver when you modified CONFIG.SYS; now, to
reestablish the connection, you must change the Bindings= to point to the
driver, and that's done by changing it to the MLID name of the Novell
driver. Then, change the corresponding name in the MAC section to match,
using the same MLID name, so that the TCP/IP protocol stack doesn't get
unhappy when it reads PROTOCOL.INI. You can remove or comment out the
hardware-specific information, as I've done in my file, since the TCP/IP
software doesn't talk directly to the hardware any more; leaving it in
doesn't hurt anything, though, since the driver that would use the
information is no longer being loaded.

Now, reboot, and enjoy having both Netware and TCP/IP connectivity on
your system!
DA(m)N NEWS 1-05                   Str. 25                  18 Dec 1993


Good luck!

Jay Maynard
Senior Systems Programmer
University of Texas Houston Health Science Center
jmaynard@oac.hsc.uth.tmc.edu


<====================================NET.CFG===========================>
Link Support
     MemPool 4096
     Buffers 8 4188
Link Driver NE2000
      INT #1 5
      PORT 320
      Frame Ethernet_802.3
      Frame Ethernet_II
      Frame Ethernet_802.2
      Frame Ethernet_SNAP
      Protocol IPX 0 Ethernet_802.3
      Protocol TCPIP 800 Ethernet_II
Protocol odinsup
      bind NE2000
Protocol ipx
      bind NE2000
Protocol TCPIP
      Bind NE2000
        ip_address      129.106.9.73
        ip_router       129.106.1.9
    tcp_sockets 8
    udp_sockets 8
    raw_sockets 1
NETWARE REQUESTER
   directory services off
<==========================================================================>

<=================================CONFIG.SYS===============================>
IFS=C:\OS2\HPFS.IFS  /CACHE:384 /CRECL:4 /AUTOCHECK:CD
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=.;C:\OS2\DLL; .... D:\NETWARE;D:\TCPIP\DLL;C:\IBMCOM\DLL;
SET PATH=C:\OS2; .... ;D:\NETWARE;L:\OS2;P:\OS2;D:\TCPIP\BIN;C:\IBMCOM;
SET DPATH=C:\OS2; .... ;D:\NETWARE;L:\OS2;P:\OS2;C:\IBMCOM;
SET PROMPT=$i[$p]
SET HELP=D:\UTILITY\HELP;C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;D:\TCPIP\HELP;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
DA(m)N NEWS 1-05                   Str. 26                  18 Dec 1993


DEVICE=C:\OS2\TESTCFG.SYS
DEVICE=C:\OS2\DOS.SYS
DEVICE=C:\OS2\PMDD.SYS
BUFFERS=30
IOPL=YES
DISKCACHE=64,LW
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=D:\ 2048 4096
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
REM SET DELDIR=C:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=OS2DASD.DMD
SET BOOKSHELF=C:\OS2\BOOK
SET EPMPATH=C:\OS2\APPS
SET FAXPM=C:\OS2\APPS
DEVICE=C:\OS2\APPS\SASYNCDA.SYS
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VCDROM.SYS
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS SERIAL=COM1
DEVICE=C:\OS2\COM.SYS
DEVICE=C:\OS2\MDOS\VCOM.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
SET VIDEO_DEVICES=VIO_SVGA
DEVICE=C:\OS2\MDOS\VSVGA.SYS
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP

REM --- NetWare Requester statements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=D:\NETWARE\LSL.SYS
RUN=D:\NETWARE\DDAEMON.EXE
DEVICE=D:\NETWARE\NE2000.SYS
DEVICE=D:\NETWARE\IPX.SYS
rem DEVICE=D:\NETWARE\SPX.SYS
rem RUN=D:\NETWARE\SPDAEMON.EXE
rem DEVICE=D:\NETWARE\NMPIPE.SYS
rem DEVICE=D:\NETWARE\NPSERVER.SYS
DA(m)N NEWS 1-05                   Str. 27                  18 Dec 1993


rem RUN=D:\NETWARE\NPDAEMON.EXE
DEVICE=D:\NETWARE\NWREQ.SYS
IFS=D:\NETWARE\NWIFS.IFS
RUN=D:\NETWARE\NWDAEMON.EXE
rem DEVICE=D:\NETWARE\NETBIOS.SYS
rem RUN=D:\NETWARE\NBDAEMON.EXE
DEVICE=D:\NETWARE\VIPX.SYS
DEVICE=D:\NETWARE\VSHELL.SYS GLOBAL
DEVICE=C:\IBMCOM\PROTOCOL\INET.SYS
DEVICE=C:\IBMCOM\PROTOCOL\IFNDIS.SYS
rem DEVICE=C:\IBMCOM\MACS\NE2000.OS2
DEVICE=D:\NETWARE\ODINSUP.SYS
REM --- NetWare Requester statements END ---
SET ETC=D:\TCPIP\ETC
SET TMP=D:\TCPIP\TMP
RUN=D:\TCPIP\BIN\CNTRL.EXE
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
SET HOSTNAME=k5zc.hsc.uth.tmc.edu
<=========================================================================>

<=================================PROTOCOL.INI============================>
[PROT_MAN]
 DriverName = PROTMAN$

[IBMLXCFG]
 NE2000_nif = NE2000.nif
 TCPIP_nif = TCPIP.nif

;*----------------------------------------------*
;*------------- PROTOCOL SECTION ---------------*
;*----------------------------------------------*

[TCPIP_nif]
 DriverName = TCPIP$
 Bindings = NE2000

;*----------------------------------------------*
;*--------------- MAC SECTION ------------------*
;*----------------------------------------------*

[NE2000]
;DriverName = MS2000$
;interrupt = 5
;iobase = 0x320
<=========================================================================>

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 28                  18 Dec 1993


 Co je vlastn novho v OS/2 2.1


  Perspektiva Uivatele:
 

 Vylepen podpora aplikac:

   WIN-OS/2 3.1 Standard reim, WIN-OS/2 podpora je dotaena na rove
    podpory Windows 3.+ aplikac (vetn Windows multimdilnch aplikac).
    pracujcch v Standartnm reimu, objoje seamless a celoobrazovkov.
    Plne nahrazuje WIN-OS/2 3.0 podporu.
   WIN-OS/2 3.1 Enhanced kompatibilita, nov reim byl pidn k WIN-OS/2
    podpoe. Umouje vtin Windows 3.1 Enhanced aplikac pracovat pod
    WIN-OS/2 za pedpokladu e nevyaduj specieln adi zazen (VxD).
   Zahrnut MMPM/2 1.1 -  Multimedia Presentation Manager/2 1.1 je nyn
    soust dodvky OS/2 2.1. MMPM/2 poskytuje 32-bitovou multimediln
    podporu pro PM aplikace, vetn monosti videa.

 Vylepen operanho systmu

   WIN-OS/2 3.1 zlepen vkonnosti - vkonnost Windows aplikac pracujcch
    pod WIN-OS/W byla podstatn zlepena, zejmna pi prci v seamless
    reimu
   32-bit PM grafika - kompletn pepracovn grafickho zkladu poskytuje
    pedpoklad pro chod vkonnch aplikac. Okamit prospt umouj 32bitov
    seamless displejov adi.

 ir podpora hardware

   Instalace z CD-ROM  -  OS/2 2.1 me bt instalovn z CD-ROM. Jde o
    zsadn zmnu a umouje uetit mnoho asu a energie. Dv instalan
    diskety jsou poskytnuty pro sputn CD-ROM instalace.
   SCSI CD-ROM podpora - IBM a ne-IBM SCSI CD-ROM jsou podporovny
   OS/2 2.1 pedinstalovan na IBM a PC stroje, mnoho z IBM a ne-IBM systm
    me bt nyn dodvno s pedinstalovanm OS/2 2.1
   Dodaten SCSI podpora - IBM a ne-IBM SCSI karty jsou podporovny
   Seamless 32-bit displejov adie pro XGA, XGA-2, SVGA (Tseng, Headland,
    Western Digital, Trident, ATI, Cirrus, and IBM VGA 256-color), 8514/A a
    VGA - Umouj seamless integraci OS/ PM a Windows 3.1 aplikac na
    OS/2 desktop.
   Mnoho novch a vylepench PM tiskovch adi zahrnuje i nov rychl
    tiskrny je nov dodvno k OS/2 2.1.
   Podpora pro Windows 3.1 tiskrny a displejov adie - Standartn soubor
    Windows 3.1 tiskovch a displejovch adi je soust OS/2 2.1,
    a mohou tak bt pouity s WIN-OS/2.
   Advanced Power Management podpora -  OS/2 2.1 zahrnuje programy pro
    sporu energine na notebook a laptop potach s APM specifikacemi.
   PCMCIA podpora -  OS/2 2.1 zahrnuje funkce podporujc notebooky a
    laptopy s PCMCIA sbrnc

 Vznamn zmny v OS/2 2.1 


 Vylepen podpora aplikac

DA(m)N NEWS 1-05                   Str. 29                  18 Dec 1993


   Dual-Thread MVDM podpora -  umouje mnoha DOS multimedilnm aplikacm
    pracovat svin pomoc poskytnut loh uvnit VDM pro souasn ten z
    disku a kreslen obrazovky i tvorbu zvuk.
   DOS_AUTOEXEC nastaven - specifick AUTOEXEC me bt sputn automaticky
    pi vytvoen VDM
   Zlepen Clipboard a DDE podpory -  Clipboard a DDE podpora ve
    WIN-OS/2 byla zlepena, umouje vt prchodnost a efektivnost specieln
    pi vmn dat mezi WIN-OS/2 a OS/2 PM aplikacemi.
   Schopnost spustit DOS i OS/2 aplikaci zevnit Windows aplikace. Je
    mon provst "shell" do DOSu i OS/ aplikace zevnit z Windows programu.
    Toto je specieln vhodn pro Windows programy zvisl na DOS utilitch.

 OS/2 2.1 technick vylepen

   Zahrnut Windows 3.1 File Manager a vtiny Accessories - vtina z
    Windows 3.1 Accessories, zahrnujce i File Manager, Write a Paintbrush,
    je nyn soust WIN-OS/2 3.1.
   Vylepen WIN-OS/2 Setup a konfigurace -  Setup a konfiguran procedury
    pro WIN-OS/2 aplikace byly vznan zlepeny, zejmna pro Clipboard a
    DDE podporu.

 Operan systm vylepen

   Varovn o ACL File Protections ped instalac, OS/2 2.1 instalace
    kontroluje ped startem zda jsou soubory i adrese ochrnny ACL,
    aby bylo jist e instalace me bt dokonena spn.
   Page Tuning Performance vylepen - vylepen byla provedena ve sprv
    pamti v dcm programu umoujc znan zrychlen prce pi
    nedostatku pamti.
   XCOPY vylepen -  XCOPY program byl vylepen pro kopie se systmovmi
    a skrytmi soubory a zachovv readonly pznaky.
   Zlepen OLE podpora v WIN-OS/2 3.1 -  Object Linking and Embedding
    (OLE) podpora pro dokumenty byla zlepena jako nsledek zmny WIN-OS/2
    kdu za Windows 3.1 kd.
   Truetype** Fonty v WIN-OS/2 3.1 - Truetype Font technologie a fonty jdra
    jsou zahrnuty jako vsledek zahrnut Windows 3.1 kdu.
   ISO Font podpora -  Poskytnuta je skupina ISO font pro zajitn novho
    ISO 9241-3 ergonomickho standartu na pslunm hardware.
   Zlepen INI zpracovn - moduly zodpovdn pro prciu s .INI soubory
    byly pepracovny na rove pln 32bitovho kd co zajiuje rychlost
    a vt spolehlivost.

 ir podpora hardware

   Nahrvateln ABIOS - tato monost je poskutnuta pro ABIOS schopnost nahrn
    do pamti RAM z ABIOS soubor na disku, msto pouit ABIOS v ROM. Toto
    je nutn pro PS/2 Modely 56 a 57, PS/2 Server 85 a ThinkPad 700 srii
    notebook a jakkoliv ostatn PS/2 systmy pouvajc ABIOS nahrvateln
    msto ABIOS v ROM.
   Vylepen Selective Install programu - program byl vylepen o rozdlen
    na adi displeje, SCSI 5adi4, CD-ROM adi, instlaci tiskrny a t
    umouje uivateli insalovayt WIN-OS/2 programy jako volbu pi instalaci.
   instalan program pro adi displeje - umouje jednoduchou metodu
    instalace a konfigurace XGA, XGA/2, SVGA, 8514/A adi, monitor
    a rozlien.
   PS/2 Server 195 a 295 podpora - OS/2 2.1 bude pracovat na PS/2 Server 195
DA(m)N NEWS 1-05                   Str. 30                  18 Dec 1993


    a 295 systemech, Dve Server 195 a 295 podpora byla limitovna na OS/
    1.3.
   Pentium zalenn - OS/2 2.1 zahrnuje zmny zaleujc Intel nov
    Pentium procesor. Prvn fze tohoto zalenn zlepuje vkonnost DOS
    loh skrz pouit Pentium virtulnho reimu.
   Zlepen strnkovacho mechanismu - OS/2 2.1 vvoji provedli nkter
    skryt zmny pro zlepen veobecn vkonnosti OS/2.1, zejmna pi
    nedostatku pamti.
   XGA-2 DMQS potlaen - umouje vyuit schopnost ne-IBM displej i pi
    pipojen k XGA-2 adaptru pomoc potlaen automatick detekce (DMQS)
    displeje v XGA-2
   Rozen instalace tiskren - zjednoduen instalace dodaten tiskovch
    adi v OS/2 2.1

Mal vylepen v OS/2 2.1 


 Zlepen podpora aplikac
   OS2VER soubor - nkter aplikace kontroluj na specifick slo verze
    OS/2 2.0 ped starem. OS2VER soubor umouje sdlit tmto aplikacm e
    pracuj v OS/2 2.0 akoliv ve skutenosti pracuj v OS/2 2.1
   DPMI 1.0 podpora - DPMI podpora byla pozdvihnuta na rove DMPI 1.0 m
    umouje vce aplikacm pouvat DOS-DPMI
   PC Support/400 podpora - Nov rozen verze PC Support/400 (V2R3),
    dostupn v druh polovin 1993, bude pracovat v OS/2 2.1 VMD.
   Multimedia podpora pro zvuk v WIN-OS/2 3.1 -  Windows 3.1 Multimedia
    podpora pro zvuk je zahrnuta jako vsledek pouit WIndows 3.1 kdu
   Workplace Shell viditeln zmny - nkter men vylepen byla provedena
    ve vzhledu Workplace Shell, zejmna nov proveden notebooku a nov ikony
    pro CD-ROM disky.
   Settings Notebook Drag/Drop vylepen - je nyn mon pidat programov
    objekty to menu i zmnit ikonu objektu pouitm drag/drop
   Auto-uzamen pi startu PC-  Workplace Shell me bt konfigurovn pro
    automatick uzamen ihned po startu systmu a poaduje potom heslo
    pro monost pouit OS/2, dodaten rove ochrany proti zneuit.
   Tiskov spooler vylepen -  tiskov spooler umouje zadvat a mnit
    priority loh.

OS/2 2.1 Technick vylepen  


 Vnitn zmny Operanho systmu
   Paletov manaer pro XGA, XGA-2, SVGA, 8514/A -  Podpiruje 256barvovou
    paletu, umouje nastavit specifick barvy pro aplikace.

 ir podpora hardware
   Podpora Brazilsk klvesnice
   Trackpoint II podpora -  Ukazovac zazen ThinkPad 700 srie notebook
    je nyn podporovno
   Podpora pro rozen 2.88MB disky -  Nov 2.88MB disketov mechaniky
    (6451271) poskytujc programov vysunut a zamen/odemen
   Podpora pro 3.5" rozen pepisovateln optick disky - nov 3.5"
    Rewritable Optical drive (6451295), s podporou pro P-ROM (partial
    read-only memory) optick disky a s programovm uzamenm/odemenm
    a vysunutm mdia
   Formtovac program vylepen pro P-ROM optick disky
DA(m)N NEWS 1-05                   Str. 31                  18 Dec 1993


   Vt kurzor na VGA LCD displejch - Na VGA LCD displejch notebook je
    zobrazovn vt kurzor pro snadnj itelnost
   MSCDEX podpora -  VCDROM virtuln adi podporuje veker CD zvukov
    funkce originlnho MSCDEX DOS adie

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 32                  18 Dec 1993


                           OS/2 a HRY!!!!!!!!!!!


This file provides guidelines for running various games under OS/2.  The
info here has been gathered from postings to the net and from my own
experiences.  Much of the information here is incomplete, so if anyone
spots an error, or if anyone has a solution for a particular problem,
please email me and I will update this file.

---------------------------------------
GENERAL TIPS (READ THIS FIRST!):
=======================================

Read the README file in your OS/2 root directory.  It has tips for running
specific DOS and Windows apps under OS/2.

Read the comp.sys.ibm.pc.games FAQ.  This is very important since it will
tell you about possible problems when running the game even under plain
DOS.  If you can't find a copy of the FAQ in comp.sys.ibm.pc.games, email
Chris Warren, the keeper of the FAQ, at warren@apple.com for a copy.

If you have trouble installing the game under OS/2 and you are trying to
install the game on an FAT drive, boot up plain DOS (via dual boot or the
Boot Manager) and install it there.  Sometimes a game (or other apps) won't
install for some reason under OS/2, but once installed they'll work fine
under OS/2.

If you experience strange anomalies or incompatibilities of any kind
(especially with older games), try booting a real copy of DOS from a floppy
inside a VDM running under OS/2 and run the game in that DOS session.  (See
VMDISK in the Command Reference online docs for details.)  Some games that
require keydisks will only work this way.

In order to achieve maximum performance and speed, especially for graphics
intensive games such as flight simulators, try the following settings:

DOS Fullscreen:  check this option; best performance can always be
 achieved by running the game in a full screen DOS session.
DOS_BACKGROUND_EXECUTION:  OFF
 (so it won't take CPU time when you switch away from it)
DOS_HIGH: ON (more memory for those that need it)
DOS_RMSIZE: 640
DPMI_MEMORY_LIMIT: 0  (most
 DOS games don't use DPMI memory)
EMS_MEMORY_LIMIT: 1024  (this is EXPANDED memory.  If a game
 uses more than 1024k, use a higher number; if the game uses no
 EMS, such as Ultimas 4-5 and most of the earlier EGA games
 [SSI games, Tunnels and Trolls, Might and Magic II, Dragon
 Wars, Magic Candle I, Knights of Legend, etc.] set EMS to 0)
HW_ROM_TO_RAM: ON  (copies ROM BIOS to RAM--several people
 have said this boosts performance on their machines)
HW_TIMER: ON  (this is important, especially for those games that
 use soundboards.  However, one user noted that when this setting
 is set to ON it causes many games that send sound directly to the
 SB to crash the entire system.  I have not experienced this myself.)
IDLE_SECONDS: 10
DA(m)N NEWS 1-05                   Str. 33                  18 Dec 1993


IDLE_SENSITIVITY: 100  (this is important)
KBD_ALTHOME_BYPASS: ON  (this prevents the DOS session from
 being shrunk to a window via ALT-HOME; keep it on OFF if you
 want to run your game in a window)
VIDEO_FASTPASTE:  ON  (reported by some to boost performance)
VIDEO_RETRACE_EMULATION:  OFF  (important for fast graphics,
 though you may have to experiment with this one)
VIDEO_ROM_EMULATION: OFF
XMS_MEMORY_LIMIT:  64  (this is EXTENDED memory; when you have
 DOS_HIGH=ON, DOS can use this 64k which will help give you more
 base memory)

For best performance close ALL windows and apps (especially DOS apps) before
you run the game so that the game can get as much of the CPU as
possible.

Trying to find the right combination of DOS parameters for finicky
games is sometimes a matter of experimentation.

-----------------------------------------
SOUND CARDS:
=========================================

Soundblaster: make sure that you don't have your Soundblaster set for IRQ7.
 OS/2 uses IRQ7 (which is LPT1) to print, even though DOS doesn't, so
 under OS/2 you need to change the default IRQ for your SB from 7 to
 5 (or to some other available IRQ).

Roland LAPC-1: the default IRQ2 and 330 address work fine.  IRQ2 is
 automatically mapped to IRQ9 on 386 and 486 boards.

PRO AUDIO SPECTRUM-16: be
 sure to set the IRQ's to something other
        than 7.  See the note under Soundblaster above.  You can load
        the PAS16's mvsound.sys by opening the DOS games program
        object icon, going into its DOS settings, and entering a line
        similar to the following in the DOS_DEVICE box:

              c:\proaudio\mvsound.sys d:3 q:2

        The path and the optional parameters will vary of course.

------------------------------------------
SPECIFIC GAMES:
==========================================


Use the settings detailed above for the following games, varying EMS as
needed.  Exceptions to the above settings are noted where applicable.  I
have decided to include all the games that were mentioned on the net by
OS/2 users--even if there were no problems reported--to allow those who are
thinking about buying a game to know how it runs.  A complete list will
also let people post or email additional hints when they see their game
listed.

[NOTE: "runs fine" means I've tested the game myself.  "Reported to run
DA(m)N NEWS 1-05                   Str. 34                  18 Dec 1993


    fine" means that the game was mentioned on the net as being compatible
    with OS/2.]


ACES OF THE PACIFIC:

--reported to run fine by a couple different people.
--one person made the following note:
     There's a patch out which increases screen update considerably.
     Without the patch, AotP is slightly slow on a 386/40, with the patch
     it is OK.


ALONE IN THE DARK:

--reported to run fine.  Be sure to set DOS_UMB and HW_NOSOUND to off
   and HW_TIMER to on for best sound production.


ATLANTIS:

--reported to run fine.


A-TRAIN:

--two people reported having to run the game in monochrome mode because
   if you try to run it in color it displays in a horrible monochrome
   mode anyway; and although the game was playable there was no sound.

Anybody got it to run in color?


BATTLE CHESS:

--reported to run fine.


BREACH 2:

--one user reported that he couldn't get the mouse to work, so
 he had to use the keyboard instead under OS/2.


CASTLE WOLFENSTEIN [WOLF3D]:

--t
his is one of the most finnicky games, and may require some
    experimentation to make it run well.  According to net reports,
 this game uses a special split-screen mode of the video card,
 and thus its behavior tends to rely on a person's hardware
 peculiarities more than OS/2 itself.  I find that I can run this
 game fine, but if I switch away from the game and then switch back
 to it the bottom portion of the screen will no longer display
 the statistics for my character.
--sometimes the special effects sounds for this game (shots, doors
DA(m)N NEWS 1-05                   Str. 35                  18 Dec 1993


 opening, people talking, etc.) will get lost after a brief
 period of time.  If this happens, create a batch file (wolf3d.bat)
 and have your program object point to the batch file.  In the
 batch file put the following two lines:
  SET BLASTER=A220 I5 D1
  WOLF3D.EXE
 The first line tells the wolf3d.exe program which address you
 are using, which IRQ you are using (in this case it's IRQ5),
 and which DMA you are using (in this case DMA1).  That should
 solve the loss of special effects sounds.  SB-Pro owners should
 add T2 or T3 to the end of the first line (check your docs for
 details).
--if you have further problems, set XMS memory to 64k.


CHUCK YEAGER'S AIR COMBAT:

--one user made the following suggestion when using the PC speaker
 for sound: Start up the game and allow it to go through the
 intro (even though the sound will just crackle).  Then after
 the intro, do a test flight and do a ^S to kill the sound.
 This will kill the sound for future sessions.  If you want
 digitized speech thereafter you can turn it on during flights
 BUT be sure to turn off the sound before you finish a mission.


CIVILIZATION (Microprose):

--Make sure you have the updated version.  It will have the "rename" button
 on the city screen.  This version performs much better under OS/2.
 If you don't have this version, you can download an update from the
 Microprose forum on CompuServe.
--Always use fullscreen mode, and when the program starts up, use vga
 resolution and ibm sound.  (ega
no sound slows it down.) If you
    want to turn off sound, do it from the options menu.
--one person reported that he could not start a new game in vga since
 he got a divide by zero error in the dos box.  But it was
 possible to load a saved game into vga mode.  Another person
 reported that he cured this divide by zero error when he set
 COM_HOLD to ON.
--another user made the following observation:

   I had been having speed problems running the game in adlib/soundblaster
   mode (and believe it or not I never tried anything else). However:
   When I ran Civilization in PC SPEAKER mode, then quit, and ran it
   again in soundblaster/adlib mode (in the same DOS session), it ran
   at the correct speed!  Since doing this on a regular basis would be
   a pain in the ass, I wanted to find another way to 'prep' the system
   for Civilization: and I found it. I ran SBFMDRV.COM (comes with the
   soundblaster) before running civilization. This way I can run Civ
   from a batch file called by a WPS icon.


COMMANCHE: MAXIMUM OVERKILL:

DA(m)N NEWS 1-05                   Str. 36                  18 Dec 1993


--this game will not run under OS/2 because it attempts to put the
   CPU into protected mode.


COMMANDER KEEN 3:

--reported to run fine.


COMMANDER KEEN 4:

--reported to run fine, with the exception that if you switch away
   from the game to the WPS and then back again the screen will get
   messed up.


CONQUERED KINGDOMS:

--one person said they could not get this game to run because the
   mouse pointer would get lost when using the game under OS/2.


CURSE OF THE AZURE BONDS:

--runs fine.


DARKLANDS:

--runs fine.  If you find the intro animation jerky, try turning your
   VIDEO_RETRACE_EMULATION to ON (normally you should set it to OFF
   for best performance).


DARKSEED:

--one person said:
   the intro will start and run OK under OS2, but then as part of the
   copy protect mechanism, the game wants to do something'illegal' on the
   A-disk'. OS2 catches the illegal instruction, and the game won't
   proceed beyond the demo.
--another person said he could get this game
 run by booting real DOS
   from a boot image, but the digitized sounds needed to be turned off
   because it exhibited the same problems that Wizardry has (see
   "WIZARDRY 7").


DRAGON WARS:

--runs fine.


DRAKKHEN:

--one user reported that this game runs under OS/2, but it often
DA(m)N NEWS 1-05                   Str. 37                  18 Dec 1993


 crashes giving the "Contact your IBM rep" message.  Any
 suggestions?


DUNE II:

--reported to run fine.  One user, however, said that when he ran it
   the game would eventually hang after first losing the Soundblaster
   sound, and another user said he could not get the digitized sounds
   to work correctly either.


ELF:

--according to one user there are problems with this game.


ELFLAND (ver. 1.1):

--reported to run fine, with the exception that if you switch away
   from the game and then back to it the screen will get messed up.
   Also, according to the person who made the report on this game,
   it tends to lock up occasionally under OS/2, but that occurred
   under plain DOS as well.


ERIC THE UNREADY:

--this game crashed about a dozen times during play.  OS/2 reported
   several reasons for the crash, including trying to access
   a nonexistent fpu and trying to issue a command that's not
   supported by the 386 instruction set.  I didn't try running it
   under a real copy of DOS booted in a vdm because I wanted to
   continue to tinker with the DOS settings.  I got the settings
   to a point where the last half of the game went without a single
   crash; here were my final settings for the game:

   COM_HOLD: on (don't know if this matters or not)
   DOS_HIGH: off
   DOS_UMB: off
   DPMI_MEMORY_LIMIT: 0
   EMS_MEMORY_LIMIT: 0 (this game doesn't use any)
   HW_ROM_TO_RAM: on
   HW_TIMER: on
   IDLE_SECONDS: 30
   IDLE_SENSITIVITY: 100
   VIDEO_FASTPASTE: on
   VIDEO_ONDEMAND_MEMORY: on
   VIDEO_RETRACE_EMULATION: off
   VIDEO_SWITCH_NOTIFICATION: on
   XMS_MEMORY_LIMIT: 0

   I ran the game in regular vga mode.  It has svga (VESA) capability,
   but that just makes the pictures smaller, so I didn't use it.  As
   f
ar as the crashing goes, it seemed to do it when the music changed
DA(m)N NEWS 1-05                   Str. 38                  18 Dec 1993


   themes or when the music started a song over again.  I tried turning
   INT_DURING_IO to ON but it made no difference.  I have an LAPC-1
   on IRQ2 and a Soundblaster at IRQ5.  BTW, this game has the BEST
   music I've ever heard--tons of different songs... some of them
   written for just one scene in the game!  And the Soundblaster
   digitized voices and digitized sounds worked superbly under OS/2.


ETERNAM:

--reported to run fine.


EYE OF THE BEHOLDER I:

--runs fine.


EYE OF THE BEHOLDER II:

--reported to run fine.


F15:

--one person said that he could not get this game to run at all.  It
  either gave him an illegal instruction @$c, or failed to run when
  trying to read the keydisk.  He even tried loading DOS 5.0 and
  DR DOS 6.0 in a vdm, but it still did not work.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 39                  18 Dec 1993


===============================================================================
                          DOS (Dumb Operating System)
===============================================================================


Summary:

This article discusses common questions and issues with DoubleSpace
actual compression ratio (ACR) and estimated compression ratio (ECR).
The following three subjects are covered:

 - Actual Compression Ratio
 - Estimated Compression Ratio
 - Viewing and Changing the Compression Ratio

More Information:

Actual Compression Ratio
------------------------

The actual compression ratio (ACR) represents the compression ratio
for data that already exists on a drive. The ACR varies over time
depending on the type of files you store on you hard disk.

The ACR is calculated by dividing the sum of the uncompressed data
size by the physical space consumed after the data is compressed. For
example, if a disk with 100 megabytes (MB) of uncompressed data is
compressed and occupies 50 MB of disk space, the compression ratio is
2:1. The formula is as follows:

   100MB/50MB =2.0

   Note: 2.0 is written as 2.0:1 (that is, 2 to 1)

Estimated Compression Ratio
---------------------------

The estimated compression ratio is a number that DoubleSpace uses to
calculate the amount of free space on a compressed drive. Changing the
ECR doesn't change the compression algorithm or the ACR. It simply
changes the value that DoubleSpace uses to estimate the free disk
space.

You may need to increase the compression ratio if you are trying to
store several new highly compressible files and you are low on disk
space.

For more information on ECR:

 - Run DoubleSpace, choose Change Ratio from the Drive menu, and then
   press the F1 function key.

  -or-

 - Type "help dblspace /ratio" (without the quotation marks) at the
   MS-DOS command prompt.
DA(m)N NEWS 1-05                   Str. 40                  18 Dec 1993


Viewing and Changing the Compression Ratio
------------------------------------------

To view the ACR and ECR for a drive, type "dblspace" (without the
quotation marks) at the MS-DOS command prompt, select the drive you
are interested in, and then press the ENTER key.

To view the ACR for a file or directory, use the DIR /C or DIR /CH
command. For example, to see the ACR for COMMAND.COM, type the
following at the MS-DOS command prompt:

   dir c:\command.com /ch

To view the ACR for the DOS directory, type the following at the
MS-DOS command prompt:

   dir \dos /ch

Note: DIR /C reports the ACR of the compressed data based on an
8-kilobyte (K) cluster size. DIR /CH reports the ACR based on the
compressed data based on the host drive cluster size. Use this number
when you compare the ACR and ECR.

To set the ECR to the ACR value, type "dblspace /ratio" (without the
quotation marks) at the MS-DOS command prompt.

To set the ECR to a specific value, type the following at the MS-DOS
command prompt:

   dblspace /ratio=n.n

where "n.n" is the ECR value.

-------------------------------------------------------------------------------
DA(m)N NEWS 1-05                   Str. 41                  18 Dec 1993


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




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). 


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