1. vxdsource.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (vxdsource.zip)

First beta release of the Data Capture application notes.

1. VxD currently only maintains two static buffers of 8192 (8k)
bytes apiece for incoming CRN news data.  Next release should
support dynamic allocation of filespace dependent on the data
size transmitted in absolute block 0.  Unpredictable results
will occur if a file greater than 8192 bytes is transmitted.

2. If the very first block of a new CRN data file is not block
number 0, then the remainder of the entire file will be ignored.
This harks back to number 1 and is a temporary issue based on
filesize issues.

3. As long as two different data files do not overlap, the VxD
will not complain about both of them being either message #1 or
message #0.  However, there should be at least a one to two
second gap between the files in this case.  

4. Once sync is obtained by the VxD, any data will be ignored 
for the first two seconds.  Any data received during this two
second interval will cause the remainder of that datafile to 
be discarded until no blocks have been received for a full two
seconds.  Then, the VxD will be clear to receive data.  This
works independently between datafile #0 and datafile #1.

5. If sync is lost for more than one second, any datafiles in
progress will be discarded and the remainder of the data will
be ignored until the two second "quiet zone" has passed after
the last data.

6. An apparently incomplete data file (due to one or more lost
blocks of data during reception) will be flagged as complete
after approximately two seconds of no additional data being
received for that particular datafile.  If it is anticipated
that pager data may intrude on the transmission of a data file
for more than two seconds per shot, now is a good time to make
us aware of this, as incomplete files will be stored.

7. Although the data capture application decodes any filename
(zero terminated) from the front of the resultant data stream,
it currently stores all incoming datafiles as C:\TEMP\OUTPUT.HTM.
This, obviously, will be corrected very soon.

8. Make sure that the frequency used for testing purposes is
transmitting MBS encoded datastream when the data capture application
is started.  If no other ADS Cadet product has scanned the FM Band,
the data capture program will do this upon first startup.  It's 
important that some application has scanned the FM Band with MBS
sync in progress on the frequency desired so that the data capture
application will get the MBS station from the VxD.

9. Datacap application appears initially as a taskbar icon of a yellow
circle with a blue and white interior.  If this icon has a red "X" 
across it, then MBS sync is not currently detected.  When sync is
established, the X disappears and the blue/white interior of the icon
will spin.

10. Right-click on the datacap blue/white icon to bring up the setup
dialog.  Choose the MBS frequency from the list and press "Use this one".
If the desired frequency is not shown in the list, then another Cadet
application will need to be run in order to Rescan the FM Band.  Be sure
that MBS sync is available on the desired frequency before doing this.

11. The second tab on the setup dialog does not perform anything yet.
The data capture application is always looking for data and will store
it when it is received.

12. Left-click on the datacap blue/white icon to bring up the splash
dialog for the program.  Pressing OK simply clears the dialog from the
screen.  Pressing "Shut Down" will end the data capture application.
The listbox on the right side of the splash dialog is only temporary
and is used to display debug information coming from the VxD regarding
CRN/MBS data.  This will obviously disappear in the next release.

WinSoft Development Corporation
24 July, 1996