Puppy Linux Discussion Forum

Congratulations!!

I think not all of this is needed .

#gunzip easy-3.4.7-amd64.img.gz ( unpacking image )
#truncate -s 2G easy-3.4.7-amd64.img ( make it bigger )
Place on Ventoy stick

On the latest version the image is not compressed so no need to unpack.
I think that in this case the script ...

I'm not understanding.

I have a 4G USB stick that I wrote Easy 3.4.7 to w/ Win Etcher. That works just fine So, Easy is able to do whatever it needs to do on that little stick.

The problem seems to be that on a stick w/ even more 'spare room', the 16G Ventoy stick, Easy can't find a place to ...

The error you see is very logical.
As easy is made to write to a partition on an usb drive that is grown at first start.
The initial partition in the .img file is very small and easy is not made to grow the image file .
You could make the image bigger ( something like dd if=/dev/zero bs=1M count ...

First cross posting is not needed nor wanted!
Is PI4 still powering with microUSB ? IF so it would be most likely a bad contact there.
I Don't think your power supply is failing 5,25V is inside tolerances , where did you measure?
Can you measure the voltage and possibly the ripple on the IO header ...

Hello @BarryK .

filemnt is broken for the old encrypted puppy save files! Error : "losetup-FULL: invalid option -- 'p'"
In fact losetup is missing -p and -e options!
Cryptsetup in the build would be nice so LUKS encryption would work.
Is there a reason why Ciper blowfish is not in raspberry pups ...

Starts OK on my "AMD Sempron(tm) Processor 3000+" (only 1 core) !
Only 2 bugs I see!
1: I have to select the sound card every time I boot "Card 0 : V8237 [VIA 8237], dev 0" or 1 both work to next boot.
2: Old encryption is broken filemnt script won't mount .2fs encrypted files!
The problem is the ...