(old)Puppy Linux Discussion Forum

I should not have answered. The Devs of FatDog and
rcrsn51 are more apt to help you out.

You need to make a reference to where the save file are
in the boot code. It looks like this


title fatdog FD2
find --set-root --ignore-floppies --ignore-cd /FD2/initrd
kernel /FD2/vmlinuz psubdir=FD2 savefile=direct:device:sda2:/FD2/fd64save.ext3
initrd /FD2/initrd

So you need to specify where the savefile is.

instead of psubdir=FD2 savefile=direct:device:sda2:/FD2/fd64save.ext3
you need the way to secure that it finds it on your USB so it knows
about where to look for it.

Those active in the thread that use usb can instruct you or use the search
link in my signature and look for Fatdog and usb and save-file

spandey wrote:2. kernel /Fatdog/vmlinuz savefile=ram:device:sda2:/fd64save.ext4

The savefile is in root of sda2.

This looks OK. But go to Control Panel > Utilities and run the Savefile Argument Builder.

Thanks it worked!!!

Just out of curiosity, how is the working version of the savefile argument different from your original version?

The new argument uses UUID instead of sda2.

spandey wrote:The new argument uses UUID instead of sda2.

The savefile is in root of sda2.

Since you are using a flash drive, should this not have been sdb2? Or does your machine not have a hard drive?

The machine doesn't have Hard drive.

Is there a PET out there for Figaro’s password Manager? My attempts to download and install the source code have been fruitless to say the least!

Running Fatdog601 -- Firefox version -- with a 512MB ext4 save file in sda3, but do not see a "Resize save file" option. I really want to add 1GB of space to my save file, but do not understand how to do it with this system.

I"ve read the manpages and the FAQ, but afraid I either missed the easy version or did not understand.

Help?

-Roy

Is there a way to PREVENT Fatdog from saving the session? I tried adding the following code which I found here on the board some time ago to the rc.shutdown script. It works fine with Slacko and Lucid Puppy but Fatdog doesn't seem to like it.

roy:

Control panel/fatdog64 savefile tool.

Note:
You can not use the savefile tool while savefile is in use.
You will have to run fatdog64 with the pfix=ram option.
irishrm.

irishrm wrote:You will have to run fatdog64 with the pfix=ram option.

The Fatdog version of this option is "savefile=none".

gtkdialog-0.8.2 for FD64.

Rename /usr/bin/gtkdialog to /usr/bin/gtkdialog-old just for safekeeping then install:
http://www.smokey01.com/software/Fatdog ... -0.8.2.pet

Bill_Gates wrote:Is there a PET out there for Figaro’s password Manager? My attempts to download and install the source code have been fruitless to say the least!

Try this: http://www.smokey01.com/software/Fatdog ... 4-0.79.pet

I haven't really tested it but it worked when I clicked on the binary.

Cheers.

FD64 contains the driver for a Cohiba/aka you-name-it/ ...and Netgear wg111 - apparently, although it's a struggle to get it staying alight. Some claims on the InterWeb that Netgear doesn't/didn't do a 64bit driver, but those comments may refer to the devil's OS. Whatever, cannot get this dongle to run in Mint, so would appreciate some guidance from those who actually know what they're doing, please, together with a raw (not .raw) driver!

Sage wrote:FD64 contains the driver for a Cohiba/aka you-name-it/ ...and Netgear wg111

As usual, your first step is to run "lsusb" and determine the vendor:product ID codes for this device.

Then run "dmesg | grep firmware"

Does this device work in 32-bit Puppies?

irishrm & rcrsn51,

That worked great! Thank you very much!

I am setting up this laptop for a friend (read: New Puppy Convert) and she really likes the speed of it. Says she doesn't really want Windows any more.....

One other non-pressing issue is that she wanted a program to view and capture images with her webcam.... rcrsn51's gucview filled the bill nicely!

But the default jpeg images from that program are not supported by fotoxx image viewer, so I had to change gucview's default to png for it to work.

I want to thank everyone concerned with this version -- and the Puppy community as a whole -- for the thoughtfulness and hard work involved in bringing these things to the masses.

-Roy

smokey01 wrote: Try this: http://www.smokey01.com/software/Fatdog ... 4-0.79.pet

I haven't really tested it but it worked when I clicked on the binary.

Cheers.

Thank You smokey01, that worked like a charm!

Update on USB install:

I'm running fatdog64-600 on a usb install with the USB being regarded as a hard-drive. (see earlier posts)

While experimenting I discovered that If I place the savefile on the hard-drive It is recognized at boot.

If I have a savefile on the USB and on the hard-drive they are both recognized and I am given the option of which savefile to load.

So now I'm booting from the USB with the savefile being loaded from the hard-drive.

This means that there is no worries about USB failure and I have a very fast boot and shut-down time.

I have tried to replicate this with other puppies, using various commands I googled from the forum, but with no success.
If anyone can tell me how this can be done I would love to know.

irishrm.

Many thanks, rcrsn51, for leaping to the rescue again!

As usual, your first step is to run "lsusb"

- done that, it's recognised, but presume 64bit kernel has the p54 (Prism54) in common?

Does this device work in 32-bit Puppies?

Yes! I did actually report that somewhere within the last month?
My enquiry really relates to 64bit issues (I think!). Loads of good stuff on this device on LinuxQuestions.org (not all of which I understand and some that refers to Wdoze which I completely abandoned half a decade back).
It seems to be listed for WEP/WPA-PSK but I have my router configured for WPA2+ only. Doesn't affect 32bit operation in Puppy when WPA2+ is selected.