The Sandbox Team is happy to propose you a new release of iBoot : Version 3.0
This new release includes following improvements
- In main window, a new button is proposed, to check (and eventually mount) the /mmc media mount:
Because, after a fresh install in flash, generally the /mmc media was'nt mounted, due to ext3 format : Official images does'nt support this kind of media by default.
So, installation of iBoot on a fresh flashed firmware was a bit complex.
Now, that should be simplest, using this new button.
This new release allows to install iBoot on :
--> /mmc
--> /hdd
depending on configuration of receiver into iBoot settings (onto Windows interface)
The bootmenue version included in this package will be modified soon, I hope, to avoid the flashing effect when displaying list of firmwares available to boot.
The font has been enlarged, to be more readable ( I'm an old man......)
This version of bootmenue supports remote command unit codes for :
- firmwares based on 0.10 or oldest in flash
- firmwares based on 0.11 in flash ( new RCU codes mapping), like Satlinux 2.0.14 .
The .zip file must be extracted into any Windows directory,
double-clic on iBoot.exe
configure at least 1 receiver
If you force a re-installation of iBoot on the receiver, that'll also force an update of tools already present, into /mmc/iboot/bin or /hdd/iboot/bin.
But all existing firwares will be preserved and usable.
If your receiver was using iBoot 2.0, it's ABSOLUTELY NECESSARY to force a re-installation from 3.0, otherwise you'll not be able anymore to install new firmwares in multiboot ( But existing will still be usable to boot )
This new release includes following improvements
- In main window, a new button is proposed, to check (and eventually mount) the /mmc media mount:
Because, after a fresh install in flash, generally the /mmc media was'nt mounted, due to ext3 format : Official images does'nt support this kind of media by default.
So, installation of iBoot on a fresh flashed firmware was a bit complex.
Now, that should be simplest, using this new button.
This new release allows to install iBoot on :
--> /mmc
--> /hdd
depending on configuration of receiver into iBoot settings (onto Windows interface)
The bootmenue version included in this package will be modified soon, I hope, to avoid the flashing effect when displaying list of firmwares available to boot.
The font has been enlarged, to be more readable ( I'm an old man......)
This version of bootmenue supports remote command unit codes for :
- firmwares based on 0.10 or oldest in flash
- firmwares based on 0.11 in flash ( new RCU codes mapping), like Satlinux 2.0.14 .
The .zip file must be extracted into any Windows directory,
double-clic on iBoot.exe
configure at least 1 receiver
If you force a re-installation of iBoot on the receiver, that'll also force an update of tools already present, into /mmc/iboot/bin or /hdd/iboot/bin.
But all existing firwares will be preserved and usable.
If your receiver was using iBoot 2.0, it's ABSOLUTELY NECESSARY to force a re-installation from 3.0, otherwise you'll not be able anymore to install new firmwares in multiboot ( But existing will still be usable to boot )
Last edited: