(old)Puppy Linux Discussion Forum

Posted: **Wed 25 Jul 2012, 21:49**

Hello there Lighthouse programmers

I was asking this question in the forum and someone kindly suggested I post here to see if someone can help.

I've just installed Lighthouse 64 and its really impressive. Everything works out of the box! ( I have an AMD 4400 ).

I wanted to use it for music and downloaded the audiosfs for lighthouse 64. It's great but I can't use any of my windows apps with it due to wineasio not being present.

Is there anyway someone might be able to take a look to see if it can be compiled for your next audio sfs release please? I am sure many people would find it useful.

Thanks for your time

Posted: **Wed 25 Jul 2012, 22:35**

Most slackware64-13.37 builds work just fine in Lighthouse64

If I don't find it via the puppy package manager I head over to
http://slackbuilds.org/repository/13.37/

There is a search field in the top right

I found this
http://slackbuilds.org/repository/13.37/audio/wineasio/
"WineASIO provides an ASIO to JACK driver for WINE. ASIO is the most common
Windows low-latency driver, so is commonly used in audio workstation
programs."

Always look for the link to "Download slackbuild"

Alwasy read the readme file. It sounds like it may build on LH64 because its multi lib

"This can't be built on a stock Slackware64 system, since it requires
32-bit Wine. It may (or may not) be possible to build on a 64-bit multilib
system; let me know how it goes."

good luck

Posted: **Wed 25 Jul 2012, 22:36**

Double post

Posted: **Thu 26 Jul 2012, 02:42**

L64 is not what Slackware64 calls multilib, but mostly pure 64-bit. With multilib you can compile in either architecture, without chrooting. However where S64 uses a 64-bit Wine, L64 uses only 32-bit Wine. Confusing huh?

Anyway, I don't know if that Slackbuild will work, sometimes they need tweaking and require the DevX SFS be installed. Have you tried the audio-all-in-one-amd64-10.sfs from Fatdog64-521? It's loaded with Jack Rack, Rosegarden, sound editors, studios, drum machines, etc.

http://distro.ibiblio.org/pub/linux/dis ... e-sfs.html
http://distro.ibiblio.org/pub/linux/dis ... g/sfs/500/

TaZoC

Posted: **Thu 26 Jul 2012, 02:59**

meeki,
If you restart GKrellM, try disabling the KrellKam windows, either right-click on the cam -> options -> change Number of Panels to 0...
or just roll your mouse wheel over the webcam !

See if that helps or not.

Also you can disable GKrellM autostart in a file manager by moving /root/Startup/GKrellM into /Startup/DisabledItems.

Posted: **Thu 26 Jul 2012, 08:51**

you are right about slackware vs LH64 = wierd diff.

I have 3 slakware paks running with out a issue

The skype ver 4 I linked works perfect

Also running 2 lib packs for depends

I had 2 not work as all.

And the last one I tryed was apache server for slackware and i will perma crash your pup save after boot.

So its hit or miss. I'm happy to take it

Thanks for letting me know where GKrellM is located and started saved me the time of tracking it all down. I just had so much going on at the time i did it the cheezy way

your script is nice... checks if its running "pidof " then "gerp" chacks the GKrellm.pid ???

only issue is it does not check where its drawn on X.

For some reason It trys to load all 3 windows and crashes. because more than one instance of it is running.

2 ways I'll try to fix this tomorrow as i need ot goto bed.

Put DISPLAY=:0.0 in your bash

or the EZ way put a countdown on my script to wait about 5 seconds till it draws DISPLAY=:0.1 and DISPLAY=:0.2

I'll try to fix it in your scrip so you can update it in the next release so other nuts with mufti monitors don't crash.

I bet you did not think people would have multiple monitors on Lighthouse.

Posted: **Thu 26 Jul 2012, 14:01**

@Meeki,
Questions

Might you have made a PET of your work?
And, might you be aware of this, reported from a Fatdog601 user?

smokey01 wrote:
gcmartin wrote:
smokey01 wrote:Thanks but no.
Is there something wrong with that PET that was offered you?
Just curious of the problem you encountered.
Thanks in advance
It wasn't a pet and it didn't run. Something is wrong, not sure yet.

It keeps complaining it can't fine the file or directory. ...

Here to help

Posted: **Thu 26 Jul 2012, 18:14**

I have attempted to make a pet of Skype 4.0.0.8 It works but has a bug where you cant close the chat window if you open it up.

While goofing around I found and tried the Slackware package 4.0.0.7 tried it and it worked fine.

MAKE SURE you have your devx for your package installed. befor you go trying o use a Slackware package.

Posted: **Thu 26 Jul 2012, 18:20**

Earth to Meeki come in over

I've been asking on the forums about something and they have sent me here hoping you can help me. Fingers crossed!

I installed Lighthouse 64 the other day - it's really good! It works a treat on my AMD 4400.

I wanted to make some music with it but I can't see where I can find a Wineasio.dll that will work on this distro. I tried Ubuntu / .deb compiled for 64 bit but that didn't work.

Can anyone help please? I am desperate !

Thank you for any help you can offer.

Posted: **Thu 26 Jul 2012, 19:37**

Hang in there I'm building a sfs ATM for tazoc so we can have an Apache Web Server, MySQL, PHP. This should work in Lighthouse64 and FATDOG64. It takes my work box about 1 hr to ./config the Perl for it. I'm on round 3 of this.

After that I'll look into getting your winealso working.

Then after that It looks like everyone wants a true skype4 pet for the 64bit puppys
The issue with skype is that the have no static 64bit version. So it runs off of 32libs getting them into the install folder and called right is a pain. As stated before I have one that works but has bugs. I may share or host a pet from another source but when I make a pet by hand like I did with dropbox I make sure there are no bugs with current Lighthouse release.
So until I get the Message Window fixed in the pet fixed I will not release it.

I'm working on all the above. Give me some time ill sort it out.

Posted: **Thu 26 Jul 2012, 19:58**

Thanks loads Meeki! I really appreciate it.

Posted: **Thu 26 Jul 2012, 20:15**

meeki wrote:Put DISPLAY=:0.0 in your bash

or the EZ way put a countdown on my script to wait about 5 seconds till it draws DISPLAY=:0.1 and DISPLAY=:0.2

I'll try to fix it in your scrip so you can update it in the next release so other nuts with mufti monitors don't crash.

I bet you did not think people would have multiple monitors on Lighthouse.

Actually, I'm running 2 monitors and I think Q5sys has 3 or 4, but we're both running proprietary video drivers and haven't seen problems. Just restart X with all monitors on and I get one huge desktop with just one GKrellM. (Its options has a setting whether or not to allow multiple instances, default is no.) I also use Zarfy Monitor Control in the System Menu sometimes.

But yeah whatever changes /usr/local/bin/GKrellm needs I'll put them in, thanks! For now I'm putting

Code: Select all

DISPLAY=:0.0 #1207226 suggested by meeki

near the top.

TaZoC

Posted: **Thu 26 Jul 2012, 21:01**

I'm running The Nivida drivers pet.

I'm not running Xinerama or twin view. Or one big desktop. I'm running seperate X-Screens for each. So I have 3 instances of X and 3 instances of Openbox going at one time.

No crashes for over 2 hrs now with the startup scrip modded. The below mod puts it in the stock window. I'm running it on my far Right monitor with DISPLAY=:0.1

Code: Select all

#!/bin/sh
# 2010-01 TazOC-www.lhpup.org
DISPLAY=:0.0
PIDFILE="/var/run/GKrellm.pid"

if pidof GKrellM | grep " "; then # >1 instance of this script
 [ -s /var/run/GKrellm.pid ] && kill `cat $PIDFILE`
 sleep 1
fi
echo "`pidof GKrellM`" > ${PIDFILE}

if [ -x /usr/bin/gkrellm ];then
 sleep 3
 pidof gkrellm 1>/dev/null && killall gkrellm
 sleep .1
 gkrellm &
fi
rm -f ${PIDFILE}

exit # END SCRIPT

Posted: **Thu 26 Jul 2012, 23:55**

tazoc wrote:Actually, I'm running 2 monitors and I think Q5sys has 3 or 4, but we're both running proprietary video drivers and haven't seen problems. Just restart X with all monitors on and I get one huge desktop with just one GKrellM. (Its options has a setting whether or not to allow multiple instances, default is no.) I also use Zarfy Monitor Control in the System Menu sometimes.

But yeah whatever changes /usr/local/bin/GKrellm needs I'll put them in, thanks! For now I'm putting
Code: Select all
DISPLAY=:0.0 #1207226 suggested by meeki
near the top.

TaZoC

Correct. I'm running 4x screens with no problem whatsoever. Once I got the driver loaded I just used the bundled nvidia configure program to set everything up the way I wanted and let it write the xorg.conf script.

Code: Select all

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 280.13  (buildmeister@swio-display-x86-rhel47-03.nvidia.com)  Wed Jul 27 17:15:45 PDT 2011


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 1080
    Screen      1  "Screen1" 0 0
    Screen      2  "Screen2" 1920 0
    Screen      3  "Screen3" 1920 1080
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "1"
EndSection

Section "Files"
    FontPath        "/usr/share/fonts/default/Type1"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor3"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:6:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:6:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-0: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-3: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-0: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-3: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Posted: **Fri 27 Jul 2012, 04:28**

Q5sys, your running Xinerama. Its a fine way to do a desktop. I have no issues with it.

Xinerama allows "X applications and window managers to use two or more physical displays"; so its handling the applications

I'm just bucking the system

Best way I can describe what im doing, though I'm sure im wrong on the details:
I'm running 3 separate desktops they function independent of each other. you cant drag an open window to the other screen. Other funny things happen too! if you were to try and open a second instance of firefox on the other monitor it will freek out and say sorry its already runnin. There is a way around this with multiple profiles firefox -p "profile name" I then use sync to tie them all together.

Posted: **Sun 29 Jul 2012, 14:18**

Well I now know why WineASIO is not standard package anywhere.

"Get the ASIO SDK from Steinberg
Due to the licensing restrictions of the SDK it's impossible to distribute the asio.h header file with WineASIO so you have to get it yourself. "
quote source http://wiki.cockos.com/wiki/index.php/I ... g_WineASIO

Also here is the ASIO Licensing agreement.pdf
http://dl.dropbox.com/u/12968946/lighth ... eement.pdf

Sad to say mate your on your own.

Before you go trying to build it you should know that it needs the wine-dev for a file on make called wine/debug.h
Because lighthouse and puppys are small package builders tend to clean up at the end killing such files that do not effect run.

So unless I can get the build sfs I can not do much about the ASIO issue.

Posted: **Wed 01 Aug 2012, 01:06**

meeki wrote:Q5sys, your running Xinerama. Its a fine way to do a desktop. I have no issues with it.

Xinerama allows "X applications and window managers to use two or more physical displays"; so its handling the applications

I'm just bucking the system

Best way I can describe what im doing, though I'm sure im wrong on the details:
I'm running 3 separate desktops they function independent of each other. you cant drag an open window to the other screen. Other funny things happen too! if you were to try and open a second instance of firefox on the other monitor it will freek out and say sorry its already runnin. There is a way around this with multiple profiles firefox -p "profile name" I then use sync to tie them all together.

Its always good to have people buck the system and do things different!

Posted: **Wed 01 Aug 2012, 01:54**

Truecrypt 7.1a (64bit)

someone want to test this on their lhp64 system?

Posted: **Wed 01 Aug 2012, 09:06**

Testing now

Posted: **Wed 01 Aug 2012, 09:21**

meeki wrote:Testing now

dont forget to set it to not to use Kernel crypto services.

(old)Puppy Linux Discussion Forum

Lighthouse 64 5.14.2 Beta 4

Wineasio request

WineASIO

KrellKam

Wineasio request

Multiple monitors and GKrellM

Re: Multiple monitors and GKrellM