|
DESCRIPTION
The Kernel Stream Driver comes with the following files:
| File
Name |
Description |
| brg.c |
Baud
Rate Generator Example |
| devioctl.h |
Header
for I/O Control calls |
| dtest.c |
C
source for dtest.exe |
| dtest.exe |
Test
program |
| install.txt |
Installation
Description |
| list.com |
Utility
to look at MPEG structure |
| mpeg.bat |
Runs
stest.exe and does a file compare |
| mpeg1.bat |
Runs
stest.exe and does a file compare |
| mrec.c |
C
source for mrec.exe |
| mrec.exe |
Send
and Receive MPEG in stream mode |
| msend.c |
C
source for msend.exe |
| msend.exe |
Send
MPEG in stream mode |
| mtest.c |
C
source for mtest.exe |
| mtest.exe |
Copy
files in both directions over the link |
| raw.doc |
Description
of stream mode operation |
| raw.key |
Special
registry key for raw or stream mode |
| srec.exe |
Program
like mrec.exe except has synchronization |
| stats.c |
C
source for reporting on driver statistics |
| stest.c |
C
source for stest.exe |
| stest.exe |
Same
as mtest except with synchronization |
| sync.c |
C
source for sync.exe |
| sync.exe |
Stand
along synchronization program |
| t1mlink.key |
Standard
driver key |
| t1mlink.sys |
Kernel
Stream Driver |
Data is transmitted without HDLC framing with this driver.
Because of this it is sometimes called a stream mode or raw
mode driver. Because it doesn't add or take away information
to the stream of data, it can be used to transmit or receive
an MPEG Transport or Program Streams. The Kernel Stream Driver
can be used to transmit or receive data over a point to multi-point
connection. It produces a half duplex flow of data. If control
signaling (backchannel) is required it would have to be provided
by using a second communications path.
This driver can be interfaced with the output of an encoder
card, such as the MovieMaker or Forge/Fusion and it can transmit
this output to a set-top box or other type of integrated receiver/decoder
(IRD). A program is provided to give byte alignment called
synch.exe. Byte alignment is also called synchronization in
the documentation.
It
is a requirement of the T1/WAN Master and Kernel Stream Driver
that there be no breaks in the flow of data. This is because
there is now way of adding acceptable idle characters or "padding"
characters to the stream. The stream must be continuous and
unchanged with no gaps. This limits the ultimate data rate
which can be transmitted since it puts restrictions on the
host computer system resources because the stream driver must
have the highest priority. In spite of this, data rates of
1.5M bits/sec (T1 rate) can be achieved.
An example using the Kernel Stream Driver is shown below:

|