Abekas_A60_Digital_Disk_Recorder_Ethernet_Preliminary_Manual_Dec87 Abekas A60 Digital Disk Recorder Ethernet Preliminary Manual Dec87

A

Carllnn

C;"mflany

digital

disk

recorder

A60

Ethernet

Manual

PRELIMINARY

A60

Ethernet

Manual

Rev

1.2

7-DEC-87

Copyright

(C)

1987

Abekas

Video

Systems,

Inc.

This

manual

describes

the

installation

and

use

of

the

A60

as

an

Ethernet

node

supporting

file

transfer

and

remote

login

using

some

of

the

TCP/IP

family

of

protocols.

It

also

includes

an

application

note

describing

some

of

the

mechanisms

behind

the

file

transfers.

Abekas

Video

Systems,

Inc.

101

Galveston

Drive

Redwood

City,

CA

94063

(415)

369-5111

uucp

Email:

••.

!pyramid!abekas!a60mail

1.

2.

3.

4.

CONTENTS

Introduction

to

Ethernet

1.1

Ethernet

••.•

and

TCP/IP.

1.2

TCP/IP

.•••••.

1.3

Telnet

and

FTP.

1.4

Unix

'r'

Commands.

1.5

The

Abekas

A60

..•.

TCP/IP

Application

Notes

••••.

2.1

Typical

File

Transfer

••

2.2

Layered

Model

•••.

2.3

Physical

layer.

2.4

2.5

2.6

2.7

Transceivers

••..

Different

Ethernet

Standards.

SQE

•••.•...•••..•••

Data

Link

Layer

••••..

Ethernet

Addresses.

Network

Layer

••..••••

IP

••••••••..••.•••..

Internet

Addresses

•.

ICMP.

GGP.

ARP

••

RARP

••••••••

Transport

Layer

..

TCP

•••••••••.

UDP

••••••••••

Upper

Levels

.•

Telnet

••

FTP

••••

. . . . . . . . . .

TFTP

••

rep

••

. . . . . . . . . . . . .

Installing

an

A60

on

a

Unix

Network

•.

/

etc/hosts

.•.....•..•.•..••....

Setting

the

A60

Internet

Address.

Setting

the

A60

Hostname

..

/etc/ethers

....•....•

Implementation

Notes.

Ethernet

Address

.•.

Address

Resolution

.•.

IP

••.•••.•......•.

i

2

3

4

5

6

7

8

9

10

11

12

13

14

16

17

18

20

22

24

25

10.

11.

Appendix

••••••••••.•••••••••••

10.1

10.2

10.3

10.4

10.5

10.6

Complete

TCP/IP

Packet

••••••••

FTP

Implementation.

Defaults

••••••••

Opening

Message

.•..

Commands

and

Responses

••

File

Names

•••••••.••••••••••..

rlogin

Implementation

••

rsh

Implementation.

rcp

Implementation.

Bibliography

••••••..•.•••

iii

59

60

62

63

64

A60

Ethernet

Manual

1.

Introduction

to

Ethernet

and

TCP/IP

1.1

Ethernet

is

a

Local

Area

Network

(LAN)

Standard

originally

developed

at

Xerox

Palo

Alto

Research

Center.

2

Ethernet

interconnects

a

group

of

computers

(referred

to

as

hosts

or

nodes)

with

a

single

50-ohm

coaxial

cable

with

terminations

.at

both

ends.

Data

is

passed

serially

at

10MHz

in

the

form

of

packets,

that

is

in

chunks

anywhere

from

46

up

to

1500

bytes

or

characters.

Each

packet

carries

addressing

information

to

show

its'

source

and

destination.

Unlike

the

Public

switched

telephone

system

or

a

video

routing

matrix

the

single

cable

is

shared

by

all

the

devices

on

the

network

so

there

are

a

set

of

rules

to

determine

when

a

node

can

access

the

cable.

The

technique

used

is

referred

to

as

Carrier

Sense

Multiple

Access

with

Collision

Detection

(CSMA-CD).

Before

transmitting

a

node

listens

to

confirm

that

nobody

else

is

transmitting,

then,

as

it

transmits

it

continues

to

monitor

the

cable

in

case

another

node

started

transmitting

at

the

same·time.

If

two

devices

transmit

simultaneously

it

is

referred

to

as

a

collision

and

both

devices

have

to

stop

immediately

and

wait

a

random

amount

of

time

before

attempting

to

transmit

again.

Different

manufacturers

have

adopted

the

low-level

Ethernet

hardware

and

packet

specifications

and

built

their

own

networks

on

top

of

it.

Xerox

XNS, IBM-SNA, HP-NS

and

DEC-DECnet

are

all

networking

systems

that

allow

users

to

share

resources

and

files

and

can

run

over

Ethernet.

In

the

area

of

Personal

Computers

3com

Corporation

and

Novell

are

supplying

File

server

systems

based

on

Ethernet.

Small

scale

Office

LAN's

are

mostly

based

on

cheapernet

which

uses

thin

RG58

50

Ohm

cable

and

BNC

connectors,

i~

this

case

the

coaxial

cable

is

'T'eed

directly

onto

the

Ethernet

Interface

in

the

computer.

Higher

level

applications

use

better

quality

thick

yellow

cable

and

external

transceivers

that

can

attach

to

the

cable

with

a

spike-like

tap.

PRELIMINARY

Ethernet

A60

Ethernet

Manual

3

1.2

TCP/IP

The

TCP/IP

protocol

family

is

emerging

as

a

useful

common

standard

for

network

interconnection.

The

strength

of

TCP/IP

has

been

that

it

is

not

tied

to

any

particular

manufacturer,

it

is

the

result

of

extensive

research

since

the

70's

by

the

Advanced

Research

Projects

Agency

(ARPA)

community.

with

backing

from

the

DOD

the

emphasis

for

these

protocols

has

been

to

interconnect

different

types

of

computers

running

different

operating

systems.

TCP/IP

is

now

available

as

an

add

on

to

most

computer

systems

either

in

the

form

of

and

interface

board

with

built

in

software

such

as

the

Excelan

Ethernet

Controllers

or

as

an

extra

software

package

running

along

side

a

native

Ethernet

implementation.

(The

Biblography

for

this

manual

lists

some

of

the

companies

offering

TCP/IP

packages)

One

reason

for

the

spread

of

TCP/IP

amongst

the

Computer

Graphics

Community

has

been

its

inclusion

in

the

Berkeley

Versions

of

the

UNIX

operating

system

(referred

to

as

4.2

BSD

UNIX

as

opposed

to

[he

AT&T

Unix

V),

most

graphics

engines

and

the

Workstations

that

control

them

use

Unix

as

it

is

a

popular

operating

system

for

software

development.

TCP

and

IP

are

acronyms

for

'Transmission

Control

Protocol'

and

'Inter-network

Protocol'

just

two

of

the

layers

in

the

suite

of

communications

protocols

that

are

required

to

allow

transfer

of

data

from

one

computer

to

another.

IP

is

the

layer

immediately

on

top

of

Ethernet

that

adds

Network

addressing

information

to

the

packet.

These

Internet

addresses

allow

IP

packets

to

be

transferred

to

other

networks

not

just

Ethernet,

it

is

similar

to

the

way

that

Containerized

freight

can

be

carried

equally

well

by

road

rail

or

sea.

TCP

provides

an

error

free

bidirectional

communications

channel

above

which

other

utilities

such

as

a

remote

login

or

file

transfer

can

be

built.

TCP

works

by

giving

each

packet

a

sequence

number

so

that

a

message

or

file

can

be

reassembled

even

if

the

packets

arrive

in

the

wrong

order.

PRELIMINARY

TCP/IP

A60

Ethernet

Manual

4

TCP

also

has

an

acknowledgement

mechanism

whereby

the

receiver

replys

with

the

latest

complete

sequence

number

it

has

assembled,

so

that

should

a

packet

get

lost

or

delayed

in

the

network

the

sender

will

retransmit

the

missing

packet

if

it

hasn't

been

acknowledged

within

a

reasonable

timeout

period.

The

third

TCP

mechanism

is

the

window

which

limits

the

amount

of

unacknowledged

data

the

sender

can

send

out,

so

that

it

can't

get

too

far

ahead

if

the

receiver

is

missing

a

packet

from

back

at

the

start

of

the

message.

For

the

majority

of

File

transfers

or

TCP

connections

there

is

no

data

lost,

all

the

packets

arrive

in

the

correct

order,

the

power

of

the

TCP/IP

protocols

lies

in

the

fact

that

they

are

not

restricted

to

running

on

a

single

local

area

network.

The

ARPA

Internet

for

example

combines

over

a

100

different

networks

and and

includes

satellite

links

across

to

research

facilities

in

Europe.

When

packets

are

passing

across

several

networks

through

'gateways'

which

provide

an

interface

from

one

type

of

network

to

~nother

there

is

more

chance

of

a

packet

getting

lost.

There

is

no

~uarantee

that

all

that

packets

will

take

the

same

route

to

the

destination,

this

is

possible

since

each

packet

carries

separate

addressing

information.

It

is

up

to

the

gateways

to

decide

what

the

most

efficient

route

is

and

if

during

the

life

of

the

connection

one

of

the

intervening

gateways

or

networks

goes

down

the

TCP/IP

protocol

is

robust

enough

to

be

able

to

replace

any

unacknowledged

lost

data

by

retransmission.

That

is

assuming

an

alternative

route

can

be

found.

1.3

Telnet

and

FTP

On

top

of

the

guaranteed

delivery

TCP

connections

the

A60

supports

file

transfer

and

remote

control.

Remote

control

is

achieved

by

allowing

the

remote

user

to

'login'

as

if

the

A60

were

another

computer

and

type

commands

interactively.

There

are

two

ways

of

doing

each,

firstly

the

official

ARPA

file

transfer

and

remote

login

utilities

called

FTP

(File

Transfer

Protocol)

and

Telnet

which

are

specifically

intended

to

work

between

different

Computer

architectures

and

Operating

Systems.

pRELIMINARY

Telnet

and

FTP

A60

Ethernet

Manual

5

1.4

Unix

'r'

Commands

The

other

alternative

is

the

native

Unix

utilities

'rcp'

(Remote

CoPy)

'rlogin'

(Remote

Login)

and

'rsh'

(remote

shell)

these

will

be

popular

with

Unix

users

since

they

offer

a

less

verbose

user

interface

-

file

transfers

are

achieved

by

cryptic

one

line

commands

rather

than

FTP

which

normally

produces

a

secondary

prompt

and

requires

at

least

three

commands

to

transfer

one

file.

1.5

The

Abekas

A60

The

A60

can

be

viewed

as

a

Video

Server

-

permitting

all

the

rendering

engines

and

computers

in

a

graphics

lab

to

share

the

ability

to

tryout

animation

sequences

and

layoff

rendered

images

without

the

preroll

and

lineup

problems

associated

with

single

frame

VTRs.

It

is

a

powerful

sharable

resource

that

treats

all

the

frames

or

fields

on

a

disk

as

separate

files

that

can

be

copied

to

or

from

the

A60.

The

remote

control

provided

across

Ethernet

is

intended

to

be

human

readable

in

that

the

commands

for

playing

or

setting

up

segments

are

executed

by

merely

typing

"PLAY"

or

"DEFSEG

0.20

1.30"

so

a

user

sitting

at

a

workstation

can

easily

preview

frames

or

animations

without

the

need

for

a

remote

control

panels

beside

every

workstation.

As

an

Ethernet

device

the

A60

appears

to

be

just

another

node

that

files

can

be

transferred

to

in

the

same way

they

would

be

moved

from

one

computer

system

to

another,

there

is

no

need

for

a

separate

VTR

controller

or

special

software.

Installation

on

Ethernet

is

just

a

question

of

the

plugging

the

A60

into

a

Transceiver

which

is

a

small

box

that

provides

the

interface

to

the

Ethernet

Coax.

The

System

Manager

then

specifies

an

Internet

address

for

the

machine

which

has

to

be

entered

on

the

A60

control

panel.

The

other

computers

on

the

network

can

then

use

this

Internet

address

to

access

the

A60.

PRELIMINARY

The

Abekas

A60

Ethernet

Manual

6

2.

TCP/IP

Application

Notes

This

section

gives

a

brief

outline

of

the

functions

of

each

of

the

protocols

used

in

the

A60

and

the

way

they

interact.

2.1

Typical

File

Transfer

Take

for

example

the

opening

of

an

FTP

connection

on

a

Unix

system.

To

invoke

the

FTP

program

the

user

types

:

unix%

ftp

a60

Which

causes

a

control

connection

to

be

opened

to

the

host

specified.

The

hostname

is

the

name

used

to

refer

to

the

A60

on

the

users'

machine.

Somewhere

there

will

be

a

file

(/etc/hosts

on

unix)

which

gives

the

mapping

between

the

name

(or

some

other

optional

alias)

and

the

Internet

Address

that

has

been

assigned

for

the

A60.

A

typical

entry

in

/etc/hosts

has

the

following

form

:

192.5.200.9

a60

The

FTP

program

will

first

find

the

Internet

address

of

the

remote

host

by

referring

to

the

/etc/hosts

file.

Then

it

has

to

find

an

Ethernet

address

that

corresponds

to

this

Internet

address.

This

Ethernet

address

is

the

address

of

a

device

on

the

local

ethernet,

either

the

A60

itself

or

a

Gateway

through

which

the

A60

can

be

reached.

In

some

cases

the

host

computer

may

have

retained

this

information

from

a

but

for

the

first

transfer

to

an

unknown

remote

host

the

local

host

has

to

resolve

the

Internet

-

Ethernet

address

mapping.

To

do

this

it

uses

the

Address

Resolution

Protocol

(ARP).

ARP

involves

sending

a

broadcast

packet

to

all

the

hosts

on

the

network.

only

the

host

with

the

required

Internet

address

or

a

Gateway

that

can

reach

it

will

reply

with

a

ARP

reply

packet

supplying

the

requested

Ethernet

address.

)RELIMINARY

Typical

File

Transfer

A60

Ethernet

Manual

7

Once

the

local

host

knows

how

to

reach

the

A60

over

Ethernet

it

can

open

up

a TCP

connection

to

the

FTP

port

on

the

A60.

The

A60

which

has

been

waiting

for

a

connection

to

be

made

to

the

FTP

port

responds

with

an

opening

message

and

the

FTP

program

passes

the

Users

name

to

the

A60.

Since

the

A60

does

not

do

any

username

checking

the

user

then

specifies

the

filename

to

transfer

A

data

connection

is

opened

from

the

A60

end

to

the

port

chosen

by

the

FTP

program

on

the

users'

machine

and

the

data

is

transferred.

The

data

connection

is

closed

once

the

data

has

been

transferred,

the

control

connection

is

closed

when

the

user

issues

the

'quit'

command.

2.2

Layered

Model

The

ISO

standards

authority

has

proposed

an

Open

Systems

Interconnection

model

consisting

of

seven

layers.

The

reason

for

dividing

the

Protocols

into

layers

is

so

that

different

protocols

at

the

same

level

can

be

used

interchangeably

to

provide

the

same

function

for

the

layers

above.

RELIMINARY

f

~-1

Presentation

.\

Application

Session

I

1

Transport

i

t

Network

Data

Link

Physical

OSI

diagram

Layered

Model

A60

Ethernet

Manual

8

The

TCP/IP

family

of

protocols

can

be

applied

to

several

low

level

networks

architectures,

in

this

case

the

two

lower

levels

-

that

is

the

Physical

layer

which

defines

the

connectors

and

voltages,

and

the

Data

link

layer

which

defines

the

way

data

is

passed

between

two

pieces

of

equipment

on

the

same

local

network

are

both

defined

by

the

IEEE

802.3

standard

(which

in

turn

is

based

on

the

Xerox

Ethernet

V2).

Another

comparable

Network

standards

is

X.25

which

is

used

for

public

packet

switched

services.

Family

Tree

2.3

Physical

layer

Ethernet

was

developed

at

Xerox

PARC

and

is

based

on

the

concept

of

a

baseband

Carrier

Sense

Multiple

Access

with

Collision

Detection.

(CSMA-CD)

Transceivers

The

host

computer

will

be

coupled

onto

the

Ethernet

Coax

by

a

device

called

a

transceiver.

In

some

instances

(particularly

in

the

case

of

'Cheapernet')

the

transceiver

can

be

part

of

the

Ethernet

interface

board

in

the

host

computer.

The

Remote

pRELIMINARY

Transceivers

A60'Ethernet

Manual

9

transceivers

can

be

up

to

50m

away

from

the

computer

and

typically

come

with

a

plug

in

module

to

allow

either

a

spike

tap,

N-series

or

BNC

connectors

to

interface

to

the

cable.

Cheapernet

uses

thin

RG58

50-ohm

coax

and

BNC

style

connectors

rather

than

the

high

grade

10mm

thick

Yellow

coax

that

permits

the

non-intrustive

"vampire

tap"

transceivers

to

be

spiked

into

it

and

removed

without

having

to

take

the

network

down.

The

thick

coax

can

be

used

for

networks

up

100

nodes

on

500m

of

cable

whereas

Cheapernet

is

limited

to

30

nodes

on

185

m

of

cable.

Only

two

repeaters

are

allowed

on

a

local

network

because

of

the

propagation

delays

through

them.

The

transceivers

should

be

placed

at

multiples

of

2.5metres

on

the

cable.

The

following

is

an

non-exhaustive

list

of

Transceivers

currently

available.

Inmac

Transceivers:

part

number

8043

HP

part

number

30241A

LAN

802.3

MAU

(Medium

Attachment

Unit)

3com

Ethernet/IEEE

802.3

Transceivers:

3C107

Transceiver

with

AMP

piercing

tap

3C108

Transceiver

with

N

series

connectors

3C109

Tranceiver

with

BNC

connectors

DEC

Ethernet

bits:

DESTA

-

Thin

ethernet

transceiver

DELNI -

Ethernet

in

a

box

The

DELNI

has

eight

0-15

connectors

for

connecting

up

to

eight

ethernet

devices

without

using

transceivers

or

coaxial

cable.

It

also

has

a

ninth

connector

for

connecting

to

a

regular

transceiver

(and

thus

to

a

larger

net),

or

to

another

DELNI

(for

a

hierarchical

DELNI

network).

Different

Ethernet

Standards

There

are

three

different

Ethernet

standards

:

Ethernet

V1,

V2

and

the

Newer

IEEE

802.3

standard.

The

are

electrical

differences

between

the

different

standards

mainly

concerning

the

grounding

requirements

for

the

transceiver.

For

Ethernet

V1

and

V2

the

connector

shell,

cable

shield

and

PRELIMINARY

Different

Ethernet

Standards

A60

Eth~rnet

Manual

10

one

of

the

connector

are

all

connected

together

whereas

for

IEEE

802.3

the

cable

shield

is

separate

from

1

ground.

The

grounding

should

be

achieved

at

the

host

end

of

the

transceiver

cable.

outer

Shield

1 9

Collision

-

Collision

+ 2 • •

10

Transmit

-

Transmit

+ 3 • •

•

11

Ground

*Inner

Shield

•

4 • •

12

Receive

-

Receive

+ 5 • •

13

Power

+12v

Ground

6 • •

• •

14

Ground

*Vcc

7 •

15

No

Connect

Logic

8

Transceiver

(AUI)

cable

pinout

*

Notes

(Pin

4

Electrically

Isolated

from

Outer

shield

for

802.3)

(Pin

7

appears

to

be

a

no

connect

on

most

machines)

Male

connector

at

transceiver,

Female

at

main

chassis.

SQE

Some

transceivers

support

SQE

or

Signal

Quality

Error

(sometimes

called

heartbeat)

in

which

case

they

will

simUlate

a

collision

in

the

gap

at

the

end

of

every

transmission

from

the

host.

This

provides

a

way

of

assuring

that

the

collision

detection

circuitry

in

the

host

interface

is

functioning

correctly.

Ethernet

VI

does

not

provide

for

SQE.

IRELIMINARY

SQE

A60

Ethernet

Manual

11

2.4

Data

Link

Layer

The

Data

Link

layer

provides

for

source

and

destination

addresses

and

a

trailing

CRC

allows

the

integrity

of

the

whole

packet

to

be

checked.

Ethernet

and

IEEE

specifications

differ

in

a

few

minor

respects,

The

IEEE

spec

states

that

the

field

immediately

following

the

source

address

is

an

optional

length,

however

the

Ethernet

receiving

hardware

is

capable

of

determining

the

packet

length

by

other

means.

The

original

Xerox

Ethernet

spec

defines

this

as

a

type

field

which

is

used

to

resolve

the

above

in

the

hierarchy.

The

types

used

for

the

ARPA

family

of

protocols

are

intentionally

chosen

to

be

illegal

lengths

Ceg ,

larger

than

the

maximum

permissible)

so

as

to

remove

any

confusion

between

the

IEEE

and

Xerox

implementation

of

Ethernet.

Ethernet

Addresses

Ethernet

addresses

are

six

bytes

conventionally

written

as

six

hex

numbers

separated

by

colons.

Ethernet

addresses

are

intended

to

be

unique

for

any

piece

of

equipment

that

conforms

to

the

IEEE

802.3

standard.

For

instance

Abekas

Equipment

will

start

00:00:76:XX:XX:XX

Using

the

Ethernet

Broadcast

packet

mechanism

it

is

possible

for

the

local

host

to

send

a

packet

to

all

the

devices

on

the

local

network

rather

than

to

one

specific

address.

This

is

address

FF:FF:FF:FF:FF:FF.

2.5

Network

Layer

The

Network

Layer

provides

a

packet

delivery

system

between

two

hosts.

IP

The

Internet

Protocol

adds

to

a

packet

the

information

required

to

pass

it

from

one

host

to

another

across

different

networks.

The

intention

is

that

a

gateway

that

is

passing

the

packet

from

one

network

to

another

need

only

examine

the

IP

header

to

determine

the

routing

information.

~RELIMINARY

IP

A60

Ethernet

Manual

'

12

The

Internet

Protocol

also

provides

a

mechanism

for

breaking

packets

into

smaller

fragments

for

passing

them

over

a

network

with

restricted

packet

size.

Internet

Addresses

Internet

address

is

a

four

byte

number

conventionally

expressed

as

four

decimal

numbers

(0

••

255)

separated

by

dots.

eg

192.9.200.5

The

Internet

Address

can

be

subdivided

into

two

parts,

the

first

is

referred

to

as

the

Network

number

and

the

second

as

the

local

address.

All

the

machines

on

the

same

local

network

should

have

the

same

Network

Number

but

different

Local

Addresses.

If

a

host

is

asked

to

send

a

packet

to

a

remote

host

with

a

different

Network

number

it

will

assume

that

the

remote

host

is

on

a

different

network

and

attempt

to

find

a

gateway

to

it.

Network

Numbers

for

Internet

sites

are

assigned

by

the

ARPA

authorities

the

local

addresses

are

chosen

by

the

local

system

administrator.

There

are

many

Ethernet

networks

that

are

not

actually

part

of

the

Internet

and

only

use

a

default

Network

number.

There

are

three

classes

of

internet

address

based

on

the

Network

number.

For

a

class

A

address

the

first

byte

of

the

internet

address

will

be

less

than

128,

the

local

address

is

then

formed

by

the

lower

three

bytes

allowing

for

4096

separate

hosts

on

the

one

network.

A

class

B

address

will

have

a

first

byte

in

the

range

128

to

191

and

in

this

case

the

lower

two

bytes

form

the

local

address.

Class

C

addresses

the

first

byte

will

have

a

value

greater

than

191

only

the

last

byte

identifies

the

individual

machine

or

internet

node.

Internet

addresses

are

intended

to

be

more

wide

ranging

than

the

native

addressing

scheme

for

the

local

network,

it

is

possible

to

connect

to

an

Internet

host

across

several

different

types

of

network

eg

Local

Area

Ethernet,

long

haul

X.25

packet

switched

services

and

Local

area

Token

ring

networks.

fRELIMINARY

Internet

Addresses

A60

Ethernet

Manual

13

ICMP

Internet

Control

Message

Protocol

Is

almost

an

integral

part

of

IP,

it

is

intended

to

handle

error

reporting

from

Gateways

to

hosts

or

hosts

to

hosts.

It

gives

the

originating

host

more

information

about

the

reason

a

packet

has

been

rejected

or

cannot

be

delivered.

ICMP

also

provides

an

echo

system

used

by

'ping'

programs

to

help

isolate

inter-network

problems.

A

Selection

of

the

ICMP

Massages

:

GGP

Echo

Request

Echo

reply

Redirect

:

Use

alternative

route

Time

Exceeded

:

Packet

died

of

old

age

Parameter

problem

:

Something

wrong

with

the

IP

Header

Destination

Unreachable,

either:

Network

Host

Protocol

Port

Gateway

to

Gateway

Protocol

Handles

communication

between

Gateways

for

control

purposes.

Allows

them

to

exchange

routing

information

and

keep

up

to

date

on

the

availability

of

neighboring

Gateways.

ARP

The

Address

Resolution

Protocol

uses

the

Ethernet

Broadcast

Mechanism

to

allow

a

host

to

resolve

Internet

to

Ethernet

address

mappings

by

asking

all

the

hosts

on

the

local

network

if

any

of

them

claim

to

be

the

required

Internet

address.

If

the

hosts

support

ARP

they

will

decode

the

packet,

it

contains

both

the

Internet

and

Ethernet

Addresses

of

the

local

host

and

the

Internet

address

of

the

host

it

is

trying

to

reach.

Only

the

requested

host

or

a

Gateway

that

can

reach

it

on

another

network

reply

directly

to

the

requesting

machine.

.PRELIMINARY

ARP

A60

Ethernet

Manual

14

RARP

The

Reverse

Address

Resolution

Protocol

allows

an

Ethernet

host

to

determine

its

own

Internet

Address

by

broadcasting

a

request

to

the

net.

2.6

Transport

Layer

The

fourth

OSI

layer

is

the

Transport

Layer,

which

is

concered

with

creating

and

maintaining

logical

connections

between

individual

processes

on

different

hosts.

TCP

The

transport

layer

adds

a

source

and

destination

port

number

to

the

packet

addresses.

This

allows

the

packet

traffic

to

be

routed

to

several

different

processes

or

users

within

a

particular

machine.

A

TCP

connection

is

characterized

by

the

combination

of

local

and

remote

Internet

addresses

and

the

local

and

remote

port

numbers.

So

for

instance

several

people

may

be

logged

in

on

a

machine

though

the

port

assigned

to

the

rlogin

service.

If

two

of

~he

users

originate

from

the

same

machine

they

will

have

to

be

on

different

ports

on

their

local

machine.

The

TCP

software

can

then

uniquely

identify

which

connection

a

packet

belongs

to.

Some

of

the

lower

port

numbers

(normally

less

than

1024)

are

reserved

for

system

functions,

these

are

'well

known'

port

numbers

that

are

published

for

other

computers

wishing

to

use

a

particular

service.

Opening

connections

to

these

ports

is

normally

a

privileged

operating

system

function.

Commonly

used

TCP

port

numbers

FTP 21

Telnet

23

Rsh

514

Rlogin

513

The

TCP

packet

header

also

carries

Sequence

and

Acknowledge

numbers.

The

sequence

number

represents

the

position

of

the

first

rRE

LIMI

NARY

TCP

A60

Ethernet

Manual

15

byte

of

this

packet

in

the

transmitted

data

stream.

The

Acknowledge

represents

the

byte

after

the

last

fully

reassembled

byte

of

the

data

stream

received.

In

other

words

the

Receiving

TCP

can

buffer

several

packets

that

may

be

out

of

sequence

but

the

Acknowledge

number

will

only

increase

once

the

incoming

data

is

complete

up

to

that

byte

number.

Sequence

numbers

are

fixed

when

the

connection

is

opened,

packets

are

exchanged

with

the

SYN

flag

set

to

indicate

the

initial

sequence

number.

The

TCP

header

also

includes

a window

to

indicate

to

the

other

end

how much

buffer

space

is

currently

available.

This

acts

as

a

method

of

flow

control

since

the

transmitter

should

not

continue

if

more

than

a

windows'

worth

of

data

remains

unacknowledged.

The

transmitting

side

of

TCP

is

responsible

for

resending

a

data

if

it

is

not

acknowledged

within

a

timout

period.

There

is

a

TCP

option

that

allows

the

maximum

number

of

data

bytes

in

a

packet

to

be

specified,

the

default

is

512.

TCP

connections

can

be

opened

either

Actively

or

Passively.

In

the

~ctive

case

the

remote

port

and

host

address

are

fully

specified,

whereas

a

passive

open

will

only

specify

the

port

number

at

the

local

end

and

wait

for

an

incoming

attempt

to

connect.

On

closing

the

connection

it

is

necessary

for

both

sides

to

exchange

and

acknowledge

packets

with

the

FIN

flag

set.

pRELIMINARY

TCP

A60

Ethernet

Manual

16

1

Typical

Data

Packet

UDP

The

User

Datagram

Protocol

is

a

simple

extension

to

IP

that

adds

only

a

source

and

destination

port

number

and

a

checksum.

A

Datagram

is

a

standalone

packet

with

neither

guaranteed

delivery

nor

special

sequence.

TFTP

and

Sun

Microsystems'

RPC

and

NFS

are

among

the

protocols

built

on

top

of

UDP.

2.7

Upper

Levels

For

the

TCP/IP

protocols

the

top

three

as!

reference

layers

tend

to

be

merged

into

one

program

at

the

highest

Application

layer.

The

OSI

model

also

provides

for

a

Session

layer

which

handles

user

validation

and

mapping

host

names

to

network

addresses,

and

a

Presentation

Layer

which

handles

machine

differences

like

byte

swapping

and

terminal

standardization.

ik>RELIMINARY

Upper

Levels

A60

Ethernet

Manual

17

Telnet

is

a

remote

login

program

based

on

the

concept

of

a

virtual

Terminal.

The

virtual

Terminal

has

a

set

of

default

conditions

that

can

be

changed

by

'negotiation'

and

mutual

agreement

between

the

local

and

remote

host.

For

instance

echo

is

by

default

local

and

the

local

host

is

expected

to

buffer

lines

of

text

until

is

pressed.

The

Telnet

connection

has

an

escape

mechanism

where

hex

FF

is

the

escape

character,

FF

occurring

in

the

data

stream

is

transmitted

as

FF

FF.

The

escape

character

preceds

an

option

negotiation

which

contains

a

code

to

indicate

WILL,

WON'T,

DO

or

DON'T

and

the

particular

option

code.

Before

an

option

will

be

implemented

on

both

sides

both

sides

have

to

positively

agree

to

do

it.

The

escape

sequence

is

also

used

to

implement

'out

of

band'

signals

such

as

Abort

Output,

Interrupt

Process

and

Erase.

FTP

The

File

Transfer

Protocol

uses

a

Telnet

connection

for

User

authentication

and

control.

The

control

is

achieved

using

a

pommand

and

Response

Dialog

which

mayor

may

not

be

visible

to

the

user.

Commands

are

of

the

form

"USER

Simon"

and

"STOR

pic.rgb".

FTP

responses

are

preceded

by

a

three

digit

code

which

allows

a

machine

to

assess

the

required

action.

Some

of

the

meanings

are

listed

below

1xx

is

a

positive

preliminary

reply

2xx

is

a

positive

completion

reply

5xx

is

a

Permanent

negative

completion

reply

xOx

is

a

Syntax

error

x2x

refers

to

a

connection

x5x

refers

to

the

file

system

PRELIMINARY

FTP

A60

Ethernet

Manual

18

Simple

FTP

transfer

[

open

TCP

connection

to

port

21

on

the

A60 ]

<--

220

Abekas

A60 FTP

(a60)

-->

USER

simon\r\n

<--

230

User

OK

-->

PORT

192,9,200,1,30,244\r\n

<--

200

PORT

spec

accepted:

host

192.9.200.1

port

7924

-->

STOR

407.rgb\r\n

[

Active

open

from

A60

end

port

20

to

192.9.200.1

port

7924

]

<--

150

OK

here

goes

[

Data

Transferred

]

far

end

closes

data

connection

when

done

<--

226

File

Transfer

OK

-->

QUIT\r\n

<--

221

Closing

control

connection

TFTP

The

Trivial

File

Transfer

Protocol

is

built

on

top

of

UDP

and

provides

an

easy-to-implement

file

transfer.

Data

is

transferred

in

512

byte

blocks

each

data

packet

carrying

a

block

number.

Each

~lock

has

to

be

acknowledged

before

the

can

be

transmitted.

TFTP

is

used

for

booting

diskless

hosts

on

a

local

network

and

exchanging

mail.

rcp

As

is

the

case

with

most

Unix

applications

the

implementation

of

'r'copy

is

elegantly

minimal.

Most

of

the

handshaking

is

achieved

by

the

transmission

of

a

single

null

byte.

Most

of

the

Ire

commands

use

a

single

TCP

connection

although

there

is

provision

for

a

'standard

error'

connection

rcp

pic400.rgb

a60:312.rgb

-->

\0

(no

standard

error)

-->

simon\Osimon\O

(local

and

remote

username)

<--

\0

(user

info

validated)

-->

rcp

-t

312.rgb\0

(the

command)

<--

\0

(command

OK)

-->

C0666

1049760

pic400.rgb

(Access

flags,

length,

name)

?RE

LIMI

NARY

rcp

-->

\0

<--

\0

A60

Ethernet

Manual

-->

[1049760

bytes

of

data]

-->

\0

<--

\0

~RELIMINARY

19

rep

A60

Ethernet

Manual

20

3.

Installing

an

A60

on

a

Unix

Network

These

notes

apply

in

particular

to

Sun

Microsystems

Unix,

there

may

be

local

variations.

Installation

should

be

simply

matter

of

adding

the

Internet

address

chosen

for

the

A60

to

the

file

/etc/hosts

and

then

entering

this

address

on

the

A60

control

panel.

For

these

changes

to

the

host

machine

you

will

almost

certainly

require

superuser

privilege.

This

is

probably

the

point

to

contact

your

local

Unix

Guru.

/etc/hosts

In

the

following

notes

"ourhost"

and

"yphost"

are

fictitious

example

hostnames.

If

there

is

more

than

one

Sun

Workstation

connected

to

the

network

the

chances

are

that

the

network

service

called

the

Yellow

Pages

will

be

running.

The

Yellow

Pages

allow

all

the

machines

on

the

network

to

share

the

same

configuration

tables,

especially

things

like

host

names,

password

and

account

info~ation.

This

simplifies

the

task

of

maintaining

the

system

wide

databases

and

means

they

only

need

to

be

updated

in

one

place.

The

existence

of

the

Yellow

Pages

can

be

determined

by

typing

the

command

"ypwhich"

,

Unix

should

respond

with

the

name

of

the

yp

server.

ourhost%

ypwhich

:

ourhost

is

not

running

ypbind

Says

that

the

Yellow

Pages

are

not

running.

(ypbind

is

the

name

of

the

program

that

accesses

the

YP

service)

ourhost%

ypwhich

yphost

Says

the

Yellow

Pages

are

originating

form

the

host

called

'yphost'

PRELIMINARY

/etc/hosts

A60

Ethernet

Manual

21

When

the

yellow

pages

are

running

network

nodes

only

consult

their

own

tables

at

boot

time,

after

this

requests

for

system

configuration

such

as

hostnames

are

provided

by

the

yellow

pages

service.

The

new

hostname

need

only

be

entered

on

the

YP

server

machine

and

it

then

has

to

be

"pushed'

out

to

all

the

other

clients.

First

login

on

the

YP

server

machine

either

over

the

net

or

by

actually

walking

over

to

the

YP

server.

ourhost%

rlogin

yphost

root

Then

edit

the

/etc/hosts

file

(note

that

root

normally

has

a #

as

a

prompt)

yphost#

vi

/etc/hosts

Entries

in

the

hosts

file

have

the

following

format

:

Everything

to

the

right

of

ali'

is

ignored

as

a

comment.

Lines

consist

of

two

or

more

fields

separated

by

whitespace

(tabs

or

~paces).

The

first

field

on

a

line

is

the

internet

address

of

the

host,

following

normal

convention

it

is

expressed

as

four

decimal

numbers

separated

by

dots.

The

second

field

on

a

line

is

the

hostname.

Any

subsequent

names

on

the

line

are

aliases

for

the

same

machine

(normally

local

abbreviations

or

nicknames).

An

example

entry

would

be

:

192.9.200.5

a60

Now

we

have

to

update

the

dynamic

version

of

the

host

table

:

yphost#

cd

/etc/yp

yphost#

make

hosts

the

response

should

be

Updated

hosts

Pushed

hosts

PRELIMINARY

/etc/hosts

A60

Ethernet

Manual

22

setting

the

A60

Internet

Address

The

A60's

Internet

address

is

set

via

the

Miscellaneous

Menu

on

the

control

panel.

To

select

the

appropriate

menu

type

74<Menu>

Then

enter

the

address

in

two

halves

as

pairs

of

bytes

separated

by

a

dot.

eg

192.009<enter>

200.005<enter>

Note

that

leading

zeroes

have

to

be

included.

setting

the

A60

Hostname

The

default

A60

hostname

is

"a60"

which

is

fine

unless

you

have

more

than

one.

To make

life

easier

it

is

possible

to

change

the

hostname

on

the

A60

so

that

it

is

obvious

which

machine

has

been

logged

into.

Log

in

to

the

a60

using

Telnet

or

rlogin

and

issue

the

hostname

command

to

set

a new name.

ourhost%

rlogin

a60

Abekas

A60

Remote

Login

a60%

hostname

fred

fred%

AD

ourhost%

/etc/ethers

There

is

a

further

refinement

for

Sun

networks

that

allows

the

A60

to

ask

the

network

what

its'

Internet

address

is

by

way

of

the

Reverse

Address

Resolution

Protocol

(RARP).

This

requires

an

addition

to

the

file

/etc/ethers.

Note

that

this

step

will

not

usually

be

necessary

since

the

A60

stores

its

Internet

address

in

Non-Volatile

RAM.

It

only

uses

RARP

if

the

RAM

contents

are

lost,

or

the

Internet

Address

is

manually

set

from

the

control

panel

to

0.0.0.0

and

the

machine

is

restarted.

To

find

out

if

a

host

supports

RARP

try

the

following:

yphost#

ps

-ax

I

grep

rarp

e

it

should

show

you

all

the

processes

with

anything

to

do

with

RARP

apart

from

the

line

that

says

"grep

rarp"

(which

is

part

of

the

command

you

just

typed)

there

ought

to

be

a

mention

of

/usr/etc/rarpd

if

the

RARP

Daemon

(the

process

that

catches

RARP

requests)

is

running.

If

this

is

the

case

you

'RELIMINARY

/etc/ethers

A60

Ethernet

Manual

23

can

add

the

Ethernet

address

of

the

A60

to

the

/etc/ethers.

yphost#

vi

/etc/ethers

A

typical

entry

in

ethers

is

O:O:76:60:FF:FF

a60

Again

if

the

Yellow

Pages

is

running

you

have

to

force

it

to

update

its'

copy

of

the

'ethers'

file.

yphost#

cd/etc/yp

yphost#

make

ethers

If

the

Internet

address

on

the

A60

is

set

to

all

zeros

the

A60

will

attempt

try

to

find

its

address

from

the

network

when

it

is

rebooted.

If

you

watch

the

Internet

Address

Menu

it

should

show

the

correct

address

when

it

finds

it.

~RELIMINARY

/etc/ethers

A60

Ethernet

Manual

4.

Implementation

Notes

The

following

notes

list

the

specific

aspects

of

the

implementation

of

TCP/IP

on

the

A60.

Ethernet

Address

24

The

unique

Ethernet

Address

for

each

machine

is

set

in

Software

PROM

for

the

68000

(top

6

bytes

of

the

27256

at

location

7C

on

the

computer

card).

A60's

have

a

officially

allocated

Ethernet

address

range

00:00:76:60:XX:XX

the

last

two

bytes

being

determined

by

the

Computer

Card

Serial

Number.

The

Ethernet

address

of

a

particular

card

should

be

engraved

on

the

left

hand

side

at

the

front

of

the

card.

Note

that

if

the

Computer

card

is

swapped

the

Ethernet

Address

is

likely

to

be

different.

The

A60

is

compatible

with

IEEE

802.3

or

10

Mbit/s

Ethernet

V2

-

only

difference

is

the

transceiver

cable

grounding

arrangements.

The

A60

doesn't

care

if

the

transceivers

generate

SQE

-

it's

just

ignored.

Address

Resolution

The

A60

supports

both

the

Address

Resolution

Protocol

(ARP)

and

Reverse

ARP.

The

A60

will

attempt

to

use

RARP

in

the

event

that

the

machines'

Internet

address

is

set

to

0.0.0.0

and

the

a

power-on

reset

occurs.

This

will

either

be

the

result

of

a

really

cold

start

-

eg

the

Non

Volatile

RAM

in

the

machine

has

been

trashed

or

if

the

address

is

set

to

0.0.0.0

from

the

control

panel

and

the

Computer

Reset

button

is

pressed.

RARP

will

only

work

if

someone

out

there

is

serving

up

Ethernet/Internet

address

mappings

(such

as

the

rarpdaemon

on

a

Sun

which

refers

to

the

/etc/ethers

file)

PRELIMINARY

Address

Resolution

A60

Ethernet

Manual

25

If

there

is

no

reply

the

Internet

address

will

remain

at

zero.

IP

The

A60

IP

is

not

capable

of

reassembling

fragmented

packets.

The

A60

sends

ICMP

protocol

unreachable

for

services

it

doesn't

support

such

as

UDP.

Incoming

ICMP

information

is

not

recognized.

Ought

to

support

GGP

simple

echo

reply

but

it's

never

been

tested.

Don't

think

we

support

4.2

BSD/VAX

Trailer

Encapsulation

whatever

that

is.

If

the

Least

Significant

Byte

of

the

Internet

is

configured

as

zero

the

ethernet

drivers

will

use

the

broadcast

address.

I'm

not

sure

why

we

do

this

any

more.

TCP

The

A60 TCP

initial

sequence

number

is is

always

zero.

A60 TCP

does

not

check

security

or

precedence

level

of

packets.

Since

the

A60

is

not

really

a

shareable

resource

it

only

supports

one

connection

per

socket.

Any

subsequent

connection

attempts

will

meet

with

a TCP

reset.

There

appears

to

be

a

problem

with

BSD

socket

connections.

They

don't

seem

to

differentiate

between

different

types

of

ICMP

Destination

Unreachable

replies

If

an

attempt

is

made

to

connect

to

a

socket

that

is

already

in

use

we

used

to

reply

with

a

type

three

:

Port

unreachable

On a

sun

this

aborts

all

existing

connections

to

that

host.

On

the

HP

9000/300

it

just

shows

a

Network

Unreachable

error

message.

When a TCP

packet

is

not

acknowledged

the

A60

will

resend

the

packet

up

to

twenty

times

at

approx

1

sec

intervals

before

aborting

the

connection.

TCP

Seg

size

option

of

1024

is

written

out

and

the

A60

responds

RELIMINARY TCP

A60

Ethernet

Manual

26

appropriately

by

honoring

incoming

SEG

SIZE

option,

the

default

segment

size

is

512.

Telnet

None

of

the

Telnet

options

are

supported.

The

A60

will

just

respond

courteously

with

the

appropriate

negative

response

eg

WILL->DONT

WONT->DONT

DO->WONT

etc

Ought

to

issue

the

Telnet

option

"Suppress

go

ahead"

especially

since

we

don't

issue

Go

Aheads

!!

but

don't

as

yet.

A60

Telnet

will

accept

CR,

LF

or

CRLF

as

a

line

terminator.

The

HP

9000/300

workstation

has

problems

with

A60

Telnet

-

<CR>

doesn't

locally

echo

as

<CRLF>

use

<LF>

instead.

FTP

We

attempt

to

m1n1m1se

the

password

and

accounting

formalities

by

replying

with

a

User

OK

after

just

a

user

name.

Some

applications

at

the

other

end

still

insist

on

providing

a name

and

password

however

facilities

such

as

the

Unix

'.netrc'

file

can

smooth

the

FTP

login

sequence.

The

A60

isn't

a

real

computer

and

there

just

wasn't

space

to

keep

track

of

names

and

access

permissions.

Third

party

FTP

transfers

eg

controlled

from

somewhere

different

from

the

data

connection

have

never

been

tested.

When

using

FTP

most

applications

require

that

TYPE

IMAGE

is

specified

in

order

to

stop

the

local

host

expanding

carriage

Returns

into

Carriage

Return-Line

Feed

sequences.

Although

these

aren't

valid

CCIR

601

video

values

(so

they

shouldn't

appear

in

the

file)

it

still

takes

the

host

time

to

filter

the

data.

Hangs

up

at

the

moment

if

the

Remote

client

restarts

and

our

end

is

still

open.

Its

OK

if

we

restart

with

the

other

end

still

up

since

the

sent

from

the

other

end

will

most

likely

be

out

of

sequence

and

illicit

a

reset

from

our

end.

IPRELIMINARY

FTP

A60

Ethernet

Manual

27

rcp

A60

rcp

can't

cope

with

wildcard

transfers

eg

the

command

rcp

*.rgb

a60:

will

return

an

error

message

rlogin

can

be

terminated

by

D

or

C

In

rlogin

either

ASCII

back-space

or

delete

have

the

same

effect.

rcp

actually

uses

the

rsh

port

General

Segments

that

have

been

set

"record

lockout"

from

the

A60

control

Panel

appear

to

the

file

transfer

utilities

as

write

protected

files.

Remote

Control

through

the

Login

utilities

is

locked

out

while

a

file

transfer

is

in

progress.

When

the

A60 SCSI

Port

is

in

use

the

Ethernet

services

are

not

available

The

A60

is

still

liable

hang

up

if

the

remote

end

of

a

connection

goes

away

without

any

warning

-

it

keeps

the

connection

open

and

refuses

any

further

attempts

to

connect

to

that

port,

even

from

the

same

host.

At

the

moment

he

only

way

round

this

is

to

issue

a

reset

command

over

rsh,

rlogin

or

Telnet

(assuming

they

are

not

all

hung

at

once).

The

reset

command

will

clear

out

all

existing

connections.

Filenames

(or

frame

numbers)

can

have

all

sorts

of

directory

junk

on

them

-

the

parser

works

back

from

the

far

end

of

the

name -

eg

optional

extension,

plus

for

second

field,

frame

number,

f

for

field.

i>RELIMINARY

General

A60

Ethernet

Manual

28

4.1

Copyright

Notice

The

following

notice

has

to

be

included

because

Abekas

TCP/IP

is

based

on

a

Public

Domain

program

called

PC/IP

originally

written

by

John

Romkey

and

others

at

MIT.

Copyright

1984,1985

Massachusetts

Institute

of

Technology

Permission

to

use,

copy,

modify,

and

distribute

this

program

for

any

purpose

and

without

fee

is

hereby

granted,

provided

that

this

copyright

and

permission

notice

appear

on

all

copies

and

supporting

documentation,

the

name

of

M.I.T.

not

be

used

in

advertising

or

pUblicity

pertaining

to

distribution

of

the

program

without

specific

prior

permission,

and

notice

be

given

in

supporting

documentation

that

copying

and

distribution

is

by

permission

of

M.I.T.

makes

no

representations

about

the

suitability

of

this

software

for

any

purpose.

It

is

provided

"as

is"

without

express

or

implied

warranty.

PRELIMINARY

Copyright

Notice

A60

Ethernet

Manual

29

5.

File

Transfer

5.1

RGB

Conversion

The

A60

has

the

capability

to

convert

raw

RGB

files

to

YUV

and

back

again.

The

arithmetic

is

done

32

bit

fixed

point

using

the

on

board

Multiplier

Accumulator

Chip.

Reciprocal

Anti

Aliasing

and

Interpolation

filters

are

used

to

minimise

generation

loss.

Some

slight

degradation

will

be

visible

on

the

first

pass

into

and

out

of

the

machine.

Once

the

image

has

been

bandwidth

limited

to

YUV

space

it

does

not

degrade

further

on

successive

passes.

The

conversion

process

does

slow

up

the

transfer

of

data

however.

On

a

lightly

loaded

Ethernet

with

a

host

that

supports

1024

byte

TCP

packets

a

525

line

YUV

image

should

take

about

5

seconds

to

transfer

in

either

direction.

RGB

images

take

approximately

20

seconds

to

transfer

to

the

A60

and

33

seconds

to

read

from

the

A60.

video

data

in

the

files

transferred

to

and

from

the

A60

as

raw

RGB

or

YUV

data

with

no

compression,

Run

Length

Coding

or

other

~tructure.

Refer

to

the

A60/A64

Digital

Video

Interface

Manual

for

more

information

on

the

format

of

the

data

and

the

size

of

the

frame

buffer.

Note

that

the

A60

does

not

check

the

length

of

the

file

transferred

but

files

longer

than

a

frame

in

length

can

cause

the

Frame

buffer

addressing

to

wrap

round

and

cause

unpredictable

effects.

5.2

File

Names

on

the

A60

The

A60

expects

a

filename

to

contain

the

frame

number

and

an

optional

extension

.yuv

and

.rgb

are

currently

supported,

yuv

is

the

default.

The

frame

number

can

either

be

given

as

an

absolute

frame

number

(in

decimal)

or

a

time

code.

The

A60

starts

at

the

end

of

the

filename

and

works

back

so

you

can

include

all

the

directory

paths

you

want

they

are

all

get

ignored.

PRELIMINARY

File

Names

on

the

A60

Ethernet

Manual

30

rcp

thing400

a60:/users/simon/piccys/thing400.yuv

parses

OK

as

400.yuv

Be

careful

that

filenames

donlt

have

an

If

I

immediately

before

the

frame

number

since

this

is

interpreted

as

being

a

field

transfer.

Fields

and

Frames

video

can

be

transferred

as

Frames

or

Fields,

A

frame

is

twice

as

long

as

a

field

and

the

lines

are

interleaved

in

the

same

way

~s

they

appear

on

the

display.

A

field

transfer

is

indicated

by

an

IF'

immediately

preceding

the

frame

number.

The

first

field

of

a

frame

will

be

implied

by

default.

To

access

to

the

second

field

the

frame

number

must

have

a

,+,

after

it

or

alternatively

if

the

frame

number

is

specified

in

timecode

the

seconds

and

frames

should

be

separated

by

colons

rather

than

dots.

write

Protection

The

A60

has

the

ability

to

Write

Protect

or

Record

Lockout

segments

of

the

Disk,

an

attempt

to

transfer

to

a

Record-Locked-

out

section

will

result

in

an

appropriate

"Write

Protected"

error

message.

There

is

no

way

to

change

the

Record

Lockout

form

the

Ethernet

remote

software.

I

PRELIMINARY

write

Protection

A60

Ethernet

Manual

31

5.3

FTP

The

following

is

the

example

of

an

FTP

transfer

files

to

and

from

the

A60

host%

ftp

a60

Connected

to

a60.

220

Abekas

A60

FTP

(a60)

230

User

OK

ftp>

type

image

200

TYPE

OK

ftp>

send

piccy

25

200

PORT

spec

accepted:

host

192.9.200.6

port

1061

150

OK

here

goes

226

File

Transfer

OK

699840

bytes

sent

in

4.92

seconds

(1.4e+02

Kbytes/s)

ftp>

send

sym/symb576.rgb

25.rgb

200

PORT

spec

accepted:

host

192.9.200.6

port

1062

150

OK

here

goes

226

File

Transfer

OK

1244160

bytes

sent

in

29.40

seconds

(41

Kbytes/s)

ftp>

quit

221

Closing

control

connection

PRELIMINARY

FTP

A60

Ethernet

Manual

5.4

rcp

host%

rcp

piccy

a60:23

host%

rcp

sym/symb576.rgb

a60:rgb

rcp:

RGB

Not

a

valid

frame

number

host%

rcp

sym/symb576.rgb

a60:24.rgb

host%

rcp

a60:24.rgb

zzz

Note

that

rcp

from

A60

to

'.'

(eg

the

same

name

in

the

current

dir)

is

supported

host%

rcp

a60:24.rgb

•

host%

Is

*.rgb

024.rgb

32

The

A60

will

generate

a

file

in

the

form

[F]

001

[+]

.yuv

however

the

reverse

case

is

not

supported,

the

A60

insists

on

having

the

filename

specified

explicitly.

host%

rcp

symb576.rgb

a60:

rcp:

•

Not

a

valid

frame

number

IBY

the

same

token

directory

copies

or

wildcards

aren't

accepted

host%

rcp

*.rgb

a60:

rcp:

A60

only

supports

single

file

transfers

5.5

Unix

Script

Hints

Here

are

some

suggestions

for

ways

to

use

Unix

Command

Files

to

shuffle

files

onto

or

off

the

A60.

They

all

run

under

the

'C'shell.

~RELIMINARY

Unix

Script

Hints

A60'Ethernet

Manual

33

#

copy

dir

SMe

siggraph

87

#

copies

all

the

frames

with

same

root

name

eg

'pic'

in

pic001.yuv

#

takes

3

params

:

copydir

rootname

host

baseframe

#

note

that

frame

numbers

in

filenames

should

have

leading

zeros

# -

or

Is

screws

up

the

ordering

set

frame=$3

set

list='ls

$1*'

foreach

i

($list)

rcp

$i

$2:$frame

set

frame='expr

$frame

'+'

l'

end

IPRELIMINARY

Unix

Script

Hints

A60

Ethernet

Manual

34

#

copy

tape

SMC

9-SEP-87

#

unloads

frames

that

have

been

tar-ed

onto

Quarter

Inch

tape

#

each

file

was

named

tmp.yuv

and

saved

to

the

tape

using

#

one

call

to

tar

per

frame

(dd

wouldn't

stream

properly)

#

device

names

are

for

a

Sun

SCSI

Archive

tape

#

takes

at

least

2

args

:

copy

tape

hostname

base

frame

#

optional

third

arg

for

number

of

files

to

transfer

#

optional

fourth

arg

for

number

of

files

skip

before

transfer

#

transfers

25

frames

from

tape

to

A60

if

(

($1

==

'''')

I I ( $ 2 == .... »

then

echo

"Usage:

copy

tape

hostname

startframe

[count

[skip]]"

exit

endif

set

frame=$2

if($3

== .... )

then

set

count=25

else

set

count=$3

endif

if($4

!=

.... )

then

echo

"skipping

$4

files"

mt

-f

/dev/nrstO

fsf

$4

endif

while($count

> 0)

tar

-xvf

/dev/nrstO

mt

-f

/dev/nrsto

fsf

rcp

tmp.yuv

$1:$frame

set

frame='expr

$frame

'+'

l'

set

count='expr

$count

'-'

l'

end

echo

rewinding

tape

mt

-f

/dev/nrstO

rewind

Unix

Script

Hints

A60

Ethernet

Manual

35

6.

A60

Remote

Control

over

Ethernet

The

following

notes

outline

the

commands

available

over

the

A60's

TCP/IP

Ethernet

connection.

It

assumes

some

knowledge

of

the

operation

of

the

A60.

Refer

to

the

A60

Operators

Manual

for

more

information

on

how

the

machine

can

be

divided

into

segments

and

the

limits

on

play

speed

etc.

remote

commands

can

be

invoked

in

three

ways

Telnet,

Rsh

and

Rlogin.

The

following

examples

assume

the

commands

are

given

on

a

UNIX

machine

with

the

prompt

"host%

"

The

A60

has

several

operating

modes

particularly

Segment,

Normal

play

and

Loop Mode,

most

of

the

commands

given

here

will

work

with

the

machine

in

any

state

however

they

can

leave

the

machine

in

a

different

state.

6.1

Telnet

From

Sun

Unix

type

host%

telnet

a60

Abekas

A60

Remote

Login

a60>

play

a60>

quit

6.2

rsh/rlogin

rsh

allows

a

single

command

to

be

executed

on

the

remote

machine

for

instance

host%

rsh

a60

play

-0.5

PRELIMINARY

rsh/rlogin

A60

Ethernet

Manual

36

Both

Rsh

and

Rlogin

offer

an

interactive

login,

either

or

host%

rsh

a60

host%

rlogin

a60

Abekas

A60

Remote

Login

a60%

play

a60%

quit

the

login

can

also

be

terminated

by

AD

or

AC

Note

that

it

is

also

possible

to

redirect

a

file

to

the

remote

shell

(even

though

this

is

not

legal

Unix

Syntax)

Note

that

to

achieve

the

same

effect

between

two

Unix

machines

you

actually

have

to

type

"rsh

rhost

csh

<

script"

host%

cat

script

clearseg

defseg

100

200

defseg

300

400

·loopseg

1 2

host%

rsh

a60

<

script

This

provides

an

easy

way

to

keep

track

of

the

segment

list

from

the

host

computer

since

it

is

not

possible

to

read

back

the

segment

list.

Feedback

is

limited

to

the

'where'

command

but

this

should

be

enough

to

indicate

that

the

A60

has

reached

the

end

of

a

segment

with

a

pause

in

it.

PRELIMINARY

rsh/rlogin

A60

Ethernet

Manual

host%

cat

script

clearseg

defseg

100

200

P

defseg

300

400

P

loopseg

1 2

host%

rsh

a60

<

script

host%

rlogin

a60

a60% w

165

a60% w

174

a60% w

190

a60% w

199

a60% w

199

a60%

plays

a60% w

307

37

Note

that

out

point

for

a

segment

is

not

inclusive

eg

defseg

100

200

plays

frames

100

to

199.

6.3

Command

Notes

Upper

or

lower

case

allowed

Shorter

forms

of

commands

given

here

can

be

given

Parameters

separated

by

spaces

Only

one

command

per

line

Note

that

segments

are

numberd

from

one

Be

warned

that

in

the

case

of

ambiguity

the

earlier

command

in

this

list

is

executed.

6.4

Parameters

speed

[-][0-9].[0-9]

limits

+/-

30

for

525

line

systems

(25

for

625)

resolves

three

decimal

places

eg

-1

1.5

0.5

.5

-30

7.125

are

all

legal

speeds

PRELIMINARY

Parameters

A60

Ethernet

Manual

38

frame

[f][+-][O-99][.:][O-99][+-]

accepts

absolute

frame

numbers

with

trailing

1+1

to

indicate

the

second

field

or

timecode

with

I.'

or

1:1

for

field

1

or

2

field

mode

or

auto

frame

is

not

changed

eg

1

3:01

1.00.24

f231+

are

all

valid

seg

[1-100]

segments

can

be

numbered

from

1 -

100

The

segment

number

follows

the

order

in

which

the

segments

were

defined.

source

-

any

of

the

following

is

permissible

as

a

record

source,

it

should

only

be

necessary

to

type

the

initial

letter

of

each.

option.

bars

pattern

input

-

aux

<frame>

<pattern

num>

Digital

Video

in

#1

Digital

Video

in

#2

- a

frame

number

pattern_num

from

0 100%

Bars,

95%

Bars,

75%

Bars,

Lin

Ramp, Mod

Ramp,

10

step,

X

Hatch,

2T

pulse,

Pluge,

Multiburst,

Bow

Tie,

Digital

test,

100% Combo,

95%

Combo,

75%

Combo

display_mode

-

field

or

frame

-

typed

in

full

6.5

Commands

play

[speed]

defaults

to

1.0

play

from

the

current

position

stop

loop

or

play

goto

[frame]

defaults

to

0

goto

the

given

field

or

frame

jog

[offset]

defaults

to

+1

relative

goto,

field

or

frame

offset

is

determined

by

the

current

display

mode

loop

<in>

<out>

[speed]

PRELIMINARY Commands

A60

Ethernet

Manual~

39

loop

play

the

specified

segment

defseg

<in>

<out>

[speed]

[pause]

define

the

from

in

to

out

with

optional

speed

defaults

to

1.0

pause

can

be

typed

in

full

or

just

'pi

defaults

to

1

goseg

[seg]

goto

the

'in'

point

of

the

given

segment

playseg

[speed]

play

thru

the

segment

list

from

the

current

position

or

alternatively

resume

playing

after

a

pause

loopseg

<in>

<out>

[speed]

loop

play

the

specified

segments

clearseg

clear

the

segment

list

macro

<macro

number>

execute

the

given

macro

quit

close

down

the

connection

hostname

set

the

hostname

returned

in

the

prompts

(default

'a60')

makes

it

easier

to

use

two

machines

where

returns

the

current

frame

record

<in>

[<out>]

record

from

various

sources

pattern,

input

or

specific

<frame>

pattern

[pattern

num]

draws

the

given

pattern

into

the

store

mode

<display_mode>

PRELIMINARY

Commands

A60

Ethernet

Manual

40

7.

Troubleshooting

Some

of

these

things

are

probably

covered

in

the

user

manual

but

if

like

me

you

read

manuals

when

it

appears

to

be

broken

this

might

save

you

some

reading.

Debug

Port

The

A60

Computer

Card

has

a

RS232

serial

port

running

at

9600

baud.

It

only

sends

data

it

does

not

receive

it.

The

connection

is

through

the

5

pins

on

the

right-hand

end

of

the

card

The

right

most

is

1

which

is

the

transmit

data

from

the

A60

and

the

center

pin,

3

is

ground.

2

would

be

receive

if

it

did

anything.

Debug

Mask

A60

RS232

025

1

-->

3

2

<--

2

3 7

The

hex

weightings

of

the

bits

in

the

debug

mask

are

as

follows:

800

TCP

window

info

400

Telnet

200

IP

100

TCP

80

Application

eg

FTP

or

rsh

40

Timeouts

20

Ethernet

10

Protocol

Errors

8

Network

Errors

4

Info

messages

2

Dump

packets

(when

IP

debug

is

on

as

well)

1

Bughalt

Debug

level

can

be

set

through

any

of

the

login

connections

by

using

the

debug

command

with

a

hex

argument.

Debug

Mask

A60

Ethernet

Manual

41

Alternatively

the

debug

level

can

be

set

from

the

control

panel

(menu

73)

o

Debug

off

1

Errors

and

TCP

2

Errors

TCP

and

Window

3

Everything

except

Dump

4

Errors

and

Application

5

Errors

Telnet/Sockets

and

Application

6

Errors

Telnet/Sockets

Application

and

TCP

default

Errors

and

TCP

(llC)

(9IC)

(1FC)

(09C)

(49C)

(59C)

(1IC)

Note

that

with

debug

on

the

machine

will

run

slower

especially

with

the

lower

levels

of

debug

where

it

has

to

print

several

lines

per

packet.

The

buffering

for

the

debug

port

is

fairly

crude

so

if

there

are

large

amounts

of

debug

information

being

transmitted

the

buffer

can

wrap

round

and

information

can

become

garbled.

High

Level

Debug

If

the

Telnet/Socket

debug

bit

(400)

is

set

the

following

messages

will

be

generated

*****

"\00"

*****

"simon\OOdebug

80\OA"

Lines

starting

with

five

stars

show

what

arrives

on

a

packet

by

packet

basis.

The

text

is

enclosed

in

double

quotes

and

any

non

printing

characters

appear

as

backslash

and

two

hex

digits.

***

Open

***

RSH

EXIT

TELNET

recv

opt:

DO

SUPPRESS-GO-AHEAD

If

the

Application

debug

bit

(80)

is

set

the

following

messages

will

Lines

starting

with

three

stars

show

significant

events

such

as

opening

and

closing

connections.

RSH

EXEC

GOT

FNAME

RSH

EXEC

play

PRELIMINARY

High

Level

Debug

A60

Ethernet

Manual

42

TELNET

EXEC

goseg

TCP

Debug

Port

Numbers

20

FTP

Data

21

FTP Command

23

Telnet

513

rlogin

514

rsh

and

rcp

These

are

the

'well

known'

port

numbers

used

for

TCP

1022

send

[4]

102.9.200.3

1021

(tcb

4)

Seq

33741057

Ack

1

Win

4096

SYN

ACK

Intitially

TCP

debug

describes

each

packet

by

the

local

port

number

and

the

foreign

Internet

Address

and

port.

Once

Established

the

TCP

connection

is

only

referenced

by

tcb

(tcp

control

block)

number.

TCP

(4)

send

[0]

Seq

1

Ack

33741058

Win

450

PSH

ACK

IP

Debug

ipdemux

got

pkt[120]

prot

6

from

192.9.200.1

On

the

input

side

IP

prints

a

message

per

packet

with

the

length

and

the

protocol

number.

Relevant

protocol

numbers

are

as

follows:

TCP 6

ICMP 1

GGP

3

inwrite

pkt[25]

prot

6

to

192.9.200.1

route

192.9.200.1

Ethernet

Debug

ET SEND:

p[45]

->

192.9.200.1

ET_DEMUX:

got

pkt[60]

buf(O)

type

IP

ET

free

buf(O)

PRELIMINARY

Ethernet

Debug

IP

0800

ARP

0806

RARP

8035

A60

Ethernet

Manual

ET_DEMUX:

got

pkt[60]

type

ARP

ET

SEND

->

02:60:8C:29:79:10

"

43

Some

packets

will

be

discarded

-

ARP

request

that

are

not

intended

for

this

machine.

7.1

Where

to

Start

Ethernet

cable

Is

the

machine

correctly

connected

to

the

ethernet

cable

1"

Assuming

Ethernet

activity

can

be

generated

from

another

host

eg

attempt

to

'ping'

the

A60

repeatedly.

There

is

an

LED

on

the

computer

card

(second

from

left)

that

shows

Ethernet

receives.

(Some

Transceivers

also

have

transmit,

receive

and

collision

LEDs

which

are

of

great

assistance

at

this

stage.)

Receive

LEDs

permanently

'on'

on

both

the

Transceiver

and

the

Computer

Card

-

Transceiver

not

connected

to

cable.

Collisions

with

every

receive

-

cable

incorrectly

terminated.

Receive

at

transceiver

but

not

at

Computer

-

Problems

with

the

Transceiver

cable.

Internet

Address

Is

the

Internet

Address

set

up

correctly

1

Assuming

you

have

access

to

a

'ping'

program

and

that

the

Internet

address

has

been

entered

on

the

Control

panel.

The

Internet

address

should

have

the

same

network

address

as

the

rset

of

the

hosts

on

the

same

local

net.

The

network

address

is

PRELIMINARY

Internet

Address

A60

Ethernet

Manual

4'4

the

top

byte

of

the

internet

address

if

the

top

byte

is

less

than

128,

the

top

two

bytes

if

the

top

byte

is

greater

or

equal

to

128

and

less

than

192

or

the

top

three

bytes

if

the

top

byte

is

greater

or

equal

to

192.

If

the

Network

part

of

the

address

is

not

the

same

the

remote

host

will

think

the

A60

is

on

a

different

network.

Most

pings

will

have

to

start

by

using

ARP

to

find

the

Ethernet

Address

of

the

A60.

If

Ping

fails

more

than

about

1

percent

of

the

time,

unless

the

network

is

unusually

heavily

loaded

this

sounds

like

a

grounding

problem.

68000

Is

the

Motorola

68000

that

controls

the

A60

Ethernet

Hardware

running?

If

the

68000

has

hung

the

A60

will

be

unable

to

write

test

patterns

into

the

store

but

the

disk

transport

functions

may

appear

to

work

OK. -

Press

the

Reset

switch

on

the

Computer

card

at

the

right

hand

side

near

the

front.

Disks

Are

the

disks

up?

If

communications

appear

to

be

OK

but

the

A60

won't

record

or

play,

the

disks

might

be

spun

down,

there

is

a

toggle

switch

on

the

front

of

the

Computer

card

which

should

be

to

the

right

for

normal

operation.

Z80

Has

one

of

the

Z80s

crashed

?

If

the

HLC

or

LLC

goes

down

the

A60

will

not

respond

to

commands

from

the

control

panel.

The

status

display

may

be

showing

an

illegal

timecode.

If

the

Reset

button

fails

to

correct

this

condition

try

clearing

the

Non-Volatile

RAM

by

changing

the

position

of

the

first

DIP

switch

at

18k

on

the

computer

card.

rRELIMINARY

Z80

A60

Ethernet

Manual

45"'

Reference

Syncs

Is

the

external

reference

selected?

If

the

disks

are

up

but

churning

their

innards

out

trying

to

lock

to

a

non

existent

reference

sync

you

could

extend

their

life

somewhat

by

switching

the

Internal/External

Sync

select

to

the

right.

RGB

Transfers

If

YUV

data

can

be

transferred

OK

but

RGB

comes

out

green.

Is

the

file

extension

being

specified

correctly?

-

There

may

be

problems

with

the

MAC

chip.

PRELIMINARY

RGB

Transfers

A60

Ethernet

Manual

46

8.

Example

Program

The

following

is

a

simple

SunView

application

intended

to

demonstrate

use

of

the

Berkeley

Socket

interface

and

remote

control

of

the

A60

over

Ethernet.

It

consists

of

three

files,

demo.c

the

Ethernet

interface

to

the

A60,

panel.c

a

simple

Suntools

panel,

and

a60.icon

an

icon

used

by

the

program.

Since

the

origination

of

an

rlogin

is

a

privileged

operation

the

program

has

to

be

owned

by

root

and

have

the

set

user

ID

on

execution

bit

set.

The

following

sequence

of

commands

should

produce

an

executable

program.

%

cc

demo.c

panel.c

-lsuntool

-lsunwindow

-lpixrect

-0

demo

%

su

#

/etc/chown

root

demo

# chmod

4755

demo

Although

the

program

starts

up

with

the

window

open

you

have

to

close

it

and

then

reopen

it

before

it

actually

establishes

a

connection

to

the

A60.

There

can

only

be

one

connection

(to

A60

rlogin)

open

at

a

time

so

if

the

window

refuses

to

open

someone

else

must

be

logged

on

to

the

A60.

Something

probably

ought

to

be

done

about

throwing

away

data

from

the

A60,

at

the

moment

this

is

just

being

buffered

up,

but

at

least

there

is

no

echo

unless

the

rlogin

was

opened

up

with

the

string

"\Osimon\Osimon\Osun/9600\O".

Rlogin

turns

off

echo

if

the

terminal

speed

param

is

omitted.

PRELIMINARY

Example

Program

A60

Ethernet

Manual

8.1

demo.c

/*

demo.c

-

quick

lash

up

to

show

remote

control

of

A60

* -

from

within

a

Suntools

app

-

using

TCP/IP

*

Copyright

(c)

1987

Abekas

Video

Systems

Inc.

*

Based

on

an

example

proggys

47

*

in

the

IPC

Primer

in

"Networking

on

the

Sun

Workstation"

*/

#include

<stdio.h>

#include

<netdb.h>

#include

<errno.h>

#include

#include

#include

char

login

str[]

=

"\Osimon\Osimon\Osun\O":

char

play

fwd

str[]

=

"play\n";

char

play-back

str[]

=

"play

-l\n";

char

stop=str[]

=

"stop\n";

int

sd;

/*

global

socket

descriptor

*/

open_connection()

{

struct

sockaddr

in

skt;

struct

servent

*rlogin

service;

struct

hostent

*a60;

-

int

lport;

char

c,

tmp_str[80],

str[80];

if«rlogin_service

=

getservbyname("login",

"tcp"»

==

NULL)

{

fprintf(stderr,

"demo:

tcp:

unknown

service\n"):

exit(l);

}

if«a60

=

gethostbyname("a60"»

==

NULL)

{

fprintf(stderr,

"demo

:

a60

:

unknown

host\n")j

exit(l)j

}

bzero«char

*)&skt,

sizeof(skt»;

bcopy(a60->h

addr,

(char

*)&skt.sin

addr,

a60->h_length)j

skt.sin_addr~s

addr

= INADDR_ANY: -

PRELIMINARY

demo.c

A60

Ethernet

Manual

if«sd

=

socket(AF_INET,

SOCK_STREAM,

0»

<

0)

(

perror("demo:

socket");

exit(3);

}

/*

attempt

bind

to

a

privileged

socket

*/

lport

= IPPORT

RESERVED

-1;

for

( ; ; )

(

skt.sin

port

=

htons«u

short)lport);

if

(bind(sd,

(caddr_t)&skt,

sizeof(skt»

>=

0)

break;

if(errno

!=

EADDRINUSE

&&

errno

!=

EADDRNOTAVAIL)

(

perror("socket");

break;

}

Iport--;

if(lport

==

IPPORT_RESERVED/2)

{

}

fprintf(stderr,

"socket:

All

ports

in

use\n");

break;

}

bzero«char

*)&skt,

sizeof(skt»;

bcopy(a60->h

addr,

(char

*)&skt.sin

addr,

a60->h

length);

skt.sin

family

=

a60->h

addrtype;

-

skt.sin-port

=

rlogin

service->s

port;

if«connect(sd,

(char-*)&skt,

sizeof(skt»)

<

0)

{

perror("demo:

connect");

exit(3);

}

printf("OK

so

far\n");

write

(sd,

login_str,

sizeof(login

str»;

}

close_connection()

{

close(sd);

48

PRELIMINARY

demo.c

}

play_forwards()

{

A60

Ethernet

Manual

write

(sd,

play_fwd_str,

strlen(play_fwd_str»;

}

play_backwards()

{

write

(sd,

play_back_str,

strlen(play_back_str»;

}

stope)

{

write

(sd,

stop_str,

strlen(stop_str»;

}

PRELIMINARY

49

demo.c

A60

Ethernet

Manual

8.2

panel.c

/*

panel.c

-

quick

lash

up

to

show

remote

control

of

A60

* -

from

within

a

Suntools

app

-

using

TCP/IP

*

see

sunview

programmers

guide

for

examples

*

copyright

(c)

1987

Abekas

Video

Systems

Inc.

*/

#include

#include

#include

#include

<stdio.h>

#include

<math.h>

static

short

icon

image[]

= {

#include

"a60.icon"

} ;

Frame

frame;

Canvas

canvas;

Panel

a60

panel;

Panel_item

play_fwd_button,

stop_button,

play_back_button;

Pixwin

*pw;

Pixfont

*font,

*bold;

static

Notify_value

catch_closes();

/*

calls

five

routines

from

demo.c

50

*

these

first

three

are

called

when

the

appropriate

button

is

pressed

*/

extern

void

play

backwards();

extern

void

stope);

extern

void

play_forwards();

/*

also

calls

open

connection

and

close

connection

as

the

window

*

is

opened

and

closed

*/

maine)

{

/*

open

fonts

*/

font

=

pf

open

("/usr/lib/fonts/fixedwidthfonts/screen.r.12");

bold

=

pf=open

("/usr/lib/fonts/fixedwidthfonts/screen.b.12");

PRELIMINARY

panel.c

A60

Ethernet

Manual

51

1*

create

frame

*1

frame

=

window

create(NULL,

FRAME,

-

FRAME

LABEL,

"demo

-A60

panel",

FRAME-ICON, &a60

icon,

0);

- -

a60_panel

=

window

create(frame,

PANEL,

-

0);

stop_button

=

panel

create

item(a60

panel,

PANEL BUTTON,

PANEL_NOTIFY_PROC,

play_backwards,

PANEL

LABEL

IMAGE,

panel_button_image(a60_panel,

"«",

0)

;

=

panel

create

item(a60

panel,

PANEL BUTTON,

4,

bold),

-PANEL_NOTIFY_PROC,

stop,-

PANEL

LABEL IMAGE,

panel_button_image(a60_panel,

"STOP",

6,

bold

0)

;

play_fwd_button

=

panel_create_item(a60~anel,

PANEL_BUTTON,

PANE

L_NOTI FY_PROC,

play_forwards,

PANEL

LABEL

IMAGE,

window

fit(a60

panel);

window=fit(frame);

0)

;

panel_button_image(a60_panel,

"»"

,

4,

bold),

notify_interpose_event_func(frame,

catch_closes,

NOTIFY_SAFE);

window_main_loop(frame);

)

1*

this

routine

intercepts

events

and

catches

open

and

closes

*1

static

Notify

value

catch_closes(frame,

event,

arg,

type)

Frame

frame;

-

Event

*event;

Notify

arg

arg;

Notify=event_type

type;

{

PRELIMINARY

panel.c

A60

Ethernet

Manual

int

was

closed,

now

closed;

Notify_value

value;-

was_closed

=

(int)

window_get

(frame,

FRAME_CLOSED);

value

=

notify_next_event_func(frame,

event,

arg,

type);

now_closed

=

(int)

window_get

(frame,

FRAME_CLOSED);

if(was

closed

1= now

closed)

if(now_closed)

close_connection();

else

open

connection();

return(value);

}

52

PRELIMINARY

panel.c

A60

Ethernet

Manual

53

8.3

a60.icon

/*

Format_version=l,

Width=64,

Height=64,

Depth=l,

Valid_bits~er_item=16

*/

OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOo,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOo,OxOOOo,OxOOO0,

OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

Ox07FF,OxFFFF,OxFFFF,OxFFCO,Ox0622,Ox2222,Ox2222,Ox2240,

Ox0444,Ox4444,Ox4444,Ox4440,Ox05FF,OxF911,Oxll15,Ox3140,

Ox04FF,OxF888,Ox888A,OxD8CO,Ox06FF,OxFA22,Ox223E,OxB240,

Ox0444,Ox445F,OxFFC5,Ox7440,Ox0511,OxlllF,OxFF90,Ox1140,

Ox0488,Ox889F,OxFF88,Ox88CO,Ox06E3,OxBF3F,OxFFA2,Ox2240,

Ox04E7,OxDF5F,OxFFC7,OxE440,Ox05F3,Ox9FIF,OxFF97,OxF140,

Ox04EB,Ox9F9F,OxFF8F,OxF8CO,Ox06E3,OxBF3F,OxFFBF,OxFE40,

Ox04E7,OxDF5F,OxFFDF,OxFC40,Ox05F3,Ox9FIF,OxFF9F,OxFD40,

Ox04EB,Ox9F9F,OxFF9F,OxFCCO,Ox06E3,OxBF3F,OxFFBF,OxFE40,

Ox04FF,OxDF5F,OxFFCF,OxFC40,Ox05FF,Ox9FIF,OxFF97,OxF140,

Ox04FF,Ox9F9F,OxFF8B,OxE8CO,Ox0622,Ox2222,Ox2222,Ox2240,

Ox0444,Ox4444,Ox4444,Ox4440,Ox0511,Oxllll,Oxlll1,Oxl140,

OX07FF,OxFFFF,OxFFFF,OxFFCO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOO,OxOOOO,OxOOOO,OxOOOo,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOo,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OXOOOO,OxOOOO,OxOOOo,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOo,OxOOOO,OxOOO0,

OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOO,Ox0083,Ox8700,OxOOOO,OxOOOO,Ox0084,Ox4880,OxOOO0,

OxOOOO,Ox0144,Ox0880,OxOOOO,OxOOOO,Ox0144,Ox0980,OxOOO0,

OxOOOO,Ox0147,Ox8A80,OxOOOO,OxOOOO,Ox0224,Ox4C80,OxOOO0,

OXOOOO,Ox03E4,Ox4880,OxOOOO,OxOOOO,Ox0224,Ox4880,OxOOO0,

OxOOOO,Ox0223,Ox8700,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OxOOOO,OxOOOo,OxOOOo,OxOOOo,OxOOOo,OxOOOo,OxOOoo,Oxooo0,

OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0,

OXOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOOO,OxOOO0

PRELIMINARY

a60.icon

A60

Ethernet

Manual

54

9.

Glossary

~P

Address

Resolution

Protocol

-

used

to

obtain

Internet

to

Ethernet

address

mappings

rather

than

configure

and

maintain

a

list

on

each

host.

~PA

AUI

Advance

Research

Projects

Agency,

US

Government

agency

responsible

for

developing

TCP/IP

family

of

protocols.

Attachment

unit

Interface

-

the

long

way

of

saying

transceiver

cable.

Normally

limited

to

50

meters

and

carries

twisted

pair

differential

signals

for

transmit,

receive

and

collision

detection.

The

AUI

cable

also

carries

12v

power

for

the

Transceiver.

Bridge

Bridges

are

generally

connections

between

Networks

of

the

same

type

at

the

Data

Link

Layer.

Broadcast

Packet

an

Ethernet

packet

carrying

the

address

FF:FF:FF:FF:FF:FF

which

will

be

recieved

by

all

the

hosts

on

the

network.

Cheapernet

an

alternative

form

of

ethernet

that

uses

thin

RG58

50-Ohm

cable

with

BNC

connectors

and

'T'

pieces

at

the

tranceivers

rather

than

the

normal

normally

used

for

Ethernet.

This

cable

suffers

from

greater

loss

and

the the

cable

run

is

typically

limited

to

185

m.

In

all

other

respects

it

is

electrically

compatible

with

'Normal'

Ethernet.

Client

The

consuming

(user)

end

of

a

client-server

relationship.

connection

CRC

the

link

between

two

specific

ports

on

two

Internet

Hosts

analogous

to

a

telephone

call

being

set

up

between

two

phones

on

a

network.

Cyclic

Redundancy

Check

- a

sort

of

serial

check

sum

that

PRELIMINARY

Glossary

A60

Ethernet

Manual

55

assures

the

integrity

of

a

serial

data

stream

by

using

some

sort

of

polynomial

feedback

-

basically

a

shift

register

and

a

few

exclusive

or

gates.

CSMA-CD

Collision

Sense

Multiple

Access

with

Collision

Detection

-

Describes

the

mechanism

that

allows

several

devices

to

share

the

single

Ethernet

cable.

Domain Names

A name

addressing

scheme

that

uses

a

hierarchy

of

domain

names

to

describe

the

address

of

a

remote

computer

in

a

similar

way

to

the

way

as

a

mailing

address

eg

simon@master.abekas.COM.uucp

Ethernet

Vi

and

V2

The

original

Ethernet

standard

was

developed

by

Xerox

and

published

jointly

with

DEC

and

Intel.

Ethernet

Address

A 48

bit

address

conventionally

written

as

6

hex

bytes

separated

by

colons

The

IEEE

hopes

that

there

are

enough

addresses

for

every

piece

of

ethernet

equipment

in

the

universe

to

have

its

own

unique

address,

typically

vendors

ship

equipment

with

the

Ethernet

address

contained

in

a

small

bipolar

ROM.

Fragments

FTP

Sub

divisions

of

Internet

packets

-some

times

necessary

if

a

different

networks

have

different

maximum

packet

lengths.

File

Transfer

Protocol

4:2:2

The

Ratio

of

the

sampling

frequencies

for

components

in

Digital

Video.

Four

Luminance

samples

for

two

each

of

the

color

difference

signals.

Gateway

Gateways

allow

interconnection

of

different

Networks

at

the

Network

layer.

IEEE

802.3

The

IEEE

standard

for

CSMAjCD

Networks,

forms

part

of

the

802.x

family

of

standards

for

Local

Area

Network

Interfaces

and

Protocols.

Internet

Address

PRELIMINARY

Glossary

A60

Ethernet

Manual

56

A

Four

byte

number

representing

the

address

of

a

host

on

the

"Internet".

Jabber

A

condition

detected

by

a

Tranceiver

to

prevent

locking

up

the

net

-

if

the

output

is

active

for

more

than

1/10

second

the

Transceiver

should

latch

up

and

prevent

further

transmissions

until

the

Transmit

signal

is

inactive

for

at

least

1/4

second.

Heartbeat

See

SQE

Host

A

computer

that

is

a

node

on

a

network.

Hostname

MAU

NFS

NIC

The

name

by

which

a

particular

machine

is

known

at

the

user

interface

level

-

normally

associated

with

a

Network

address.

Medium

Attachment

unit

The

official

IEEE name

for

what

mortals

refer

to

as

a

Transceiver.

Network

File

System

(Developed

by

Sun

Microsystems)

Network

Information

center

-

The

central

repository

for

all

information

regarding

the

development

of

the

ARPAnet

OSI

Layered

Model

Ping

The

much

vaunted

abstract

model

for

the

seven

layer

hierarchy

of

network

protocols

issued

by

ISO

the

International

standards

body.

still

under

development

at

the

higher

layers.

Program

that

uses

the

ICMP

Echo

Request

facility

to

verify

the

connections

between

two

machines.

Note

that

this

only

checks

correct

operation

of

IP

or

up

to

the

Network

layer.

Port

Number

An

addressing

scheme

within

a

host

computer

that

allows

more

than

one

simUltaneous

connection

to

that

computer.

Repeaters

PRELIMINARY

Glossary

RFC

A60

Ethernet

Manual

57

Repeaters

connect

buffer

two

sections

of

the

same

Network

with

very

little

intelligent

signal

processing.

Request

For

Comment -

the

main

instrument

of

the

ARPA

community

a

sort

of

Network

Memo.

Often

quoted

in

references

e.g.

RFC

793

is

the

latest

description

of

TCP.

Available

from

the

Network

Information

center

(see

NIC

above).

Server

SQE

A

host

or

node

on

the

network

that

provides

a

service,

eg

a

File

Server

provides

a

File

system

for

Diskless

nodes.

signal

Quality

Error

-some

Ethernet

Transceivers

generate

a

collision

signal

immediately

after

each

transmission.

This

permits

the

Ethernet

Interface

to

verify

that

its

collision

detection

circuitry

is

functioning

correctly.

Socket

a

socket

is

an

abstraction

in

BSD

unix

for

the

interprocess

communications

primitive

the

known

as

the

pipe.

A

socket

can

be

opened

in

much

the

same

way

as

a

file

would

be

opened.

Telnet

ARPA

remote

terminal/login

program.

TFTP

Trivial

File

Transfer

Protocol

-

built

on

UDP

-

simple

to

implement.

lOBASE5

and

lOBASE2

IEEE

names

for

Ethernet

and

Cheapernet

respectively

Thin-LAN

or

Thin-net

see

Cheapernet

Transceivers

the

box

that

attaches

the

Host

computers

Ethernet

Interface

the

best

ones

use

a

spike

arrangement

to

non-intrusively

attach

to

the

cable

(eg

without

cutting

it).

Couples

the

Transmit

signal

from

the

ethernet

signal

onto

the

cable

through

an

isolating

transformer,

detects

collisions,

and

passes

the

received

Ethernet

signal

up

to

the

interface.

PRELIMINARY

Glossary

, A60

Ethernet

Manual

58

UNIX

is

a

Trademark

of

(AT&T)

Bell

Laboratories!

two

main

flavors

X.25

YW

BSD

4.2

and

ATT

system

V

the

Berkeley

Software

Distribution

(BSD)

version

is

the

one

that

supports

the

ARPA

protocols

most

popular

Unix

Systems

eg

Sun

Microsystems,

HP-UX

and

DEC

Ultrix

are

a

mixture

of

the

two

Public

Wide

Area

Packet

Switched

Network

Standard.

the

Native

data

format

of

the

A60,

an

alternative

encoding

·to

RGB

for

component

video

and

one

that

is

more

suited

to

the

limited

bandwidth

of

Broadcast

TV.

The

Y

channel

is

luminance

and

the

U

and

V

are

color

difference

components

B-Y

and

R-Y

respectively.

The

color

difference

signals

are

normally

stored

at

half

the

sampling

frequency

of

the

Luminance.

PRELIMINARY

Glossary

~

A60

Ethernet

Manual

59

10.

Appendix

This

information

is

provided

for

those

who

intend

to

write

their

own

applications

to

'manually'

access

the

file

transfer

and

remote

control

services

on

the

A60.

10.1

Complete

TCP/IP

Packet

The

following

is

a

complete

dump

of

a

packet.

Physical

I

Link

Network

I

Transport

I

AA

AB

00 00

76

60

FF

08

00

20

01

FF

90

08

00

45

00

35

FE

70

00 00

OF

06

90

2B

CO

09

C8

01

CO

09

C8

05

21

83

00

17

18

4A

OE

DB

00 00

00

3B

50

18

10

00

AA

CF

00

Ethernet

Preamble

and

sync

Destination

Addr

Source

Addr

Type

Version,

Header

len,

Type

of

Serv

Length

10,

Fragment

stuff

Time

to

live,

Protocol

Header

Checksum

Source

Address

Destination

Address

Source

Port

Destination

Port

Sequence

Acknowledge

Flags

Window

Checksum

Urgent

Pointer

68

65

6C 6C

6F

20

77

6F

72

6C

64

00

OA

Data

2A 2B

49

80

Ethernet

CRC

IpRELIMINARY

Complete

TCP/IP

Packet

A60

Ethernet

Manual

60

10.2

FTP

Implementation

The

following

notes

are

intended

to

show

the

various

states

and

messages

of

the

Abekas

FTP

server.

Defaults

As

suggested

in

the

ARPA

FTP

Paper

these

are

the

defaults

assumed

by

A60

FTP.

ftp->fport

=

ftp->lport

=

ftp->passive

=

ftp->type

=

ftp->format

=

ftp->byte_size

=

ftp->mode

=

ftp->structure

=

opening

Message

20;

FALSE;

ASCII;

NON_PRINT;

8;

STREAM;

FILE;

220

Abekas

A60 FTP

(Hostname)

220

Abekas

A60 FTP

Commands

and

Responses

The

following

are

a

list

of

all

the

commands

supported

and

the

possible

responses.

Some

of

the

responses

are

as

the

result

of

internal

events

such

as

ABORT

where

the

data

connection

was

closed

mid-transfer.

USER

name

>

20

500

Username

too

long

230

User

OK

QUIT

221

Closing

control

connection

PASV

227

Entering

Passive

Mode.

iii,iii,iii,iii,ppp,ppp

PORT

error

501

Host/Port

spec

not

enough

commas

200

PORT

spec

accepted:

host

iii.

iii. iii.

iii

port

nnn

TYPE

error

501

TYPE

:

bad

args

ASCII

NON

PRINT

200

TYPE

OK

NON

PRINT TELNET

CC

504

can't

cope

with

that

TYPE

IMAGE

200

TYPE

OK

PRELIMINARY Commands

and

Responses

MODE

EBCDIC

LOCAL

error

STREAM

BLOCK

COMPRESSED

error

FILE

RECORD

PAGE

argc

1= 2

name

parse

data

conn

150

OK

here

UNO

PEN

ABORT

LRESET

FRESET

NORMAL

A60

Ethernet

Manual

504

can't

cope

with

that

TYPE

501

MODE

:

bad

arg

200

MODE

OK

504

can't

cope

with

that

MODE

STRU

501

STRU

:

bad

arg

200

STRU

OK

504

can't

cope

with

that

STRU

RETR

501

arg

count

550

Bad

File

name

125

Data

Connection

already

open

goes

425

Can't

open

Data

Connection

426

Connection

Closed

Transfer

Aborted

426

Connection

Closed

Local

Reset

426

Connection

Closed

Foreign

Reset

226

File

Transfer

OK

STOR

NOOP

name

parse

550

Bad

File

name

data

conn

125

Data

Connection

already

open

150

OK

here

goes

UNO

PEN

ABORT

LRESET

FRESET

NORMAL

425

Can't

open

Data

Connection

426

Connection

Closed

Transfer

Aborted

426

Connection

Closed

Local

Reset

426

Connection

Closed

Foreign

Reset

226

File

Transfer

OK

200

NOOP

OK

else

202

Command

not

implemented

61

PRELIMINARY Commands

and

Responses

A60

Ethernet

Manual

62

10.3

File

Names

The

A60

is

not

case

sensitive

The

correct

syntax

for

a

'filename'

on

the

A60

is

as

follows:

optional

leading

slash

or

directory

path

(ignored)

'F'

to

indicate

a

field

transfer

(optional)

timecode

19.20

frame

at

19

seconds

20

frames

or

19:20

second

field

or

590

frame

590

or

590+

frame

590

second

field

extension

.RGB

or

.YUV

(optional

-

defaults

to

YUV)

10.4

rlogin

Implementation

-->

\0

-->

simon\Osimon\O

-->

vt100/9600\0

<--

\0

<--

Abekas

A60

Remote

<--

a60%

(no

standard

error

connection)

(local

and

foreign

username)

(term/speed)

(user

info

validated)

Login\n

User

input

is

echoed

character

for

character

Both

backspace

and

delete

characters

do

the

same

thing

eg

-->

\b

(backspace)

<--

\b

(backspace

space

backspace)

The

Sun

appears

to

leave

out

the

/9600

bit

when

the

connection

doesn't

expect

echo

eg

when

invoked

by

"rlogin

host

<

script"

Venix

running

on

a PC,

sent

\n\n

instead

of

vt100/9600

10.5

rsh

Implementation

-->

1022\0

-->

simon\Osimon\O

<--

\0

-->

play

-l\r

possible

responses

(open

standard

error

to

port

1022)

(local

and

foreign

username,

or

vice

versa)

(user

info

validated)

(the

command)

(even

if

stderr

open

-

still

sent

down

stdout)

<--

\OOlrsh:

framestore

access

locked

<--

\OOlXXX:

command

not

found

PRELIMINARY

rsh

Implementation

A60

Ethernet

Manual

63

10.6

rcp

Implementation

pic312.yuv

a60:312

(no

standard

error)

Copy

to

A60

eg

rcp

-->

\0

-->

simon\Osimon\o

<--

\0

(local

and

foreign

username,

or

vice

versa)

(user

info

validated)

-->

rcp

-t

400\0

<--

\0

(the

command)

(command

OK)

-->

~666

829440

pic400.yuv\n

(File

info

access

flags,

length,

name)

-->

\0

<--

-->

[829440

bytes

of

data]

-->

\0

<--

\0

Copy

from

A60

eg

rcp

a60:400.rgb

pic400.rgb

-->

\0

(no

standard

error)

-->

simon\Osimon\O

(local

and

foreign

username,

or

vice

versa)

<--

\0

(user

info

validated)

-->

rcp

-f

400.rgb\0

(the

command)

-->

\0

<--

C0666A400.rgb\n

-->

\0.

<--

(

bytes

of

data)

~ri>

possible

responses

<--

\OOlrsh:

framestore

access

locked

<--

\OOlrcp:

arg

count

<--

\OOlrcp:

A60

only

supports

single

file

transfers

<--

\OOlrcp:

nnn

Not

a

valid

frame

number

<--

\OOlrcp

server:

expected

flag

<--

\OOlrcp:

nnn

:

Permission

denied

<--

\OOlrcp:

invalid

flag

~RELIMINARY

rcp

Implementation

A60

Ethernet

Manual

11.

Bibliography

from

Abekas

A64

External

Control

Protocol

Manual

Abekas

A60

External

Control

Protocol

Manual

Abekas

A60/64

Digital

Video

Interface

Manual

ARPA

publications

DDN

Network

Information

Center

SRI

International,

Room

EJ291

333

Ravenswood

Avenue

Menlo

Park,

CA

94025

DDN

Protocol

Implementations

and

Vendors

Guide

-

useful

compendium

of

different

TCP/IP

applications

revised

bi-annually

DDN

Protocol

Handbook

(Three

Volumes)

Particular

RFC's

of

interest:

RFC

826

Address

Resolution

Protocol

David

Plummer

Symbolics

Nov

82

RFC

903

Reverse

Address

Resolution

Protocol

June

84

Finlayson,

Mann,

Mogul,

Theimer

Stanford

University

RFC

791

DARPA

Internet

Protocol

Sept

81

J

Postel

(Editor)

RFC

792

DARPA

Internet

Control

Message

Protocol

sept

81

J

Postel

(Editor)

RFC

793

DARPA

Transmission

Control

Protocol

J

Postel

(Editor)

RFC

854

TELNET

Protocol

Specification

May

83

Postel

and

Reynolds

RFC

959

File

Transfer

Protocol

Oct

85

Postel

and

Reynolds

64

PRELIMINARY

Bibliography

A60

Ethernet

Manual'

IEEE

802.3

LAN

Standards

CSMA/CD

Access

Method

and

Physical

spec'ifications

Oct

84

IEEE

Ethernet

specs

:

A

LAN

Data

Link

Layer

and

Physical

Layer

Specification

version

2 Nov 82

DEC,

Intel,

Xerox

Other

Background

Reading

Byte

Magazine

July

87

Scientific

American

october

87 P

136

Networks

for

Advanced

Computing

Robert

E Kahn

Handbook

of

Computer

Communication

Standards

Vol

3

Department

of

Defense

(DOD)

Protocol

Standards

William

Stallings,

Macmillian

87

65

PRELIMINARY

Bibliography

A60

Ethernet

Manual

66

TCP/IP

Implementations

The

following

machines

are

known

to

support

TCP/IP,

in

some

cases

it

will

depend

on

the

operating

system.

Digital

Equipment

Corp.

VAX

and

microVAX

running

ULTRIX

or

BSD

Unix

Hewlett

Packard

HP

9000

300

and

800

running

HP-UX

Sun

Microsystems

Apollo

Computer

Symbolics

Apple

Computer

Macintosh

II

with

Ethertalk

For

the

remainder

there

are

add

ons

available

from

the

following

vendors

(Information

based

on

entries

in

the

DDN

Protocol

Implementations

and

Vendors

Guide)

Excelan

2180

Fortune

Drive

San

Jose,

CA

95131

(408)

434-2300

Intelligent

Ethernet

Controllers

for

VAX,

MicroVAX

and

IBM-PC.

TCP/IP

software

support

for

RSX-11,

VMS,

Unix

System

V

and

MS-DOS

Wollongong

1129

San

Antonio

Road

Palo

Alto,

CA

94303

(415)

962-7200

TCP/IP

software

for

HP

9000

series

500,

VAX,

IBM-PC

3com

Corporation

1365

Shorebird

Way

PO

Box

7390

Mountain

View,

CA

94039

(415)

961-9602

PRELIMINARY

Bibliography

A60

Ethernet

Manual

Ethernet

Interfaces

for

the

IBM-PC

FTP

Software

PO

Box

150

Kendall

Square

Branch

Boston,

MA

02142

(617)

864-1711

TCP/IP

software

for

the

IBM-PC

PRELIMINARY

67

Bibliography

Abekas_A60_Digital_Disk_Recorder_Ethernet_Preliminary_Manual_Dec87 Abekas A60 Digital Disk Recorder Ethernet Preliminary Manual Dec87

Abekas_A60_Digital_Disk_Recorder_Ethernet_Preliminary_Manual_Dec87 manual pdf -FilePursuit

Abekas_A60_Digital_Disk_Recorder_Ethernet_Preliminary_Manual_Dec87 Abekas_A60_Digital_Disk_Recorder_Ethernet_Preliminary_Manual_Dec87

Navigation menu

Versions of this User Manual:

Views

Navigation