Having completed the first-run screens I opted to reboot in order to create a savefile before proceeding further. No sizes were offered then the screen below appeared..

Can you reproduce this? If so can you provide exact steps so I can see what goes wrong. Include what media and filesystem you want to save to, size of partition, your boot media and anything else you think relevant.
If you can reproduce this then it would have occurred in beta4 and RC1 as the only change to the shut down routine is the NTFS bugfix since November 12.

Anyone else see this?

If I hear nothing in the next 24 hrs regarding this issue, I'll add shinobar's pupsaveconfig to the repo as a possible work around with an advisory in the release notes.

-

Some notes on installation:

There are about say a thousand [?] ways to install puppy.

If you boot from a subfolder it will save to that subfolder. If you use PUI to create a frugal to HDD it will create a subfolder. I think it's still possible to save up to 3 levels deep but this is not advised. Tweaking the kernel line of your boot loader config may be necessary (menu.lst in most cases).

If you boot from CD it will save to the top level.

You can use PUI to create an USB install and it will save to the top level. For multiple pups on an USB you can manually create the stick with subfolders and use ETP's tut to boot with syslinux or other tuts using grub4dos on the stick. I believe grub2, lilo and grub legacy can work too, and of course if you format to ext2/3/4 extlinux (still part of syslinux).

Save files can be moved around as long as puppy knows where to find it, specified in your bootloader config._________________Puppy Linux Blog - contact me for access

With regard to my previous post I normally do a frugal manual install to a USB stick and then subsequently transfer the main sfs & savefile to my hard drive. The kernel I leave on the USB and change my boot codes accordingly.
On this occasion however, I intended to put the savefile on the SSD from the outset and was only using a 16 Meg partition on the USB stick the remainder being unformatted. The main sfs therefore was already located on the SSD. My syslinux boot codes were therefore as follows:

I thought at first that I may have shot myself in the paw by not giving the first shutdown procedure the option to offer to save to the USB there being insufficient space to do so. This was not the case however, as I had in effect restricted puppy’s options with the boot codes. The problem was that the first shutdown procedure was not mounting sda1.

Provided I mounted sda1 prior to running first shutdown everything behaved as it should with a choice of savefile sizes being offered but no choice of save drive due to my restrictive boot codes. In conclusion I did shoot myself in the paw but not in the way I first suspected!
Please accept my apology for raising a false alarm.

Thanks for the explanation . I already added shino's pupsaveconfig to the repo anyway. It is useful in some abnormal cases where there is a failure of the standard tools. No problem.

-

mavrothal..

I have compiled luvcview, got the sources from ubuntu Precise repos, it's totally at the opposite end of the scale as webcam apps go.. requires only Sdl, which we have anyway. It is known not to work on some webcams so YMMV. Working ok here, recording and snapshot tested. There is no audio facility though. I'll upload to the repo at any rate, someone might like a very simple webcam app.

I have compiled luvcview, got the sources from ubuntu Precise repos, it's totally at the opposite end of the scale as webcam apps go.. requires only Sdl, which we have anyway.

luvcview never worked for me and this one is no exception

Tried to see what is the minimum of gtk3 that guvcview does need, but suddenly the guvcview-1.6.1-i486-s.pet was nowhere in any mirror.
Turns out that is in "pet_packages-slacko" instead of "pet_packages-slacko14"._________________== Here is how to solve yourLinux problems fast ==

So it turns out that guvcview only needs libgtk-3 and libgdk-3 from the 55MB Gtk-3 package! You may want to include these in the guvcview pet and remove Gtk-3 from the dependencies.
Till then I made the 4MB guvc_deps_s14-1.pet that is all guvcview-1.6.1-i486-s.pet needs to work in Slacko 14_________________== Here is how to solve yourLinux problems fast ==

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum