1306 replies to this topic

[Odyssey]

a small bug with the Russian language.

I do not know where the problem is in the plugin or pli 4.0 ...

p.s. red color is not Russian language = it is Belorussian language

[Pedro_Newbie]

That's my fault, I made some (wrong) google translations.

You could alter the wrong translations if you like in the language pack. If you are willing to correct it I can add it to the backupsuite.

Here's the language pack

Attached Files

•  BackupSuite_RU.rar   3.11KB   18 downloads

[westsib]

Here's my language pack.

Think also fits...

Attached Files

•  BackupSuite.zip   3.1KB   22 downloads

Edited by westsib, 28 September 2013 - 22:49.

[Pedro_Newbie]

Thanks it will be included in the 13.2 version

[dym1]

Here's language pack SK.

 

 

 BackupSuite.rar   5.77KB   9 downloads

 

[Pedro_Newbie]

Thanks, it will also be available with the next version (13.2)!

[Pedro_Newbie]

Here's the new version with the above updated/created language packs (Russian and Slovak) thanks to Dym1 & Westsib

Attached Files

•  enigma2-plugin-extensions-backupsuite_13.2_mips32el.ipk   48.97KB   36 downloads

[Odyssey]

it was necessary to write to me, I initially did Russian translation of this plugin

I did the translation - it is correct and meets the linguistic meaning

Attached Files

•  BackupSuite_RUS.rar   3.02KB   4 downloads

Edited by Odyssey, 29 September 2013 - 16:24.

[Pedro_Newbie]

I forgot who made the first translation. The translation provided in your post is this the right one, I can't judge the translations so I'll have to trust on the judgement of the Russian users.

 

I will update the next release (13.3) with your language pack

[Pedro_Newbie]

OK, new version 13.3

 

Attached Files

•  enigma2-plugin-extensions-backupsuite_13.3_mips32el.ipk   49.09KB   60 downloads

Edited by Pedro_Newbie, 29 September 2013 - 16:52.

[Odyssey]

I found a small bug in my translation.

update mo and po files

 

Attached Files

•  BackupSuite_ru.rar   6.33KB   6 downloads

[Pedro_Newbie]

Thanks, in the next version it will be included. I removed an extra \n at line 166, this \n isn't there in the original text, poedit complained about it

[Odyssey]

Thanks, in the next version it will be included. I removed an extra \n at line 166, this \n isn't there in the original text, poedit complained about it

I added it to split the text into paragraphs - for better readability.

[Odyssey]

I have a request, the main plug-in window to make transparent to see the background of the current program

[Pedro_Newbie]

I don't see possibilities to do so, but, depending on what skin you are using, you can see PIG (Picture in Graphics) so a small version of your TV program, like in PLi-HD.
Or you'll have to make a skin_user.xml with an modified console screen to make it transparent.

[bosspapy]

Hi Pedro

I'm trying to install your plugin on a decoder Amiko Alien with bassd on image openpli. image.

Did I state that the decoder has a Sti (SH4) and has a boot sual-Spark and Enigma2.

Clearly I am interested in solving the problem in E2.

I installed the package mtd-utils for sh4

This is the result of the usual command to check MTD:

SPARK7162: ~ # cat/proc/mtd

dev: size size erasesize name

mtd0: 00100000 00020000 "uboot"

mtd1: 00020000 00a00000 "Spark kernel"

mtd2: 00020000 "Reserve0" 00700000

mtd3: 00200000 00020000 "Reserve1"

mtd4: 16c00000 00020000 "Spark user 's"

mtd5: 00800000 00020000 "E2 kernel"

mtd6: 07700000 00020000 "E2 user 's"

SPARK7162: ~ #

the MTD files are located in the/dev folder as nandump and nandwrite binaries are built into busibox and are achieved with a simlink

You wonder if there are any conditions to run the plugin, if so, you can modificarmi the sh file of your plugin?

Thank you

bosspapy from Italysat team

 

 

[Pedro_Newbie]

• you'll have to provide the path used one the USB-sticks when flashing like the Xtrends use e.g. /et9x00/<files>, the VU's use /vuplus/duo2/<files> etc. and change the $MAINDEST accordingly
• determine the used filenames like e.g. kernel.bin, rootfs.bin, e2-rootfs.jffs2, e2-kernel.bin or whatever name used and any other file needed to flash.
• you'll have to determine the make and model of the box while running the backupsuite.sh by e.g. cat /proc/stb/info/boxtype (if present or any other way to determine the mark/model) and feed it to $MODEL or manipulate it to suite your needs, or hardcode it with MODEL=<the required name>
• for the kernel dump use $NANDDUMP /dev/mtd5 -q > "$WORKDIR/vmlinux.gz"

 

If you change the current backupsuite.sh accordingly you would get a whole end may be even without errors but you should test run and report back with the log.

You can change the ET's parts in the backupsuite.sh to test it or use the backupsuite.sh I made for you last may for the Hypercube.

[bosspapy]

• you'll have to provide the path used one the USB-sticks when flashing like the Xtrends use e.g. /et9x00/<files>, the VU's use /vuplus/duo2/<files> etc. and change the $MAINDEST accordingly

            AmikoAlienTriplex use folder enigma2 

• determine the used filenames like e.g. kernel.bin, rootfs.bin, e2-rootfs.jffs2, e2-kernel.bin or whatever name used and any other file needed to flash.

• names files in the folder enigma2 aren't   e2jffs2 .img  and  ulimage (should be a loader of 2,003 kb)
•  
• you'll have to determine the make and model of the box while running the backupsuite.sh by e.g. cat /proc/stb/info/boxtype (if present or any other way to determine the mark/model) and feed it to $MODEL or manipulate it to suite your needs, or hardcode it with MODEL=<the required name>
  
  OK  I update the names of the two variables
•  
• for the kernel dump use $NANDDUMP /dev/mtd5 -q > "$WORKDIR/vmlinux.gz"

              Yes OK !
 

If you change the current backupsuite.sh accordingly you would get a whole end may be even without errors but you should test run and report back with the log.

You can change the ET's parts in the backupsuite.sh to test it or use the backupsuite.sh I made for you last may for the Hypercube.

Of course, just finished the test or if there are any mistakes can you please post the log

PS: I have made changes but I get an error on liblzo2.so. 2 library: file too short.

I downloaded libraries for SH4 on git for debian, probably there is a problem.

Anyway I'll update on developments and to getting things done I am attaching the logs.

Thank you for your courtesy

[ColinB]

Hi Pedro_Newbie,

 

thanks for your excellent plugin for XP1000.

 

I noticed a small problem when I looked through my backups. The image version file shows openpli-3.0 when I am backing up openpli-4-0 and it shows the backup date not the image date that is shown in Menu_Information_About

 

I ask about the date because if I need to go back to and older Image I cant tell from the image-version file how old it is.

 

Thanks again

[Pedro_Newbie]

You're right, the text openpli-3.0 is/was hardcoded, I shall correct this (probably just strip the version -3.0 part)

It is intended to show the backup date and not the image date.

May be I could consider to change this IF I can find where the information is stored