devs/foxbox
1
0
Fork 0
forked from len0rd/rockbox
Code Pull requests Activity

fixed a typo, stripped trailing whitespace and made some small tweaks to the installation chapter

Browse source 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@11589 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
Nils Wallménius 2006-11-25 11:54:51 +00:00
parent 6b1d2cbd82
commit c35d3a1f1c
1 changed files with 146 additions and 146 deletions
Download patch file Download diff file Expand all files Collapse all files

12
manual/getting_started/installation.tex
View file

@ -84,9 +84,9 @@ software.
and load the remaining firmware from disk. It is also responsible for the
disk mode on your \dap{}.
This boot loader is stored in special flash memory in your \playerman. It is
already installed on your \dap{}, so it is never necessary to modify this
in order to install Rockbox.}
This boot loader is stored in special flash memory in your \playerman{}.
It is already installed on your \dap{}, so it is never necessary to modify
this in order to install Rockbox.}
\item[The Rockbox boot loader.] \index{Boot loader}
\opt{HAVE_RB_BL_ON_DISK}{The Rockbox boot loader is loaded from disk by
@ -168,7 +168,7 @@ you want to install and get the version for your \dap{}.
Because daily builds and CVS builds are development versions which change
frequently, they may behave differently than described in this manual, or
they may introduce new (and maybe annoying) bugs. If you do not want to get
undefined behaviour from your \dap\ you should really stick to the current
undefined behaviour from your \dap{} you should really stick to the current
stable release, if there is one for your \dap{}. If you want to help the
project development, you can try development builds and help by reporting
bugs. Just be aware that these are development builds that are highly
@ -180,7 +180,7 @@ you downloaded above, and extract its contents to your \daps{} drive.
Use the ``Extract all'' command of your unzip program to extract the files in
the \fname{.zip} file onto your \dap{}. Note that the entire contents of the
\fname{/zip} file should be extracted directly to the root of your \daps{}
\fname{.zip} file should be extracted directly to the root of your \daps{}
drive. Do not try to create a separate directory or folder on your \dap{} for
the Rockbox files! The \fname{.zip} file already contains the internal
directory structure that Rockbox needs.
@ -188,7 +188,7 @@ directory structure that Rockbox needs.
\note{
If the contents of the \fname{.zip} file are extracted correctly, you will
have a file called \fname{\firmwarefilename} in the main folder of your
\daps{} drive, and also a folder called /\fname{.rockbox}, which contains a
\daps{} drive, and also a folder called \fname{/.rockbox}, which contains a
number of other folders and system files needed by Rockbox. If you receive a
``-1'' error when you start Rockbox, you have not extracted the contents of
the \fname{.zip} file to the proper location.