[Release Notes for 601]
Kirk and myself is pleased to announce Fatdog64 601. This is a maintenance release and mainly contain bugfixes over 600. If 600 is working for you and its known bugs do not affect you, you don't need to update to 601. For new users, usage of 601 is recommended over 600.

Changes from 600:

YASSM updated to 2.4.6 (rcrsn51) - this has ability to search for shares

savefile-argument-builder update to 1.2 (rcrsn51) - this fixes a bug when finding UUID

update xorg with patched version that fixes panning

fix major bug: savefile-tool does not always work

fix major bug: launching console applications can lock X desktop

new tool: fatdog disk usage

update kernel to 3.4.5

update seamonkey to 2.11

update guess_fstype and busybox for ext4 detection

and other minor fixes.

Note that since 601 contains an updated kernel, if you use ATI or NVIDIA drivers you will have uninstall them and get the new driver package. This process can botch your existing savefile so please make sure you make a backup of your savefile first.

[Release Notes for 600]
Kirk and myself are pleased to announce Fatdog64 600 Final, after over 6 months of development time and 2 months of continuous testing.

[ISO and devx]
Fatdog64 600 final is released in two official flavours:
- Seamonkey (Fatdog64-600.iso)
- Firefox (Fatdog64-600-firefox.iso)
And one "unofficial" version using "small initrd" (Seamonkey only) - Fatdog64-600-small-initrd.iso (only available on the personal mirrors below).

[PET Packages]
Other SFS and packages are available from ibiblio and its mirrors.
When possible, get the packages from official pet repo first using the Package Manager (available from the Control Panel). Package Manager provides dependency tracking for both installation and uninstallation.

[Previous releases]
Earlier discussion threads during testing stages - though some of the info have been superseded, they still contain useful information and hints.

Special thanks for rcrsn51 who tirelessly updates his tools (peasy-apps, YASSM & others) for Fatdog throughout the long nights from alpha2 stages until final, as well as the superb provision of printing and scanning support.

Thanks to 01micko, shinobar and zigbert for providing and updating key applications in Fatdog.

Most heartfelt thanks to all alpha, beta and rc testers who helped to uncover tons of bugs: 01micko, Billtoo, Jim1911, rcrsn51, James C, gcmartin, and many others - I'm sure I missed many.

EDIT: Final is also now avaialble in ibiblio and its mirrors._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.Last edited by jamesbond on Sun 22 Jul 2012, 05:13; edited 4 times in total

Know issues for 601:
1. Win+E to call up Rox folder sometimes bring the Rox window behind, and extra Alt-Tab is required to bring it to front.
2. Elantech touchpad is not recognised.

Know issues for 600:
1. "drive mounter" doesn't work for non-root.
2. "mount -t cifs" doesn't work. Fix: move /usr/sbin/mount.cifs to /sbin/mount.cifs
3. "samba share app" cannot open shares in different subnet.
4. CRITICAL PROBLEM: savefile-tool sometimes fails to recognise the filesystem type of the savefile and refuse to work.
5. Adding/removing drive icons (e.g. when one runs gparted) can cause the icons to scatter around. Fix: Control Panel -> Display -> Event Manager: change icon size from 64 to 63.
6. Panning doesn't work because of xorg problem.
7. CRITICAL PROBLEM: Do not try to launch terminal/console application directly from desktop. It will lock up the desktop, you will have to Ctrl-Alt-Backspace to restart it.
8. Printing using "cups-pdf" in browser/email client (as spot) fails if one uses the login manager. As a workaround, use "print as file" instead.

All these are fixed in 601._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.Last edited by jamesbond on Sat 28 Jul 2012, 07:39; edited 6 times in total

Maybe i am missing something, but i cant find manual save button. With disabling autosave feature it comes in pretty handy to create stable "checkpoints" during experiments. Is there a command to manually save?

I understand that fatdog can be used as a server. Since server does not need gui, office software and stuff it would be preferrable to trim those from base sfs. one way i can come up with is manually unpacking and removing files (which is kinda hard to figure out whether delete them or not). Since there is no tool for that in fatdog (i am pretty sure i saw such a tool in some puppies), is there any other way to trim some fat?

Fantastic. Can't find anything broken in Fatdog64-600 Final and I've been trying things for awhile now. In fact, VLC seems to open and aquire cable television signals faster and better. Not sure if that's because of the added DVB firmware but whatever the case it's great.

For anyone having trouble getting their PVR or other tv tuner cards to work in VLC [find and tune channels] I've got a few tips that could help. I found a chart of NTSC frequencies. Frequency tuning control is available in VLC>Media>Capture Devices...

You may need an ATSC or QAM chart, depending on your tuner and cable company or air broadcast standards. Simply enter the frequency number of your favorite channel and it will play! In my case, I have to add a zero because chart is in MHz, VLC uses KHz,

In this case, I enter 337250 KHz to get Channel 43 The History Channel. I think I can make a playlist or something and this way, channels.conf is not necessary. People with NTSC cards cannot use the newest DVB tools to generate one. This is the workaround.

The forum trashes the formatting of this chart no matter what I tried. So I have attached "ntsc.chart.txt" Hope this works for someone else as well as it did for me. Okay attachment NOT accepted. Go to NASA: http://hamradio.arc.nasa.gov/ntscfreq.html

I understand that fatdog can be used as a server. Since server does not need gui....

Have you ever set up other Puppies as servers? Trying to do it entirely from the command line is really awkward.

How many users are you planning to support? Typically, enterprise servers are big-memory machines. If you are running Fatdog on a multi-GB machine, the amount of RAM taken up by the GUI stuff is irrelevant

There is no significant advantage to stripping a Puppy in order to run it as a dedicated server. In any case, the file sharing capability in Fatdog really isn't intended for that purpose.

Or you could use the "small initrd" version of Fatdog. In that case, the base sfs is NOT loaded into RAM, so you can save some memory.

There have been a few issues when I warmed up a long forgotten NForce board. <nox> boot parameter gave me the prompt but xorgwizard doesn't work. Fortunately, xwin brought up the correct res. screen. SMonster kept crashing with BBC/iplayer and sound was badly distorted and faint - couldn't find the mixer. Had problems d/l Firefox, the d/l message window kept going blank. Other minor irritations with the Control Panel, not all associated with Fattie, though. Please bring back FULL support!
Will try the FF variant later.
Otherwise, rather nice and very fast. Porteus manages an Xfce Slack-based 64bit in only 202Mb (cf DW).
Correction.Last edited by Sage on Fri 06 Jul 2012, 06:33; edited 1 time in total

Maybe i am missing something, but i cant find manual save button. With disabling autosave feature it comes in pretty handy to create stable "checkpoints" during experiments. Is there a command to manually save?

You need to use the RAM-layer in order to enable manual save button. Use "savefile=ram:blahblahblah" instead of "savefile=direct:blahblahblah" to enable the RAM layer. Use the Event Manager to change the automatic save period (either to zero or to an enormously large value) to disable automatic saving.

Anyway, if you intend to experiments, Fatdog comes with a sandbox that is meant exactly for that. It's usage is documented in the FAQ. Run your experiment in sandbox; if it works, apply it outside.

EDIT:

Sage wrote:

Please bring back FULL support!

It is possible to run Fatdog64 in layered full-install (ie all the system files are expanded and stored in a dedicated partition instead of squashfs file, but the layering system still active - similar to PUPMODE=3), just that there is no tools to install Fatdog that way. It is not possible (well, not without great effort) to have true full install without any layers (PUPMODE=2) - many of the system scripts assume that the layering system is present._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

1. Previously running Fatdog64-600 rc [and right now typing this from it], with no obvious problems.

2. Downloaded Fatdog64-600-firefox.iso, burned live CD-RW, booted same, and got...
"Machine Check Error"
And the PC goes into a cyclic reboot loop, displaying that error at each attempt to load Fatdog.

3. Previously [a day or two back], this happened only with Saluki.
Previous to that I'd never seen any other OS produce this error.

I edit this due to my too wild suggestion. So sorry!_________________I use Google Search on Puppy Forum
not an ideal solution thoughLast edited by nooby on Fri 06 Jul 2012, 16:06; edited 1 time in total

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