readme

支持Xbase DBF格式的一套函数库的程序

Bullet/95 for Win32-Intel, Windows95, WinNT, Windows3.1 w/Win32s
README 18-Nov-1996-chh.
Installation instructions, order information, and product support numbers

-----------------------------------------------------------------------------
Shareware Installation
-----------------------------------------------------------------------------

Copy all package files to the directory you want to install to.  The
subdirectory SRC\ is created from the unzip process and contains the
source code of the demo programs, bd9demo.exe and bd9wdemo.exe.

From the install directory, do:

        x>install

The installer asks a question, then converts the BULLET95.DL_ to the
dynamic link library BULLET95.DLL.  Place BULLET95.DLL in any directory
that you want, so long as the OS can find it when it loads a program
that uses Bullet.

The install.bat file calls bsinst9.exe, a Win32 console app.  If you
do not have Win95 or NT (for example, are using OS/2 to develop in),
you have to use the installer from either the DOSX32 or OS/2 Bullet
packages (e.g., c>bsinstx bullet95.dl_).  These packages can be downloaded
from the sites listed in the Product Support section, below.

Bullet/95 itself requires Windows 95, NT 3.5 or later, or Win32s 1.25 or
later.

Distribution and other license restrictions are detailed in the
License Agreement, located in file LICENSE.TXT.

Order forms are included in the package (!ORDER.*), with detailed
ordering instructions provided in ORDER INFORMATION section below.

-----------------------------------------------------------------------------
Installation, Compiler-specific
-----------------------------------------------------------------------------

To use the Bullet library code to create an EXE, link with the BULLET9i.LIB
or BULLET9c.LIB import library, or use a .DEF file (the Bullet DLL exports
"BULLET").  Microsoft Visual C/C++ should use BULLET9c.LIB as the import
library; it is in COFF format.  If your linker uses OMF libraries, link to
BULLET9i.LIB.

For Win32, 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, 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.

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.

When building the bd_* demo, be sure to define PLATFORM.  For Win32, use
PLATFORM=5.  For example, from MS Developer Studio, in the Project Settings,
added PLATFORM=5 in the Preprocessor definitions.  bd_* demo is a console
app, unless FOR_WINDOWS=1 is defined (though this is intended only for
demo'ing on Win32s).  The shareware version is limited to 5 open files,
not counting memo files.  The registered versions are available in 100,
250, and 1024 open files.  The included bd9demo.exe is built with the
1024-file, static link Bullet library; it is ready to run.  The bd9wdemo.exe
file was built the exact same way, except FOR_WINDOWS=1 was defined.
bd9demo.exe is a console, multi-threaded app; bd9wdemo is a GUI, single-
threaded app, suitable for Win32s under Windows 3.1x.

If you have any installation problems with getting Bullet to work with 
your compiler, unregistered users should direct help requests to
[e-mail].  This is for installation problems only.  Registered users
should use [e-mail], as always.  See the PRODUCT SUPPORT section
below.

Effective with this release, shareware versions will be updated on a
regular basis, rather than once a year.  So, if this archive is older
than a month or so, a new one most likely is available.  The most
current versions are always at www.40th.com, or the 40th Floor BBS.


-----------------------------------------------------------------------------
Order Information
-----------------------------------------------------------------------------

To order Bullet by check, bank check, money-order, or cash, use form
!ORDER.FRM.  For credit card order, use form !ORDER.CC.

Payment Options
---------------

- Check, money-order, cash

Your funds have to be in US Dollars and, if by check, have to be drawn on
or payable through a US bank.  If sending currency, use Registered
AirMail.  Personal checks may require 10 working days to clear.  Most major
non-American banks have branch banks in the US.  Contact your bank for
details.  Direct wire-transfer is available: enquire to [e-mail].

To order, send payment (payable to Cornel Huth) and the order form !ORDER.FRM:

     Cornel Huth
     6402 Ingram Rd
     San Antonio, Texas 78238-3915
     USA

- Credit card, Eurochecks in DM, other

For credit card orders or for orders that cannot use the Direct-To-Author
order form, use the special Bullet/BMT Micro order form, or see
the file !ORDER.CC in the distribution package.

Order Options
-------------

Prices are:

- Option A is $ 95 for 2-process/100 open files per process, DLL
- Option B is $145 for 32-process/250 open files per process, DLL
- Option C is $195 for unlimited-process/1024 open files per process, DLL
  and LIB (OMF and COFF)
- Option E is $249 for DOSX32, OS/2, and Win32 versions of Bullet, all in
  one box, at Option C level.

All Bullet 2 versions include a printed manual and standard AirMail
shipping at no extra charge.  All OS/2 versions include a personal-use
REXX interface to Bullet at no extra charge.

The BULLET*.DLL may be distributed with your end-user programs.  There are
no run-time fees and there are no royalty fees.  Refer to the
LICENSE AGREEMENT (in file LICENSE.TXT) for limitations on distributing
BULLET*.DLL with a non-end-user package.

- Option A: permits two processes to use the Bullet DLL at the same time.
This is not a user limit, but a process limit.  This two-process limit means
that you can start two different programs that use BULLET*.DLL, and have them
both run at the same time, on the same machine.  Before starting a third
program that uses BULLET*.DLL, you must end one or both of the previous two.
Most programmers should need only 1 Bullet process active at a time.  There's
an extra process should you need it.  The total number of Bullet DBF and index
files open at any one time may be up to 100 files per process, total (sum of
data and index; memo files are not counted against this).  Most programmers
should not need more than 100 files open at the same time.

- Option B: permits 32 processes to use the Bullet DLL at the same time.
The total number of Bullet DBF and index files open at any one time may be
up to 250 files per process, total.

- Option C: permits an unlimited number of processes (limited only by the OS
itself) to use the Bullet DLL at the same time.  In addition to the BULLET
dynamic link library (BULLET*.DLL), Option C provides the BULLET static link
library (BULLET*.LIB, in both OMF and COFF format), which may be directly
linked into your end-user executable program so as to not require BULLET*.DLL.
The total number of Bullet DBF and index files open at any one time may be
up to 1024 files per process, total.  Special-order versions with more than
1024 files are available.

- Option E: is as option C, but includes Bullet for DOSX32, OS/2, and Win32
platforms, all in one box.

Note: Bullet using Win32s, as run on Windows 3.1x, is limited to a single
process.  This does not apply for Bullet using regular Win32.

Delivery Options
----------------

Standard AirMail to all destinations is available at no extra charge.
Shipping weight is approximately 2lbs (1kg) and 10x12x1" (25x30x3cm).

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.  Contact Product Support for details, or
just send $5 along with a photocopy of your receipt (for proof of purchase)
to the author, Cornel Huth.

Note: All shipments outside of the US may go through your country's Customs.
Each package is valued at the total price of the order, less any shipping
costs, if any, unless pre-arranged otherwise.  Your Customs Office may delay
mail delivery if duty is required.


-----------------------------------------------------------------------------
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 by registered users, or $5 by postal mail, or from the web site (ask
for instructions, if needed).  Re-createable 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.

For everyone else, or for general information, send e-mail to: [e-mail]

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.


-----------------------------------------------------------------------------
License Agreement
-----------------------------------------------------------------------------

See file LICENSE.TXT for license terms and restrictions.