|
From: <st...@us...> - 2010-06-01 19:16:47
|
Revision: 22587
http://vice-emu.svn.sourceforge.net/vice-emu/?rev=22587&view=rev
Author: strik
Date: 2010-06-01 19:16:38 +0000 (Tue, 01 Jun 2010)
Log Message:
-----------
Remove generated files.
Removed Paths:
-------------
trunk/vice/doc/html/vice_1.html
trunk/vice/doc/html/vice_10.html
trunk/vice/doc/html/vice_11.html
trunk/vice/doc/html/vice_12.html
trunk/vice/doc/html/vice_13.html
trunk/vice/doc/html/vice_14.html
trunk/vice/doc/html/vice_15.html
trunk/vice/doc/html/vice_16.html
trunk/vice/doc/html/vice_2.html
trunk/vice/doc/html/vice_3.html
trunk/vice/doc/html/vice_4.html
trunk/vice/doc/html/vice_5.html
trunk/vice/doc/html/vice_6.html
trunk/vice/doc/html/vice_7.html
trunk/vice/doc/html/vice_8.html
trunk/vice/doc/html/vice_9.html
trunk/vice/doc/html/vice_toc.html
trunk/vice/doc/vice.info
Property Changed:
----------------
trunk/vice/doc/
trunk/vice/doc/html/
Property changes on: trunk/vice/doc
___________________________________________________________________
Modified: svn:ignore
- Makefile
Makefile.in
texinfo.tex
vice.html
+ Makefile
Makefile.in
texinfo.tex
vice.html
vice.info
Property changes on: trunk/vice/doc/html
___________________________________________________________________
Modified: svn:ignore
- Makefile
Makefile.in
+ Makefile
Makefile.in
vice_*.html
Deleted: trunk/vice/doc/html/vice_1.html
===================================================================
--- trunk/vice/doc/html/vice_1.html 2010-06-01 18:38:03 UTC (rev 22586)
+++ trunk/vice/doc/html/vice_1.html 2010-06-01 19:16:38 UTC (rev 22587)
@@ -1,461 +0,0 @@
-<HTML>
-<HEAD>
-<!-- This HTML file has been created by texi2html 1.52
- from ../vice.texi on 30 May 2010 -->
-
-<TITLE>VICE Manual - 1 GNU GENERAL PUBLIC LICENSE</TITLE>
-</HEAD>
-<BODY>
-Go to the first, previous, <A HREF="vice_2.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-<P><HR><P>
-
-
-<H1><A NAME="SEC1" HREF="vice_toc.html#TOC1">1 GNU GENERAL PUBLIC LICENSE</A></H1>
-
-<P>
-Version 2, June 1991
-
-</P>
-
-<PRE>
-Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675
-Mass Ave, Boston, MA 02111-1307, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-</PRE>
-
-
-
-<H2><A NAME="SEC2" HREF="vice_toc.html#TOC2">Preamble</A></H2>
-
-<P>
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
-</P>
-<P>
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-</P>
-<P>
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-</P>
-<P>
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
-</P>
-<P>
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-</P>
-<P>
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-</P>
-<P>
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-</P>
-<P>
- The precise terms and conditions for copying, distribution and
-modification follow.
-
-</P>
-
-
-<H2><A NAME="SEC3" HREF="vice_toc.html#TOC3">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</A></H2>
-
-
-<OL>
-<LI>
-
-This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-<LI>
-
-You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-<LI>
-
-You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-
-<OL>
-<LI>
-
-You must cause the modified files to carry prominent notices
-stating that you changed the files and the date of any change.
-
-<LI>
-
-You must cause any work that you distribute or publish, that in
-whole or in part contains or is derived from the Program or any
-part thereof, to be licensed as a whole at no charge to all third
-parties under the terms of this License.
-
-<LI>
-
-If the modified program normally reads commands interactively
-when run, you must cause it, when started running for such
-interactive use in the most ordinary way, to print or display an
-announcement including an appropriate copyright notice and a
-notice that there is no warranty (or else, saying that you provide
-a warranty) and that users may redistribute the program under
-these conditions, and telling the user how to view a copy of this
-License. (Exception: if the Program itself is interactive but
-does not normally print such an announcement, your work based on
-the Program is not required to print an announcement.)
-</OL>
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-<LI>
-
-You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-
-<OL>
-<LI>
-
-Accompany it with the complete corresponding machine-readable
-source code, which must be distributed under the terms of Sections
-1 and 2 above on a medium customarily used for software interchange; or,
-
-<LI>
-
-Accompany it with a written offer, valid for at least three
-years, to give any third party, for a charge no more than your
-cost of physically performing source distribution, a complete
-machine-readable copy of the corresponding source code, to be
-distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange; or,
-
-<LI>
-
-Accompany it with the information you received as to the offer
-to distribute corresponding source code. (This alternative is
-allowed only for noncommercial distribution and only if you
-received the program in object code or executable form with such
-an offer, in accord with Subsection b above.)
-</OL>
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-<LI>
-
-You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-<LI>
-
-You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-<LI>
-
-Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-<LI>
-
-If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-<LI>
-
-If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-<LI>
-
-The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-<LI>
-
-If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-
-
-<P><STRONG>1.1 NO WARRANTY</STRONG></P>
-
-<LI>
-
-BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-<LI>
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-</OL>
-
-
-<H2>1.2 END OF TERMS AND CONDITIONS</H2>
-
-
-
-<H2><A NAME="SEC4" HREF="vice_toc.html#TOC4">How to Apply These Terms to Your New Programs</A></H2>
-
-<P>
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-</P>
-<P>
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-</P>
-
-<PRE>
-<VAR>one line to give the program's name and an idea of what it does.</VAR>
-Copyright (C) 19<VAR>yy</VAR> <VAR>name of author</VAR>
-
-This program is free software; you can redistribute it and/or
-modify it under the terms of the GNU General Public License
-as published by the Free Software Foundation; either version 2
-of the License, or (at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
-</PRE>
-
-<P>
-Also add information on how to contact you by electronic and paper mail.
-
-</P>
-<P>
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-</P>
-
-<PRE>
-Gnomovision version 69, Copyright (C) 19<VAR>yy</VAR> <VAR>name of author</VAR>
-Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
-type `show w'. This is free software, and you are welcome
-to redistribute it under certain conditions; type `show c'
-for details.
-</PRE>
-
-<P>
-The hypothetical commands <SAMP>`show w'</SAMP> and <SAMP>`show c'</SAMP> should show
-the appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than <SAMP>`show w'</SAMP> and
-<SAMP>`show c'</SAMP>; they could even be mouse-clicks or menu items--whatever
-suits your program.
-
-</P>
-<P>
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
-</P>
-
-<PRE>
-Yoyodyne, Inc., hereby disclaims all copyright
-interest in the program `Gnomovision'
-(which makes passes at compilers) written
-by James Hacker.
-
-<VAR>signature of Ty Coon</VAR>, 1 April 1989
-Ty Coon, President of Vice
-</PRE>
-
-<P>
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
-
-</P>
-<P><HR><P>
-Go to the first, previous, <A HREF="vice_2.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-</BODY>
-</HTML>
Deleted: trunk/vice/doc/html/vice_10.html
===================================================================
--- trunk/vice/doc/html/vice_10.html 2010-06-01 18:38:03 UTC (rev 22586)
+++ trunk/vice/doc/html/vice_10.html 2010-06-01 19:16:38 UTC (rev 22587)
@@ -1,298 +0,0 @@
-<HTML>
-<HEAD>
-<!-- This HTML file has been created by texi2html 1.52
- from ../vice.texi on 30 May 2010 -->
-
-<TITLE>VICE Manual - 10 c1541</TITLE>
-</HEAD>
-<BODY>
-Go to the <A HREF="vice_1.html">first</A>, <A HREF="vice_9.html">previous</A>, <A HREF="vice_11.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-<P><HR><P>
-
-
-<H1><A NAME="SEC157" HREF="vice_toc.html#TOC157">10 c1541</A></H1>
-
-<P>
-VICE is provided with a complete stand-alone disk image maintenance
-utility, called <CODE>c1541</CODE>.
-
-</P>
-<P>
-You can either invoke it from the command
-line or from within one of the VICE emulators, using the "Run c1541"
-command which will open a new <CODE>xterm</CODE> window with a running
-<CODE>c1541</CODE> in it.
-
-</P>
-<P>
-The syntax is:
-
-</P>
-
-<PRE>
-c1541 [IMAGE1 [IMAGE2]] [COMMAND1 COMMAND2 ... COMMANDN]
-</PRE>
-
-<P>
-<CODE>IMAGE1</CODE> and <CODE>IMAGE2</CODE> are disk image names that can be
-attached before <CODE>c1541</CODE> starts. <CODE>c1541</CODE> can handle up to
-two disk images at the same time by using two virtual built-in drives,
-numbered <CODE>8</CODE> and <CODE>9</CODE>; <CODE>IMAGE1</CODE> (if present) is always
-attached to drive <CODE>8</CODE>, while <CODE>IMAGE2</CODE> is attached to drive
-<CODE>9</CODE>.
-
-</P>
-<P>
-<CODE>COMMAND</CODE>s specified on the command-line all begin with the minus
-sign (<CODE>-</CODE>); if present, <CODE>c1541</CODE> executes them in the same
-order as they are on the command line and returns a zero error code if
-they were successful. If any of the <CODE>COMMAND</CODE>s fails, <CODE>c1541</CODE>
-stops and returns a nonzero error code.
-
-</P>
-<P>
-If no <CODE>COMMAND</CODE>s are specified at all, <CODE>c1541</CODE> enters
-interactive mode, where you can type commands manually. Commands in
-interactive mode are the same as commands in batch mode, but do not
-require a leading <CODE>-</CODE>. As with the monitor, file name completion
-and command line editing with history are provided via GNU
-<CODE>readline</CODE>. Use the command <SAMP>`quit'</SAMP> or press <KBD>C-d</KBD> to
-exit.
-
-</P>
-
-
-
-<H2><A NAME="SEC158" HREF="vice_toc.html#TOC158">10.1 Specifying files in c1541</A></H2>
-
-<P>
-When accessing CBM DOS files (i.e. files that reside on disk images),
-c1541 uses a special syntax that lets you access files on both drive 8
-and 9. If you prepend the file name with <CODE>@8:</CODE> or <CODE>@9:</CODE>, you
-will specified that file is to be found or created on drive 8 and 9,
-respectively.
-
-</P>
-<P>
-For instance,
-
-</P>
-
-<PRE>
-@8:somefile
-</PRE>
-
-<P>
-will name file named <CODE>somefile</CODE> on unit 8, while
-
-</P>
-
-<PRE>
-@9:somefile
-</PRE>
-
-<P>
-will name file named <CODE>somefile</CODE> on unit 9.
-
-</P>
-
-
-<H2><A NAME="SEC159" HREF="vice_toc.html#TOC159">10.2 Using quotes and backslashes</A></H2>
-
-<P>
-You can use quotes (<CODE>"</CODE>) in a command to embed spaces into file
-names. For instance,
-
-</P>
-
-<PRE>
-read some file
-</PRE>
-
-<P>
-will read file <CODE>some</CODE> from the disk image and write it into the
-file system as <CODE>file</CODE>, while
-
-</P>
-
-<PRE>
-read "some file"
-</PRE>
-
-<P>
-will copy <CODE>some file</CODE> into the file system, with the name
-<CODE>some file</CODE>.
-
-</P>
-<P>
-The backslash character (<CODE>\</CODE>) has a special meaning too: it lets
-you literally insert the following character no matter what it is. For
-example,
-
-</P>
-
-<PRE>
-read some\ file
-</PRE>
-
-<P>
-will copy file <CODE>some file</CODE> into the file system, while
-
-</P>
-
-<PRE>
-read some\ file this\"file
-</PRE>
-
-<P>
-will copy <CODE>some file</CODE> into the file system with name
-<CODE>this"file</CODE> (with an embedded quote).
-
-</P>
-
-
-
-<H2><A NAME="SEC160" HREF="vice_toc.html#TOC160">10.3 c1541 commands and options</A></H2>
-
-<P>
-This is a list of the <CODE>c1541</CODE> commands. They are shown in their
-interactive form, without the leading <CODE>-</CODE>.
-Square brackets [] indicate an optional part, and "<COMMAND>" translates
-to a disk command according to CBM DOS, like "i0" for example.
-
-</P>
-<DL COMPACT>
-
-<DT><CODE>[<command>]</CODE>
-<DD>
-Execute specified CBM DOS command and print the current status of the
-drive. If no <CODE>command</CODE> is specified, just print the status.
-
-<DT><CODE>? [<command>]</CODE>
-<DD>
-Explain specified command. If no command is specified, list available
-ones.
-
-<DT><CODE>attach <diskimage> [<unit>]</CODE>
-<DD>
-Attach <CODE>diskimage</CODE> to <CODE>unit</CODE> (default unit is 8).
-
-<DT><CODE>block <track> <sector> <disp> [<drive>]</CODE>
-<DD>
-Show specified disk block in hex form.
-
-<DT><CODE>copy <source1> [<source2> ... <sourceN>] <destination></CODE>
-<DD>
-Copy <CODE>source1</CODE> ... <CODE>sourceN</CODE> into destination. If N > 1,
-<CODE>destination</CODE> must be a simple drive specifier (<CODE>@n:</CODE>).
-
-<DT><CODE>delete <file1> [<file2> ... <fileN>]</CODE>
-<DD>
-Delete the specified files.
-
-<DT><CODE>exit</CODE>
-<DD>
-Exit (same as <CODE>quit</CODE>).
-
-<DT><CODE>extract</CODE>
-<DD>
-Extract all the files to the file system.
-
-<DT><CODE>format <diskname,id> [<type> <imagename>] [<unit>]</CODE>
-<DD>
-If <CODE>unit</CODE> is specified, format the disk in unit <CODE>unit</CODE>. If
-<CODE>type</CODE> and <CODE>imagename</CODE> are specified, create a new image named
-<CODE>imagename</CODE>, attach it to unit 8 and format it. <CODE>type</CODE> is a
-disk image type, and must be either <CODE>x64</CODE>, <CODE>d64</CODE> (both VC1541/2031),
-<CODE>g64</CODE> (VC1541/2031 but in GCR coding), <CODE>d71</CODE> (VC1571), <CODE>d81</CODE>
-(VC1581), <CODE>d80</CODE> (CBM8050) or <CODE>d82</CODE> (CBM8250/1001).
-Otherwise, format the disk in the current unit, if any.
-
-<DT><CODE>gcrformat <diskname,id> <imagename></CODE>
-<DD>
-Create and format a G64 disk image named <CODE>imagename</CODE>.
-
-<DT><CODE>help [<command>]</CODE>
-<DD>
-Explain specified command. If no command is specified, list available
-ones.
-
-<DT><CODE>info [<unit>]</CODE>
-<DD>
-Display information about unit <CODE>unit</CODE> (if unspecified, use the current
-one).
-
-<DT><CODE>list [<pattern>]</CODE>
-<DD>
-List files matching <CODE>pattern</CODE> (default is all files).
-
-<DT><CODE>quit</CODE>
-<DD>
-Exit (same as <CODE>exit</CODE>).
-
-<DT><CODE>read <source> [<destination>]</CODE>
-<DD>
-Read <CODE>source</CODE> from the disk image and copy it into <CODE>destination</CODE> in
-the file system. If <CODE>destination</CODE> is not specified, copy it into a
-file with the same name as <CODE>source</CODE>.",
-
-<DT><CODE>rename <oldname> <newname></CODE>
-<DD>
-Rename <CODE>oldname</CODE> into <CODE>newname</CODE>. The files must be on the
-same drive.
-
-<DT><CODE>tape <t64name> [<file1> ... <fileN>]</CODE>
-<DD>
-Extract files from a T64 image.
-
-<DT><CODE>unit <number></CODE>
-<DD>
-Make unit <CODE>number</CODE> the current unit.
-
-<DT><CODE>unlynx <lynxname> [<unit>]</CODE>
-<DD>
-Extract the specified Lynx image file into the specified unit (default
-is the current unit).
-
-<DT><CODE>validate [<unit>]</CODE>
-<DD>
-Validate the disk in unit <CODE>unit</CODE>. If <CODE>unit</CODE> is not specified,
-validate the disk in the current unit.
-
-<DT><CODE>write <source> [<destination>]</CODE>
-<DD>
-Write <CODE>source</CODE> from the file system into <CODE>destination</CODE> on a
-disk image.
-
-<DT><CODE>zcreate <x64name> <zipname> [<label,id>]</CODE>
-<DD>
-Create an X64 disk image out of a set of four Zipcoded files named
-<CODE>1!zipname</CODE>, <CODE>2!zipname</CODE>, <CODE>3!zipname</CODE> and
-<CODE>4!zipname</CODE>.
-
-</DL>
-
-
-
-<H2><A NAME="SEC161" HREF="vice_toc.html#TOC161">10.4 Executing shell commands</A></H2>
-
-<P>
-If you want to execute a shell command from withing <CODE>c1541</CODE>, just
-prepend it with an exclamation mark (<CODE>!</CODE>). For example,
-
-</P>
-
-<PRE>
-!ls -la
-</PRE>
-
-<P>
-will execute the command <CODE>ls -la</CODE>, which will show you all the
-files in the current directory.
-
-</P>
-
-<P><HR><P>
-Go to the <A HREF="vice_1.html">first</A>, <A HREF="vice_9.html">previous</A>, <A HREF="vice_11.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-</BODY>
-</HTML>
Deleted: trunk/vice/doc/html/vice_11.html
===================================================================
--- trunk/vice/doc/html/vice_11.html 2010-06-01 18:38:03 UTC (rev 22586)
+++ trunk/vice/doc/html/vice_11.html 2010-06-01 19:16:38 UTC (rev 22587)
@@ -1,617 +0,0 @@
-<HTML>
-<HEAD>
-<!-- This HTML file has been created by texi2html 1.52
- from ../vice.texi on 30 May 2010 -->
-
-<TITLE>VICE Manual - 11 The emulator file formats</TITLE>
-</HEAD>
-<BODY>
-Go to the <A HREF="vice_1.html">first</A>, <A HREF="vice_10.html">previous</A>, <A HREF="vice_12.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-<P><HR><P>
-
-
-<H1><A NAME="SEC162" HREF="vice_toc.html#TOC162">11 The emulator file formats</A></H1>
-
-<P>
-This chapter gives a technical description of the various files
-supported by the emulators.
-
-</P>
-
-
-
-<H2><A NAME="SEC163" HREF="vice_toc.html#TOC163">11.1 The T64 tape image format</A></H2>
-
-<P>
-(This section was taken from the C64S distribution.)
-
-</P>
-<P>
-The <CODE>T64</CODE> File Structure was developed by Miha Peternel for use in
-the C64S emulator. It is easy to use and allows future extensions.
-
-</P>
-
-
-
-<H3><A NAME="SEC164" HREF="vice_toc.html#TOC164">11.1.1 T64 File structure</A></H3>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Size</B></TD>
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>0</TD>
-
-<TD>64</TD>
-<TD>tape record</TD>
-</TR>
-<TR><TD>64</TD>
-
-<TD>32*n</TD>
-<TD>file records for n directory entries</TD>
-</TR>
-<TR><TD>64+32*n</TD>
-
-<TD>varies</TD>
-<TD>binary contents of the files</TD>
-</TR></TABLE>
-
-
-
-<H3><A NAME="SEC165" HREF="vice_toc.html#TOC165">11.1.2 Tape Record</A></H3>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Size</B></TD>
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>0</TD>
-
-<TD>32</TD>
-<TD>DOS tape description + EOF (for type)</TD>
-</TR>
-<TR><TD>32</TD>
-
-<TD>2</TD>
-<TD>tape version ($0200)</TD>
-</TR>
-<TR><TD>34</TD>
-
-<TD>2</TD>
-<TD>number of directory entries</TD>
-</TR>
-<TR><TD>36</TD>
-
-<TD>2</TD>
-<TD>number of used entries (can be 0 in my loader)</TD>
-</TR>
-<TR><TD>38</TD>
-
-<TD>2</TD>
-<TD>free</TD>
-</TR>
-<TR><TD>40</TD>
-
-<TD>24</TD>
-<TD>user description as displayed in tape menu</TD>
-</TR></TABLE>
-
-
-
-<H3><A NAME="SEC166" HREF="vice_toc.html#TOC166">11.1.3 File record</A></H3>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Size</B></TD>
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>0</TD>
-
-<TD>1</TD>
-<TD>entry type (see below)</TD>
-</TR>
-<TR><TD>1</TD>
-
-<TD>1</TD>
-<TD>C64 file type</TD>
-</TR>
-<TR><TD>2</TD>
-
-<TD>2</TD>
-<TD>start address</TD>
-</TR>
-<TR><TD>4</TD>
-
-<TD>2</TD>
-<TD>end address</TD>
-</TR>
-<TR><TD>6</TD>
-
-<TD>2</TD>
-<TD>free</TD>
-</TR>
-<TR><TD>8</TD>
-
-<TD>4</TD>
-<TD>offset of file contents start within T64 file</TD>
-</TR>
-<TR><TD>12</TD>
-
-<TD>4</TD>
-<TD>free</TD>
-</TR>
-<TR><TD>16</TD>
-
-<TD>16</TD>
-<TD>C64 file name</TD>
-</TR></TABLE>
-
-<P>
-Valid entry types are:
-
-</P>
-<TABLE BORDER>
-
-<TR><TD><B>Code</B></TD>
-
-<TD><B>Explanation</B></TD>
-</TR>
-<TR><TD><CODE>0</CODE></TD>
-
-<TD>free entry</TD>
-</TR>
-<TR><TD><CODE>1</CODE></TD>
-
-<TD>normal tape file</TD>
-</TR>
-<TR><TD><CODE>2</CODE></TD>
-
-<TD>tape file with header: header is saved just before file data</TD>
-</TR>
-<TR><TD><CODE>3</CODE></TD>
-
-<TD>memory snapshot v0.9, uncompressed</TD>
-</TR>
-<TR><TD><CODE>4</CODE></TD>
-
-<TD>tape block</TD>
-</TR>
-<TR><TD><CODE>5</CODE></TD>
-
-<TD>digitized stream</TD>
-</TR>
-<TR><TD><CODE>6</CODE> ... <CODE>255</CODE></TD>
-
-<TD>reserved</TD>
-</TR></TABLE>
-
-<P>
-Notes:
-
-</P>
-
-<UL>
-<LI>VICE only supports file type <CODE>1</CODE>.
-
-<LI>Types <CODE>3</CODE>, <CODE>4</CODE> and <CODE>5</CODE> are subject to change (and
-
-are rarely used).
-</UL>
-
-
-
-<H2><A NAME="SEC167" HREF="vice_toc.html#TOC167">11.2 The G64 GCR-encoded disk image format</A></H2>
-
-<P>
-(This section was contributed by Peter Schepers and slightly edited by
-Ettore Perazzoli.)
-
-</P>
-<P>
-This format was defined in 1998 as a cooperative effort between several
-emulator people, mainly Per H\xE5kan Sundell, author of the CCS64 C64
-emulator, Andreas Boose of the VICE CBM emulator team and Joe
-Forster/STA, the author of Star Commander. It was the first real public
-attempt to create a format for the emulator community which removed
-almost all of the drawbacks of the other existing image formats, namely
-<CODE>D64</CODE>.
-
-</P>
-<P>
-The intention behind <CODE>G64</CODE> is not to replace the widely used
-<CODE>D64</CODE> format, as <CODE>D64</CODE> works fine with the vast majority of
-disks in existence. It is intended for those small percentage of
-programs which demand to work with the 1541 drive in a non-standard way,
-such as reading or writing data in a custom format. The best example is
-with speeder software such as Action Cartridge in Warp Save mode or
-Vorpal which write track/sector data in another format other than
-standard GCR. The other obvious example is copy-protected software
-which looks for some specific data on a track, like the disk ID, which
-is not stored in a standard <CODE>D64</CODE> image.
-
-</P>
-<P>
-<CODE>G64</CODE> has a deceptively simply layout for what it is capable of
-doing. We have a signature, version byte, some predefined size values,
-and a series of offsets to the track data and speed zones. It is what's
-contained in the track data areas and speed zones which is really at the
-heart of this format.
-
-</P>
-<P>
-Each track entry in simply the raw stream of GCR data, just what a read
-head would see when a diskette is rotating past it. How the data gets
-interpreted is up to the program trying to access the disk. Because the
-data is stored in such a low-level manner, just about anything can be
-done. Most of the time I would suspect the data in the track would be
-standard sectors, with SYNC, GAP, header, data and checksums. The
-arrangement of the data when it is in a standard GCR sector layout is
-beyond the scope of this document.
-
-</P>
-<P>
-Since it is a flexible format in both track count and track byte size,
-there is no "standard" file size. However, given a few constants like
-42 tracks and halftracks, a track size of 7928 bytes and no speed offset
-entries, the typical file size will a minimum of 333744 bytes.
-
-</P>
-<P>
-Below is a dump of the header, broken down into its various parts.
-After that will be an explanation of the track offset and speed zone
-offset areas, as they demand much more explanation.
-
-</P>
-
-<PRE>
-Addr 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
----- -----------------------------------------------
-0000: 47 43 52 2D 31 35 34 31 00 54 F8 1E .. .. .. ..
-</PRE>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>$0000-0007</TD>
-
-<TD>File signature (<CODE>GCR-1541</CODE>)</TD>
-</TR>
-<TR><TD>$0008</TD>
-
-<TD><CODE>G64</CODE> version (presently only $00 defined)</TD>
-</TR>
-<TR><TD>$0009</TD>
-
-<TD>Number of tracks in image (usually $54, decimal 84)</TD>
-</TR>
-<TR><TD>$000A-000B</TD>
-
-<TD>Size of each stored track in bytes (usually 7928, or $1EF8) in LO/HI format.</TD>
-</TR></TABLE>
-
-<P>
-An obvious question here is "why are there 84 tracks defined when a
-normal <CODE>D64</CODE> disk only has 35 tracks?" Well, by definition, this
-image includes all half-tracks, so there are actually 42 tracks and 42
-half tracks. The 1541 stepper motor can access up to 42 tracks and the
-in-between half-tracks. Even though using more than 35 tracks is not
-typical, it was important to define this format from the start with what
-the 1541 is capable of doing, and not just what it typically does.
-
-</P>
-<P>
-At first, the defined track size value of 7928 bytes may seem to be
-arbitrary, but it is not. It is determined by the fastest write speed
-possible (speed zone 0), coupled with the average rotation speed of the
-disk (300 rpm). After some math, the answer that actually comes up is
-7692 bytes. Why the discrepency between the actual size of 7692 and the
-defined size of 7928? Simply put, not all drives rotate at 300 rpm.
-Some can be faster or slower, so a upper safety margin of +3% was built
-added, in case some disks rotate slower and can write more data. After
-applying this safety factor, and some rounding-up, 7928 bytes per track
-was arrived at.
-
-</P>
-<P>
-Also note that this upper limit of 7928 bytes per track really only
-applies to 1541 and compatible disks. If this format were applied to
-another disk type like the SFD1001, this value would be higher.
-
-</P>
-<P>
-Below is a dump of the first section of a <CODE>G64</CODE> file, showing the offsets
-to the data portion for each track and half-track entry. Following that
-is a dump of the speed zone offsets.
-
-</P>
-
-<PRE>
-Addr 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
----- -----------------------------------------------
-0000: .. .. .. .. .. .. .. .. .. .. .. .. AC 02 00 00
-0010: 00 00 00 00 A6 21 00 00 00 00 00 00 A0 40 00 00
-0020: 00 00 00 00 9A 5F 00 00 00 00 00 00 94 7E 00 00
-0030: 00 00 00 00 8E 9D 00 00 00 00 00 00 88 BC 00 00
-0040: 00 00 00 00 82 DB 00 00 00 00 00 00 7C FA 00 00
-0050: 00 00 00 00 76 19 01 00 00 00 00 00 70 38 01 00
-0060: 00 00 00 00 6A 57 01 00 00 00 00 00 64 76 01 00
-0070: 00 00 00 00 5E 95 01 00 00 00 00 00 58 B4 01 00
-0080: 00 00 00 00 52 D3 01 00 00 00 00 00 4C F2 01 00
-0090: 00 00 00 00 46 11 02 00 00 00 00 00 40 30 02 00
-00A0: 00 00 00 00 3A 4F 02 00 00 00 00 00 34 6E 02 00
-00B0: 00 00 00 00 2E 8D 02 00 00 00 00 00 28 AC 02 00
-00C0: 00 00 00 00 22 CB 02 00 00 00 00 00 1C EA 02 00
-00D0: 00 00 00 00 16 09 03 00 00 00 00 00 10 28 03 00
-00E0: 00 00 00 00 0A 47 03 00 00 00 00 00 04 66 03 00
-00F0: 00 00 00 00 FE 84 03 00 00 00 00 00 F8 A3 03 00
-0100: 00 00 00 00 F2 C2 03 00 00 00 00 00 EC E1 03 00
-0110: 00 00 00 00 E6 00 04 00 00 00 00 00 E0 1F 04 00
-0120: 00 00 00 00 DA 3E 04 00 00 00 00 00 D4 5D 04 00
-0130: 00 00 00 00 CE 7C 04 00 00 00 00 00 C8 9B 04 00
-0140: 00 00 00 00 C2 BA 04 00 00 00 00 00 BC D9 04 00
-0150: 00 00 00 00 B6 F8 04 00 00 00 00 00 .. .. .. ..
-</PRE>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>$000C-000F</TD>
-
-<TD>Offset to stored track 1.0 ($000002AC, in LO/HI format, see below for more)</TD>
-</TR>
-<TR><TD>$0010-0013</TD>
-
-<TD>Offset to stored track 1.5 ($00000000)</TD>
-</TR>
-<TR><TD>$0014-0017</TD>
-
-<TD>Offset to stored track 2.0 ($000021A6)</TD>
-</TR>
-<TR><TD>...</TD>
-
-</TR>
-<TR><TD>$0154-0157</TD>
-
-<TD>Offset to stored track 42.0 ($0004F8B6)</TD>
-</TR>
-<TR><TD>$0158-015B</TD>
-
-<TD>Offset to stored track 42.5 ($00000000)</TD>
-</TR></TABLE>
-
-
-<PRE>
- 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
- -----------------------------------------------
-0150: .. .. .. .. .. .. .. .. .. .. .. .. 03 00 00 00
-0160: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-0170: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-0180: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-0190: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-01A0: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-01B0: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-01C0: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-01D0: 00 00 00 00 03 00 00 00 00 00 00 00 03 00 00 00
-01E0: 00 00 00 00 02 00 00 00 00 00 00 00 02 00 00 00
-01F0: 00 00 00 00 02 00 00 00 00 00 00 00 02 00 00 00
-0200: 00 00 00 00 02 00 00 00 00 00 00 00 02 00 00 00
-0210: 00 00 00 00 02 00 00 00 00 00 00 00 01 00 00 00
-0220: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
-0230: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
-0240: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
-0250: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-0260: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-0270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-0280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-0290: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-02A0: 00 00 00 00 00 00 00 00 00 00 00 00 .. .. .. ..
-</PRE>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>$015C-015F</TD>
-
-<TD>Speed zone entry for track 1 ($03, in LO/HI format, see below for more)</TD>
-</TR>
-<TR><TD>$0160-0163</TD>
-
-<TD>Speed zone entry for track 1.5 ($03)</TD>
-</TR>
-<TR><TD>...</TD>
-
-</TR>
-<TR><TD>$02A4-02A7</TD>
-
-<TD>Speed zone entry for track 42 ($00)</TD>
-</TR>
-<TR><TD>$02A8-02AB</TD>
-
-<TD>Speed zone entry for track 42.5 ($00)</TD>
-</TR></TABLE>
-
-<P>
-Starting here at $02AC is the first track entry (from above, it is the
-first entry for track 1.0)
-
-</P>
-<P>
-The track offsets (from above) require some explanation. When one is
-set to all 0's, no track data exists for this entry. If there is a
-value, it is an absolute reference into the file (starting from the
-beginning of the file). From the track 1.0 entry we see it is set for
-$000002AC. Going to that file offset, here is what we see...
-
-</P>
-
-<PRE>
- 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
- -----------------------------------------------
-02A0: .. .. .. .. .. .. .. .. .. .. .. .. 0C 1E FF FF
-02B0: FF FF FF 52 54 B5 29 4B 7A 5E 95 55 55 55 55 55
-02C0: 55 55 55 55 55 55 FF FF FF FF FF 55 D4 A5 29 4A
-02D0: 52 94 A5 29 4A 52 94 A5 29 4A 52 94 A5 29 4A 52
-</PRE>
-
-<TABLE BORDER>
-
-<TR><TD><B>Offset</B></TD>
-
-<TD><B>Description</B></TD>
-</TR>
-<TR><TD>$02AC-02AD</TD>
-
-<TD>Actual size of stored track (7692 or $1E0C, in LO/HI format)</TD>
-</TR>
-<TR><TD>$02AE-02AE+$1E0C</TD>
-
-<TD>Track data</TD>
-</TR></TABLE>
-
-<P>
-Following the track data is filler bytes. In this case, there are 368
-bytes of unused space. This space can contain anything, but for the
-sake of those wishing to compress these images for storage, they should
-all be set to the same value. In the sample I used, these are all set
-to $FF.
-
-</P>
-<P>
-Below is a dump of the end of the track 1.0 data area. Note the actual
-track data ends at address $20B9, with the rest of the block being
-unused, and set to $FF.
-
-</P>
-
-<PRE>
- 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
- -----------------------------------------------
-1FE0: 52 94 A5 29 4A 52 94 A5 29 4A 52 94 A5 29 4A 52
-1FF0: 94 A5 29 4A 52 94 A5 29 4A 52 94 A5 29 4A 52 94
-2000: A5 29 4A 52 94 A5 29 4A 52 94 A5 29 4A 52 94 A5
-2010: 29 4A 52 94 A5 29 4A 52 94 A5 29 4A 52 94 A5 29
-2020: 4A 52 94 A5 29 4A 52 94 A5 29 4A 52 94 A5 29 4A
-2030: 55 55 55 55 55 55 FF FF FF FF FF FF FF FF FF FF
-2040: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2050: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2060: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2070: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2080: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2090: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-20A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-20B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-20C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-20D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-20E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-20F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2100: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2110: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2120: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2140: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-2190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-21A0: FF FF FF FF FF FF .. .. .. .. .. .. .. .. .. ..
-</PRE>
-
-<P>
-The speed offset entries can be a little more complex. The 1541 has four
-speed zones defined, which means the drive can write data at four
-distinct speeds. On a normal 1541 disk, these zones are as follows:
-
-</P>
-<TABLE BORDER>
-
-<TR><TD><B>Track Range</B></TD>
-
-<TD><B>Speed Zone</B></TD>
-</TR>
-<TR><TD>1-17</TD>
-
-<TD>3 (highest writing speed)</TD>
-</TR>
-<TR><TD>18-24</TD>
-
-<TD>2</TD>
-</TR>
-<TR><TD>25-30</TD>
-
-<TD>1</TD>
-</TR>
-<TR><TD>31 and up</TD>
-
-<TD>0 (lowest writing speed)</TD>
-</TR></TABLE>
-
-<P>
-Note that you can, through custom programming of the 1541, change the
-speed zone of any track to something different (change the 3 to a 0) and
-write data differently. From the dump of the speed offset entries
-above, we see that all the entries are in the range of 0-3. If any entry
-is less than 4, this is not considered a speed offset but defines the
-whole track to be recorded at that one speed.
-
-</P>
-<P>
-In the example I had, there were no offsets defined, so no speed zone
-dump can be shown. However, I can define what should be there. You
-will have a block of data, 1982 bytes long. Each byte is encoded to
-represent the speed of 4 bytes in the track offset area, and is broken
-down as follows:
-
-</P>
-
-<PRE>
-Speed entry $FF: in binary %11111111
- |'|'|'|'
- | | | |
- | | | +- 4'th byte speed (binary 11, 3 dec)
- | | +--- 3'rd byte speed (binary 11, 3 dec)
- | +----- 2'nd byte speed (binary 11, 3 dec)
- +------- 1'st byte speed (binary 11, 3 dec)
-</PRE>
-
-<P>
-It was very smart thinking to allow for two speed zone settings, one in
-the offset block and another defining the speed on a per-byte basis. If
-you are working with a normal disk, where each track is one constant
-speed, then you don't need the extra blocks of information hanging
-around the image, wasting space.
-
-</P>
-<P>
-What may not be obvious is the flexibility of this format to add tracks
-and speed offset zones at will. If a program decides to write a track
-out with varying speeds, and no speed offset exist, a new block will be
-created by appending it to the end of the image, and the offset pointer
-for that track set to point to the new block. If a track has no offset
-yet, meaning it doesn't exist (like a half-track), and one needs to be
-added, the same procedure applies. The location of the actual track or
-speed zone data is not important, meaning they do not have to be in any
-particular order since they are all referenced by the offsets at the
-beginning of the image.
-
-</P>
-<P><HR><P>
-Go to the <A HREF="vice_1.html">first</A>, <A HREF="vice_10.html">previous</A>, <A HREF="vice_12.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-</BODY>
-</HTML>
Deleted: trunk/vice/doc/html/vice_12.html
===================================================================
--- trunk/vice/doc/html/vice_12.html 2010-06-01 18:38:03 UTC (rev 22586)
+++ trunk/vice/doc/html/vice_12.html 2010-06-01 19:16:38 UTC (rev 22587)
@@ -1,664 +0,0 @@
-<HTML>
-<HEAD>
-<!-- This HTML file has been created by texi2html 1.52
- from ../vice.texi on 30 May 2010 -->
-
-<TITLE>VICE Manual - 12 Acknowledgments</TITLE>
-</HEAD>
-<BODY>
-Go to the <A HREF="vice_1.html">first</A>, <A HREF="vice_11.html">previous</A>, <A HREF="vice_13.html">next</A>, <A HREF="vice_16.html">last</A> section, <A HREF="vice_toc.html">table of contents</A>.
-<P><HR><P>
-
-
-<H1><A NAME="SEC168" HREF="vice_toc.html#TOC168">12 Acknowledgments</A></H1>
-
-<P>
-VICE derives from X64, the first Commodore 64 emulator for the X Window
-System. Here is an informal list of the people who were mostly involved
-in the development of X64 and VICE:
-
-</P>
-<P>
-The VICE core team:
-
-<UL>
-
-<LI>
-
-<B>Andreas Boose</B> gave lots of
-information and bug reports about the VIC-II, the 6510 and the
-CIAs; moreover, he wrote several test-routines that were used
-to improve the emulation. He also added cartridge support and
-has been the main head behind the drive and datasette emulation
-since version 0.15. Also added several UI elements to the
-MSDOS, MS-Windows and Unix ports. He rewrote the C128 emulation
-adding Z80 mode, C64 mode and function ROM support, wrote the
-screenshot and the event system and started the plus4 emulator.
-Restructured the serial bus emulation and added realdrive and
-rawdrive support.
-
-<LI>
-
-<B>Dag Lem</B> implemented the reSID SID emulation
-engine and video hardware scaling.
-
-<LI>
-
-<B>Tibor Biczo</B> improved the MS-Windows port
-and plus4 emulation.
-
-<LI>
-
-<B>Andreas Dehmel</B> wrote the Acorn RISC OS port.
-
-<LI>
-
-<B>Andreas Matthies</B> improved the
-datasette support, the VIC20 video emulation and some ui stuff
-in the Win32 and MSDOS port. He also wrote the BeOS port and
-implemented video/audio capture support.
-Improved history recording/playback and implented support for
-video recording and netlink feature. Made the win32 user
-changable keyboard shortcut system. Various bug(fixe)s. ;-)
-
-<LI>
-
-<B>Martin Pottendorfer</B>
-Implemented Gnome Port based on Oliver Schaertels GTK+ port
-Added support code for internationalization based on gettext
-Improved the *nix fullscreen support
-Translated the Unix Port to German
-Implemented the fliplists + ui (unix).
-
-<LI>
-
-<B>Spiro Trikaliotis</B> wrote the Win32
-console implementation for the built-in monitor, corrected some
-REU related bugs, improved the CIA emulation, added com-port
-CIA support to the win32 port, added text copy and paste support
-to the win32 port, added support for the TFE and RR-Net (cs8900a),
-and wrote some further patches.
-
-<LI>
-
-<B>Markus Brenner</B> added VDC emulation to x128
-and added support for some more cartridges.
-
-<LI>
-
-<B>David Hansel</B> wrote the Star NL10 printer driver, implemented IEC
-devices and improved the tape emulation.
-
-<LI>
-
-<B>Marco van den Heuvel</B> Translated the UI to Dutch. Made the
-Internationalization support for the Win32 and Amiga ports. Wrote
-the GEORAM and RamCart cartridge code. Wrote the c64 +60K, +256K and
-256K memory expansions code. Wrote the pet REU code. Wrote the plus4
-memory expansions code. Made the ethernet support for the Msdos port.
-Maintains the RiscOS, QNX 4.x, QNX 6.x, SkyOS, Solaris, Openserver,
-Unixware, HPUX, GP2X, Minix 3.x, Amiga, ppc-BeOS and newly
-resurrected OS/2 binary ports. Maintains the win64 and watcom project
-files. Co-maintains the SDL port(s). Added new .crt support. Added
-new screenshot formats. Added new sound recording support. Added
-SIDcart support for pet, plus4 and vic20. Improved the MMC64 emulation.
-Added 2 MHz mode and banks 2/3 support for x128. Added the various
-userport joystick emulations. Added text copy and paste support to the
-amiga and beos ports. Added DQBB and Isepic cartridge support. Added
-SFX soundsampler and soundexpander support. Added digiblaster support.
-And lots of other fixes and improvements.
-
-<LI>
-
-<B>Christian Vogelgsang</B> maintains the Mac OS X port. Added Intel Mac
-support and universal binary creation. Wrote the build scripts for
-all external Mac libraries and the bindist bundle tool. Improved
-the TFE chip emulation. Added some Gtk+ fixes.
-
-<LI>
-
-<B>Fabrizio Gennari</B> added some improvements to the MSDOS- and GTK
-port.
-
-<LI>
-
-<B>Hannu Nuotio</B> implemented DTV flash emulation, DTV support in the
-monitor, large parts of the DTV VIC emulation, burst mode and skip
-cycle emulation as well as many other things. Added NEOS and Amiga
-mouse, paddle and light pen support. Added new monitor commands and
-features, including memmap. Made MIDI support and OSS MIDI driver.
-Implemented most of the SDL UI. Rewrote xvic CPU/VIC-I core for
-cycle based emulation.
-
-<LI>
-
-<B>Daniel Kahlin</B> Worked on DTV VIC emulation, palette, DTV SID support
-in resid, better DMA/Blitter support and did lots of refactoring. Added
-new monitor commands and features. Improved the VIC emulation for xvic.
-Made MIDI driver code for win32. Rewrote the xvic cartridge system.
-Added Mega-Cart and Final Expansion V3.2 support to xvic.
-
-<LI>
-
-<B>Antti S. Lankila</B> Made the ReSID-fp engine, rewrote the PAL
-emulation code and fixed the sound core for lower latency. Rewrote DTV
-SID support (ReSID-dtv).
-
-</UL>
-
-<P>
-Former team members:
-
-</P>
-
-<UL>
-
-<LI>
-
-<B>M. Kiesel</B> started implementing x64dtv. The C64DTV memory model
-and early versions of the DMA and Blitter engine have been implemented
-by him. Added new monitor commands and features.
-
-<LI>
-
-<B>Thomas Bretz</B>
-Copyright (C) 1999-2004
-Started the OS/2 port.
-
-<LI>
-
-<B>Daniel Sladic</B>
-Copyright (C) 1997-2001
-Started the work on hardware-level 1541 emulation and wrote the new
-monitor introduced with VICE 0.15.
-
-<LI>
-
-<B>Andr\xE9 Fachat</B>
-Copyright (C) 1996-2001
-Wrote the PET and CBM-II emulators, the CIA and VIA emulation,
-the IEEE488 interface, implemented the IEC serial bus in `xvic'
-and made tons of bug fixes.
-
-<LI>
-
-<B>Ettore Perazzoli</B>
-Copyright (C) 1996-1999
-Made the 6510, VIC-II, VIC-I and CRTC emulations, part of the
-hardware-level 1541 emulation, speed optimizations, bug fixes,
-the event-driven cycle-exact engine, the Xt/Xaw/Xfwf-based GUI
-for X11, a general code reorganization, the new resource
-handling, most of the documentation. He also wrote the MS-DOS
-port and the initial MS-Windows port (well, somebody had to do
-it).
-
-<LI>
-
-<B>Teemu Rantanen</B>
-Copyright (C) 1993-1994, 1997-1999
-Implemented the SID emulation and the trap-based disk drive and
-serial bus implementation; added support for multiple display
-depths under X11. Also wrote `c1541'
-
-<LI>
-
-<B>Jouko Valta</B>
-Copyright (C) 1993-1996
-Wrote `petcat' and `c1541', `T64' handling, user service and
-maintenance (most of the work in x64 0.3.x was made by him);
-retired from the project in July 96, after VICE 0.10.0.
-
-<LI>
-
-<B>Jarkko Sonninen</B>
-Copyright (C) 1993-1994
-He was the founder of the project, wrote the old version of the
-6502 emulation and the XDebugger, and retired from the project
-after x64 0.2.1.
-
-</UL>
-
-<P>
-Internationalization Team:
-
-</P>
-
-<UL>
-
-<LI>
-
-<B>Peter Krefting</B> provided the Swedish user interface translations.
-
-<B>Andrea Musuruane</B> provided the Italian user interface translations.
-
-<B>Czirkos Zoltan</B> and <B>Karai Csaba</B> provided the Hungarian user
-interface translations.
-
-<B>Emir Akaydin</B> provided the Turkish user interface translations (in world record time).
-
-<B>Mikkel Holm Olsen</B> provided the Danish user interface translations and fixed a few monitor bugs.
-
-<B>Paul Dub\xE9</B> from Rivi\xE8re-du-Loup, Qu\xE9bec, provided the French user interface
-translations.
-
-<B>Flooder</B> provided parts of the Polish user interface translations.
-
-</UL>
-
-<P>
-External contributors:
-
-</P>
-
-<UL>
-
-<LI>
-
-<B>Michael Schwendt</B> helped with the
-SID (audio) chip emulation, bringing important suggestions and bug
-reports, as well as the wave tables and filter emulation from his
-SIDplay emulator.
-
-<LI>
-
-<B>Christian Bauer</B> wrote
-the very interesting "VIC article" from which we got invaluable
-information about the VIC-II chip: without this, the VIC-II
-implementation would have not been possible.
-
-<LI>
-
-<B>Wolfgang Lorenz</B> wrote an excellent 6510 test suite that helped us
-to debug the CPU emulation.
-
-<LI>
-
-<B>Giuliano Procida</B> is the maintainer
-of the VICE <CODE>deb</CODE> package for the Debian distribution, and also
-helped proofreading the documentation.
-
-<LI>
-
-<B>Marko M\xE4kel\xE4</B> wrote lots of CPU documentation.
-
-<LI>
-
-<B>Chris Sharp</B> wrote the AIX sound driver.
-
-<LI>
-
-<B>Krister Walfridsson</B> implemented joystick and sound support for
-NetBSD.
-
-<LI>
-
-<B>Peter Andrew Felvegi aka Petschy</B>
-fixed a couple of bugs in the fast serial emulation.
-
-<LI>
-
-<B>Olaf Seibert</B> contributed some PET, and disk drive patches.
-
-<LI>
-
-<B>Daniel Fandrich</B> contributed some disk drive patches.
-
-<LI>
-
-<B>Heiko Selber</B> contributed some VIC20 I/O patches.
-
-<LI>
-
-<B>Steven Tieu</B> added initial support for 16/24 bpp X11 displays.
-
-<LI>
-
-<B>Alexander Lehmann</B> added complete support for all the VIC20 memory
-configurations for the old VICE 0.12.
-
-<LI>
-
-<B>Lionel Ulmer</B> implemented joystick support for Linux and a first
-try of a SID emulation for SGI machines.
-
-<LI>
-
-<B>Bernhard Kuhn</B> made some joystick improvements for Linux.
-
-<LI>
-
-<B>Gerhard Wesp</B> contributed the
-<CODE>extract</CODE> command in <CODE>c1541</CODE>.
-
-<LI>
-
-<B>Ricardo Ferreira</B> contributed the
-<CODE>unlynx</CODE> and <CODE>system</CODE> commands in <CODE>c1541</CODE> and added
-aRts sound support.
-
-<LI>
-
-<B>Tomi Ollila</B> donated <CODE>findpath.c</CODE>.
-
-<LI>
-
-<B>Richard Hable</B> contributed the initial version of the REU
-emulation.
-
-<LI>
-
-<B>Vesa-Matti Puro</B> wrote the very first 6502 CPU
-emulator in x64 0.1.0. That was the beginning of the story...
-
-<LI>
-
-<B>Dan Miner</B> contributed some patches to the fast disk drive
-emulation.
-
-<LI>
-
-<B>Frank Prindle</B> contributed some patches.
-
-<LI>
-
-<B>Peter Weighill</B> gave many ideas and contributed the ROM patcher.
-
-<LI>
-
-<B>Dominique Strigl</B>, <B>Craig Jackson</B> and <B>Lasse Jyrkinen</B>
-contributed miscellaneous patches in the old X64 times.
-
-<LI>
-
-<B>Per Olofsson</B> digitalized the C64 colors used in the (old) default
-palette.
-
-<LI>
-
-<B>Paul David Doherty</B> wrote
-<CODE>zip2disk</CODE>, on which the Zipcode support in <CODE>c1541</CODE> is based.
-
-<LI>
-
-<B>Robert H. Forsman Jr.</B>, <B>Brian Totty</B> and <B>Robert W. McMullen</B>
-provided the widget set for implementing the <CODE>Xaw</CODE> GUI.
-
-<LI>
-
-<B>Shawn Hargreaves</B> wrote
-Allegro, the graphics and audio library used in the MS-DOS version.
-
-<LI>
-
-<B>Peter Schepers</B> contributed a document describing the G64 image
-format.
-
-<LI>
-
-<B>Oliver Schaertel</B> wrote the X11 full screen, parts of custom ROM
-set support and 1351 mouse emulation for unix.
-
-<LI>
-
-<B>Luca Montecchiani</B> contributed a new Unix joystick driver.
-
-<LI>
-
-<B>Dirk Farin</B> rewrote the MITSHM code.
-
-<LI>
-
-<B>Manfred Spraul</B> wrote the MS-Windows text lister.
-
-<LI>
-
-<B>Peter Karlsson</B> provided the swedish UI translations.
-
-<LI>
-
-<B>Paul Dub\xE9</B> provided the french translation for the Unix ports.
-
-<LI>
-
-<B>Nathan Huizinga</B> added support for E...
[truncated message content] |
