Hi abushcrafter,
Thank you for the feedback, you must have seen the new poll question! For the benefit of those who haven't it asks, "What is your favorite desktop / window manager?" and is at the beginning of the first post. I used Xfce 4 for a while when I was working on the new SFS but I'm back in KDE4 so that was my vote... results are not scientific as I imagine one could vote more that once!
[Edit: oh my, it looks like the poll appears on every page. Hmm, I wasn't expecting that.]
TazOC_________________lhpup.orgLighthouse 64 6.02

The directories are empty because they are auto-magically filled as needed by simply running Wine Configuration, any of the links in /root/.wine/drive_c, Wine entries in the Menus, or by clicking on an .exe in ROX.

The reason, I installed the wine .pet is that when I clicked on setup951.exe nothing happened. I also tried one other exe which didn't work so I installed the Wine pet. It still wouldn't work, so I executed in a console and found that it needed the OLEAUT32.dll. So I located it and copied it over the existing file which was newer. The older file did work. I'll try it again, with a fresh install and something other than e-Sword, and let you know. Their may be a problem with latest Wine.
Thanks,
Jim

So I've been playing around in KDE a bit more since I tested Compiz, and I noticed that under settings it has the bit there for display. Now I can run my laptop with an external adapter but its a clone of my screen, there is the option there for extending a single desktop across two screens but I get the message that this module has not been included.
What exactly would need to be included in KDE to allow this ability? When I ran Fedora and Suse, I ran dual screens without a single problem through KDE. So Im assuming it has something to do with how KDE has been rigged to work with Puppy, do you know the details on this? If I could get Puppy to work across my screens... i'd be in heaven.

Hi Q5sys,
I think this is more of a Puppy question rather than KDE. The display setup is done by /usr/sbin/xorgwizard which doesn't know about KDE and probably doesn't need to. Although I haven't set up dual-monitor, Xinerama or Multi-view, I imagine it involves editing /etc/X11/xorg.conf, or depending on the driver you chose in xorgwizard, possibly exit to CL and type 'aticonfig --initial=dual-head --screen-layout=right' or 'aticonfig --help' for the ATI Catalyst 9.9 driver in Mariner, or 'nvidia-xconfig --help' for the nVidia driver in Mariner. I don't have any idea for an Intel adapter, probably xorg.conf would need to be edited or maybe 'xrandr' in a terminal can do it.

TazOC,
Thanks for the input, Ive read through those threads, but they've been of no help. As far as xorgwizard sees, I only have 1 monitor. KDE however sees both of them, and I can clone without trouble, just cant extend the desktop. In fact...
If I run the xorgwizard at startup then the system only sees one monitor @ 1280x800. If I plug in another monitor then I have to rerun the xorgwizard, at which point it then sees one monitor at 1024x768 (but will display on both screens as a clone).
However the xorg.conf files say the same thing except for the resolution difference, nothing more about screen or monitor 0 and 1

However If I start off with xorg thinking I only have the 1280x800, and plug in a second monitor and start KDE, KDE automatically starts outputting to that screen as a clone without having to touch the Xorg wizard. KDE detects the resolution of each monitor and everything, it only will clone the image though.

I have never been able to get xorgwizard to detect both screens. I've even tried manually editing the data in after seeing others sample .conf files, but xorg then wont run at all.

Thats why I was thinking that the solution might be found in KDE, since xorgwizard never seemed to want to work for me, but KDE partly did.
I'll drop a post in MU's thread though, so I can attack it from that angle as well.

EDIT:
I noticed that after upgrading from F to G, truecrypt no longer works. When trying to mount an ecrypted disk I get the following:
Even tried re-installing TrueCrypt.
It worked flawlessly in F, with what you've changed for the latest G version of Lighthouse, can you think of anything that might have caused this?Last edited by Q5sys on Sat 13 Mar 2010, 21:08; edited 1 time in total

I tried the new version of lighthouse puppy, my broadcom 4311 worked in the past version but doesnt work in this version.

My intel 915gm wasnt working in the past version as xorg setup just froze to a black screen and compiz/wine programs that required intel drivers didnt work; but it works in this version. The xorg setup worked anyways didnt try the wine yet.

Anyone know any fixes for the broadcom issue, the thing scans and detects the networks and stuff but it doesnt connect when I hit "use".

I noticed that after upgrading from F to G, truecrypt no longer works.

It worked flawlessly in F, with what you've changed for the latest G version of Lighthouse, can you think of anything that might have caused this?

I'm getting the same error here. Yes, I had updated '/bin/mount-FULL' to fix volume management in Dolphin and PCMan File Manager. Unfortunately truecrypt-6.3a.pet needs the Puppy version of mount-FULL. I'm attaching the one that works with TrueCrypt. As yet I don't have a solution that works for both TrueCrypt and Dolphin/PCManFM, but if you use TC in LHP 4.43Gu1 this will make it work again.
TazOC

I noticed that after upgrading from F to G, truecrypt no longer works.

It worked flawlessly in F, with what you've changed for the latest G version of Lighthouse, can you think of anything that might have caused this?

I'm getting the same error here. Yes, I had updated '/bin/mount-FULL' to fix volume management in Dolphin and PCMan File Manager. Unfortunately truecrypt-6.3a.pet needs the Puppy version of mount-FULL. I'm attaching the one that works with TrueCrypt. As yet I don't have a solution that works for both TrueCrypt and Dolphin/PCManFM, but if you use TC in LHP 4.43Gu1 this will make it work again.
TazOC

TazOC,
Thanks for the info and the gz. With my setup right now, TC is more important to me than Dolphin (as I use Thunar for file management)
Do you know off the top of your head if the older versions of TC also needed that version of mount-FULL?
Somewhere I have a backup copy of the 5.x, 6.1 and 6.2 pets of TC. Would it be worth it to you for me to check with those older versions of TC and see if one is natively compatible with 4.43Gu1? Or do you know the answer to that already?

One other thing, I was reading THIS thread about setting up a dialog to ask to save the session at shutdown instead of automatically doing it.
The person who wrote the post mentioned to look for: /usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
and then replace it with the coding he supplied. However when I open /etc/rc.d/rc.shutdown I see that code in there 3 times @ lines 776, 806, 812. I would have asked him but since its your puplet and you've been editing the save thing recently, you'd be a bit more in the know as to how you have it coded.

Lastly since I was talking about File managers, what conf file do I need to edit to change the default file manager? Rox is the default right now, but if I wanted to change it to Thunar or Dolphin, where is the file i'd need to edit to make that change. Or is it a much more indepth process? (I'm trying to learn as much as I can as I go)

And for all the work you've done so far and continue to do for the community with LHP and for answering my continous questions... thank you, thank you, thank you.

Do you know off the top of your head if the older versions of TC also needed that version of mount-FULL?
Somewhere I have a backup copy of the 5.x, 6.1 and 6.2 pets of TC. Would it be worth it to you for me to check with those older versions of TC and see if one is natively compatible with 4.43Gu1? Or do you know the answer to that already?

I don't know, but I think it's better to stick with the latest version of TC. Thanks for the offer, though. I'm trying to find another binary for TC 6.3x that might work. There is a 'Mount Options' panel in Settings | Preferences but I don't know if anything in there would help.

Quote:

One other thing, I was reading THIS thread about setting up a dialog to ask to save the session at shutdown instead of automatically doing it.
The person who wrote the post mentioned to look for: /usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
and then replace it with the coding he supplied. However when I open /etc/rc.d/rc.shutdown I see that code in there 3 times @ lines 776, 806, 812. I would have asked him but since its your puplet and you've been editing the save thing recently, you'd be a bit more in the know as to how you have it coded.

Type 'ver' in a terminal to see your current PUPMODE. So which occurrence(s) in rc.shutdown you change depends on which PUPMODEs you want to be prompted in. Looks like it's also necessary to change the save interval in Desktop Icons/Event Manager to 0 if you don't want a save to flash to occur prior to shutdown.

Quote:

Lastly since I was talking about File managers, what conf file do I need to edit to change the default file manager? Rox is the default right now, but if I wanted to change it to Thunar or Dolphin, where is the file i'd need to edit to make that change. Or is it a much more indepth process? (I'm trying to learn as much as I can as I go)

I imagine there are many places in Puppy/LHP that have ROX hard-coded. The first one I'd change in LHP is /applications/FileSystem.desktop. Then you'd probably want to make another icon in Wbar for your preferred FM with Wbar Setup. So yes I'm afraid it is rather complex to totally switch over to another FM. Maybe we could set up a 'defaultfilemanager' in /usr/local/bin to use in the future.

Quote:

And for all the work you've done so far and continue to do for the community with LHP and for answering my continous questions... thank you, thank you, thank you.

You're welcome, I appreciate your feedback; it makes LHP better and helps the community as well.
TazOC_________________lhpup.orgLighthouse 64 6.02

I tried the new version of lighthouse puppy, my broadcom 4311 worked in the past version but doesnt work in this version.

Anyone know any fixes for the broadcom issue, the thing scans and detects the networks and stuff but it doesnt connect when I hit "use".

I don't recall making any changes to networking or hardware detection that could explain why it worked before but not in 4.43 Gu1. The nearest workaround I could find is here: http://www.murga-linux.com/puppy/viewtopic.php?p=346454#346454 but it references Broadcom 4312. A custom puplet discussed by tempestuous in that post "isn't even compatible with all Broadcom wifi devices, only certain models." However the situation will hopefully improve in the future with newer kernels.
-TazOC_________________lhpup.orgLighthouse 64 6.02

Just a quick note here, should anyone else run into the same issue I just had (and an apology if this has already been covered):

I was having trouble printing an actual .pdf version of my browser. Every time I would attempt to print (without checking the Print to File box), a quick dialog box would briefly appear and, before I had a chance to read its contents, disappear. Nothing else happened -- no prompt to save the .pdf file or anything. The newly created .pdf file just didn't appear to even exist (even after performing a file search).

[NOTE: I am not connected to a printer. I was only trying to capture a web page as a .pdf file.]

Checking the Print to File box in the print dialog box did allow a Post Script file to be properly printed and saved to my specified location.

The problem of no actual .pdf file creation was solved by adding an empty (hidden) file in root called .Xauthority

Although I did nothing to change my own computer's name, apparently /root/.Xauthority is required when the computer name is changed from puppypc to anything else. This might be the result of something in Lighthouse? Perhaps in the Mariner sfs (/etc/hostname shows a computer name 'Mariner' instead of the traditional 'puppypc')?

I was having trouble printing an actual .pdf version of my browser. Every time I would attempt to print (without checking the Print to File box), a quick dialog box would briefly appear and, before I had a chance to read its contents, disappear. Nothing else happened -- no prompt to save the .pdf file or anything. The newly created .pdf file just didn't appear to even exist (even after performing a file search).

The problem of no actual .pdf file creation was solved by adding an empty (hidden) file in root called .Xauthority

Although I did nothing to change my own computer's name, apparently /root/.Xauthority is required when the computer name is changed from puppypc to anything else. This might be the result of something in Lighthouse? Perhaps in the Mariner sfs (/etc/hostname shows a computer name 'Mariner' instead of the traditional 'puppypc')?

Hi Roy,
I was not aware of this bug and I got the same result here--your fix works and I will include it in the next release. This likely affects the base ISO as well; /etc/hostname is 'Mariner'. Thank you for pointing this out and good job finding the solution!
TazOC_________________lhpup.orgLighthouse 64 6.02

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum