Puppy Linux Discussion Forum

[nooby]

Thanks to both of you.
smokey thanks for the link to that pdf and for hosting all the files at
http://www.smokey01.com/software/Fatdog64-600/

I will look through them and decide on if I maybe need
use Geeqie because I am used to it and the one default
is too new to me. I fail to do full screen on that one.

[LateAdopter]

Hello Kirk & jamesbond

When I try to use Avidemux the GUI locks up by simply opening a file, TS or AVI, selecting PLAY and, after it starts playing, selecting STOP.

If I run avidemux3_qt4 from a terminal, there is an error during loading:

libQtScript.so.4 no such file or directory. Could this cause a problem?

There are no errors shown in the terminal when I select STOP.

If I open the file and just use the navigation controls, they seem to work normally.

Do you get this problem, or is it just me?

Thanks.

[Billtoo]

I'm running from a multi-session DVD+RW.
Computer
Processor 8x Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Memory 16395MB (208MB used)
Machine Type Physical machine
Operating System Fatdog64 [442447e63b]
User Name root (root)
Date/Time Sun 30 Dec 2012 02:08:40 PM GMT
Display
Resolution 3840x1080 pixels
OpenGL Renderer Gallium 0.4 on NVC8
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel PCH
Audio Adapter HDA-Intel - HDA NVidia
Monitors
Monitor 0 1920x1080 pixels
Monitor 1 1920x1080 pixels
OpenGL
Vendor nouveau
Renderer Gallium 0.4 on NVC8
Version 2.1 Mesa 9.0
Direct Rendering Yes
Network controller RaLink Device 3090

I used the Display Properties utility in the Desktop section of the control
panel to set up for 2 monitors.
It's working well so far.
Running nexuiz wrecked my Display Properties but it was an easy fix, I
think I'll install the nvidia pet in the package manager though.
I did:
OpenGL
Vendor NVIDIA Corporation
Renderer GeForce GTX 560 Ti/PCIe/SSE2
Version 4.3.0 NVIDIA 310.19
Direct Rendering Yes

[jamesbond]

[LateAdopter]

Hello jamesbond

Yes Oss seems OK on a quick check. I had changed the audio from dummy to ALSA default.

I notice that closing the window, when a video is playing, by clicking X, does close the window but does not stop the video playing.

Not very serious. Maybe the inability to load libADM_script_qt.so due to the missing dependency does matter.

Thanks for the suggestion.

[Billtoo]

I did an install to a 64gb flash drive with the fatdog installer.
Running on an hp desktop pc,
I start it with: savefile=ram:device:sdf1 waitdev=8
I tried it with:savefile=direct:device:sdf1 waitdev=8 but that didn't
work well at all, always waiting for apps to load etc.
Anyways, this is working well.

[nooby]

I used this one savefile=none as was recommended
but you maybe wanted to reuse a savefile you had
from the HD?

May I ask
What is the name for the program that create the analog Clock
and what is under it up to the right? Is that one built in maybe
only me not knowing about it?

[mdisaster2]

Just installed Fatdog 611 under Virtualbox 2.4.6. Bottom line, Fatdog it is downright awesome

In the virtual machine I set up (2 cores, 1024 Mb RAM) Fatdog works great, it is lightning fast, and on top of that mouse support under Virtualbox is downright perfect - actually I had full seamless mouse integration working out of the box, without even installing the Virtualbox Guest Additions.
(this is the case with some other distros but not with other Puppies, whose mouse is more or less broken under virtualbox, see for example the latest Distrowatch review of Slacko).

I did notice a slight problem with timezone setting though. Normally I set up my virtuals machine to use UTC time, then I set the correct timezone (Europe/Rome)in the guest system at install time, and that is all I have to do to see the correct time in the systray icon.

However in Fatdog I get the wrong time (GMT instead of GMT+1). I did go in the "Set date and time applet" and set the correct time, but I noticed it told me that I am on CET Time (which is not the case), and unless I messed something then at next reboot the time was wrong again. Even disabling NNTP doesn't seem to help. Did I miss whatever setting tells Fatdog that the hardware clock is set to UTC ?

Other questions, probably specific to the virtualbox environment.
- on boot I get a message about eth0 not being configured - skipping, however networking works fine.
- is WpaGUI for wireless only ? I thought so, but when I disabled the WpaGUI service and rebooted I lost ethernet connectivity as well.
- I am downloading the devx sfs to see if I can compile the Guest Additions (it seems a pity not to have the GA since Fatdog works so well in VB - later I'll report on my results). Are the kernel sources included in the sfs or do I need a separate download ?

Not virtualbox related:
- I could use an applet to set time from a Internet server (or is NNPT supposed to do the job ? )
- the SFS manager is great, but I really wish the interface was select-then-click, like the one of the Package manager.

[jamesbond]

[nooby]

Sorry I should refer to the post by Billtoo and his picture
which has a clock and some other things below it
a bit like the widget thing in Lupu? Okay I reboot and
have a look at it. thanks

I am in FD now but failed to get that clock going.
Does one have to use the terminal to activate it?

[nooby]

sorry me ask so much. When I am in the FD64 control panel
it force me to double click. Can I change that to single click please

How do I change that?

[Billtoo]

[nooby]

Thanks I use a similar on Lupu so I thought it looked familar
butdid not guess it would work on FD64? But I test that now then.
Thanks indeed

[smokey01]

[nooby]

Thanks Smokey,

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?

to make it less confusing. Rox is set to single click I talk about the
FatDog Control thing.

another annoying thing is that when I finally have the times correct
at Lupu and have set all the dials correct and then boot into FD64
and set it's time correct and then boot back into Lupu then Lupu clock
is one hour wrong again.

So it can be my fault failing to set the BIOS clock right
and setting the Lupu clock right and setting the FD64 clock right
so many options that can go wrong.

Is there some way in Lupu and FD64 to find out what the BIOS clock is
so I can know if either of these OS change the BIOS at reboot?