have not done it myself but here is the tut from satcity.nl in case you didn't know about it
If you have a USB Memory Stick or a Flash Card and wish to use it as a multiboot solution, please refer to this post (done by me too):
http://216.12.210.231/~satcity/board...;threadid=2763
=================================================
MOTIVATION
=================================================
I am sure all of you know about the MS Windows NT bootloader which enables you to start different already-installed operating systems (Linux has Lilo to do that).
I am, also, sure that many of you thougth that the same thing would be nice to have for our nice dream box (DB). Instead of erasing installed image and flashing a new image and finding out that it is not better or has missing functionality comparing to other images. One better keeps already installed images there and just install a new image and at boot up select the image one would like to boot from. I have seen the SF image has one image with enigma booted from memory or HD. So to say, it is not a "true" multi (different) images boot, and moreover it is not configurable in a way like one can open a conf file and add more image entries (just like to windows bootloader or linux Lilo).
Using such a solution:
+ One does not put pressure on the FLASH memory all the time re-writing images.
+ if some images are not functional, one does not need (any more) to use the null-modem cable and wait ages to reinstall a functional image. One needs just to restart the DB and select another bootable image and then fix the problem with the non functional image.
+ If one would like to record movies and he often uses, say, Traveller which (hypothetically speaking) is bad for recording movies. On the other hand, one has Jirkas image installed which good for recording movies. Just a restart of the DB and then selecting Jirkas image does what one needs.
- One does not see the Boot Logo of the bootable images when booting.
- One should not use the network automatic Upgrade. One has to download the image using a PC and then ftp it to the DB. Please check the section UPDATING to see how to update images.
- The most drawback is the waiting time to start the DB and being able to watch a channel is almost doubled. This effect guaranteed the clean startup of the choosen image, in order to load the image associated drivers.
=================================================
INSTALLATION
=================================================
1. One shall have a functioning hard disk drive installed, so one can have different images installed.
2. Download a software called ImageOnHD v27 from:
http://projekte.ng-software.de/dl/Im...geOnHD_v27.rar
[
http://projekte.ng-software.de/db_hd.html site will have later on a newer version, which will require you to modify my scripts if you wish to use them, for the image name for example. Now it is ImageOnHD-v27.img I do not know how it will be named later ]
3. On your PC, uncompress the downloaded file and then ftp all the resulting uncompressed files to the DB under /hdd. Then telnet to the DB.
4. On the DB:
cd /hdd
chmod u+x iohdsetup uncramfs setup_v27
Before you run the command iohdsetup, please notice that it will remove your images files after installing them, if the installtion for some reason fails, your image files are gone. So, it is recommended to make backups of the image files. You should install at the same time EXACTLY 3 images (myfirstImage and others are imaginary names use the name of the images you really have downloaded to your HD)
iohdsetup -install myfirstImage mySecondImage myThirdImage
Use the remote control: Menu / Setup / Update / Manual Update. A confirmation box pops up, click yes. If the DB does not restart normally, then please restart it by pressing the three buttons on the front panel of the DB.
5. Once the DB boots, you see the images list on the LCD display (not the TV display) as: Image 1, Image 2, Image 3. Select the image you wish to boot from, and then the DB will RESTART itself automatically and go in the next boot directly to the image you selected.
6. Later, if you switch the DB off and on again you will have the possiblity to select the image you wish to boot from. No matter whether if you select a new image or stick to the last selected image, the DB will first reboot and then boot directly to the selected image.
I believe that the installation script is aggresive, I made a much simpler and novice friendly script. It is attached at the end of this message [SetupImageOnHD_v27.txt please change its extension from txt to sh after downloading it and ftping it to the DB /hdd/ ].
Installation with this script works like the above one, except for step 4:
cd /hdd
./chmod u+x SetupImageOnHD_v27.sh
./SetupImageOnHD_v27.sh -install image1.img image2.img image3.img
This script does not delete any file without your wish. It deletes some files if you do:
./SetupImageOnHD_v27.sh -clean
=================================================
CONFIGURATION:
=================================================
After a successful installtion, the main files to configure is /hdd/flashext/lcdmenu.conf and /hdd/flashext/lcdmenu.main. Next is an example of my configuration showing only two useful items to change (in both files):
***********
menu_items=SFTeamJul03,TravlerJun03,SatCityJul03,x-tras
***********
This is the menu of images displayed on the LCD display of the DB. Notice that, there are no spaces after commas. Each image name length shoud NOT exceed 12 characters, else it will be displayed as an empty line on the lcd but still it remains as a functional entry.
***********
timeout=3
***********
This is the time out the DB will wait for you to select an image to boot from, if you do nothing it will boot to the last-selected image. This is useful, when you want to stick to the latest image you selected, so you turn your DB on and do not need to wait long.
=================================================
UPDATING
=================================================
First, I would like to thank: Tita, Sat_Freak for their useful hints on updating.
===========
A SINGLE IMAGE
===========
The scipts which come with the sw do not support that. Please use my attached script (see above).
One can update only one image at a time, note that the number 1 after the image name refers to which directory to update the image:
./SetupImageOnHD_v27.sh -update imageX.img 1
Another example:
./SetupImageOnHD_v27.sh -update imageX.img 3
If you do not wish using my script, there is an option:
1. Reboot the DB
2. Select Xtra image from LCD menu, Then select Service Image
4. After boot completes, telnet to the DB and use the command: setimg. Example: setimg 1 imageX.img. The number 1 refers to the directory where the image to update is installed, you may use number 2 or 3 depending on which image you wish to update.
The advantage of my script is that you do not need to reboot to different image to do update.
===========
The ImageOnHD
===========
1. Ftp the latest version of ImageOnHD.img and install.tar.gz to the DB under /hdd
2. Run the accompanied script setup. Note that this scipt deletes some directories under /hdd such as bin/ so please open the script and see what it does first (It is the original script not mine).
./setup_v27
Alternatively, you could use my installation script (RECOMMENDED):
./SetupImageOnHD_v27.sh -upgrade ImageOnHDXX.img
3. No matter which script you choose, using the the remote control, please do: Menu / Setup / Update / Manual Update. A confirmation box pops up, click yes. If the DB does not restart normally, then please restart it by pressing the three buttons on the front panel of the DB.
=================================================
REMOVING EVERYTHING
=================================================
**PREQUISITE**
If you wish to remove everything, you have to flash some other image than ImageOnHD and restart the DB using that image.
*******
On the DB, run my installation script
./SetupImageOnHD_v27.sh -remove
=========
FAQs
=========
1. ImageOnHD REFUSES TO BOOT.
-------------------------------------------
If sometimes the ImageOnHD refuses to boot to an image, just keep pressing for 10 seconds the three buttons at the front panel of the DB. Then choose to boot Xtra image and then Then select the entry Service Image.
Option one: Just reboot and (hopefully) things will work.
Option two: Telnet to your DB and see what is the problem. I have observed sometimes some files of an image being deleted, so I did an update for that image and things worked again. Example: ./SetupImageOnHD_v27.sh -update imageX.img 1
--
EHF
SetupImageOnHD_v27.txt
Report to moderator Logged
Linear Mode
