Lighthouse Pup 5.00 G 185M

For talk and support relating specifically to Puppy derivatives
Post Reply
Message
Author
ICPUG
Posts: 1308
Joined: Mon 25 Jul 2005, 00:09
Location: UK

#106 Post by ICPUG »

Many, many thanks Tazoc for the explanation of the workings of Xorg wizard in LHP. That should keep me busy for a while in improving my education.

This LHP is going to be a fixture on my laptop now as the Puppy to use when you want a bit more than the basic Puppy (in my case Wine, Open Office and the ability to play as many video codecs as possible).

User avatar
Q5sys
Posts: 1105
Joined: Thu 11 Dec 2008, 19:49
Contact:

wow

#107 Post by Q5sys »

so I take about a month off and i'm left in the dust. lol
Guess I need try to catch up on whats been done through the A version into the B version.
TazOC, any ideas on when the KDE expansion will be completed? A bunch of my apps use a ton of KDE libs, just looking forward to when I can jump in the deep end with v5 and splash around with it. :P
(no rush, just curious)

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

Re: wow

#108 Post by tazoc »

Q5sys wrote:so I take about a month off and i'm left in the dust. lol
Guess I need try to catch up on whats been done through the A version into the B version.
TazOC, any ideas on when the KDE expansion will be completed? A bunch of my apps use a ton of KDE libs, just looking forward to when I can jump in the deep end with v5 and splash around with it. :P
(no rush, just curious)
Hi Q5sys,
Sure, I found that KDE 4 was unstable with the radeon Xorg driver, on my hardware, at least--and I wasn't sure if that was the cause or if something else amiss. But since I compiled the ATI Catalyst driver and switched over to it, KDE 4 is now very stable, even with desktop effects and shadows enabled. The last piece I've been working on is the latest Moblock IP range blocking packages, that work well with KDE. It requires an updated iptables which is in the base ISO. So I'm debugging LHP 5.00 C with hplip-3.9.12 HP Scanner Driver (thanks to Jim1911), iptables-1.4.7, libnl-1.1 (thanks to BK), Flash-10.1.53.64, atk-1.30.0, gslapt-0.5.3b, PPM from Spup 0.2, SeaMonkey 2.05 and a few bugfixes. I hope to release that next week and then Mariner and a large KDE 4.4.4 SFS with many updates.
-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]

User avatar
Q5sys
Posts: 1105
Joined: Thu 11 Dec 2008, 19:49
Contact:

Re: wow

#109 Post by Q5sys »

tazoc wrote:Sure, I found that KDE 4 was unstable with the radeon Xorg driver, on my hardware, at least--and I wasn't sure if that was the cause or if something else amiss. But since I compiled the ATI Catalyst driver and switched over to it, KDE 4 is now very stable, even with desktop effects and shadows enabled. The last piece I've been working on is the latest Moblock IP range blocking packages, that work well with KDE. It requires an updated iptables which is in the base ISO. So I'm debugging LHP 5.00 C with hplip-3.9.12 HP Scanner Driver (thanks to Jim1911), iptables-1.4.7, libnl-1.1 (thanks to BK), Flash-10.1.53.64, atk-1.30.0, gslapt-0.5.3b, PPM from Spup 0.2, SeaMonkey 2.05 and a few bugfixes. I hope to release that next week and then Mariner and a large KDE 4.4.4 SFS with many updates.
-TazOC
Sweet, I'll work with than then and move forward. I compilied the newest intel driver for A... but that was back before we figured out the problem. Once I get C up and running I'll recompile it and if everything works smoothly, i'll upload it for everyone who is using Intel Gfx.

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

intel driver compiling

#110 Post by tazoc »

Q5sys wrote:I compilied the newest intel driver for A... but that was back before we figured out the problem. Once I get C up and running I'll recompile it and if everything works smoothly, i'll upload it for everyone who is using Intel Gfx.
That sounds good, what website has the source you used? Was it http://intellinuxgraphics.org/install.html and http://xorg.freedesktop.org/archive/ind ... r/?C=M;O=D? If and when you recompile the Intel drivers it would be great if you could make a few notes to share in case you're away and we might want to repeat the task.
Thanks,
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]

User avatar
Q5sys
Posts: 1105
Joined: Thu 11 Dec 2008, 19:49
Contact:

Re: intel driver compiling

#111 Post by Q5sys »

tazoc wrote:That sounds good, what website has the source you used? Was it http://intellinuxgraphics.org/install.html and http://xorg.freedesktop.org/archive/ind ... r/?C=M;O=D? If and when you recompile the Intel drivers it would be great if you could make a few notes to share in case you're away and we might want to repeat the task.
Thanks,
TazOC
When I did it last time, I grabbed it from the Intel site, along with all of the requirements that the intel site said it needed (mesa, cairo, etc). Granted you already had mesa in A, but I went and did it anyway. This time I'll probably just try to do the driver only and see if it works well, then if it doesnt add in something and try again. That way its the smallest package possible and doesnt possibly introduce any issues into LHP.
So out of the list, what does LHP v5 already have?
3D driver: mesa 7.8.1 release
Libdrm: libdrm-2.4.20 release
Cairo: cairo-1.9.6 release
Clutter: clutter-1.2.4 release

I will have to go with the 2010 Q1 driver since the Q2 driver requires a 2.6.34 kernel.

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

Re: intel driver compiling

#112 Post by tazoc »

Q5sys wrote:So out of the list, what does LHP v5 already have?
3D driver: mesa 7.8.1 release
Libdrm: libdrm-2.4.20 release
Cairo: cairo-1.9.6 release
Clutter: clutter-1.2.4 release

I will have to go with the 2010 Q1 driver since the Q2 driver requires a 2.6.34 kernel.
Libdrm-2.4.20 is fully in the base ISO.

LHP Base has all of mesa-7.8.1 except the huge dri modules in /usr/lib/xorg/modules/dri/. Those are in Mariner SFS except for the generic swrast_dri.so, which is in the Base ISO. So the full mesa requires the Mariner SFS due to size constraints.

Cairo is 1.8.8. Clutter is missing.

Pkg names and versions for the base ISO are in /initrd/pup_ro2/var/log/packages; open one with a text editor for description of pkg. Most pkgs currently installed, inc. SFS add-ons are in /var/log/packages. Gslapt shows these also.

Sidenote: In LHP 5C I'm including /bin/bash4, compiled by BarryK for testing. I edited /usr/bin/Console-LHP

Code: Select all

SHELL=/bin/bash4
to use bash4. So far it's OK now in Sakura. To switch everything to bash4.1, rename /bin/bash4 to /bin/bash. Please indicate if you have done that and found a bug with a script.
Thank you,
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]

drblock2
Posts: 153
Joined: Mon 19 Jan 2009, 12:38

#113 Post by drblock2 »

tazoc,

First let me thank you for the most impressive Puppy ever. Most of the discussion so far has understandably centered around getting X to work. I could report some adventures with this as well, but fundamentally, as soon as I added nomodeset to the kernel line in my grub menu, the display appeared and the rest was a question of adjusting things to my liking.

There are, however, two major bugs lingering on from earlier Pups. Here they are with solutions:

1. pnethood does not connect to a Windows XP share unless you type something (even one character) in the login name and password boxes. Shinobar created a fix for this:

http://208.109.22.214/puppy/viewtopic.p ... 5388963ba1

2. CUPS, even when installed from the Wizard, does not offer the option "Windows Printer via SAMBA". Without this, you will not be able to use a printer connected to a Windows machine via smb. Growler provided a sure-fire solution for Puppy 4.2.1. Copy /opt/samba/bin/smbspool to /usr/lib/cups/backend/smb. For reasons unknown, the link smb in /backend/ does not work. Delete it, copy smbspool and rename it "smb".

Now, you will be able to access remote files and print on a Windows server along with all the other wonderful features that work right out of the box.

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

#114 Post by tazoc »

Hi drblock2,
Thank you for the feedback and helpful bug fixes. I will incorporate them into the next release, as I'm almost done uploading 5.00 C and am busy with web site updates. I've been working since early this morning and I'm beat... it looks like I won't be able to finish up this release today. :( I wish I could say it's already done, but it'll just have to wait until tomorrow.
-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]

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

Lighthouse Pup 5.00 C released

#115 Post by tazoc »

Lighthouse Pup 5.00 C Base ISO

* Abiword, Gnumeric, SeaMonkey, Flash plugin and Transmission updated
* Added hplip-3.9.12 HP Scanner Driver (thanks to Jim1911) and ttf-thai-arundina (Thai font rendering).

Mariner ISO 5.00 C

* Base ISO plus Mariner, Xfce, OpenOffice, Opera and VirtualBox SFS add-ons.
* Mariner SFS updated to 5C_490; (others unchanged)
updated Firefox 3.6.6, JavaRE-6u20 and added wqy-zenhei free font (Asian font rendering)

KDE 4.4.4 C SFS

* KDE 4.4.4 plus Amarok 2.3.1b1, K3b Disc Burning, KDE Edu pack
* Interactive globe wallpaper
* Updated CdKase and Sidebar desktop applets
* Alternative Plasma Netbook interface

If you experience a slowdown or freeze in KDE, disable Desktop Effects: System Settings | Desktop | Desktop Effects | uncheck Enable Desktop Effects | Apply | Close & restart X. Do the same if CdKase or Sidebar's background is washed out or bright.

-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]

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

#116 Post by Jim1911 »

Hi TazOC,

Your new Lighthouse Pup 5.00 C is really superb. The auto-setup is flawless with my system. All that was necessary for a complete setup was to install your nvidia 195 pet and setup my HP printer. CUPS detected it properly and the scanner works without any extra setup.

Minor oversight, Bibletime is missing these dependencies in the current sfs: libgssapi-krb5.so.2, libkrb5.so.3, libk5crypto.so.3, libkeyutils.so.1, libkrb5support.so.0, libkutils.so.1 which were probably in your older KDE sfs. Also, BibleTime 2.7 was just released, so you may want to update it when you add the missing dependencies. Thanks for adding e-Sword to the WBAR setup.

Although, KDE is loaded, I haven’t tried it yet, having too much fun exploring the other features. :lol:

Thanks again for another excellent distribution,
Jim :D

gcmartin

What does this installation note really mean?

#117 Post by gcmartin »

Deleted - duplicate entry
Last edited by gcmartin on Thu 01 Jul 2010, 17:19, edited 1 time in total.

gcmartin

What does this installation note really mean?

#118 Post by gcmartin »

Can anyone provide an example of this instruction for Lighthouse installation.
On the Lighthouse website at this location ===> http://www.lhpup.org/tips-lhp.htm#Installation
One of the notes is
Note 2: All files except for the last (extra SFS files) can be placed in a directory one level deep so that multiple installs can be placed in the same partition.
Above the note, the paragraph is talking about folder /mnt/Home. I need help understanding what is meant by this note.
  1. Can anyone supply an example of the folder that this should reside in?
    AND
  2. Is the mention of "extra SFS files" referring to the line 'Optional: SFS files e.g., 5-LHP-Mar-4f_443.sfs'?
It occurs that a excerpt of the discussion from that website would be appropriate, here: So...

Code: Select all

After rebooting into your newly saved Lighthouse environment, click on the Pmount Drives icon on the desktop or Wbar launcher, and the 'Mount' button for your CD/DVD drive. A window should open showing the files below. Then click on the File System icon, click on 'mnt' and 'home'. Drag and drop the following files from the Lighthouse CD-Rom to this /mnt/home folder (where the spupsave.3fs file is located.) When prompted to copy or move the files, select copy. This is the recommended Frugal Install:

    * spup-nnn.sfs (where nnn is the version e.g., spup-480.sfs)
    * initrd.gz
    * vmlinuz
    * click-to-verify-lhp or click-to-verify-mariner
    * Optional: SFS files e.g., 5-LHP-Mar-4f_443.sfs

Note 2: All files except for the last (extra SFS files) can be placed in a directory one level deep so that multiple installs can be placed in the same partition. This is ideal when using a GRUB bootloader (Menu | System | Utility | GRUB Bootloader Config.)
Lastly, if I wanted to do a 2nd installation of a different version (from iso), what would I do differently?

Thanks in advance for your explanation(s)

gcmartin

Boot failure - Downloaded Mariner ISO and burned to CD

#119 Post by gcmartin »

This may be a common problem, but I've got it again. This is what I did leading up to the problem
  1. Downloaded Mariner 5.00C ISO and the md5 file as well.
  2. I md5sum the ISO and it matches with the md5 file.
  3. Burned ISO to a blanked CDRW.
I'm getting boot failures on each PC I attempt. What does the LAST message, in the list below, really mean? Messages are

Code: Select all

Loading drivers needed to access disk drives ...	done
Locating main file and session files...	done
 Loading spup-490.sfs (sr0)
 MinRAM to copy: 413M free RAM: 1772M... copying to ram..........	done
Setting up the layered filesystem...	done
Performing a 'switch_root' to the layered filesystem...Kernel panic - not syncing: Attempted to kill init!
The systems stopped at the last message above with a flashing cursor.

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

Re: What does this installation note really mean?

#120 Post by Jim1911 »

gcmartin wrote:Can anyone provide an example of this instruction for Lighthouse installation.
On the Lighthouse website at this location ===> http://www.lhpup.org/tips-lhp.htm#Installation
One of the notes is
Note 2: All files except for the last (extra SFS files) can be placed in a directory one level deep so that multiple installs can be placed in the same partition.
Above the note, the paragraph is talking about folder /mnt/Home. I need help understanding what is meant by this note.
  1. Can anyone supply an example of the folder that this should reside in?
mnt/home refers to the partition that the pup is installed on and is the only partition that must be mounted on bootup. For example on partition sda2 on my computer I have multiple frugal pups installed each in it's own directory.

mnt/home or the sda2 partition, is the root level where all extra sfs files should be placed except the base distribution sfs file. Extra SFS files for all pups can be located here and they will not be loaded unless specified to be loaded by the Boot Manager.

mnt/home/Lighthouse is a directory one level deep, this directory must contain the Lighthouse files including the base sfs file which for the latest version is spup-490.sfs.

mnt/home/Lucid is another directory one level deep and includes the base sfs file luci-207 along with the other Lucid files

You may add as many pups as you like without them interfering with each other as you have available space.

An example menu.lst entry is:

Code: Select all

Linux bootable partition config begins
  title Lighthouse  (on /dev/sda2)
  root (hd0,1)
  kernel /Lighthouse/vmlinuz pmedia=satahd pfix=fsck pdev1=sda2 psubdir=Lighthouse
  initrd /Lighthouse/initrd.gz
# Linux bootable partition config ends

gcmartin

Lighthouse Pup 5.00 C 231M k2.6.33.2

#121 Post by gcmartin »

@Jim1911 Thank you for helping me.

I want to ensure that I am clear, thanks to you, along with the website's writings. (Seems that there is a discrepancy on where the base pup file, spup-490.sfs, should be...either it should be in base or it should be in a sub-directory; say "/mnt/home/Lighthouse")
If I understand correctly, /mnt/home is the base directory. It happens to reside on /dev/sda2. Because it is the base, this is then, also, the root-level directory for the Lighthouse system. In that base directory, there MUST be the following (which was copied from the Lighthouse CD):
  1. DO NOT COPY ===> spup-nnn.sfs (where nnn is the version e.g., spup-490.sfs)
  2. initrd.gz
  3. vmlinuz
  4. click-to-verify-lhp or click-to-verify-mariner
  5. All other SFS files from the CD
NOW, NEXT, COPY spup-490.sfs to /mnt/home/Lighthouse

If I am to use the menu.lst as you suggest, I should have a folder on sda2 that is /mnt/home/Lighthouse for the menu.lst to work.
Right?
Thanks in advance.

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

Re: Lighthouse Pup 5.00 C 231M k2.6.33.2

#122 Post by Jim1911 »

gcmartin wrote:@Jim1911 Thank you for helping me.

I want to ensure that I am clear, thanks to you, along with the website's writings. (Seems that there is a discrepancy on where the base pup file, spup-490.sfs, should be...either it should be in base or it should be in a sub-directory; say "/mnt/home/Lighthouse")
If I understand correctly, /mnt/home is the base directory. It happens to reside on /dev/sda2. Because it is the base, this is then, also, the root-level directory for the Lighthouse system. In that base directory, there MUST be the following (which was copied from the Lighthouse CD):
  1. DO NOT COPY ===> spup-nnn.sfs (where nnn is the version e.g., spup-490.sfs)
  2. initrd.gz
  3. vmlinuz
  4. click-to-verify-lhp or click-to-verify-mariner
  5. All other SFS files from the CD
NOW, NEXT, COPY spup-490.sfs to /mnt/home/Lighthouse

If I am to use the menu.lst as you suggest, I should have a folder on sda2 that is /mnt/home/Lighthouse for the menu.lst to work.
Right?
Thanks in advance.
No, those files copied from the CD should all be in the /mnt/home/Lighthouse. You are not correctly reading my comments. I'll try to clarify since the use of mnt/home is apparently confusing. Instead, refer to it as dev/sda2. mnt/home is simply the partition on which the pup directory is placed that is mounted when the OS is loaded

Extra sfs files should be in dev/sda2 along with the pup subdirectories. All files from the CD should be in the subdirectory (dev/sda2/Lighthouse). Incidentally, it isn't necessary to burn a CD. Just click on the iso file to mount it and then open the subdirectory and copy the needed files. Only 3 files are needed in dev/sda/Lighthouse, initrd.gz, vmlinuz, and spup-490.sfs although there is usually no harm in copying all of them to the subdirectory since they are such small files.

As you can see there are numerous pup directories on my sda2 partition. mnt/home is partition sdb6 that has the blue dot on the attached desktop photo as I am posting from a test version of Lucid.

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

Re: Boot failure - Downloaded Mariner ISO and burned to CD

#123 Post by tazoc »

gcmartin wrote:I'm getting boot failures on each PC I attempt. What does the LAST message, in the list below, really mean? Messages are

Code: Select all

Loading drivers needed to access disk drives ...	done
Locating main file and session files...	done
 Loading spup-490.sfs (sr0)
 MinRAM to copy: 413M free RAM: 1772M... copying to ram..........	done
Setting up the layered filesystem...	done
Performing a 'switch_root' to the layered filesystem...Kernel panic - not syncing: Attempted to kill init!
The systems stopped at the last message above with a flashing cursor.
Hi gcmartin,
Kernel panic means the Linux kernel could not continue, usually because a file system or boot error occurred. Try booting from the LiveCD, entering puppy pfix=ram,nocopy to see if not copying the main file to RAM helps. If so include this on the kernel line in your GRUB entry. A kernel panic might also occur if the boot files from two separate Puppies or puplets were mixed. (See below for a description of 'boot files'.
gcmartin wrote:Can anyone provide an example of this instruction for Lighthouse installation.
On the Lighthouse website at this location ===> http://www.lhpup.org/tips-lhp.htm#Installation
One of the notes is
Note 2: All files except for the last (extra SFS files) can be placed in a directory one level deep so that multiple installs can be placed in the same partition.
Above the note, the paragraph is talking about folder /mnt/Home. I need help understanding what is meant by this note.
  1. Can anyone supply an example of the folder that this should reside in?
    AND
  2. Is the mention of "extra SFS files" referring to the line 'Optional: SFS files e.g., 5-LHP-Mar-4f_443.sfs'?
]Lastly, if I wanted to do a 2nd installation of a different version (from iso), what would I do differently?
Yes, extra SFS files are add-ons, such as the latest 5-Mariner-5C_490.sfs. These add-ons must reside in the base of the partition, as Jim1911's example in /mnt/sda2/, if that is the partition you're installing Lighthouse to. /mnt is where partitions are typically mounted at, so /mnt/sda2 or /mnt/home are still the base of sda2.

It is a bit confusing, as one might assume that only '/' is the base, but when a partition is mounted it's base becomes /mnt/<partition name>. The other confusing part is that the main file spup-490.sfs for Lighthouse or lupu-501.sfs for Lucid Puppy is also an SFS, however it is not an 'extra SFS' but rather the main file that is used to boot, and so spup-490.sfs must stay with the other boot files, initrd.gz, vmlinuz. Again these boot files must stay together and can either be in the base of the partition (if you only have one puplet on that partition), or in a folder one-level-deep (allows sharing the partition with other puplets). When you save your session to a pupsave that file which contains all of the updated and personal files you have saved during each session will also reside in the same folder as the boot files discussed here.

The boot (and main) files on the ISO can reside together in a folder one-level-deep and other puplets/Puppy installs are done the same way, that is their boot files would be together in another folder one level deep e.g., /mnt/home/lupu/lupu-501.sfs. Their add-on 'extra SFS' files, if any, must also be in the base of the partition, e.g., /mnt/home/openoffice-3.2.sfs.
Hope that helps,
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]

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

#124 Post by tazoc »

Jim1911 wrote:Your new Lighthouse Pup 5.00 C is really superb. The auto-setup is flawless with my system. All that was necessary for a complete setup was to install your nvidia 195 pet and setup my HP printer. CUPS detected it properly and the scanner works without any extra setup.

Minor oversight, Bibletime is missing... Also, BibleTime 2.7 was just released, so you may want to update it when you add the missing dependencies. Thanks for adding e-Sword to the WBAR setup.
Hi Jim,
You're very welcome and thank you for the positive feedback and comments. I had not had a chance to work on BibleTime until yesterday, (as with some other add-ons that are grayed out on the download page.) I tried to compile the latest BibleTime 2.7 but kept getting errors like this one,

Code: Select all

undefined reference to`ldap_sasl_bind@OPENLDAP_2.4_2'
even with all the dependencies installed. Might be a missing or mismatched header file or something. Some of the dependencies, ~35 packages in all, weren't available from Slackware so I went to Debian for some and Slack for others. Next time I'll try using everything from Debian, but it's much more time consuming that way as Debian and Ubuntu divide up many packages into numerous smaller ones.

So I updated Bibletime-2.5-1C.sfs, including the missing dependencies and most of Qt4.6.2 as well so that it works even with the Lighthouse 5.00C base ISO alone. Please try it from Bibletime-2.5-1C.sfs | md5.txt, deselecting any prior versions of BibleTime in Bootmanager before rebooting. If it works OK I'll put this new one on the web site.

Thanks,
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]

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

#125 Post by Jim1911 »

tazoc wrote:So I updated Bibletime-2.5-1C.sfs, including the missing dependencies and most of Qt4.6.2 as well so that it works even with the Lighthouse 5.00C base ISO alone. Please try it from Bibletime-2.5-1C.sfs | md5.txt, deselecting any prior versions of BibleTime in Bootmanager before rebooting. If it works OK I'll put this new one on the web site.
Since I'd already added the dependencies in my installation, I used a new save file with your update. It works fine, sorry that 2.7 is giving problems, however your 2.5.1 works as well as any that I've seen. Even ubuntu's version doesn't have all of the menu icons. Kubuntu does now have Bibletime 2.7 and it's running properly. I'll have to check ubuntu.

Thanks again and I do like the KDE desktop, IMO it outshines Kubuntu and is certainly faster.
Jim :D

Post Reply