BlackHole Vu+ Duo 1.3.8 Multiboot

[iet8]

My usb would format and map good, but after restart then the usb stick was not mounted. I remap the usb stick but after restart its still not mounted.

I think it was the 5 time i remap, and i did not restart. I exit out from meny, then go into devise manager and remap it again, now i restarted.
After restart it was mounted

hi
i had the same pb with me, and solved remap and shutdown the receiver from the back butom and resart again.

 

[iet8]

Hi
I found that while the meoboot installing the new image on the external flash converting time of the file from nfi to boot_cfe_auto.jffs2 takes a long time depend on usb flash speed.
Why u don’t make the meoboot accept nfi files or boot_cfe_auto.jffs2 to save time.
Regards

 

[Tamaki]

If I boot an usb-image (vti) via meoboot the remote control has no function?

Did you try to reboot, sometimes after the first install remote doesn't work, after reboot it begins to work.

 

[ALPA]

No
Meoboot is OE 1.6 python 2.6 and I think Pli OE 1.5 python 2.5

Can we expect fix for this in the future?

 

[Mito]

Can we expect fix for this in the future?

There isn't nothing to fix.
Images have to be "compatible".

 

[Yersi]

Can we expect fix for this in the future?

It is because of pli, pli is outdated.
BH and MeoBoot work very well.
thanks

 

[Armageddon]

After intensive testing the mystery is solved.
This bug does not exist in our image, but in
the SAT lists used by some members.
Missing an extra parameter for this channel.
My friend Dzoni have also found that this bug
does not exist in BH image.

Hi, I can also see a problem regarding recording on some channels on sat 28.2E. For example More 4+1. Seems ok but the filesize on disk is zero. You mentioned that there in an missing extra parameter for the channel. How do I confirm the error and how to solve it? I´ve had that problem on DEBH 1.33 also, but not on DM800 boxes only on Vu+duo. Any Ideas?

 

[Tamaki]

I think that one of the problems with openpli is that it is not OE1.6. but it is has got a own OE (called 2.0 if think).
So, maybe there could be compatibility problems.

 

[malakudi]

I posted the following questions on the 1.3.7 thread but since 1.3.8 was released it didn't receive any response from blackhole team members.

Can we expect any newer enigma2 code? vuplus official 5.3 image is still based on July 2010 enigma2 trunk. Are you going to implement newer enigma2 source code on Blackhole? Or you will always be on sync with vuplus official release?
Do you have any "inside" information about future driver releases and newer enigma2 code support? enigma2 is now switching to DVBAPI v5, is VU going to support this as well?
Latest drivers have some issues (most important is the lipsync bug on vtuner and the problems on playback previously recorded content), is VU driver development team aware of these issues? Are you as a team in contact with driver developers?

 

[Dzoni]

This question and sugestion You need to post in section "original image" that can see Vu coder and give You answer.

 

[angelofsky1980]

Can we expect any newer enigma2 code? vuplus official 5.3 image is still based on July 2010 enigma2 trunk. Are you going to implement newer enigma2 source code on Blackhole? Or you will always be on sync with vuplus official release?

The image is aligned with Vu+ releases.

Do you have any "inside" information about future driver releases and newer enigma2 code support? enigma2 is now switching to DVBAPI v5, is VU going to support this as well?
Latest drivers have some issues (most important is the lipsync bug on vtuner and the problems on playback previously recorded content), is VU driver development team aware of these issues? Are you as a team in contact with driver developers?

We haven't "inside" informations but we have reported to Vu+ Dev team some bugs to correct and some suggestions to implement in future releases.

 

[newfunfan]

About meoboot image installation on /media/usb test result.

If you have a sata HDD in your duo you can make image installation quiker:

After meoboot installation

go to directory media/usb and remove directory MbootUpload
Then in /media/hdd create a directory MbootUpload access right 755
and in /media/usb create a symlink that match MbootUpload to /media/hdd/MbootUpload

This will help a lot it will drop down the number of access to your usb stick ( in fact this is the way BA works the nfi is on HDD even it you install BA on usb)

- After a lot of test you have the installation speed and boot speed depend a lot on the usb you use.
- Another thing always put the ub in the back of your duo and in the upper slot.

Hope it will help some of you

 

[malagas]

About meoboot image installation on /media/usb test result.

If you have a sata HDD in your duo you can make image installation quiker:

After meoboot installation

go to directory media/usb and remove directory MbootUpload
Then in /media/hdd create a directory MbootUpload access right 755
and in /media/usb create a symlink that match MbootUpload to /media/hdd/MbootUpload

This will help a lot it will drop down the number of access to your usb stick ( in fact this is the way BA works the nfi is on HDD even it you install BA on usb)

- After a lot of test you have the installation speed and boot speed depend a lot on the usb you use.
- Another thing always put the ub in the back of your duo and in the upper slot.

Hope it will help some of you

yes, but like the image says, can we istall meoboot directly into hdd or not?

 

[Mito]

yes, but like the image says, can we istall meoboot directly into hdd or not?

Yes, you can.

 

[unisat]

Hi

Can not find" Recording Path" under menu>setup>system.

Where can I find it to be able to set the target for recording.

TIA

 

[unisat]

About meoboot image installation on /media/usb test result.

If you have a sata HDD in your duo you can make image installation quiker:

After meoboot installation

go to directory media/usb and remove directory MbootUpload
Then in /media/hdd create a directory MbootUpload access right 755
and in /media/usb create a symlink that match MbootUpload to /media/hdd/MbootUpload

This will help a lot it will drop down the number of access to your usb stick ( in fact this is the way BA works the nfi is on HDD even it you install BA on usb)

- After a lot of test you have the installation speed and boot speed depend a lot on the usb you use.
- Another thing always put the ub in the back of your duo and in the upper slot.

Hope it will help some of you

How can we create a symlink that match MbootUpload to /media/hdd/MbootUpload in /media/usb.

Would you please explain in details.

Thanks

 

[Mito]

Hi


Can not find" Recording Path" under menu>setup>system.

Where can I find it to be able to set the target for recording.

TIA

You have to enable expert mode in Customize menu:
Menu > Setup > Sytem > Customize > Setup Mode: Expert

Then you will find Recording Path:
Menu > Setup > Sytem > Recording Path

 

[unisat]

You have to enable expert mode in Customize menu:
Menu > Setup > Sytem > Customize > Setup Mode: Expert

Then you will find Recording Path:
Menu > Setup > Sytem > Recording Path

Noted . Thanks.

 

[Matrix10]

to Matrix10

Of course, it works fine on VTI 2.1
What is the problem this time?

You have test the same version you have in VTI image ???
Which version you tested ??

Im not using this plugin but i think we have problems with plugin version and skin coding

So pls info abt plugin version and skin you using in BH and Vti.

I have test with BlackShadow2 and the same plugin used in VTI image.

 

[biscamax]

Fantastic image, fantastic team, excellent job you made. I'm realy glad you back with your magnific image and your magnific support, thank you very much for your hard work.