Hey guys... How about some SFS files of games?
Quick attachment, & there's lots of games that take up lots of space,
so they fill up the Save file really fast & SFS files solves this problem.
Maybe one for all these simpler games, & one each for FPS & RPG games?
There aren't many SFS files & there should be tons of them.
Let me guess... There's still no SFS file maker GUI?
Top 10 mini GAMES for Puppy 4
-
ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
No not a gui yet but When I was talking to Mu basically a newer way of doing it was made up:)sunburnt wrote:Hey guys... How about some SFS files of games?
Quick attachment, & there's lots of games that take up lots of space,
so they fill up the Save file really fast & SFS files solves this problem.
Maybe one for all these simpler games, & one each for FPS & RPG games?
There aren't many SFS files & there should be tons of them.
Let me guess... There's still no SFS file maker GUI?
He basically made a script the same as dir2pet
this one is dir2sfs
first you make a folder and put your directories in it then type dir2sfs and it builds the sfs, When something is that simple you don't need a gui
I added it to my latest Gslapt for series 3&4
the forum/download is http://murga-linux.com/puppy/viewtopic.php?t=28994
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
Hi sunburnt, nice to read you again 
Were you busy?
Or did you prefer another system meanwhile?
I did some work on a grafical SFS-tool already:
http://www.murga-linux.com/puppy/viewtopic.php?t=26097
welcome back!
Mark
Were you busy?
Or did you prefer another system meanwhile?
I did some work on a grafical SFS-tool already:
http://www.murga-linux.com/puppy/viewtopic.php?t=26097
welcome back!
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
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?
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?
I meanwhile made new versions of my puplet Muppy.
It now has a menu, that detects changes in /usr/share/applications.
This simple technique also can be used by Puppys fixmenus:
http://murga-linux.com/puppy/viewtopic.php?t=26170
So fixmenus would detect new menu-entries, when a sfs is added.
As you don't want to merge them with unionfs, the check had to be extended somehow.
SFS- files could be mounted to /mnt/SFS/
Puppy could have an inbuilt script, that searches there for menu-entries, or "startscripts".
Such an SFS then would provide such folders:
/mnt/SFS/number1/menue-entries/killergame.desktop
/mnt/SFS/number1/menue-entries/boardgame.desktop
/mnt/SFS/number1/startscripts/showintro.sh
So if the SFS would be mounted as
/mnt/SFS/number1
then Puppys modified fixmenus would add menuentries for "killergame" and "boardgame", and execute showintro.sh.
showintro.sh could set PATH and LD_LIBRARY_PATH , and display a welcome-text.
This certainly is doable, and I think it would be great, to reduce problems we still have with unionfs.
Mark
It now has a menu, that detects changes in /usr/share/applications.
This simple technique also can be used by Puppys fixmenus:
http://murga-linux.com/puppy/viewtopic.php?t=26170
So fixmenus would detect new menu-entries, when a sfs is added.
As you don't want to merge them with unionfs, the check had to be extended somehow.
SFS- files could be mounted to /mnt/SFS/
Puppy could have an inbuilt script, that searches there for menu-entries, or "startscripts".
Such an SFS then would provide such folders:
/mnt/SFS/number1/menue-entries/killergame.desktop
/mnt/SFS/number1/menue-entries/boardgame.desktop
/mnt/SFS/number1/startscripts/showintro.sh
So if the SFS would be mounted as
/mnt/SFS/number1
then Puppys modified fixmenus would add menuentries for "killergame" and "boardgame", and execute showintro.sh.
showintro.sh could set PATH and LD_LIBRARY_PATH , and display a welcome-text.
This certainly is doable, and I think it would be great, to reduce problems we still have with unionfs.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
LD_LIBRARY_PATH, I knew I didn't have it right... It has been awhile.
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.
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.
?@changturkey,
why not start a new heavier games thread.
@zigbert,
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.
why not start a new heavier games thread.
@zigbert,
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.
- Attachments
-
- xfreecell-1.05b-800x600.tar.gz
- (44.78 KiB) Downloaded 668 times
-
- xfreecell-1.05b-1024x768.tar.gz
- (44.79 KiB) Downloaded 712 times
Last edited by muggins on Sat 17 May 2008, 08:52, edited 1 time in total.
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.
Sigmund
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.
Sigmund