(old)Puppy Linux Discussion Forum

Anyone use wine?

The link is to green-dome's latest. we have 1.3.25 in the repo, his version. Is it worth the update? [I rarely use wine.. er.. the software variety]

playdayz wrote:
The FF 7.0.1 in Tor is also configured for vidalia--in my experience it is a pain to configure vidalia and so I think the tor-browser bundle is a good thing for most users--if we can figure out the full screen business. I'll try the jwm 01micko just posted, maybe....

yes much prefer the bundle browser for ease of use. only advantage to having vidalia separate can tell is ability to configure some other browser.

we have 1.3.25 in the repo, his version. Is it worth the update? [I rarely use wine.. er.. the software variety]

Yes, I use it. My experience is that greendome's wine is of uniform high quality. i would just grab the latest and package it up. But 25 is reasonably new so I would say, low priority As soon as you post one, there will be another one, it seems like anyway.

I'll do it. Ha-ha.

I'll do it.

A request.. post pet.specs, saves me downloading

-------

Leafpad will replace nicoedit which is unmaintained.

Wine 1.3.28 pet specs - I guess I'll test it now IMHO greendome is making a big contribution. It is so luxurious to know that the latest wine is always there and waiting, in a high quality package.

playdayz, Thanks for that..

Best thing is to delete that pet.specs and repackage

New woof is very particular about the binary-compat and compat-version fields.. alot has changed.

-

I have also found your woof issue with older woof..
Line 46 in woof_gui_tabs needs to be commented else it clobbers gtkdialog Cheers

playdayz wrote:Wine 1.3.28 pet specs - I guess I'll test it now IMHO greendome is making a big contribution. It is so luxurious to know that the latest wine is always there and waiting, in a high quality package.

Code: Select all

wine-1.3.28-i486_v1|wine|1.3.28-i486_v1||Utility|109796K|pet_packages-4|wine-1.3.28-i486_v1.pet||Wine Windows Program Loader|puppy|4|official|
wine_DOC-1.3.28-i486_v1|wine_DOC|1.3.28-i486_v1||BuildingBlock|244K|pet_packages-4|wine_DOC-1.3.28-i486_v1.pet||Wine Windows Program Loader_DOC|puppy|4|official|
wine_DEV-1.3.28-i486_v1|wine_DEV|1.3.28-i486_v1||BuildingBlock|21908K|pet_packages-4|wine_DEV-1.3.28-i486_v1.pet||Wine Windows Program Loader_DEV|puppy|4|official|

I use greendome's latest daily, never had a problem. V 29 is out now, and when he makes it available, I'll upgrade. Greendome's contributions are really fine.

Best thing is to delete that pet.specs and repackage Wink

I can do that.

with |slackware|13.37|| ?

playdayz wrote:

Best thing is to delete that pet.specs and repackage Wink

I can do that.

with |slackware|13.37|| ?

yeah.. if you just delete the pet.specs it should be automatic when you run dir2pet.

01micko:

Welp... the puppy vga=normal pfix=ram bootup using B++ did manage to keep the icons on the desktop like they should be but... I still get the 1224x1224 resolution not the 1440x900 I selected from the probe and my screen is much to much in width.

BTW, I was using B5++ on my last post, just forgot to put the ++ in the thread Also, as far as the 2.26.39.4 kernel on my system, I have no problem with it installed in Squeeze-4.99.2 and believe it or not also in an older version of Lupu 501 and no problems!!!! So 2.26.39.4 works just fine on my old box with other puppy's.

Here's the log you requested:
>>>---Indian------>

Hi Mick,

01micko wrote:Anyone use wine? The link is to green-dome's latest. we have 1.3.25 in the repo...

Yesterday, I have just OK installed the 1.3.25 on B5. Not yet installed favorite applications (have yet to install some extra .dlls that might be required)

Is it worth the update?

Do not know ? Maybe both version could be proposed as a choice (as for Firefox on lupu528); and let the user make his test...?
Charlie

Charlie and Indian,

I noticed Xorg server version mis-matches.. I don't know if it's a big deal but I recompiled both siliconmotion and vesa, see attached.

Install and run xorgwizard

Posted wrong thread.

I have added gettext to tray apps: freememapplet_tray, network_tray and powerapplet_tray. It was new experience for me. I usually do this in bash. I have made pet-packages for Wary and Slacko. pot file is in /usr/share/doc/nls.
I couldn't find source for freememapplet_tray-2.6 so I just changed icons in freememapplet_tray-2.3.

hi all

just done a frugal install of 4.9.X.7 (B5++) on my quad core desktop (4gb ram, onboard nvidia graphics)

2.6.39.4 nvidia driver working great, tor works full screen after jwm pet was applied, firefox-aurora-7.0.1-spup.pet working great, so is pburn 3.4.1

will even handle 1085hd video (230mb download for a 5 minute video )

I thought 4.9.X.7 was fast on the laptop but this has taken the performance to another level

mick do you know yet which kernel we are going with as I am about to start trying to make some pets.

cheers

don

01micko:

Installed both-
(1) xf86-video-siliconmotion-1.7.5-i486.pet
(2) xf86-video-vesa-2.3.0-i486.pet

Sorry to say mic... nothing changed, still get the 1224x1224 resolution instead of the selected 1440x900!

Just don't know... and... it's still very confusing why Slacko is the only puppy that does this?

>>>---Indian------>

Hi Mick,
thanks for those pets !
UPDATED: please go to next Charlie6's post if what follows is not relevant.
---------------------------
Have installed both pets (siliconmotion and vesa) in the working slackosave whose xorg.conf code is described in an earlier post.

Also sorry here! Xorgwizard keeps hanging up whatever the choice on siliconmotion or vesa upon xorgwizard-driver-choice-step.
In each case, the display went black ; X hangs up. No return to the prompt even by doing Ctrl-Back-Space. But restart of system by doing Ctrl-Alt-Delete.

for information:
- I hopefully made a backup of it in /etc/X11, so I can fastly get a working slackosave again if something in X crashes.
- to recover my slackosave.3fs working, I open it from a working puppy (i.e. Lupq311) and then copy the working xorg.conf backup.
- monitor frequency ranges "C" is the working choice with all puppies till now on this Laptop.
- Running xorgwizard by selecting 'Menu/exit to prompt' and ther doing xorgwizard;
- In Puppy Video Wizard box:
Xvesa is not available (full grey displayed - it had never been available on whatever Slacko);
if doing Probe/select frequency ranges C /video resolution 1024x768x16 and test/test X now/ ---> got black screen hang up (*);
if doing Probe/select frequency ranges C /video resolution 1024x768x16 and OK/doing 'xwin' in command line/ ---> got a message telling ' dirname extraoperand ... usr/lib/.../siliconmotion_drv_so ' and afterwards got black screen hang up (*);
if doing Choose/siliconmotion/select frequency ranges C /video resolution 1024x768x16 and Test/Test_X_NOW/ ---> get black screen hang up (*);
(*)Restart of system by doing Ctrl-Alt-Delete
-------------------------------
Got also a try on 4.99x live-cd:
upon live-cd boot-up, loading of initrd.gz slows down and cannot complete (This happened sometimes; also some live-cd cannot even be read on this laptop: such as with 4.99.4, I could hear the cd-driver producing a noise like regular spaced Tick! ...Tick!...Tick!...; I believe it could be a problem related to the vmlinuz or initrd.gz files)
there came a warning message "enter any character to try loading again" --> cannot go farther, gave up with 4.99.x.

note that on Wary5.1.4 live-cd boot-up (whose Woof build is 29Augustus as for 4.99.4 if me good remember )
doing choice keyboard/locale fr_BE then OK/GMT+1 then OK ,then Local/choice on Xorg/Probe/select frequency ranges C /video resolution 1024x768x16 and test/ brings a working Wary (the video driver announced in the last XorgVideoWizard box is 'siliconmotion')

In attachment: some reports after installed those pets on B5
Note: the xorg.confChooseSilMo.gz has been picked-up opening the slackosave.3fs "from outside" using another puppy session.

Hope this could help. Sorry again if (too) detailed.
Charlie

For Testing

Google Chrome 14
ftp://distro.ibiblio.org/puppylinux/pet ... slacko.pet

Iron 14
ftp://distro.ibiblio.org/puppylinux/pet ... slacko.pet

Chromium 16
ftp://distro.ibiblio.org/puppylinux/pet ... slacko.pet

These should replace previous versions. If uninstalled they reinstate Seamonkey as the default browser.

Hi Mick,
Sorry again .. . ooops...I should have read competely the comment "Charlie" attached with the siliconmotion.pet.
So I was supposed to only install that one. Not both pets.
So straightaway uninstalled the vesa pet and doing the test again.
After doing xwin ...here success now: X restarts OK!
BUT: keyboard is 'us'; the xorg.conf file is as described on post see page 4 this thread.[ Adding Section Device containing Option XkbLayout 'be' will fix that ].
Also note that the current slackosave.3fs is the one created with Slacko-4.99.1.
In attachment the new info files.
Cheers, Charlie

Hi Charlie,

From your logs it tells me that you are using a xorg.conf when we were booting straight to desktop. This method indeed had a keyboard bug.

It also tells me that there is a bug in Xorg. How it works is that xorgwizard runs Xorg with the argument "--configure". This does not start X but simply creates the video and monitor sections of xorg.conf. When you run xorgwizard this happens and X wont start. When you boot with essentially an empty xorg.conf (this is how boot to desktop works) you get a desktop. Xorg is contradicting itself!!! Of course Xorg should choose the same options when booting to desktop as when "Xorg --configure" is run. I will have to devise a work around. Save me digging and post output of lspci -nn|grep -iE "vga". Thanks again.

-

Indian,

Thanks for trying. I have one more trick up my sleeve, I'll need your xorg.conf file. EDIT: I reckon the solution I am building for Charlie will fix your bug too Indian.. In early alphas we booted straight to desktop. Did that work for you?