home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
ZR_B451F.ZIP
/
ZYRION.DOC
< prev
next >
Wrap
Text File
|
1994-11-05
|
31KB
|
1,035 lines
NOT FOR DISTRIBUTION
PLEASE GIVE ME ALSO YOUR FEEDBACK REGARDING THIS DOCUMENTATION WHAT HAS NOT
BEEN READY YET!
THANKS CATHY AND FRANS.
(not ready yet for testers only)
General ZyRion Documentation
#421A1CR3#
The ZyRion Inter Application File Transfer Protocol
by
Frans Lupschen
International Communication Research
FreeWare releases by ICR Holland (c) 1990,91,92,93,94
ZyRion Protocol Driver [ BSR<Tm> ]
The Division Bell
MatrixSoft Systems - Protosoft
International Communication Research Holland
- ZyRion Version 4.23ß Beta Release -
Coded and Designed by Frans Lupschen
The nice name ZyRion by Marlin Lee England
Corrections by Cathy Warner
The First help (1991) by John Lots
The Idea adapted from Chuck Forberg's ZModem to develope
this reliable transfer protocol
==============================================================================
Please be so kind as to read the whole documentation. It will prevent
that you'll end up with questions to others, or ZyRion support sites.
No part of this publication may be reproduced without the prior written
consent of the copyright holders. All brand and product names mentioned
in this publication are trademarks or registered trademarks of their
respective copyright holders.
==============================================================================
Page -----------
1 ....................................... ZyRion "General info"
2 ....................................... Compatible Versions
3 ....................................... Legal Stuff
4 ....................................... SAP, FOSSIL, OS/2, ISDN
5 ....................................... Setup
6 ....................................... Environment Variables
7 ....................................... Black List Data file
8 ....................................... Secure Key information
9 ....................................... -P parameter
10 ...................................... -B Parameter
Page
11 ...................................... -C Parameter
12 ...................................... Control Send File [ @ Parameter ]
13 ...................................... DTE Rate
14 ...................................... Connect Rate
15 ...................................... Normal Baudrate
16 ...................................... ISDN Information
17 ...................................... RVC [ Real Voice Chat ]
18 ...................................... DFC Matrix
19 ...................................... Internal cache (Receive)
20 ...................................... OS/2.? and ZyRion
Page
21 ...................................... Windows and ZyRion
22 ...................................... Windows NT and ZyRion
23 ...................................... ZModem and ZyRion
24 ...................................... ZyRion and BBS Systems
25 ...................................... ZyRion and Terminal packages
26 ...................................... Error Rate
27 ...................................... Speed [ Bits Per Second ]
28 ...................................... Questions and Answers
29 ...................................... Encode/Decode AVWIT engine
30 ...................................... Problem analyses
Page
31 ...................................... Screen Layout
32 ...................................... UARTS
33 ...................................... Overruns (RTS/CTS)
34 ...................................... The old song
35 ...................................... The Devision Bell
36 ...................................... Extra Information
37 ...................................... Los Endos
ZyRion General Info. Page - 1 -
--------------------
ZyRion is a stand alone File Transfer Protocol. The purpose is to transfer data
as fast as possible over public phone lines, keep error rates low, and most -
important keep the user interface friendly.
And at last ZyRion is NOT a ZModem hack, it uses new advanced features like -
a replacement of the CRC calculations due to the transfer, These calculations
will cost CPU time, and CPS rates might drop on slow PC's. You will say "Wrong"
because CRC32 or CRC16 calculations cost just a short time. Well thats already
too much due to the fact that we want a data flow that is fast and reliable, -
and fast. I'm not refering to the Modem's speed. This is just the Async low -
level init speed based on DTE rates or just real connect rates without having
a locked DTE rate.
BSR or Bit Shift Rotation is based on a total new concept. It will handle the
binary sequence in a NON ASCII method, and there is a DFC Matrix table that -
uses variable byte output streams. Sometimes one byte can be 5 bits sometimes
7 bits etc..... In that order we gain speed without increasing the baudrate, -
and that is the heart of ZyRion.
A special bit will be used for Sync and Matrix check on a 8 by 8 matrix buffer
sequence to ensure 100% error free packet transmissions or re-transmissions.
Abstract (Can be skipped, if its not in your interrest)
-------------------------------------------------------
The ZyRion file transfer protocol provides reliable file and command
transfers with complete END--TO--END data integrity between application
programs. ZyRion's BSR/32/DFC protects against errors that continue to
sneak into even the most advanced networks.
Low error rate : Unlike traditional and many recently introduced protocols,
ZyRion safeguards all data and supervisory information with effective error
detection and in one stroke [Sbyte] correction. ZyRion rapidly transfers
files, particularly with buffered (error correcting) modems, timesharing
systems, satellite relays, and wide area packet switched networks.
User Friendliness is an important ZyRion feature. ZyRion AutoDownload
(Automatic file Download initiated without user intervention) greatly
simplifies file transfers compared to the traditional protocols.
ZyRion provides advanced file management features including Crash
Recovery, flexible control of selective file transfers, and security
verified command downloading.
ZyRion has advanced Async management features for DOS, OS2, WIN/NT and
more, If no external device driver like X00, or SIO has been detected
it will switch to a advanced internal driver called SAP.
The SAP Driver will enable auto sence for timeslice and other needed time
slice stuff, this is also the case in external mode.
ZyRion DFC based control is flexible during Bit Rotate Shift calculated
32 bit phase shift in shift out bit by bit sequence to get the best and
reliable matrix buffer, wich will send 10 bits all the time, 1 stop 8 data
bits and 1 start bit. This advanced technic is the key of ZyRion's speed.
Since 2.5 of a byte can be transfered in one 10 bits stroke, in other words
2 bytes "65 66" "A B" will only take up 10 bits, not 20 bits or 8 bits and not
16 bits (if we exclude the start and stop bits).
In high bit mode this BSR routine uses variable phase Bit Shift Rotation to
manage Short and Long bit streams. This technic IF enabled will pass another
routine called B.E.B or Byte Encoded Byte to ensure that the receiver will -
Decode the BEB byte in the proper way, since it might be that in one BEB are
two binary sequences ONE complete byte and one part byte of the next shift in
byte to be passed. A Sync bit will be inserted to ensure low error rate at all
cost.
Older _versions_ of ZyRion will escape this SB (Sync Bit) to gain more speed -
however this can lead to unrecoverable _BSR sequences, therefore I decided -
in this version NOT to escape this SB, and here comes the new name from NOT -
DFC mode but BSR mode, as a matter of fact BSR/32 is a new advanced DFC, -
technical but still compatible with the older DFC technic!
ZyRion protocol features allow implementation on a wide variety of systems
operating in a wide variety of environments. A choice of buffering and
windowing modes allows ZyRion to operate on systems that cannot support
other streaming protocols. Finely tuned control character escaping allows
operation with real world networks without Kermit's high overhead.
ZyRion is the only high performance, high reliability public protocol that
does not require larger buffer allocations for normal file transfers.
At this moment I have a BiDirectional version ready for internal Alpha -
testings. It proves that BSR can be used in such a way, but it will still -
take a few months before I can ever release a wide beta!
Complex ?
---------
ZyRion software is more complex than unreliable X+YMODEM routines, and even
the reliable _ZMODEM_ has no such complex _SB and BSR_ methods to protect it
against errors that continue to sneak in. Since ZMODEM still uses CRC16 and
CRC32 to protect data packets (512 - 1024) and ZEDZAP (512 - 8192), all these
ZMODEM based protocols are also frame based and Escaping from dirty bytes.
ZyRion keeps his data packets on one stream Sbyte hit, with a maximal of -
4096 bytes for each packet including Sync Bytes.
The overlap byte or OByte tells ZyRion (RX site) how many SBytes are waiting.
For example ONE PACKET of 4096 raw data will be reduced by the BSR routine to
4044 bytes, in that case there is a complete packet, only variable. The 4045 -
byte will be the OByte ones the OByte has been received the next waiting data
will be shifted into the _matrix buffer_ to get a full raw 4096 bytes data
packet. Is the Packet 3840 bytes, then byte 3841 will be the OByte etc.......
These packets are build in a own internal binary array wich is not compatible
with the normal _ASCII_ table. This table has a total other variable binary
form and has built up protection on both sides equal to 64 bits. Check before
one SByte hits. This will keep ZyRion at top speed and the error rate low if -
a static hit shows up. IF so (BSR_ERROR), the Overlap Byte will be shifted down
16 bytes or maximal 1024 bytes back, this will prevent to much overhead.
A disadvantage is when the (BSR_ERROR) shows up just before the SByte has been
sent. In that case ZyRion (like other protocols) needs to shift back one raw
Data Packet to ensure 100% secure and error free re-transmissions.
However ZModem needs to do this all the time (resending) one of Data Packets -
with a bad CRC. ZyRion has the advantage that such condition shows up ones in
a BAD while so to speak, but the BSR routine will ensure that the data will -
flow at top speed since the binary bit stream is variable. This will re-gain -
speed since the overhead is low.
ZyRion uses "ANTI VIRUS" technics. Don't confuse this with "SCAN" technics
like Virus Scan utilities, thats not the purpose of ZyRion. For that you need
to use one of the many good Virus Scan utilities on the market today like -
F-PROT, TBSCAN etc...... Zyrion protects only itself.
FATAL INTERACTIONS
------------------
NOTE: For hackers, don't try to remove or change ZyRion in anyway. I know you
are able to do so, but it will disable ZyRion's built in check. I only want to
stress out here that it is not an ANTI HACKERS routine. Even DON'T UNLZEXE -
"ZyRion.exe". In that case ZyRion will give the message "Infected by ......".
Briefly Zyrion's CRC32 has been stored into the Secure.key in encrypted form.
Also the Size of the current version and extra information are stored in this
Key file.
To make it reliable for REAL Virus infections, ZyRion takes its own CRC as a
Longint and this Longint is protected by a CRC16. A small DFC packet at the
end of Zyrion.exe has the same info. to compare the data with the data in the
secure.key. Regardless to any modification with either the key or with ZyRion -
it will enable the Warning routine what will tell you that it might be infected
or modified, so the note for hackers is only "in case" so that users don't
panic, because a modified secure.key or zyrion.exe file will trigger or activate
this routine.
This routine will NOT only display the message, but it will also terminate the
compare routine at the tail of the Zyrion.exe file. Result: zyrion will NOT -
work anymore to prevent "if infected" more damages to the end users computer
hard and/or software, so you as user and other people are warned, so be aware
that this can happen.
ZyRion Blacklist operations are simply based on reject inbound files and sent
to the sender. A Skip sequence is in that way that the sender skips to the next -
file "IF ANYWAY".
ZyRion will read a file (if Excists) called "BLACKLST.DAT". The format of this
file is plain ASCII, and the syntax is EXE, COM, SYS, BAT etc...... If found,
ZyRion will skip all files which have these extentions.
For example my BLACKLST.DAT file :
CLOCK$
ZYRION.EXE
COM
SYS
BAT
This will skip CLOCK$, ZYRION.EXE (ONLY) and all (.COM .SYS .BAT) Files.
Real Voice Chat (RVC) "registered/Pro" versions only, if enabled it will -
truncate each packet before the next shift in procedure and will insert
a data voice packet to advoid low CPS rates. ZyRion uses a two way SByte to -
stay in sync.
You need at least a SoundBlaster/Pro-16. All complete checked data will be
shifted in and out using the proper DMA channel in use to gain/keep speed.
You just need a microphone, speaker, or headset and while the transfer is -
in progress you can speak with the remote site in full digitized sound "Mono".
For more information about the ZyRion/Rvc-Pro call 31-45-256961 21K8!
ZyRion Header structure (Auto Download).
----------------------------------------
If your terminal can handle Auto Download sequences, then it needs to look for
this header string :
zsE000000000000 OR zs//E000000000000 if the remote uses a RVC Version.
<start><Padding 2 times><BiSync><DFC Indicator><Hex sequence>
In these days mutation "Scrambled" Viruses sneak in or P&S attacks are
modernized. ZyRion has a anti crypted shield to advoid such attacks.
Compatible Versions Page - 2 -
-------------------
Mainly all FREE releases are compatible with each other, headers and other -
handshake characters have not been changed.
But internal there are a lot of changes to gain more througput. For example if
somebody uses ZyRion 4.09F and you as end user use ZyRion 4.21F then the new -
ZyRion will be faster in transmit mode, so don't check over and over your setup
or hardware, but use allways the last new release.
NOTE : ZyRion versions before 4.04 will NOT work!
Legal Stuff Page - 3 -
-----------
FREE VERSION LICENCE AGREEMENT:
A. This is a licenced agreement between you, the end user, and
Fransiscus Jan Hendrik Lupschen. The ZyRion 4.21F - FreeWare
software and information attached hereto, hereafter "ZYRION",
is the property of Fransiscus Jan Hendrik Lupschen.
B. You acknowledge and agree that ZYRION is a proprietary product
of Fransiscus Jan Hendrik Lupschen, protected by applicable
copyright laws and international treaty provisions.
You further acknowledge and agree that all rights, title, and
interest in and to ZYRION <DFC/BSR(Tm) are and shall remain
with Fransiscus Jan Hendrik Lupschen.
C. ZYRION may be used for a period of thirty (30) days on a trial
basis to allow you to determine its suitability for your
particular application. After this period you MUST register
each copy of ZYRION that you run simultaneously.
This is done so we know who has ZYRION software installed.
Register under these terms does NOT mean you need to pay for
this Version, if so you will see another notice in this doc.
D. Registration _entitles_ you to use ZYRION and any _future
versions of ZYRION for as long as it has been released as Free-
Ware X.XXF, subject to any special licensing conditions
and/or applicable upgrade fees attached to future versions.
E. In the event that you are in violation of this licence
agreement, you agree and accept that Fransiscus Jan Hendrik -
Lupschen may cancel your registration and any rights to use -
Free ZyRion releases or Commercial releases that you may have.
In the case of a dispute over the _licence agreement_, you -
further agree and accept to fully reimburse Fransiscus Jan -
Hendrik Lupschen for legal and other expenses resulting from
the dispute.
F. ZYRION is provided "as is", without warranty of any kind or
fitness for a particular purpose, either expressed or implied,
all of are hereby explicitly disclaimed.
Fransiscus Jan Hendrik Lupschen only guarantees that ZyRion -
will occupy disk space.
G. Neither Fransiscus Jan Hendrik Lupschen "ICR Holland" nor any -
of his employees, agents, or other representatives are in any -
way obligated to provide future versions of, or support for,
ZyRion.
H. You may freely distribute and copy ZYRION provided that no fee
is charged and the _ZYRION<DFC/BSR(Tm)_ distribution archive
contains unmodified copies of the original files as produced
by Fransiscus Jan Hendrik Lupschen.
Pay Bulletin Board Systems may, however, charge their normal -
fee provided that no additional charge for ZYRION is levied.
No part of ZYRION may be modified, altered, reverse engineered,
sold, or distributed in any form whatsoever which would involve
some sort of trade without prior written _permission_ from -
Fransiscus Jan Hendrik Lupschen.
I. ZYRION may not be used in any unlawful or illegal manner.
J. ZYRION Free or commercial may only be used and registered by
physical persons for use on equipment, _including_ but not
limited to telephone lines, electricity, hardware & software,
maintained and operated 100% by means of taxed personal income.
ZYRION may not be used to provide commercial services.
FOSSIL Drivers & SAP Page - 4 -
--------------------
A FOSSIL (Fido/Opus/SEAdog Standard Interface) driver is a memory resident
program (TSR) that works as a layer between the aplication program and your
computer's hardware. ZyRion (In External mode) requires a FOSSIL driver to
function.
One of the advantages of the standard FOSSIL interface is that programs can
be ported easily to other machines and/or operating systems, or to communicate
with devices that do not normally function with the SAP, such as ISDN cards.
There are several FOSSIL drivers available. ZyRion has been tested with Opus -
Comm, X00, and BNU with good results.
X00 and BNU will be described here.
BNU
BNU, written by David Nugent, comes in two flavors. One is a device driver, -
the other is a .COM file, loaded from AUTOEXEC.BAT or another batch file.
The .COM flavor is assumed in the example.
For a detailed description of the driver, please refer to the documentation -
included in the BNU distribution archive. [AUTOEXEC.BAT]
BNU /R=1024 /T=512 /L1:57600
/R=1024
Specifies a receive buffer of 1024 bytes.
/T=512
Specifies a transmit buffer of 512 bytes.
/L1:38400
Locks COM2 at 57600 BPS (for use with a high-speed modem).
If you are not using a high-speed modem the above example should most likely -
be modified to not lock COM2.
X00
X00, written by Ray Gwinn, is a _device driver (later versions can also be -
loaded as an executable from AUTOEXEC.BAT), it is loaded from your CONFIG.SYS
file when your machine is started. For a detailed description of the X00 driver,
read the documentation included in the X00 distribution archive.
[CONFIG.SYS]
device=X00.SYS E 1 B,1,57600 T=512 R=1024
E
Disable 5 second advertisement when X00 is first loaded.
1
Number of COM ports X00 should allow to be accessed at
one time.
B,1,57600
Locks COM2 at 57600 BPS.
X00
T=512
Specifies a transmit buffer of 512 bytes.
R=1024
Specifies a receive buffer of 1024 bytes.
If you are not using a high-speed modem the above example may not be what you -
want. The most common command line for X00 is:
device=X00.SYS E 1
OS/2 2.x .. Warp etc.
ZyRion can be used in an OS/2 DOS box with excellent results.
The two drivers described above, BNU and X00, should, however, not be used for -
optimum results. Two drivers that have been tested with good results exist.
The first one, VFD for Virtual FOSSIL Driver, written by Joakim Hernberg is a -
FOSSIL layer that interfaces with the native OS/2 2.x COM driver or compatible -
replacements thereof); the other is SIO/VX00 by Ray Gwinn.
SAP (Serial Async Professional, v8.10.1)
The SAP is an internal [I] low level driver, you don't need a FOSSIL. The SAP
Driver, written by Fransiscus Jan Hendrik Lupschen, takes all Async traffic -
over. It will also control the CTS/RTS, Status Buffering, etc......
The command line options for ZyRion remain the same in all situations. There
is one exception you should keep in mind. If you use a FOSSIL (External) or -
the build in SAP (Internal), always be sure that (If you use a Locked rate)
to tell ZyRion to also use the maximum locked rate in the *.PRM File(s). You
can use "ZR-SETUP.EXE" for this purpose. We will discribe that later in this
document.
If you want you can enable "Auto dectect". This will force ZyRion to first -
look for a External FOSSIL Driver, and if found use it. If NOT found use
its own SAP. You need to tell ZyRion that the Auto detect mode is enabled by -
using the external setup program.
One of the internal SAP Advantages is, that it has no limit (Under/Upper limit
is to pass baudrates). In NON LOCKED mode, you can pass -B300 or -B320 or
-B3760 Etc...
The second SAP Advantage is that it can handle up to 36 serial ports, including
special serial cards. However the standard Free ZyRion release comes with a -
Secure.key that allows you to use a maximum of 4 communication ports.
More about SAP and FOSSIL drivers (to compare) in chapter "UARTS"!
SETUP with ZR-SETUP Page - 5 -
N/A YET
Environment Variables Page - 6 -
You need to set up some environment variable, but this is easy to do. Just be
sure that you have included the _PATH_ statement in your AUTOEXEC.BAT.
The Path statement is needed so that Zyrion knows where all his files are. A
special reason is the security key and some other related files.
For Example
-----------
Your ZyRion files are located in the subdirectory C:\NET\PROTS, and your path
statement looks like "SET PATH=C:\DOS;C:\NWCLIENT;C:\BP\BIN" then you simply
add "C:\NET\PROTS" to it like this :
"SET PATH=C:\DOS;C:\NWCLIENT;C:\BP\BIN;C:\NET\PROTS"
Under an OS/2 session you just do the same. That's all you need to do.
If needed you can add another statement to your autoexec.bat, this time its -
for a "LOG" file. ZyRion's LOG file is DSZ compatible.
If so, add this : SET ZRLOG=C:\NET\PROTS\FILENAME
The Filename can be any name you want, as long as it doesn't exceed the DOS -
limit which is 12 characters (MAX.). See your DOS manuel regarding length of
filenames.
for example:
"SET ZRLOG=C:\NET\PROTS\ZYRION.LOG" or "SET ZRLOG=C:\NET\PROTS\DSZLOG.LOG"
If you have a BBS, just be sure that your BBS is able to read this log!
NOTE:
If you use RVC then add this statement to your AUTOEXEC.BAT :
SET RVC=220,7,2
Where 220 is the Address of your soundcard.
Where 7 is the interrupt and 2 the DMA channel!
Multi Log Files for Multi Line purposes.
---------------------------------------
MultiLog Files for more lines, ZyRion will create in this case more
seperated LOG files, each log file has been called LINEX.LOG where X is
the current communication port, so -p2 will be LINE2.LOG etc...
You need to set the environment SET MULTILOG=<Drive>\Path <- no backslash -
For Example :
SET ZRLOG=C:\ZR-EXE\ZYRION.LOG { Normal single line LOG File }
SET MULTILOG=C:\ZR-EXE { MultiLine Environment }
In multiLine mode you can left out the ZRLOG= Environment.
However you also need to change in your setup MultiLog to Y = YES!
If you do not so, then NO log will be created unless you use both -
Environments, or only the Single Line Environment.
Last note : ZYRION.LOG can be any name you want, but the MultiLog has
been fixed to LINE1.LOG, LINE2.LOG, LINE3.LOG etc....
After the above setup and this section, you need to RE-BOOT your System.
Black List Data File Page - 7 -
Black List means a list of extentions that are not allowed, in short ZyRion
will skip these files.
ZyRion will search for a file called "BLACKLST.DAT" and if found it will read
it. After it has been read, Zyrion will process the data in this file.
For example EXE, in this case ZyRion will ignore all files with the extention
.EXE, like ZYRION.EXE!
I strongly advice you to create this file with one name in it, and that is -
CLOCK$. CLOCK$ will mess up your system, if somebody try's to upload it.
But if you put it in your black list Data file it will be ignored.
Here is an example :
------------------
copy con BLACKLST.DAT (Good)
CLOCK$
EXE
SYS
COM
BAT
Don't use wildcards like this :
-----------------------------
copy con BLACKLST.DAT (Wrong)
CLOCK$
*.EXE
*.SYS
*.COM
*.BAT
In this example CLOCK$, all .EXE, .SYS, .COM, .BAT files will be ignored.
Instead ZyRion will send a SKIP header frame to the sender, what basicly
tells the remote "I got this file already" to advoid wrong entries in the
LOG file, if enabled.
Secure Key information Page - 8 -
N/A YET
-P parameter Page - 9 -
The -P parameter is the second parameter after SD or RD. -P2 Will tell ZyRion
to use COM2.
The SAP Driver (Internal driver) can handle up to 36 communication ports, -
while the External driver "FOSSIL" can handle less communication ports.
Refer to your FOSSIL documentation regarding this.
-B Parameter Page - 10 -
The -B parameter is the third parameter after -Px, you will only use this -
parameter IF ZyRion has not been locked (NO Fixed DTE rate).
The -B2400, or -B9600 are real baudrates NO connect rates, The FOSSIL driver
can only handle some fixed rates like -B300, -B2400, -B9600, -B19200, -B38400
etc..., refer to your FOSSIL documentation.
The SAP driver (Internal driver from ZyRion) can handle all baudrates between
75 - 115200 baud!
So -B3412 or -B14400 or -B64000 are LEGAL baudrates, but only for the internal
driver!
-C Parameter Page - 11 -
The -C parameter is the third parameter after -Px. You will only use this -
parameter IF ZyRion has been locked (Fixed DTE rate).
-C means CONNECT RATE. It can be any connect rate that has been received from
your modem. Your communication package takes care regarding passing connect -
rates to external file transfer protocols.
The fixed DTE rate never changes for both SAP or FOSSIL!
Control Send File Page - 12 -
DTE Rate Page - 13 -
Connect Rate Page - 14 -
Normal Baudrate Page - 15 -
ISDN Information Page - 16 -
RVC [ Real Voice Chat ] Page - 17 -
DFC Matrix Page - 18 -
Internal cache (Receive) Page - 19 -
OS/2.? and ZyRion Page - 20 -
Windows and ZyRion Page - 21 -
Windows NT and ZyRion Page - 22 -
ZModem and ZyRion Page - 23 -
ZyRion and BBS Systems Page - 24 -
ZyRion and Terminal packages Page - 25 -
Error Rate Page - 26 -
Speed [ Bits Per Second ] Page - 27 -
Questions and Answers Page - 28 -
Encode/Decode AVWIT engine Page - 29 -
Problem analyses Page - 30 -
Screen Layout Page - 31 -
UARTS Page - 32 -
Overruns (RTS/CTS) Page - 33 -
The old song Page - 34 -
The Devision Bell Page - 35 -
Extra Information Page - 36 -
Los Endos Page - 37 -