(old)Puppy Linux Discussion Forum

Hi All,

I fixed the permissions on those files. Sorry I missed it...I've been a tad distracted the last while.

@T..remember to set attribs to 644 or rw-r--r-- or let me know when you have a problem via pm.

When using wget with passwords that are now on puppylinux.asia do this

wget -c http://puppylinux.asia/members/T/apps_s ... 86_420.sfs --user=puppy --password=linux

Eric

PS...Beem and Henry you are not blacklisted...lol..just a permission problem

caneri wrote:PS...Beem and Henry you are not blacklisted...lol..just a permission problem

You owe us some canadian beer.
Some Unibroue f.e. La Fin Du Monde

Cripes Beem..I trust the ftp users to know how to upload...sheesh...AND do their own backups!!

That beer sounds interesting.

I'm a bit busy with the new things coming..we'll see how this all shakes loose.

Sorry I missed the perms.
Eric

Don't worry caneri, I was just poking a little bit.
But in fact, from a bartender in the Ardennes in Belgium, I got a package of Unibroue beers.
So I had a taste of it already.
Some were good.

sorry guys I'm on vacation at disney world - did a quick post will try to fix it as soon as I get back home

Edit: Looks like Eric beat me to it - thanks... I only had time to start the upload and walk away from the computer

Hey I just installed wine-1.1.17-i486.pet and it says I'm missing some dependencies.
For wldap32.dll.so: libldap_r-2.4.so.2 & liblder-2.4.so.2
For wineesd.drv.so: libesd.so.0

Is this going to be a problem running 3D games?

not unless you use an exe that requires them ... they are "soft" dependencies, but they are small and available from the same location as wine... see links earlier in thread

I'm trying to play a certain game called Ragnarok Online and I'm having some trouble enabling the use of my ATI Radeon x700. There's a separate program that is the configuration of the game. There's a dropdown menu that lets you choose the type of graphics you'd like to use and I don't see my ATI Radeon x700 in there. There's only D3D. I have recently installed MU's ATI Catalyst 8.12 with Xorg. So OpenGL is enabled. Do I have to enable opengl in Wine or something? I'm using Wine 1.1.17 on Puppy 4.1.2.

inside of a wine game, you must use "opengl" if that is available.
If not, you can try the Direct3d driver.
Wine is mapping those drivers to Puppys native opengl drivers (in your case those from Ati).

But Ati just has limited support in Wine.
If a game uses Direct3D pixel or vertex shaders (like Bioshock), you will see black areas, or a completely black screen.
This is one reason, why I installed XP again.
To play games in Wine, Nvidia cards are the first choice.
Some run fine though in Wine with Ati, Those that support OpenGL in Windows, like "Chronicles of Riddick".

For Ragnarok, you might find hints at:

http://www.winehq.org/search?cx=partner ... q=ragnarok

http://appdb.winehq.org/objectManager.p ... on&iId=701

http://appdb.winehq.org/objectManager.p ... &iId=12042

Mark

But the problem is that I don't have the option of using the ATI Radeon x700 in the settings. Otherwise, I would choose it. How come it's not there when I've installed ATI Catalyst with Xorg? Unless, it's just another ATI bug blehh

no, you cannot use a ati driver from inside of your game.
If you can select a manufacturers driver in your Windows program, it will not work.
Because it would be a Windows-driver!

Wine supports only these 2 generic Windows drivers: Direct3D and OpenGL.
When you select one of these two in a Windows program, then internally the Linux driver will be used, with full accelleration, if it provides it.
As you have the Linux Ati driver installed, this one will be used by Wine and so also by your game.

And as I said: usually the OpenGL Windows driver works better, but not every game has OpenGL support. So if you have bad luck, only the less good Direct3D driver is available (for example in games, that have no option to select a driver).

I hope, I coulld explain it better now.
Mark

1.1.19 is out.

Umm.. I uploaded 1.1.19 to puppylinux.asia/members/T/

went to change permissions but the connection timed out at about the same time and now I am getting
500 OOPS: cannot change directory:/mnt/w1011/d39/s12/b02d8349/www/puppylinux.asia/members/T/

I get a similar message when I try to go to puppylinux.asia/members/T/
Cannot read /mnt/w1011/d39/s12/b02d8349/www/puppylinux.asia/members/T/.htaccess

will PM eric to try to get it fixed

Hey..I just happened to be on the forum...it's fixed.

LOL..I did that to myself before....and wondered how in the world I did it. I had the wrong area highlighted when I changed perms I guess.

Anyway it's good now...directories are 755 and files are 644.

Eric

Thanks Eric and thanks (I haven't even told anyone about the LITE webdesktop yet - shhhh it's a secret)

anyhow updated to 1.1.19
Winelite.pet (all dependencies from previous posts)
http://puppylinux.asia/members/T/486_pe ... 9-i486.pet

Winefull.sfs
http://puppylinux.asia/members/T/apps_s ... 86_420.sfs

Dear techosaurus,

I tried the 1.1.19 pet last night and it installed fine under 3.01. However, I noticed that there was no ALSA support. I didn't check all the previous posts, but this may be by design. In any case, I need ALSA, so I later went to winehq.org and downloaded the slackware version - 1.1.19, converted it to a pet and now have ALSA again.

With kind regards,
vovchik

@vovchik - that's really not good... I compiled this one with 4.2 and the 4.2 devx ... will recompile on 4.1.2 until I can figure out where the new ALSA DEV package is so I can rebuild the new devx... I was worried about this during development, but since the 1.1.18 version works in 4.2 then I will go back to compiling on gpup and the 4.1.2 devx (smp makes for much quicker compiles)

Well 4.20 seems to be a mix of alsa 1.1.16 and 1.1.19 which might not help

mike

The ALSA libs were updated to 1.1.19,but everything else is old:

* alsa-driver
* alsa-utils
* alsa-tools
* alsa-firmware
* alsa-plugins
* alsa-oss

OK back to using gpup 4.1.2 ... compiling now - here are the instructions in case anyone is interested

setup gpup with devx_412.sfs

install these pets (available via petget or @ puppylinux.asia/members/T/ - puppy:linux for user:password)
cups-1.1.23
esound-0.2.41-i486
esound_DEV-0.2.41-i486
jack-audio-connection-kit-0.116.1-i486
jack-audio-connection-kit_DEV-0.116.1-i486
libexif-0.6.16
libexif-gtk-0.3.5
libgphoto2-2.4.2
libgphoto2_DEV-2.4.2
openldap-2.4.13-i486
openldap_DEV-2.4.13-i486
sane-backends-1.0.19
xorg_xorg_full_dri-7.3
xorg_xorg_full_dri_DEV-7.3

download the wine-x.x.xx.tar.bz2 and extract it somewhere

open the wine-x.x.xx folder

hit the "`" button (usually under the ESC key) to open a terminal window there

type or copy the following code and paste it into the rxvt terminal (center mouse click or right and left at the same time) after the configure has run just type: after that's done type it will take a while to compile even with the -j3 option (only use on dual cpu... -j5 for quad)... when that is finished you need to make pets... I do this 2 different ways for lite and full

for winelite we would type (I usually end up making this as a pet) for winefull we would type (I usually end up making this as a sfs) I always choose to split it into a main package and DEV, DOC and NLS...(option 3) they can be recombined later

it will ask for dependencies - there are so many and since some packages aren't in the repo I don't bother with this part

after that is done its time to build our pet

for wine-lite, rename the wine-x.x.xx-486 folder to winelite-x.x.xx-486 and copy my pre-prepared fileset of goodies to the folder - (I will post a tarball of it) ... then from a terminal in its parent directory type: NOTE if you insert my fileset there is no need to create a menu entry

then I install winelite which will automatically run winecfg and create the /root/.wine directory which I will later copy into the sfs folder

for the winefull-x.x.xx-486.sfs I use "new2dir make install" vs "new2dir make install-lib" This "installs" additional wine development tools that aren't necessary to run programs but are good for compiling win32 exes
... this is why I also put the wine_DEV-x.x.xx folder and contents into the wine-x.x.xx-486
... I also copy the same "winegoodies" as in the winelite version
... then to save users from having to download dependencies, I convert the dependencies first to tgz and then extract them so I can include those contents as follows click on the tar.gz to open it, extract the contents and copy them to the wine-x.x.xx-486 folder (I have all of them pre-copied to 1 folder already to make it faster)
last but not least I copy the /root/.wine folder that was created when I installed winelite to wine-x.x.xx-486/root/.wine (ensure that you set up sound, press apply and test it during the wine-lite install)
... Now all that is left is building the winefull-x.x.xx-486_412.sfs