Here's a strange quirk.
I have a new desktop - AMD Sempron Processor 3000+
I cannot get the CDs for LHP 5C or 5D to load.(I verified they work on my laptop).
A CD of LHP 4.1.2 loads OK and so does Fatdog64.
After booting from the CD and getting to the splash page, I've tried every combination of boot parameters but I cannot even see any messages. All that happens is the ... loading vmlinuz and initrd.gz messages, then "Ready".
I also set up grub, and tried booting after copying the files onto the hard disk but that also fails. Any known problems with AMD Sempron?
B.
Lighthouse Pup 5.00 G 185M
AMD Sempron Problem
[i]Laptop[/i]: Acer Aspire 5810TZ
8-bit,
I think you may be too enthusiastic to roll up your sleeves and get under the hood when you go to x-delta upgrade your lhp-mariner-c. The way we lazy people do is, first, make sure we have somewhere with about a gigabyte and a half of extra room, since we end up with two Mariner iso's. Usually that's in /mnt/home, not in a save-file. We make a new directory there and put into it our lhp-mariner500C iso (a silver disk icon), our lhp-mariner500-C-D iso-xdelta (a page witth green text) and our lhp-mariner-500-D md5 file (the usual blue text). Then, when you right-click on either the 500C iso or the iso xdelta you should get the xdeltaGUI menu entry at the bottom of the top group, right above "customize menu". If you left-click the xdeltaGUI on the Mariner500C iso you will get a fail, so left click the xdeltaGUI menu entry on the C-D Mariner iso xdelta file, thee green page. The GUI window should appear and say it is working and to wait.... When a new silver disk icon identified Mariner 500D iso appears, right-click on it then left-click the md5sumGUI menu entry, fourth from the top. It will check the integrity of the new D iso.
It's so quick and easy even us lazy procrastinators can get around to it and do it!
Note that to directly update your current installed frugal install instead of a copy of the C iso, you have to manually add the update files. That procedure is too complicated for me, so I just run the new iso and let it update in the usual "updating from...to..." puppy fashion.
Note 2 that sometimes menu-entries of added programs get lost in updating (also in running pfix=clean). If you open a console and type the program name it will start if it is still there. When I lose menu entries I put an icon on the desktop, because it is easier for me than learning to fix the menu (which I can never remember where is).
A couple of other things I do to slide by on the easy side, that you might find equally convenient are, in abiword, when the gui comes up full of text, just hit the new button. A new blank abiword gui appears and you can blow off the text-filled one behind it. And what we who are too lazy to open the hood and pull wires do to get rid of embarrassing start and stop sounds is move the top volume slider to zero and leave it there. It stays off through shutdowns and starts until moved back up, when we have to remember to move it to zero again, so not to upset librarians, wake the sleepers around us on the night-bus, or over-excite the pekingese of the lady on the next park-bench (or the lady if the sound is "hello", instead of "woof-woof").
I think you may be too enthusiastic to roll up your sleeves and get under the hood when you go to x-delta upgrade your lhp-mariner-c. The way we lazy people do is, first, make sure we have somewhere with about a gigabyte and a half of extra room, since we end up with two Mariner iso's. Usually that's in /mnt/home, not in a save-file. We make a new directory there and put into it our lhp-mariner500C iso (a silver disk icon), our lhp-mariner500-C-D iso-xdelta (a page witth green text) and our lhp-mariner-500-D md5 file (the usual blue text). Then, when you right-click on either the 500C iso or the iso xdelta you should get the xdeltaGUI menu entry at the bottom of the top group, right above "customize menu". If you left-click the xdeltaGUI on the Mariner500C iso you will get a fail, so left click the xdeltaGUI menu entry on the C-D Mariner iso xdelta file, thee green page. The GUI window should appear and say it is working and to wait.... When a new silver disk icon identified Mariner 500D iso appears, right-click on it then left-click the md5sumGUI menu entry, fourth from the top. It will check the integrity of the new D iso.
It's so quick and easy even us lazy procrastinators can get around to it and do it!
Note that to directly update your current installed frugal install instead of a copy of the C iso, you have to manually add the update files. That procedure is too complicated for me, so I just run the new iso and let it update in the usual "updating from...to..." puppy fashion.
Note 2 that sometimes menu-entries of added programs get lost in updating (also in running pfix=clean). If you open a console and type the program name it will start if it is still there. When I lose menu entries I put an icon on the desktop, because it is easier for me than learning to fix the menu (which I can never remember where is).
A couple of other things I do to slide by on the easy side, that you might find equally convenient are, in abiword, when the gui comes up full of text, just hit the new button. A new blank abiword gui appears and you can blow off the text-filled one behind it. And what we who are too lazy to open the hood and pull wires do to get rid of embarrassing start and stop sounds is move the top volume slider to zero and leave it there. It stays off through shutdowns and starts until moved back up, when we have to remember to move it to zero again, so not to upset librarians, wake the sleepers around us on the night-bus, or over-excite the pekingese of the lady on the next park-bench (or the lady if the sound is "hello", instead of "woof-woof").
CLAM1
I did the xdelta3 update on a seperate partition with 120 gigs of space.
That enough for you?
I also have on that partition, a directory I call ISO_files that contains most ISO's I have downloaded.
As to the menu entries for installed programs disappearing when upgrading a pupsave file, that should not happen and when it does, the backups should be placed in /tmp in a directory specified.
The directory the upgrade process says they are put in does not exist afterword to recover said files.
I guess if you have a version of Puppy up and customized you should back up your pupsave before the upgrade so as to be able to recover those files.
Either that, or say to h with any upgrades and use what you have.
Especially if you got it working the way you want!
If I upset anyone with this, so be it.
The last Puppy version that I have used without problems, after some fixes, is Puppy 431 frugal Beta 2.
I did the xdelta3 update on a seperate partition with 120 gigs of space.
That enough for you?
I also have on that partition, a directory I call ISO_files that contains most ISO's I have downloaded.
As to the menu entries for installed programs disappearing when upgrading a pupsave file, that should not happen and when it does, the backups should be placed in /tmp in a directory specified.
The directory the upgrade process says they are put in does not exist afterword to recover said files.
I guess if you have a version of Puppy up and customized you should back up your pupsave before the upgrade so as to be able to recover those files.
Either that, or say to h with any upgrades and use what you have.
Especially if you got it working the way you want!
If I upset anyone with this, so be it.
The last Puppy version that I have used without problems, after some fixes, is Puppy 431 frugal Beta 2.
Re: AMD Sempron Problem
What graphics chip does it have? Could this be KMS related? Also there is a BIOS setting on some systems for C1E. Disable it if present in BIOS and try again.Barburo wrote:Here's a strange quirk.
I have a new desktop - AMD Sempron Processor 3000+
I cannot get the CDs for LHP 5C or 5D to load.(I verified they work on my laptop).
A CD of LHP 4.1.2 loads OK and so does Fatdog64.
After booting from the CD and getting to the splash page, I've tried every combination of boot parameters but I cannot even see any messages. All that happens is the ... loading vmlinuz and initrd.gz messages, then "Ready".
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
C-F bug fix and GoogleEarth update
I have updated the C-F SFS for 5D:Barburo wrote:Hi Taz,
I seem unable to get C-F 0.7.9-1f to run at all in 5D. It worked fine in 5C. I tried C-F in KDE, LXDE and Xfce too. To be sure I did a clean install and retried with same C-F sfs. Same problem: not recognized.
CompizFusion-0.7.9-1g.sfs 16M C-F bug fix for Lighthouse Pup 5.00 D
GoogleEarth-5.2.1.sfs 32M Google Earth version update
8-bit,
I've been working on the Xdelta3 bug you found and discovered that the context menu item is missing when the .xdelta3 is saved to an NTFS or vfat partition. I've fixed that for the next release and will update the mimetype, default left-click action and GUI as well. CLAM01's suggestion to save into /mnt/home or another partition rather than in main file system, (pupsave) is something that hadn't occurred to me. I don't know yet if that would be related to the bug.
I haven't observed or figured out the missing menu items at upgrade yet. I'm assuming you have updated the menus (in JWM/Icewm, Menu | Refresh Menus | restart WM) or fixmenus in a terminal | restart X).
BarryK noted a bug /tmp/versioncleanup missing at upgrade. I will see if I can find and incorporate that fix.
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
8-bit,
120gb should be plenty, since the limitation is enough room in the end for two almost 700mb Mariner iso's and an about 100mb xdelta file. I always isolate the process into its own new directory, which I name for the upgrade. When done I delete all else and have only the new iso and its md5 in the directory, where I usually add my custom modifications of the version. I have to add a couple of programs to make my system usable for work, so I always make a custom version with the additions. When I add the proverbial one tweak over the line playing and wreck everything I just shovel out the broken bits, reload and have everything ready for work again.
Menu entries disappearing, even though they aren't supposed to seems to be one of those things computer systems seem to like to do, or maybe it's the daemons in them that like to, to keep us on our toes. Us lazy it makes have to think up quick-n-dirty work-around solutions. The more intelligent, curious and careful it recruits to computer programming. They who have to sort out and find the why and fix the glitch right the daemons thus separate from us who bailing-wire icons on our desktops, and hook in. The next you may know, if you have to fix the menu things, you may find yourself over your eyebrows in code and surrounded by daemons looking to you to massage them. Once they have you there will, of course, always be another with another ache or pain, demanding more massage...
The phantom tmp file I have run into, or failed to run into, too. To work around I make my custom systems and then make a couple of extra directories in /mnt/home where I park back-up copies of what I make or download that is important, that, in a worst case I want to not lose in a wreck of a save-file.
But the added programs whose menu entries disappear, not being gone, themselves, would not be in a removed stuff file, anyway, and I don't think menu upgrading saves old menu-files. You could probably do so before upgrading, though, making a bak copy or something.
My current full-time full-service working OS is a customized Mariner 443 that is doing all and doing all well, being stable and reliable. 500 I am still playing with, but coming up to upgrading to for work. My 443 custom is something over 900mb and lives in my disk drive on a 1.44gb Sony compact video-camera dvd rw, with a clone on a usb stick for portability.
120gb should be plenty, since the limitation is enough room in the end for two almost 700mb Mariner iso's and an about 100mb xdelta file. I always isolate the process into its own new directory, which I name for the upgrade. When done I delete all else and have only the new iso and its md5 in the directory, where I usually add my custom modifications of the version. I have to add a couple of programs to make my system usable for work, so I always make a custom version with the additions. When I add the proverbial one tweak over the line playing and wreck everything I just shovel out the broken bits, reload and have everything ready for work again.
Menu entries disappearing, even though they aren't supposed to seems to be one of those things computer systems seem to like to do, or maybe it's the daemons in them that like to, to keep us on our toes. Us lazy it makes have to think up quick-n-dirty work-around solutions. The more intelligent, curious and careful it recruits to computer programming. They who have to sort out and find the why and fix the glitch right the daemons thus separate from us who bailing-wire icons on our desktops, and hook in. The next you may know, if you have to fix the menu things, you may find yourself over your eyebrows in code and surrounded by daemons looking to you to massage them. Once they have you there will, of course, always be another with another ache or pain, demanding more massage...
The phantom tmp file I have run into, or failed to run into, too. To work around I make my custom systems and then make a couple of extra directories in /mnt/home where I park back-up copies of what I make or download that is important, that, in a worst case I want to not lose in a wreck of a save-file.
But the added programs whose menu entries disappear, not being gone, themselves, would not be in a removed stuff file, anyway, and I don't think menu upgrading saves old menu-files. You could probably do so before upgrading, though, making a bak copy or something.
My current full-time full-service working OS is a customized Mariner 443 that is doing all and doing all well, being stable and reliable. 500 I am still playing with, but coming up to upgrading to for work. My 443 custom is something over 900mb and lives in my disk drive on a 1.44gb Sony compact video-camera dvd rw, with a clone on a usb stick for portability.
Clamo1.
My mainstay seems to be a highly customized version of Puppy 431 scsi beta2 that Barry put out for testing and then pulled because of scsi disk booting problems.
I had updated the browser to the latest Seamonkey, added a patch for clean umount of the pupsave.2fs file, added a fix for using the man command from a command line, installled the Floppy Formatter program (I wrote the GUI for it) so I could format USB floppies, added pupsave-backup that I found on the forum, and most likely other fixes that I added and have forgotten.
I mainly keep it around for my SCSI hardware though.
I would like to modify lupu-510 (Puppy 510) to support my SCSI devices, but I am no experienced programmer by any means and although the source is included in devx, I still do not know just what I need for the 2.6.33.2 kernel to make it all work.
And yes, I have tried loading the devx and kernel source with bootmanager.
I have lots of drive space and 3 gigs of ram to play with.
I have already tried navigating to the source directory for the driver and trying he make file. But a file was missing there and I am sure there are others I need for SCSI to be successful.
I even went so far as to try to compile the kernel with SCSI support, but my resulting vmlinuz file was 4 megs and the original was 12 megs.
The interesting thing is that Puppy did boot with it. It kicked out an error of not being able to find lupu-510.sfs and the file was where it is supposed to be.
I restored the original kernel and it booted fine with it.
So here I sit all broken hearted. Tried to sh*t and only far*ed.
My mainstay seems to be a highly customized version of Puppy 431 scsi beta2 that Barry put out for testing and then pulled because of scsi disk booting problems.
I had updated the browser to the latest Seamonkey, added a patch for clean umount of the pupsave.2fs file, added a fix for using the man command from a command line, installled the Floppy Formatter program (I wrote the GUI for it) so I could format USB floppies, added pupsave-backup that I found on the forum, and most likely other fixes that I added and have forgotten.
I mainly keep it around for my SCSI hardware though.
I would like to modify lupu-510 (Puppy 510) to support my SCSI devices, but I am no experienced programmer by any means and although the source is included in devx, I still do not know just what I need for the 2.6.33.2 kernel to make it all work.
And yes, I have tried loading the devx and kernel source with bootmanager.
I have lots of drive space and 3 gigs of ram to play with.
I have already tried navigating to the source directory for the driver and trying he make file. But a file was missing there and I am sure there are others I need for SCSI to be successful.
I even went so far as to try to compile the kernel with SCSI support, but my resulting vmlinuz file was 4 megs and the original was 12 megs.
The interesting thing is that Puppy did boot with it. It kicked out an error of not being able to find lupu-510.sfs and the file was where it is supposed to be.
I restored the original kernel and it booted fine with it.
So here I sit all broken hearted. Tried to sh*t and only far*ed.
None of the principal developers want to know! As you see from my recent comments, I've encountered many systems that refuse to start properly or at all since that time. My enquiries remain ignored. It is very inconvenient for them. The only option for me has been to switch to Mint, Austrumi and a handful of others which perform flawlessly on all systems. Mint also recognises some of my webcams that others prefer to avoid.The last Puppy version that I have used without problems, after some fixes, is Puppy 431 frugal Beta 2.
As I've said many times, my strength is HW & my weakness is SW which limits my ability to cope with the breath-taking pace of recent 'progress'. One step forward...?!
Lighthouse Pup 5.00 D 223M Xorg-server 1.7.7
I just discovered Lighthouse Pup a few days ago and it's working very well for me.
I'm using xfce and I have installed many of the sfs modules.
I wish I'd found lhp sooner, it's one of the best imho.
Thanks.
I'm using xfce and I have installed many of the sfs modules.
I wish I'd found lhp sooner, it's one of the best imho.
Thanks.
LHP_5.00-D_update1.pet
Thank you, Billtoo. 
Yesterday I found that some files, notably /bin/mount-FULL and /usr/share/alsa may not get updated when upgrading from LHP 5.00 C to D, build 490->495. This can cause audio problems and a 'failed' status during boot-up at "Making the filesystem usable...". Some dialogs may show 'puppyversion' as 490, instead of 495. I have corrected this for the next release, and attached a PET below with these and a few other updates for 5D:
Yesterday I found that some files, notably /bin/mount-FULL and /usr/share/alsa may not get updated when upgrading from LHP 5.00 C to D, build 490->495. This can cause audio problems and a 'failed' status during boot-up at "Making the filesystem usable...". Some dialogs may show 'puppyversion' as 490, instead of 495. I have corrected this for the next release, and attached a PET below with these and a few other updates for 5D:
- - /bin/mount-FULL, /etc/rc.d/rc.update, rc.sysinit
- /etc/puppyversion, /usr/local/bin/Xdelta3GUI
- .xdelta3 mimetype and default rox action
- sqlite-3.6.23.1, /usr/share/alsa
- PPM excludes and Lighthouse Help Page
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
TazOC!
I tried your <window manager | refresh menu> suggestion and it worked!! It was even easier than my lazy way!!! Now I can be lazier still and feel competent, too!!!! Thank you!
I now have only xzgv without a menu entry, which is no surprise, since I install it by downloading a tgz and extracting the binary to drop into bin. I only launch xzgv from the desktop anyway, dropping a file on it when I need to use the contents or reference something in it. There is nothing better for burrowing around in large files of graphic content... I mean of tiffs and jpegs...
Also, per your earlier suggestion, I downloaded and installed your Graphics 3in1c sfs, which I hadn't looked to notice was there before. It works everywhere, and, of course, works great. I at the same time downloaded an update vlc sfs (1.0.6), but haven't yet found how to launch it. The wbar and menu entries still launch 1.0.0, according to the <help | about> info.
I tried your <window manager | refresh menu> suggestion and it worked!! It was even easier than my lazy way!!! Now I can be lazier still and feel competent, too!!!! Thank you!
I now have only xzgv without a menu entry, which is no surprise, since I install it by downloading a tgz and extracting the binary to drop into bin. I only launch xzgv from the desktop anyway, dropping a file on it when I need to use the contents or reference something in it. There is nothing better for burrowing around in large files of graphic content... I mean of tiffs and jpegs...
Also, per your earlier suggestion, I downloaded and installed your Graphics 3in1c sfs, which I hadn't looked to notice was there before. It works everywhere, and, of course, works great. I at the same time downloaded an update vlc sfs (1.0.6), but haven't yet found how to launch it. The wbar and menu entries still launch 1.0.0, according to the <help | about> info.
LHP 5.00 C had some old leftover vlc binaries in /usr/bin. In ROX-Filer right-click | Mount-data0 to mount the Vlc-1.0.6-i486b.sfs and copy the vlc files over from /mnt/data0/usr/bin/*vlc* to /usr/bin/.CLAM01 wrote:downloaded an update vlc sfs (1.0.6), but haven't yet found how to launch it. The wbar and menu entries still launch 1.0.0, according to the <help | about> info.
If you're in LHP 5D and have previously installed vlc 1.0.0.pet, vlc 1.0.0 is still in your pupsave layer, which takes precedence over any files (with the same name and path) in an SFS layer below. Type which vlc in a terminal to see where the binary being executed is. The Vlc-1.0.6-i486b.sfs uses /usr/bin/vlc. If vlc 1.0.0 is at the same location, then it is 'hiding' the newer version. I would uninstall vlc 1.0.0 with the same method that you installed it.
If you've done that and vlc in a terminal reports an error like 'command not found' then force a purge of whiteout (.wh.*) files from the pupsave layer, e.g., /initrd/pup_rw/usr/bin/.wh.vlc by adding or removing an SFS with the BootManager and rebooting. When a file is deleted from a read-only layer below the top layer, a whiteout .wh.<filename> is created which effectively hides it from normal access. These whiteouts are only visible when navigating within the pupsave (top layer) at /initrd/pup_rw/. (IIRC when the pupsave is on a flash drive, the pupsave layer is at /initrd/pup_ro1)
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
CompizFusion-0.7.9-1g.sfs works fine with LXDE Xfce and KDE4.
I've been using Xfce for a while and it seems that I must double click any icon on the desktop to activate. I can set to single click within folders - even within the Desktop folder, but not from the desktop. Any way to set this to single click (or is it a characteristic of Xfce)?
B.
I've been using Xfce for a while and it seems that I must double click any icon on the desktop to activate. I can set to single click within folders - even within the Desktop folder, but not from the desktop. Any way to set this to single click (or is it a characteristic of Xfce)?
B.
[i]Laptop[/i]: Acer Aspire 5810TZ
Xfce desktop
Hi Barburo,Barburo wrote:CompizFusion-0.7.9-1g.sfs works fine with LXDE Xfce and KDE4.
I've been using Xfce for a while and it seems that I must double click any icon on the desktop to activate. I can set to single click within folders - even within the Desktop folder, but not from the desktop. Any way to set this to single click (or is it a characteristic of Xfce)?
B.
Thank you for testing the updated C-F add-on. Tazmod asked about the Xfce desktop a while back and here was my reply:
-TazOCMy search for a workaround that allows single-clicking the desktop icons was not very fruitful. You can either hide all the icons except the Trash and make do with Wbar, or possibly convert the desktop to Nautilus instead of Xfce, but I think I would miss the Xfce context menu and other features that Nautilus doesn't have; not to mention the dependencies that might be needed.
What I usually do is leisurely right-click | Open when I don't want to rapidly double click. I read somewhere that the gtk in Xfce requires a double-click, but I don't know why you can single-click in Thunar but not on the Xfce desktop.
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
mtpaint 3.34.55 compiled
I compiled mtPaint 3.34.55 on Lighthouse 4.4.3
using configuration
I made a pet package that should run on most Puppies.
New feature -opens SVG format.
DOWNLOAD HERE
________________________________________________________________
using configuration
Code: Select all
./configure --bindir=/usr/bin release GIF gif jpeg tiff gtk2 staticft intlI made a pet package that should run on most Puppies.
New feature -opens SVG format.
DOWNLOAD HERE
________________________________________________________________
-
its-me-again
- Posts: 109
- Joined: Thu 29 Apr 2010, 05:23
problems
Hi all i am testing lighthouse pup 5.00 d update. there is no re-size puppy save file in the menu. its been removed. i looked 3-4 times over the menu with a fine tooth comb. now i cant use pup save file. its to small.
my save file is teh ext3 version one with light encryption. i don't think that should make a difference.
also my standard keyboard layout is slightly messed up. both the laptop and teh External kboards are the same. teh arrow keys the group containing insert home etc adn carious others this is most annoying. i have set teh keyboard to us so it should be normal. this seems to be a fault or bug.
also i installed some sfs files only one has come up on desktop. arg y the other ones not there i never know.
are there any fixes or workarounds for these. please.
my save file is teh ext3 version one with light encryption. i don't think that should make a difference.
also my standard keyboard layout is slightly messed up. both the laptop and teh External kboards are the same. teh arrow keys the group containing insert home etc adn carious others this is most annoying. i have set teh keyboard to us so it should be normal. this seems to be a fault or bug.
also i installed some sfs files only one has come up on desktop. arg y the other ones not there i never know.
are there any fixes or workarounds for these. please.
Re: problems
To resize personal save file in KDE4 with Kickoff Menu style, just type resize in search bar and it will show the resize program. With lxde or jwm you will find it in the utility section of the menu. As for the other problems you mention, they suggest a bad download or corrupt installation. Ext3 is the best choice as it is the safest version for a save file.its-me-again wrote:Hi all i am testing lighthouse pup 5.00 d update. there is no re-size puppy save file in the menu. its been removed. i looked 3-4 times over the menu with a fine tooth comb. now i cant use pup save file. its to small.
my save file is teh ext3 version one with light encryption. i don't think that should make a difference.
also my standard keyboard layout is slightly messed up. both the laptop and teh External kboards are the same. teh arrow keys the group containing insert home etc adn carious others this is most annoying. i have set teh keyboard to us so it should be normal. this seems to be a fault or bug.
also i installed some sfs files only one has come up on desktop. arg y the other ones not there i never know.
are there any fixes or workarounds for these. please.
Re: problems
Hi, please indicate which Window Manager/Desktop you are using. In IceWM/JWM use the Refresh Menus tool (bottom of main menu, (IceWM Menu | Window Manager | Refresh Menus.) Or type resizepfile.sh in a terminal.its-me-again wrote:Hi all i am testing lighthouse pup 5.00 d update. there is no re-size puppy save file in the menu. its been removed. i looked 3-4 times over the menu with a fine tooth comb. now i cant use pup save file. its to small.
Usually that is because the Xvesa video driver was selected. Xvesa is a very limited fallback to use if all others fail. Exit X to CL and type xorgwizard and try Option 3 xorgwizard, force vesa.also my standard keyboard layout is slightly messed up. both the laptop and teh External kboards are the same. teh arrow keys the group containing insert home etc adn carious others this is most annoying. i have set teh keyboard to us so it should be normal. this seems to be a fault or bug.
Most SFS files do not have desktop icons. Use Refresh Menus (see above) after rebooting and their menu entries should appear. In IceWM, JWM point at highest item in long menus to scroll up and lowest item to scroll down. Menu items can also be found by opening File System | /Applications and left-click on the desired .desktop file.also i installed some sfs files only one has come up on desktop. arg y the other ones not there i never know.
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
Re: mtpaint 3.34.55 compiled
Thank you don570, I will try to include it in the next release.don570 wrote:I compiled mtPaint 3.34.55 on Lighthouse 4.4.3
I made a pet package that should run on most Puppies.
New feature -opens SVG format.
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
Awwwww,......
I just got my copy of Lighthouse Pup 5.00 (by "snail-mail"). I can use it just fine as a live CD...but can't seem to get it to work when I do a full install. I starts to boot just fine, then after a second or two, just goes to black screen,...then just goes down and re-boots,....and re-boots,...and re-boots,....
Yeah,...maybe I got ahold of a bad CD. (yuck!) I Like the live CD, anyhow. Gosh,...wish I could install it on HD, though (maybe I'll try again on getting a good CD).
EDIT: hold on,....gonna try it on one of my other older PIIIs....(maybe it was the computer I tried to put it on,....here goes). LIke I said,...I REALLY like what I saw on the live CD. This, and john biles's TEENpup are just sooooooo cool.
I just got my copy of Lighthouse Pup 5.00 (by "snail-mail"). I can use it just fine as a live CD...but can't seem to get it to work when I do a full install. I starts to boot just fine, then after a second or two, just goes to black screen,...then just goes down and re-boots,....and re-boots,...and re-boots,....
Yeah,...maybe I got ahold of a bad CD. (yuck!) I Like the live CD, anyhow. Gosh,...wish I could install it on HD, though (maybe I'll try again on getting a good CD).
EDIT: hold on,....gonna try it on one of my other older PIIIs....(maybe it was the computer I tried to put it on,....here goes). LIke I said,...I REALLY like what I saw on the live CD. This, and john biles's TEENpup are just sooooooo cool.