☆ NeoBooT ☆
-------------------------
For lovers of experiments and enjoy the new
♤ Let's differentiate between the word "multi-boot", and the names of the plugins and "multi-boot" add-ons that are available for Enigma OpenSource devices, and the most famous of them are (Open Multiboot - Egami Bot - Opd Boot - Neoboot)
There is also NFRxboot, which is located on the picture NFR
And change the plugins of the Dream MeoBoot and MMBoot devices (MeoBoot and MMbooT))
If we rank them in terms of capabilities and preference (from my point of view... you may disagree with me)
- Neoboot
- Egami Boot
- Opd boot
- Open Multiboot
The genius of the bluegis and the developer is manifested....
In designing the blogs in a smart and advanced way from the rest of the other multi-boot blogs, or you can say that he was able to mix the best of all the other blogs in NeoBoot
This appears in more than one place
- We can say that this is baryallen now for the creator Gutmin, but for the VU stb
- The plugin does not contain a menu to move to the images like other blogs, but from within the plugin itself
And when choosing any image from his position on the plugin , he injects the bot files into it and takes off on it...
Therefore, the device considers it the original image on the internal flash, and from that you can install two bootloaders on this image that is installed on the external to contain other images.....
- The Neoboot boots and plays the image on the external flash twice as fast as the Open Multiboot boot, which means that you will have half the time to enter and play the image on the external flash if you use the Neoboot
♤ Through Neoboot, it is possible to install images of other devices on the VIEW devices, including images of devices (Novaler - Octagon - Giga Blue - Zigma) original images of the devices downloaded from the difference site and not modified
♤ If we talk about the neoboot blog, we will find very high jobs and capabilities in it
Among them, for example:
• Owns 6 different skin
• Additional feed can be updated on photos
• You can erase the password from it if you forget it
• The IPTV player can be updated on all uploaded images
• The TV list can be updated and copied to all images
• Unused languages can be erased to reduce space
• It is possible to solve problems with the protocol (ftp) on external images
• The latest images can be downloaded from the Internet and installed on the device
• Allows installing custom images for other devices with the same processor
• It is possible to save and restore images (Backup & Restore).
• It was originally designed specifically for the VIEW devices and supports 15 models of it, that is, all models
• The blog version can be updated from the internal image for all the external images
• Swap and mount can be done through the plugin for external memory (hard - flash memory).
• It is possible to install more than 9 images on the external other than the image of the internal flash (an infinite number according to the available space)
• The problems of wireless definitions on images can be solved by copying the drivers for the image on the outside from the image on the internal
• Each image on the external is treated as if it were on the internal flash, and it is allowed to install on it two other multiple bootloaders, on which images are installed on the external
To download images for installation on Neoboot, you have two ways
* The first method is the traditional way to transfer the compressed zip images that you have previously downloaded to the Neoboot upload folder, which is (image upload).
The second method is online
By pressing the red button (download image), a message will appear asking you to install Plugin Flash Online
It will take you to the page to download the most famous pictures of the teams, and after choosing the device, you can download the version you want
The blog will ask you where you want to download the image, and you will select the Neoboot folder for the images to start downloading.
Notes and recommendations:
-------------------------------------------
You will notice the plugin connection to the Internet when you enter the neoboot interface to install an image or to move between images
It is contacting the developer server to verify the vip code and it takes 5:3 seconds and the user does not feel it
But when there is no internet, the spinning wheel will start and freeze a bit until the message that the connection failed appears and that the plugin is not activated
When all settings are finished, press the green button to start installing the image
The device takes approximately 1:2 minutes, depending on the size of the image or the packet, in which it is decompressed and the files referred to on the settings page are transferred until completion.
The completion message appears, whether the operation is successful or unsuccessful, and the reason for the failure will appear, and it is often the inability of the neoboot to decompile the file due to an error in compressing the image file or the backup
To remedy this (decompress the backup by any decompressing program and then rename it after reviewing its contents and re-compress it again)
When booting from any image fails, the plugin returns to the internal flash image
The Neoboot interface shows the installed images that can be moved to
And it shows the uniqueness and excellence of the neoboots, as there is no start page like the rest of the blogs that appear upon take off to be selected from
But it is the interface of the plugins. From any image, it is transferred to any image directly within approximately one and a half minutes, which is the boot time.
- To install an image, delete an image, or upgrade the blog version, this is done only from the image on the internal flash
- The developer recommended using the Openpli image on the internals of all devices when installing the plugin and gave the possibility to install on the Egami image for other devices
- It is possible to try and succeed by installing on other images, but it is possible in the future or with any updates that stand, and when you return the problem to the developer, he will respond to you. I do not support other than what I recommended of images on the internal
- To avoid the problem of inodes (indexing pointer), which is the problem of not being able to install images or add-ons and giving a message that there is no space with the presence of space on the outside
It is formatted external memory was flash memory or hard through the command
mkfs.ext4 -i 8400 /dev/sda1- There are experts who recommend leaving the image on the internal raw, and nothing is added to it from the file of channels, no additions, no skins, not even updates to preserve space so that the picture works in a typical way because it is very light
- And there are those who do not follow that due to the large internal flash size for some devices and makes a file of channels, favorites, add-ons and subscriptions from IPTV and, through Neoboot, transfers this to any image that it installs on the external
- It is recommended to use a USB flash memory v3.0 that does not exceed 16 GB or an external hard after you make the settings through the device manager and download it from the Openpli Feed
- Do not upgrade to the latest version without a need, if the version works for you in a good way, it is only updated if there is an addition that is not available to you except for the upgrade
- Sometimes a message may appear that the plugin is not activated, you will write the removal code and come back and then write the activation code again, and it will work for you completely
- To show and use your image from other multiboot folder
You can take advantage of your old folder of your previously installed images from OpdBoot, Open Multiboot, EgamiBot, or NFRxboot
Download on the external, for example, an image of openatv, then activate the open multiboot on it, and after activation, move the files of your previously saved images folder to the multiboot folder
In the end, you will find that you are installed by the neoboot, an image on which the Open Multiboot is installed, and other images are installed on it
When you reinstall the plugin and you basically already have its folders, you must rename it with a different name by adding to it, for example, the hashtag # until the installation is completed and returned, otherwise it will be deleted
You can apply this to various images with various add-ons for multiple boots
When this is successful, you will find when you enter from the neoboot to a image that has its own bootmanger on it
The appearance of the multi boot menu for the images installed on it to move between them, including what is considered the image of the internal flash, which is the image installed by the neoboot
