As a bread and butter user, I find Fatdog to be very good, it has the applications I use from the get go. The one minor fault I have is that the installed Samba will not connect to Windows 7, but XP and Linux do just fine. I don’t use Windows 7 much anyway.

I like having Qt configuration working, so, I added what was required to get it going from the larger qt4-472.pet.

The boot-up time is very good, less than 10 seconds on my semi slow 4 core computer. My son’s little bit quicker 6 core, loads in less than seven!

I have Fatdog 600 Seamonkey with Firefox added, running off of a vfat 32 partition, this is because of my older Mepis grub bootloader.

I am also, just using OpenBox and Lxpanel, I have white outed JWM and removed it from the menus because it does not work well with Xcompmgr and other numerous things. I believe it can be dropped from this OS all together and save a little space.

Over all really great job, Kirk and jamesbond.

PS: I am reversing my opinion on JWM, I compiled an older JWM 508, which is better able to handle xcompmgr. I than modified /usr/bin/jwm_menu_create to correct errors with the jwm -p test.Last edited by Kal on Wed 25 Jul 2012, 14:15; edited 1 time in total

James try right click on Rox title bar and select layer then Always on top.

Thanks, if I do this Rox windows are always on top, but this isn't what I want. I want newly opened Rox windows to appear on top, even if all existing open windows are beneath others.

kirk wrote:

I've attached a patched version of Xorg-server-1.11.4. This should fix the panning problem. Please test.

Working for me. With the panning problem fixed, the "zoom" function in Fatdog works again _________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

That said, there are a couple annoyances. Several have already been shared.

The most recent is the following: I booted pristine (no options) on a 4GB RAM X2 system to desktop.

I allowed the system to sit overnight. Open the Control Panel this morning and reset the system name. Exited Control Panel, open Openbox config and set for 5 virtual desktops.

In desktop 3 I started Hardinfo

and In deskop 2 I open Geany edit from desktop icon

I began typing and spell-checking a text document. When satisfied, I went to desktop 1 inserted a USB drive (still having issues with manual system mounts to get to NAS drives on LAN) and went back to my document. I save the document to the root of the NAS drive. After this completed, I began to continue editing my document.

About 15 secs into the editing, my system went into a spin and the desktop "locked"! No keyboard keystrokes in Geany...no mouse activity.

I Cntrl-Alt-F3 and login to run "top". It took 2+ minutes for login processing to complete. And TOP shows the PC at 0% user 55% system??? The top tasks consistently were

Geany

wpa_gui -t

lxpanel.bin

glipper.bin

with some ancillary pops into top 5 from

(df) /bin/sh /bin/sh -k

frememappletd

(fat-udev-he) ...

.

Killing Geany took forever. Going back to Xdesktop and attempting a Geany to see if it would reconnect original document gave me ONLY a incomplete start of Geany.

Next, Restart of desktop took forever. After which, I turn it off.

I know this may not directly ID the problem, but, maybe understanding the steps may help to zero-in.

Hope many of the things reported make it into the update._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Running a Pristine Live media system
Control Panel>Desktop Tab>Adobe Flash Player>Playback Tab cancels the Flash Player Preference settings.

Is this a bug?_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Actually I figured out the problem, it's that they were not installed with the package manager, although in other Puppies all installed packages show up.

All installed packages show up. In my earlier post, at least two installed programs shown were not installed by package manager.

Jim1911 is right. You can manually check whether the "missing" packages are registered correctly - just open the file /root/.packages/user-installed-packages. If they are found inside but is not shown by the package manager, then it's a bug, let me know (please send the file to me). If they are not listed in that file to begin with ... well, try to install again and then check the file again, are they inside after that? If still not, let me know which package exactly and I'll try to duplicate that.

Sorry, it took a while because I had to reinstall some other OSes which required wiping Fatdog64, I still haven't figured that out but I reinstalled Fatdog and resumed testing.

Here is what I found out. I tried installing 10 .pet packages, and I actually did it two times (because I forgot to save, but it is better for testing).

All the packages created individual files in /root/.packages, however two of those .pets did not register in the user-installed-packages file (and consequently in the package manager).

Those two .pets are the gtk hash utility and the cpu temp utility. However, the gtk hash appeared in the regular Puppy menu. The hash utility also registered in the user-installed-packages, but only after it was installed the second time. As I wrote, I carried this test out two times, and on the second test it also only registered only on the second try.

The cpu temp pet simply opened another instance of itself on the taskbar every time it was reinstalled and never registered in the user-installed-packages file. It did, of course, have its own file in the .packages directory when installed.

The cpu temp pet simply opened another instance of itself on the taskbar every time it was reinstalled and never registered in the user-installed-packages file. It did, of course, have its own file in the .packages directory when installed.

I think I know what the problem is. The CPUtemp package contains a post-install script that auto-starts the applet in the system tray. That way, you know it's working.

But that may conflict with the package manager - I believe I saw that in another Puppy. I will replace the auto-start with a message that says "CPUtemp will start working at the next bootup".

Thanks for finding this.

[Edit] Here is a new version. It auto-starts and registers correctly in the Package Manager. Please test.

There is another issue with CPUtemp in FD600. It contains sensors-detect which lets you search for alternate temperature modules. However, it is a Perl script and FD600 does not have Perl. OTOH, I have never seen sensors-detect find anything useful.

[Edit] To get sensors-detect working, install the devx package. That gets you Perl. But you also need to run

Here to help_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

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