shinobar wrote:How to uninstall PET? The Un-Install button on the Fatdog Package Manager doesn't work..
1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
If this doesn't work (I'm interested to know why it doesn't work), you can use the old and familiar Puppy Package Manager. Run it from terminal like this: /usr/local/petget/pkg_chooser.sh
If that still doesn't work, manually uninstall the package from terminal like this:
silent_petget pkg-name-version.pet uninstall
Here is a neat little desktop recorder using ffmpeg.
Thank you Grant, excellent addition.
While we're at this subject, I'd just like to clarify a few things:
- screencaster is optimised for making an extremely small output file.
By default it captures that 3 frames per second. You can adjust the frame rate at the "advanced" tab, but quality will suffer because the maximum bit rate is hardcoded to 128kbps.
Anyway, screencaster in beta1 has a bug which makes it unusable; this is fixed in the next release.
- shinobar's FFconvert 1.8 (or is it 1.3) will be in the next release (thanks shinobar)
- VLC can also capture screen - use "Media" - "Convert/Save" and then "Capture Device"
shinobar wrote:The getnvidia avoids the dialog.
Thank you shinobar. I will package nvidia for the final release; however this script of yours hopefully will help those who need nvidia *now*. I'll probably use it too to make the official nvidia pet
smokey01 wrote:shinobar wrote:@smokey01 recorder-1.0.pet attached could not install nor extract.
I think FD uses different compression to some of the other Puppies when building Pets.
600 uses xz compression for the pet. If you need to convert it, extract it and re-pet again:
Code: Select all
tar -xJvf some-fd600.pet
dir2pet some-fd600
kickstart wrote:He has done in the past as he recommended a modeswitch dotpet to me. Unfortunately it was 32 bit and didn't work in Fatdog. Looks like I'm going to have to do some more experimenting with the offerings on the draisberghof.de and sakis.3g websites. I'll do a frugal install of 600b and include the devx.sfs as I believe any compiling will have to be done in the Fatdog environment. (I'm still pretty clueless with the nuts & bolts of Linux so it will be a bit of a challenge - though I've heard it said that exercising the brain helps ward off senility!)
If it works with 32-bit, give it a try with the 32-bit compatibility library loaded. It is located here:
http://distro.ibiblio.org/pub/linux/dis ... g/sfs/600/ (similar paths in one of the mirrors - mirrors are listed in page 1 of this thread).
Sylvander wrote:3. Downloaded Xfe [to the tmp folder]...
The best way to do this is to to use the Package Manager; it is available in "Control Panel" - "System" - "Package Manager"
Sylvander wrote:Managed to download and install without supplying the root password
Well, you are already running as root, so it wouldn't ask for root password anymore
gcmartin wrote:IPV6 is the direction of the planet. Here is a Puppy thread where several members has made some good finding to assist the community.
FATDOG does have the base mechanism to do such, but, they have been helpful is extending the base to make it easy to understand and simple to implement.
For the upcoming FATDOG, we may want to PET this or provide a berth within.
Yes, Fatdog is ipv6 capable. Kernel module is available (modprobe ipv6); the userland tools are also ipv6 aware. If the ISP provides ipv6 - then Fatdog can happily access any ipv6 sites. Miredo/Teredo is needed for those who needs to access ipv6 sites but does not have ipv6-capable ISP. It works by acting as a proxy client on the computer, and send the traffic to a few public proxy server on the Internet (google: teredo public servers), which *receives all your miredo traffic* and translates them for ipv6 sites.
Thank you everyone for testing
