GPL Software for DOS

This package contains the full source code, executable code and documentation for current Future Lab GPL applications for DOS. This version is designated 1.36-2006.09.17 which is a package version. Each application and the Bbuuzzb database engine also have their own versions. Currently, the DOS version consists of all single user applications. Any application that requires a TCP/IP protocol stack and uses WinSock is not part of the this DOS package.

# System Requirements

You must have enough disk space for the decompressed contents of this package which is about 3.67MB currently.

These DOS version programs are built using the Turbo C V3.0 native DOS 16bit compiler and will run in native DOS or in a DOS box under various operating systems like:

- OS/2
- Windows 3.1
- Windows 95
- Windows 98
- Windows Me
- Windows NT
- Windows 2000
- Windows 2003 Server
- Windows XP
- DOS emulator under Linix/Unix
- DOS emulator under Mac

Since all of the enclosed software is extremely compact and not at all bloated, the memory requirements are minimal. Each of the DOS applications can easly run in real mode memory.

If you want to re-compile this GPL code, you will need a DOS full ANSI C complaint compiler. I use Borland's Turbo C/C++ V3. Make sure you understand the code structure and the module dependencies.

# Decompressing the Package

All files in this package use the 8.3 naming convention except for the HTML documentation which uses the '.html' extension (for compatibility with Unix). This means that you will have to de-compress the files onto a filing system that will support long filenames.

To decompress the package:

- create a top level directory, name it as you wish
- extract the package into the directory to just created

# Package Structure

This package contains all the source code, executable programs, Turbo C V3.0 library files and documentation. The directory structure of the package is as follows:

- gpl.txt - GPL license file
- readme.html - this file
- index.html - link to 'readme.html'
- apps - executable programs
- code - source code and library file tree
  - apps - GPL application code
  - clib - GPL library code
    - library - Turbo C V3 library files
  - dbeng - Bbuuzzb database API code
  - include - header files
- css - CSS Level 1 stylesheet for documentation
- images - image files for documentation
- docs - documentation tree
  - apps - GPL C application docs
  - cpp - GPL C++ docs
    - apps - GPL C++ application docs
    - library - GPL C++ library docs
  - dbeng - Bbuuzzb database API docs
  - library - GPL library docs
  - script - Unix script docs
  - socloc - socloc API docs
  - tcl - tcl docs

# Recompiling the Source Code Using Turbo C V3

In order to recompile the source code included in this package, you will need to have Turbo C V3 installed. Create a top level directory that will contain the project, library and include directories. Underneath this top level directory, create the following subdirectories:

- clib - library code
- dbeng - Bbuuzzb database engine code
- include - header files
- lib - library files
- source - GPL application code

## Loading the Compiler Tree

This section will discuss how to load each of the Turbo C V3 directories.

### clib

Copy the package library directory code\clib into this directory.

### dbeng

Copy the package library directory code\dbeng into this directory.

### include

Copy the package include directory code\include into this directory.

### lib

Copy the package binary library directory code\clib\library into this directory.

### source

Copy the package source directory code\apps into this directory.

## Other Project Details

Edit the main include file stdhead.h and make sure the correct platform is selected via the appropriate define. Also make sure the define MULTIUSER is not defined.

# Running the Applications, A Quick Start

All of the applications are text console-based and can be run from an MS-DOS prompt. The database applications require a configuration file. You should execute these database programs from within the same directory where they are stored. You should also store all configuration files within this same directory. Here is a list of all Future Lab GPL applications and their runtime requirements:

## datagen

This application only has a single user form and does not require and configuration files. This application can be placed into any directory and may be run from any directory. Refer to the datagen application doc for more information.

## db

This application is the single user command line interface to the Bbuuzzb database engine. This application needs to be executed in a directory that also contains the Bbuuzzb database configuration file. Refer to the db application doc for more information.

## dbgen

This application is the single user random data generator for the Bbuuzzb database engine. This application needs to be executed in a directory that also contains the Bbuuzzb database configuration file. Refer to the dbgen application doc for more information.

## dbstress

This application is the single user database stress program. It sends operational commands to the Bbuuzzb database engine. This application needs to be executed in a directory that also contains the Bbuuzzb database configuration file. Refer to the dbstress application doc for more information.

## fxpstres

This application only has a single user form and does not require and configuration files. This application can be placed into any directory and may be run from any directory. Refer to the fxpstres application doc for more information.

## dos2unix

This application only has a single user form and does not require and configuration files. This application can be placed into any directory and may be run from any directory. Refer to the dos2unix application doc for more information.

## iex

This application is the single user ASCII import program into the Bbuuzzb database engine. This application needs to be executed in a directory that also contains the Bbuuzzb database configuration file. Refer to the iex application doc for more information.

## iexm

This application is the multi user ASCII import program into the Bbuuzzb database server. In order to run this application, the Bbuuzzb database server must be running.

This application needs to be executed in a directory that also contains a socloc startup file and the Bbuuzzb configuration file. Refer to the iexm application doc for more information.

## rmtree

This application will delete an entire directory tree from a disk. Refer to the rmtree application doc for more information.

## daymvdel

This application will move or delete files or entire directory trees based on file age in days. This application requires a task list file before the program can be run. Refer to the daymvdel application doc for more information.

## sched

This application will track your personal schedule of events including budget. This is a single user Bbuuzzb database application. This application needs to be executed in a directory that also contains a Bbuuzzb configuration file. Refer to the sched applicaton doc for more information.

# Documentation Guide

Here is a complete guide to the included package documentation. Note that I have tried to make sure that most links function properly. You will find that all links that refer to the Future Lab GPL software function properly. Links that refer to other parts of the Future Lab web site will not function properly from this readme file. In that case, please refer to the actual Future Lab web site.

- Software change log
- C software overview
- C++ software overview
- Bbuuzzb database engine and API guide
- Socloc overview
- Socloc API guide
- GPL library guide
- Unix script guide
- Tcl software overview

Goto Top | Contact Author | Future Lab Web Site | Feedback

Copyright © 1999-2006 Future Lab, Last Updated Sep 18, 2006