Forums

1958 bug are in openpli image i dont now if this bug is fixed in new images from openpli, ps the splash_cfe_auto.bin have i get it from code.vuplus.com

Edited by janejak, 22 January 2015 - 13:58.

but u can make ur own splash_cfe_auto.bin just take a pics of anyting u want and save as bmp file it have to be in 300X300DPI and sice 720X480 pixels and then rename the bmp file to splash_cfe_auto.bin then u get ur private splash screen :-)

Does anyone have a idea why in the images of Vu (so not in the OpenPLi images) there is a splash_cfe_auto.bin in the Ultimo and Uno but not in the Duo and Solo?

Edited by 40H3X, 11 July 2015 - 15:31.

Ja: die boxen ondersteunen het schrijven van splashbins niet.

Das helder dank!

English!

sorry

I suggest some other images are so proud to demonstrate that it is possible to overwight the manufacturer's splash screen...

Whatever the reason: it would be very easy for PLi to embed the manufacturer splash screens in the image folders. This would stop this endless row of asking the very same thing.

It is for this very reason that ViX decided to do just that ages ago.

There is a point where an image maker should not add workarounds for stupid things a user might be doing. Fix the problem not the symptom.

It all goes back to the principle that once you'll start "working around" there is no end to it! In this case, it concerns the splash screen. Which IMHO is hardware specific and should not be changed by the image. When an image maker decides to change it, they should at least have the courtesy to build in a restore of the splash screen.

There is a point where an image maker should not add workarounds for stupid things a user might be doing. Fix the problem not the symptom.

Well, the only 'stupid' thing a user does in this respect is flashing another image then PLi or ViX (at least as far as I know all other imagebuilders add their own splashcreens).

And IMHO the ViX-solution (adding the factory splashscreen to the image folder) is a very simple and good cure for this common 'stupidity'

And I'm not 100% sure that the above remarks will convince all imagebuilders that they should stop doing this...

Pricesely.

Adding the original manufacturer splash screen to your image zips would have no negative consequences to anyone, only positive ones.

Those who already have the original bootlogo would never notice anything while those who swap images just to see how bad the other images are compared to OpenPLi are now sort of penalized for their comeback to OpenPLi. The original manufacturer logo in the OpenPLi image zip would cure the problem without any damage to anyone.

Afaik you can still flash splash screen on Xtrends. But you have to press CH- on front panel and not ok like for images.

But I need to wait for the prompt on the ET display, right?

Unfortunately no prompt comes on.

Yes, you need to wait for the prompt. Try other usb stick. And perhaps also copy bootloader to the stick.

I think adding the manufacturer's splash screen to the image is not a good idea with just the reason other image are overwriting it... Note that the splashscreen is written in a limited reserved space of flash...
Edited by littlesat, 15 July 2015 - 05:44.

Well, it's your choice not to help people. And remember you're the only imagebuilder not doing this.

No idea what 'the limited space of flash' has to do with anything; it's filled anyway.