Posts by giorbak

    Hi odem2014


    Could you fix the information window that resizes based on the content?

    If the information is too long, it exceeds the screen limits, making it unreadable.

    Can you restrict it within the screen boundaries and enable text wrapping if it is too long?


    Thanks


    7.jpg     8.jpg


    9.jpg     10.jpg

    My fstab files are 100% correct. You can verify that in the following images.

    You're using UUID for mounting, which is the recommended method, but using the partition name (e.g., sda1) works perfectly fine.


    I have no issues with the Multiboot Manager in any image. All of them display the correct order for the images.

    There is only a problem with the Image Backup in OpenATV.

    I see that you have OpenATV-7.6. Did you try to do a Full Backup with it? If so, what does it show? Share a screenshot.


    1.jpg  2.jpg  3.jpg


    4.jpg  5.jpg  6.jpg

    All partitions are correctly mounted in the fstab file. I have 50 slots on Octagon sf8008 and 30 slots on Edision osmio4kplus.

    I didn't use a script to create the slots, but did them manually with the program "Partition Wizard"; also manually the STARTUP files.

    The order of images in the "Image Backup" window is: 1, 10-19, 2, 20-29, 3, 30-39, 4, 40-49, 5, 50, 6-9 (they are not mixed up).

    As you can see, the problem is due to OpenATV that not numbering the slots correctly.

    If I remember correctly, in the old OpenATV versions, there was the same issue with "Multiboot Manager" and was fixed some time ago.

    odem2014


    If you have free time and it's easy for you, can you correct the order of the images in the Full Backup window?

    It's not something necessary, but it would be nice if the list of images was organized.

    Image: OpenATV - Skin: Aglare-5.6


    Thank you


    1.jpg     2.jpg

    Ανεβάζω την Ελληνική μετάφραση για τη νέα έκδοση του AJPanel.



    Edit

    Υπάρχει και νέα πολύ σύντομη ενημέρωση του AJPanel με μια μικρή διόρθωση.

    Ανεβάζω αναγκαστικά τα νέα αρχεία για να έχετε Ελληνικά στη νέα έκδοση.

    It can be fixed in the next version. Although some buttons are there just for the sake of order, maybe in a next version I will use them for some other function. For example, the red exit button is not needed at all because exit works without the red button, simply using the exit button on the remote. But I put it in, maybe I will use it for some future function.


    I understand, and I would be grateful if you implement it in a future version.


    However, even if you need to change the function of some coloured buttons, it would be better if they were assigned to the order of the remote control.

    Imagine if I gave you a keyboard with the keys messed up, and you had to type a text. You'd write it down, but it would give you a lot of trouble.

    ciefp


    Thank you for the wonderful and useful add-ons you created.


    Since we use the colored remote control buttons, it would be preferable to place the corresponding buttons (Red, Green, Yellow, Blue) in the same order on the screen,

    so that we don't have to look at the remote control every time we press a button.

    We've learned that order, and I've noticed that I often press the wrong button because out of habit I don't look at the remote control.


    Thank you

    I added protection to the empty slots to prevent the box from getting stuck in the boot, if the script is executed.

    To operate, the script filename of empty slots must contain the word "Empty" (case-insensitive), e.g., "Slot-01 - [Empty].sh", "Slot-1_empty" etc.


    If you select a slot that does not exist in your system (e.g., Slot-70) you will receive a message.

    Also, if you select an existing slot but the STATUP file is missing, you will receive the corresponding message.


    1.jpg  2.jpg  3.jpg

    I don't think the use of Mutltiboot with scripts is interested in most users, but I will upload them for "curious" ones.


    In the zip file below, you will find the folder "Multiboot_Manager", that contains 70 scripts for 70 slots.

    You can use as many files as the slots of your system and delete the rest ones.

    It's recommended to place the folder on the hdd root to make easy access from all images. Change the attributes of the directory and the contained files to 755.

    You can execute the script you want, and you will boot on the corresponding image (slot).


    If you want a graphical interface, you can run the scripts with the AJPanel File Manager. Bookmark the "Multiboot_Manager" directory to easily transfer to the files.

    The files are simple scripts and are not able to read the image names and will only display the slots.

    You can rename them by writing the appropriate name for each image, and the empty slots can be named [Empty].

    Do NOT boοt in an empty slot because the system will hang on startup. In case you do that, you can come back with the Recovery menu.


    Edit

    Don't forget to rename the script in case you install a new image or upgrade an existing one.



    1.jpg     2.jpg


    3.jpg     4.jpg

    The given commands work on oe-alliance images only. If you try on pli-based image, they will not execute.

    The path for oe-a is "/boot" while on pli is "/media/mmc" (at least on sf8008).


    I created a script that checks and uses the appropriate directory of the STARTUP files and informs which slots you can boot into.

    If you select a slot within the limits, but the appropriate STARTUP file is missing, you will be notified.


    You will have to run the script exclusively on Telnet to be able to select the desired slot with the keyboard.

    I recommend putting it on the hdd root and giving it 755 permissions so you can access it from all images.


    If you want to boot directly from the image without using Telnet and PC, I can create a list of 50, 60 or 70 scripts, and you run them through AJPanel.

    I've done something similar in the past with "old friend" Dreamboxd dm800se (see picture).

    In this case, only the slots without the image name will be displayed (in dreambox I entered the name when I was flashing an image).


    Multiboot.jpg     Dreambox_multiboot.jpg

    Known old problem of Aglare-FHD.

    Until the issue is fixed, if you want to flash in a slot not shown in the list, go to the "/boot" directory and delete or rename the large STARTUP files.

    Otherwise, go to the end of the list and with the arrow keys on RC calculate the slot you want to flash at the risk of deleting an image.

    I did this several times, fortunately without any problem.


    1.jpg     2.jpg


    3.jpg     4.jpg