Thanks, later today I will try to follow your description and see what happens. I feel unsure about the name z or Z in the description. Is that something I tell it or is that built into your pet that it looks for a z and ignore other names like lupu525_s.sfs or something.

Important questions

Should the first pupsave file one make be a 3.fs and not a 2fs I always make them 2fs while your .desktop maybe wants them to be 3fs?_________________I use Google Search on Puppy Forum
not an ideal solution though

Thanks, later today I will try to follow your description and see what happens. I feel unsure about the name z or Z in the description. Is that something I tell it or is that built into your pet that it looks for a z and ignore other names like lupu525_s.sfs or something.

Most recent pups do not use a z-drive sfs and so it can be utilized for other purposes. At bootup puppy looks for an sfs file named with the following 8 character format:
z-firstletterofpup-3lastdigitsofpupver-3lastdigitsofkernelver.sfs. So, for example the z file for
lupu-510 would be named zl510332.sfs

Important questions

Should the first pupsave file one make be a 3.fs and not a 2fs I always make them 2fs while your .desktop maybe wants them to be 3fs?

It doesn't make any difference because the pup-save file will be converted to an SFS file.

1. I made a dir with sfs files in it and named i sfsfiles it is placed on mnt/home

2. I made a small pupsavefile that I now need to rename as you explained above. in my case it is lupu525 so it will be zl525332.sfs then
due to lupu525 having the kernel 2.6.33.2 kernel was that right?

But the dir2sfs program I don't understand how to apply it.

I am in pfix=ram now so feel for doing it. I am using your sfsexec and managed to start opera 11 or something sfs but the Chrome 12 failed to start.

I think I have a FF3.013 that I can test if it works too.

So need to get the dir2sfs program going and with correct name

Edit late at night here now so most likely I look for your answer tomorrow.

Which dir2sfs.pet should I use? The lupu525lite does not have dir2sfs so I borrowed one from some other puppy but that could fail due to missing libraries or something.

Where can I find a working pet for dir2sfs that works in Lupu?

good night_________________I use Google Search on Puppy Forum
not an ideal solution though

1. I made a dir with sfs files in it and named i sfsfiles it is placed on mnt/home

2. I made a small pupsavefile that I now need to rename as you explained above. in my case it is lupu525 so it will be zl525332.sfs then
due to lupu525 having the kernel 2.6.33.2 kernel was that right?

Just to review steps-
After you have made the small pupsave file with whatever added pets, reboot with pfix=ram.

Now click on the small pupsave file and it will mount as a filesystem. Go to the /mount directory and It will probably look something like this according to what name you gave the file - "/mnt/+initrd+mnt+dev_ro2+lupu-525+lupusave-setup.2fs" when mounted.

Now in the /mnt directory, open a terminal and enter the command "dir2sfs +initrd+mnt+dev_ro2+lupu-525+lupusave-setup.2fs" (Note: space after "dir2sfs")

This command will make an SFS file which you can then rename "zl525332.sfs "

Then, move "zl525332.sfs" to the same location as the main lupu-525.sfs file.

Now, when you reboot, the "zl525332.sfs" file will be automatically loaded.

that one can use
mksquashfs manually and don't really need a dir2sfs scriptfile.

I think "dir2sfs" is in most pups (you can test this in a terminal by typing "which dir2sfs") and see if the command finds the file. If for some reason it isn't there, you can use the command "mksquashfs ". But, it's better to use "dir2sfs" because it contains some error checking so you don't destroy any existing files. ("dir2sfs" uses the "mksquashfs" command)

I trid to follow your description but my ability to read instructions is very random at best and not there at worst case scenario.

Btu I almost made it. I looked very real to me but it did not bot the zl525332.sfs file when it booted. And me having placed firefox on teh hdd it did not like at all.

I start all over tomorrow and try to be more carful I don't want to give up on this one.

Something in your description seems to fail me.

I should cite or quote you to be correct but I seems to come up to this hurdle.

Are the sfsexec.pet supposed to be incorporated in the small savefile that I later make a dir2sfs of

The one thing that went wrong was that I made that one two times.

One need to start totally fresh then if I get it. Not use a current pupsave file?

The problem is that my OS is on sda3 and the script maybe suppose it is on sda1? It fail to find the zl525332.sfs file it does not boot it.

Maybe it clear up tomorrow. Too late at night to start all over now.

Edit this is one day later

Surprise

Spent some 3 hours trying to do exactly as you describe so with reservation that I am incredibly bad at following instructions I utterly fails.

I have booted with both pfix=ram and booted as usual but it fails to boot the zl525332.sfs file.

Is there a sure way to confirm that it boot it. Can one confirm in anyway what gets booted or not.

When I made the dir2sfs it took it from here
created: /mnt/+mnt+sda3+lupu-525+lupusave.2fs_525.sfs ( 47 MB )
created: /mnt/+mnt+sda3+lupu-525+lupusave.2fs_525.sfs-md5.txt

The sda3 should not be there should it? should it not be like this
created: /mnt/+mnt+home+lupu-525+lupusave.2fs_525.sfs

the sda3 comes from that the Lupu has not saved anything yet.

My gut feeling is that one should not use the pfix=ram thing to make dir2sfs file.

one should reboot into another puppy and make the sfs from that one and that way it will have the internal structure in right places?

But I can be badly wrong. So what can explain why it fails. Must be something in the way I do it that differ from your description.

Something that is obvious to you and that I fail to read into your txt as what you tell me to do? Or is it as simple as you having the frugal install on sda1?_________________I use Google Search on Puppy Forum
not an ideal solution thoughEdited_time_total

Background I have Lupu525 put in a subdir with the three needed files for to prepare a frugal install on Sda3 on the NTFS hdd. So grub4dos boot it up with pfix=ram and so on...

1. First I boot up with pfix=ram to make a totally fresh lupu.
2. Then I chose all the personal preferences I want. Then save these in a Lupusave file
3. I then reboot using pfix=ram and make a copy of the lupusave for backup purpose and place it out of reach in another subdir many layers away.

4. and then reboot with pfix=ram to not let any other pupsavefile either to be loaded and mounted.

5. I then mount the pupsavefile using Rox and open up a terminal in that Rox space and tell terminal do do dir2sfs giving it the path I see in rox and dir2sfs report it worked as I described in a post above this one.

Could I have included too much in the code? I used this one

dir2sfs /mnt/+mnt+sda3+lupu-525+lupusave.2fs

should it have been just this?
dir2sfs +mnt+sda3+lupu-525+lupusave.2fs

or could it be that I use grub4dos and that that one fail to allow lupu to boot the zl525332.sfs

the sda3 is due to that my computer have three partitions. Does that make it fail?

Could I maybe solve it by not using dir2sfs not at all using the mksquashfs just as it is? I give it a try. I have the savefil backed up so no big deal?_________________I use Google Search on Puppy Forum
not an ideal solution thoughEdited_times_total

Finally some progress but only after using a wild workaround which fail to have my personal settings from the zl....sfs.

1. I did a pfix=ram boot and then installed sfsexec which did not get loaded.
2. I had made a copy of the zl525332.sfs that fail to load when I boot up and placed in among the sfsfiles in that direcory for them that I told sfsexec to make use of and
3 then I loaded that zl525332.sfs and that gave me the firefox I had in the save file but none of the other changes did survive though.

so I am writing now from the pfix=ram booted but that make use of the zl525332.sfs in a way you did not write about for as I get you it should be booted.