summaryrefslogtreecommitdiff
path: root/manual/getting_started
diff options
context:
space:
mode:
Diffstat (limited to 'manual/getting_started')
-rwxr-xr-xmanual/getting_started/h10_install.tex6
-rw-r--r--manual/getting_started/installation.tex44
-rwxr-xr-xmanual/getting_started/ipod_install.tex8
-rw-r--r--manual/getting_started/iriver_install.tex40
-rw-r--r--manual/getting_started/main.tex12
5 files changed, 55 insertions, 55 deletions
diff --git a/manual/getting_started/h10_install.tex b/manual/getting_started/h10_install.tex
index cc804f008a..36a36d8ec4 100755
--- a/manual/getting_started/h10_install.tex
+++ b/manual/getting_started/h10_install.tex
@@ -4,7 +4,7 @@ The \playertype{} can be connected to a computer in two different modes:
4 \item Universal Mass Storage (UMS): In this mode, it will appear on your computer as a regular disk. This mode works with all major operating systems, including Windows, Linux and Mac OS X. 4 \item Universal Mass Storage (UMS): In this mode, it will appear on your computer as a regular disk. This mode works with all major operating systems, including Windows, Linux and Mac OS X.
5 \item Media Transfer Protocol (MTP): In this mode, it will appear on your computer as a Media Device. MTP was created by Microsoft for use with DAPs and only works with Windows XP and Media Player 10. 5 \item Media Transfer Protocol (MTP): In this mode, it will appear on your computer as a Media Device. MTP was created by Microsoft for use with DAPs and only works with Windows XP and Media Player 10.
6\end{itemize} 6\end{itemize}
7The \playerlongtype{} is \opt{h10}{only available as a MTP device, but}\opt{h10_5gb}{available as both a MTP and as a UMS device, depending on where and when you bought it. You can tell which you have by how it appears when you conect it to a computer. If it appears as a regular disk then it is UMS. If it appears as a Media Device on Windows XP, or if it doesn't appear at all on other operating systems, then it is MTP. Even if you have a MTP \dap{}, it} can be forced into UMS mode using the UMS trick. 7The \playerlongtype{} is \opt{h10}{only available as a MTP device, but}\opt{h10_5gb}{available as both a MTP and as a UMS device, depending on where and when you bought it. You can tell which you have by how it appears when you connect it to a computer. If it appears as a regular disk then it is UMS. If it appears as a Media Device on Windows XP, or if it doesn't appear at all on other operating systems, then it is MTP. Even if you have a MTP \dap{}, it} can be forced into UMS mode using the UMS trick.
8 8
9\subsubsection{UMS mode and the UMS trick} 9\subsubsection{UMS mode and the UMS trick}
10It is possible to force a MTP \playertype{} to start up in UMS mode using the following procedure: 10It is possible to force a MTP \playertype{} to start up in UMS mode using the following procedure:
@@ -28,9 +28,9 @@ It is possible to force a MTP \playertype{} to start up in UMS mode using the fo
28 \end{itemize}} 28 \end{itemize}}
29 \item Connect your \playertype{} to the computer using UMS mode and the UMS trick\opt{h10_5gb}{ if necessary}. 29 \item Connect your \playertype{} to the computer using UMS mode and the UMS trick\opt{h10_5gb}{ if necessary}.
30 \item Make a backup of the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file in the \fname{System} directory on your \playertype{}. 30 \item Make a backup of the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file in the \fname{System} directory on your \playertype{}.
31 \opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which doesn't have a FM radio) it is possible that this file will be called \fname{H10EMP.mi4} instead. If so, rename the \fname{H10.mi4} you downloade in step 1 to \fname{H10EMP.mi4}.}} 31 \opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which doesn't have a FM radio) it is possible that this file will be called \fname{H10EMP.mi4} instead. If so, rename the \fname{H10.mi4} you downloaded in step 1 to \fname{H10EMP.mi4}.}}
32 \note{You should keep a safe backup of this file for use if you ever wish to switch back to the \playerman{} firmware.} 32 \note{You should keep a safe backup of this file for use if you ever wish to switch back to the \playerman{} firmware.}
33 \note{If you can't see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and folers.} 33 \note{If you can't see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and folders.}
34 34
35 \item Copy the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4} (or \fname{H10EMP.mi4} if you have a \playertype{} Pure)} file you downloaded to the System directory on your \dap{}. 35 \item Copy the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4} (or \fname{H10EMP.mi4} if you have a \playertype{} Pure)} file you downloaded to the System directory on your \dap{}.
36\end{enumerate} 36\end{enumerate}
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex
index 946635c559..5a22d0b606 100644
--- a/manual/getting_started/installation.tex
+++ b/manual/getting_started/installation.tex
@@ -14,11 +14,11 @@ software.
14 Rockbox is distributed as an archive using the 14 Rockbox is distributed as an archive using the
15 \fname{.zip} format. Thus you need a tool to handle that compressed 15 \fname{.zip} format. Thus you need a tool to handle that compressed
16 format. Usually your computer should have a tool installed that can 16 format. Usually your computer should have a tool installed that can
17 handle the \fname{.zip} file format. Windows XP has builtin support for 17 handle the \fname{.zip} file format. Windows XP has built-in support for
18 \fname{.zip} files and presents them to you as folders unless you have 18 \fname{.zip} files and presents them to you as folders unless you have
19 installed a third party program that handles compressed files. For 19 installed a third party program that handles compressed files. For
20 other operating systems this may vary. If the \fname{.zip} file format 20 other operating systems this may vary. If the \fname{.zip} file format
21 is not recognized on your computer you can find a program to handle them 21 is not recognised on your computer you can find a program to handle them
22 at \url{http://www.info-zip.org/} or \url{http://sevenzip.sf.net/} which 22 at \url{http://www.info-zip.org/} or \url{http://sevenzip.sf.net/} which
23 can be downloaded and used free of charge. 23 can be downloaded and used free of charge.
24 24
@@ -30,7 +30,7 @@ software.
30 30
31 \opt{ipod}{ 31 \opt{ipod}{
32 \note{Your \dap{} should enter disk mode automatically when connected to a 32 \note{Your \dap{} should enter disk mode automatically when connected to a
33 computer via USB. If your computer does not recognize your \dap{}, you 33 computer via USB. If your computer does not recognise your \dap{}, you
34 may need to enter the disk mode manually. Disconnect your \dap{} from the 34 may need to enter the disk mode manually. Disconnect your \dap{} from the
35 computer. Reset the \dap{} by pressing and holding the \ButtonMenu{} and 35 computer. Reset the \dap{} by pressing and holding the \ButtonMenu{} and
36 \ButtonSelect{} buttons simultaneously. As soon as the \dap{} resets, 36 \ButtonSelect{} buttons simultaneously. As soon as the \dap{} resets,
@@ -42,7 +42,7 @@ software.
42 42
43\item[Text editor.] As you will see in the following chapters, Rockbox is 43\item[Text editor.] As you will see in the following chapters, Rockbox is
44 highly configurable. In addition to saving configurations within Rockbox, 44 highly configurable. In addition to saving configurations within Rockbox,
45 Rockbox also allows you to create customized configuration files. If you 45 Rockbox also allows you to create customised configuration files. If you
46 would like to edit custom configuration files on your computer, you will 46 would like to edit custom configuration files on your computer, you will
47 need a text editor like Windows' ``Wordpad''. 47 need a text editor like Windows' ``Wordpad''.
48 48
@@ -75,22 +75,22 @@ software.
75 75
76 \begin{description} 76 \begin{description}
77 \opt{HAVE_RB_BL_ON_DISK}{ 77 \opt{HAVE_RB_BL_ON_DISK}{
78 \item[The \playerman{} bootloader.] 78 \item[The \playerman{} boot loader.]
79 The \playerman{} bootloader is the program that tells your \dap{} how to boot 79 The \playerman{} boot loader is the program that tells your \dap{} how to boot
80 and load the remaining firmware from disk. It is also responsible for the 80 and load the remaining firmware from disk. It is also responsible for the
81 disk mode on your \dap{}. 81 disk mode on your \dap{}.
82 82
83 This bootloader is stored in special flash memory in your \playerman. It is 83 This boot loader is stored in special flash memory in your \playerman. It is
84 already installed on your \dap{}, so it is never necessary to modify this 84 already installed on your \dap{}, so it is never necessary to modify this
85 in order to install Rockbox.} 85 in order to install Rockbox.}
86 86
87 \item[The Rockbox bootloader.] \index{Bootloader} 87 \item[The Rockbox boot loader.] \index{Boot loader}
88 \opt{HAVE_RB_BL_ON_DISK}{The Rockbox bootloader is loaded from disk by 88 \opt{HAVE_RB_BL_ON_DISK}{The Rockbox boot loader is loaded from disk by
89 the \playerman{} bootloader. It is responsible for loading the Rockbox 89 the \playerman{} boot loader. It is responsible for loading the Rockbox
90 firmware and for providing the dual boot function. It directly replaces the 90 firmware and for providing the dual boot function. It directly replaces the
91 \playerman{} firmware on the \daps{} disk.} 91 \playerman{} firmware on the \daps{} disk.}
92 \opt{HAVE_RB_BL_IN_FLASH}{ 92 \opt{HAVE_RB_BL_IN_FLASH}{
93 The bootloader is the program that tells your 93 The boot loader is the program that tells your
94 \dap{} how to boot and load other components of Rockbox. This is the 94 \dap{} how to boot and load other components of Rockbox. This is the
95 component of Rockbox that is installed to the flash memory of your 95 component of Rockbox that is installed to the flash memory of your
96 \playerman.} 96 \playerman.}
@@ -107,14 +107,14 @@ software.
107 107
108 \end{description} 108 \end{description}
109 109
110 \subsection{Installing the bootloader} 110 \subsection{Installing the boot loader}
111 \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}} 111 \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}}
112 \opt{ipod}{\input{getting_started/ipod_install.tex}} 112 \opt{ipod}{\input{getting_started/ipod_install.tex}}
113 \opt{x5}{\input{getting_started/iaudio_install.tex}} 113 \opt{x5}{\input{getting_started/iaudio_install.tex}}
114 \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}} 114 \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}}
115 115
116 \subsection{Installing the firmware} 116 \subsection{Installing the firmware}
117 After installing the bootloader, the installation becomes fairly easy. 117 After installing the boot loader, the installation becomes fairly easy.
118} 118}
119 119
120There are three different types of firmware binaries from Rockbox website: 120There are three different types of firmware binaries from Rockbox website:
@@ -217,7 +217,7 @@ use.
217 your player using Itunes, you will not be able to see your music because 217 your player using Itunes, you will not be able to see your music because
218 Itunes changes your files' names and hides them in directories in the 218 Itunes changes your files' names and hides them in directories in the
219 \fname{Ipod\_Control} folder. You can view files placed on your \dap{} by 219 \fname{Ipod\_Control} folder. You can view files placed on your \dap{} by
220 Itunes by initializing and using Rockbox's Tag Cache. See 220 Itunes by initialising and using Rockbox's Tag Cache. See
221 \reference{ref:tagcache} for more information. 221 \reference{ref:tagcache} for more information.
222 } 222 }
223} 223}
@@ -252,7 +252,7 @@ connect the \playerman{} to your computer, and delete the
252\optv{ipod}{ 252\optv{ipod}{
253 Next, open a command window (Windows) or a terminal window (Mac or Linux). 253 Next, open a command window (Windows) or a terminal window (Mac or Linux).
254 Navigate to the folder you created when you downloaded the 254 Navigate to the folder you created when you downloaded the
255 \fname{ipodpatcher} program you used to install the Rockbox bootloader. 255 \fname{ipodpatcher} program you used to install the Rockbox boot loader.
256 Type the following command: 256 Type the following command:
257 257
258 \begin{code} 258 \begin{code}
@@ -272,24 +272,24 @@ Turn the \dap{} back on and the original \playerman{} software will load.
272 272
273\opt{h1xx}{ 273\opt{h1xx}{
274 \note{ 274 \note{
275 There's no need to remove the installed bootloader. If you want to remove 275 There's no need to remove the installed boot loader. If you want to remove
276 it, simply flash an unpatched \playerman{} firmware. Be aware that doing so 276 it, simply flash an unpatched \playerman{} firmware. Be aware that doing so
277 will also remove the bootloader USB mode. As that mode can come in quite 277 will also remove the boot loader USB mode. As that mode can come in quite
278 handy (especially when having disk errors) it is recommended to keep the 278 handy (especially when having disk errors) it is recommended to keep the
279 bootloader. It also gives you the possibility of trying Rockbox anytime 279 boot loader. It also gives you the possibility of trying Rockbox anytime
280 later by simply installing the distribution files. 280 later by simply installing the distribution files.
281 } 281 }
282} 282}
283 283
284\opt{h300}{ 284\opt{h300}{
285 \note{ 285 \note{
286 There's no need to remove the installed bootloader, although you if you 286 There's no need to remove the installed boot loader, although you if you
287 retain the Rockbox bootloader, you will need to hold the \ButtonRec{} 287 retain the Rockbox boot loader, you will need to hold the \ButtonRec{}
288 button each time you want to start the original firmware. If you want to 288 button each time you want to start the original firmware. If you want to
289 remove it simply flash an unpatched \playerman{} firmware. Be aware that 289 remove it simply flash an unpatched \playerman{} firmware. Be aware that
290 doing so will also remove the bootloader USB mode. As that mode can come in 290 doing so will also remove the boot loader USB mode. As that mode can come in
291 quite handy (especially when having disk errors), you may wish to keep the 291 quite handy (especially when having disk errors), you may wish to keep the
292 bootloader. It also gives you the possibility of trying Rockbox anytime 292 boot loader. It also gives you the possibility of trying Rockbox anytime
293 later by simply installing a new build. 293 later by simply installing a new build.
294 } 294 }
295} 295}
diff --git a/manual/getting_started/ipod_install.tex b/manual/getting_started/ipod_install.tex
index a50519db8e..040532b950 100755
--- a/manual/getting_started/ipod_install.tex
+++ b/manual/getting_started/ipod_install.tex
@@ -5,7 +5,7 @@ Please check the wiki for up-to-date and improved installation instructions!
5If you find errors you're of course welcomed to report them so we can fix it 5If you find errors you're of course welcomed to report them so we can fix it
6for the next daily builds.} 6for the next daily builds.}
7 7
8 Installing the bootloader is the trickiest part of the installation. 8 Installing the boot loader is the trickiest part of the installation.
9 \opt{ipodnano}{First, you need to find out which version of the Apple 9 \opt{ipodnano}{First, you need to find out which version of the Apple
10 firmware you're running. To do this, start the Apple firmware and go to 10 firmware you're running. To do this, start the Apple firmware and go to
11 Settings screen. In the ``About'' screen you'll find the version number 11 Settings screen. In the ``About'' screen you'll find the version number
@@ -87,7 +87,7 @@ for the next daily builds.}
87 ipodpatcher -r \emph{N} bootpartition.bin 87 ipodpatcher -r \emph{N} bootpartition.bin
88 \end{code} 88 \end{code}
89 \note{You should keep a safe backup of this \fname{bootpartition.bin} file 89 \note{You should keep a safe backup of this \fname{bootpartition.bin} file
90 for use if you ever wish to either upgrade the Rockbox bootloader or 90 for use if you ever wish to either upgrade the Rockbox boot loader or
91 uninstall Rockbox from your Ipod} 91 uninstall Rockbox from your Ipod}
92 \item Extract the Apple firmware from the partition image image just created: 92 \item Extract the Apple firmware from the partition image image just created:
93 \begin{code} 93 \begin{code}
@@ -102,7 +102,7 @@ for the next daily builds.}
102 ipod_fw -o apple_sw_5g_rcsc.bin -e 1 bootpartition.bin 102 ipod_fw -o apple_sw_5g_rcsc.bin -e 1 bootpartition.bin
103 \end{code} 103 \end{code}
104} 104}
105 \item Merge the Rockbox bootloader you downloaded previously with the Apple 105 \item Merge the Rockbox boot loader you downloaded previously with the Apple
106 firm\-ware.% 106 firm\-ware.%
107\optv{ipodnano}{ 107\optv{ipodnano}{
108 If your firmware version is lower than 1.2 this works you need 108 If your firmware version is lower than 1.2 this works you need
@@ -265,7 +265,7 @@ Now, proceed with installing the firmware itself.
265 \item \url{http://www.rockbox.org/viewcvs.cgi/*checkout*/tools/ipod_fw.c} 265 \item \url{http://www.rockbox.org/viewcvs.cgi/*checkout*/tools/ipod_fw.c}
266 \end{itemize} 266 \end{itemize}
267 Now compile it to an executable by opening a command prompt and changing 267 Now compile it to an executable by opening a command prompt and changing
268 to the folder created previously. Thn run the following command: 268 to the folder created previously. Then run the following command:
269 \begin{code} 269 \begin{code}
270 gcc -o ipod_fw ipod_fw.c 270 gcc -o ipod_fw ipod_fw.c
271 \end{code} 271 \end{code}
diff --git a/manual/getting_started/iriver_install.tex b/manual/getting_started/iriver_install.tex
index fb950a23dd..0cb59492e8 100644
--- a/manual/getting_started/iriver_install.tex
+++ b/manual/getting_started/iriver_install.tex
@@ -1,11 +1,11 @@
1% $Id$ % 1% $Id$ %
2 2
3 Installing the bootloader is the trickiest part of the installation. 3 Installing the boot loader is the trickiest part of the installation.
4 The Rockbox bootloader allows users to boot into either the Rockbox 4 The Rockbox boot loader allows users to boot into either the Rockbox
5 firmware or the iriver firmware. For legal reasons, we cannot distribute 5 firmware or the \playerman{} firmware. For legal reasons, we cannot distribute
6 the bootloader. Instead, we have developed a program that will patch the 6 the boot loader. Instead, we have developed a program that will patch the
7 Iriver firmware with the Rockbox bootloader. These instructions will explain 7 Iriver firmware with the Rockbox boot loader. These instructions will explain
8 how to download and patch the Iriver firmware with the Rockbox bootloader 8 how to download and patch the Iriver firmware with the Rockbox boot loader
9 and install it on your jukebox. 9 and install it on your jukebox.
10 10
11 11
@@ -22,7 +22,7 @@
22 your player.} 22 your player.}
23 \opt{IRIVER_H300_PAD}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU. 23 \opt{IRIVER_H300_PAD}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU.
24 \note{The US H3xx firmware is not currently supported and cannot be 24 \note{The US H3xx firmware is not currently supported and cannot be
25 patched to be used with the bootloader. If you wish to install Rockbox 25 patched to be used with the boot loader. If you wish to install Rockbox
26 on a US \playername, you must use an international firmware, which will 26 on a US \playername, you must use an international firmware, which will
27 permanently remove DRM support from the player.} 27 permanently remove DRM support from the player.}
28 }% 28 }%
@@ -32,7 +32,7 @@
32 to your desktop. Likewise, if the file that you downloaded is an 32 to your desktop. Likewise, if the file that you downloaded is an
33 \fname{.exe} file, double-click on the \fname{.exe} file to extract 33 \fname{.exe} file, double-click on the \fname{.exe} file to extract
34 the \fname{.hex} file to your desktop. 34 the \fname{.hex} file to your desktop.
35 When running linux you should be able extracting \fname{.exe} 35 When running Linux you should be able extracting \fname{.exe}
36 files using \fname{unzip}. 36 files using \fname{unzip}.
37 % 37 %
38 \item Download the firmware patcher \fname{fwpatcher.exe} from 38 \item Download the firmware patcher \fname{fwpatcher.exe} from
@@ -50,7 +50,7 @@
50 to the \fname{.hex} file that you previously downloaded to your desktop. 50 to the \fname{.hex} file that you previously downloaded to your desktop.
51 % 51 %
52 \item Click \setting{Patch}. The firmware patcher will patch the 52 \item Click \setting{Patch}. The firmware patcher will patch the
53 original firmware to include the Rockbox bootloader. The \fname{.hex} 53 original firmware to include the Rockbox boot loader. The \fname{.hex}
54 file on your desktop is now a modified version of the original 54 file on your desktop is now a modified version of the original
55 \fname{.hex} file. 55 \fname{.hex} file.
56 % 56 %
@@ -65,7 +65,7 @@
65 or that it is connected to the power adaptor. Interrupting the next step 65 or that it is connected to the power adaptor. Interrupting the next step
66 due to a power failure most likely will brick your \dap{}.} 66 due to a power failure most likely will brick your \dap{}.}
67 % 67 %
68 \item Update your \daps{} firmware with the patched bootloader. To do this, turn 68 \item Update your \daps{} firmware with the patched boot loader. To do this, turn
69 the jukebox on. Press and hold the 69 the jukebox on. Press and hold the
70 \opt{IRIVER_H100_PAD,IRIVER_H300_PAD}{\ButtonSelect{} button }% 70 \opt{IRIVER_H100_PAD,IRIVER_H300_PAD}{\ButtonSelect{} button }%
71 to enter the main menu, and navigate to \setting{General $\rightarrow$ Firmware 71 to enter the main menu, and navigate to \setting{General $\rightarrow$ Firmware
@@ -76,24 +76,24 @@
76 firmware update is complete the player will turn itself off. (The update 76 firmware update is complete the player will turn itself off. (The update
77 firmware process usually takes a minute or so.) 77 firmware process usually takes a minute or so.)
78 78
79 You have now installed the Rockbox bootloader. 79 You have now installed the Rockbox boot loader.
80\end{enumerate} 80\end{enumerate}
81 81
82\note{If you install the Rockbox bootloader but do not install the 82\note{If you install the Rockbox boot loader but do not install the
83 Rockbox firmware the Rockbox bootloader will load the iriver firmware when the 83 Rockbox firmware the Rockbox boot loader will load the Iriver firmware when the
84 jukebox is turned on. 84 jukebox is turned on.
85 To load the \playerman{} firmware press and hold \ButtonRec{} before 85 To load the \playerman{} firmware press and hold \ButtonRec{} before
86 powering up the \dap{} until the \playerman{} logo appears. 86 powering up the \dap{} until the \playerman{} logo appears.
87 } 87 }
88 88
89\note{The bootloader has a builtin ``bootloader USB mode''. This function 89\note{The boot loader has a built-in ``boot loader USB mode''. This function
90 switches to USB mode when the \dap{} is connected to a computer upon 90 switches to USB mode when the \dap{} is connected to a computer upon
91 power-up. This way you can access the \daps{} harddisk without the need 91 power-up. This way you can access the \daps{} hard disk without the need
92 to boot any firmware (which is also useful when your harddisk is 92 to boot any firmware (which is also useful when your hard disk is
93 damaged). The screen will simply display the text ``bootloader USB mode''. 93 damaged). The screen will simply display the text ``boot loader USB mode''.
94 After you disconnect the \dap{} from USB the bootloader will 94 After you disconnect the \dap{} from USB the boot loader will
95 continue booting Rockbox. As in bootloader USB mode the firmware 95 continue booting Rockbox. As in boot loader USB mode the firmware
96 itself hasn't been loaded this is also a simple way of updating Rockbox. 96 itself hasn't been loaded this is also a simple way of updating Rockbox.
97 After the disconnect the bootloader will load the updated version of 97 After the disconnect the boot loader will load the updated version of
98 Rockbox. 98 Rockbox.
99} 99}
diff --git a/manual/getting_started/main.tex b/manual/getting_started/main.tex
index 0e930ff1a6..d85f4c4894 100644
--- a/manual/getting_started/main.tex
+++ b/manual/getting_started/main.tex
@@ -4,14 +4,14 @@
4This is the manual for Rockbox. Rockbox is an open source firmware replacement 4This is the manual for Rockbox. Rockbox is an open source firmware replacement
5for a growing number of MP3 players. Rockbox aims to be considerably more 5for a growing number of MP3 players. Rockbox aims to be considerably more
6functional and efficient than your device's stock firmware while remaining easy 6functional and efficient than your device's stock firmware while remaining easy
7to use and customizable. Rockbox is written by users, for users. Not only is it 7to use and customisable. Rockbox is written by users, for users. Not only is it
8free to use, it's also released under the GNU public license, which means that 8free to use, it's also released under the GNU public license, which means that
9it will always remain free both to use and to change. 9it will always remain free both to use and to change.
10 10
11Rockbox has been in development since 2001, and recieves new features, tweaks 11Rockbox has been in development since 2001, and receives new features, tweaks
12and fixes each day to provide you with the best possible experience on your MP3 12and fixes each day to provide you with the best possible experience on your MP3
13player. A major goal of Rockbox is to be simple and easy to use, yet remain very 13player. A major goal of Rockbox is to be simple and easy to use, yet remain very
14customizable and configurable. We believe that you should never need to go 14customisable and configurable. We believe that you should never need to go
15through a series of menus for an action you perform frequently. We also believe 15through a series of menus for an action you perform frequently. We also believe
16that you should be able to configure almost anything about Rockbox you could 16that you should be able to configure almost anything about Rockbox you could
17want, pertaining to functionality. Another top priority of Rockbox is audio 17want, pertaining to functionality. Another top priority of Rockbox is audio
@@ -32,14 +32,14 @@ firmware. There is, however, more help available. The Rockbox website at
32written by members of the Rockbox community and this should be your first port 32written by members of the Rockbox community and this should be your first port
33of call when looking for further help. 33of call when looking for further help.
34 34
35If you can't find the informations you're searching for on the Rockbox 35If you can't find the information you're searching for on the Rockbox
36website there are a number of support channels you should have a look at. 36website there are a number of support channels you should have a look at.
37You can try the Rockbox forums located at \url{http://forums.rockbox.org/}. 37You can try the Rockbox forums located at \url{http://forums.rockbox.org/}.
38Another option are the mailing lists which can be found at 38Another option are the mailing lists which can be found at
39\url{http://www.rockbox.org/mail/}. From that page you can subscribe to the 39\url{http://www.rockbox.org/mail/}. From that page you can subscribe to the
40lists and browse the archives. For searching the list archives simply use 40lists and browse the archives. For searching the list archives simply use
41the search field that is located on the left side of the web site. 41the search field that is located on the left side of the web site.
42Also you can ask on IRC. The main channel for rockbox is \texttt{\#rockbox} 42Also you can ask on IRC. The main channel for Rockbox is \texttt{\#rockbox}
43on \url{irc://irc.freenode.net}. A bunch of helpful developers and users 43on \url{irc://irc.freenode.net}. A bunch of helpful developers and users
44are usually around. Just join and ask -- if someone knows the answer you'll 44are usually around. Just join and ask -- if someone knows the answer you'll
45usually get an answer pretty quickly. More information including IRC logs 45usually get an answer pretty quickly. More information including IRC logs
@@ -70,7 +70,7 @@ you finding important parts or parts you could skip. The following icons
70are used: 70are used:
71\note{This indicates a note. A note starts always with the text ``Note''. 71\note{This indicates a note. A note starts always with the text ``Note''.
72 For easier finding of notes we have put this an icon in the margin like 72 For easier finding of notes we have put this an icon in the margin like
73 here. Notes are used to mark informations that could help you 73 here. Notes are used to mark information that could help you
74 or indicate a possible ``weirdness'' in rockbox that would be explained. 74 or indicate a possible ``weirdness'' in rockbox that would be explained.
75} 75}
76\warn{This is a warning. In contrast to notes mentioned above, a warning 76\warn{This is a warning. In contrast to notes mentioned above, a warning