@ belham2 Hi belham2 simple (dirty) trick: unsquash -> take out the folder with the firefox binary, rename it FF (to keep it simple) place it in /opt. In /usr/bin make a small script: firefox, with the content: #!/bin/sh exec /opt/FF/firefox "$@" and that's all. It works 100% with no conta...

Hi Barry, and thank you for your reply. BarryK wrote: I can't remember, with earlier releases of Quirky, 8.7.1 and before, did I build it with q.sfs inside initrd.q? Well, don't know about 8.7.1 but I have both April-7.0 and April-7.2. Here is the April-7.2 iso and what is inside, just initrd.q and ...

Hi Everyone, To Barry and TiredPup: I had the Kernel Panic by installig manually in one folder named "q881" the 3 files: vmlinuz, initrd.q and q.sfs. By examening the older Quirky, April-7 realised it had only 2 files: vmlinuz & initrd.q, the latter being quite large (180MB). Of course...

Why the panic?

Finally somebody has common sense, not just about usb stick labeling.
Thanks Barry!

@perdido

Try "#!/bin/sh" NOT "#!/bin/bash"

if i remember well, taz doesn't like bash,
only ash.

Tom

Hi SAGE, Put this little script in your Startup folder, and name it "au.sh" (or any other name) : #!/bin/sh aumix -v 90 aplay /usr/share/audio/2barks.au & exit You'll never will have sound problems. Values are from zero to 100. Ilike'it around 77-80 which is little bit higher than the ...

Thank you Jürg for the report, looks good. I still don't quite know how the UEFI method worked, did it work smoothly or you had to make some changes to the reFind configuration file? Thanks. To don570: Hi Don, and thank you for your observations. You are right, the Optiplexes are basically similar, ...

to lp-dolittle: that's exellent news Jürg. I'm glad you succeeded and congratulations. Just out of curiosity I'd like if you'd supply some details about the machine (PC) you used and wheather it has any internal drives or only this external one. I'm asking this because by doing some more experiments...

In my last post I left out 2 lines. The correct code is: timeout 33333 scanfor manual menuentry "EASY-2.1.6" { volume LINUX loader /E-216/vmlinuz initrd /E-216/initrd icon /EFI/BOOT/icons/os_easy.png ostype Linux options "rootwait rw vga=792" } sorry

Hi Jürg, Let'say you have an internal drive with 3 partitions. They are called sda1, sda2, sda3 and we want to install EASY-2.1.6 on an external USB drive. 1) UEFI Take 1 anything USB: memorystick or external drive just large enough to fit 3-or 4 times the easy.img's size. 8GB is more than plenty. T...

Hi lp-dolittle , apologies for not getting back sooner, I was (still is) under the weather. That external ext3 drive should be exelent, all you need is a boot loader on it and setting the bootflag on, with gparted. I recommend extlinux which is what I use in the past 8-10 years. It is the simplest a...

Hi Oui , you are right: " conditions and usages of each Operating System are very different... " but I was writing strictly about my experience with PeasyWifi in EasyOS, both Pyro and Buster. And as the name suggests, it was designed specifically for wireless connections, although it works...

To Barry & all, regarding wireless network-managers. My best experience hands down is with PeasyWifi (PWF). After trying out all of the others in the last 2 years sns, frisbee, super-sns, nm-tui, etc. this is the fastest and most consistent little program. It always works, even if I remove all t...

To Barry, I forgot to tell that the removal of symlinks was done in Buster 2.1.5 with SM-2.49.5. Chromium_75.0.3770.142-bk1_amd64.sfs was used in /opt/ simple script in /usr/bin: chromium exec /opt/Chromium/chromium --test-type --no-sandbox "$@" Testing once again, it turns out only libnss...

jamesbond,
you are a stable genius!!!

I just removed these links from /usr/lib/
libnspr4.so
libnss3.so
libnssckbi.so
libnssdbm3.chk
libnssdbm3.so
libnssutil3.so

and now chromium is working like new!
Thank you, and thank you Barry!