COPYFILES utility RP AUTOMATION INC. DEC 1988

 

Preliminary Documentation

 

 

1.0 Introduction

This set of programs provides a mechanism for copying files

from one diskette to another using the VAL II system.

 

 

 

2.0 Subroutine Description

 

The following subroutines are provided in this package:

 

Name Description

 

rp.copyfiles This is the program that the

user needs to EXECUTE from the

VAL II monitor ("." prompt).

Ensure that no PC program is

executing when performing this

function.

 

rp.delete These programs are not to be

rp.flpdir EXECUTE'd by the user. They are

rp.flperr used internally by the routines

rp.flpin that perform the COPYFILES

rp.flpin.cmd function.

rp.flpout

rp.flpout.out4.in

rp.flpout1

rp.format

rp.get.string

rp.get.string.upper

rp.openr

rp.openw

rp.print.file

rp.rblk

rp.rdfiles

rp.type.string

rp.wblk

rp.wfiles

 

 

3.0 Software Installation

The software is installed using the following procedure:

 

1) The ZALLOCATE command must be used to create a buffer

area for this program to use. The amount of ZALLOCATE'd

space is optional, but it is recommended that as much

as possible be allocated so that there will be a minimum

amount of diskette changing.

 

2) Load the RP_COPYFILES.V2 file from floppy. This is

done by typing:

LOAD RP_COPYFILES.V2

 

3) Execute the program by typing:

EXECUTE RP.COPYFILES

 

4) Answer the questions appropriately when asked to do so.

 

 

4.0 Software execution

 

1) The program will ask for a prompt when the first disk

is installed in the floppy disk drive. Pressing <RETURN>

at this point causes the floppy disk directory to get

listed on the CRT screen.

 

2) Select which files are to be copied. When all files to

be copied have been entered, press <RETURN> at the next

prompt.

 

3) The files will then begin to get read from the first

floppy diskette. When all files have been read, or if

the ZALLOCATE'd area gets filled, then the program will

prompt for changing to the new diskette. When the new

diskette is in place and <RETURN> is typed, those files

in memory will be written to the new diskette.

 

4) When all files have been read and written, then the

program finishes and returns to the VAL II monitor.

 

 

 

5.0 Special notes

 

1) When a file is read from the first diskette, the

filename is displayed. And, each time that a new

block is read, a number between 0 and 7 is displayed

on the screen. This is a count for the number of

blocks being read for that file.

 

2) When a file is written to the second diskette, the

filename is displayed. Each time that a new block

is read, a number between 0 and 7 is displayed on

the screen. This is a count for the number of blocks

being written to that file.

 

3) If the diskette to be written to is not formatted, then

the program will query the user whether to FORMAT the

diskette or RETRY. This gives the user the option to

change to a different diskette if desired.

 

4) If a filename already exists on the second diskette, then

the program will query the user whether to DELETE the

file or RETRY. This gives the user the option to change

to a different diskette if desired.

 

5) If any of the specified files are not found on the

diskette, then the program will simply ignore those

files.

 

6) If a file is not completed during a reading/writing

session, then when the first diskette is read again,

the message is:

Continuing to read <filename>

instead of:

Reading <filename>

and a similar message is generated when writing the

file.

 

 

6.0 Variable names used

The following list of real variable names are used within this set

of programs. They are reserved and should not be used:

rp.blkcnt rp.bs.sp.bs[] rp.checksum

rp.chr rp.cr.lf[] rp.dirbuf[]

rp.file.blks[] rp.get.i rp.getchr

rp.getcmd rp.i rp.idir

rp.in.new rp.in.ptr.blks rp.in.ptr.name

rp.inbuf[] rp.num.blks rp.num.wds

rp.numb rp.out.new rp.out.ptr.blks

rp.out.ptr.name rp.outchr[] rp.temp.data[]

rp.tmp rp.type.i rp.z.beg.addr

rp.z.data.zpoke[]

 

7.0 Messages

"*** ZALLOCATE AREA NOT SET UP ***"

This message signifies that the user forgot to use the

ZALLOCATE command before LOAD'ing in the "RP_COPYFILES.V2"

file. The program will abort at this point, and the entire

loading procedure must done again.

"Press <CR> to ..."

When this message gets displayed, the diskettes should be

swapped, and then the <CR> (<RETURN>) key pressed.

"*** Floppy error nn ***"

This message signifies that a floppy error occured. The

number corresponds to the internal floppy error code:

2 = File already exists (creating new file with same name)

3 = File does not exist (opening file for reading)

4 = Communications error between VAL & floppy

5 = Disk full (writing to disk)

6 = Communications error between VAL & floppy

7 = Communications error between VAL & floppy

10 = Communications error between VAL & floppy

11 = Communications error between VAL & floppy

12 = Floppy not ready

13 = Floppy read error (diskette may be bad)

14 = Communications error between VAL & floppy

41 = No STX received during block transfer

42 = Incorrect checksum received during block transfer

"Cannot open WRITE file. Type <CR> to retry, <F> to FORMAT DISK:"

This message signifies that an error occured when trying

to write the first file on the diskette. If an "F" character

is typed (followed by a <CR>), then the diskette will get

FORMAT'd. Otherwise, the program will assume that the user

changed the diskette and will retry the writing procedure.

 

RP Automation
Tel  (800) 367-7862  (800) FOR PUMA  Fax  (203) 792-2154
Email  info@rpautomation.com

all content copyright RP Automation 1997