i feared the worse, us having problem with being not fast
enough on the fingers are too few to make our wishes known
can one not change it even in some conf fig file setting?
Seems odd that somebody force all of us into double click when there
are no good reason for it?

Ah, but there is a very good reason for it. Most other Puppies automatically install the application as soon as you click on your selection which can also be an unwanted action. I bet you have accidentally done this too.

It's easy enough to scroll up and down the list with the cursor keys and select with the space bar or Enter Key.

Many people don't like some of the differences in Fatdog but they are all there for a good reason. A lot of thought has gone into Fatdogs development. Differences are not all bad. If they were we would still be using the abacus.

Ignore the error message at the end of the compiling step saying that virtualbox services can't be installed or started (same as in Slako).
The services are installed just fine, you just need to put the command VBoxClient-all in .xinitrc or somewhere else where it gets executed at startup.

After the next reboot you should be able to use all the features that you enabled in the virtual machine settings, and System Information now should show VBOX0 as the display name. However in order to change the screen resolution you'll need to use xrandr to define a new modeline - there may well be an easier way (possibly involving xorgwizard), but I haven't figured it out yet.

I tried to use the Wine sfs (wine-1.5.4-i486.sfs) with Fatdog64 611. It did not work after being loaded. Using the console, I got this error for winecfg: Line 29 /usr/bin/winecfg not found. However, Pfind does find winecfg in/usr/bin. I downloaded the sfs wine file from the ibiblio 600 directory. Am I using the wrong version? Thanks for the help on this.

In general, Fatdog64 works well on my Acer Aspire Revo._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

nooby, the control panel can be navigated with Tab and cursor keys too. Items can be launched by pressing Enter key. You only need to use the mouse to close it (click the "x" button) - and that's single-click

mdisaster2, thank you for the step-by-step guide. I know I will be keeping your notes for later needs. PS: the "install guest addition" won't work because Fatdog does not auto-launch anything (and for good reason).

JustGreg, wine is 32-bit application. In fact it is the one created by our own green_dome So you also need to load the 32-bit compatibility SFS for it to run.

Hi! I'm having difficulties when mounting linux partitions in fatdog. I have a disk with many partitions, some of them containing another OS. Everytime I mount one of them, fatdog changes the permissions of the root directory in that partition to 770. It makes me broke two ubuntu based systems until I realize what was happening. Fortunately, once discovered the cause, the solution was easy, just restoring the permissions. Now I'm doing a chmod before unmounting, but that's not comfortable.. What could be happening and how is it fixable?
Another annoying thing occurs when running gparted. It tooks the drive icons, passes through a blender and throw them in aleatory order on the desktop. Never noticed that behavior by gparted before..

Quote:

nooby, the control panel can be navigated with Tab and cursor keys too. Items can be launched by pressing Enter key.

Hi! I'm having difficulties when mounting linux partitions in fatdog. I have a disk with many partitions, some of them containing another OS. Everytime I mount one of them, fatdog changes the permissions of the root directory in that partition to 770. It makes me broke two ubuntu based systems until I realize what was happening. Fortunately, once discovered the cause, the solution was easy, just restoring the permissions. Now I'm doing a chmod before unmounting, but that's not comfortable.. What could be happening and how is it fixable?

Edit /etc/eventmanager and use the right ACCESS_MODE and UMASK_MODE. UMASK_MODE is just 777 xorg ACCESS_MODE (or simply put, UMASK_MODE + ACCESS_MODE must be equal to 777).
There is a GUI for this using Fatdog Event Manager from Control Panel, but it only allows you to choose between two values: 770 and 750. On another note, Fatdog also chgrp the mountpoint to the current user's group. If you really really don't like this and want to disable this, edit /usr/sbin/fatdog-drive-icon-mount-helper.sh but then you're on your own.

Quote:

Another annoying thing occurs when running gparted. It tooks the drive icons, passes through a blender and throw them in aleatory order on the desktop. Never noticed that behavior by gparted before..

Fatdog uses udev directly for drive icons. Whenever gparted runs, it reads the drive in a such a way that forces the kernel to re-read the partition table (=not surprising for a partition table editor...), and thus kernel will issue udev "change" event. Fatdog responds to this change event by re-drawing the icons; unfortunately there is no way to ensure that the events are received in any particular order. Other puppies don't have this issue because they don't use udev directly, they use a daemon (pup_event_frontend) to poll for changes instead.

1. I am afraid there is a bug. I noticed it in 6.1.0 too, but now I'm sure something's not working right. When shutting down, it gets stuck on the "Spin down disks ..." line and doesn't shut off. I've waited more that 10 minutes.

It always does it after making the save file, but at other times too. Please note I don't save directly to home, but to a folder in home.

I can turn the computer off with the switch, and the file is indeed saved, but it shouldn't get stuck like that.

2. On an unrelated note, what program do I need to add to make the lives .sfs work? I do not connect to the internet on that computer. The dependency checker seems to work (?) in a weird way in Fatdog64 (yes, I also tried with the .pet).

This approach in FATDOG 611+ might be reconsidered as other OSes on a HDD/USB would be impacted. Please understand, though, that I am aware of much thought and consideration already in current system release.

Just a thought._________________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

1. I am afraid there is a bug. I noticed it in 6.1.0 too, but now I'm sure something's not working right. When shutting down, it gets stuck on the "Spin down disks ..." line and doesn't shut off. I've waited more that 10 minutes.

It always does it after making the save file, but at other times too. Please note I don't save directly to home, but to a folder in home.

I can turn the computer off with the switch, and the file is indeed saved, but it shouldn't get stuck like that.

This can happen for a number of reasons, most likely driver conflict with your hardware. Try booting with parameter "showerr" and it should let you see what is happening when you shutdown.

Quote:

2. On an unrelated note, what program do I need to add to make the lives .sfs work? I do not connect to the internet on that computer. The dependency checker seems to work (?) in a weird way in Fatdog64 (yes, I also tried with the .pet).

Yes, lives no longer work in 610 because it depends on certain libraries which got removed when we removed kino. I have re-uploaded the libraries as "lives_support", you need to install when you install lives in 610. (You need to select it manually as it is not indicated in the dependency check). For convenience, I'm also uploading lives.sfs which has all the needed libraries.

gcmartin wrote:

I recently got bit by this too.

Can you tell me the details of what happened and how you managed to overcome the situation?

Jamesbond, thanks for the detailed answers! I changed ACCES_MODE to 755 and UMASK_MODE to 022, and problem solved. The chgrp doesn't seems to be harmful, so I left as it was.

In a very very humble opinion, I think this permissions thing could be a serious trouble for a linux begginer (for example someone who has an ubuntu install and decides to gives fatdog a try. When he reboots he could be in front of a broken system, without elements to diagnose nor repair the damage - been there many times!! - Of course, he will never use fatdog again!). I hope this is constructive,

I think this permissions thing could be a serious trouble for a linux begginer.

it's confusing because there are 2 users spot and root active sometimes. using puppy 4.10 as linux beginner had sooo many crazy problems but i learned from them. and it didn't come with a fatdog control panel and everything in there which novice computer users are used to. the package manager didn't even have dependency checks, refresh package lists, resizeable window or make any sense!

When trying to get 32bit apps running on Fatdog64 it is useful to check whether libraries are class ELF64 or ELF32. The tool readelf will tell you. Errors occur when the 32bit app finds the 64bit library instead of the 32bit library.

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