Page 13 of 17

Posted: Mon 03 Sep 2012, 20:13
by GKM
Hi there,

Did anyone try the XLock lock screen from the Fatdog control panel? I tried it, but it does not appear to accept any password. I tried to set a root password, and it works with the logon screen, but not with Xlock. I also tried a few standard puppy passwords, and the cpasswd option from the command line, but to no avail. What do I do wrong?
Regards,

GKM

Posted: Wed 05 Sep 2012, 01:21
by kirk
GKM,

Yes, that's a bug. James has fixed it for the next release. Not sure when that will be.


Smokey01,

Thanks for the fix.


RandSec,

Originally during Fatdog64-600 development, we had decided to drop support for multi-session saves. But, James found that it did seem to work, though I don't know to what extent. I haven't tested it my self. Maybe James will respond next time he checks in here.
Sound should be adjustable in ALSA Mixer, unless you're using digital sound to an external receiver, then VLC preferences should be looked at.
The new big initrd does have a faster boot for the most popular boot methods.

Posted: Wed 05 Sep 2012, 16:13
by gcmartin
kirk wrote: ... Originally during Fatdog64-600 development, we had decided to drop support for multi-session saves. But, James found that ...
Thanks Kirk.

I'm sure you are aware that I, too (along with others) are LIve DVD users. And, I think you remember that ran FATDOG for several years merely booting its multi-session, mutli-save system, in production, never needing to install on USB/HDD with extremely rewarding success.

This is/was a very attractive approach and use of FATDOG. Heres hoping it continues.

Here to help

Update java

Posted: Tue 11 Sep 2012, 00:33
by winwin
Hi, I don't how to update the java in Fatdog64? Can anyone give me a help?

Posted: Sat 15 Sep 2012, 03:57
by smokey01
Codeblocks-10.05 is available on my site for FD64:
http://www.smokey01.com/software/Fatdog ... 5-fd64.pet

It does require wxWidgets which is available via the FDPM or here:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 2.8.12.pet

It's a very impressive application for developing C & C++ applications.

Documentation here:
http://www.codeblocks.org/user-manual

Enjoy..

sound quit working

Posted: Mon 17 Sep 2012, 21:45
by Hans
Hello all

First: Kirk, Jamesbond and all others contributing to this release, thanks!
It gets better and better every time, I'm happy!

But what to do when all was perfect, wouldn't be fun right?
So I am happy to report, I have an issue with my sound, first reported bij Billtoo in http://murga-linux.com/puppy/viewtopic.php?t=79001
First time I had this problem was when I was playing around with this new release.
I followed Billtoo's instructions and deleted the savefile.
This weekend I decided to migrate permanently and again the sound issue came forward.
Not wanting to delete all the work I just put in to the new install I dug a litte deeper.
I compared the new install (on sda3) with the play-around-one on sda5.
In term on sda3:

Code: Select all

# fuser -i /dev/snd/*
/dev/snd/controlC0:   5096  5136
/dev/snd/pcmC0D0c:    5096m
/dev/snd/pcmC0D0p:    5096m
In term on sda5:

Code: Select all

# fuser -i /dev/snd/*
/dev/snd/controlC0:   5135
So I fixed it with a workaround bij putting a script in ~/startup:

Code: Select all

#!/bin/sh
SND=`fuser -i /dev/snd/controlC0 | grep -o ' [[:digit:]]\{4\} '`
kill$SND
And it works.

Not a single clue what's going on though.

Putting the script in /etc/init.d after the 20-alsa script does not work, I had to put it in ~/startup.
And at every reboot or poweroff I hear the soundcard unloading, so I guess this part (line 70 and 71) of the 20-alsa script is not functioning, due to this soundcard problem.

Does anyone know what goes wrong with my snd_hda_intel?

Not able to create a savefile

Posted: Sun 23 Sep 2012, 15:51
by joe0855
Hello Gents,

It's been a while since I've last visited the Fatdog forum. I've been using Fatdog64 521 and have been very happy with it. Was curious in trying 601. For test purposes, I've created a quick USB boot version of 601 using Unetbootin (live USB).

For some reason, I can't get the OS to recognize the savefile. I've tried the Savefile Argument Builder.

Went into the 'syslinux.cfg' file and made the following change to the append line:
'append search savefile=ram:uuid:ECF6-A259:/fd64save.ext4'.

But after rebooting the system, the OS still doesn't recognize the savefile. Any ideas?

Thanks,
Joe

savefile

Posted: Sun 23 Sep 2012, 16:01
by Hans
So it does not work on syslinux? In the fatdog64 installer one can choose for syslinux though.

Works with grub, I used it twice

Posted: Sun 23 Sep 2012, 16:27
by rcrsn51
I don't think that you should be using both "search" and "savefile=".

[Edit] I checked this with syslinux using "search" and "savefile=" together. The savefile was correctly located.

Maybe you need the "waitdev" argument too. Start with "waitdev=10".

Posted: Sun 23 Sep 2012, 18:41
by joe0855
rcrsn51 wrote: Maybe you need the "waitdev" argument too. Start with "waitdev=10".

Thanks rcrsn51, worked like a champ! Changing the append statement to look like:
'append search savefile=ram:uuid:ECF6-A259:/fd64save.ext4 waitdev=10'

did the trick.

Posted: Sun 23 Sep 2012, 18:48
by rcrsn51
Excellent. Now take out the "search" because it's redundant. And reduce the "waitdev" value to the shortest time interval that works.

Posted: Mon 24 Sep 2012, 03:18
by joe0855
Ok, so I removed the 'search' parameter and was able to reduce the waitdev to 1 sec (go figure).

Thanks again rcrsn51!

Posted: Thu 27 Sep 2012, 05:47
by spandey
I have Luppu 5,2,8 running of USB flash and booting with GRUB4DOS. It's working fine with no issues so far.
I just downloaded Fatdog 601 ISO and after mounting copied the contents to a Directory in same USBFLASH.
Using GRUB4DOS I am able to boot it. But when I like to download SFS files using it's Control Panel --> system--> SFS Manager
, there's an error that Fatdog is not installed !!!

I don't want to use Fatdog Installer as it might destroy my other content in USB. What parameters I need to change?

Posted: Thu 27 Sep 2012, 08:13
by nooby
spandey I would do a manual frugal install
so that no other OS get messed up? Those
active here would know how to and the FAQ
for FatDog knows how to do it too?

Posted: Thu 27 Sep 2012, 09:13
by spandey
Nooby, I did a manual install only. After rebooting it doesn't pick up the savefile and won't allow ant new pet to be installed.

I tried two options as per usr/share/doc/faqs/boot-options.html in the fatdog.

1.kernel /Fatdog/vmlinuz savefile=ram:usb

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

The savefile is in root of sda2.

Posted: Thu 27 Sep 2012, 09:25
by nooby
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

Posted: Sat 29 Sep 2012, 20:21
by rcrsn51
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.

Posted: Sun 30 Sep 2012, 14:04
by spandey
Thanks it worked!!!

Posted: Sun 30 Sep 2012, 14:21
by rcrsn51
Just out of curiosity, how is the working version of the savefile argument different from your original version?

Posted: Sun 30 Sep 2012, 16:00
by spandey
The new argument uses UUID instead of sda2.