Fatdog64-600 Final and 601 (July 2012)
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
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
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.
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.
Thanks Kirk.kirk wrote: ... Originally during Fatdog64-600 development, we had decided to drop support for multi-session saves. But, James found that ...
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
Hi, I don't how to update the java in Fatdog64? Can anyone give me a help?
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..
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
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:
In term on sda5:
So I fixed it with a workaround bij putting a script in ~/startup:
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?
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
Code: Select all
# fuser -i /dev/snd/*
/dev/snd/controlC0: 5135
Code: Select all
#!/bin/sh
SND=`fuser -i /dev/snd/controlC0 | grep -o ' [[:digit:]]\{4\} '`
kill$SND
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
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
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
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?
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?
Last edited by spandey on Thu 27 Sep 2012, 09:25, edited 1 time in total.
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.
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.
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
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
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though