Sophie: opencbm-0.4.2a-5mdv2010.0 i586

opencbm-0.4.2a-5mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
 <TITLE>OpenCBM 0.4.2 Users Guide: Utilities: d64copy</TITLE>
 <LINK HREF="opencbm-21.html" REL=next>
 <LINK HREF="opencbm-19.html" REL=previous>
 <LINK HREF="opencbm.html#toc7" REL=contents>
</HEAD>
<BODY>
<A HREF="opencbm-21.html">Next</A>
<A HREF="opencbm-19.html">Previous</A>
<A HREF="opencbm.html#toc7">Contents</A>
<HR>
<H2><A NAME="d64copy"></A> 7.5 <A HREF="opencbm.html#toc7.5">d64copy</A></H2>

<P><I>d64copy</I> is a fast disk image transfer (both read and write) program for
the 1541 and compatible devices (1570, 1571, third-party clones). A 1581 drive
is <I>not</I> supported! Maximum transfer speed is achieved by custom drive- and
transfer-routines based on the Star Commander ((C) Joe Forster/STA) routines.</P>

<H3><A NAME="invoking-d64copy"></A> d64copy invocation</H3>

<P>Synopsis: <CODE>d64copy [OPTION]... SOURCE TARGET</CODE></P>

<P>Either SOURCE or TARGET must be an external drive, valid names are 8, 9, 10 and
11. The other parameter specifies the file name of the .d64 image.</P>
<P>Here's a complete list of known options:</P>
<P>
<DL>
<DT><B>-h, --help</B><DD><P>Display help and exit</P>

<DT><B>-V, --version</B><DD><P>Display version information and exit.</P>

<DT><B>-q, --quiet</B><DD><P>Quiet output, fewer messages (also suppresses warnings, should not be used)</P>

<DT><B>-v, --verbose</B><DD><P>Verbose output, more messages (can be repeated)</P>

<DT><B>-n, --no-progress</B><DD><P>Omit progress display</P>

<DT><B>-s, --start-track=<I>start track</I></B><DD><P>Set start track (defaults to 1)</P>

<DT><B>-e, --end-track=<I>end track</I></B><DD><P>Set end track (default is 35 for .d64 images, 70 for .d71 images). <I>d64copy</I>
is able to access tracks 1-35 in <CODE>original</CODE> transfer mode and 1-42 with
<CODE>serial1</CODE>, <CODE>serial2</CODE> and <CODE>parallel</CODE>. The 1571 supports tracks 1-70
in double sided (.d71) mode.</P>

<DT><B>-t, --transfer=<I>transfer mode</I></B><DD><P>Set transfermode. Valid modes are:
<UL>
<LI><CODE>auto</CODE>     (default)</LI>
<LI><CODE>original</CODE> (slowest)</LI>
<LI><CODE>serial1</CODE></LI>
<LI><CODE>serial2</CODE></LI>
<LI><CODE>parallel</CODE> (fastest)</LI>
</UL>

<CODE>original</CODE> and <CODE>serial1</CODE> should work in any case.
<CODE>serial2</CODE> won't work with more than one device
connected to the IEC bus, 
<CODE>parallel</CODE> requires an additional XP1541/XP1571 cable.</P>

<P>If <CODE>auto</CODE> is used, d64copy itself determines the best transfer mode usable
with the current setup, and uses that one. Thus, you will seldom want to 
manually overdrive the <I>transfer mode</I> option.</P>

<DT><B>-i, --interleave=<I>interleave</I></B><DD><P>Set interleave value. This is ignored when reading in warp mode. Default is 16
for transfer mode <CODE>original</CODE>, for turbo and warp write as follows:
<BLOCKQUOTE><CODE>
<PRE>

          turbo (r/w)    warp (write only)
serial1       3                 5
serial2      12                11
parallel      6                 3
</PRE>
</CODE></BLOCKQUOTE>

Lower values might slightly reduce transfer times, but if set a bit to low,
transfer times will dramatically increase.</P>

<DT><B>-w, --warp</B><DD><P>Enable warp mode. This is default now; this option is only supported for
backward-compatibility with OpenCBM (cbm4linux/cbm4win) versions before 0.4.0.</P>

<DT><B>--no-warp</B><DD><P>Disable warp mode. Warp mode is usually a good idea for transferring disk
images unless you have a very slow CPU and/or bad disk material. Warp mode
sends raw GCR data over the bus, which assures data integrity on the PC side
and relieves the drive's CPU. Thus, it is unlikely you will want to use that
option.</P>

<DT><B>-b, --bam-only</B><DD><P>BAM-only copy. Only blocks marked as allocated are copied. For extended tracks
(36-40), SpeedDOS BAM format is assumed. Use with caution, at least one wide-spread
directory editor tends to forget to allocate some directory blocks.</P>

<DT><B>-B, --bam-save</B><DD><P>Safe BAM-only copy. This is like the <CODE>-b</CODE> option but always copies the
entire directory track (18, 18 and 53 in double-sided mode).</P>

<DT><B>-d, --drive-type=<CODE>type</CODE></B><DD><P>Skip drive type detection. <CODE>0</CODE> or <CODE>1541</CODE> specifies 1541 mode (1 MHz,
parallel cable at VIA $1800), <CODE>1</CODE> or <CODE>1571</CODE> forces 1571 mode (2 MHz,
parallel cable at CIA $4000).</P>

<DT><B>-2, --two-sided</B><DD><P>Double-sided mode for copying .d71 images to/from a 1571 drive. Warp mode is
not supported (yet).</P>

<DT><B>-r, --retry-count=<CODE>count</CODE></B><DD><P>Number of retries.</P>

<DT><B>-E, --error-mode=<CODE>mode</CODE></B><DD><P>Controls whether error is appended to the disk image (15x1->PC only).
Allowed values for <CODE>mode</CODE> are (abbreviations allowed):
<UL>
<LI><CODE>always</CODE></LI>
<LI><CODE>on_error</CODE>  (default)</LI>
<LI><CODE>never</CODE></LI>
</UL>
</P>

</DL>
</P>

<H3><A NAME="d64copy examples"></A> d64copy Examples</H3>

<P>Read a D64 disc image from the floppy in drive 8 to the file image.d64,
automatically selecting the fastest transfer method:
<HR>
<PRE>
d64copy 8 image.d64
</PRE>
<HR>
</P>

<P>Copy the D64 disc image in image.d64 to the floppy in drive 9, automatically
selecting the fastest transfer method:
<HR>
<PRE>
d64copy image.d64 9
</PRE>
<HR>
</P>

<P>Copy a double-sided disc from a 1571 drive 9 to image.d71, using
<CODE>serial1</CODE> transfer method and only reading the blocks which are
marked as used in the BAM:
<HR>
<PRE>
d64copy -2 -B --transfer=serial1 9 image.d64
</PRE>
<HR>
</P>

<HR>
<A HREF="opencbm-21.html">Next</A>
<A HREF="opencbm-19.html">Previous</A>
<A HREF="opencbm.html#toc7">Contents</A>
</BODY>
</HTML>