Driver Startup; Global Variables; Limits On Open Files - Dialogic Brooktrout Digital Board Installation And Configuration Manual

Driver Startup

Global Variables

Limits on Open Files

March 2013
After you install the driver, it has a service associated with it named
boston, a kernel-mode driver.
If driver startup fails, the error message that appears is almost
always unrelated to the actual cause of failure. The Event Log
contains an error message supplied by the driver. Using the Event
Viewer, look for the most recent entries in the System section labeled
boston. Occasionally the Event Log fills up. If this happens, set
Action\Properties\Overwrite events as needed.
Under kernel debugging environments, the debugger also contains a
message. Under other conditions, entries can also appear in the
Event Log\debugger. If you encounter unusual behavior, check the
Event Log\debugger.
If you plan to compile your application for use with the Dialogic®
Brooktrout® Bfv API library, do not use local variable names that
match any of the names of the global variables defined by the Bfv
API library. Such duplications will prevent the application from
compiling.
The Bfv API global variables include:
the variables used by getopt (for example, optind)
the _mill_priority variable, specific to Windows
The Microsoft Visual C++ compiler library limits the number of files
that can be opened. Developers often encounter this limit when
developing multithreaded Dialogic® Brooktrout® Bfv API
applications. Microsoft has updated their libraries, greatly
increasing this limit. For Visual C++ 4.1+, the limit is 512 files. You
can increase this limit using the _setmaxstdio function from the
compiler library.
Special Considerations
113