summaryrefslogtreecommitdiff
path: root/manual/getting_started/installation.tex
diff options
context:
space:
mode:
Diffstat (limited to 'manual/getting_started/installation.tex')
-rw-r--r--manual/getting_started/installation.tex58
1 files changed, 30 insertions, 28 deletions
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex
index c270e8bb4c..10d13b6e12 100644
--- a/manual/getting_started/installation.tex
+++ b/manual/getting_started/installation.tex
@@ -93,7 +93,7 @@ follow the instructions at
93 \end{itemize} 93 \end{itemize}
94\end{description} 94\end{description}
95} 95}
96\opt{h300}{ 96\opt{iriverh300}{
97\begin{description} 97\begin{description}
98 \item[DRM capability.] If your \dap{} has a US firmware, then by installing Rockbox you will 98 \item[DRM capability.] If your \dap{} has a US firmware, then by installing Rockbox you will
99 \emph{permanently} lose the ability to playback files with DRM. 99 \emph{permanently} lose the ability to playback files with DRM.
@@ -161,14 +161,15 @@ follow the instructions at
161 \setting{MSC} from within the original firmware.} 161 \setting{MSC} from within the original firmware.}
162 } 162 }
163 163
164 \opt{h10,h10_5gb}{ 164 \opt{iriverh10,iriverh10_5gb}{
165 The installation requires you to use UMS mode and so 165 The installation requires you to use UMS mode and so
166 may require use of the UMS trick, whereby it is possible to force a MTP 166 may require use of the UMS trick, whereby it is possible to force a MTP
167 \playertype{} to start up in UMS mode as follows: 167 \playertype{} to start up in UMS mode as follows:
168 \begin{enumerate} 168 \begin{enumerate}
169 \item Ensure the \dap{} is fully powered off by \opt{h10}{using a pin to 169 \item Ensure the \dap{} is fully powered off by \opt{iriverh10}{using
170 push the small reset button inside the hole between the Hold switch and 170 a pin to push the small reset button inside the hole between the
171 remote control connector.}\opt{h10_5gb}{removing the battery and putting it back in again.} 171 \ButtonHold{} switch and remote control connector.}\opt{iriverh10_5gb}{removing
172 the battery and putting it back in again.}
172 \item Connect your \playertype{} to the computer using the data cable. 173 \item Connect your \playertype{} to the computer using the data cable.
173 \item Hold \ButtonRight{} and push \ButtonPower{} to turn the \dap{} on. 174 \item Hold \ButtonRight{} and push \ButtonPower{} to turn the \dap{} on.
174 \item Continue holding \ButtonRight{} until the USB Connected screen appears. 175 \item Continue holding \ButtonRight{} until the USB Connected screen appears.
@@ -319,7 +320,7 @@ letter the \dap{} gets assigned, on other systems this is a path in the
319filesystem.\\* 320filesystem.\\*
320 321
321 322
322\opt{h100,h300}{ 323\opt{iriverh100,iriverh300}{
323 Rockbox Utility will ask you for a compatible copy of the original 324 Rockbox Utility will ask you for a compatible copy of the original
324 firmware. This is because for legal reasons we cannot distribute 325 firmware. This is because for legal reasons we cannot distribute
325 the bootloader directly. Instead, we have to patch the Iriver firmware 326 the bootloader directly. Instead, we have to patch the Iriver firmware
@@ -330,13 +331,13 @@ filesystem.\\*
330 \wikilink{IriverBoot}. 331 \wikilink{IriverBoot}.
331 332
332 Supported Iriver firmware versions currently include 333 Supported Iriver firmware versions currently include
333 \opt{h100}{1.63US, 1.63EU, 1.63K, 1.65US, 1.65EU, 1.65K, 1.66US, 334 \opt{iriverh100}{1.63US, 1.63EU, 1.63K, 1.65US, 1.65EU, 1.65K, 1.66US,
334 1.66EU and 1.66K. Note that the H140 uses the same firmware as the H120; 335 1.66EU and 1.66K. Note that the H140 uses the same firmware as the H120;
335 H120 and H140 owners should use the firmware called \fname{ihp\_120.hex}. 336 H120 and H140 owners should use the firmware called \fname{ihp\_120.hex}.
336 Likewise, the iHP110 and iHP115 use the same firmware, called 337 Likewise, the iHP110 and iHP115 use the same firmware, called
337 \fname{ihp\_100.hex}. Be sure to use the correct firmware file for 338 \fname{ihp\_100.hex}. Be sure to use the correct firmware file for
338 your player.} 339 your player.}
339 \opt{h300}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU. 340 \opt{iriverh300}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU.
340 \note{The US \playername{} firmware is not supported and cannot be 341 \note{The US \playername{} firmware is not supported and cannot be
341 patched to be used with the bootloader. If you wish to install Rockbox 342 patched to be used with the bootloader. If you wish to install Rockbox
342 on a US \playername{}, you must first install a non-US version of the 343 on a US \playername{}, you must first install a non-US version of the
@@ -444,7 +445,7 @@ data partiton.}}
444correct version for your \dap{}.}} 445correct version for your \dap{}.}}
445 446
446\item Connect your \dap{} to the computer via USB 447\item Connect your \dap{} to the computer via USB
447 \opt{sansa,sansaAMS,h10,h10_5gb,vibe500}{ in MSC mode } 448 \opt{sansa,sansaAMS,iriverh10,iriverh10_5gb,vibe500}{ in MSC mode }
448 \opt{ipod3g,ipod4g,ipodmini,ipodcolor}{ or Firewire }as described in 449 \opt{ipod3g,ipod4g,ipodmini,ipodcolor}{ or Firewire }as described in
449 the manual that came with your \dap{}. 450 the manual that came with your \dap{}.
450 451
@@ -483,11 +484,11 @@ structure that Rockbox needs.\\}
483\opt{swcodec}{% 484\opt{swcodec}{%
484 \nopt{gigabeats}{% 485 \nopt{gigabeats}{%
485 \subsubsection{Installing the bootloader} 486 \subsubsection{Installing the bootloader}
486 \opt{h100,h300}{\input{getting_started/iriver_install.tex}} 487 \opt{iriverh100,iriverh300}{\input{getting_started/iriver_install.tex}}
487 \opt{mpiohd200}{\input{getting_started/mpio_install.tex}} 488 \opt{mpiohd200}{\input{getting_started/mpio_install.tex}}
488 \opt{ipod}{\input{getting_started/ipod_install.tex}} 489 \opt{ipod}{\input{getting_started/ipod_install.tex}}
489 \opt{iaudio}{\input{getting_started/iaudio_install.tex}} 490 \opt{iaudio}{\input{getting_started/iaudio_install.tex}}
490 \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}} 491 \opt{iriverh10,iriverh10_5gb}{\input{getting_started/h10_install.tex}}
491 \opt{gigabeatf}{\input{getting_started/gigabeat_install.tex}} 492 \opt{gigabeatf}{\input{getting_started/gigabeat_install.tex}}
492 \opt{sansa}{\input{getting_started/sansa_install.tex}} 493 \opt{sansa}{\input{getting_started/sansa_install.tex}}
493 \opt{sansaAMS}{\input{getting_started/sansaAMS_install.tex}} 494 \opt{sansaAMS}{\input{getting_started/sansaAMS_install.tex}}
@@ -526,7 +527,7 @@ structure that Rockbox needs.\\}
526 \end{itemize} 527 \end{itemize}
527} 528}
528 529
529\opt{h10,h10_5gb,ipod,mrobe100,sansa,archos,sansaAMS,cowond2,vibe500,ondavx777}{ 530\opt{iriverh10,iriverh10_5gb,ipod,mrobe100,sansa,archos,sansaAMS,cowond2,vibe500,ondavx777}{
530 Safely eject / unmount the USB drive, unplug the cable and restart. 531 Safely eject / unmount the USB drive, unplug the cable and restart.
531} 532}
532 533
@@ -534,7 +535,7 @@ structure that Rockbox needs.\\}
534 Safely eject / unmount your \dap{}. 535 Safely eject / unmount your \dap{}.
535} 536}
536 537
537\opt{h100,h300}{ 538\opt{iriverh100,iriverh300}{
538 \begin{itemize} 539 \begin{itemize}
539 \item Safely eject / unmount your \dap{}. 540 \item Safely eject / unmount your \dap{}.
540 541
@@ -665,7 +666,7 @@ You can uninstall Rockbox automatically by using Rockbox Utility. If you
665installed Rockbox manually you can still use Rockbox Utility for uninstallation 666installed Rockbox manually you can still use Rockbox Utility for uninstallation
666but will not be able to do this selectively. 667but will not be able to do this selectively.
667 668
668\opt{h100,h300}{\note{Rockbox Utility cannot uninstall the bootloader due to 669\opt{iriverh100,iriverh300}{\note{Rockbox Utility cannot uninstall the bootloader due to
669the fact that it requires a flashing procedure. To uninstall the bootloader 670the fact that it requires a flashing procedure. To uninstall the bootloader
670completely follow the manual uninstallation instructions below.}} 671completely follow the manual uninstallation instructions below.}}
671 672
@@ -677,14 +678,15 @@ completely follow the manual uninstallation instructions below.}}
677 \fname{\firmwarefilename} file. 678 \fname{\firmwarefilename} file.
678} 679}
679 680
680\opt{h10,h10_5gb}{ 681\opt{iriverh10,iriverh10_5gb}{
681 If you would like to go back to using the original \playerman{} software, 682 If you would like to go back to using the original \playerman{} software,
682 connect the \dap{} to your computer, and delete the 683 connect the \dap{} to your computer, and delete the
683 \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file and rename 684 \opt{iriverh10}{\fname{H10\_20GC.mi4}}\opt{iriverh10_5gb}{\fname{H10.mi4}}
684 \fname{OF.mi4} to \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} 685 file and rename \fname{OF.mi4} to \opt{iriverh10}{\fname{H10\_20GC.mi4}}%
685 in the \fname{System} directory on your \playertype{}. As in the installation, 686 \opt{iriverh10_5gb}{\fname{H10.mi4}} in the \fname{System} directory on
686 it may be necessary to first put your device into UMS mode. 687 your \playertype{}. As in the installation, it may be necessary to first
687} 688 put your device into UMS mode.
689 }
688 690
689\opt{vibe500}{ 691\opt{vibe500}{
690 If you would like to go back to using the original \playerman{} software, 692 If you would like to go back to using the original \playerman{} software,
@@ -726,18 +728,18 @@ completely follow the manual uninstallation instructions below.}}
726 and insert the charger. The original firmware will automatically be flashed. 728 and insert the charger. The original firmware will automatically be flashed.
727} 729}
728 730
729\opt{h100,h300}{ 731\opt{iriverh100,iriverh300}{
730 If you want to remove the Rockbox bootloader, simply flash an unpatched 732 If you want to remove the Rockbox bootloader, simply flash an unpatched
731 \playerman{} firmware. Be aware that doing so will also remove the bootloader 733 \playerman{} firmware. Be aware that doing so will also remove the bootloader
732 USB mode. As that mode can come in quite handy (especially if you experience 734 USB mode. As that mode can come in quite handy (especially if you experience
733 disk errors) it is recommended to keep the bootloader. It also 735 disk errors) it is recommended to keep the bootloader. It also
734 gives you the possibility of trying Rockbox anytime later by simply 736 gives you the possibility of trying Rockbox anytime later by simply
735 installing the distribution files. 737 installing the distribution files.
736 \opt{h100}{ 738 \opt{iriverh100}{
737 The Rockbox bootloader will automatically start the original firmware if 739 The Rockbox bootloader will automatically start the original firmware if
738 the \fname{.rockbox} directory has been deleted. 740 the \fname{.rockbox} directory has been deleted.
739 } 741 }
740 \opt{h300}{ 742 \opt{iriverh300}{
741 Although if you retain the Rockbox bootloader, you will need to hold the 743 Although if you retain the Rockbox bootloader, you will need to hold the
742 \ButtonRec{} button each time you want to start the original firmware. 744 \ButtonRec{} button each time you want to start the original firmware.
743 } 745 }
@@ -792,7 +794,7 @@ completely follow the manual uninstallation instructions below.}}
792 please ensure that you are either logged in as an administrator (Windows), or 794 please ensure that you are either logged in as an administrator (Windows), or
793 you have root rights (Linux)} 795 you have root rights (Linux)}
794 796
795\opt{h100,h300}{ 797\opt{iriverh100,iriverh300}{
796 \item[Immediately loading original firmware.] 798 \item[Immediately loading original firmware.]
797 If the original firmware is immediately 799 If the original firmware is immediately
798 loaded without the Rockbox bootloader appearing first, then the Rockbox bootloader 800 loaded without the Rockbox bootloader appearing first, then the Rockbox bootloader
@@ -800,11 +802,11 @@ completely follow the manual uninstallation instructions below.}}
800 the update if the filename is correct, including case. Make sure that the patched 802 the update if the filename is correct, including case. Make sure that the patched
801 Iriver firmware is called \fname{.hex}.} 803 Iriver firmware is called \fname{.hex}.}
802 804
803\nopt{h100,h300,mpiohd200}{\item[``File Not Found'']} 805\nopt{iriverh100,iriverh300,mpiohd200}{\item[``File Not Found'']}
804\opt{h100,h300,mpiohd200}{\item[``-1 error'']} 806\opt{iriverh100,iriverh300,mpiohd200}{\item[``-1 error'']}
805 If you receive a 807 If you receive a
806 \nopt{h100,h300,mpiohd200}{``File Not Found''} 808 \nopt{iriverh100,iriverh300,mpiohd200}{``File Not Found''}
807 \opt{h100,h300,mpiohd200}{``-1 error''} 809 \opt{iriverh100,iriverh300,mpiohd200}{``-1 error''}
808 from the bootloader, then the bootloader cannot find the Rockbox firmware. 810 from the bootloader, then the bootloader cannot find the Rockbox firmware.
809 This is usually a result of not extracting the contents of the \fname{.zip} 811 This is usually a result of not extracting the contents of the \fname{.zip}
810 file to the proper location, and should not happen when Rockbox has been 812 file to the proper location, and should not happen when Rockbox has been