KDE installtion gives this error.

[softappweber]

Error: No Configuration File Found | No default or UI Configuration Directive Found!
Boot:


I am using YUMI Multiboot loader (My favorite) to use different distros with USb. But I only use Porteus Cinnamon as my main OS. I was eager to use KDE and Kiosk version of Porteus, but when I load their iso files on USB using YUMI and then try to run as I run Porteus Cinnamon, it does not start and both of them give me this error.

Can anyone tell me origin of this error? I want to explore all the flavors of Porteus. I do not understand and know why they call it 'desktop environments' :-). Please help, your help will be greatly appreciated.

[Ed_P]

Hard to debug without seeing the boot menu. Since YUMI is creating the menu you should ask them why it doesn't work with the Porteus ISOs.

[beny]

hi, if you have the last porteus 5,you can only if you wish add the desktop environment to the porteus base but without the changes option, you have a different way to manage kde or xfce or cinnamon so with changes you have only a lot of issue,i think but isn't confirmed you can't run two version of the same system located into one root.

[Ed_P]

Actually it's possible to test different DEs by just downloading the DE's 003 file and putting it in the base system's /modules folder and adding the noload= cheatcode to the vmlinuz boot parms for the base DE, for example noload=cinnamon, and don't save changes when exiting. Actually that means boot with the changes=EXIT cheatcode also so changes are only saved when you exit.

If you test a lot of DEs having boot parms similar to this makes setting up the menu easier.

Code: Select all

noload=kde;jinn;lxqt;xfce;lxde;mate;open;changes  changes=EXIT:$linux_folder/changes/50save.dat

[softappweber]

Actually it's possible to test different DEs by just downloading the DE's 003 file and putting it in the base system's /modules folder and adding the noload= cheatcode to the vmlinuz boot parms for the base DE, for example noload=cinnamon, and don't save changes when exiting. Actually that means boot with the changes=EXIT cheatcode also so changes are only saved when you exit.

If you test a lot of DEs having boot parms similar to this makes setting up the menu easier.

Code: Select all

noload=kde;jinn;lxqt;xfce;lxde;mate;open;changes  changes=EXIT:$linux_folder/changes/50save.dat

I think this is the solution for my problem. What I understood from replies is that I need to load few files from these two DEs into root folder of my Porteus Cinnamon and apply cheatcodes and then try to run it from RAM. This method can mess up with my Porteus Cinnamon and that's why I do not want to apply it.

Thanks everyone for replies. Again I needed step by step guide to do it, since I am naive I can NOT do it just by reading instructions.

By the way, would anyone please tell me ; How do these desktop environments differ from each other? What features, functions they have which are different from each other? Why do these different DEs exist? what's the purpose?
If I can know it, I would never trouble to try any other DE other than Cinnamon if it is not useful for me. :-)

[Ed_P]

I would never trouble to try any other DE other than Cinnamon if it is not useful for me.

Well, now you know how to try them, one by one and see which ones are useful for you and which ones aren't. Do you like one with the taskbar on the top or on the bottom? Do you like one with a lot of icons or one with no icons?

"trouble"ing to find out is how you learn to not be "naive". And downloading a DE module and adding a boot menu doesn't take much time. Here's my KDE one on my Cinnamon system.

Code: Select all

    set iso="/ISOs/Porteus-CINNAMON-v5.0-x86_64-221210.iso"



menuentry " Porteus 5.0 ISO - KDE - AF+"  --class slackware   --class icon-porteus  {

     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules noload=cinn;jinn;lxqt;xfce;lxde;mate;open;mychanges"  #kde5; 

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
     }