Vu+ Real Multiboot Now Available

I would like to ask if it is possible to install the kexec multiboot without creating the slots in recovery?
Or is it possible to ensure that the slots created in 1.2.3 can be deleted from the multiboot screen and leave only those created on USB?!!


IT:
Vorrei chiedere se possibile installare il multiboot kexec senza creare gli slot in recovery?
Oppure se e possibile far si che gli slot creati 1.2.3 si possono eliminare dal schermata multiboot e lasciare solo quelle create su usb?!!
The procedure is complicated that's why has been created the utility to install it.

What you are asking is not supported but, but you can do that manally.
If you consider enough confident you can just install vuplus-multiboot as usual to convert the first image into a recovery image,
- then with sftp/ftp/ssh delete the STARTUP_x slot you don't want/need and rename the one you want to keep to the right sequence.
- you can edit subdir= entry inside each startup file and adjust it to stay aligned with the slot.
- take a backup of that STARTUP_x files (you might need them)
 
Why do you want to do this ?

It can be done, but I don't understand your reason for wanting too.
The reason is why I want all the space for recovery images that I normally use and use the images in the extra slots to play with them
You will say but pretend that the 3 slots aren't there... :)

IT:

Il motivo e perchè voglio tutto lo spazio per immagine di Ripristino che uso normalmente e usare le immagini nei slot extra per giocarci
Tu dirai ma fai finta che non ci siano le 3 slot ... :)
 
The procedure is complicated that's why has been created the utility to install it.

What you are asking is not supported but, but you can do that manally.
If you consider enough confident you can just install vuplus-multiboot as usual to convert the first image into a recovery image,
- then with sftp/ftp/ssh delete the STARTUP_x slot you don't want/need and rename the one you want to keep to the right sequence.

- you can edit subdir= entry inside each startup file and adjust it to stay aligned with the slot.
- take a backup of that STARTUP_x files (you might need the

The procedure is complicated that's why has been created the utility to install it.

What you are asking is not supported but, but you can do that manally.
If you consider enough confident you can just install vuplus-multiboot as usual to convert the first image into a recovery image,
- then with sftp/ftp/ssh delete the STARTUP_x slot you don't want/need and rename the one you want to keep to the right sequence.
- you can edit subdir= entry inside each startup file and adjust it to stay aligned with the slot.
- take a backup of that STARTUP_x files (you might need them)
ok thanks I'll do some tests but for me personally nothing more than to tinker around a bit.... I always back up the flash without multiboot ;)

IT:
ok grazie faccio delle prove ma per me personalmente niente di più che per smanettare un pò .... faccio sempre il backup della flash senza multiboot ;)
 
If I installed OpenMultiboot ( found in latest OpenBH 5.4.1.007 ) for old VU+ MIPSE 1.3 Ghz VU+ Duo2 - is it right or will have crashes?
 
The main fact about this new Multiboot (that is surely much better than the old OpenMultiboot) is that is not possible to choose an image at the startup. This is the only lack compared to OpenMultiboot.
 
Receiver VU DUO 4K SE. I flashed and selected multiboot, in the menu "menu - standby and reboot - multiboot" I see two options:
1. Recovery mode: boot to access recovery options
2. Slot 1 eMMC: OpenBH 5.4.1.008 (24-10-2024) (current).
Why did it install in slot 1, and not in slot 0? And how to transfer it
to slot 0?
 
Receiver VU DUO 4K SE. I flashed and selected multiboot, in the menu "menu - standby and reboot - multiboot" I see two options:
1. Recovery mode: boot to access recovery options
2. Slot 1 eMMC: OpenBH 5.4.1.008 (24-10-2024) (current).
Why did it install in slot 1, and not in slot 0? And how to transfer it
to slot 0?
Slot0 in this multiboot solution is the recovery
 
But I pressed slot 0 and the receiver hung on Started Enigma, I had to reflash it. What should I have done?
Paste the log from /home/enigma2/log so we could analyze..
Or you could have copied /STARTUP_N into /STARTUP to start the previous slot (using FTP or with telnet)
 
Back
Top