corrupted image files when sourced from box

[dzebrys]

hi,

recently i've prepared own firmware cook where i've included picro osd mod.
the problem i've stuck is that whatever i sourced base files from original picto osd.bin
by mounting it in box or using cramfs-16k it result in some corrupted files.

let say after mounting it i'm tarballing the content of /osd dir to /tmp/sthng.tar.gz.
then i'm moving it to ubuntu where manipulation goes. the problem is that villa_bg.png and
other large bg images are corrupted. the output is not valid png with proper size but image
with all-red-paint content. also there is a bunch of small osd img files with size of 147 B
that seems simillary corrupt [no content just red dot].

does anybody cross that problem? any solution?

here's the link to osd http://wdtv.free.fr/dl/live/picto/default_bg/layout_16:9/lilibabe.osd.bin

br/piotr

[KAD]

only thing I found similiar is images without an extension

if you use filezilla to FTP images into /osd that do not have any file extension
I can almost guarantee it will corrupt the image every time
but that's a filezilla issue and it does not sound like your situation

[recliq]

Please explain what exactly you are trying to do, what you do now sounds a little weired...

[dzebrys]

hi,

i need extracted osd files from picto to include it in custom firmware cook.
i know two ways to do it:
a) copy it to pendrive and restart box
b) use cramfs tool like with firmware unpacking

in both cases i'm unable to got valid png background files from osd.

in case a) i'm using mc to pack content of /osd directory to tarball
so that files are all way handled internally by box. the weird is that
after restart when osd mounts it is ok, proper background is displayed
by box. when i copy it to external nas storage or when tarballing on box
and unpacking on desktop with ubuntu some files seems not valid/corrupted.

off course i've found some workaround but that is dirty and png files have
large size [found jpg background on download site and exported it to png]


br/piotr

[KAD]

here's how I would do it, much easier

boot your root.bin
FTP contents of picto osd from linux to WD
reboot WD to save changes

KAD

[dzebrys]

hi,

i've checked xml files and there is no reference to those png background images i've problem with.
so i think they are already corrupted into osd bin. also most probably the small img files [147B] are
intentionally modified by lilababbe to not show up by dmaosd.

br/piotr

[PaulF]

hi,

i've checked xml files and there is no reference to those png background images i've problem with.
so i think they are already corrupted into osd bin. also most probably the small img files [147B] are
intentionally modified by lilababbe to not show up by dmaosd.

br/piotr

My osd xml files point to villa_bg.jpg

[ceshiwuhao]

Please explain what exactly you are trying to do, what you do now sounds a little weired...

[dsairmt]

copy it to pendrive and restart box
use cramfs tool like with firmware unpacking