Posted: Sun 09 Oct 2011, 01:48
sszindian, I am still thinking, Is this a frugal install or LiveCD that has the savefile problem?
READ-ONLY Archive
https://oldforum.puppylinux.com/
Playdayz,playdayz wrote:sszindian, I am still thinking, Is this a frugal install or LiveCD that has the savefile problem?
A short comment:rerwin wrote:Please do not wait. It does not apply to most upgrade situations and never to full installations. Proceed with your upgrade!Richardscsijon wrote:?so now all I need is to await your pre-installer pet and I can go ahead?
jhect, Yes. Click the Install icon on the desktop, then click the bottom button on the dialogue that opens, Run Puppy Package Manager. Then look in the bottom right corner of Puppy Package Manager to see if Instant Update 001 is listed as installed.Is there a way to find out if IU 001 installed?
sszindian, This is going to sound weird, but I have seen it myself, that's why I asked. Sometimes Puppy would give me a Kernel Panic when booting a Live CD. I was puzzled and frustrated but on a whim I rearranged the CD and HDD connections to the motherboard. With SATA drives there are several possible connections for each. Believe it or not, Lucid then booted where the same CD had given a kernel panic earlier. I can only conclude it is something about timing or priority of the drives, who knows. This has happened twice with two different Lucids--5.2.8 was one of them. I am not suggesting you rearrange your drive cables--a Live CD should not have that problem, but as I said, I have seen it twice and rearranging the cables fixed it both times. However, as far as I can recall, the problem arose in trying to boot the LiveCD, not after it had booted and created a savefile. In fact, consider carefully if you are not comfortable inside your computer.I boot 'all puppy's' from a CD
Anytime you run a live CD of Puppy with the option puppy pfix=ram.scsijon wrote:upgrade starts here:-
Install from CD using "puppy pfix=ram,noswap"
-----------------
menu>setup>puppy universal installer
!all ok to clicking upgrade button
!I wonder if it should include the word upgrade in pui's first screen?
all seems ok with upgrade, reboot next
-----------------
shutdown
?0 it wanted to create a savefile, I did so with defaults
------------------
Code: Select all
(gtkdialog3:2385): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:3079: signal name `depressed' is invalid for instance `0x8518a70'
When I remaster a live cd, after adding all the changes I want, I delete /root in /tmp directory and copy changed root directory to /tmp.rerwin wrote:
Regarding majorfoo's concern about the "message that puppy was not shut down properly" when booting a remastered CD, the indication of that, hidden file /etc/.XLOADED, does not get copied into the remastered CD image. At least I don't see how it could be, in the remasterpup2 script. Please try again with 528 to see if it still happens, and let me know.
Richard
Thanks pemasu, that confirms what I have discovered also. Yes, gnome-mplayer is deinterlaced by default. XineDVD was not however and that will change in Update 002.Interlaced is for CRT monitors. LCD and plasma screens needs deinterlaced video.
Gnome-Mplayer has deinterlaced enabled as default, I think.
Thanks Geoffrey. That appears to be a Warning. Did the program crash or keep running successfully? If it crashed then I need to do something, but if it kept running successfully then I don't--maybe the gtkdialog team doesI noticed this when running Menu Entry Maker from the terminal and select the combobox for Start with or Category
Code:
(gtkdialog3:2385): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c signal name `depressed' is invalid for instance `0x8518a70'
can anyone else confirm this is the case, I've posted this error on the Gtkdialog Development thread.
The program still runs fine, might have to rewrite it at a later date though, I guess some of the other older scripts will suffer the same fate.playdayz wrote:Thanks Geoffrey. That appears to be a Warning. Did the program crash or keep running successfully? If it crashed then I need to do something, but if it kept running successfully then I don't--maybe the gtkdialog team doesI noticed this when running Menu Entry Maker from the terminal and select the combobox for Start with or Category
Code:
(gtkdialog3:2385): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c signal name `depressed' is invalid for instance `0x8518a70'
can anyone else confirm this is the case, I've posted this error on the Gtkdialog Development thread.
majorfoo,majorfoo wrote:When I remaster a live cd, after adding all the changes I want, I delete /root in /tmp directory and copy changed root directory to /tmp.
Next I delete /etc in /tmp directory and copy changed etc directory to /tmp.
Reason for this is to insure that ALL changes I made carried forward to the new iso.