Mark - I finally got it loaded, but there are serious problems with the keyboard. Neither the option for the UK nor (save us all!) the US are responding correctly, possibly not loading properly. The numerals are only obtainable by holding down the shift key and I couldn't set my network because I couldn't find the full stop (point, period). There were a lot of strange symbol keys present, but these didn't seem to correspond to any recognisable European or Asian script. This is fairly fundamental, probably meriting an incremental version issue rather than a patch? Indeed, I cannot d/l any patches until it's fixed.
[ If you need a selection of UK keyboards, let me know how many! I may have a French one somewhere, too. ]

Otherwise it is totally brilliant and you deserve a lot of congratulations. Glad to see the TuxRacer has become de rigeur at last - apart from Solitaire, and this one I don't know why small distro writers bother with some of the other cr*p listed under their token games offerings. Waste of space in many cases.

But, but, but - once you manage to refine and debug everything, I would strongly advise that you reinstate the full install to HD option. This one really is worth it. This facility should make it viable on an even larger range of HW.

Stranger and stranger. Seems to be some machine-specific issues, possibly associated with memory capacity? My biggest, fastest machine runs OK with everything loaded including KDE, but lesser beasts seem to give a range of different issues, including k/b mis-function, lock-ups, etc. Initial selections can give some strange behavior, too, but not reproducibly. Await the results from additional testers. But it's still terrific and rivals the major distros now.
In the meantime, it would be helpful to have an assessment of the minimum memory requirement for the full monty, please.

I ran it on a notebook with I think 256 MB (don't have it here).
It ran fine, but I used a 500 MB swap-partition.
Older Muppy-versions freezed the computer without swap, when I ran OpenOffice.
(when the memory-bar in Icedock reached maximum).

Thanks for that, Mark. In the interests of speed of testing, I loosened all the HD cradles to run the CD, so no swap. Assumed those machines had enough main memory. Perhaps not. Bigger, does, of course, bring its own penalties! Perhaps a warning is needed in the initial boot screen so that new converts don't get a bad impression?

Apart from laptops, which I tend to avoid, there's a simple answer to using the full version of Mark's masterpiece. Fit one older CD drive to read and boot from and fit a more modern DVD/CD-RW/DVD-RW for running, saving, watching, burning stuff. Ideally, choose an older drive made after ~1997 with a speed >x20 if you want to boot to a CD-RW/DVD-RW image, but almost anything will boot to a CD-R. Nobody wants old CD drives any more so they can be canabilised from the local skip/tip/dumpster; around 50% are likely to be still working!!

Would it be possible to auto-detect whether to use Xvesa or Xorg depending on the graphics card? There are problems using Xvesa with Intel chipsets, yet Xorg works just fine so I was wondering if it would be possible to revert to Xorg if an Xvesa functionality probe fails._________________Jam

Congratulations again on a great version of puppy. It is running very fast on my 400MHz processor with 192MB RAM and 500MB swapfile. Faster than Puppy 2.13. and also KDE is extremely usable for the first time ever on this PC

I wonder what I am doing wrong here with the icewin trayicons. Even if I associate an application-specific icon with the shortcuts contained in the /root/trayicons folder, they do not appear in the icewin tray even after having been refreshed using the >> and << buttons. Not an urgent problem. Have a good day!

Best regards

tronkel (Jack)_________________Life is too short to spend it in front of a computer