10.02.2013 Views

a E i - Commodore Is Awesome

a E i - Commodore Is Awesome

a E i - Commodore Is Awesome

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

El<br />

F<br />

he purpose of these programs is to<br />

copy whole disks on tape, so as to store<br />

them in a convenient low volume form.<br />

The backup on tape proceeds at 16<br />

times the standard CM speed (even<br />

faster than standard turbo tape<br />

format!) This means that the 175K of a<br />

1541 disk drive are packed on only five<br />

minutes of tape.<br />

Data is saved in three steps each of<br />

which saves approximately 60K of<br />

data, in track increasing order. All<br />

blocks are transferred, even free ones.<br />

This ensures that a disk copy will<br />

always fi t the .atne length of tape, a<br />

useful feature if you want to rewrite<br />

updated data over an already existing<br />

copy. (However there is one exception<br />

— if blocks do not read properly, they<br />

are written in shortform so the entire<br />

copy will be shorter. It also means that<br />

it is not really worthwhile to use this<br />

program to save nearly empty disks.)<br />

the program is made up of two<br />

complimentary parts: MCOPYTD<br />

and MCOPYDT. MCOPYTD saves<br />

data on tape and MCOPYDT reads it<br />

back to disk. These programs can also<br />

be used with the 1571 disk drive in 1541<br />

mode. However only single sided disks<br />

or the first side of a double sided one<br />

can be saved with this version of the<br />

program. To use MCOPY, just RIJN<br />

the two Basic programs (when keying<br />

these, don't forget the DATA<br />

000,000. lines, since the checksum<br />

does not detect such omissions). Of<br />

course, since they are created on disk,<br />

a formatted disk must be in the drive.<br />

Getting Started<br />

Load MCOPYDT (disk to tape).<br />

Make certain that you are past the<br />

leader of the tape.<br />

Put the disk to be copied in the drive,<br />

Run MCOPYDT: the introductory<br />

message appears_<br />

Press record and play (the tape does<br />

not move yet).<br />

C64 PROGRAMA<br />

isk Archive<br />

A handy set of two programs to help you save your<br />

programs to tape in a convenient firm.<br />

By Jean Lebailley<br />

Press RETURN. The program starts to<br />

read the disk, then transfers its contents<br />

on to tape in three steps. DO<br />

NOT stop the recorder between steps.<br />

When the process ends the message<br />

"END OF COPY" appears, along<br />

with error messages if needed. Note the<br />

tape counter value.<br />

An error does not always mean<br />

that the whole copy is bad. However<br />

when the tape is reread the same error<br />

will be recreated on the new disk (also<br />

the copy on tape will be shorter).<br />

Therefore, it is up to the user to decide<br />

what to do when such an error occurs.<br />

Reading Back<br />

Load MCOPYTD (tape to disk).<br />

Put a new disk in the drive.<br />

Put a cassette into the datasette. Position<br />

tape to read the first of the three<br />

subsections previously saved. Reading<br />

over the end of other data does not<br />

matter since MCOPY only starts<br />

reading after having found a special<br />

synchronising header.<br />

Run M CO P Y D<br />

The read back proceeds in the same<br />

way as MCOPYDT, in three steps.<br />

At the end of the process, the<br />

message "END OF COPY" appears.<br />

Remove the disk from drive (it doesn't<br />

matter if the red LED is still on, this is<br />

normal).<br />

Two kinds of errors can arise<br />

during the readback process. Unfortunately,<br />

they are almost always fatal.<br />

WRITE ERROR TRACK NN —<br />

means that the drive could not reread<br />

the data, it just writes on that track.<br />

This is usually caused by a bad disk.<br />

Try again with another one (see also<br />

TAPE LOADING ERROR).<br />

TAPE LOADING ERROR — The cassette<br />

could not be read back properly.<br />

This is usually caused by one of the<br />

following:<br />

YOUR COMMODORE january 1987<br />

58<br />

Bad tape; use only good quality cassettes.<br />

Although the encryption<br />

scheme used to write on tape is very<br />

reliable by itself, a singly false bit in the<br />

601(4 causes the error. I previously<br />

wrote these programs using standard<br />

turbo routines but an error occured<br />

nearly every time in one of the three<br />

sequences, it was also slower and the<br />

length of tape used was data dependent.<br />

(10 took less time to save than 'FF's.)<br />

Try to save 60K with standard turbo<br />

on the same tape you are very likely to<br />

see several errors, not just one.<br />

Read head is dirty, clean it.<br />

Read head has gone out of alignment<br />

since the tape was written. Realign it.<br />

The recorder has been knocked or<br />

moved during read or write: this causes<br />

tape speed changes that can lead to<br />

errors.<br />

The tape has been damaged, usually<br />

unrecoverable.<br />

Too much friction inside cassette.<br />

Rewind it and retry.<br />

You can (and it is recommended)<br />

leave blank space on tape between<br />

disks: to do that, just press the ! key<br />

and the recorder starts. Stop by pressing<br />

any other key.<br />

I<br />

N<br />

BS 1 0 R EM<br />

E SC 20 REM CREATES MCOPYDT ON DI<br />

F SK<br />

T<br />

91 30 REM<br />

Y<br />

53 40 REM FAST DISK TO TAPE BAC<br />

E<br />

KUP PROGRAM<br />

T<br />

B9 SO REM SALTS UP TO 12 SINGLE<br />

7<br />

SIDED DISKS<br />

.<br />

83 BO REM<br />

R<br />

14 70 REM ON A SINGLE CEO CASSE<br />

.<br />

TIE<br />

F<br />

OF BO R EM<br />

n<br />

T e3 90 REM WRITTEN BY J.LEBAILLY<br />

E<br />

EB 100 REM<br />

36 110 OPEN2,8,2,"e0:MCOPYDI,P.<br />

FS 120 PRINT#2,CHRS(1);CHRS(B);

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!