High Voltage Shareware/high1.zip/high1/DIR15/BM105.ZIP/BMHELP.HLP

Text File | 1993-12-08 | 93KB | 2,256 lines

.! CASE- TAB- MARG+1,77 VER 0053 WHEN 930323 20:30:27
.!
.! Help file for Bike Manager (TM) version 1.05
.!
.! Copyright (c) 1992 - 1993, Joern Yngve Dahl-Stamnes
.!
.! This file must not be modified. Any modification to this file may
.! cause the help system to fail.
.!
.! Date: 22nd of July 1993
.!
.!--------------------------------------------------------------------
.T News in version 1.05
The most important changes doen in Bike Manager version 1.05 is:
.l
.t 2
* Scroll-windows are now used when analysing goals. The user may also
press the F1 key when in an object menu showing defined goals to view
the goal definitions.
.l
.t 2
* Description text added to all training type objects. You may need to
update your old database if you want to add this feature. The
description text for a bike object is extended and is equival for all
types of objects.
.l
.t 2
* The trail object is extended with a flag telling if the trail is a
"multiple stage" trail, which mean you will use more than one day to
ride the trail.
.l
.t 2
* If you change the number of rating values, the program will check if
one or more training entries are outside the new rating range. If so,
the program will not let you change the number of rating values.
.l
.t 2
* The commands 'View.Weekly distance/time', 'View.Training data',
'View.Trail data' and 'View.Training HRM data' are enhanced.
.l
.t 2
* Preference mask "Protect object" added to all objects (bikes, trails
and training types). When set, it prevent the object being deleted.
.l
.t 2
* Bike attribute "Disable altitude input" added to all bike objects. You
may need to update your old database and apply this attribute if
necessary.
.l
.t 2
* The program can now record the average heart rate during a workout
(measured by Polar Accurex II). All training type objects are extended
with two fields, one for the average heart rate you want to have during
a workout and how much it may deviate from this value. You may need to
update your training type definitions if you are using a heart rate
monitor which measure your average heart rate.
.l
.t 2
* When a message is displayed at the bottom of the screen, the user may,
if using the mouse, point at the line and click any key to continue.
This work as if pressing the space bar.
.l
.t 2
* After the program has loaded a databse, it will pause for a short time
before returning to the menu. The user do not longer need to press the
space bar to continue.
.E
.!--------------------------------------------------------------------
.T News in version 1.04
Several bugs in version 1.03 has been fixed, some features has been
changed a bit and new features has been added to the program. For more
details, see file HISTORY.TXT. The major changes is:
.l
.t 2
* When selecting an object like a bike, a training type or a trail, you
may get more information about the highlighted object in the object menu
by pressing the F1 key. A window will then pop up on the screen showing
detail information about the object.
.l
.t 2
* All goal definitions are extended from one object reference to four
object references. In other words, there is no problem defining minimum
training distance if you are using more than one bike.
.l
.t 2
* The FAQ file (Frequently Asked Question and Answers) from
rec.bicycles' is now available from the program. All topics in the file
are shown in a menu, and you may choose any topic you wish to read. the
FAQ command work as the Help command.
.l
.t 2
* The new command 'View.Monthly distance/time' prints the monthly
training time and distance based on the selected training entries.
.l
.t 2
* 'View.Weekdays' is a new command which shows the training distance and
time for each weekday based on the selected training entries.
.l
.t 2
* Improved menues make it easier to move around in the menues. Some
commands have shortcuts. Better mouse support for left-handed people.
.l
.t 2
* Reading large databases on a machine without a math co-processor is
now a bit faster.
.l
.t 2
* The command switch -b is added. It turn the program into black & white
modus for those who runs it on a PC with a monocrome adapter and/or
screen.
.l
.t 2
* When adding a new training entry, you can create new bikes, training
types and trail while in the "Training Entry Form" by selecting "[new]"
in the object menu.
.l
.t 2
* The help system has been rewritten. You can now get help in all
command menues by pressing the F1 key. All help text is now stored in a
single ASCII file. NOTE: This file must not be changed in any way.
.l
.t 2
* The 'View.Weekly distance' command has been rewritten. It now shows
the weekly training time, weekly average speed and distance.
.l
.t 2
* The trail objects is extended with a new field for the accumulated
altitude for the trail (see topic "BMUPD" for more information about how
to update your old databases).
.l
.t 2
* When defining a bicycle computer, the program will ask for which
functions the computer have. The bicycle computers functions is enabled
in a menu. You should update any bicycle computer definitions in your
database, since the program check which functions the computer have when
you add a training entry to the database.
.l
.t 2
* Each bike object is extended with an attribute. This tell the program
which kind of information you want or do not want to enter when adding a
new training entry to the database. You should set the attribute for all
bikes in your old database (command 'Object.Bike Attributes').
.l
.t 2
* The command 'Print.Summary report' will now include a report based on
the rating values used by the selected training entries.
.l
.t 2
* The command switch -l is added to the program. It can be used together
with the -m command switch (use mouse) if you are left handed. It will
cause the mouse buttons to shift position.
.E
.!--------------------------------------------------------------------
.T Help
The help system in Bike Manager version 1.04 has been rewritten since
the last version of the program. It is now possible to get help in all
command menues by hitting the F1 key. In addition you can use the Help
command in the main menu to get help on the topics in the help file.
.l
Almost all topics in the help file have more than one page of text, and
you may use the "Page Up" and "Page Down" key to go the previous or the
next page. The "End" or the ESC key is used to close the text window and
return to the command menu or the help topic menu.
.l
At the bottom of the help text window you will see which page you are on
and the text "--END--" if you are on the last page for the current
topic.
.l
.c *** NOTE ***
.l
Since the help system has been rewritten, it is not longer possible to
add new topics to the help system nor modify the help file (as in
version 1.03). If you modify the help file, the help system may not
longer work as it should.
.E
.!--------------------------------------------------------------------
.T Glossary
.c Database
.l
A database is a collection of data organized after a well-defined rule.
This make it is possible for a program to search through the data. In
Bike Manager the term database is used on a collection of data that is
stored in one file on the disk. In a database you may find different
type of objects like bikes, training types and trails, training data
etc.
.l
A database is stored on the disk as on single ASCII file with the file
extension .BK1. All files must be stored in the same directory as the
program file. If not, the file cannot be found by Bike Manager.
.l 2
.t 4
.c Object
.l
An object is used to describe a bike, a trail or a training type. These
objects are used when creating a new training entries in a database.
Each object consist of different types of data depending on what kind of
type the object is.
.l 2
.t 4
.c ODO, ODOmeter
.l
An ODO/ODOmeter is a function that you find on most bicycle computer. It
continuously measure the distance. It is very commonly that you have to
reset the computer to reset the ODO value.
.l 2
.t 4
.c Training entry
.l
A training entry is a collection of data which describe a single
training (workout) on a bike. Things like training date, which bike,
which trail, distance etc. are stored in a training entry. Each training
entry is given an unique ID by Bike Manager when created.
.E
.!--------------------------------------------------------------------
.T -Main
.c Bike Manager (TM) version 1.05
.c Copyright (c) 1991 - 1993, Joern Yngve Dahl-Stamnes
.c All rights reserved.
.l
In the main menu you will find the following commands:
.l
File    - Create, save and retrieve databases, terminate the program.
.b
Objects - Create, edit and delete objects.
.b
Entry   - Create, edit and delete training entries.
.b
View    - Look at data in a database.
.b
Print   - Print data in a database to a file or a printer.
.b
Setup   - Configurate a database.
.b
Misc    - Misc. commands.
.b
FAQ     - View the topics in the FAQ file.
.b
Help    - Get help.
.l
You may also use the F1 key when in a command menu to get help on the
commands in the menu. Other topics are available by using the Help
command in the main command menu.
.E
.!--------------------------------------------------------------------
.T File
In this menu you will find commands to read a database into the program,
to store a database back to a file on the disk, to export data and other
related commands. There are also two commands to quit Bike Manager and
return to DOS or to temporary go to DOS (create DOS shell).
.l
.t 4
Command: 'File.New'
.b
This command will delete the current database in the program (wipe it
out of the memory but not on the disk) so that you may create a new
database from scratch.
.l
If the current database has been changed but not saved, you will be
warned about it and you must confirm if you really want to delete it
without saving it first. If you answer N for no, you can use the
'File.Save' command to save the database. If you answer Y for yes, you
will erase the current database from the memory (but not the file).
.l
.t 4
Command: 'File.Retrieve'
.b
Read a database on the disk into the program. When using this command,
Bike Manager will search for all databases on the disk (in the same
directory as where the program file is located) and create a menu where
the name of the found databases are shown. This make it easy to select
the database you want to read. Press ESCape (or the right mouse button)
to cancel the command.
.l
If you have a database in the program that has been changed but not
saved back to disk, you will be warned about this. You have to confirm
that you want to retrieve a new database or not. If you answer N for no,
you will cancel the command and you may use 'File.Save' to save the
current database. If you answer Y for yes, the current database will be
erased from the memory before the new database is read.
.l
.t 4
Command: 'File.Save'
.b
Store the current database back to the disk. The database must have a
name before you can save it back to disk. The revision number for the
database will be increased by one. If the database is new and without a
name, use the command 'File.Save as...' to give it a name.
.l
.t 4
Command: 'File.Save as...'
.b
This command is used to give a nameless database a name or to give a
named database a new name. It will store the database on a file with the
new name. The revision number for the database will be set to one.
.l
.t 4
Command: 'File.Memory usage'
.b
Show how much memory the current database i using. All values are in
bytes. You will see that a database will occupy more space on the disk
than in memory.
.l
.t 4
Command: 'File.Export...'
.b
If you want to export data from the database to another application
(e.g. Excel), you may use this command. It will create an ASCII file
with some of the data from the selected training entries. This can be
useful to create different graphs based on your trainings.
.l
The ASCII file will consist of one line for each training entry (note
that only the selected training entries will be printed). In each line
you will find the training date, -time, distance and ODO values before
and after the training. The different fields is separated with a
tabulator sign.
.l
If you are going to read the file into Excel, you can get Bike Manager
to write the training data in a format which Excel understand (format
"=date(year;month;day)"). If you do not select the Excel format option,
the date format will be the same as elsewhere in the database.
.l
.t 4
Command: 'File.Quit BM'
.b
This command will terminate Bike Manager. If the current database has
been changed but not saved, you will be notified, and you have to
confirm that you want to leave the program without saving the current
database. If you answer N for no, you will cancel the command and you
may use 'File.Save' to save the current database. If you answer Y for
yes, you will leave the program without saving it.
.l
.t 4
Command: 'File.Exit to DOS'
.b
Create a DOS shell where you can give DOS commands. When you want to
leave the shell, you must issue the DOS command EXIT to close the shell.
You will then return to the program.
.E
.!--------------------------------------------------------------------
.T Objects
In this menu you will find commands to create, edit and delete objects
from the database. An object may be a bike, a trail or a training type.
At least one object of each type must exist in the database before you
can add data from a training into the database.
.l
In the menu you will see this commands:
.l
.t 4
Command: 'Objects.Bike objects'
.b
This command must be used when you want to create a new bike, edit an
old bike, delete a bike or copy one bike to a new bike (with a new
name). These function is controlled in a sub-menu. Each bike object
should have an unique name.
.l
.t 4
Command: 'Objects.Trail objects'
.b
Create a new trail object, edit an old trail, delete a trail or copy one
trail to a new trail (with a new name). When using this command, you
will get a new sub-command menu where you may choose which operation you
want to perform. It is strongly recommended that each trail object have
an unique name so that you can distinguish each object when you are
going to use it.
.l
.t 4
Command: 'Objects.Training types'
.b
Work as the command described above, except that it is used when you
want to do changes to the training type objects. Each training type
object have two fields that are used when you have defined a heart rate
monitor (HRM) in the database. The fields contain the upper and lower
target zone values you will be using when doing this type of training.
If you have not defined a HRM in the database, or if the monitor you
have defined do not have a target zone option, the fields will not be
shown in the dialog window, and the values will be set to 0 by the
program. Again, each training type object should have an unique name.
.l
.t 4
Command: 'Objects.Preferences'
.b
Over time there will be a lot of object in a database, especially the
trail objects. And some of these objects may only be used a short period
during a season or a year. Some even only once a year. Outside the
period an object that is not in use are just an annoying entry in its
object menu. It would be better if these objects did not appear in the
object menu. The object preference function will handle this problem.
.l
With the command 'Objects.Preferences' you can control under which
circumstances an object shall be shown in its object menu. It is
possible to make an object invisible in its object menu when adding new
training data to the database, while it is visible when selecting
training entries based on that object.
.l
The command have a sub-menu where you choose which object type you wish
to change or view the preference setting for, e.g. bike objects. When
you have chosen the object type, you will get a new menu where you have
commands to go forward and backward in the list of objects and to change
the preference for an object. Each object have four preference flags
that you may set or clear:
.l
.t 4
flag: Hide object in the Entry form
.b
When this flag is set, the object will not be shown in its object menu
when using the commands 'Entry.New entry...' or 'Entry.Edit entry data'.
Therefore, the object cannot be used when adding new data to the database
nor when editing old training data.
.l
.t 4
flag: Hide object in the Objects menu.
.b
When the flag is set, the object will not be shown in its object menu
when using commands in the Objects command menu. This prevent you from
deleting, editing or copying the object. However, it will be shown when
using the command 'Objects.Preference'.
.l
.t 4
flag: Hide object in the Select menu
.b
If set, the object will not be visibly in its object menu when using
commands in the Select command menu (the select command is found in
several other command menues). This make it impossible to select
training entries based on the object.
.l
.t 4
flag: Do not print object
.b
This flag, when set, prevent an object to be printed to a file or a
printer when using the commands 'Print.Bike data', 'Print.Trail data' or
'Print.Training data'.
.l
.t 4
flag: Ptorect object
.b
When this flag is set for an object, you cannot delete the object from
the database. This flag is used both by Bike Manager and the tool
program BMP.
.l
.t 4
Command: 'Objects.Bike attributes'
.b
Each bike object in the database have an attribute which tell the
program which kind of data you wish to enter when adding a new training
entry to the database (where the bike is used). The attribute consist of
three different flags:
.l
.t 4
flag: Disable HRM input
.b
If set, the program will skip the fields in the Training Entry form
where you normally enters data from a heart rate monitor (HRM). Normally
these fields will be used as long as you have defined a heart rate
monitor in the database. The flag make it able to tell the program that
you do not use a heart rate monitor when you are out riding on the bike.
.l
.t 4
flag: Disable temperature input
.b
If set, prevent the program from asking about the maximum and minimum
temperature during a training when the bike was used.
.l
.t 4
flag: Disable freetext
.b
If set, disable the use of free-text for all training entries where the
bike is used. Normally the program will ask for a free-text description
for each training entry if the flag "Free text on" (controlled by the
command 'Setup.Options').
.l
.t 4
flag: Disable altitude input
.b
If set, disable the input field "Accum. altitude" in the Training Entry
Form. If you do not want to record the accumulated altitude at all, you
should set this flag for all your bikes.
.E
.!--------------------------------------------------------------------
.T -Objects.types
This command menu is common for the command 'Objects.Bike objects',
'Objects.Trail objects' and 'Objects.Training types'. In the menu you
will find commands to create new objects, edit objects and delete
objects.
.l
.t 4
command: 'Create new object'
.b
Create a new object (bike, trail or training type) in the database from
scratch. If you are going to create a new object of a given type for the
first time, this is the only command you can use in this menu. The other
commands in the menu is disabled as long as no object of the chosen
type exist in the database.
.l
.t 4
command: 'Edit object'
.b
Edit an object in the database. When using the command, you will get an
object meny showing all the existing objects of the given type. Select
the object that you want to edit, or press the ESC key to cancel the
command.
.l
.t 4
command: 'Copy object'
.b
Create a new object by copying an old object. This command can be used
when you are going to create a new object that is almost identical to an
old object. Select the object you which to copy and press RETURN to
create a new object. You may then change the fields for the old object.
The new object should be given an unique name, which mean you have to
change the first field in the dialog window.
.l
.t 4
command: 'Delete object'
.b
Delete an object from the database. The object is selected from the
object menu. You may press the ESC key to cancel the command or RETURN
to delete the object.
.E
.!--------------------------------------------------------------------
.T Entry
In this command menu you will find commands to add new data from a
workout (create a new training entry), edit an old training entry,
delete training entries or the free-text for training entries in the
database.
.l
.t 4
Command: 'Entry.New entry...'
.b
This command add a new training entry to the database. The command will
create a dialog window with different data fields where you add the data
from the training. The program takes you through each field, one by one.
When you are finished, you will be asked if the data you have given is
correct or not. A horizontal menu at the bottom in the dialog window are
used to confirm the data or not. If you choose 'OK', then the training
entry is added to the database, while 'Cancel' cause the data to be
ingored and you will return to the command menu. Choose 'Edit' if you
want to edit the data in the dialog window or 'Clear' if you want to do
it all over again. Note that some of the fields in the window may not be
in use, e.g. like the ODO before and after the ride. The fields will not
be used if you do not have defined a bicycle computer with ODOmeter
function for the bike that was used.
.l
To enter data in the bike, trail, training type and rating fields, the
program will use an object menu where you choose the right bike, trail
etc. Note that it is possible to create a new bike, trail or a training
type from the Training Entry form dialog window by selecting the "[new]"
item in the menu.
.l
If there is a heart rate monitor defined in the database, but it have
not been used during the training or if the data from it is incorrect,
you can leave the fields empty (just press RETURN). If all the time
fields for the heart rate monitor is left empty (the total time is
zero), the program will skip the three other fields used for recording
information form your heart rate monitor. For the maximum and minimum
temperature fields, enter a value greater or equal to 900 if you do not
know the temperature. A value greater or equival to 900 are the same as
N/A (Not Available).
.l
When you have verified that the data is correct (as described above),
Bike Manager will create a new window on the screen if the flag "Free
text on" is set and the attribute flag "Disable freetext" for the bike
used in the training entry is not set. This window is used to add a
free-text to the training entry. You may write whatever you like in this
window. The size of text is limited to 15 lines with 60 character in
each line.
.l
The free-text editor is very simple, but it work. The HOME key will
place the cursor at the beginning of the current line, while the END key
will move it to the end of the line. The arrow keys can be used to move
the cursor in any direction. Note that if you move the cursor up or
down, the cursor will always be placed at the beginning of the line.
.l
The DEL key will erase the character under the cursor and move the text
to the right of the cursor one place to the left, while the backspace
key (above the return key) will erase the character under the cursor and
insert a space and move the cursor on place to the left (if possible).
The INS key will move the text from the cursor (including the character
under the cursor) on place to the right and insert a space.
.l
On the top of the free-text window, the current line number and the
total number of lines will be shown. The current line will be white
while all other lines will be red.
.l
The mouse are not used by the text editor, and if you are using it, it
will be hidden while in the editor. Use the ESCape key to terminate the
editor.
.l
.t 4
Command: 'Entry.Edit entry data'
.b
This is the command you have to use to edit an old training entry. When
you use it, the program will create a menu where all selected training
entries are shown (use the command 'Entry.Select' to select training
entries). You select the entry you want to edit or press ESCape (or
right mouse button) to cancel the command. Note that you can only select
one of the selected training entries.
.l
When you have selected a training entry, you will enter the Training
Entry form dialog window as if you were going to add a new training
entry. The only difference is that the data from the selected training
entry will be used as default.
.l
You may choose to edit any field, or hit the RETURN key to leave it
unchanged. For the bike, trail, training type and rating where the
program use a menu to change the data, just hit the ESCape key (or right
mouse button if you are using the mouse) to leave the field unchanged.
Or you may select a new object or rating for the field.
.l
When you have gone through all fields, Bike Manager will ask you if the
new data is OK or not. This is described above (see 'Entry.New
entry...'). Hit the RETURN key to verify that the data is OK, or choose
another option in the horizontal menu at the bottom of the screen.
.l
.t 4
Command: 'Entry.Edit entry text'
.b
If you want to edit only the free-text for an training entry, use this
command. As for the 'Entry.Edit entry data' command, you have to choose
the training entry from a menu.
.l
When the training entry is selected, you will enter the free-text editor
window where you may edit the text. Note that there is no way to undo
any changes in the text. Hit the ESCape key to leave the editor.
.l
.t 4
Command: 'Entry.Delete entries'
.b
This command will delete all selected training entries from the
database. There is no way to undo it when you first have executed this
command, except to read the database into the program again.
.l
To avoid using this command by accident, the program will ask you if you
really want to do the command. To continue, you have to answer "YES".
All other answers (e.g. like "Y" or "YE") will be parsed as NO, and the
program will not continue with the command.
.l
When you have confirmed that you really want to do the command, the
program will, if the flag "Confirm on delete" is on (see topic "Setup"),
ask you to confirm the deletion of each training entry. Answer "y" for
yes or "n" for no. If the flag is turned off, all training entries will
be deleted without any confirmation.
.l
.t 4
Command: 'Entry.Delete freetext'
.b
Will delete the free-text for all selected training entries, and there
is no way to undo the command without reading the database into the
program again. Just as for the command described above, you have to
confirm that you really want to execute the command. Answer "YES" to
continue. Any other answers will cause the command to be aborted.
.l
When you have confirmed that you want to execute the command, the
free-text for all selected training entries will be deleted.
.l
.t 4
Command: 'Entry.Select'
.b
See topic "Select".
.E
.!--------------------------------------------------------------------
.T View
This command menu contain different commands to view the data in the
database. Some commands view data based on object types, while other
view single training entries and other the sum of many entries.
.l
Note that all commands in this menu will only view data based on the
selected training entries. All other training entries are ignored. You
will get an error message if you try to do a command and no training
entries are selected.
.l
.t 4
Command: 'View.Total distance/time'
.b
This command will display the sum of all selected training entries  in
the database in a window. In the window you will see one line for each
bike (max. 14 bikes at the same time).
.l
There are three different fields showing the total distance. The first
field is the summary of the values from the dst field (trip distance),
the second is the summary of the difference in the ODO values before and
after the training. The third distance field is the summary of the
maximum distance from each training (either from the dst field or from
the difference in the ODO values). Following the three distance field
comes the total training time and finnaly the number of training
entries.
.l
After all bikes has been shown in the the window, you will get a line
with the total for all bikes and the period (from and to date) for the
selected training entries.
.l
.t 4
Command: 'View.Weekly distance/time'
.b
Shows the summary of all selected training entries week for week. In a
window on the screen you will find one line for each week. Each line
show the week number, weekly distance, weekly ODO distance (based on the
difference between the ODO values before and after each training),
weekly training time, average speed, average weekly training distance
and the number of trainings that week.
.l
The average speed is based on the training distance (dst field) and the
training time, while the average distance is based on the training
distance (dst) field and the number of trainings found. Note that if the
training time for one or more entries for a week is zero, then the
average speed becomes too high. This is marked with an asteriks (*) at
the end of the line.
.l
If the window is not big enough to show all weeks, you may use the arrow
keys or the page up/down keys to scroll the window. The keys you can use
are shown at the bottom of the window. Press ESC to return to the
command menu.
.l
At the end of the list, the program will print the number of weeks and
the number of training entries displayed. Then two lines with the
average weekly training distance based on both the trip distance (dst
field) and the differnece in the ODO values.
.l
.t 4
Command: 'View.Monthly distance/time'
.b
Creates a window on the screen where you can view the monthly training
time, distance (both trip distance and the difference in the ODO values
before and after each training) and the number of training entries.
.l
The window will cover on year. If the selected training entries span a year,
then the program will wait until the user press the space bar before showing
the next year.
.l
This command is almost equal with the command 'Print.Monthly report'.
.l
.t 4
Command: 'View.Weekdays'
.b
The command create a window where you can see how much training you have
done on the different weekdays. For each day, you can read the training
distance, training time, accumulated climbing and the number of trainings.
.l
.t 4
Command: 'View.Training data'
.b
Looks at the number of trainings based on the training type object in
all selected training entries. In a scroll window on the screen you can
see the training distance (trip distance) and training time and number
of trainings for each training type in the database.
.l
If there is too many training types in the database, not all training types
can be shown in the window at the same time. If the window is not big
enough to show all the training types, you may scroll the window by
using the arrow keys or the page up/down keys. Press ESC to return to
the command menu.
.l
.t 4
Command: 'View.Training HRM data'
.b
This command allow you to view summary data recorded from a heart rate
monitor. In a window, you will get the time used below, in and above the
target zone for the different training types with different target
zones. The values will be shown in time and in percent. This command can
only be used if you are using a heart rate monitor.
.l
The look of the window is almost the same as for the command 'View.Training
data'. For each training type you can see the how much of the time is used
above, within or under the target zone.
.l
Again, you may use the arrow keys and the page up/down key to scroll the
window if the size of the window is too small to show all data at the
same time.
.l
.t 4
Command: 'View.Trail data'
.b
The command do almost the same work as 'View.Training data', except that
this command use the trail and not the training type. You will find training
distance, training time and the number of training for each trail used.
.l
.t 4
Command: 'View.Trail skill data'
.b
Each trail object have a data field called "Skill level". This value
tell something about how hard the trail is. 1 for easy trails and 9 for
tough and hard trails. This command will shows training distance,
training time and the number of training entries based on the trail
skill level in a window.
.l
.t 4
Command: 'View.Statistical data'
.b
When using this command the program will create a window on the screen
and print statistical data based on all selected training entries in
the window. There will be three different sets of statistical data,
speed, time and length data.
.l
For each set you will see the minimum and maximum value, average value
and standard deviation. The program will also find the number of
training entries where the average speed, the training time or the
training distance is within the shown average ± standard deviation.
.l
.t 4
Command: 'View.Selected entry data'
.b
This command shows all data for each training entry in a window on the
screen. At the bottom of the screen you will find three buttons marked
"Next", "Previous" and "Quit". They are used to show the next or the
previous training entry or to quit and return to the command menu.
.l
.t 4
Command: 'View.Selected entry text'
.b
Same as the command above, except that the free-text for each training entry
will be shown in the window.
.l
.t 4
Command: 'View.Rating descriptions'
.b
Show the defined rating values and descriptions in a window. For each
rating, the program will find how many of the selected training entries
that use this rating. The count is shown behind the rating description.
.l
.t 4
Command: 'View.Select'
.b
See topic "Select"
.E
.!--------------------------------------------------------------------
.T Print
The Print command menu contain commands to print information from the
database to a file or a printer. Only the selected training entries will
be used when the program prints information.
.l
.t 4
Command: 'Print.Print setup...'
.b
This command must be used before any other Print command, since it define
if the program shall print data to a file or to a printer, and how the
data shall be printed. In a dialog window you can define the printer device
(filename or printerport) and page layout.
.l
If you want to print to a printer connected to a printerport, you should
enter the name of the printerport. Valid printerports are LPT1, LPT2 or
LPT3. A default filename/printerport can be defined in the environment
variable BMPF in autoexec.bat, e.g.:
.l
.t 4
.i 8
set BMPF=OUTPUT.PRN
.l
The environment variable BMPI you may define two escape sequences that is
used when the program begin the printing and when the file or printerport is
being closed. The syntax is:
.l
.t 4
.i 8
set BMPI=i1,i2,...iN;e1,e2,...,eN;
.l
where i1 to iN is the ASCII value for the escape sequence that are to be
printed when the program begin the printing. e1 to eN is the ASCII
values for the escape sequence that are printed when the file or
printerport are closed (e.g. when you leave the program). All values are
in decimals.
.l
.t 4
Command: 'Print.Select'
.b
See topic "Select"
.l
.t 4
Command: 'Print.Entries'
.b
Prints data from each selected training entry. The training date, the
bike used, type of training, trail, training distance etc. will be
printed. If the flag "Print training desc." is on, then the free-text
for each training entry will be printed after the data.
.l
.t 4
Command: 'Print.Entries (brief)'
.b
A short-version of the command above. Only one line with data from each
selected training entry will be printed. In the line you will find the
date, the bike, trail, training time and distance (from the dst field
and from the difference in the ODO values before and after the ride) and
the average speed.
.l
Since the length of the line in most cases will be to short to hold all the
information as described above, some of the fields will be truncated so that
the data fits in one line.
.l
.t 4
Command: 'Print.Monthly report'
.b
Prints a report that shows the total training time and distance and the
number of rides for each month based on all selected training entries.
Also the minimum and maximum trip distance and difference in the ODO
values for each month will be printed.
.l
If the selected training entries cover more than one year, the program
will print one report for each year. After each report you will find the
monthly average training distance and -time.
.l
.t 4
Command: 'Print.Summary report'
.b
Print four different short reports based on the data from the selected
training entries. The first report is based on the bike, the second on
the training type, the third on the trail and the forth on the rating
value used in the selected training entries.
.l
In the first field in each report you will find the name of the bike,
the training type, trail or the rating. Then follows the total training
time, total training distance and the sum of the difference in the ODO
values before and after each training. The last field show the number of
trainings found for the bike, training type, trail or rating.
.l
.t 4
Command: 'Print.Bike data'
.b
Prints the data for all defined bike objects in the database, except
those bikes that have the preference flag "Do not print object" set.
.l
.t 4
Command: 'Print.Trail data'
.b
Prints the data for all trail objects defined in the database, except if
the objects preference flag "Do not print object" is on. Also the
free-text that describe the trail will be printed.
.l
.t 4
Command: 'Print.Training data'
.b
Prints data about all defined training types in the database, except
those training types which have the preference flag "Do not print
object" set.
.l
.t 4
Command: 'Print.Personal info.'
.b
Print your personal information in the database. If this data is not
defined, an error message will be shown on the screen.
.l
.t 4
Command: 'Print.From Feed'
.b
Prints a Form-Feed character to the file or to the printer. This will
begin a new page on the printer.
.l
.t 4
Command: 'Print.Close file'
.b
Close the file or the printerport. This command must be used if you want to
write data to a new file or to another printer on your PC. The command will
be executed automaticly when you leave the program (with the command
'File.Quit BM').
.E
.!--------------------------------------------------------------------
.T Goals
In the Goals command menu you will find commands to define, analyse and
delete goal definitions in the database. A goal defines what you want to
achieve by your training. The types of goals that you may define is not
of the most sophisticated, but if you use them in the right way, they
will help you find out if you will reach the goals.
.l
Each goal record is identified by a name and a type. You may choose any
name you want for each goal record, but the type depend on what kind of
goal record you want to define. This is controlled with the command
'Goals.Define goals'. It is possible to use the same name for two or
more goal record, but this is not recommended.
.l
When in an object menu showing which goals you have defined, you may
press the F1 key to view the definitions for the current goal in the
menu (the highlighted goal in the menu).
.l
.t 4
Command: 'Goals.Analyse goals'
.b
Perform the analysis of the defined goals against the selected training
entries in the database. You can choose if you want to analyse all goal
record, or those goal record which is currently active or if you only
want to analyse old goal records. A goal record is active if the current
date is within the goals period, while an old goal is when todays date
is past the goals period.
.l
The result from the analysis will be printed in a scroll window on the
screen. If you have many goals and many training entries it may take
some time before the window pop up after you executed the command. In
the scroll window you may use the arrow keys and the page up/down keys
to scroll the window, or press ESC to return to the command menu. Most
of the goal record will create three to four lines with information in
the window.
.l
The program will use the value in the distance field (trip distance) or
the value based on the difference in the ODO values before and after
each training depending on the flag "Analyse dst/ODO field". If the flag
is set, then the trip distance field will be used. If not set, then the
difference in the ODO values will be used.
.l
Note that only the selected training entries will be used during the
analysis of the goal records. You will be notified if some of the
training entries is not selected. A message will be printed at the top
of the window.
.l
.t 4
Command: 'Goals.Define goals'
.b
Defines new goals or edit old goal records. When you use this command,
you will get a menu where you choose which type of goal you want to
define or edit. When the type of goal has been chosen, a new menu
showing all defined goal records of the chosen type will pop up on the
screen. If you want to edit an old gold definition, select the one you
want to edit. To create a new goal definition, select "[new]" at the
bottom of the menu.
.l
If there are not any defined goals for the type you choosed, then the
last menu will not be shown. Instead you will go directly to the dialog
window where the goal is defined.
.l
When you define a new goal you must choose at least one object. After
you have chosen the first object, you can continue to choose three more
objects of the same type (e.g. bikes). If you do not want to select as
many as four objects, you can press the ESC button to continue with the
definition of the goal record.
.l
When you edit an old goal record, you can leave the first object
unchanged by pressing ESC button. But for object no. 2, 3 and 4, you
must select the same object. If you press ESC at this point, the object
and all objects that follows it will be erased from the goal record.
.l
.t 4
goal type "Min. distance/bike/period"
.b
This goal defines how much (distance) you want to ride within a period
(from and to date) with one or more bikes. The bikes is chosen from an
object menu, and you may create a new bike by selecting "[new]" in the
bike item menu.
.l
.t 4
goal type "Min. long trainings/bike/period"
.b
Defines how many long trainings/rides you want to have within a given
period with one or more bikes. You control how long a long ride is, and
the period is given in from and to date.
.l
.t 4
goal type "Min. distance/training/period"
.b
Defines how much training of a given type (or types) you want to perform
within a period (from and to date). You choose which training types
objects you want to use in the goal record, and you can create a new
training type by selecting "[new]" at the bottom of the menu.
.l
.t 4
goal type "Avg. weekly distance/bike/period"
.b
Defines a goal for your average weekly training distance for a given
bike (or bikes). The period is given as from a week to another, and the
two weeks does not have to be within the same year.
.l
.t 4
Command: 'Goals.Delete goals'
.b
Delete a goal record from the database. First you have to choose which
type of goal record you want to delete. Then a menu showing all goal
records of the chosen type. Select the one you want to delete, or press
ESC to cancel the command.
.l
.t 4
Command: 'Goals.Select'
.b
See topic "Select"
.E
.!--------------------------------------------------------------------
.T -Setup.Delete
The commands in this menu are used to delete misc. data definitions from
the database. When using one of the commands in the menu, whil be asked
to confirm that you really want to delete information from the database.
.l
.t 4
Command: 'Setup.Delete definitions.Computer data'
.b
Delete a bicycle computer definition from a bike object. If more than
one bike objects exist in the database, you must choose the bike the
computer you want to delete is mounted on. If you are installing a new
bicycle computer on a bike, you do not have to delete the old one from
the bike object before you define the new one. Instead edit the computer
definition and change the necessary fields.
.l
.t 4
Command: 'Setup.Delete definitions.Gearing data'
.b
Delete gearing information from a bike object. If there is more than one
bike in the database, you must choose one of the bikes in the menu. If
no gearing information exist for the bike, an error message will be
printed on the screen.
.l
.t 4
Command: 'Setup.Delete definitions.Monitor data'
.b
Delete the heart rate monitor (HRM) from the database. If you are going
to use a new HRM, you do not have to delete the old definition. Edit the
old definition and insert new data.
.l
.t 4
Command: 'Setup.Delete definitions.Personal information'
.b
Delete the personal information in the database. If the personal
information has not been defined, an error message will be printed on
the screen.
.E
.!--------------------------------------------------------------------
.T Setup
The Setup command menu is used to control how things Bike Manager shall
work, e.g. like date format, km vs. miles, if the program shall make a
backup of the database file when a database is written back to its file
on the disk etc.
.l
.t 4
Command: 'Setup.Measuring'
.b
This command control if you want to use km. or miles for distance. A new
menu showing different measuring types and the current setting will
appear on the screen. By selection one of the types, you change the unit
for this type.
.l
If you are using the mouse, click on a measuring type and it will change
between its two units. To return to the Setup command menu, press ESC.
The setting which is shown when you leave the menu will be used.
.l
Note that the program will use metric for all values in the program and
in the database file. If you choose to use miles instead of km, the
values will be converted when they are being printed to the screen, to a
file or to a printer. Changing some of the settings will not affect any
of the training entries in the database.
.l
.t 4
Command: 'Setup.Date & time format'
.b
In Bike Manager you can select on out of four different time formats and
one out of ten different date format. This format will be used both for
input and output, e.g. when selecting training entries based on the
training date or when a summary report are being printed to a printer or
a file. You can also control which sign you want to use in the time and
date format, e.g. if you want dd-mmm-yyyy or dd/mmm/yyyy.
.l
.t 4
Command: 'Setup.Computer data...'
.b
This command must be used if you are using a bicycle computer on one of
your bikes. Even if it is possible to use a computer on more than one
bike, Bike Manager assume that you are using the computer on only one
bike. So when you use this command, you will be asked to choose the bike
you are have mounted the computer on. The definitions will be a part of
the bike object.
.l
Most bicycle computers on the market require that the user define the
cicumference of the wheel in centimeters so that the computer can
calculate the correct speed and distance. The value are given as an
integer value. It is not impossible to get the circumference in
millimeters. When defining a computer, you can enter the value that the
bicycle computer are using and the correct wheelsize. Then you can get
the program to correct the distance values from the bicycle computer.
the option flag "Correct wheelsize" control this function.
.l
When you have entered data into the fields in the dialog window and
confirmed them, a new window will appear on the screen. In this menu you
can tell the program which functions the computer have. Check with the
manual for the bicycle computer which functions the computer have, and
turn on the right flags in the menu. When done, press the ESC key to
return to the Setup command menu.
.l
.t 4
Command: 'Setup.Monitor data...'
.b
If you are using a heart rate monitor (HRM) when you are training, you
should define it in the databases you are using. When the heart rate
monitor has been defined, you can enter data from the monitor into the
database.
.l
Some of the information which you will be asked about when using the
command are things that the program will not be use, such as brand name
and serial number. You will also be asked about which functions the
monitor have. This is important since the program use this information
to find out what kind of data the program can ask for when you are
entering data from a workout. A menu are being used to select the
functions the monitor have.
.l
.t 4
Command: 'Setup.Rating value/descr...'
.b
This command defines the rating values and description text. A rating
value is used by Bike Manager to rate a workout from an easy ride to an
extremely hard ride. You can select the range of the rating values (e.g.
from 1 to 9). The minimum rating value is 1 and the maximum is 29. To
make it easier to select the rating value when entering new data into
the database, you can add a short description text to each rating value.
This text will appear in the menu where you select the rating.
.l
If you try to use this command to change the number of rating values,
the program will, after you have given the new number of ratings, check
if some of the training entries are outside the new range. If so, the
program will refuse to change the number of rating values.
.l
.t 4
Command: 'Setup.Personal information...'
.b
This command is used to define the users name, address, phone number,
year of birth, sex and height. Some of these data are only information
data not used by the program, while year of birth and sex are used by
the program.
.l
.t 4
Command: 'Setup.Options'
.b
The Setup.Options command are used to control the behaviour of the
program. You will get a menu showing several option flags. By turning
flags on or off you change the way the program works. A square sign to the
left of the flag name show if the flag show if the flag is turned on or
not.
.l
See topic "Option flags" for information about each flag in the menu.
.l
.t 4
Command: 'Setup.Delete definitions'
.b
This command have a sub-command menu where you find commands to delete
data definitions made by other commands in the Setup menu. The commands
in the menu allow you to delete bicycle computers, heart rate monitor
data and personal information in the database. When using one of the
commands in the menu, you will be asked to confirm that you really want
to do the command.
.E
.!--------------------------------------------------------------------
.T Misc
In the Misc command menu you will find miscellaneous commands which does
not belong in any other command menues.
.l
.t 4
Command: 'Misc.Calendar'
.b
The calendar utility is, as the name say, a calendar. It create a window
on the screen where you can view one month at a time. You may add one
short message for each day, e.g. trainings, tours and races which you
must remember. When you read a database into the program, the program
will check if there is any messages for the next seven days. If there is
any messages, it will be printed in a window after the database has been
read. This function is controlled by the flag "Check calendar msgs." in
the Setup.Options command menu.
.l
.t 4
Command: 'Misc.Gearing chart'
.b
This is a gearing calculator which is used to find which gears you have
on your bike. By defining the size of the wheel, the number of
chainwheels and cogs and their size (number of teeths) the program will
show you a gearing chart - a window showing the gear number for any gear
combination.
.l
The gearing data can be saved as a part of a bike object. This make it
possible for you to go back to the chart later and do any modification
if needed.
.l
.t 4
Command: 'Misc.HRM adviser...'
.b
If you are using a heart rate monitor (HRM) where you can define your
target zone, Bike Manager can help you find your target zone based on
your age, sex, resting rate and the effort you want to train at. For
general training purpose, your effort should be between 60 and 80 % of
your maximum.
.l
Note that this function will only work if your PC's clock are right (at
least the year must be right) and that you personal information is
defined in the database (see 'Setup.Personal information...').
.l
In the window the command create, you will find two scales. The first
one use only your age and sex to calculate your target zone, while the
second one also use your resting rate. The second scale can be used by
people with a good fitness level. Note that the values shown in the
window are only an advice.
.l
To leave the window and return to the Misc command menu, press the ESC
key.
.E
.!--------------------------------------------------------------------
.T FAQ
This command is used to access the FAQ file from the News-list
"rec.bicycles.*". You will get a menu on the screen showing all the
topics in the FAQ file. The topics are organized in the same way as on
the original FAQ file, which make it easy to find the topic you want to
look at. Select the topic you which to view.
.l
The FAQ file is updated frequently on the net, and the modified version
of the FAQ file will normally be available some days later on the ftp
server ugle.unit.no by the the author of Bike Manager.
.l
The original FAQ file are maintained by:
.b
Mike Iglesias
.b
[e-mail]
.l
The original file can be downloaded by anonymous ftp from
draco.acs.uci.edu (128.200.34.12). The original and the modified FAQ
file for Bike Manager and other bike-related information can be
downloaded by anonymous ftp from ugle.unit.no (129.241.1.97). The files
are located in the directory local/biking.
.E
.!--------------------------------------------------------------------
.T Option flags
Option flags are used to control how the program shall work. When you
use th command 'Setup.Options' you will get a menu showing all the
option flags that you can turn on or off. To the left of the option flag
names you will find a sign if the flag is on. Below is a list of all
option flags and their function when they are set:
.l
.t 4
flag "Select new entries"
.b
When a new training entry is added to the database, it will be selected.
.l
.t 4
flag "Select read entries"
.b
All training entries will be selected after the database has been read.
.l
.t 4
flag "Backup mode"
.b
When saving a database back to the file (command 'File.Save'), the old
version of the file will be renamed from *.BK1 to *.BAK
.l
.t 4
flag "Show printer status"
.b
Create a window on the screen as long as the file or printer which the
program will print data to (through the command menu 'Print') is open.
The current page- and line number will be shown in the window. The
window will be closed when you close the file or printer.
.l
.t 4
flag "Date on new entries"
.b
Use the current date as default date when you add new training entries
to the database.
.l
.t 4
flag "Select mode AND"
.b
Select mode AND will be default when you enter the Select command menu.
If the flag is off, then OR mode will be used.
.l
.t 4
flag "Edit entry text & data"
.b
Will enter the free-text editor after you have edited an old training
entry in the database.
.l
.t 4
flag "Confirm on delete"
.b
The program will ask the user to confirm each training entry that are to
be deleted with the command 'Entry.Delete entries'
.l
.t 4
flag "Correct wheelsize"
.b
Add a correction value to each training entry if there is a bicycle
computer on the bike used during the training and the wheel
circumference is not 100% correct on the bicycle computer.
.l
.t 4
flag "Free text on"
.b
Enter the free-text editor after a new training entry has been added to
the database (command 'Entry.New entry').
.l
.t 4
flag "Analyse dst/ODO field"
.b
Use the value in the trip distance field (dst) when analysing goals. If
the flag is not set, then the difference in the ODO values before and
after the training will be used.
.l
.t 4
flag "Print training desc."
.b
Prints the free-text for each training entry when using the command
'Print.Entries'.
.l
.t 4
flag "Check calendar msgs."
.b
Check if there is calendar messages in the database for the next seven
days after the database has been read into the program. If a message is
found, then the message(s) will be printed in a window on the screen.
.E
.!--------------------------------------------------------------------
.T The menues
Bike Manager have a main menu where each command in the menu have a new
sub-menu. In the help text all command will be given in the form
'X.Y.Z'. To execute this command you must first use the main command X,
then select Y in X's menu and then the command Z in Y's menu.
.l
If a command in a menu have three dots (...) just after the command
name, it mean that this command have a dialog window for entering data.
Some command have an arrow to the right, which mean that this command
have a new sub-command menu (except for the mail commands which all have
a sub-command menu).
.l
If you do not use the mouse, you should use the arrow keys to move the
cursor in the menu. To execute a command in the menu, press the RETURN
key. The ESC key are used to go back to the previous command menu. The
ESC key will not work in the main menu.
.l
If you use the mouse, click on the command you want to execute with the
left mouse button. The right mouse button work as the ESC key. Note that
the mouse cannot be moved outside the current command window.
.l 2
.t 4
.c The Main menu
.l
When you have started Bike Manager you will see the horizontal main
command menu close to the top on the screen. Each command in the menu
have a sub-command menu.
.l
File   - Reading and saving databases, quit the program
.b
Objects- Define, edit and delete objects (bikes, trails etc.)
.b
Entry  - Edit, create and delete training data.
.b
View   - Print data in the database to the screen.
.b
Print  - Print data in the database to a file or a printer.
.b
Goals  - Define, edit, delete and analyse goals.
.b
Setup  - Configurate a database.
.b
Misc   - Calendar, Gear chart calcultator and Hear rate monitor advisor.
.b
FAQ    - Read the FAQ file.
.b
Help   - On-line help.
.l
When using the FAQ or the Help command, you will get a list of all
topics in the help file. You can also get help when in a command menu by
pressing the F1 key.
.l 2
.t 4
.c The Object menues
.l
Some of the menues in the program are objects menu, and their size will
depend on the number of objects you have defined in a database. An
object menu have a scrollbar to the left of the object names. In the
scrollbar you will find a marker which show where in the menu you are.
In many cases the number of objects will be more than the size of the
window. If you are using the keyboard, the window will scroll if
possible when you try to above or below the window.
.l
If you are using the mouse, click in the scrollbar with the left mouse
button. The window will scroll so that the marker in the scrollbar moves
to the position of the mouse.
.l
If you do not use the mouse, you can also move up and down in the window
by using the Page Up, Page Down, Home and End key on the keypad. A
search for an object can be done by pressing a letter key, e.g. press 'T'
to scroll the first object which begin with a 'T'
.E
.!--------------------------------------------------------------------
.T How to start the program
It is not necessary to add anything to the command search path to start
the program, but you may if you wish. If you choose not to add the
directory where the program is located to your path, you may either set
default to the programs directory or you may write the complete path to
the program when you start it.
.l
When the program start, you will get a logo on the screen. By pressing a
key, the logo window will disappear and the program will continue. If
you press the ESC key, then the program will terminate and you return to
DOS.
.l
There are several command switches that you may use to control the
startup of the program. A command switch is a hyphen or a slash followed
by a single-letter character. Some of the command swtiches need an
argument, which must be given after the command switch with at least on
space between the option and the argument. These command switches may be
used:
.l
.t 3
command switch -?:
.i 2
Print a short message about which switches that exist and then
terminate.
.l
.t 3
command switch -b:
.i 2
Use this command switch when you are using the program on a PC with a
monocrome screen. It will force the program to use black and white
colors only.
.t 3
command switch -m:
.i 2
Tell the program that you want to use the mouse instead of the keyboard
to move around in the menues. A mousedriver must be loaded before you
start the program. If the program ca not find the mousedriver, an error
message is printed on the screen and the program will use the keyboard
(as if the -m command switch was not used).
.l
.t 3
command switch -l:
.i 2
Can be used together with the -m command switch if you are a left handed
person. When this command switch is used, the left and right mouse
button are switched.
.l
.t 4
command switch -r:
.i 2
This command switch need an argument which must be a valid name to an
existing database file. It tell the program that you want to read the
database into the program when the program start.
.l
.t 4
command switch -s:
.i 2
Display extended information in the status window at the top of the
screen. If not used, only the database name will be printed in the
status window.
.l
.t 4
switch -D:
.i 2
Define which date format that shall be default. The numeric argument
that must be given to the command switch, is a value between 0 and 9 and
correspond to the date format found in the 'Setup.Date & Time
format.Date Format' command menu.
.l
.t 4
command switch -T:
.i 2
Define the default time format. The argument must be a number between 0
and 3 and correspond to the time format found in the 'Setup.Date & time
format.Time format' command menu.
.E
.!--------------------------------------------------------------------
.T How to use the mouse
Bike Manager support the use of a mouse in all menues. Before you start
the program, a mousedriver must have been loaded, and you must start the
program using the -m command switch.
.l
The left mouse button are used to select a command or an object from a
menu, while the right mouse button work as the ESC key, to exit from the
menu (do not work while in the main menu). If your mousedriver support
the middle button, it will work as a help button as the F1 key. If you
start Bike Manager with -m and -l command switches, then the left and
right button will change place (for left handed people).
.l
.t 6
I have reports that say there might be a problem with the Microsoft
mousdriver version 7.04. If you are using this mousedriver and the mouse
do not work properly, try load your mousedriver with the /y switch.
.E
.!--------------------------------------------------------------------
.T Introduction
.c Bike Manager (TM) version 1.05
.c Copyright (c) 1991, 1993, Joern Yngve Dahl-Stamnes
.c All rights reserved.
.l
This program is not freeware, it is shareware and distributed on "as is"
basis. You may evaluate this program for a period of 30 days. After this
time and if you intend to use the program on a regular basis, you should
registered it. The one-time registration fee is US $30 and will cover a
diskette with the latest version of the program and a copy of the user
manual in english. See the file READ.ME for more information.
.l
The program is written in Microsoft C 5.1 and compiled on a EverCom
386DX/33 with a 387DX co-prosessor under DOS 5.0. The program will work
without a x87 co-prosessor but will be slow. Bike Manager has been
tested on several computers including a Sun SparcStation running Solaris
OS with Sun Soft PC.
.l
The program does only use 8-bit ASCII text graphic. It will work on
monocrome, CGA or better without any problem. I have been told that
there has been some problem running the program on a XT with an old
Hercules graphic monocrome card, but that the -b command switch may fix
this.
.l
Bike Manager is a tool you can use to have a better overview of your
training activity. By loging all your training, races, tours and even
daily commuting you can get a good overview of how much you ride, how
often, average speed over a period etc.
.l
Data from each training session is entered by the user into the program
and is called a training entry. A training entry is based on different
object types and other data such as date, distance, time etc. An object
may be a bike, a trail or a training type. It is important that you
define at least one object of each type before you enter data from a
training. Without one bike, one trail and on training type in the
database, you cannot enter data from a training.
.l
A bicycle computer is one of the best tool you can use to be able to
enter data as correct as possible. However, it is not necessary to have
on in order to use Bike Manager. If you are using a heart rate monitor
(HRM), the program will also accept data from it.
.l
In addition to data such as distance, time etc (data that can be
measured), you can also add a free-text for each training entry. You can
write whatever you like, things like problems during the ride, weather
conditions and bike maintenance.
.l 2
.t 4
.c Create a new database.
.l
If you are using Bike Manager for the first time, there will be no
database file that you can read in and use right away. Before you can
begin feeding the program with training data, you must set up a database
in order to get full benefit of the program. Most of the definitions in
the database are only done once. Later you may copy a database when you
want to create a new one.
.l
.t 5
.c Define the bike objects
.b
With the command 'Objects.Bike objects.Create new object' you can define
the bike or bikes that you are using when out training, touring or
whatever. You may also copy one bike object to another object and give
it a new name ('Objects.Bike objects.Copy old object').
.l
When defining a bike object, you will be asked for information about the
bike. The first field in the dialog window will be the bike name. This
name is the one you will see in the bike object menu. If you defines
more than one bike, you should give each name an unique name. The you
will be asked about the brand name, model name, serial number etc. None
of these data are used in the program, but you know where you have it
when you need it.
.l
A bike object can have more information than the datafields shown in the
dialog window. Other data that are attached to a bike object is bicycle
computer information and gearing information. By using the command
'Misc.Gearing chart' you can add information to a bike about its gears.
.l
If you have a bike computer on the bike, this should also be defined by
the command 'Setup.Computer data...'. This is important, since the
program then can expect relevant data from your bike computer when you
add training data to the database.
.l 2
.t 5
.c Measuring
.b
You can choose which units you want to use for distance, height etc.
Bike Manager will store all values in metric inside the program and on
the database file. But when printing data, it can convert e.g. distance
to miles. You can also enter data in miles. To select the right units,
use the command 'Setup.Measuring'.
.l
You may combine any measure units in the menu. If you wish, you may use
miles for distance but kilometer per hour for speed.
.l
.i 4
distance    : miles or kilometer
.i 4
height      : meter of feet
.i 4
length      : meter or feet
.i 4
speed       : miles per hours (mhp) or kilometer per hour (km/h).
.i 4
temperature : deg. C or deg. F.
.l 2
.t 5
.c Define the heart rate monitor.
.b
If you are going to use a heart rate monitor when you are riding, you
have to define it in the database. Bike Manager will only ask you for
information from the heart rate monitor when it has been defined in the
database. To define it, use the command 'Setup.Monitor data...'
.l
In a dialog window you will be asked about the brand name, serial number
and which functions the heart rate monitor have. The functions can be
enabled by answering Y, while N disable it. The following functions is
"known" for the program:
.l
Target zone: a function which make it able for the user to program the
monitor with the high and low limit heart beat you want to maintain
during training. This is called a target zone.
.l
Target zone timers: the heart rate monitor can after the training, show
you how much time you have used over, within and under the target zone.
.l
Recovery rate: is a function that can measure how fast you are
recovering after a training. This is done by measuring how much lower
your heart rate is after e.g. 60 seconds. In most cases you can program
the recovery time.
.l
Stopwatch function: if the heart rate monitor also work as a stopwatch,
turn on this function.
.l
No. of stored laptimes: if the function above was turned on, then you
will be asked how many laptimes the heart rate monitor can store for
later recall.
.l 2
.t 5
.c Define the trails
.b
A trail object is a (limited) description of a trail that you are using
when out riding. In most cases you will have several trails defined in
your database. To describe a trail in detail will be an almost
impossible task. Therefore the data that the program will ask you about
are just the "highlights" from the trail. A new trail object can be
created by the command 'Objects.Trail objects.Create new object'.
.l
The trail name is the name that will appear in the trail object menu, so
you must give each trail an unique name. This make it easier to select
the right trail later. You will also be asked about the minimum and
maximum altitude and the total accumulated altitude for the trail. You
can also define a map reference and the trail skill level which tell
something about how hard the trail is. 1 means a very easy trail while 9
is a extremely hard trail. You can also add a free-text describing the
trail in more details, e.g. if there is any steep hills etc.
.l 2
.t 5
.c Define the training type objects
.b
The training type object tells something about the way you are training.
Most of the users of Bike Manager will need more than one type, e.g. on
type for time trails, one for long group rides, one for touring, one for
training etc. To create a new training type object, use the command
'Objects.Training types.Create new object'.
.l
A training type is identified by a name, as the bike and the trail
object. Each training type must be given an unique name. In addition to
the name, you will also be asked about how important speed, endurance
and strength is for this kind of training. These values are given in
percentage. Note that these values are not used in this version of Bike
Manager.
.l
Since the program support the use of a heart rate monitor (HRM), you can
also define the target zone you want to use for this type of training.
The target zone is given as maximum and minimum beat per minute. If you
do not use a HRM (must be defined before you define training types), the
fields will not be shown in the dialog window, and the program will set
the value in the fields to 0. The values will be copied into the
training entry when you add it to the database. You may later change
these values. Any changes will not affect the training entries that use
this type of training.
.l 2
.t 5
.c Date and time formats
.b
You can also choose which date and time format you want the program to
use. The date format is the one that you will see most of in the
program. There is ten different date formats and four different time
formats that you can choose from. By using the command 'Setup.Date &
time format' you will get a new command menu where you can choose if you
wish to change the date format or time format. When executing one of the
commands, you will get a menu showing the different formats. When you
have selected one of the formats in the menu, you will be asked for the
sign to be used in the format (e.g. dd-mmm-yyyy or dd/mmm/yyyy).
.l 2
.t 5
.c Define a bicycle computer
.b
If you are using a bicycle computer on a bike, you should define it the
database, so that the program knows what type of data it can expect when
the bike is used. This is done by the command 'Setup.Computer data...'.
First you will be asked about which bike this computer are being used
on. When you have selected a bike, you will get a dialog window on the
screen where you can enter information about the computer. When you have
gone through all the fields in the window and confirmed the data, a menu
showing different types of function a computer may have will appear on
the screen. Check with the user manual for the bicycle computer and make
sure that the right flags are turned on (a sign will be shown in front
of the function name when the flag is on). It is important that this is
done correctly, since Bike Manager use this information when asking
about data from a training session where the bike using this computer
where used.
.l
Among the fields in the dialog window is the "Set size" and "Actual
size". The first field shall contain the value which the bicycle
computer are using (normally the circumference of the wheel in
centimeter). The second field is the same value, but can be more correct
than the one the bicycle computer are using. These values are used to
correct the readings from the computer (only when the flag "Correct
wheelsize" is on).
.l 2
.t 5
.c Define rating values and description
.b
The rating values tells something about how hard a training was. A low
value indicate an easy ride while a high value indicate a really hard
ride (blood, sweat and tears). Each time you enter a new training into
the program, you will be asked for the rating value for the training. To
make it easy for the user, you can also attach a short description e.g.
like "Easy" or "Hard" to each rating value. This make it easier for you
when you are beeing asked about the rating value.
.l
You can choose how many rating values you want in a database, e.g.
ratings from 1 to 9. The limit is 30 rating values (1 to 29).
.l 2
.t 5
.c Personal information
.b
The personal information you may define in a database is your name and
addresse, phone number, year of birth, sex and height. Only your year of
birth and sex is used by the program. The information must be defined if
you plan to use the HRM adviser.
.l 2
.t 5
.c Options
.b
With the command 'Setup.Options' you can control how the program shall
work. By turning different flags on or off, you can enable or disable
several functions in the program. See topic "Option flags" for more
information about each flag.
.l 2
.t 5
.c Define your goals
.b
If you want to set goals for your training, Bike Manager can help you
comparing your training with your goals. By defining the goals in the
database, you can later check to see how you are doing according to the
previous defined goals. See topic "Goals" for more information.
.p
.c Using an old database to create a new one
.l
If you want to create a new database and you have an old database from
the previous training season, you may use the old one to create the new
database. This is a much faster way of doing it, since most of the
definitions that you need already exist in the old database. To create a
new one, do as follow:
.l
.i 4
Read in the old database.
.i 4
Delete all training entries.
.i 4
Delete all old calendar messages. This can be done by the BMP program
(use the command switches "-b -t -r -g"), or you may do it in Bike
Manager.
.i 4
Edit or delete all goal records. If you want to delete them, this can be
done by the BMP program (do not use the -g command switch). If you want
to use the same goals as last seasos, you must edit each goal
definition.
.i 4
Use the command 'File.Save as...' and give the database a new name.
.p
.c Environment variables
.b
Bike Manager use only a few environment variables. You do not have to
define them unless you want or if the program tell you to do so. The
variables shall be defined in autoexec.bat for permanent use, or by
using the set command in DOS for temporary use.
.l
BMPF: Define the default filename or printerport that the program shall
use when printing data.
.l
BMPI: Define the pre- and postfix escape sequence to be used when
printing data to a file or a printer. See topic "Print" for more
information.
.l
BMHELP: Normaly the program will use the helpfile BMHELP when the user
want help. An alternative file can be used instead of this file by
defining the environment variable BMHELP, e.g. set BMHELP=nohelp to use
the norwegian help file (supplied on request).
.p
.c Suggestion for improvements, bugs etc.
.b
If you have any suggestion for improvements or if you discover any bugs,
please feel free to contact me about it. Send an e-mail or a fax to me
about it, and I'll try to fix it as fast as possible.
.l
E-mail address:
.i 5
[e-mail]
.E
.!--------------------------------------------------------------------
.T Bike Manager and Windows
.l
Bike Manager is not a window application, but that does not mean you
cannot start it from windows. By creating a Program Information File
(PIF) you can start Bike Manager from windows by double click an icon.
.l
When creating the PIF-file, you shall write the path to the directory
where you have installed Bike Manager in the field "Startup directory".
You should also set the "Display Usage" to "Full Screen" and enable the
"Close Window on Exit" option.
.l
There are several icon files provided with the distribution of Bike
Manager that you can use in Windows. The icon files should work for both
Windows version 3.0 and 3.1.
.E
.!--------------------------------------------------------------------
.T Select
This command menu is located under the Entry, View, Print and Goals
command menues. Its purpose is to control which training entries that
you want to select for processing, e.g. when you want to print a summary
report. In the menu, there is several commands which make it possible to
select training entries based on which bike you used, which training
type, which trail, average speed, distance etc.
.l
If the program has been started with the command switch "-s", then you
can see in the status window how many entries that exist in the
database, and how many of them that are selected. The field left to the
date (format N/N) will show the total number of entries and the number
of selected entries.
.l
.t 4
Command : 'Select all'
.b
The command select all training entries in the database regardless of
previous selection status and selection mode.
.l
If you are using selection mode AND, this command must be used before
any other command. If not, you cannot select any entries at all.
.l
.t 4
Command : 'Unselect all'
.b
Unselect all training entries. If you are using the select mode OR, you
should use this command before you select training entries before you
start selection new training entries.
.l
.t 4
Command: 'on bike'
.b
Selects training entries based on which bike that was used. The bike is
selected from the bike object menu. If you press ESC in the menu, you
cancel the command. If you press the F1 key, you can get more
information about the current bike (the highlighted one).
.l
.t 4
Command: 'on training'
.b
Selects training entries based on the training type. The training type
is selected from the training type object menu. If you press ESC in the
menu, you cancel the command. You may press F1 to get more information
about the highlighted training type in the menu.
.l
.t 4
Command: 'on trail'
.b
The command selects training entries based on which trail you rode on.
You select the trail from the trail object menu. You may press ESC while
in the menu to cancel the command. The F1 key can be used to get more
information about the hightlighted trail.
.l
.t 4
Command: 'on rating'
.b
Selects training entries based on the rating value, which you select from
a menu showing all rating values. Press ESC while in the menu to cancel
the command.
.l
.t 4
Command: 'on date'
.b
Selects training entries based on the training date. You will be asked
for two dates in a dialog window. All training entries within the two
given dates will be selected. As default, the date on the first and the
last training entries will be used in the dialog window. You may press
ESC to cancel the command.
.l
.t 4
Command: 'on distance'
.b
Selects training entries based on the training distance. A dialog window
will appear on the window where you will be asked for the maximum and
minimum training distance. All training entries where the training
distance (trip distance) is within the maximum and minimum value will be
selected. You may press ESC to cancel the command.
.l
.t 4
Command: 'on average speed'
.b
Selects training entries based on the average speed. You will be asked
for the maximum and minimum average speed in a dialog window. All
training entries which have an average speed which is within the high
and low value will be selected. You may press ESC to cancel the command.
.l
The average speed is calculated from the training distance (trip
distance) and the training time. It the training time is 0, then the
average speed will also be set to 0.
.l
.t 4
Command: 'on training time'
.b
Selects training entries based on the training time. Again, you will be
asked for the maximum and minimum training time in a dialog window. All
entries where the training time is within the given values will be
selected. The ESC key can be used to cancel the command.
.l
.t 4
Command: 'Invert select'
.b
This command change the select flag for all training entries. In other
words - when using this command, all training entries that are selected
will not long be selected, while those which was not selected will be
selected.
.l
.t 4
Command: 'AND/OR sel. mode'
.b
Change the select mode from OR to AND or from AND to OR. By default, the
select mode will be OR unless the flag "Select mode AND" is set.
.l
When in OR mode, new training entries will be selected regardless of the
previous select status for the training entries. When using a command to
select training entries, the number of selected training entries may
increase when in OR mode. It will never reduce the number of selected
training entries.
.l
In AND mode, only the selected training entries will be evaluated when
new selection command are used. In other words, when using a command to
select training entries, the number of selected training entries may be
reduced. It can never increase.
.l 2
.t 4
Example:
.b
You can select training entries based on several criteria with using
several select commands. As an example, lets select all training entries
where a specific bike has been used within a given period:
.l
.t 4
.i 4
1. Command 'Unselect all'.
.i 4
2. Command 'on bike' and select the bike.
.i 4
3. If in OR mode, use 'AND/OR sel. mode' to set AND mode.
.i 4
5. Command 'on date' and enter the from and to date.
.l
The selected training entries will only be within the given time period
and the bike which these training entries are using will be the one you
selected with the command 'on bike'.
.E
.!--------------------------------------------------------------------
.T Errors and workarounds
All error- and information messages will be printed in a small window at
the bottom of the screen. When a message is shown in the window, the
program will wait until the user hit the spacebar.
.l
.c Irregularities an Bike Manager and workarounds.
.l
.t 5
1.
.b
All training entries are internaly kept in chronological order. If the
user use the command 'Entry.Edit entry data' and change the date, the
order may be broken, which may cause error when e.g. selection training
entries on date.
.l
This can be fixed by saving the database back to the file and the read
it again ('File.Save' and then 'File.Retrieve...').
.l
.t 5
2.
.b
If you select training entries on date and the change the date for a
selected training entry to a date that is outside the period you
selected the entries on (outside from- and to date), the entry will
still be selected.
.l
Fixed by unselect all entries and the select the again.
.l
.t 5
3.
.b
If you are using Apollo Domain PC Interconnect (DPCI) on you PC, you
should not keep the program and the files on the network device (on the
Apollo Domain disk). Sometime Bike Manger fail when it try to open the
error- and message file over the network. There is no fix for this
error.
.E
.!--------------------------------------------------------------------
.T BMP, the purger program
If you want to store only a few training entries from a large database
to a smaller database by deleting the training entries that you do not
want to store, there is a chance that there will be objects and other
kind of information that you do not need anymore. The extra data in the
smaller database can be removed by the purger program.
.l
First you read the large database into Bike Manager and delete the
training entries that you do not want to store in the new and smaller
database. Then you save the modified database to a new file using the
command 'File.Save as...' and quit Bike Manager. The purger program can
then be invoked to remove the objects that is no longer needed in the
new database. The BMP program have several command switches that control
it:
.l
.t 2
command switch: -b
.b
Prevent that any bike objects get deleted by the program even if there
exist a bike object that is not in use (not used by any training entry).
.l
.t 2
command switch: -t
.b
Prevent that any trail objects get deleted by the program.
.l
.t 2
command switch: -r
.b
Prevent that any training type objects get deleted by the program.
.l
.t 2
command switch: -g
.b
Prevent any goal definitions to be deleted by the program.
.l
.t 2
command switch: -m
.b
Prevent that any calendar messages outside the date period the training
entries in the database represent get deleted by the program.
.l
.t 2
command switch: -v
.b
Turn on the verbose mode. When the verbose mode is on, the program will
print messages to the screen when something is deleted from the
database.
.l
.t 2
command switch: -s name
.b
Change the database name if any changes has been done by the program.
This cause the database to be written to a different database file. The
name of the new database file must be given after the command switch.
.l
.t 2
name
.b
Gives the name of the database to be read by the program. This argument
must be given. If not, the program will print an error message and
terminate.
.p
Example:
.l
.i
bmp -v foobar -s xyzzy
.l
Read the database FOOBAR and delete all objects, goals and calendar
messages that is not needed. If any changes is done, the database is
written back to the database file XYZZY.
.l
.c Note
.l
Note that the database will only be written back to the disk if the
program makes any changes in the database. If no objects, goal records
or calendar messages is deleted, then the program will not write
anything back to the disk.
.l
Since the program does not communicate with the user except through
command switches and arguments, the program can be used in a batch-file.
.E
.!--------------------------------------------------------------------
.T BMUPD, the update program
In Bike Manager version 1.05, there is some changes in the trail
objects. A new field "Total Accumulated Altitude" (TAA) is added to each
object. This field contain, as the name say, the total accumulated
altitude for the trail.
.l
All training entries has also extended with the same field. But if you
have databases that has been created by Bike Manager version 1.03, 1.02
or 1.01, this field will be set to 0 when an old database are read by
Bike Manager. The field in each training entry should be updated.
.l
The program BMUPD has been provided for the user to make the update of
all training entries easier. The program will update all training
entries based on the information in each trail.
.l
To update an old database, you must first update each trail object in
the database by reading it into Bike Manager and then use the command
'Object.Trail objects.Edit old object' and update each trail object. The
accumulated altitude can be measured with a bicycle computer that have
such a function, or it can be estimated by reading a map.
.l
When the trails are updated, save the database back to disk by the
command 'File.Save' and the quit Bike Manager. Then start the update
program BMUPD and let it do the work.
.l
The BMUPD program have some command switches that control how it should
update the training entries:
.l
.t 2
command switch: -a
.b
By default, only the training entries where the value in the field for
the accumulated altitude is equal to 0 that will be updated. If the
value is higher than 0, the training entry will not be updated by the
program, unless the -a command switch is given. See also command switch
-z.
.l
.t 2
command switch: -v
.b
Turn on the verbose mode, which cause the program to write information
to the screen when working.
.l
.t 2
command switch: -s name
.b
Tell the program to save the database back to a different database file
if any modification has been done by the database BMUPD read. The new
name must be given after the -s command switch.
.l
.t 2
command switch: -z
.b
By default, the program will only update a training entry if the value
in the "Total Acummulated Altitude" in the trail object the entry use is
higher than 0. If the value is 0, then the training object will not be
updated, which mean the program will not set the value in a training
entry to 0. If the -z command switch is given, then the program can set
the value in the training entry to 0.
.p
Example:
.l
.i
bmupd -v foobar -s xyzzy
.l
Read the database FOOBAR and update all training entries where the value
in the field acummulated altitude in the training entry is equal to 0
and use a trail where the value in the "Total Acummulated Altitude" is
greater than 0. If any changes is done by the program, the database will
be written back to the new database file named XYZZY.
.l
Since the program does not communicate with the user except through
command switches and arguments, the program can be used in a batch-file.
.E
.!--------------------------------------------------------------------
.T about Bike Manager
.c Bike Manager (TM)
.c version 1.05
.c Copyright (c) 1991 - 1993
.c Joern Yngve Dahl-Stamnes
.c Frostavn 7
.c N-7043 Trondheim
.c Norway
.l
.c e-mail: [e-mail]
.l
.c All rights reserved.
.l
.c release date 26. July 1993
.l
Bike Manager is written in C and compiled with Microsoft C compiler
version 5.1 under MS-DOS 5.00 on a EverCom 386DX/33 with a 387DX/33.
.E
.!====================================================================
.!
.! End of file.