diff options
Diffstat (limited to 'manual')
-rw-r--r-- | manual/getting_started/installation.tex | 292 |
1 files changed, 146 insertions, 146 deletions
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex index 0af9ccfe05..4accc0658d 100644 --- a/manual/getting_started/installation.tex +++ b/manual/getting_started/installation.tex | |||
@@ -9,45 +9,45 @@ already available on your computer but if not you need to get some additional | |||
9 | software. | 9 | software. |
10 | 10 | ||
11 | \begin{description} | 11 | \begin{description} |
12 | 12 | ||
13 | \item[ZIP utility.]\index{zip} | 13 | \item[ZIP utility.]\index{zip} |
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 built-in 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 recognised 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 | ||
25 | \item[USB connection.] To transfer Rockbox to your \dap{} you need to | 25 | \item[USB connection.] To transfer Rockbox to your \dap{} you need to |
26 | connect it to your computer. To proceed you need to know where to access the | 26 | connect it to your computer. To proceed you need to know where to access the |
27 | \dap{}. On Windows this means you need to figure out the drive letter | 27 | \dap{}. On Windows this means you need to figure out the drive letter |
28 | associated with the device. On Linux you need to know the mount point of | 28 | associated with the device. On Linux you need to know the mount point of |
29 | your \dap{}. | 29 | your \dap{}. |
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 recognise 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, |
37 | press and hold the \ButtonMenu{} and \ButtonPlay{} buttons | 37 | press and hold the \ButtonMenu{} and \ButtonPlay{} buttons |
38 | simultaneously. Your \dap{} should enter disk mode, and you can try | 38 | simultaneously. Your \dap{} should enter disk mode, and you can try |
39 | reconnecting to the computer. | 39 | reconnecting to the computer. |
40 | } | 40 | } |
41 | \opt{ipod3g,ipod4g,ipodcolor,ipodmini}{ | 41 | \opt{ipod3g,ipod4g,ipodcolor,ipodmini}{ |
42 | \note{\index{Firewire}Firewire detection is not supported in Rockbox at | 42 | \note{\index{Firewire}Firewire detection is not supported in Rockbox at |
43 | the moment. Please use USB only.} | 43 | the moment. Please use USB only.} |
44 | } | 44 | } |
45 | } | 45 | } |
46 | 46 | ||
47 | \item[Text editor.] As you will see in the following chapters, Rockbox is | 47 | \item[Text editor.] As you will see in the following chapters, Rockbox is |
48 | highly configurable. In addition to saving configurations within Rockbox, | 48 | highly configurable. In addition to saving configurations within Rockbox, |
49 | Rockbox also allows you to create customised configuration files. If you | 49 | Rockbox also allows you to create customised configuration files. If you |
50 | would like to edit custom configuration files on your computer, you will | 50 | would like to edit custom configuration files on your computer, you will |
51 | need a text editor like Windows' ``Wordpad''. | 51 | need a text editor like Windows' ``Wordpad''. |
52 | 52 | ||
53 | \end{description} | 53 | \end{description} |
@@ -57,153 +57,153 @@ software. | |||
57 | \index{Installation} | 57 | \index{Installation} |
58 | \opt{MASCODEC}{ | 58 | \opt{MASCODEC}{ |
59 | \subsection{Using the windows installer} | 59 | \subsection{Using the windows installer} |
60 | Using the Windows self installing executable to install Rockbox is the | 60 | Using the Windows self installing executable to install Rockbox is the |
61 | easiest method of installing the software on your \dap{}. Simply follow the | 61 | easiest method of installing the software on your \dap{}. Simply follow the |
62 | on-screen instructions and select the appropriate drive letter and | 62 | on-screen instructions and select the appropriate drive letter and |
63 | \dap{}-model when prompted. You can use ``Add / Remove Programs'' to | 63 | \dap{}-model when prompted. You can use ``Add / Remove Programs'' to |
64 | uninstall the software at a later date. | 64 | uninstall the software at a later date. |
65 | 65 | ||
66 | \subsection{Manual installation} | 66 | \subsection{Manual installation} |
67 | For non{}-Windows users and those wishing to install manually from the | 67 | For non{}-Windows users and those wishing to install manually from the |
68 | archive the procedure is still fairly simple. | 68 | archive the procedure is still fairly simple. |
69 | } | 69 | } |
70 | 70 | ||
71 | \opt{SWCODEC}{ | 71 | \opt{SWCODEC}{ |
72 | \subsection{Introduction} | 72 | \subsection{Introduction} |
73 | 73 | ||
74 | \opt{HAVE_RB_BL_ON_DISK}{There are three separate components of Rockbox, | 74 | \opt{HAVE_RB_BL_ON_DISK}{There are three separate components of Rockbox, |
75 | two of which need to be installed in order to run Rockbox.} | 75 | two of which need to be installed in order to run Rockbox.} |
76 | 76 | ||
77 | \opt{HAVE_RB_BL_IN_FLASH}{There are two separate components of Rockbox | 77 | \opt{HAVE_RB_BL_IN_FLASH}{There are two separate components of Rockbox |
78 | that need to be installed in order to run Rockbox.} | 78 | that need to be installed in order to run Rockbox.} |
79 | 79 | ||
80 | \begin{description} | 80 | \begin{description} |
81 | \opt{HAVE_RB_BL_ON_DISK}{ | 81 | \opt{HAVE_RB_BL_ON_DISK}{ |
82 | \item[The \playerman{} boot loader.] | 82 | \item[The \playerman{} boot loader.] |
83 | The \playerman{} boot loader is the program that tells your \dap{} how to boot | 83 | The \playerman{} boot loader is the program that tells your \dap{} how to boot |
84 | and load the remaining firmware from disk. It is also responsible for the | 84 | and load the remaining firmware from disk. It is also responsible for the |
85 | disk mode on your \dap{}. | 85 | disk mode on your \dap{}. |
86 | 86 | ||
87 | This boot loader is stored in special flash memory in your \playerman. It is | 87 | This boot loader is stored in special flash memory in your \playerman{}. |
88 | already installed on your \dap{}, so it is never necessary to modify this | 88 | It is already installed on your \dap{}, so it is never necessary to modify |
89 | in order to install Rockbox.} | 89 | this in order to install Rockbox.} |
90 | 90 | ||
91 | \item[The Rockbox boot loader.] \index{Boot loader} | 91 | \item[The Rockbox boot loader.] \index{Boot loader} |
92 | \opt{HAVE_RB_BL_ON_DISK}{The Rockbox boot loader is loaded from disk by | 92 | \opt{HAVE_RB_BL_ON_DISK}{The Rockbox boot loader is loaded from disk by |
93 | the \playerman{} boot loader. It is responsible for loading the Rockbox | 93 | the \playerman{} boot loader. It is responsible for loading the Rockbox |
94 | firmware and for providing the dual boot function. It directly replaces the | 94 | firmware and for providing the dual boot function. It directly replaces the |
95 | \playerman{} firmware on the \daps{} disk.} | 95 | \playerman{} firmware on the \daps{} disk.} |
96 | \opt{HAVE_RB_BL_IN_FLASH}{ | 96 | \opt{HAVE_RB_BL_IN_FLASH}{ |
97 | The boot loader is the program that tells your | 97 | The boot loader is the program that tells your |
98 | \dap{} how to boot and load other components of Rockbox. This is the | 98 | \dap{} how to boot and load other components of Rockbox. This is the |
99 | component of Rockbox that is installed to the flash memory of your | 99 | component of Rockbox that is installed to the flash memory of your |
100 | \playerman.} | 100 | \playerman.} |
101 | 101 | ||
102 | \item[The Rockbox firmware.] | 102 | \item[The Rockbox firmware.] |
103 | \opt{HAVE_RB_BL_IN_FLASH}{Unlike the \playerman{} firmware, which runs | 103 | \opt{HAVE_RB_BL_IN_FLASH}{Unlike the \playerman{} firmware, which runs |
104 | entirely from flash memory, } | 104 | entirely from flash memory, } |
105 | \opt{HAVE_RB_BL_ON_DISK}{Similar to the \playerman{} firmware, } | 105 | \opt{HAVE_RB_BL_ON_DISK}{Similar to the \playerman{} firmware, } |
106 | most of the Rockbox code is contained in a | 106 | most of the Rockbox code is contained in a |
107 | ``build'' that resides on your \daps{} hard drive. This makes it easy to | 107 | ``build'' that resides on your \daps{} hard drive. This makes it easy to |
108 | update Rockbox. The build consists of a file named \firmwarefilename{} and a | 108 | update Rockbox. The build consists of a file named \firmwarefilename{} and a |
109 | directory called \fname{.rockbox}, both of which are located in the root | 109 | directory called \fname{.rockbox}, both of which are located in the root |
110 | directory of your hard drive. | 110 | directory of your hard drive. |
111 | 111 | ||
112 | \end{description} | 112 | \end{description} |
113 | 113 | ||
114 | \subsection{Installing the boot loader} | 114 | \subsection{Installing the boot loader} |
115 | \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}} | 115 | \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}} |
116 | \opt{ipod}{\input{getting_started/ipod_install.tex}} | 116 | \opt{ipod}{\input{getting_started/ipod_install.tex}} |
117 | \opt{x5}{\input{getting_started/iaudio_install.tex}} | 117 | \opt{x5}{\input{getting_started/iaudio_install.tex}} |
118 | \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}} | 118 | \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}} |
119 | 119 | ||
120 | \subsection{Installing the firmware} | 120 | \subsection{Installing the firmware} |
121 | After installing the boot loader, the installation becomes fairly easy. | 121 | After installing the boot loader, the installation becomes fairly easy. |
122 | } | 122 | } |
123 | 123 | ||
124 | There are three different types of firmware binaries from Rockbox website: | 124 | There are three different types of firmware binaries from Rockbox website: |
125 | \label{Version} | 125 | \label{Version} |
126 | current version, daily build and CVS build. You need to decide which one | 126 | current version, daily build and CVS build. You need to decide which one |
127 | you want to install and get the version for your \dap{}. | 127 | you want to install and get the version for your \dap{}. |
128 | 128 | ||
129 | \begin{description} | 129 | \begin{description} |
130 | 130 | ||
131 | \item[Current Version.] The current version is the latest stable release, free | 131 | \item[Current Version.] The current version is the latest stable release, free |
132 | of known critical bugs. The current stable release of Rockbox, version 2.5, | 132 | of known critical bugs. The current stable release of Rockbox, version 2.5, |
133 | is available at \url{http://www.rockbox.org/download/}. | 133 | is available at \url{http://www.rockbox.org/download/}. |
134 | \opt{SWCODEC}{ | 134 | \opt{SWCODEC}{ |
135 | \note{The current stable release is available only for Archos jukeboxes. | 135 | \note{The current stable release is available only for Archos jukeboxes. |
136 | There has not yet been a stable release for the \playername{}. Until | 136 | There has not yet been a stable release for the \playername{}. Until |
137 | there is a stable release for \playername{}, use a daily build or CVS | 137 | there is a stable release for \playername{}, use a daily build or CVS |
138 | build. | 138 | build. |
139 | } | 139 | } |
140 | } | 140 | } |
141 | 141 | ||
142 | \item[Daily Build.] The daily build is a development version of Rockbox. It | 142 | \item[Daily Build.] The daily build is a development version of Rockbox. It |
143 | contains features and patches developed since last stable version. It | 143 | contains features and patches developed since last stable version. It |
144 | may also contain bugs! This daily build is generated automatically every day | 144 | may also contain bugs! This daily build is generated automatically every day |
145 | and can be found at \url{http://www.rockbox.org/daily.shtml}. | 145 | and can be found at \url{http://www.rockbox.org/daily.shtml}. |
146 | 146 | ||
147 | \item[CVS Build (formerly, ``Bleeding Edge Build.'')] CVS stands for | 147 | \item[CVS Build (formerly, ``Bleeding Edge Build.'')] CVS stands for |
148 | ``Concurrent Versions System.'' CVS is the system that Rockbox | 148 | ``Concurrent Versions System.'' CVS is the system that Rockbox |
149 | developers use to keep track of changes to the Rockbox source code. CVS | 149 | developers use to keep track of changes to the Rockbox source code. CVS |
150 | builds are made automatically every time there is a change to the | 150 | builds are made automatically every time there is a change to the |
151 | Rockbox source. These builds are for people who want to test the code | 151 | Rockbox source. These builds are for people who want to test the code |
152 | that developers just checked in. | 152 | that developers just checked in. |
153 | 153 | ||
154 | \end{description} | 154 | \end{description} |
155 | 155 | ||
156 | \nopt{player}{ | 156 | \nopt{player}{ |
157 | \note{\index{Installation!Fonts} | 157 | \note{\index{Installation!Fonts} |
158 | Rockbox has a fonts package that is available at | 158 | Rockbox has a fonts package that is available at |
159 | \url{http://www.rockbox.org/daily.shtml}. While the daily builds and CVS | 159 | \url{http://www.rockbox.org/daily.shtml}. While the daily builds and CVS |
160 | builds change frequently, the fonts package rarely changes. Thus, the | 160 | builds change frequently, the fonts package rarely changes. Thus, the |
161 | fonts package is not included in the daily builds and CVS builds. (The | 161 | fonts package is not included in the daily builds and CVS builds. (The |
162 | stable release, on the other hand, does not change, so fonts are | 162 | stable release, on the other hand, does not change, so fonts are |
163 | included with the stable release.) When installing Rockbox for the | 163 | included with the stable release.) When installing Rockbox for the |
164 | first time, you should install the fonts package. | 164 | first time, you should install the fonts package. |
165 | } | 165 | } |
166 | } | 166 | } |
167 | 167 | ||
168 | Because daily builds and CVS builds are development versions which change | 168 | Because daily builds and CVS builds are development versions which change |
169 | frequently, they may behave differently than described in this manual, or | 169 | frequently, they may behave differently than described in this manual, or |
170 | they may introduce new (and maybe annoying) bugs. If you do not want to get | 170 | they may introduce new (and maybe annoying) bugs. If you do not want to get |
171 | undefined behaviour from your \dap\ you should really stick to the current | 171 | undefined behaviour from your \dap{} you should really stick to the current |
172 | stable release, if there is one for your \dap{}. If you want to help the | 172 | stable release, if there is one for your \dap{}. If you want to help the |
173 | project development, you can try development builds and help by reporting | 173 | project development, you can try development builds and help by reporting |
174 | bugs. Just be aware that these are development builds that are highly | 174 | bugs. Just be aware that these are development builds that are highly |
175 | functional, but not perfect! | 175 | functional, but not perfect! |
176 | 176 | ||
177 | After downloading the Rockbox package connect your \dap{} to the computer via | 177 | After downloading the Rockbox package connect your \dap{} to the computer via |
178 | USB as described in the manual that came with your \dap{}. Take the file that | 178 | USB as described in the manual that came with your \dap{}. Take the file that |
179 | you downloaded above, and extract its contents to your \daps{} drive. | 179 | you downloaded above, and extract its contents to your \daps{} drive. |
180 | 180 | ||
181 | Use the ``Extract all'' command of your unzip program to extract the files in | 181 | Use the ``Extract all'' command of your unzip program to extract the files in |
182 | the \fname{.zip} file onto your \dap{}. Note that the entire contents of the | 182 | the \fname{.zip} file onto your \dap{}. Note that the entire contents of the |
183 | \fname{/zip} file should be extracted directly to the root of your \daps{} | 183 | \fname{.zip} file should be extracted directly to the root of your \daps{} |
184 | drive. Do not try to create a separate directory or folder on your \dap{} for | 184 | drive. Do not try to create a separate directory or folder on your \dap{} for |
185 | the Rockbox files! The \fname{.zip} file already contains the internal | 185 | the Rockbox files! The \fname{.zip} file already contains the internal |
186 | directory structure that Rockbox needs. | 186 | directory structure that Rockbox needs. |
187 | 187 | ||
188 | \note{ | 188 | \note{ |
189 | If the contents of the \fname{.zip} file are extracted correctly, you will | 189 | If the contents of the \fname{.zip} file are extracted correctly, you will |
190 | have a file called \fname{\firmwarefilename} in the main folder of your | 190 | have a file called \fname{\firmwarefilename} in the main folder of your |
191 | \daps{} drive, and also a folder called /\fname{.rockbox}, which contains a | 191 | \daps{} drive, and also a folder called \fname{/.rockbox}, which contains a |
192 | number of other folders and system files needed by Rockbox. If you receive a | 192 | number of other folders and system files needed by Rockbox. If you receive a |
193 | ``-1'' error when you start Rockbox, you have not extracted the contents of | 193 | ``-1'' error when you start Rockbox, you have not extracted the contents of |
194 | the \fname{.zip} file to the proper location. | 194 | the \fname{.zip} file to the proper location. |
195 | } | 195 | } |
196 | 196 | ||
197 | \section{Enabling Speech Support (optional)}\label{sec:enabling_speech_support} | 197 | \section{Enabling Speech Support (optional)}\label{sec:enabling_speech_support} |
198 | \index{Speech}\index{Installation!Optional Steps} | 198 | \index{Speech}\index{Installation!Optional Steps} |
199 | If you wish to use speech support you will also need a language file, available | 199 | If you wish to use speech support you will also need a language file, available |
200 | from \wikilink{VoiceFiles}. For the English language, the file is called | 200 | from \wikilink{VoiceFiles}. For the English language, the file is called |
201 | \fname{english.voice}. When it has been downloaded, unpack this file and copy | 201 | \fname{english.voice}. When it has been downloaded, unpack this file and copy |
202 | it into the \fname{lang} folder which is inside the \fname{/.rockbox} folder on | 202 | it into the \fname{lang} folder which is inside the \fname{/.rockbox} folder on |
203 | your \dap{}. Voice menus are turned on by default. See | 203 | your \dap{}. Voice menus are turned on by default. See |
204 | \reference{ref:Voiceconfiguration} for details on voice settings. | 204 | \reference{ref:Voiceconfiguration} for details on voice settings. |
205 | 205 | ||
206 | \section{Running Rockbox} | 206 | \section{Running Rockbox} |
207 | Remove your \dap{} from the computer's USB port.% | 207 | Remove your \dap{} from the computer's USB port.% |
208 | \nopt{ipod}{Unplug any connected power supply and turn the unit off. When | 208 | \nopt{ipod}{Unplug any connected power supply and turn the unit off. When |
209 | you next turn the unit on, Rockbox should load.}% | 209 | you next turn the unit on, Rockbox should load.}% |
@@ -219,31 +219,31 @@ use. | |||
219 | \note{ | 219 | \note{ |
220 | Rockbox starts in the \setting{File Browser}. If you have loaded music onto | 220 | Rockbox starts in the \setting{File Browser}. If you have loaded music onto |
221 | your player using Itunes, you will not be able to see your music because | 221 | your player using Itunes, you will not be able to see your music because |
222 | Itunes changes your files' names and hides them in directories in the | 222 | Itunes changes your files' names and hides them in directories in the |
223 | \fname{Ipod\_Control} folder. You can view files placed on your \dap{} by | 223 | \fname{Ipod\_Control} folder. You can view files placed on your \dap{} by |
224 | Itunes by initialising and using Rockbox's database. See | 224 | Itunes by initialising and using Rockbox's database. See |
225 | \reference{ref:database} for more information. | 225 | \reference{ref:database} for more information. |
226 | } | 226 | } |
227 | } | 227 | } |
228 | 228 | ||
229 | \section{Updating Rockbox} Updating Rockbox is easy. Download a Rockbox build. | 229 | \section{Updating Rockbox} Updating Rockbox is easy. Download a Rockbox build. |
230 | (The latest release of the Rockbox software will always be available from | 230 | (The latest release of the Rockbox software will always be available from |
231 | \url{http://www.rockbox.org/download/}). Unzip the build to the root directory | 231 | \url{http://www.rockbox.org/download/}). Unzip the build to the root directory |
232 | of your \dap{} like you did in the installation step before. If your unzip | 232 | of your \dap{} like you did in the installation step before. If your unzip |
233 | program asks you whether to overwrite files, choose the ``Yes to all'' option. | 233 | program asks you whether to overwrite files, choose the ``Yes to all'' option. |
234 | The new build will be installed over your current build. | 234 | The new build will be installed over your current build. |
235 | 235 | ||
236 | \note{ | 236 | \note{ |
237 | Settings are stored on an otherwise-unused sector of your hard disk, not in | 237 | Settings are stored on an otherwise-unused sector of your hard disk, not in |
238 | any of the files contained in the Rockbox build. Therefore, generally | 238 | any of the files contained in the Rockbox build. Therefore, generally |
239 | speaking, installing a new build does \emph{not} reset Rockbox to its default | 239 | speaking, installing a new build does \emph{not} reset Rockbox to its default |
240 | settings. Be aware, however, that from time to time, a change is made to the | 240 | settings. Be aware, however, that from time to time, a change is made to the |
241 | Rockbox source code that \emph{does} cause settings to be reset to their | 241 | Rockbox source code that \emph{does} cause settings to be reset to their |
242 | defaults when a Rockbox build is updated. Thus it is recommended to save your | 242 | defaults when a Rockbox build is updated. Thus it is recommended to save your |
243 | settings using the \setting{Manage Settings} $\rightarrow$ | 243 | settings using the \setting{Manage Settings} $\rightarrow$ |
244 | \setting{Write .cfg file} function before updating your Rockbox build so that | 244 | \setting{Write .cfg file} function before updating your Rockbox build so that |
245 | you can easily restore the settings if necessary. For additional information | 245 | you can easily restore the settings if necessary. For additional information |
246 | on how to save, load, and reset Rockbox's settings, see | 246 | on how to save, load, and reset Rockbox's settings, see |
247 | \reference{ref:SystemOptions}. | 247 | \reference{ref:SystemOptions}. |
248 | } | 248 | } |
249 | 249 | ||
@@ -251,57 +251,57 @@ The new build will be installed over your current build. | |||
251 | 251 | ||
252 | If you would like to go back to using the original \playerman{} software, then | 252 | If you would like to go back to using the original \playerman{} software, then |
253 | connect the \playerman{} to your computer, and delete the | 253 | connect the \playerman{} to your computer, and delete the |
254 | \fname{\firmwarefilename} file. | 254 | \fname{\firmwarefilename} file. |
255 | 255 | ||
256 | \opt{h10,h10_5gb}{ | 256 | \opt{h10,h10_5gb}{ |
257 | Next, put the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} | 257 | Next, put the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} |
258 | file backed up in the installation phase back into the \fname{System} | 258 | file backed up in the installation phase back into the \fname{System} |
259 | directory on your \playertype{}, replacing the file that is there already. As | 259 | directory on your \playertype{}, replacing the file that is there already. As |
260 | in the installation, it may be necessary to first put your device into UMS | 260 | in the installation, it may be necessary to first put your device into UMS |
261 | mode. | 261 | mode. |
262 | } | 262 | } |
263 | 263 | ||
264 | \optv{ipod}{ | 264 | \optv{ipod}{ |
265 | Next, open a command window (Windows) or a terminal window (Mac or Linux). | 265 | Next, open a command window (Windows) or a terminal window (Mac or Linux). |
266 | Navigate to the folder you created when you downloaded the | 266 | Navigate to the folder you created when you downloaded the |
267 | \fname{ipodpatcher} program you used to install the Rockbox boot loader. | 267 | \fname{ipodpatcher} program you used to install the Rockbox boot loader. |
268 | Type the following command: | 268 | Type the following command: |
269 | 269 | ||
270 | \begin{code} | 270 | \begin{code} |
271 | ipodpatcher -w \emph{N} bootpartition.bin | 271 | ipodpatcher -w \emph{N} bootpartition.bin |
272 | \end{code} | 272 | \end{code} |
273 | 273 | ||
274 | Remember that \emph{N} is the number that you found when you installed | 274 | Remember that \emph{N} is the number that you found when you installed |
275 | Rockbox on your \playerman{}. | 275 | Rockbox on your \playerman{}. |
276 | } | 276 | } |
277 | 277 | ||
278 | If you wish to clean up your disk, you may also wish to delete the | 278 | If you wish to clean up your disk, you may also wish to delete the |
279 | \fname{.rockbox} folder and its contents. Turn the \playerman{} off. | 279 | \fname{.rockbox} folder and its contents. Turn the \playerman{} off. |
280 | 280 | ||
281 | \opt{h300}{Press and hold the \ButtonRec{} button.} | 281 | \opt{h300}{Press and hold the \ButtonRec{} button.} |
282 | 282 | ||
283 | Turn the \dap{} back on and the original \playerman{} software will load. | 283 | Turn the \dap{} back on and the original \playerman{} software will load. |
284 | 284 | ||
285 | \opt{h1xx}{ | 285 | \opt{h1xx}{ |
286 | \note{ | 286 | \note{ |
287 | There's no need to remove the installed boot loader. If you want to remove | 287 | There's no need to remove the installed boot loader. If you want to remove |
288 | it, simply flash an unpatched \playerman{} firmware. Be aware that doing so | 288 | it, simply flash an unpatched \playerman{} firmware. Be aware that doing so |
289 | will also remove the boot loader USB mode. As that mode can come in quite | 289 | will also remove the boot loader USB mode. As that mode can come in quite |
290 | handy (especially when having disk errors) it is recommended to keep the | 290 | handy (especially when having disk errors) it is recommended to keep the |
291 | boot loader. It also gives you the possibility of trying Rockbox anytime | 291 | boot loader. It also gives you the possibility of trying Rockbox anytime |
292 | later by simply installing the distribution files. | 292 | later by simply installing the distribution files. |
293 | } | 293 | } |
294 | } | 294 | } |
295 | 295 | ||
296 | \opt{h300}{ | 296 | \opt{h300}{ |
297 | \note{ | 297 | \note{ |
298 | There's no need to remove the installed boot loader, although you if you | 298 | There's no need to remove the installed boot loader, although you if you |
299 | retain the Rockbox boot loader, you will need to hold the \ButtonRec{} | 299 | retain the Rockbox boot loader, you will need to hold the \ButtonRec{} |
300 | button each time you want to start the original firmware. If you want to | 300 | button each time you want to start the original firmware. If you want to |
301 | remove it simply flash an unpatched \playerman{} firmware. Be aware that | 301 | remove it simply flash an unpatched \playerman{} firmware. Be aware that |
302 | doing so will also remove the boot loader USB mode. As that mode can come in | 302 | doing so will also remove the boot loader USB mode. As that mode can come in |
303 | quite handy (especially when having disk errors), you may wish to keep the | 303 | quite handy (especially when having disk errors), you may wish to keep the |
304 | boot loader. It also gives you the possibility of trying Rockbox anytime | 304 | boot loader. It also gives you the possibility of trying Rockbox anytime |
305 | later by simply installing a new build. | 305 | later by simply installing a new build. |
306 | } | 306 | } |
307 | } | 307 | } |