HP 82713A User manual
HEWLEIT-PACKARD
HP82713A
Plug-In Module
Simulator
OWNER'S MANUAL
For
Use
With
the HP-75
•
•
l
.
i
• Printed in U.S.A.
Fli;;'
HEWLETT
~I:..
PACKARD
HP82713A
Plug-In
Module
Simulator
Owner's
Manual
For
Use
With
the
HP-75
September
1982
82713-90001
© Hewlett-Packard Company
1982
Autostart
Card
Instructions
A
magnetic
card
labeled
AUTOSTART,
which
contains
a
included
in
the
software
accompanying
your
HP
Simulator.
AUTOSTART
gives
you
the
capability
of
including
in
program
that
your HP-75
will
execute
as
soon
as
it
be
particularly
useful
to
you
if
your
plug-in
module
dedicated
system.
special
82713A
LEX
file,
is
Plug-In
Module
your
plug-in
module a
is
turned
on.
This
will
will
be
used
for
a
Just
follow
these
three
simple
steps
in
order
to
make
use
of
the
AUTOSTART
capability
in
a
plug-in
module you
are
developing:
1.
Read
the
LEX
file
from
the
AUTOSTART
card
into
your
HP-75
(COPY
CARD
TO
'AUTOSTRT').
2.
Specify
AUTOSTRT
as
the
lexname
in
the
BUILD
operation
of
your
PMS.
3.
Write
the
BASIC
program you
wish
to
be
executed
automatically
at
turn-on,
and copy
it
into
your
PMS
under
the
name
of
AUTOST
(not
AUTOSTRT).
And
that's
all
HP-75. With
the
HP-75 on
automatically.
there
the
by
is
to
it.
You
may
now
purge
one
or
both
files
from
your
autostart
plug-in
module
files
present,
any
time
you
turn
pressing
[ATTN]
it
will
execute
the
AUTOST
program
You
should
be aware
of
the
following
limitations
on your
use
of
AUTOSTART:
o
You
will
not
be
able
to
use
another
LEX
file
in
the
same bank
of
your
plug-in
module.
o
AUTOSTRT
executes
a
DEF
KEY
for
character
159
and
uses
it
to
run
the
AUTOST
program
when
the
HP-75
is
turned
on.
If
you
subsequently
redefine
character
159
to
some
other
operation,
that
operation
will
be
executed
instead
of
your
AUTOST
program.
For example,
DEF
KEY
CHR$(159),'HELLO';
will
cause
HELLO
to
be
displayed
in
your
HP-75
at
turn-on,
and
your
AUTOST
program
will
not
run.
82713-90007
rliPfJ
HEWLETT
':1::..
PACKARD
1000 N.E.
Circle
Blvd.,
Corvallis,
OR
97330
c
Hewlett-Packard
Company
1982
Printed
in
U.S.A.
10/82
•
•
Introduction
Your
HP
82713A
Plug-In
Module
to
help
you
prepare
your
plug-in
modules
in
support
of
Simulator
(PMS)
was
designed
by
Hewlett-Packard
program
materials
for
incorporation
into
custom
your
HP-75
portable
computer.
The
ROM
(read-only
memory)
of
a
plug-in
module
is
simulated
by
bytes
of
RAM
(random-access
memory).
Data
can
easily
be
written
from
the
RAM,
just
as
it
is
in
the
HP-75
itself.
Circuitry
is
retains
the
memory
after
power
has
been removed from
the
unit.
8K
or
16K
into
or
read
used
which
The
PMS
incorporates
the
flexibility
of
RAM
and
the
memory
characteristics
of
ROM
in
a
single,
easy-to-use
package.
With
the
simulator
you
can
accomplish
the
following:
o
Since
computer
memory
is
not
required,
you
can
conduct
realistic
performance
tests
of
your
programs.
o
You
can
field
test
your
programs.
o
You
can
verify
absolutely
the
function
and
fit
of
your
software
within
the
plug-in
module.
o
You
can
compare
the
performance
of
a
program
in
the
plug-in
module
to
the
performance
of
the
same
program
in
the
computer.
o
You
can
temporarily
store
files
and
programs.
If
you
are
concerned
updating,
the
PMS
will
you
are
an
accountant;
software.
Just
read
plug-in
module.
Doing
permanent
module.
with
"semifixed"
programs
that
require
periodic
be
particularly
useful
to
you.
Suppose,
for
example,
each
year
you
need
to
use
the
latest
tax
table
in
your
the
current
data
into
your
simulator,
and
use
it
as
a
this
saves
you
the
cost
and
time
required
to
obtain
a
You
need
to
have
an
HP-75
portable
computer
and
to
understand
the
HP-75
keyboard
and programming
techniques
in
order
to
operate
the
PMS.
5
Only two
pieces
of
equipment
and
the
associated
software
are
needed
to
operate
your
PMSj
the
simulator
itself
(which
includes
a
built-in
cable
and
connector),
an HP-75
portable
computer,
and
the
system
commands
recorded
on
magnetic
cards.
After
you
have
studied
your
HP-75
computer
specific
commands
that
will
understand
how
maintain
it.
And
you
cover
the
PMS
and
how
6
this
manual you
will
know
how
to
connect
the
PMS
to
and
how
to
turn
it
on and
off.
You
will
know
the
enable
you
to
write
programs
into
the
simulator.
You
the
continuous
memory works and what you
must
do
to
will
know
the
warranty
and
repair
prov~s~ons
which
to
make
use
of
them
should
the
need
arise.
•
'.
GETTING
STARTED
Operation
CAUTION
Be
sure
to
turn
the
HP-75
off
before
plugging
anything
into
an
external
port.
Failure
to
do
so
may
damage
the
computer
or
the
plug-in
unit.
To
assemble
a
simulator
system,
end
of
the
cable
into
any
edge
of
your HP-75.
you need
only
to
plug
the
connector
on
the
one
of
the
three
external
ports
on
the
front
The
HP
82713A
Plug-In
Module
Simulator
System
Up
to
three
simulators
may
be
plugged
into
the
external
ports
at
the
same
time.
If
only
one
or
two
simulators
are
used,
they
may
be
plugged
into
any
of
the
ports
in
any
order.
7
PMS
ADDRESSES
A
PMS
consists
of
two
banks
of
RAM,
each
of
which
contains
8K
bytes
of
memory. Each bank
can
be
accessed
independently.
A
permanent
plug-in
module
can
contain
up
to
two
full
PMS
banks.
The
address
of
a
particular
PMS
bank
depends
upon
the
port
into
which
the
PMS
is
plugged.
The
ports
are
searched
in
sequence
from
left
to
right.
The
two banks
of
the
first
PMS
found
will
be
designated
as
ROMA
and
ROMB.
--
I I
ROMA
ROMC
ROME
ROMB
ROMD
ROMF
))
))
))
PORT
1
PORT
2
PORT
3
Addresses
Using
Three
PMS's
I I
ROMA
ROMB
))
PORT
3
Addresses
Using
One
PMS
HOW
TO
TURN
THE
PMS
ON
AND
OFF
Operating
power
for
the
PMS
is
obtained
from
the
HP-75.
Therefore,
to
the
simulator
on and
off
you need
only
to
turn
the
HP-75 on and
off.
to
removing
the
PMS
(or
a
permanent
plug-in
module),
execute
the
CLEAR
command
to
insure
that
the
HP-75
will
not
expect
the
plug-in
unit
present
when
it
is
turned
on
again.
8
turn
Prior
VARS
to
be
I
•
..
•
CONTINUOUS
MEMORY
Programs
that
you
write
and
record
in
the
PMS
remain
there
until
you
purpose-
ly
remove them.
The
continuous
memory
of
the
PMS
saves
the
programs,
even
after
operating
power
is
removed.
The
battery,
which
provides
the
continuous
memory,
is
wired
into
the
PMS.
Although
it
is
not
rechargeable,
it
should
give
you
several
years
of
carefree
use.
Note:
The
PMS
simulates
a
ROM
and
will
retain
its
memory
for
long
periods
of
time.
It
should
be
remembered,
however,
that
the
contents
of
the
PMS
will
be
lost
before
you
receive
the
first
warning
that
the
battery
is
no
longer
maintaining
the
memory.
It
is
advisable
to
back
up
your
programs
frequently
on a
secondary
storage
medium,
such
as
a
mag
card,
or
in
the
HP-75
itself
•
If
you
turn
on
the
PMS
and an
error
232--INVALID
ately
appears
in
the
HP-75
display,
the
battery
is
and
should
be
replaced.
(Refer
to
appendix
B.)
All
in
the
PMS
is
lost.
CHECKSUM
message
immedi-
not
maintaining
the
memory
material
previously
stored
PERMANENT
PLUG-IN
MODULES
Hewlett-Packard
will
convert
the
programs
you
have
developed
and
stored
in
your
PMS
into
permanent
plug-in
modules,
should
you so
desire.
A
ROM
ID
number must be
provided
at
initialization
of
a
PMS
bank
to
identify
the
unit.
(Refer
to
the
BUILD
command, page
12.)
If
you
intend
to
have
your
programs
converted
into
permanent
plug-in
modules,
you
should
first
contact
Hewlett-Packard
and
obtain
permanent
ID
numbers
for
your
exclusive
use.
GENERAL
OPERATING
PROCEDURE
The
simple
operating
procedure
for
the
PMS
is
outlined
below.
The commands
are
described
in
detail
later.
(Throughout
the
rest
of
this
manual,
the
word
"program"
will
be
used
in
the
singular.
It
should
be
understood,
however,
that
multiple
programs
may
be
used
so
long
as
they
do
not
exceed
available
space
limitations.)
9
To
operate
the
PMS:
1.
Load
the
PMS
commands
into
your HP-75.
Do
this
by
reading
the
magnetic
cards
supplied
with
the
PMS.
This
needs
to
be done
only
once
so
long
as
the
HP-75
memory
is
maintained.
2.
Turn
the
HP-75
off,
plug
the
PMS
into
a
port
in
the
HP-75 ,
then
turn
the
HP-75
on
again.
3.
Execute
BUILD
to
initialize
the
desired
memory
bank and
to
set
the
ROM
ID.
4.
Write,
or
copy,
your program
into
the
HP-75.
*
5.
Execute
ROMSIZE
to
determine
the
size
of
the
program
in
the
HP-75 you
wish
to
copy
into
the
PMS.
*
6.
Execute
ROMAVAIL
to
determine
the
availability
of
sufficient
room
in
the
PMS
for
your program.
7.
Execute
COpy
to
read
your program
into
the
PMS.
Note:
It
is
possible
to
assign
the
same
name
to
your program
in
the
PMS
as
that
of
the
same program
in
the
HP-75.
If
you
do
so,
and you
run
the
program,
the
HP-75
will
run
the
program
in
its
own
memory
and
will
ignore
the
program
in
the
PMS.
8.
To
edit
your
program,
read
it
back
into
the
HP-75
using
the
COPY
com-
mand,
make
your
changes,
and
return
it
to
the
PMS.
9. Repeat
the
above
steps,
as
required,
until
you have
loaded
a
maximum
of
eight
programs and
files
plus
one
LEX
file
into
your
PMS
bank.
*10.
Mark
files
PRIVATE,
as
desired.
At any
time
during
the
above
process,
your program can be
tested
by
running
it
just
as
you
run
any program
in
the
HP-75
using
a
plug-in
module.
After
you have
developed
and
fully
tested
your program
in
the
PMS
and
are
satisfied
with
the
results,
you
may
elect
to
have
Hewlett-Packard
create
your
permanent
plug-in
module.
You
should
contact
Hewlett-Packard
for
further
in-
formation
on
how
to
proceed.
Refer
to
appendix
E
for
the
operational
limitations
on
the
use
of
the
PMS
and
permanent
plug-in
modules.
*
Optional
step.
10
I
•
Refer
to
appendix
A
for
a
detailed
example
of
the
PMS
in
use.
SYSTEM
COMMANDS
The
commands used by
the
PMS
are
summarized
in
the
Command
Index
inside
the
back
cover.
With
the
exception
of
the
CAT,
the
two COPY, and
the
PURGE
commands,
they
are
unique
to
the
PMS.
Note:
Since
all
of
the
PMS
commands
are
programmable,
it
is
possible
to
include
them
inadvertently
in
a
PMS
file.
Therefore,
the
PMS
command
file
should
be purged from
the
HP-75
prior
to
final
verification
of
a module
to
ensure
that
the
PMS
programs
are
not
dependent
upon
the
commands.
COMMAND
DESCRIPTIONS
The
PMS
commands
are
described
below,
together
with
examples
of
their
use,
and
lists
of
relevant
error
messages.
Error
messages
with
numbers
less
than
100
are
identical
to
the
HP-75
error
messages.
(Refer
to
your HP-75
owner's
manual
for
further
information.)
Error
messages
with
numbers
greater
than
100
are
unique
to
the
PMS
.
The
error
listings
show
the
errors
commonly
They
are
not
exhaustive;
other
applicable
displayed.
(Refer
to
appendix
C
for
details
All
commands
listed
are
programmable.
associated
with
the
HP-75
error
messages
may
of
the
error
messages.)
Syntax
Summary:
(Refer
to
appendix
D
for
further
details.)
[ ]
--
indicates
use
is
optional.
filename
- a
parameter
which
may
be any
HP-75-compatible
file
name.
command.
also
be
lexname - a
parameter
which
contains
the
name
of
a
language
extension
file.
device
- a
parameter
which
may
be
anyone
of
six
PMS
bank
addresses,
ROMA,
..•
ROMF.
romid - a
parameter
which
contains
a numeric
expression
which
identifies
a
a bank
in
the
PMS.
All
string
expressions
and commands
may
be
either
upper-
or
lowercase,
and
may
be
delimited
by
single
or
double
quotes
as
long
as
they
match.
BUILD
':device',
romid
[,'lexname']
CAT
'[filename]:device'
CHECKSUM
(':device')
11
COPY
['filename']
TO
'[filename]:device'
COPY
'ALL:device'
TO
'filename'
PRIVATE
'filename:device'
PURGE
'filename:device'
ROMAVAIL
(':device')
ROMID
(':device')
ROMSIZE
('filename')
Initializing
a Bank
(BUILD)
BUILD
':device',
romid
[,'lexname'J
This
command
initializes
the
designated
PMS
bank.
All
information
previous-
ly
recorded
in
the
bank
is
erased,
and a
catalog
directory
is
created.
A
ROM
ID
must be
specified
at
this
time.
This
number
is
used
by
the
HP-75
uniquely
to
identify
each
bank
within
a
plug-in
module.
It
may
be
any number I
in
the
range
-32767
through
-257
and
+3
through
+32767
inclusive.
However,
while
developing
your
module,
you
should
use
only
those
numbers
in
the
range
100
to
199
to
avoid
possible
confusion
with
any
permanent
plug-in
modules you
may
be
using.
No
two
PMS
banks
should
be
assigned
the
same
ROM
ID
number.
If
the
number
assigned
is
already
present,
an
error
will
be
reported.
Note:
The
use
of
duplicate
ROM
ID
numbers
could
cause
serious
operating
problems,
such
as
the
loss
of
all
files.
Any
single
language
extension
(LEX)
file
compatible
with
the
HP-75
standard
may
be
optionally
specified
for
inclusion
in
a bank
at
initialization.
A
LEX
file
can
be
removed from a bank
only
by
the
use
of
this
command.
Refer
to
your
HP-75
owner's
manual
for
a
further
discussion
of
LEX
files.
After
you
have
copied
a
LEX
file
into
the
PMS,
you must
purge
HP-75
before
typing
in
the
BASIC
program
which
uses
it.
program
may
use
the
incorrect
LEX
file.
Examples:
it
from
the
Otherwise,
the
BUILD
':roma',
100
Initializes
bank A and
assigns
it
the
ID
number 100.
12
)
BUILD'
:ROMF',
101,
'Lex'
110
BUILD'
:romb',
110
Errors:
{device
not
present}
{file
active}
{file
not
found}
{invalid
checksum}
{invalid
file}
{invalid
filespec}
.•
{wrong
file
type}
{duplicate
romid}
Listing
Files
(CAT)
Initializes
bank
F,
assigns
it
the
ID
number 101, and
copies
the
language
extension
file
Lex
into
it.
Initializes
bank
B
in
a
program
and
assigns
it
the
ID
number
110.
CAT
'[filename]:device'
]
A
CAT
command
lists
individual
files
or
all
the
files
within
a
PMS
bank.
The
file
name,
type,
byte
length,
and
time
and
date
of
entry
are
displayed
in
the
HP-75.
Examples:
CAT
'TANK:roma'
Lists
the
file
TANK
in
pms
bank
A.
CAT
':
ROMB'
Lists
all
files
in
PMS
bank
B.
13
100 A$='TANK:romf'
110
CAT
A$
Errors:
{bank
not
initialized}
{device
not
present}
{invalid
filespec}
{file
not
found}
Error
Check
(CHECKSUM)
CHECKSUM
(':device')
Assigns
string
variable.
Displays
files
in
bank F
during
the
running
of
the
program.
A
CHECKSUM
command
will
return
the
checksum
byte
required
to
produce
a
checksum
of
255
in
the
designated
bank.
If
this
checksum
does
not
match
the
checksum
stored
in
the
operation,
a 232
error--INVALID
CHECKSUM
is
displayed.
error
in
the
HP-75
or
in
the
bank.
In
no
way
can
the
bank
except
by
using
the
BUILD
command.
bank
after
a
write
This
indicates
an
then
be
accessed
Examples:
CHECKSUM
(tt:ROMCtt)
100 R$=tt:roma
tt
200
V=CHECKSUM
(R$)
210 DISP'Checksum
is'jV
14
Displays
checksum
for
bank
C.
Assigns
string
variable.
Assigns
the
checksum
for
bank A
to
V
in
a
program.
Displays
checksum
during
the
running
of
the
program.
I
•
•
•
Errors:
(bank
not
initialized)
(device
not
present)
(invalid
checksum)
(bad
parameter)
Transferring
Files
(COPY)
There
are
three
categories
of
this
command:
o
Transferring
files
from
the
HP-75
to
the
PMS.
o
Transferring
individual
files
from
the
PMS
to
the
HP-75.
o
Transferring
a
complete
bank from
the
PMS
to
the
HP-75.
Transferring
Files
From
the
HP-75
to
the
PMS
•
I
COPY
['filename']
TO
'[filename]:device'
This
command
will
copy a
specified
file
from
the
HP-75 memory
into
the
PMS.
If
the
destination
file
name
is
not
specified,
the
source
file
name
will
be
used.
If
the
source
file
name
is
not
specified,
the
current
edit
file
will
be
copied.
At
least
one
of
the
files,
however,
must be named.
(If
a
program
in
the
HP-75
has
the
same
name
as
a
program
in
the
PMS,
only
the
program
in
the
HP-75
can
be
run.)
A bank must be empty
before
a
ROM
file
is
copied
into
it.
If
a
ROM
file
is
copied
into
a
bank,
the
ID
number
of
the
ROM
file
will
become
the
bank
ROMID
number.
You
may
copy a
maximum
of
eight
files
plus
one
LEX
file
into
a
bank.
Examples:
COpy
'TEST'
TO
'T1:ROMA'
COpy
'R1'
TO
':romd'
Copies
Test
file
from
the
HP-75
to
bank A and
renames
it
T1.
Copies
R1
file
from
the
HP-75
to
bank
D
under
the
same name.
15
100 A$="Progl"
110 B$='
:roma'
120
COPY
A$
to
B$
Assigns
string
variable.
Assigns
string
variable.
Copies
Progl
file
from
the
HP-75
to
bank A
under
the
same name.
Transferring
Individual
Files
From
the
PMS
to
the
HP-75.
COPY
'filename'
TO
'filename'
This
command
will
copy a
specified
file
from a
PMS
bank
to
the
HP-75.
It
is
the
same
as
the
HP-75
COpy
command.
No
device
specifier
is
required,
since
the
HP-75
will
determine
where
the
file
is
located
so
long
as
the
file
name
is
used
in
only
one
bank.
Example:
COPY
'Tl'
TO
'Testl'
Copies
file
Tl from a
PMS
bank
to
the
HP-75 and
renames
it
Testl.
Transferring
A Complete Bank From
the
PMS
to
the
HP-75.
COPY
'ALL:device'
TO
'filename'
This
command
will
copy
the
complete
set
of
files
in
a
particular
PMS
bank
to
the
HP-75 and
designate
them
as
a
single
ROM
file.
Example:
COPY'all:romf'
TO
'End'
16
Copies
all
the
files
in
bank
F
to
the
HP-75
as
a
single
ROM
file
and names
it
End.
I
•
•
•
A
ROM
file
can
only
be
copied
or
purged;
it
can
not
be
edited.
If
you
wish
to
edit
a
ROM
file,
you
must
first
copy
it
into
an
initialized
PMS
bank
and
then
copy
the
individual
file
you
wish
to
edit
back
into
the
HP-75 ,
edit
it
and
return
it
to
the
PMS
bank,
and
recopy
it
into
the
HP-75
as
a
ROM
file.
A
ROM
file
can
not
be
copied
into
a
partially
filled
PMS
bank.
The bank
can
be
initialized
by
executing
the
BUILD
command.
The
file
named
may
be
of
any
type
compatible
with
the
HP-75.
COpy
command
is
subject
to
the
following
restrictions:
However,
the
o Language
extension
(LEX)
file:
Only one
LEX
file
may
be
stored
in
a
PMS
bank
(Refer
to
the
BUILD
command.)
o
BASIC
file:
A
file
pointer
is
allocated
and added
to
the
file.
There-
fore,
the
file
size
listed
by
the
CAT
command
may
be
too
small
to
use
in
determining
the
required
bank
memory.
(Refer
to
the
ROMSIZE
command.)
Any
single
language
extension
(LEX)
file
compatible
with
the
HP-75
standard
may
be
optionally
specified
for
inclusion
in
a
bank
at
initialization.
Errors
when
copying
into
the
PMS:
{device
not
present}
{device
not
allowed}
{bank
not
initialized}
{duplicate
name}
{bank
not
empty}
{file
not
found}
{bank
full}
{invalid
file}
{invalid
checksum}
{invalid
filespec}
{wrong
file
type}
(duplicate
romid)
17
Errors
when
copying
into
the
HP-75:
{device
not
present}
{device
not
allowed}
{bank
not
initialized}
{duplicate
name}
{invalid
filespec}
{not
enough memory}
{invalid
checksum}
{file
not
found}
File
Security
(PRIVATE)
PRIVATE
'filename:device'
This
command
will
mark
the
specified
file
within
the
PMS
as
private.
All
files
can
be
made
private.
A
private
file
can be
run
or
purged
but
can be
copied
only
when
the
complete
contents
of
the
bank
are
transferred
to
the
HP-75. A
private
file
can
not
be
listed
or
edited
since
it
can
not
be
re-
turned
to
the
HP-75.
Examples:
PRIVATE
'MYFILE:ROMA'
100 A$="Tl :romb"
110
Private
A$
Errors:
{bank
not
initialized}
{device
not
present}
{file
not
found}
{invalid
checksum}
{invalid
filespec}
18
Marks
Myfile
in
bank
A
as
private.
Assigns
a
string
variable.
Marks Tl
in
bank
B
as
private
in
the
program.
•
Erasing
a
File
(PURGE)
PURGE
'filename:device'
This
command
will
remove
the
specified
file
from
the
PMS.
It
is
not
revers-
ible.
A
LEX
file
can
not
be
purged.
Example:
PURGE
'T1:ROMA' Removes
T1
from bank
A.
Errors:
,bank
not
initialized}
{device
not
present}
{file
active}
..
{file
not
found}
•
{invalid
checksum}
{invalid
filespec}
{wrong
file
type}
Bank
Memory
Availability
(ROMAVAIL)
ROMAVAIL
('
:device')
1
This
command
will
return
the
decimal
number
of
unused
bytes
of
memory
avail-
able
in
the
specified
PMS
bank.
Examples:
ROMAVAIL
('
:romd')
Returns
the
number
of
available
bytes
of
memory
in
bank
D.
19
100 A$='
:roma'
110
ROMAVAIL
(A$)
Errors:
{bank
not
initialized}
{device
not
present}
{bad
parameter}
Bank
Identification
(ROMID)
ROMID
(':device')
Assigns
a
string
variable.
Displays
the
number
of
bytes
of
memory
in
bank
the
running
of
the
program.
available
A
during
This
command
will
return
the
decimal
bank
identification
number which was
assigned
at
initialization.
It
is
used
primarily
to
verify
the
identity
of
a
PMS
bank.
Examples:
ROMID
(":romb
n)
Returns
the
ID
number
of
bank
B.
5
IF
ROMID(':ROMC')=100
THEN
BEEP
I
The
command
used
in
a
program.
Errors:
{bank
not
initialized}
{device
not
present}
{bad
parameter}
20
I
•
•
•
File
Memory
Requirement
(ROMSIZE)
ROMSIZE
('filename')
]
This
command
will
return
the
decimal
number
of
bytes
of
memory
required
to
store
the
specified
file
in
any
PMS
bank.
All
file
types
are
allowed.
Examples:
ROMSIZE
('TEST')
Returns
the
number
of
bytes
of
memory
required
to
store
file
TEST.
10
A$='TEST'@B$='
:ROMC'
Assigns
string
variables.
20
s=romavail(B$}-romsize(a$}
30
If
s)=O
then
disp
s
Errors:
{file
not
found}
{bad
parameter}
{invalid
filespec}
KEY
REDEFINITION
If
you
wish
to
use
a
key-redefinition
file
in
your
PMS,
you
something
other
than
"keys".
When
you
wish
to
use
the
file
keys,
you must copy
it
into
the
HP-75 and
then
rename
it
to
keep
this
in
mind
when
redefining
the
keys
in
a program•
must
name
it
to
redefine
your
"keys".
Be
sure
21/22
Table of contents
Other HP Network Hardware manuals
HP
HP AJ878A - StorageWorks 320 GB Hard Drive User manual
HP
HP Presario X1000 - Notebook PC User manual
HP
HP StorageWorks X1000 G2 How to use
HP
HP 400338-001 - KVM Switch User manual
HP
HP IBRIX X9000 User manual
HP
HP ARUBA 8320 48 10/6 40 X472 5 2 Bdl Assembly instructions
HP
HP SL500 (M852x) User manual
HP
HP Compaq NC6133 User instructions
HP
HP StorageWorks T5521A Manual
HP
HP X1600 - StorageWorks Network Storage System 5.4TB SAS Model NAS... User manual
HP
HP StorageWorks 1/8 Tape Autoloader User manual
HP
HP 5900AF-48XG-4QSFP+ Assembly instructions
HP
HP StoreOnce 4700 Installation and user guide
HP
HP StorageWorks x9300 Service manual
HP
HP XP 9000 User manual
HP
HP Aruba 640 Assembly instructions
HP
HP E8491B IEEE 1394 User manual
HP
HP 5500-24G-SFP EI TAA Assembly instructions
HP
HP Deskjet 870 User manual
HP
HP c-Class Installation guide
Popular Network Hardware manuals by other brands
Accton Technology
Accton Technology 1000BASE-LX Quick installation guide
Matrix Switch Corporation
Matrix Switch Corporation MSC-CP16X4E product manual
H3C
H3C NSQ1TGX4EA0 LPU manual
WIN Enterprises
WIN Enterprises PL-80590 user manual
Emerson
Emerson Centellis 2000 Installation and use
MikroTik
MikroTik RBM11G quick start guide
