TB>
  > 2) I much prefer to use text mode .INI files for easier editing.
TB>

  Oh yes ?  What about storing binary data ?  What about parsing errors ?

  The reality is that binary INI files are generally considered to be
  more robust that text format INI files.

  This is one of the rare instances where I find myself in the unfortunate
  position of agreeing with Microsoft.  Microsoft's decision to make their
  "registry" use a private binary format rather than a text format was
  motivated by the desire to prevent users screwing up INI files by using
  text editors on them.

  OS/2's binary INI files also have this advantage.  Windows echoes are
  full of people who have hand-mangled their INI files, and suddenly find
  themselves without fonts, without printers, or with a completely
  non-functional Windows system because they've removed the wrong VxD
  line.  You don't see any equivalent messages in OS/2 echoes.

  For the benefit of developers, there do exist several small OS/2 INI
  editing utilities.  In a pinch, you could even write your own.  A couple
  of comboboxes, an entry field, and a standard file dialogue should do
  the trick.

  Plus, of course, there's always REXX for manipulating INI files.  Any
  competent user can knock together a simple REXX script for doing
  (relatively safe) INI manipulation.

    /* Dump an INI file of your choice -- (c) Copyright 1995 JdeBP. */

    parse arg FileName

    call RxFuncAdd 'SysIni','RexxUtil','SysIni'

    if FileName == '' then do
     parse source Platform Type CommandFile
     say "Usage: "CommandFile" Filename"
    end
    else do
     rc = SysIni(FileName, 'ALL:', 'apps')
     do i = 1 to apps.0
      rc = SysIni(FileName, apps.i, 'ALL:', 'keys')
      do j = 1 to keys.0
       value = SysIni(FileName, apps.i, keys.j)
       say apps.i' 'keys.j': 'translate(value,' ',x2c('07'))
      end
     end
    end

  > JdeBP <
___
 X MegaMail 2.10 #0:Dr Who is back on U.K. television!

--- Maximus/2 3.01