Puppy Linux Discussion Forum

[Henry]

Zigbert,

As per my note above I was quit impressed by the gui pf the latest Pbackup. But I have noted a problem, which reproducibly happens after I have used it to burn a cd of, say, pup_save.2fs. Emelfm2 then no longer runs!

Incidentally, I like emelfm2 a lot. Roxfiler of course is essential for several reasons, not least the thumbnail display. But emelfm2 is so convenient for example, for copying and renaming versions of pup_save.2fs back and forth between home and the folder I keep them in. Feels a little more secure than dragging between Rox windows, which tend to overlap and jump in a startling way.

Henry

[wingruntled]

I finally got to download 3.0. I had a few odd issues with it. To start I did a full HD install.
Like puppy 2.17.1 I had no sound with the onboard sound in the SIS 630 chipset on this Hitachi Deskview machine. No problem though, I just installed the snd-trident module with boot manager and that fixed that. I had to do the same with puppy 2.17.1 so it was easy this time. Everything seemed to work good except Gxine would not play full screen DVD's in any video mode. Now here is the odd thing. I installed EZpup 2.17R2 and I thought it fail because it never went beyond the checking dependentcies window. But after closing the window by clicking on it I noticed my desktop icons started changing after doing a mouse-over, so I rebooted the machine and I ended up with Icewm and everything worked. And for some odd reason Gxine now will play DVD's full screen.
Luck or what?

[Leon]

[edoc]

[Jesse]

[BlackAdder]

Not really a bug, but I noted that Puppy 3.00 does not load to ram on a 192MB machine. A quick comparison of memory usage on that machine shows:

[WhoDo]

I have noticed there is no longer an option to install Puppy as Frugal with data saved to the partition rather than a pup_save.2fs file.

That was my preferred install for most machines, as it gave all the benefits of a Frugal install in terms of upgrading, but didn't restrict my data to a single bag file that could become corrupt.

Was this a considered decision, Barry? Or did the option just fall by the wayside? Maybe I missed while I was absent moving house and jobs, or something.

[klasterson]

My problem:

this setting in xorg.conf doesn't make effect at all:

Section "Modes"
Identifier "Modes0"
ModeLine "1280x1024" 108.00 1280 1344 1456 1688 1024 1025 1028 1066 +hsync +vsync #modes0modeline0
EndSection

I have to set it manually with xvidtune on every bootup. In spite of click on Show button in Xvidtune it doesn't work...

In Xorg.0.log are this errors:
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) Warning, couldn't open module glx
(EE) Failed to load module "glx" (module does not exist, 0)

Other settings are saved correct so far.

I have GeForce FX 5200 and LG L1752 LCD.

[BarryK]

[Leon]

[BarryK]

[BarryK]

[BarryK]

[BarryK]

[PaulBx1]

A little more info on gxine. I was comparing playing a DVD in 2.16 and 3.00. In 3.00, I can resize the window, then play OK (except once it hung with no provocation), but if I play the video and resize while playing, it is a guaranteed hang of gxine. It does not help to kill gxine, you can't restart it again. I have to exit X altogether and restart it, then I can start gxine again. Same deal if I take the little progress indicator and move it forward or back; if I fool around with that enough 3.00 gxine hangs. 2.16 gxine does not have problems with these things. I tried in 3.00 to start gxine from a console window, hoping to see some message before it dies, but no luck. Bottom line, 3.00 gxine appears less robust than 2.16.

BTW, if I click the "USB interfaces" button of pupscan, it exits or hangs, and like gxine above cannot be restarted even after a kill. Kill may have a problem in this kernel...