OS/2 Shareware BBS: 10 Tools/10-Tools.zip/bullet25.zip/readme

Text File | 1997-06-25 | 10KB | 221 lines

Bullet 2
README 25-Jun-1997
Installation instructions and product support numbers
Read all before moving on.

1. Installation, Preliminary Steps
2. Installation, Compiler-specific
3. Evaluation Version Limitations
4. Installation Testing
5. Updates
6. Product Support

Order forms and instructions are in common\order.cc and order.frm files, and
in the documentation files.

-----------------------------------------------------------------------------
1. Installation, Preliminary Steps
-----------------------------------------------------------------------------

Unzip the archive contents of the platforms you want to use to the directories
of your choice, making sure you use the "create directories" option in pkzip
(the -d switch).  The files can be put into any directory, and moved at any
time; the included directory structure is just the method used for packaging.


This file is the main README for all Bullet 2 platforms.  Platform-specific
entries are indicated by DOSX32:, OS/2:, and Win32: markers.  Each platform
and level may also contain additional README* files included.

 DOSX32: Disregard references to "DLL" file.

 Win32:  If you are using VC4, or any COFF-compiler, use the BULLET95.LIB
         file from the lib\coff directory.  An OMF32-compiler version is in
         lib\omf as well as the install directory (by default).

Distribution and other license restrictions are detailed in the
License Agreement, located in the manual.


-----------------------------------------------------------------------------
2. Installation, Compiler-specific
-----------------------------------------------------------------------------

The DLL and LIB files are ready to use, and will work with nearly any capable
compiler no matter the compiler language.  Each DLL file has an import library.
Import libraries will always be referred to here as "import library".  The
code library will be referred to here as "library".

Static Link:

To use the Bullet LIB library code, link with the BULLET?.LIB library file
(?=X, 2, 95, for DOSX32, OS/2, and Win32, respectively).  Typically this is
added to your linker's options.  Consult you compiler/linker documentation
for details (e.g., see "static linking").


Dynamic Link:

To use the Bullet DLL library code, link with the BULLET?i.LIB import
library file (COFF-compilers link to the import file BULLET9c.LIB).  Consult
your compiler/linker documentation for details (see "dynamic linking").

If you have any trouble, or have special compiler requirements,
contact support at the sites listed below.


  OS/2:  BULLET2i.LIB is the import library.

 Win32:  For OMF-compilers, BULLET9i.LIB is the import library.  For
         COFF-compilers (VC4, for example), BULLET9c.LIB is.

         Bullet exports "BULLET" and "_BULLET", both of which use the _stdcall
         calling convention (BULLET cleans the stack), with a single, 32-bit
         pointer on the stack.  Both names locate the same entry point.  The
         "BULLET" entry name is for Watcom 10 compilers which do not use the
         same naming convention for _stdcall as does Microsoft.  BULLET9i.LIB,
         the OMF import library, uses simply "BULLET" (and "_BULLET), not
         _BULLET@4, which is what BULLET9c.LIB, the COFF format import library,
         (and code library BULLET95.LIB, coff version) uses.  If necessary
         you can easily create your own import library just by writing your own
         BULLET-named module, with a single, 32-bit pointer as its parameter.
         The module doesn't need to do anything.  Link it as a DLL and generate
         an import library of that DLL.  If dynamic loading is used to load
         Bullet, via Win32 API LoadLibrary, no import library is needed.

 MSVC Studio:  In your Project settings...,Link,Object/library modules:, add
         either bullet9c.lib or bullet95.lib (COFF version).  Use bullet9c.lib
         if you want to use BULLET95.DLL, or bullet95.lib if you want a static
         link (no DLL needed to run your program).

 Watcom: For Watcom 10, two import Win32 API defines need to be given to the
         linker when you link your programs.  From the IDE, at the "Windows
         linking switches" page, entry for "import files (imp:)", enter
         (include the starting and ending double-quotes):

"_GetVersionExA KERNEL32.GetVersionExA,_GetLocaleInfoA KERNEL32.GetLocaleInfoA"

         This is needed because the NT.LIB file included in W10 predates these
         Win32 API calls.  NT 3.5 or later is required.  Later Watcom compilers
         may want to use the -Zz compiler option.  NT may have a problem with
         the name KERNEL32 since it looks for that name, rather than
         KERNEL32.DLL.

         Contact Microsoft or Watcom or, if they won't remedy the problem,
         contact [e-mail] and I can tell you one method that works.

 For other compilers, like Borland, C++ Builder, it's just a matter of adding
 either the import library or the static library name to your project list.
 Alternatively, you can use a on-demand link by using LoadLibrary.

The included Win32 DLL works for Windows 95 and later, NT 3.5 and later, and
Win32s 1.15 and later.  This also applies to the static link library.  Win32s
applications written for Win32s version 1.25 or earlier will also run in OS/2
Warp.  You can, of course, create a native OS/2 application by using the OS/2
version of Bullet.


-----------------------------------------------------------------------------
3. Evaluation Version Limitations
-----------------------------------------------------------------------------


        Error 8313:  Evaluation time period has expired

is the result when you exceed approximately 300 records.  Bullet can easily
handle millions of records, though this is available only to registered users.
To register, you must order Bullet.  See the order forms, _order.cc and
_order.frm.  Order today and have a license e-mailed within 24 hours (in most
cases).


-----------------------------------------------------------------------------
4. Installation testing
-----------------------------------------------------------------------------

To make sure that you have everything set up correctly, you should build the
bd_* demo program.  When building the bd_* demo, define PLATFORM to one of
the following:

 DOSX32: PLATFORM=3

   OS/2: PLATFORM=4

  Win32: PLATFORM=5

See PLATFORM.H for more.  The PLATFORM define is used in the PLATFORM.H and
the BULLET_2.H files, as well as the bd_*.c source files.  You can define
PLATFORM either from the command-line (depends on compiler) or by adding
a #define PLATFORM=? before including PLATFORM.H (or BULLET_2.H) in your
source files.

To build the demo, include all bd_*.c files and either an import library
(for dynamic linking to BULLET) or a code library (for static linking),
then compile and link.  An IDE makes this pretty simple.  Some compilers
will want import libraries entered in a particular entry field, and code
libraries in another.  Consult your compiler/linker documentation.

The compile should complete without any errors or warnings (for C).  The
link should also complete without error.  The EXE should be run to ensure
that it operates correctly.

If you have any problems with getting Bullet to work with your compiler,
contact the support sites listed in the PRODUCT SUPPORT section below.
You'll usually have an answer within 24 hours, and often within 12.  If
you find the answer inadequate, ask again, with a bit more detail and
background.


-----------------------------------------------------------------------------
5. Updates
-----------------------------------------------------------------------------

Updates are available for $5 (to cover disk and shipping costs) for any 2.x
version update at your option level.  Updates may be downloaded from the
Bullet support BBS at no charge.  Updates may also be downloaded directly
from the internet, at any time.

You can always find the current fixes available at the sites listed below
in Product Support.  The updates are available directly off the web (or BBS)
and require no password or other special means to download.  Your license kit
contains all the information and tools you need to update Bullet 2.50 through
at least version 2.99 for DOSX32, OS/2, and Win32.


-----------------------------------------------------------------------------
6. Product Support
-----------------------------------------------------------------------------

Technical support in the use of Bullet is available for licensed users at the
40th Floor BBS or by way of the Internet.

40th Floor BBS: [phone]  N-8-1

Internet: [e-mail]
          http://www.40th.com/

Response time is usually within 24 hours by internet e-mail or if you leave a
message at the support BBS.  Alternatively, you may post a letter to
Cornel Huth/6402 Ingram Rd/San Antonio TX 78238/USA.

The latest in-version (2.x) release of BULLET 2 is available for download from
the BBS, or $15 by postal mail, or from the web site.  When you order you will
receive complete instructions on how to easily get updates from the web.

Re-creatable bugs are fixed immediately. Report a new program bug and get the
fix shipped free (include your mailing address with your report, even if it
has not changed).  Past bugs are listed at the BBS and the web site.  Contact
support if you have any questions or requests.

When requesting support for possible bug(s) use the following as a guideline:

-Include a complete problem description.
-Include sample source of the problem, if necessary (small is best).
-Include necessary data files, include files, etc.
-Include step-by-step procedure to follow in order to recreate the problem.

Once done, send it to support by way of the BBS, e-mail, or postal mail to
addresses listed above.

<eof>