If I boot Puppy from a CD on a computer with no OS can the sf file be saved to disk? and if so how do I access it to save a backup copy?
Thot maybe I should ask a dumb question B4 trying something stupid.
Questions re: Puppy on a Computer With No OS
If you boot the CD from a CD burner, the save file can be saved on the CD! Better yet, use a DVD if the computer has a DVD burner, because they work better for multisession. I've been running various Puppies from multisession CD and DVD for about 7 years.
Alternatively, the save file can be saved on an internal hard disk if the computer has one, or an external (USB) flash disk.
The computer should have at least 256 MB of RAM. That's about the only hardware restriction to run Puppy in a computer without a hard disk. More would be better.
Alternatively, the save file can be saved on an internal hard disk if the computer has one, or an external (USB) flash disk.
The computer should have at least 256 MB of RAM. That's about the only hardware restriction to run Puppy in a computer without a hard disk. More would be better.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: Puppy on a Computer With No OS
Yes you can because puppy is an OSDande wrote:If I boot Puppy from a CD on a computer with no OS can the sf file be saved to disk? and if so how do I access it to save a backup copy?
Access by running puppy
Using puppy you can try stupid things, too.
This comp is restricted to boot from a CD or the HD only - odd MB - can't change the boot options. Don't have a DVD on this particular comp. I agree a DVD would be better. Maybe a whole different comp?
But I don't see how there is room on a CD. Here is what I found and it makes no sense to me.
Just using the Slacko 533 looking at the properties of the CD that I burned from the ISO I get 115 MB used and NO MB Free! But the CD is rated for 700 MB. Where did all the xtry space go?
Not only that but the files I did copy to Flash from the HD were:
Slacko 533 2fs - 512MB
and Slacko 533 sfs - 109MB.
That's 621 MB. Plus the original 115 is 736 MB. Plus I sposed the .2fs would grow with time? Have I gone off the deep end here? Something tells me I'm a bit wide of the mark.
But I don't see how there is room on a CD. Here is what I found and it makes no sense to me.
Just using the Slacko 533 looking at the properties of the CD that I burned from the ISO I get 115 MB used and NO MB Free! But the CD is rated for 700 MB. Where did all the xtry space go?
Not only that but the files I did copy to Flash from the HD were:
Slacko 533 2fs - 512MB
and Slacko 533 sfs - 109MB.
That's 621 MB. Plus the original 115 is 736 MB. Plus I sposed the .2fs would grow with time? Have I gone off the deep end here? Something tells me I'm a bit wide of the mark.
hi Dande
I'm mainly with Flash on this - with optical storage on disc, it's read-only once it's burned (so not much call for running backups). The 'save file' of a multisession is usually a series of savedirs in a layered structure that builds over sessions - if you hit a comfy spot before the disc is full, start going NoSave and all your fresh screwups are forgiven since they're not saved
Definitely the comps RAM is a factor - especially if you load other specialized sfs files like for office suites, wine, a devX (if you do that sort of thing), personal sfs and so on. If you need more, you can do a swap partition/file for linux on the hdd (preferred) or a thumbdrive (for if you only need it rarely).
Absolutely set up browsers, file managers and anything that caches to dump the cache so it doesn't pile up in gigundus globs of whatever. Using thumbnails in rox file manager is a simple example - unless you clear the thumbnails (options->thumbnails, clear), they are saved and eat up space in a savedir and also RAM.
But that's multisession. If you did burn your liveCD 'normal', then it's basically a boot cd and 'full' at roughly 115 mb since it's closed.
Here's some stuff to osmose when you have a moment or so
I'm mainly with Flash on this - with optical storage on disc, it's read-only once it's burned (so not much call for running backups). The 'save file' of a multisession is usually a series of savedirs in a layered structure that builds over sessions - if you hit a comfy spot before the disc is full, start going NoSave and all your fresh screwups are forgiven since they're not saved
Definitely the comps RAM is a factor - especially if you load other specialized sfs files like for office suites, wine, a devX (if you do that sort of thing), personal sfs and so on. If you need more, you can do a swap partition/file for linux on the hdd (preferred) or a thumbdrive (for if you only need it rarely).
Absolutely set up browsers, file managers and anything that caches to dump the cache so it doesn't pile up in gigundus globs of whatever. Using thumbnails in rox file manager is a simple example - unless you clear the thumbnails (options->thumbnails, clear), they are saved and eat up space in a savedir and also RAM.
But that's multisession. If you did burn your liveCD 'normal', then it's basically a boot cd and 'full' at roughly 115 mb since it's closed.
Here's some stuff to osmose when you have a moment or so
native tools &etc
filesystem->gdmap - see what's eating space on (mounted) filesystems
multimedia->burniso2cd - make more dogs
(pburn can do this as well, plus it can blank rw media for recycle)
Keep your savefile slim and healthy .. recommended concepts for the tidy folk
yvw, gl&hf…
filesystem->gdmap - see what's eating space on (mounted) filesystems
multimedia->burniso2cd - make more dogs
(pburn can do this as well, plus it can blank rw media for recycle)
Keep your savefile slim and healthy .. recommended concepts for the tidy folk
yvw, gl&hf…