Search results

I would prefer to customize the bottom-right NEXT section to allow displaying 3 next events like in my favorite BH skin below.

My config file smb-user.conf was created from scratch for the Samba version in OBH 5.2 (rescue image too) without need to restore old settings. It's also working for OpenATV 7.2 and probably other images containing the new samba server.

Seems that I have some clue why I could not enter recovery mode yesterday regardless of where my flashdrive was inserted. Hope this helps to improve the recovery process for the future... In my box are 3 storage devices: 4TB HDD inside the box - detected as /dev/sda (EXT4) 250MB USB 2.0...

Installing Multiboot.py adviced for OpenATV 7.x to OpenATV 6.4 didn't worked. After GUI restart the enigma GUI stopped working (no reaction to remote). Fortunately WinSCP to box was still working so I decided to rewrite the content of file /boot/STARTUP with content of STARTUP_1 which is OpenBH...

Thanks, I will try to update OpenATV ver. 6.4 to MultiBoot the same way like the advice for ver. 7.x. Installed fresh ATV build from yesterday but it's still missing MultiBoot. But for some reason I still can't boot to recovery even when inserted the recovery flashdisk to back USB 3.0 port...

After installation of OpenATV 6.4 to Slot3(eMMC) to my Duo4k box I need to enter recovery image to change the Slot(no multiboot menu). Inserting FAT32 USB flashdisk with STARTUP_RECOVERY file to front USB 2.0 port does not help. I can access the back inserted USB3.0 flashdisk (EXT4) via ssh but...

Yes, exactly. You can make a backup of smb-user.conf if you wish but not needed. Should work after a reboot

I started with OBH 5.2 last week coming from BH. One problem after installation was access to the box via Samba1 I was used to. After Samba installation via Network/Utilities/Samba I found the configuration directory in /etc/samba. I started to experiment with different options there without...

After switching to OBH I am very much missing my favourite BH Skin MX Black Sea E which displays 3 NEXT EPG events (below). Would it be possible to update this skin to OBH or create a similar variant of the nice default OBH 5.2 skin (MX Slim-Line NP) ? I would very appreciate the effort and such...

Yes, exactly, mea culpa... After re-zip with correct directory structure the flashing is working fine. Thanks for help

Files are listed above, path is /hdd/imagebackups/imagerestore/duo4k/ Seems that directory vuplus is missing in the path. Will create a new .zipfile with vuplus and try it again.

I run it multiple times before and once during the logfile creation. Still the same error... Should I delete the directory content? root@vuduo4k:/hdd/imagebackups/imagerestore/duo4k# ls -la drwxrwxrwx 2 root root 4096 Mar 4 19:17 . drwxr-xr-x 3 root root 4096 Mar...

OK guys, sure, the debug log is attached. Box is Duo4K with internal 4TB Seagate HDD mounted as /media/hdd and USB Sandisk flashdisk 64GB mounted as /media/usb, both formatted as ext4. No problems with the drives, filesystem check OK.

Decided to go ahead today. Following the guide I made a fresh installation of OBH 5.2.2 image to the Recovery and Slot1. Now I want to install my fullbackup of BlackHole (created earlier today) to Slot2. 1st issue was that "Image manager" didn't recognized my fullbackup.zip put in...

OK, was just an idea to make it more beginner friendly. But you're right, installation seems quite easy. The whole guide is very well written(y) Old OpenMultiboot in my box got damaged(only flash image works) so I'm preparing for a complete box reinstall anyway. Hope this solution is more robust...

I know It's a lot to ask, but please don't kill me for a simple question or idea :) Would it be possible (in the future) to distribute this new "VU+ Multiboot" support to your own images (BH 3.1.0, OBH 4.4) via online update ? There are still users like me who still use those images and it seems...

Seems that similar solution for the BlackHole image already exists here , thanks to all involved. A good news for me knowing that after finally moving to OBH there will be a safety option to boot my old trusty BH image.