Hi ttuuxxx; The GUI I was working on would make SFS files from any
combination of directories, partitions, image files, & other SFS files.
So it could be used to merge several SFS files into a single large one.

Hi Mark: Howdy also, I've been tied up with personal stuff for awhile.
I posted at your SFS GUI forum thread, have a look.

I'd like to follow up on some ideas I had a year ago, & finish some apps.
The main idea for work is using SFS files mounted but not unioned.
This way they can be swapped in & out at any time without union problems.
This shouldn't be to hard to do, PATH & LIBRARY_PATH need more entries,
& also a utility to write new menu files on the fly from the SFS's menu files.
This seems workable, do you see any holes or problems with it?

You had the same idea, use generic mounts (number1, number2, etc.).
My thought was that the paths would be preset for these mount point paths,
but if the paths can be changed at SFS mount time then any mount can do.
As always... Puppy needs more loop devices, 16 would be good, 32 maybe?

Thoughts: I loved the idea of a union FS at first, but now I see it as an
end to a means that makes for a complicated & trouble prone system.
2 ways to fix this, Full install solves it but is not as secure as a SFS file.
A small main boot SFS file (like Puppy NOP, except smaller) & a good
SFS file maker (wink wink), so it can make both the main & addon SFSs.
This way .pet, .deb, or whatever can be installed directly to new SFS files.
Extracting directly from the packages to the new SFS file would be best.
The rebuild time for the main SFS file wouldn't be long, even on older PCs.
A browser & utils. are the ONLY apps. in the main SFS, addon SFSs have
the other apps., preferably SFS groups, Games, Office, Servers, Media, etc.

I've recompiled xfreecell to give a 1032x768 display( see attached), and it works in either pup2.16, or pup4. Just extract to / & it should run via xfreecell. Two different versions, one for 800x600, the other for 1024x768 display.

But I still prefer seahaven. Also, AFAIK the only change from seahaven-1.44 to seahaven-1.50 seems to be some autoplay functionality, but in retrospect I find the new autoplay annoying, so I'll re-upload a 1.44 version.

Muggins
Xfreecell in 45 kb ... That's cool. But I think we should keep it compatible with 800x600 screen. I guess your previous compile of xfreecell (1.05a) was made for small screens. But that size was 291 kb. What happend? Is it possible to get the tiny one in 800x600? ... please.

I played with different seahaven resolutions, but ended up the original one. There wasn't too much improvements when enlarging window/cards. And my main goal here is to find those mini-treasures, so 34 kb became more important than several sizes.