Category : Windows 3.X Files
Archive   : TIMESTAR.ZIP
Filename : README.DOC

 
Output of file : README.DOC contained in archive : TIMESTAR.ZIP

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Special Information on running TimeStar 2.0
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Flexibility of optionally entering time/date abbreviations:

Time of day...
If you don't specify "am" or "pm", it is assumed that values
between 8:00 and 7:59 are between 8:00am and 7:59pm
eg.
"8" == 8:00a
"12" == 12:00p
"noon" == 12:00p
"7" == 7:00p

"1100" == 11:00a

Durations...
Entering a number without a ':' is interpretted as minutes
if 5 or greater, or hours if less than 5.
eg.
"20" == :20
"3" == 3:00

Dates...
"today" == today's date
"tom" == the date tomorrow
"monday" == next Monday
"tues" == next Tuesday
"sa" == next Saturday
"w" == next Wednesday
"2/1" == 2/1/90 (the next date of the abbreviated form)


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Portability
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You can have TimeStar print single page reports that list your schedule for
the present day and next, plus a 3 month calendar. It will also list all
highlighted events for up to 90 days into the future. This allows you to see
openings for appointments when away from your desk.
To highlight an activity, select the Edit-Highlight pull-down menu,
or press F3. Highlighted events appear underlined on the display and printed
schedules.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Automatic Data Saving and Making Backups
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

To minimize data loss from unexpected natural disasters such as power
interruptions, TimeStar 2.0 saves any changes you have made to your schedules
every 60 seconds. Should a power interruption occur, you would lose only
the changes (if any) you made in the last minute. This is preferable to saving
every change as you make it, which would degrade system performance.

As an added precaution TimeStar maintains a backup file (TIMEDATA.BAK) which
contains your just previously saved data.

There are few things more important than your data. Especially the scheduling
data you rely on to plan your future, and track your accomplishments.
Be sure to make additional BACKUPs of your TimeStar data file TIMEDATA.PAK
and .ARC (archive) files on a REGULAR basis. These backups should be made on
reliable diskettes, stored in a safe place.


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Special Information on TimeStar Notebook
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Importing files into TimeStar Notebook:

Cardfile -
A Cardfile is a file produced by the Windows Cardfile application.
TimeStar can read these .CRD files. And Windows Cardfile can read
TimeStar Notebook (.NBK) files, however Cardfile should not be used
to make changes to files written by Notebook with larger than the
limitted-size Cardfile cards.

Text file -
Simply a file with just text, no special formatting or binary data,
such as this README.doc file. Also called an ASCII file.

ASCII Database -
This format is commonly used for phone lists. An ASCII file with
lines of text, can be imported as a database into TimeStar Notebook.
Each line of your original file will become a page in a Notebook,
provided it ends with a carriage return/linefeed. Tabs and 2 or more
spaces in a row will be converted to line breaks in the Notebook
page. This is an easy way for you to convert a vanilla database
file into the more powerful Notebook file.


  3 Responses to “Category : Windows 3.X Files
Archive   : TIMESTAR.ZIP
Filename : README.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/