If you hold your mouse in the position shown below (and perhaps click and move slightly, maybe with a task open) you will likely be able to crash jwm. However the 701 developer snapshot now fixes this.This is in precise 5.5RC and other versions of puppy also.

I am not sure if it is a real improvement or not but I think it is:
in /usr/sbin/delayedrun, I change line 199 to read:
[ -x "$a" ] && exec $a &
Things seem to run slightly better for me after. This is in multiple versions of puppy also.

I believe I have found a difficulty with java and how it works with puppy. This seems to have started perhaps with a java after 7.07 when at that time I used wary 5.2.2 and could directly enter from the keyboard into a java program which is run directly by java -jar. I just checked the latest java (...

My single thing I can report on is that xload in /usr/bin ought to be a link, since it is also in /usr/X11R7/bin. I came across this because I disable xload so precise will run on older computers faster.

menu/shutdown/power-off computer menu/shutdown/Exit to prompt menu/shutdown/Reboot computer What do I do now? My solution: I had a similar problem with wary 5.1.2 today. What worked for me to fix it was to make the file /etc/windowmanager contain jwm After that all those work just fine. Something I ...

With a fresh frugal install of lupu519, upon initial boot, one is presented with the opportunity to connect via wireless using the simple network connection. The simple network connection however always fails to provide a connection to my network which uses WPA2. The "failed to connect" me...

I noticed that if I run jwm and use rox to copy several files (using several windows) that a crash is encountered booting you out of xwindows. This happens for both the full hard disk and frugal usb install. If you're still wanting to cut down on space a little bit, I'd say reduce the background cho...