Posted: Mon 28 Oct 2013, 16:10
Bill started this thread...where is he??
We started with how to make a sfs from a save file.... if you read it you will see the quick dirty way given with the suggestion to do it with a non running save to avoid xloaded crap and so on . I also mentioned excluding certain folders as a refinement.
Bills and nic007 reasons are probably slightly different for experimenting with this.
I use sfs as the save mechanism and implemented it originally on puppy 2 and later ported it to later versions. The final result includes such refinements you mention though actually the biggest challenge was working it into puppies boot scripts. For Bill and nic007 that full implementation is probably is not needed...which brings me to
nic007 ....
I do not see any other way of loading extra sfs to puppy 4 apart from the zdrv idea or dummy save so I guess a little hacking is needed. There is still the problem of layer order too (I reversed it in my case so the main pup sfs is at the bottom). I also scrapped the puppy 4 init as being too complicated/quirk prone (i found 4 hairy bugs in it and posted solutions when it first appeared) and used a streamlined puppy 2 one instead....but for a simple fixed sfs config file the original script should be tweakable.
As a proof of concept we are treading one step at a time here.
Also the op(s) probably want to keep a pristine puppy and have custom sfs for each machine they have. Another advantage would be the possibility of a save loading to ram in some manner which I do with my implementation with the benefit of being able to remove the flash drive or spin down disks.
These answers get longer...the confusion grows...
mike
We started with how to make a sfs from a save file.... if you read it you will see the quick dirty way given with the suggestion to do it with a non running save to avoid xloaded crap and so on . I also mentioned excluding certain folders as a refinement.
Bills and nic007 reasons are probably slightly different for experimenting with this.
I use sfs as the save mechanism and implemented it originally on puppy 2 and later ported it to later versions. The final result includes such refinements you mention though actually the biggest challenge was working it into puppies boot scripts. For Bill and nic007 that full implementation is probably is not needed...which brings me to
nic007 ....
I do not see any other way of loading extra sfs to puppy 4 apart from the zdrv idea or dummy save so I guess a little hacking is needed. There is still the problem of layer order too (I reversed it in my case so the main pup sfs is at the bottom). I also scrapped the puppy 4 init as being too complicated/quirk prone (i found 4 hairy bugs in it and posted solutions when it first appeared) and used a streamlined puppy 2 one instead....but for a simple fixed sfs config file the original script should be tweakable.
As a proof of concept we are treading one step at a time here.
Also the op(s) probably want to keep a pristine puppy and have custom sfs for each machine they have. Another advantage would be the possibility of a save loading to ram in some manner which I do with my implementation with the benefit of being able to remove the flash drive or spin down disks.
These answers get longer...the confusion grows...
mike