Open Black Hole 0.1 update 19-06-2015 Vu+ Solo2

This is a nice plugin for trying out multiple images.
But i have one question, where do i have to install all those images?
I guess that internal flash is not big enough for 4 images??
 
i install image named "PKT-3155_GIT-17899.zip" but in openmultiboot manager i see PKTeam Hyperion ?????? Why ???? I install another build form PKTeam and image has this same name in manager. For me this is a bug becouse now i dont know what image i s newer....
 
VANT said:
i install image named "PKT-3155_GIT-17899.zip" but in openmultiboot manager i see PKTeam Hyperion ?????? Why ???? I install another build form PKTeam and image has this same name in manager. For me this is a bug becouse now i dont know what image i s newer....
Click to expand...

It´s because the image it´s called so! No matters the name of zip file image that you have uploaded to your STB to unpack on Open Multiboot! ...
For ex: I can easly rename an image to a name like " Blackhole_217.zip ", and when you install it on Open Multiboot ( unpack it ), you´ll get Open Black Hole 0.1 !

best regards
nunigais
 
where is the name is stored in installed images ? Now i dont know what image build i can run from manager becouse all build have this same name.
 
VANT said:
where is the name is stored in installed images ? Now i dont know what image build i can run from manager becouse all build have this same name.
Click to expand...

I give you my own advice ... install the images you want to run ... like:

BH 2.1.7
BH 2.1.6.1
VTi 8.2.2
OpenVix hades 012
PBnigma VI 4.3.0
SatDreamGR4.0
OpenPli4.0
OpenAtv 4.2
OpenAtv 5.0
OpenNfr 5.0
OpenLD 1.8
OpenSpa 4.0
OpenDroid 5.0

Upon install each one ... rename each one to identify each!

example:

Install Open Blackhole 0.1 from 06/06/2015

Install it from Open Multiboot pannel ... Upon install it ... before boot or install .. Open BlackHole 0.1 from 19/06/2015 ... rename it --> OpenBlackhole_First
Install Open Blackhole 0.1 buid 19/06/2015 before update --> rename it --> OpenBlackhole_1906_Bup
Install Open Blackhole 0.1 buid 19/06/2015 After update --> rename it --> OpenBlackhole_1906_Aup

This are only examples

best regards
nunigaia
 
next question.
I see inconsequences. In openmultiboot manager i see name PKTeam Hyperion, but in boot menu i see name like archive name. Its normal ? for me should be same in both manager and boot menu
 
VANT said:
next question.
I see inconsequences. In openmultiboot manager i see name PKTeam Hyperion, but in boot menu i see name like archive name. Its normal ? for me should be same in both manager and boot menu
Click to expand...

Yes .... It´s normal!
 
ok.
btw. any chance for bigger permanent clock ? in default hd skin clock is very small ;)


ps. image is very fast, IMO this is the fastest image for my solo2. Good job.
THX
 
I always keep my OBH image updated.
Today I did an online update and it found this new package:
grab.png
I didn't try to continue with the update process, just in case something is wrong on the feed. Can someone please comment?
Thanks
 
Neblinio said:
I always keep my OBH image updated.
Today I did an online update and it found this new package:
View attachment 22563
I didn't try to continue with the update process, just in case something is wrong on the feed. Can someone please comment?
Thanks
Click to expand...

Don´t worry ... even with msg you posted ( screen shot ), afaik there´s no upgrades to do now!
Be patient and wait for next updates.

best regards
nunigaia
 
I tried this image myself on my Vu+ Solo2 but it seemed to completely mess up my system. I have a WD internal hard drive installed and when I loaded up OpenBlackhole it didn't seem to automount my drive which messed everything up. I tried initialising the drive myself and it still wouldn't mount properly. I then pressed blue x2 tp get to the extra settings and try and mount in from Devices settings but no luck. So eventually I was left with no choice but to revert back to 2.1.6. It's a shame because OpenBlackhole looks like one the most customisable OS' I've seen so far on this box but not being able to install plugins or picons properly because I kept getting errors telling me I had no space left meant I had no choice but to go back.

Maybe someone here can tell me where I was going wrong but for the life of me I could not figure out why my drive was not automounting while they were on previous versions of Blackhole with no problem.
 
Blue>>Blue>> device manager>>mount points ie. RED>> use left right buttons to chose whatever name you want to give to your device>>OK>> REBOOT!!
 
You must log in or register to reply here.
Back
Top