Re: [Cooker] wine in mdk92

2003-10-01 Thread Diego Iastrubni
ביום רביעי, 1 באוקטובר 2003, 23:48, נכתב על ידי Diego Iastrubni:
> Hi,
>
> I need to beta test  a Windows App, and I tested it under wine.
> I have found that wine basicly works (and sets up the configuration quite
> well on it's own). Howvere the "c:\" is under /var/lib/wine which is not
> writable by my user.
>
> A quick fix is setting this dir g+rw to my group.
> Any one has a better idea here? That will work out of the box?
>
> Fonts are a problem (since I need to set my own fonts, and the dir is not
> listed in the afm dirs).
>
> Hopefully I will work this out.
more problems:
some programs (dcom98 for example) must be run using wine.bin other wise I get 
"command operation syntax error. type command /? for help".

every few times I run a windows program, I get this message:
"error:9: wine client error:9: wine client error:9: wine client error:9" ...
scrolling on the console.

google tells me this:
http://www.winehq.com/hypermail/wine-devel/2003/06/0639.html

I also forgot this last mail:

[EMAIL PROTECTED] .wine]$ rpm -qv libwine1
libwine1-20030813-1mdk
[EMAIL PROTECTED] .wine]$ rpm -qv wine
wine-20030813-1mdk

--

diego, 6 Tishrey 5764

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html





Re: [Cooker] wine problems

2003-07-02 Thread Per Øyvind Karlsen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 02 July 2003 15:34, Mark Draheim wrote:
> On Wed, 2 Jul 2003 13:09:41 +0200
>
> Per Øyvind Karlsen <[EMAIL PROTECTED]> wrote:
> > should be fixed in wine-20030618-4mdk, related to stupid use of
> > $RPM_BUILD_ROOT in makefiles..
>
> that stupid use is there because we patched it in there and we had all
> reason to do so. However,
>
> > such variables should never been used in makefiles IMHO..
>
> yea right, that's why I proposed this to cooker on, let's see, April 30
>
> -
> due to popular demand for a fix of manpages and apploader script:
>
> s/RPM_BUILD_ROOT/DESTDIR/destdir.patch
>
> fixes buildroot being present in manpage files section and apploader
> scripts (ie notepad etc). Should make build more sane in general. No
> adverse side effects here.
>
> Explanation: while RPM_BUILD_ROOT is set from start, DESTDIR is set at
> makeinstall_std, ie after make. At make stage it is empty and doesn't
> get in the way when building.
>
> new patch attached
> -
>
> both the explanation and the new patch were sent again on May 7
>
> So I'll try again to propose this one. The attached patch REPLACES
> patch1. There's no diff to patch1 because the diff is trivial: If you
> like you can unpack patch1 and then
>
> sed -e "s/RPM_BUILD_ROOT/DESTDIR/" wine-20021219-destdir.patch >
> wine-20030702-destdir.patch
>
> and update the spec
>
> Mark
ah, sorry:\
I remember something about this, but it somehow got lost.. also you probably 
should submit such stuff to bugzilla too so it won't be forgotten

I'll take a look at it

btw. could you confirm that #714 is solved?
- -- 
Regards,
Per Øyvind Karlsen
Sintrax Solutions
http://www.sintrax.net - +47 41681061
- 
GPG Key: http://sintrax.net/~hawkeye/key.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/AuHmv8F7V9JOSuURAloGAJ44NIe9vWOYy9UQJcKEwuDb8kCHTACfWw8R
6OaAAiQZAGsRBwUHPdmaPK4=
=URtd
-END PGP SIGNATURE-




Re: [Cooker] wine problems

2003-07-02 Thread Mark Draheim
On Wed, 2 Jul 2003 13:09:41 +0200
Per Øyvind Karlsen <[EMAIL PROTECTED]> wrote:


> should be fixed in wine-20030618-4mdk, related to stupid use of 
> $RPM_BUILD_ROOT in makefiles..

that stupid use is there because we patched it in there and we had all
reason to do so. However,

> such variables should never been used in makefiles IMHO..

yea right, that's why I proposed this to cooker on, let's see, April 30

-
due to popular demand for a fix of manpages and apploader script:

s/RPM_BUILD_ROOT/DESTDIR/destdir.patch

fixes buildroot being present in manpage files section and apploader
scripts (ie notepad etc). Should make build more sane in general. No
adverse side effects here.

Explanation: while RPM_BUILD_ROOT is set from start, DESTDIR is set at
makeinstall_std, ie after make. At make stage it is empty and doesn't
get in the way when building.

new patch attached
-

both the explanation and the new patch were sent again on May 7

So I'll try again to propose this one. The attached patch REPLACES
patch1. There's no diff to patch1 because the diff is trivial: If you
like you can unpack patch1 and then

sed -e "s/RPM_BUILD_ROOT/DESTDIR/" wine-20021219-destdir.patch >
wine-20030702-destdir.patch

and update the spec

Mark



wine-20030430-destdir.patch.bz2
Description: Binary data


Re: [Cooker] wine problems

2003-07-02 Thread Per Øyvind Karlsen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 02 July 2003 01:45, Vincent Meyer, MD wrote:
> Interesting error message with the latest wine update:
>
> [EMAIL PROTECTED] meyerv]$ wine wed.exe
> /usr/bin/wine.bin: trying to run 'F:\wed.exe', cannot open builtin library
> for 'winevdm.exe':
> /home/peroyvind/rpm/tmp/wine-root/usr/lib/wine/winevdm.exe.so: cannot open
> shared object file: No such file or directory
>
> V,
should be fixed in wine-20030618-4mdk, related to stupid use of 
$RPM_BUILD_ROOT in makefiles..
such variables should never been used in makefiles IMHO..
- -- 
Regards,
Per Øyvind Karlsen
Sintrax Solutions
http://www.sintrax.net - +47 41681061
- 
GPG Key: http://sintrax.net/~hawkeye/key.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/Ar13v8F7V9JOSuURAoQ1AKCOTgCA9Ik9Qz6cTU+Dusk5fmvcbgCaA//f
LRD9b7wxgwEo7KhpA3b8OxE=
=l1rw
-END PGP SIGNATURE-




Re: [Cooker] wine update for 9.1--slightly ot

2003-01-20 Thread J. Greenlees
rcc wrote:

On Mon, 20 Jan 2003 18:30:17 +
HA Quoc-Viet <[EMAIL PROTECTED]> wrote:



sorry for this.
the wine-mdkconf is still in the SRPMS
I haven't really busted anything have I ? :o)



don't know, I rarely install the cooker wine. It's just that Danny and I
made some changes to the default config like enabling arts by default,
putting mdk specific font dirs in, changed tmp dir, etc.

You couldn't know about my new reg files as I only sent them to Danny
for testing. They're still called wine.userreg and wine.systemreg but I
decided to install them as system.reg and user.reg because I think
there's no reason for deviating from wine's default naming scheme.

I attach both reg files. They replace the cooker ones. Also, there's my
autofs patch which I haven't yet submitted to winehq, they're probably
not interested anyway. The patch shouldn't clash with other ways of
mounting, it just tells wine to keep drives that are in config and have
an automount line even if wine cannot stat their dirs, which is the case
for autofs. Lastly, there's my mdkconf patch.

When I can't make you merge rpms into fewer rpms for wine, I'd like to
suggest splitting out the fake wine in /var/lib (wine-fakewin*.rpm ?)as
I have that dir symlinked elsewhere and don't want it "updated" each
time I install a new wine. I know that this proposal flatly contradicts
my previous statements about libification...

- Mark




has your changes to wine made it so it can run windows based 3d 
modelling apps? like discreets 3d studio max, mcneel's rhino?
only use I have for windows is these apps, which I can't get wine to run.




Re: [Cooker] wine update for 9.1

2003-01-20 Thread rcc
On Mon, 20 Jan 2003 18:30:17 +
HA Quoc-Viet <[EMAIL PROTECTED]> wrote:

> sorry for this.
> the wine-mdkconf is still in the SRPMS
> I haven't really busted anything have I ? :o)

don't know, I rarely install the cooker wine. It's just that Danny and I
made some changes to the default config like enabling arts by default,
putting mdk specific font dirs in, changed tmp dir, etc.

You couldn't know about my new reg files as I only sent them to Danny
for testing. They're still called wine.userreg and wine.systemreg but I
decided to install them as system.reg and user.reg because I think
there's no reason for deviating from wine's default naming scheme.

I attach both reg files. They replace the cooker ones. Also, there's my
autofs patch which I haven't yet submitted to winehq, they're probably
not interested anyway. The patch shouldn't clash with other ways of
mounting, it just tells wine to keep drives that are in config and have
an automount line even if wine cannot stat their dirs, which is the case
for autofs. Lastly, there's my mdkconf patch.

When I can't make you merge rpms into fewer rpms for wine, I'd like to
suggest splitting out the fake wine in /var/lib (wine-fakewin*.rpm ?)as
I have that dir symlinked elsewhere and don't want it "updated" each
time I install a new wine. I know that this proposal flatly contradicts
my previous statements about libification...

- Mark




winefiles.tar.gz
Description: GNU Zip compressed data


Re: [Cooker] wine update for 9.1

2003-01-20 Thread Danny Tholen
On Monday 20 January 2003 19:30, you wrote:
> sorry for this.
> the wine-mdkconf is still in the SRPMS
> I haven't really busted anything have I ? :o)
course not:) 
I will try to integrate the few small changes Mark and I made with this 
version and send it to you tomorrow.

Actually it might be very good that you became the new maintainer. I got the 
impression that Thierry has 2 much to do already :)


Danny

>
>
> Viet
>
> On Monday 20 January 2003 4:19 pm, Thierry Vignaud wrote:
> > <[EMAIL PROTECTED]> writes:
> > > > Need sleep and there's a new wine package in
> > > > cooker which brutally dumped our thoroughly crafted mdkconf.
> > >
> > > aha.Didn't see that yet. My cooker install is hopelessly behind. Want
> > > to do a fresh install anyway but lack the time.
> > >
> > > Thierry: any reasons for not applying some of the patches?
> >
> > there's no reason to not apply these patches.  but viet has taken wine
> > maintenance over me since he has access to zindoz.
> >
> > send him your patches with explanations as usual.
> >
> > > Also: since Mark did some new stuff (regdefaults) that are working
> > > nice, and I fixed a few bugs in the config script, it is a bit
> > > awkward and more work to sync our stuff with this new release. A
> > > mail would have been nice.
> >
> > my coworker wasn't aware of your work :-(




Re: [Cooker] wine update for 9.1

2003-01-20 Thread HA Quoc-Viet
sorry for this.
the wine-mdkconf is still in the SRPMS
I haven't really busted anything have I ? :o)


Viet



On Monday 20 January 2003 4:19 pm, Thierry Vignaud wrote:
> <[EMAIL PROTECTED]> writes:
> > > Need sleep and there's a new wine package in
> > > cooker which brutally dumped our thoroughly crafted mdkconf.
> >
> > aha.Didn't see that yet. My cooker install is hopelessly behind. Want to
> > do a fresh install anyway but lack the time.
> >
> > Thierry: any reasons for not applying some of the patches?
>
> there's no reason to not apply these patches.  but viet has taken wine
> maintenance over me since he has access to zindoz.
>
> send him your patches with explanations as usual.
>
> > Also: since Mark did some new stuff (regdefaults) that are working
> > nice, and I fixed a few bugs in the config script, it is a bit
> > awkward and more work to sync our stuff with this new release. A
> > mail would have been nice.
>
> my coworker wasn't aware of your work :-(





Re: [Cooker] wine update for 9.1

2003-01-20 Thread Thierry Vignaud
<[EMAIL PROTECTED]> writes:

> > Need sleep and there's a new wine package in
> > cooker which brutally dumped our thoroughly crafted mdkconf.
> > 
> aha.Didn't see that yet. My cooker install is hopelessly behind. Want to 
> do a fresh install anyway but lack the time.
> 
> Thierry: any reasons for not applying some of the patches?

there's no reason to not apply these patches.  but viet has taken wine
maintenance over me since he has access to zindoz.

send him your patches with explanations as usual.

> Also: since Mark did some new stuff (regdefaults) that are working
> nice, and I fixed a few bugs in the config script, it is a bit
> awkward and more work to sync our stuff with this new release. A
> mail would have been nice.

my coworker wasn't aware of your work :-(





Re: [Cooker] wine update for 9.1

2003-01-20 Thread Thierry Vignaud
rcc <[EMAIL PROTECTED]> writes:

> I guess I don't get the logic behind mdk policy. Split libs from
> actual programs and then but progs in lib packages because they
> happen to be devel tools. Ah, it dawns on me, Thierry would probably
> suggest splitting out the stuff into yet another package.

exact :-) !





Re: [Cooker] wine update for 9.1

2003-01-17 Thread rcc
On Fri, 17 Jan 2003 14:21:52 +0100 (CET)
<[EMAIL PROTECTED]> wrote:

> > no, it's more of a frontend than a configuration program. Let it
> > have its own menu entry and when the user starts it and then a
> > winexe through it, wine-config will run. Ah, I see, the user might
> > be tempted to configure wine before running an exe. Hmm, have to
> > think about this.
> ok, but using it as a frontend sounds ok to me. Configure wine can be
> a menu entry added by the xwine package?

have a look at it, it's really small and doesn't have many dependencies
besides GTK. It offers configuration via neat combo boxes and I just
noticed it even has a menu entry for launching winesetuptk (if you can
push that into contrib). So you can have everything via xwine.

http://darken.tuxfamily.org/pages/xwine_en.html 

i18n support is fairly rudimentary, the pot file created by xgettext is
a mess of English and French. But maybe that will change if the app gets
some publicity when it makes it into contrib or even the distro.


> Solution: 1) write config to globaldir!=windir. If this is possible.

that's why I said I don't really know wine registry handling. Getting
rid of the separate reg files is on the wine TODO list but who knows
when it will be implemented. If globaldir reg means /etc/wine we's have
to make it 664 for group wine. Don't know if that's a good idea.

> 2) change wine script to copy a fakeglobalreg from 
> /var/lib/wine/globalreg to userhome dir at start. And copy the, 
> potentially changed userreg to /var/lib/globalreg at exit.
> 
> Ofcourse, both options are insecure. And user1 can screw user2's
> setup. But in windows it is the same.

yea, any 3-year old can screw windows :P

I think we can postpone this registry stuff, need to test this some
more. For the time being, it would be nice to get our patches back into
the package. My automount patch shouldn't collide with any other mount
method as it basically is only an "if config has automount line then
keep drives".

- Mark




Re: [Cooker] wine update for 9.1

2003-01-17 Thread danny
> no, it's more of a frontend than a configuration program. Let it have
> its own menu entry and when the user starts it and then a winexe through
> it, wine-config will run. Ah, I see, the user might be tempted to
> configure wine before running an exe. Hmm, have to think about this.
ok, but using it as a frontend sounds ok to me. Configure wine can be a 
menu entry added by the xwine package?
> 
> it's not Thierry's name that's in the changelog. Guess HA Quôc-Viêt
> <[EMAIL PROTECTED]> got impatient.
titi is maintainer and responsible :P
> 
> maybe I'm seeing probs where there aren't any but this
Let me see if I understand you:
- registry changes are always written to home dir
- if the installed win program is in global dir, some users miss 
reg entries if using a program not installed by them
- if writing reg to globaldir=realwindir you can corrupt your realwindir, 
and therefore windows.

Solution: 1) write config to globaldir!=windir. If this is possible.
2) change wine script to copy a fakeglobalreg from 
/var/lib/wine/globalreg to userhome dir at start. And copy the, 
potentially changed userreg to /var/lib/globalreg at exit.

Ofcourse, both options are insecure. And user1 can screw user2's setup. 
But in windows it is the same.


Danny






Re: [Cooker] wine update for 9.1

2003-01-17 Thread rcc
On Fri, 17 Jan 2003 10:00:06 +0100 (CET)
<[EMAIL PROTECTED]> wrote:

> On Fri, 17 Jan 2003, rcc wrote:
> > > > I like Xwine
> > 
> > this looks so much nicer
> Well than, I can try packaging it. But should wine depend on it and
> run it automatically on first start (after the wine-config.pl)?

no, it's more of a frontend than a configuration program. Let it have
its own menu entry and when the user starts it and then a winexe through
it, wine-config will run. Ah, I see, the user might be tempted to
configure wine before running an exe. Hmm, have to think about this.
 
> > suggest splitting out the stuff into yet another package.
> Lets keep it like it is, at least untill the release.

alright
 
> > Need sleep and there's a new wine package in
> > cooker which brutally dumped our thoroughly crafted mdkconf.
> > 
> aha.Didn't see that yet. My cooker install is hopelessly behind. Want
> to do a fresh install anyway but lack the time.
> 
> Thierry: any reasons for not applying some of the patches? Also: since

it's not Thierry's name that's in the changelog. Guess HA Quôc-Viêt
<[EMAIL PROTECTED]> got impatient.

> > Regarding the native vs fake win question: I use only the fake win,
> > so I could well live with a fake win as default. The screenshots at
> > codeweavers showed an option to use a fake win in the user's
> > homedir. Now, there's an idea...
> Think it makes sense? It would require every user to install a new
> windows program. Sometimes this makes sense. Sometimes it is a huge
> waste of diskspace. I usually (symbolic) link all the files of a
> program in a public dir to a subdir in my homedir. The result is that
> I can save personal stuff there, but the program files are shared. 

maybe I'm seeing probs where there aren't any but this

[registry]
;These are all booleans.  Y/y/T/t/1 are true, N/n/F/f/0 are false.
;Defaults are read all, write to Home

makes me think.

A native win should have a perfectly working registry. And since wine
alledgedly might corrupt win when installing soft through wine, I guess
most people will install the soft under native win and only run it in
wine. That should give them a sound registry base.

Now, as I understand it, installing soft onto the fake wine will not
change the global registry but only the user's

 ; Load Windows registries from the Windows directory
"LoadWindowsRegistryFiles" = "Y"
; TRY to write all changes to home registries
"WritetoHomeRegistryFiles" = "Y"

Assuming that registry changes at install worked, the new registry keys
are in the user's reg. Another user can see the files in the fake win
but has no access to their reg entries. On multiuser systems we could
make it "write changes to windows dir" which we actually don't want to
have with native win installations.

That registry thing has always been a mystery to me, even in my days as
MS user. And I'm not that much into wine to fully understand the
implications of the registry settings.

- Mark





Re: [Cooker] wine update for 9.1

2003-01-17 Thread danny
On Fri, 17 Jan 2003, rcc wrote:
> > > I like Xwine
> 
> this looks so much nicer
Well than, I can try packaging it. But should wine depend on it and run it 
automatically on first start (after the wine-config.pl)?

> I guess I don't get the logic behind mdk policy. Split libs from actual
> programs and then but progs in lib packages because they happen to be
> devel tools. Ah, it dawns on me, Thierry would probably suggest
> splitting out the stuff into yet another package.
Lets keep it like it is, at least untill the release.

> Need sleep and there's a new wine package in
> cooker which brutally dumped our thoroughly crafted mdkconf.
> 
aha.Didn't see that yet. My cooker install is hopelessly behind. Want to 
do a fresh install anyway but lack the time.

Thierry: any reasons for not applying some of the patches? Also: since 
Mark did some new stuff (regdefaults) that are working nice, and I fixed a 
few bugs in the config script, it is a bit awkward and more work to sync 
our stuff with this new release. A mail would have been nice.

> Regarding the native vs fake win question: I use only the fake win, so I
> could well live with a fake win as default. The screenshots at
> codeweavers showed an option to use a fake win in the user's homedir.
> Now, there's an idea...
Think it makes sense? It would require every user to install a new windows 
program. Sometimes this makes sense. Sometimes it is a huge waste of 
diskspace. I usually (symbolic) link all the files of a program in a 
public dir to a subdir in my homedir. The result is that I can save 
personal stuff there, but the program files are shared. 

danny
> 
> - Mark
> 





Re: [Cooker] wine update for 9.1

2003-01-16 Thread rcc
On Thu, 16 Jan 2003 23:03:13 +0100
Danny Tholen <[EMAIL PROTECTED]> wrote:

> On Thursday 16 January 2003 00:46, rcc wrote:

> > never seen it. Is it that tcl/tk thingy I never got to run?
> yes, it didn't run?

not for me, but I didn't try very hard

because

> > I like Xwine

this looks so much nicer

> > Another thing: do we have to split wine into 4 rpms? It's a pain to
> I think Thierry even wanted to split it in even more packages?

yes, I remember that
 
> > I think wine and wine-devel would be sufficient. I've not yet
> > seen an app that depends on libwine. 
> Me neither, but it is consistant with the mdk lib policy.

I feared you would say that 
 
> > And putting /usr/bin files like winegcc in
> > a lib-devel package looks somehow not right to me.
> Well, it is used for development?

I guess I don't get the logic behind mdk policy. Split libs from actual
programs and then but progs in lib packages because they happen to be
devel tools. Ah, it dawns on me, Thierry would probably suggest
splitting out the stuff into yet another package.

> Guess I do not agree, but perhaps you can convince me?

too late, in both senses. Need sleep and there's a new wine package in
cooker which brutally dumped our thoroughly crafted mdkconf.

Regarding the native vs fake win question: I use only the fake win, so I
could well live with a fake win as default. The screenshots at
codeweavers showed an option to use a fake win in the user's homedir.
Now, there's an idea...

- Mark




Re: [Cooker] wine update for 9.1

2003-01-16 Thread Danny Tholen
On Thursday 16 January 2003 00:46, rcc wrote:
> so you can actually do work at work? :)=)
actually, it was a collegues machine.

>
> never seen it. Is it that tcl/tk thingy I never got to run?
yes, it didn't run?
>
> I like Xwine, though last time I checked the config editor was not
> implemented yet.
I'll check it too when time permits.

>
> Another thing: do we have to split wine into 4 rpms? It's a pain to
I think Thierry even wanted to split it in even more packages?

> I think wine and wine-devel would be sufficient. I've not yet
> seen an app that depends on libwine. 
Me neither, but it is consistant with the mdk lib policy.

>Some of the utils stuff seems
> better kept with wine proper.
Like? Why move all these notepad, winemine stuff to the wine program? IMO they 
should be separate.

> And putting /usr/bin files like winegcc in
> a lib-devel package looks somehow not right to me.
Well, it is used for development?

Guess I do not agree, but perhaps you can convince me?

Danny




Re: [Cooker] wine update for 9.1

2003-01-16 Thread Damian Gatabria
>
> How do you *tell* that you've corrupted Windows? =)

Umm.. it doesn't crash correctly? :oP






Re: [Cooker] wine update for 9.1

2003-01-16 Thread Adam Williamson
On Thu, 2003-01-16 at 13:46, Wim Horst wrote:

> Good idea. Its very easy, with current default install, to corrupt your 
> existing windows when playing around with wine.

How do you *tell* that you've corrupted Windows? =)
-- 
adamw





Re: [Cooker] wine update for 9.1

2003-01-16 Thread Wim Horst
Op woensdag 15 januari 2003 20:16, schreef Danny Tholen:
> On Wednesday 15 January 2003 19:41, rcc wrote:
> > anyway, wine should pick up an existing win as long as it is in fstab.
> > The dummy win is always there in /var/lib/wine. Changing from one to the
> > other means changing one line in your .wine/config
>
> actually this failed on NT/2k/XP machines (I made an error in the script
> again, I am really no perl coder), but I have that fixed now (and a few
> other bugs which happen on 2k machines. It was usefull to install mdk at
> work:)
>
> Perhaps we can use the codeweavers wizard, isn't that one GPL?
>
> Danny

Good idea. Its very easy, with current default install, to corrupt your 
existing windows when playing around with wine.




Re: [Cooker] wine update for 9.1

2003-01-15 Thread rcc
On Wed, 15 Jan 2003 20:16:36 +0100
Danny Tholen <[EMAIL PROTECTED]> wrote:

> > anyway, wine should pick up an existing win as long as it is in
> > fstab. The dummy win is always there in /var/lib/wine. Changing from
> > one to the other means changing one line in your .wine/config
> actually this failed on NT/2k/XP machines

I have none of these, Win98 is the last MS OS ever to hit my HD :)

> (I made an error in the
> script again, I am really no perl coder), but I have that fixed now
> (and a few other bugs which happen on 2k machines. It was usefull to
> install mdk at work:)

so you can actually do work at work? :)=)
 
> Perhaps we can use the codeweavers wizard, isn't that one GPL?

never seen it. Is it that tcl/tk thingy I never got to run?

I like Xwine, though last time I checked the config editor was not
implemented yet.

Another thing: do we have to split wine into 4 rpms? It's a pain to
maintain. Though the "unpackaged files" feature in cooker helps
somewhat.
I think wine and wine-devel would be sufficient. I've not yet
seen an app that depends on libwine. Some of the utils stuff seems
better kept with wine proper. And putting /usr/bin files like winegcc in
a lib-devel package looks somehow not right to me.

- Mark




Re: [Cooker] wine update for 9.1

2003-01-15 Thread Danny Tholen
On Wednesday 15 January 2003 19:41, rcc wrote:
>
> anyway, wine should pick up an existing win as long as it is in fstab.
> The dummy win is always there in /var/lib/wine. Changing from one to the
> other means changing one line in your .wine/config
actually this failed on NT/2k/XP machines (I made an error in the script 
again, I am really no perl coder), but I have that fixed now (and a few other 
bugs which happen on 2k machines. It was usefull to install mdk at work:)

Perhaps we can use the codeweavers wizard, isn't that one GPL?

Danny




Re: [Cooker] wine update for 9.1

2003-01-15 Thread rcc
On Wed, 15 Jan 2003 19:15:25 +0100
Wim Horst <[EMAIL PROTECTED]> wrote:

> Is it possible to give it a first time wizard asking to use existing
> windows or creating a new windows directory structure.

sure, if you provide the code ;)

anyway, wine should pick up an existing win as long as it is in fstab.
The dummy win is always there in /var/lib/wine. Changing from one to the
other means changing one line in your .wine/config

- Mark






Re: [Cooker] wine update for 9.1

2003-01-15 Thread Wim Horst
Op dinsdag 14 januari 2003 09:37, schreef [EMAIL PROTECTED]:

Is it possible to give it a first time wizard asking to use existing windows 
or creating a new windows directory structure.


> I will soon send an updated version to Thierry.
>
> d.
>
> On Tue, 14 Jan 2003, Vincent Meyer, MD wrote:
> > Is an update of wine planned for 9.1?
> >
> > V.





Re: [Cooker] wine update for 9.1

2003-01-14 Thread John van Spaandonk
On Tuesday 14 January 2003 09:37, [EMAIL PROTECTED] wrote:
> I will soon send an updated version to Thierry.
>
> d.
>
> On Tue, 14 Jan 2003, Vincent Meyer, MD wrote:
> > Is an update of wine planned for 9.1?
> >
> > V.

This is good news!
Please make sure that it is compiled with CUPS support, and
you will have a winner distribution for MS-office users!





Re: [Cooker] wine update for 9.1

2003-01-14 Thread danny
I will soon send an updated version to Thierry. 

d.

On Tue, 14 Jan 2003, Vincent Meyer, MD wrote:

> Is an update of wine planned for 9.1?
> 
> V.
> 





Re: [Cooker] wine problem

2002-11-02 Thread Florent BERANGER
   
 > bah, completely forgot about this. Spent my time stealing isdn stuff   
> (kernel, capi, applets) from SuSE and RH to get some form of isdn dialer   
> applet running on mdk. BTW, looks really weird to have smpppd (SuSE meta   
> pppd) running on Mandrake, even though I changed "configure with yast2"   
> to "configure with drakconnect".   
>   
> Anyway, I attached a quick fix for the cdrom problem.   
>   
> Thierry?   
>   
> - Mark   
   
>--- wine-config.pl.old  2002-10-30 00:30:24.0 +0100   
>+++ wine-config.pl  2002-09-30 23:00:14.0 +0200   
>@@ -162,7 +162,7 @@   
>  {   
>   push @fat, $_[1] if ( -d $_[1]);   
>  }   
>-   elsif ($_[0] =~ /\/mnt\/cdrom\d?/)   
>+   elsif ($_[1] =~ /\/mnt\/cdrom\d?/)   
>  {   
>   push @iso, [ $_[1], $1 ] if ($_[3] =~ /dev=([\w\/]+)/);   
>  }   
   
It's not long to apply a patch so please, do it !   
  
Thanks,  
  Florent  





Re: [Cooker] wine problem

2002-10-30 Thread Florent BERANGER
 
> bah, completely forgot about this. Spent my time stealing isdn stuff 
> (kernel, capi, applets) from SuSE and RH to get some form of isdn dialer 
> applet running on mdk. BTW, looks really weird to have smpppd (SuSE meta 
> pppd) running on Mandrake, even though I changed "configure with yast2" 
> to "configure with drakconnect". 
> 
> Anyway, I attached a quick fix for the cdrom problem. 
> 
> Thierry? 
> 
> - Mark 
 
>--- wine-config.pl.old  2002-10-30 00:30:24.0 +0100 
>+++ wine-config.pl  2002-09-30 23:00:14.0 +0200 
>@@ -162,7 +162,7 @@ 
>  { 
>   push @fat, $_[1] if ( -d $_[1]); 
>  } 
>-   elsif ($_[0] =~ /\/mnt\/cdrom\d?/) 
>+   elsif ($_[1] =~ /\/mnt\/cdrom\d?/) 
>  { 
>   push @iso, [ $_[1], $1 ] if ($_[3] =~ /dev=([\w\/]+)/); 
>  } 
 
Is anyone applying the patch ? 
Thanks 
 





Re: [Cooker] wine problem

2002-10-29 Thread Florent BERANGER
Le Mardi 29 Octobre 2002 23:22, Pierre a écrit : 
> man wine.conf 
 
no, it must works out of the box. 
For me, I have resolved the problem by editing the config file but it must be 
fixed for everyone. 
 
> 
> On 2002.10.29 19:19 Florent BERANGER wrote: 
> >   Hello, 
> > 
> > I have a problem with wine "out of the box" : 
> > [cosmicflo@cosmic cosmicflo]$ wine /mnt/cdrom/Setup.exe 
> > Warning: could not find wine config [Drive x] entry for current 
> > working 
> > directory /mnt/cdrom; starting in windows directory. 
> > /usr/bin/wine.bin: cannot find 'Setup.exe' 
> > [cosmicflo@cosmic cosmicflo]$ 
> > 
> >   Florent 
 





Re: [Cooker] wine problem

2002-10-29 Thread rcc
On Wed, 30 Oct 2002 00:12:54 +0100
Danny Tholen <[EMAIL PROTECTED]> wrote:

> On Tuesday 29 October 2002 19:19, Florent BERANGER wrote:
> > directory /mnt/cdrom; starting in windows directory.
> > /usr/bin/wine.bin: cannot find 'Setup.exe'
> > [cosmicflo@cosmic cosmicflo]$
> >
> >   Florent
> 
> eh..well...I think I made a mistake in the autoconfig script so it
> forgets to add /mnt/cdrom to the .wine/config. Nobody noticed it
> before 9.0 was released. I will fix it as soon as I have time to look
> at it again, unless Mark beats me to it:)

bah, completely forgot about this. Spent my time stealing isdn stuff
(kernel, capi, applets) from SuSE and RH to get some form of isdn dialer
applet running on mdk. BTW, looks really weird to have smpppd (SuSE meta
pppd) running on Mandrake, even though I changed "configure with yast2"
to "configure with drakconnect".

Anyway, I attached a quick fix for the cdrom problem.

Thierry?

- Mark


--- wine-config.pl.old  2002-10-30 00:30:24.0 +0100
+++ wine-config.pl  2002-09-30 23:00:14.0 +0200
@@ -162,7 +162,7 @@
  {
   push @fat, $_[1] if ( -d $_[1]);
  }
-   elsif ($_[0] =~ /\/mnt\/cdrom\d?/)
+   elsif ($_[1] =~ /\/mnt\/cdrom\d?/)
  {
   push @iso, [ $_[1], $1 ] if ($_[3] =~ /dev=([\w\/]+)/);
  }



Re: [Cooker] wine problem

2002-10-29 Thread Pierre
man wine.conf

On 2002.10.29 19:19 Florent BERANGER wrote:

  Hello,

I have a problem with wine "out of the box" :
[cosmicflo@cosmic cosmicflo]$ wine /mnt/cdrom/Setup.exe
Warning: could not find wine config [Drive x] entry for current
working
directory /mnt/cdrom; starting in windows directory.
/usr/bin/wine.bin: cannot find 'Setup.exe'
[cosmicflo@cosmic cosmicflo]$

  Florent









Re: [Cooker] wine problem

2002-10-29 Thread Danny Tholen
On Tuesday 29 October 2002 19:19, Florent BERANGER wrote:
> directory /mnt/cdrom; starting in windows directory.
> /usr/bin/wine.bin: cannot find 'Setup.exe'
> [cosmicflo@cosmic cosmicflo]$
>
>   Florent

eh..well...I think I made a mistake in the autoconfig script so it forgets to 
add /mnt/cdrom to the .wine/config. Nobody noticed it before 9.0 was 
released. I will fix it as soon as I have time to look at it again, unless 
Mark beats me to it:)

Danny






Re: [Cooker] wine success stories

2002-09-17 Thread Brent Hasty

On Wednesday 04 September 2002 00:15, Leon Brooks wrote:
would it be possiable to direct wine to the /home/user/win directory created 
when using win4lin to link to all the dll's one needs?

> On Tue, 3 Sep 2002 22:59, Thierry Vignaud wrote:
> > "Florent BERANGER" <[EMAIL PROTECTED]> writes:
> >> I hope Lotus Notes, Half Life and Warcraft3 will works fine by std.
> >
> > a friend of mine reported that warcraft3 works under wine
>
> MSAccess works, but you need a fair few DLLs and registry entries (for the
> licence, for example, and oleaut32.dll needs to be native rather than
> builtin) from a working Windows installation to do it. Sigh.
>
> In theory, it should even be able to do an ODBC connection to MS SQL Server
> via unixODBC and FreeTDS, I'll find out tomorrow.
>
> Cheers; Leon




Re: [Cooker] Wine: FIX

2002-09-11 Thread Thierry Vignaud

huug <[EMAIL PROTECTED]> writes:

> > I got wine.tar.bz2 as an attachment. (?)
>
> The old beta of Gnus titi was using had some problems with mime
> handling.

yep :-(





Re: [Cooker] Wine: FIX

2002-09-10 Thread Brad Felmey

On Mon, 2002-09-09 at 14:07, Thierry Vignaud wrote:
> Danny Tholen <[EMAIL PROTECTED]> writes:
> 
> > Seems that Thierry screwed up:)
> > He did not package the new versions of wine-config.pl and
> > wine-launcher.sh.
> 
> i used what you give me
> 
> > Thierry, if you do not have my original files anymore, I attached
> > above files + a spec with some small fixes I had to make for
> > mdk-club.
> 
> as usual, you forgot attachments ... :-(

I got wine.tar.bz2 as an attachment. (?)
-- 
Brad Felmey





Re: [Cooker] Wine: FIX

2002-09-09 Thread Thierry Vignaud

Danny Tholen <[EMAIL PROTECTED]> writes:

> Seems that Thierry screwed up:)
> He did not package the new versions of wine-config.pl and
> wine-launcher.sh.

i used what you give me

> Thierry, if you do not have my original files anymore, I attached
> above files + a spec with some small fixes I had to make for
> mdk-club.

as usual, you forgot attachments ... :-(





Re: [Cooker] Wine: FIX

2002-09-09 Thread Danny Tholen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Seems that Thierry screwed up:)
He did not package the new versions of wine-config.pl and wine-launcher.sh.
Seems I couldn't reproduce because I was testing my own rpms instead of cookers.

Thierry, if you do not have my original files anymore, I attached above files + a spec 
with some small fixes I had to make for mdk-club.

Danny



On Monday 09 September 2002 19:59, rcc wrote:
> On Mon, 9 Sep 2002 17:33:11 +0200 (CEST)
>
> <[EMAIL PROTECTED]> wrote:
> > > The source rpm has the right script but the spec doesn't cp
> > > winelauncher.sh to wine
> > >
> > > we fiddled so much with the launcher script that the cp has
> > > apparently got lost in the process
> >
> > ah.Perhaps in my famous mixup of all the different specs. I
>
> might have been me, at first I wanted to remove winelauncher and move
> generic winelauncher to wine. Since that didn't work out I might have
> removed the cp line forgetting that there's still mdk's winelauncher.
>
> > > anyway, there's a new snapshot available
> >
> > eh..arent we in super terrible deep-freeze ?
>
> don't know really, maybe make it an update then?
>
> hum, from the announcement at freshmeat
> ---
> Changes: This release adds much-improved PowerPC support, more correct
> locale definitions, progress on the conversion of handle types to
> pointers, many Visio and Quicken fixes merged from Crossover, and lots
> of bugfixes.
> ---
>
> I think the stuff from crossover alone is worth the risk ;)
>
> and anyway, wine is beta no matter what
>
> - Mark

- -- 
Do your part to help preserve life on Earth -- by trying to preserve your own.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9fQgPaeiN+EU2vEIRAqCTAJ40QQJWryvaIwc3aBiHGGocAHJV2ACgqD+E
YzfjXuVxA54XXndxcMjag6g=
=jydD
-END PGP SIGNATURE-



wine.tar.bz2
Description: application/tbz


Re: [Cooker] Wine

2002-09-09 Thread rcc

On Mon, 9 Sep 2002 17:33:11 +0200 (CEST)
<[EMAIL PROTECTED]> wrote:


> > The source rpm has the right script but the spec doesn't cp
> > winelauncher.sh to wine
> > 
> > we fiddled so much with the launcher script that the cp has
> > apparently got lost in the process
> ah.Perhaps in my famous mixup of all the different specs. I

might have been me, at first I wanted to remove winelauncher and move
generic winelauncher to wine. Since that didn't work out I might have
removed the cp line forgetting that there's still mdk's winelauncher.
 
> > anyway, there's a new snapshot available
> eh..arent we in super terrible deep-freeze ?

don't know really, maybe make it an update then?

hum, from the announcement at freshmeat
---
Changes: This release adds much-improved PowerPC support, more correct
locale definitions, progress on the conversion of handle types to
pointers, many Visio and Quicken fixes merged from Crossover, and lots
of bugfixes. 
---

I think the stuff from crossover alone is worth the risk ;)

and anyway, wine is beta no matter what

- Mark




Re: [Cooker] Wine

2002-09-09 Thread danny

On Mon, 9 Sep 2002, rcc wrote:

> On 09 Sep 2002 10:10:07 -0400
> dang, that's the old one
yup noticed that 2.
> 
> I wonder where it's coming from? And even more puzzled why it works
> here?
Yes, it also works for me. Strange.
> 
> The source rpm has the right script but the spec doesn't cp
> winelauncher.sh to wine
> 
> we fiddled so much with the launcher script that the cp has apparently
> got lost in the process
ah.Perhaps in my famous mixup of all the different specs. I
> 
> anyway, there's a new snapshot available
eh..arent we in super terrible deep-freeze ?
> 
> Danny, do you still have the 20020509 spec somewhere around? I can't
> remember the line that copies winelauncher to wine
>
will check.

Danny






Re: [Cooker] Wine

2002-09-09 Thread danny

On 9 Sep 2002, Austin Acton wrote:

> bash-2.05b$ more /usr/bin/wine
> #!/bin/sh
> # -*- Mode: sh -*-
> # Copyright (C) 2000 by Chmouel Boudjnah <[EMAIL PROTECTED]>,
> # MandrakeSoft
> # Redistribution of this file is permitted under the terms of the GNU 
> # Public License (GPL)
> 
> true_binary=/usr/bin/wine.bin
> default=/etc/wine/wine.reg
Ack! This is not my rewritten script, but the old one!
I will check the src.rpm this evening and send it to Thierry.

Danny





Re: [Cooker] Wine

2002-09-09 Thread Austin Acton

Danny, hope this helps:

1. CLEANUP
[root@groundstate austin]# urpme wine
bash-2.05b$ rm -fr .wine

2. FRESH INSTALL FROM COOKER
[root@groundstate austin]# urpmi wine
installing /var/cache/urpmi/rpms/libwine1-20020804-1mdk.i586.rpm
/var/cache/urpmi/rpms/wine-20020804-1mdk.i586.rpm

3. WHAT'S IN MY PATH
bash-2.05b$ wi [TAB]
wine   wineclipsrvwineserver winicontoppm   wish
wine.bin   wineconsolewineshelllink  winpos wish8.3
bash-2.05b$ ls -l /usr/bin/win*
-rwxr-xr-x1 root root  526 Aug 19 08:19 /usr/bin/wine
-rwxr-xr-x1 root root15096 Aug 19 08:19
/usr/bin/wine.bin
-rwxr-xr-x1 root root18412 Aug 19 08:19
/usr/bin/wineclipsrv
-rwxr-xr-x1 root root 1584 Aug 19 08:19
/usr/bin/wineconsole
-rwxr-xr-x1 root root   199800 Aug 19 08:19
/usr/bin/wineserver
-rwxr-xr-x1 root root 5726 Aug 19 08:19
/usr/bin/wineshelllink
-rwxr-xr-x1 root root13160 Jul  7 14:02
/usr/bin/winicontoppm

4. HERE'S THE SCRIPT
bash-2.05b$ more /usr/bin/wine
#!/bin/sh
# -*- Mode: sh -*-
# Copyright (C) 2000 by Chmouel Boudjnah <[EMAIL PROTECTED]>,
# MandrakeSoft
# Redistribution of this file is permitted under the terms of the GNU 
# Public License (GPL)

true_binary=/usr/bin/wine.bin
default=/etc/wine/wine.reg
configurator=/usr/share/wine/wine-config
winedir=${HOME}/.wine/

if [ ! -d ${winedir} ];then
mkdir -p ${winedir}
cp ${default} ${winedir}/config
if [ -x /usr/bin/perl ];then
perl ${configurator} ${winedir}/config || :
fi
fi

${true_binary} "$@"

5. LET'S TRY WINE-CONFIG
bash-2.05b$ mkdir .wine
bash-2.05b$ cp /etc/wine/config .wine
bash-2.05b$ cp .wine/config .wine/config-orig
bash-2.05b$ /usr/share/wine/wine-config .wine/config
bash-2.05b$ diff .wine/config .wine/config-orig
33c33
< "Path" = "/var/lib/wine"
---
> "Path" = "/mnt/windows"

6. LET'S TRY THE DEFAULT SETUP
bash-2.05b$ rm -fr .wine
bash-2.05b$ wine
cp: cannot stat `/etc/wine/wine.reg': No such file or directory
cp: cannot stat `/home/austin/.wine//config': No such file or directory
wineserver: /home/austin/.wine/config is not a valid registry file
wine client error:(nil): recvmsg: Connection reset by peer
bash-2.05b$ cat .wine/config
bash-2.05b$ 

Thanks for your efforts!  Hope we can fix this.
Austin

On Mon, 2002-09-09 at 03:50, [EMAIL PROTECTED] wrote:
> Hi Austin,
> care to be my test case? i want to get it fixed before 9.0 and
> it works on my cooker machine and also on 8.2, and for several people
> it is working. But not for a few others.
> It think it may be related to the perl autoconfig script. 
> 
> Can you check:
> 1) whether there is really 1 'wine' in your path, and that this
> file is a script which should do the copying.
> 2) Can you copy the /etc/wine/config to your home dir, and run
> the perl script /usr/share/wine/wine-config on this file?
> And see if it produces any errors, and how does it modify the config?
> 
> btw, did cookerlist break again? This is getting annoying.
> > P.S. Nancy is my girlfriend.  Don't panic.  I'm not a transvestite.  :-p
> I understand Austin, we all have our strangenesess :P
> 
> 
> bye!
> Danny
> 





Re: [Cooker] Wine

2002-09-09 Thread rcc

On 09 Sep 2002 10:10:07 -0400
Austin Acton <[EMAIL PROTECTED]> wrote:



> true_binary=/usr/bin/wine.bin
> default=/etc/wine/wine.reg
> configurator=/usr/share/wine/wine-config
> winedir=${HOME}/.wine/
> 
> if [ ! -d ${winedir} ];then
> mkdir -p ${winedir}
> cp ${default} ${winedir}/config
> if [ -x /usr/bin/perl ];then
>   perl ${configurator} ${winedir}/config || :
> fi
> fi
> 
> ${true_binary} "$@"


dang, that's the old one

I wonder where it's coming from? And even more puzzled why it works
here?

The source rpm has the right script but the spec doesn't cp
winelauncher.sh to wine

we fiddled so much with the launcher script that the cp has apparently
got lost in the process

anyway, there's a new snapshot available

Danny, do you still have the 20020509 spec somewhere around? I can't
remember the line that copies winelauncher to wine

- Mark




Re: [Cooker] wine problem

2002-09-04 Thread Austin Acton

This is because the current wine rpm installs a file called
~/.wine/config but it is empty.  It should be a copy of
/etc/wine/config.

Also it uses /tmp/wine-{username} as temp, but it doesn't create the
directory the first time you run wine.  It should, or it should use /tmp
or ~/tmp or something that exists.

Austin

On Wed, 2002-09-04 at 19:03, Florent BERANGER wrote:
>Hello,
> 
> Here the output when I try to install Adobe Photoshop 3
> with wine by default (I have it working with a wine config
> tool in past) :
> 
> bash-2.05b$ wine /mnt/cdrom/photoshp/disk1/pssetup.exe
> cp: Ne peut évaluer `/etc/wine/wine.reg' par stat(): No
> such file or directory
> cp: Ne peut évaluer `/home/cosmicflo/.wine//config' par
> stat(): No such file or directory
> wineserver: /home/cosmicflo/.wine/config is not a valid
> registry file
> wine: for some mysterious reason, the wine server failed
> to run.
> 
> 
> For info, I have just installed wine by urpmi before.
> 
> Thanks for your help
> --
> EXCEPTIONNEL!
> Tiscali lance les forfaits Internet Illimités,
> à partir de 15,95EUR / mois.
> Pour en profiter,cliquez ici: http://register.tiscali.fr/forfaits/
> Offres soumises à conditions.
> 
> 
> 





Re: [Cooker] wine Windows system detection

2002-09-04 Thread danny

On Wed, 4 Sep 2002, Florent BERANGER wrote:

> Is wine, as implemented in Mandrake, detect a Windows
> partition and use it ( FAT & NTFS ) ?
Yes, that is, Jerome and I tried to handle the detecting of the
correct windows directory on both fat32 and ntfs partitions. 
However, I have no idea whether it works on all strange combinations
of windowsdirs and partitions. Especially I never tested on NTFS 
partitions.

> 
> And is Lotus Notes works on wine (original Mdk config)
> without / with Windows partition ?
No idea. Try it;)

Danny

> 
> Thanks
> --
> EXCEPTIONNEL!
> Tiscali lance les forfaits Internet Illimités,
> à partir de 15,95EUR / mois.
> Pour en profiter,cliquez ici: http://register.tiscali.fr/forfaits/
> Offres soumises à conditions.
> 
> 
> 





Re: [Cooker] Wine server failed to run

2002-09-04 Thread Igor Izyumin

On Friday 30 August 2002 02:44 pm, Ross Melin wrote:
> Beta4 updated from cooker today.
> Wine fails with the following errors.
> $ wine /mnt/windows/windows/notepad.exe
> wineserver: /home/ross/.wine/config is not a valid
> registry file
> wine: for some mysterious reason, the wine server
> failed to run.
Do you have a valid ~/.wine/config?  Did you configure wine?
-- 
-- Igor




Re: [Cooker] wine success stories

2002-09-03 Thread Thierry Vignaud

"Florent BERANGER" <[EMAIL PROTECTED]> writes:

> I hope Lotus Notes, Half Life and Warcraft3 will works fine by std.

a friend of mine reported that warcraft3 works under wine





Re: [Cooker] WINE has no multimedia (sound)

2002-08-30 Thread Danny Tholen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

delete your .wine directory and try again.
It should be setup automagically.

Danny

On Thursday 29 August 2002 19:55, Jeremy Salch wrote:
> Whenever wine runs a program it complains about wine-MM section not being
> setup. and there is no sound

- -- 
Yes, but which self do you want to be?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9b1lPaeiN+EU2vEIRAgPSAKCeuL4asvLyW5M/ql/72UbyESJceQCfSs4N
+yLgQly/z2FOOak5mDCNy2g=
=Ilgi
-END PGP SIGNATURE-





Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

hehe, this  thread started to get amusing now:)
anyways, no offence whatsover and thanks for a insightful discussion

ahh, one more hour of sleep then I'm off to work *sigh*





Re: [Cooker] wine %description

2002-08-21 Thread Igor Izyumin

On Wednesday 21 August 2002 09:20 pm, Richard G. Houser wrote:
> Anyone else think it might be beneficial to either include the words
> "wrapper" or "compatibility layer" in this description?  These two come
> to my mind immediately whenever I think of WINE.  As an added bonus for
> the "wrapper" description, many of the Windows gamers that started at
> least 2+ years ago are likely to be familiar with Glide or OpenGL
> wrappers.  A lot of drivers just before that had buggy OpenGL support
> and some applications only supported the proprietary Glide API so these
> wrapper DLLs were a must to use many programs with the newer hardware.

That would simply confuse things.  My opinion: who cares?  It's just a package 
description, not anything which pretends to be an authoritative source.  
Hardly anybody ever reads these things.  If they do, they'll understand what 
it's supposed to do if you just call it an emulator.  People know what 
emulators are, they would get confused if you say that it is a "an API 
compatibility wrapper for Win32 binaries" or something like that.  If they 
want more details on how it works, they will do a google search and go to 
winehq.com which clarifies things on the nuts and bolts.

"Too much detail" is a major problem with package descriptions.  When people 
decide whether to install a package or not, they want to know WHAT a program 
does, not HOW it does it.
-- 
-- Igor




Re: [Cooker] wine %description

2002-08-21 Thread Richard G. Houser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Per Øyvind Karlsen wrote:

| Mandrake is not _ONLY_ targeted at "newbies", and describing wine as
| an emulator when it's not (WINE still stands for Wine Is Not an
| Emulator;) will make "hackers" think of us as stupid;)
| anyways, it's not harder than just grab the description from
| winehq.com/about
|
| From winehq.com/about:
|
| "Wine is an implementation of the Windows Win32 and Win16 APIs on top
| of X and Unix. Think of Wine as a Windows compatibility layer. Wine
| provides both a development toolkit (Winelib) for porting Windows
| sources to Unix and a program loader, allowing many unmodified Windows
| 3.x/95/98/ME/NT/W2K/XP binaries to run under Intel Unixes. Wine works
| on most popular Intel Unixes, including Linux ,
| FreeBSD , and Solaris
| .
|
| Wine does not require Microsoft Windows, as it is a completely
| alternative implementation consisting of 100% Microsoft-free code, but
| it can optionally use native system DLLs if they are available. Wine
| comes with complete sources, documentation and examples and is freely
| redistributable. (The licensing terms
| are the GNU Lesser General
| Public License.)"
|
| This should explain it good enough that most linux users understand
| what it's for, and if it's still not good enough it's just to explain
| it better, but still, claiming that wine is an emulator, when it's
| not, well... it's kinda ..
|
| From the wine package
|
| "%description
| This is an ALPHA release of Wine, the MS-Windows emulator.  This is
| still a developers release and many applications may still not work.
|
| This package consists of the emulator program for running windows
| executables.
|
| Wine is often updated."
|
| I actually don't think this explains it much better for those without
| much technical knowledge, and naming Wine "the MS-Windows emulator",
| that's actually quite stupid.
| Anyways the explanation from winehq is better and correct, and
| probably not more confusing for a new user than the one from the wine
| package
|
|
|
| Ben Reser wrote:
|
|> On Thu, Aug 22, 2002 at 01:42:57AM +0200, Philippe Coulonges wrote:
|>  
|>
|>> In my response, I mistaken your message and the one from Ben Reser.
|>> Rereading it, it may look like you're the one that don't understand
|>> the difference, but he is.
|>>   
|>
|>
|> I most certianly *DO* understand the difference.  But you're applying
|> the term emulator to only processor emulation which is certainly a fine
|> distinction that maybe hackers make, but the dictionary and common users
|> do not make!  And considering that for the most part Mandrake is for
|> common users not hackers (though some of us use Mandrake) we should be
|> using language common users understand not elitist hacker definitions.
|>
|>  
|>
|
|
Anyone else think it might be beneficial to either include the words
"wrapper" or "compatibility layer" in this description?  These two come
to my mind immediately whenever I think of WINE.  As an added bonus for
the "wrapper" description, many of the Windows gamers that started at
least 2+ years ago are likely to be familiar with Glide or OpenGL
wrappers.  A lot of drivers just before that had buggy OpenGL support
and some applications only supported the proprietary Glide API so these
wrapper DLLs were a must to use many programs with the newer hardware.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj1kSl4ACgkQUMkt1ZRwL1MgxgCcD6mtcHFqmOHx5i5/gky4poj+
BAcAn2JKoCowdOEYPzg4grMUbTNHPZGF
=EaSN
-END PGP SIGNATURE-






Re: [Cooker] wine %description

2002-08-21 Thread Ben Reser

On Thu, Aug 22, 2002 at 02:06:10AM +0200, Per Øyvind Karlsen wrote:
> Mandrake is not _ONLY_ targeted at "newbies", and describing wine as an 
> emulator when it's not (WINE still stands for Wine Is Not an Emulator;) 
> will make "hackers" think of us as stupid;)
> anyways, it's not harder than just grab the description from 
> winehq.com/about

I didn't say it was.

> From winehq.com/about:
> 
> "Wine is an implementation of the Windows Win32 and Win16 APIs on top of 
> X and Unix. Think of Wine as a Windows compatibility layer. Wine 
> provides both a development toolkit (Winelib) for porting Windows 
> sources to Unix and a program loader, allowing many unmodified Windows 
> 3.x/95/98/ME/NT/W2K/XP binaries to run under Intel Unixes. Wine works on 
> most popular Intel Unixes, including Linux , 
> FreeBSD , and Solaris 
> .
> 
> Wine does not require Microsoft Windows, as it is a completely 
> alternative implementation consisting of 100% Microsoft-free code, but 
> it can optionally use native system DLLs if they are available. Wine 
> comes with complete sources, documentation and examples and is freely 
> redistributable. (The licensing terms 
> are the GNU Lesser General 
> Public License.)"
> 
> This should explain it good enough that most linux users understand what 
> it's for, and if it's still not good enough it's just to explain it 
> better, but still, claiming that wine is an emulator, when it's not, 
> well... it's kinda ..

So submit a patch to change the spec file and be doen with it.  If you
know enough to be looking at the spec you can submit a patch.  That is a
better description but not because it just doesn't call WINE an
emulator.  Because WINE is an emulator.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

If your love has no hope of being welcomed do not voice it; for if it 
be silent it can endure, a guarded flame, within you.
- The Wisdom of the Sands




Re: ;) Re: [Cooker] wine %description

2002-08-21 Thread Ben Reser

On Thu, Aug 22, 2002 at 02:34:51AM +0200, Per Øyvind Karlsen wrote:
> Let's try to rephrase this;
> My point is that you don't call wine for an emulator just to make people 
> understand what it's purpose is, when it's not an emulator.
> Especially not when it's not hard to desribe it correctly and at the 
> same time make people understad it's purpose.

The purpose of the a %description is to let people know what the app
does.  If you don't speak in the terms they understand then it's
worthelss...  To some degree it's an emulator.  You guys just want to
use overly broad definitions of the term.  My mother and most of my
non-techie friends won't understand the distinctions you guys are trying
to make.  Now I'm not saying the %description couldn't be imporved.  But
WINE *IS* an emulator at some level.

> eg. people did'nt call PC-DOS, DR-DOS, etc. for MS-DOS emulators just 
> because they could mostly run the same programs.

Doesn't mean they couldn't be called that.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

If your love has no hope of being welcomed do not voice it; for if it 
be silent it can endure, a guarded flame, within you.
- The Wisdom of the Sands




Re: ;) Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

heh, not really,
I'm not so great at writing english as I once was:o)


Let's try to rephrase this;
My point is that you don't call wine for an emulator just to make people 
understand what it's purpose is, when it's not an emulator.
Especially not when it's not hard to desribe it correctly and at the 
same time make people understad it's purpose.

eg. people did'nt call PC-DOS, DR-DOS, etc. for MS-DOS emulators just 
because they could mostly run the same programs.


allen wrote:

>On Wednesday 21 August 2002 08:23 pm, Per Øyvind Karlsen wrote:
>  
>
>>aye, agree
>>anyways, my point is that describing something wrong is not a good idea
>>even if it would make people easily understand what it's for, especially
>>not when you can explain someting right and still make people as easily
>>understand it's purpose:)
>>
>>
>
>I'm not sure I understand...
>
>Did you just say "Get rid of marketing people ?"
>
>;)
>
>-AEF
>
>
>  
>







Re: [Cooker] wine %description

2002-08-21 Thread Ben Reser

On Thu, Aug 22, 2002 at 01:10:10AM +0200, Philippe Coulonges wrote:
> Wine Is Not An Emulator.
> 
> As such, it can only work on an Intel platform, executing native Windows 
> binaries.
> Opposite to Windows, Linux works on many hardware platforms, but Wine can't, 
> because it is not an emulator.
> 
> Does it makes the point clearer ?

No because you're still being silly.  Wine may not emulate the
processor.  But it does emulate the DLLs and API functions that
Microsoft Windows provides.  Definition 3 from the American Heritage
Dictionary (from previously provided dictionary.com URL) is:

3. Computer Science.  To imitate the function of (another system), as by
modifications to hardware or software that allow the imitating system to
accept the same data, execute the same programs and achieve the same
results as imiteated the system.

Saying that WINE is not an emulator is runs simply counter to the
everyday definition that most uers understand.  It is an emulator.  It
just isn't emulating a processor which is what you're thinking of when
you say emulator.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

If your love has no hope of being welcomed do not voice it; for if it 
be silent it can endure, a guarded flame, within you.
- The Wisdom of the Sands




Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

aye, agree
anyways, my point is that describing something wrong is not a good idea 
even if it would make people easily understand what it's for, especially 
not when you can explain someting right and still make people as easily 
understand it's purpose:)


Adam Williamson wrote:

>On Thu, 2002-08-22 at 00:49, Ben Reser wrote:
>
>  
>
>>I most certianly *DO* understand the difference.  But you're applying
>>the term emulator to only processor emulation which is certainly a fine
>>distinction that maybe hackers make, but the dictionary and common users
>>do not make!  And considering that for the most part Mandrake is for
>>common users not hackers (though some of us use Mandrake) we should be
>>using language common users understand not elitist hacker definitions.
>>
>>
>
>Actually I don't think wine really *does* fit in with most people's
>conception of an emulator. When I run an emulator I expect a recreation
>of the original machine / OS / whatever. wine expressly doesn't provide
>this; you don't run wine and get a windows desktop with a start button
>and an annoying paperclip, etc. you use wine to run windows programs,
>it's not exactly emulating windows because you can't run wine then point
>at something and go "look! windows!". badly phrased, but I hope you get
>what I mean.
>  
>







Re: [Cooker] wine %description

2002-08-21 Thread Adam Williamson

On Thu, 2002-08-22 at 00:49, Ben Reser wrote:

> I most certianly *DO* understand the difference.  But you're applying
> the term emulator to only processor emulation which is certainly a fine
> distinction that maybe hackers make, but the dictionary and common users
> do not make!  And considering that for the most part Mandrake is for
> common users not hackers (though some of us use Mandrake) we should be
> using language common users understand not elitist hacker definitions.

Actually I don't think wine really *does* fit in with most people's
conception of an emulator. When I run an emulator I expect a recreation
of the original machine / OS / whatever. wine expressly doesn't provide
this; you don't run wine and get a windows desktop with a start button
and an annoying paperclip, etc. you use wine to run windows programs,
it's not exactly emulating windows because you can't run wine then point
at something and go "look! windows!". badly phrased, but I hope you get
what I mean.
-- 
adamw





Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

ah, I actually got to the point afterwards:)
anyways, if something's wrong, it should be corrected, even if it's just 
a %description
The maintaner could just explain shortly that wine is a windows 
implementation, and that people may think of it as windows for linux, or 
something similar, whatever that's correct
:)
Philippe Coulonges wrote:

>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Le Jeudi 22 Août 2002 01:00, Per Øyvind Karlsen a goretquoté :
>
>  
>
>>?
>>
>>
>
>Wine Is Not An Emulator.
>
>As such, it can only work on an Intel platform, executing native Windows 
>binaries.
>Opposite to Windows, Linux works on many hardware platforms, but Wine can't, 
>because it is not an emulator.
>
>Does it makes the point clearer ?
>
>CU
>CPHIL
>
>- -- 
>  ()Campagne du ruban ASCII :
>  /\Contre les mails en HTML et les vcard !
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1.0.7 (GNU/Linux)
>
>iD8DBQE9ZB3TYJwqltj/jHgRAlqVAKCJVBzjRSFPSMcRp7Nnicgls5Y2sACeLPzW
>NQUoGz3KIGlHTsA/UgkHadU=
>=zmp5
>-END PGP SIGNATURE-
>
>
>
>
>  
>







Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

Mandrake is not _ONLY_ targeted at "newbies", and describing wine as an 
emulator when it's not (WINE still stands for Wine Is Not an Emulator;) 
will make "hackers" think of us as stupid;)
anyways, it's not harder than just grab the description from 
winehq.com/about

 From winehq.com/about:

"Wine is an implementation of the Windows Win32 and Win16 APIs on top of 
X and Unix. Think of Wine as a Windows compatibility layer. Wine 
provides both a development toolkit (Winelib) for porting Windows 
sources to Unix and a program loader, allowing many unmodified Windows 
3.x/95/98/ME/NT/W2K/XP binaries to run under Intel Unixes. Wine works on 
most popular Intel Unixes, including Linux , 
FreeBSD , and Solaris 
.

Wine does not require Microsoft Windows, as it is a completely 
alternative implementation consisting of 100% Microsoft-free code, but 
it can optionally use native system DLLs if they are available. Wine 
comes with complete sources, documentation and examples and is freely 
redistributable. (The licensing terms 
are the GNU Lesser General 
Public License.)"

This should explain it good enough that most linux users understand what 
it's for, and if it's still not good enough it's just to explain it 
better, but still, claiming that wine is an emulator, when it's not, 
well... it's kinda ..

 From the wine package

"%description
This is an ALPHA release of Wine, the MS-Windows emulator.  This is
still a developers release and many applications may still not work.

This package consists of the emulator program for running windows 
executables.

Wine is often updated."

I actually don't think this explains it much better for those without 
much technical knowledge, and naming Wine "the MS-Windows emulator", 
that's actually quite stupid.
Anyways the explanation from winehq is better and correct, and probably 
not more confusing for a new user than the one from the wine package



Ben Reser wrote:

>On Thu, Aug 22, 2002 at 01:42:57AM +0200, Philippe Coulonges wrote:
>  
>
>>In my response, I mistaken your message and the one from Ben Reser.
>>Rereading it, it may look like you're the one that don't understand the 
>>difference, but he is.
>>
>>
>
>I most certianly *DO* understand the difference.  But you're applying
>the term emulator to only processor emulation which is certainly a fine
>distinction that maybe hackers make, but the dictionary and common users
>do not make!  And considering that for the most part Mandrake is for
>common users not hackers (though some of us use Mandrake) we should be
>using language common users understand not elitist hacker definitions.
>
>  
>







Re: [Cooker] wine %description

2002-08-21 Thread Ben Reser

On Thu, Aug 22, 2002 at 01:42:57AM +0200, Philippe Coulonges wrote:
> In my response, I mistaken your message and the one from Ben Reser.
> Rereading it, it may look like you're the one that don't understand the 
> difference, but he is.

I most certianly *DO* understand the difference.  But you're applying
the term emulator to only processor emulation which is certainly a fine
distinction that maybe hackers make, but the dictionary and common users
do not make!  And considering that for the most part Mandrake is for
common users not hackers (though some of us use Mandrake) we should be
using language common users understand not elitist hacker definitions.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

If your love has no hope of being welcomed do not voice it; for if it 
be silent it can endure, a guarded flame, within you.
- The Wisdom of the Sands




Re: [Cooker] wine %description

2002-08-21 Thread Philippe Coulonges

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le Jeudi 22 Août 2002 01:00, Per Øyvind Karlsen a goretquoté :
> ?

Sorry.

In my response, I mistaken your message and the one from Ben Reser.
Rereading it, it may look like you're the one that don't understand the 
difference, but he is.

For Linux PPC, I was just kidding.

CU
CPHIL

- -- 
Je compose de la musique aussi naturellement
qu'une truie peut pisser.
-- Mozart.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ZCWBYJwqltj/jHgRAlUGAJ9Y51yr3iMUsYJY+HU0dkntlSSh3QCg1AUa
0Vc7X4cAnknYytN2CEINZv4=
=ECgG
-END PGP SIGNATURE-





Re: [Cooker] wine %description

2002-08-21 Thread Philippe Coulonges

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le Jeudi 22 Août 2002 01:00, Per Øyvind Karlsen a goretquoté :

> ?

Wine Is Not An Emulator.

As such, it can only work on an Intel platform, executing native Windows 
binaries.
Opposite to Windows, Linux works on many hardware platforms, but Wine can't, 
because it is not an emulator.

Does it makes the point clearer ?

CU
CPHIL

- -- 
  ()Campagne du ruban ASCII :
  /\Contre les mails en HTML et les vcard !
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ZB3TYJwqltj/jHgRAlqVAKCJVBzjRSFPSMcRp7Nnicgls5Y2sACeLPzW
NQUoGz3KIGlHTsA/UgkHadU=
=zmp5
-END PGP SIGNATURE-





Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

?
Philippe Coulonges wrote:

>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Le Mercredi 21 Août 2002 23:18, Ben Reser a écrit :
>  
>
>>On Wed, Aug 21, 2002 at 10:03:18AM +0200, Per Øyvind Karlsen wrote:
>>
>>
>
>  
>
>>>wine's %description are incorrect, wine is NOT an emulator;)
>>>Time to finally correct this?
>>>  
>>>
>>Blah who cares... It's an emulator of the interface.  Unless you're
>>using the actual windows binaries it's emulation.  Try looking up the
>>word emulator sometime:
>>http://www.dictionary.com/search?q=emulator
>>
>>Most users don't know the fine distinction anyway and frankly using the
>>term emulator is more clear.
>>
>>
>
>It looks like we just found the perfect maintainer for wine in Mandrake PPC.
>
>CU
>CPHIL
>
>- -- 
>Hé papa, je ne savais pas que "FORMAT C:" faisait ca !? 
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1.0.7 (GNU/Linux)
>
>iD8DBQE9ZBQqYJwqltj/jHgRAu9KAKCl1Cd17pL1mwIok5CXnMPMIXxRJwCZASuT
>icxSSVI77gexQ5bM0HjxyqY=
>=igfu
>-END PGP SIGNATURE-
>
>
>
>
>  
>







Re: [Cooker] wine %description

2002-08-21 Thread Philippe Coulonges

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le Mercredi 21 Août 2002 23:18, Ben Reser a écrit :
> On Wed, Aug 21, 2002 at 10:03:18AM +0200, Per Øyvind Karlsen wrote:

> > wine's %description are incorrect, wine is NOT an emulator;)
> > Time to finally correct this?
>
> Blah who cares... It's an emulator of the interface.  Unless you're
> using the actual windows binaries it's emulation.  Try looking up the
> word emulator sometime:
> http://www.dictionary.com/search?q=emulator
>
> Most users don't know the fine distinction anyway and frankly using the
> term emulator is more clear.

It looks like we just found the perfect maintainer for wine in Mandrake PPC.

CU
CPHIL

- -- 
Hé papa, je ne savais pas que "FORMAT C:" faisait ca !? 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ZBQqYJwqltj/jHgRAu9KAKCl1Cd17pL1mwIok5CXnMPMIXxRJwCZASuT
icxSSVI77gexQ5bM0HjxyqY=
=igfu
-END PGP SIGNATURE-





Re: [Cooker] wine

2002-08-21 Thread Danny Tholen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 21 August 2002 23:13, Xavier Granier wrote:

>   It do nothing.

great bug report :P


- -- 
And ever has it been known that love knows not its own depth until the
hour of separation.
-- Kahlil Gibran
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE9ZAViaeiN+EU2vEIRAn0DAJikLwnbcteW2mh6wBVrzEXpni4YAJ9wsA8z
cCJuqw4omHzFS3Udy/Vj/w==
=4a+j
-END PGP SIGNATURE-





Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

Hey, it's kinda silly to call wine an emulator when WINE stands for Wine 
Is Not an Emulator...
anyways, we want perfection!;)
Ben Reser wrote:

>On Wed, Aug 21, 2002 at 10:03:18AM +0200, Per Øyvind Karlsen wrote:
>  
>
>>wine's %description are incorrect, wine is NOT an emulator;)
>>Time to finally correct this?
>>
>>
>
>Blah who cares... It's an emulator of the interface.  Unless you're
>using the actual windows binaries it's emulation.  Try looking up the
>word emulator sometime:
>http://www.dictionary.com/search?q=emulator
>
>Most users don't know the fine distinction anyway and frankly using the
>term emulator is more clear.
>
>  
>







Re: [Cooker] wine %description

2002-08-21 Thread Ben Reser

On Wed, Aug 21, 2002 at 10:03:18AM +0200, Per Øyvind Karlsen wrote:
> wine's %description are incorrect, wine is NOT an emulator;)
> Time to finally correct this?

Blah who cares... It's an emulator of the interface.  Unless you're
using the actual windows binaries it's emulation.  Try looking up the
word emulator sometime:
http://www.dictionary.com/search?q=emulator

Most users don't know the fine distinction anyway and frankly using the
term emulator is more clear.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

If your love has no hope of being welcomed do not voice it; for if it 
be silent it can endure, a guarded flame, within you.
- The Wisdom of the Sands




Re: [Cooker] wine

2002-08-21 Thread Brent Hasty

On Wednesday 21 August 2002 13:02, Danny Tholen wrote:
My system is running pure linux, on reiserfs partitions.  I also have win4lin 
4.0 installed to make up for what wine is not yet capeable of.  Is it 
possiable to direct wine to the ~/win directory inside of each users home 
directory like it were a fat partiton with full win98 installed in it?

I will be giving the autocad2000 thing a try and let you know the results ;-).

> As people might have noticed,
> wine changed quite a bit. I'm interested in some feedback. Especially
> whether autocad runs or doesn't run.
>
> Also, I would like to ask you to remove your old ~/.wine/config, and give
> me some feedback on the .wine/config that wine auto-creates for you. Does
> it pick up all your windows partitions? Cdrom drives? Does it set the
> windows dir correctly? Especially people with win NT/2k/xp should test
> this, as I have no such system to test with.
>
> Danny

-- 
"The place of the material world in the universe is that of an exquisitely 
beautiful precipitate or varied cloud-work in the universal Æther, determined 
by a geometrical necessity" ~ Professor John G. Macvicar1870 ~

Brent Hasty
http://www.Hasty-Solutions.com




Re: [Cooker] wine %description

2002-08-21 Thread Per Øyvind Karlsen

hehe, yeah, after we poked the bot with a stick earlier today;)
-Dvalin
Randy wrote:

> Even our friendly #mandrake bot knows it's an interface layer:
>
>   Wine: An interface between windows applications and the 
> linux operating system. It does not emulate windows, but translates 
> windows calls into the closest linux functional equivalent. URL: 
> http://www.winehq.com/
>
> -Rand E
>
> "But when we said that 14 newbies went blank and had to be revived 
> with ammonia salts"
>
> Per Øyvind Karlsen wrote:
>
>> wine's %description are incorrect, wine is NOT an emulator;)
>> Time to finally correct this?
>>
>> This is an ALPHA release of Wine, the MS-Windows emulator.  This is
>> still a developers release and many applications may still not work.
>>
>> This package consists of the emulator program for running windows 
>> executables.
>>
>> Wine is often updated.
>>
>>
>>
>>
>
>
>
>







Re: [Cooker] wine %description

2002-08-21 Thread Randy

Even our friendly #mandrake bot knows it's an interface layer:

  Wine: An interface between windows applications and the 
linux operating system. It does not emulate windows, but translates 
windows calls into the closest linux functional equivalent. URL: 
http://www.winehq.com/

-Rand E

"But when we said that 14 newbies went blank and had to be revived with 
ammonia salts"

Per Øyvind Karlsen wrote:
> wine's %description are incorrect, wine is NOT an emulator;)
> Time to finally correct this?
> 
> This is an ALPHA release of Wine, the MS-Windows emulator.  This is
> still a developers release and many applications may still not work.
> 
> This package consists of the emulator program for running windows 
> executables.
> 
> Wine is often updated.
> 
> 
> 
> 





Re: [Cooker] wine config

2002-08-02 Thread rcc

On Fri, 2 Aug 2002 00:06:39 +0200
Danny Tholen <[EMAIL PROTECTED]> wrote:

> > iexplorer fails (used to start, at least), no game works (had FAKK2,
> > DeusEx, RTCW running will earlier versions)
> Maybe try with new CVS version?

I'll wait for the August snapshot, shouldn't be too far away
 

> > is this gcc related?
> Interesting, what if you try -O2 instead of O3 again?

I'll do that. 20020605 showed the same behaviour so, I guess, the
compiler is to blame.
 
> Ofcourse I'm interested in the stuff you changed, although I currently
> do not have much time.

I do some more testing then

- Mark




Re: [Cooker] wine config

2002-08-01 Thread Danny Tholen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 01 August 2002 23:38, rcc wrote:

> I can run winzip, acrobat reader, even WMP (no sound though), but
> iexplorer fails (used to start, at least), no game works (had FAKK2,
> DeusEx, RTCW running will earlier versions)
Maybe try with new CVS version?

>
> is this gcc related? I think I did build 20020710 when it came out, and
> I did it on the then current cooker with gcc3.1, IIRC it did work with
> more apps than now
Interesting, what if you try -O2 instead of O3 again?

Ofcourse I'm interested in the stuff you changed, although I currently do not have 
much time.

Danny
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9SbDzaeiN+EU2vEIRArnNAJ91N/RkiFsfypcjDnsdC3kaUgl72ACcDtK7
mfqLiMDZe52VuqqWPG1vamk=
=Aq7F
-END PGP SIGNATURE-





Re: [Cooker] wine config

2002-08-01 Thread rcc


hmm, this is what I've done already:



tried to remove most of the inconsistencies, like

- mdkconf patched config that was actually never used
  instead wine.reg was copied to user's config
- use patched sample config
- tried to guess which option is more sane when
  conflicts between wine.reg and mdkconf.old
- enabled artsdrv in config WinMM section (test!)
- adjusted font paths in config

- removed redundant winelauncher.sh because like above
  winelauncher patch was applied but the resulting
  winelauncher was never used,
  instead a static winelauncher.sh was used
- use generic winelaucher
- removed config edit from winelauncher according to danny
- left startup xmessage box intact for debugging (might want to rm that)
- make winelauncher cd to dir of exe, many apps want that
- put wine-config part into winelauncher

removed all traces of wine.reg (hopefully)

- removed redhat patch
- user config cp is now handled by winelauncher
  no need to patch the server for that
- adjusted winelauncher patch
- adjusted wine-config.pl

wine.systemreg, wine.userreg

- couldn't find where they are used so I removed them
- wine creates defaults of its own at first run

win.ini, system.ini

- removed static parts for win.ini and system.ini from
  make_a_ windows_ system.sh
- use sample win.ini, system.ini

made a dir /usr/share/wine/configsamples to hold the samples



the stuff is not ready yet but if Danny is interested, I'll send the
stuff over to him

however, most of the apps that used to run under wine do not anymore.
Thing is, they even don't run with an unpatched, unmodified, pure tgz
build which used to be an infallible indicator for spec related errors.

I can run winzip, acrobat reader, even WMP (no sound though), but
iexplorer fails (used to start, at least), no game works (had FAKK2,
DeusEx, RTCW running will earlier versions)

Tons of wine warnings and an Unhandled exception at the end - and it
just barfs on me, strange

is this gcc related? I think I did build 20020710 when it came out, and
I did it on the then current cooker with gcc3.1, IIRC it did work with
more apps than now

- Mark






Re: [Cooker] wine config

2002-08-01 Thread rcc

On Wed, 31 Jul 2002 23:27:56 +0200
Danny Tholen <[EMAIL PROTECTED]> wrote:


> >You want patches to wine.reg or a new
> > wine.reg?
> Whatever. Please cc patch/file so I can renew club rpms as well.

will do. This may take a few days as I'm trying to do some cleanup (rm
wine.reg, rm redhat patch, maybe winelauncher-patch too, make
patches<->nonwinesourcefiles consistant), and of course do some quick
testing.

- Mark




Re: [Cooker] wine config

2002-07-31 Thread Danny Tholen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 31 July 2002 22:33, rcc wrote:
> thanks for the new wine rpm
>
> but the configs are out of sync with the samples. Why patch the sample
> config with mdkconf but then use wine.reg which is outdated (still lacks
> the WinMM section and other neat stuff)?
Ah..probably my fault. I didn't check whether it was still up 2 date. Although I now
understand a few errors:)
>
> Alright, I'll look into it. 
Thanx
>You want patches to wine.reg or a new
> wine.reg?
Whatever. Please cc patch/file so I can renew club rpms as well.

Danny
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9SFZiaeiN+EU2vEIRAnspAKCIqgDGEAZ8xVMUk3C/jVZiGrIbqwCeMjI9
pvzwrbd30HtyVw8XQlzAwUI=
=7zZZ
-END PGP SIGNATURE-





Re: [Cooker] wine config

2002-07-31 Thread Thierry Vignaud

rcc <[EMAIL PROTECTED]> writes:

> Alright, I'll look into it. You want patches to wine.reg or a new
> wine.reg?

patch





Re: [Cooker] wine optimization & new version

2002-07-31 Thread danny

On Wed, 31 Jul 2002, Leon Brooks wrote:
> That would be nice, it runs AutoCAD R14. The next snapshot will also clean up 
> some leaks which crash AutoCAD 2000.

Problem is, I have a report from a club-member that autocad still freezes. 
Ofcourse it could be his config file. If you have autocad please try it.

Danny






Re: [Cooker] wine optimization & new version

2002-07-31 Thread Buchan Milne

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Leon Brooks wrote:
| On Tue, 30 Jul 2002 22:42, [EMAIL PROTECTED] wrote:
|
|>It is probably to late for 9.0, but I build a srpms for wine 20020710.
|
|
| That would be nice, it runs AutoCAD R14. The next snapshot will also
clean up
| some leaks which crash AutoCAD 2000.
|
| It would be very helpful for replaciong Windows throughout a site if Mdk9
| could have that snapshot of WINE in it.
|

Only if the RPM does work. This (autocad R14) was one of the reasons
(AFAIK) the Mandrakeclub user requested it, but he hasn't been able to
get it to run Autocad yet. I haven't had the time to try yet, but I
think it would be great if this could be done. Leon, could you also test
this?

Hint hint, HP will be supporting Pro/E on linux also, it would be great
if that was on Mandrake 9.0 with a working wine so Autocad would be
available. 10-15% of our desktops are cad stations 

Buchan


- --
|Registered Linux User #182071-|
Buchan MilneMechanical Engineer, Network Manager
Cellphone * Work+27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9R7ITrJK6UGDSBKcRAiXQAKCggp9eu1j6N3gte/uKAgytx3raNACgoD12
Z3RXqTuAFVSezeBHKgLYwdU=
=c/m5
-END PGP SIGNATURE-





Re: [Cooker] wine optimization & new version

2002-07-30 Thread Leon Brooks

On Tue, 30 Jul 2002 22:42, [EMAIL PROTECTED] wrote:
> It is probably to late for 9.0, but I build a srpms for wine 20020710.

That would be nice, it runs AutoCAD R14. The next snapshot will also clean up 
some leaks which crash AutoCAD 2000.

It would be very helpful for replaciong Windows throughout a site if Mdk9 
could have that snapshot of WINE in it.

Cheers; Leon





Re: [Cooker] wine optimization & new version

2002-07-30 Thread Thierry Vignaud

<[EMAIL PROTECTED]> writes:

> It is probably to late for 9.0,

not yet

> Anyway, should I upload it or not?

yes, go on





Re: [Cooker] wine install (user group seem to miss) / new versionof wine

2002-07-16 Thread Warly

"Florent BERANGER" <[EMAIL PROTECTED]> writes:

> Wine is an implementation of the Windows Win32 and Win16
> APIs on top of X and Unix.
>
> [root@localhost cosmicflo]# urpmi wine
> Pour satisfaire les dépendances, les paquetages suivants
> vont être installés (13 Mo):
> libwine1-20020509-2mdk.i586
> wine-20020509-2mdk.i586
> Est-ce correct ? (O/n)
> installation de
> //home/cosmicflo/cooker/Mandrake/RPMS/wine-20020509-2mdk.i586.rpm
> //home/cosmicflo/cooker/Mandrake/RPMS/libwine1-20020509-2mdk.i586.rpm
>
> Preparing...
> ##
> warning: group wine does not exist - using root
> warning: group wine does not exist - using root

[...]

> warning: group wine does not exist - using root
> warning: group wine does not exist - using root
> wine
> ##
> libwine1
> ##
>
> wine group seem to missing.

wine need to be rebuild due to the new setup policy, I guess.

-- 
Warly




Re: [Cooker] wine and GL?

2002-07-01 Thread Stéphane Teletchéa

Le Lundi 1 Juillet 2002 16:12, vous avez écrit :
> On Sunday 30 June 2002 11:05 am, Gregoire Favre wrote:
> > Hello,
> >
> > I just wanted to run wine and I got:
> >
> > Couldn't open required GL library /usr/X11R6/lib/libGL.so.1.2.350!
> > wine: Unhandled exception, starting debugger...
> > err:seh:EXC_DefaultHandling Unhandled exception code c005 flags 0
> > addr 0x400f4846
> > Exit 1
>
> This is the same error I was getting with KDE apps...  I fixed it by sym
> linking libGL.so.1.2  libGL.so.1.2.305
>
> > I have up to date (well I have maybe one date late packages) rpm...
> >
> > What is to be done?
> >
> > Thank you very much,
> >
> > Greg
> > 
> > http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]

Be carefull if you use the OpenGL driver provided by nvidia, their libraries 
are in /usr/lib and so /usr/X11R6/lib/libGL.so.xxx may be a conflicting mesa 
file.
stef




Re: [Cooker] wine and GL?

2002-07-01 Thread François Pons

Jeremy Salch <[EMAIL PROTECTED]> writes:

> This is the same error I was getting with KDE apps...  I fixed it by sym 
> linking libGL.so.1.2  libGL.so.1.2.305

It still doesn't work with newer Mesa (remove symlink) ?

François.




Re: [Cooker] wine and GL?

2002-07-01 Thread Jeremy Salch

On Sunday 30 June 2002 11:05 am, Gregoire Favre wrote:
> Hello,
>
> I just wanted to run wine and I got:
>
> Couldn't open required GL library /usr/X11R6/lib/libGL.so.1.2.350!
> wine: Unhandled exception, starting debugger...
> err:seh:EXC_DefaultHandling Unhandled exception code c005 flags 0
> addr 0x400f4846
> Exit 1


This is the same error I was getting with KDE apps...  I fixed it by sym 
linking libGL.so.1.2  libGL.so.1.2.305







>
> I have up to date (well I have maybe one date late packages) rpm...
>
> What is to be done?
>
> Thank you very much,
>
>   Greg
> 
> http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]

-- 
Mr. Jeremy Salch - Data Services
Granbury.Com, Inc. 
[EMAIL PROTECTED] - email
www.granbury.com - Business Website
www.tblx.net - Personal Website




Re: [Cooker] wine and GL?

2002-07-01 Thread François Pons

Gregoire Favre <[EMAIL PROTECTED]> writes:

> > Mesa is wrong :-( Sorry...
> > 
> > I made an error of packaging, this is fixed in 2mdk.
> 
> Wouah, very speedy fix: thank you very much, it works perfactly now!

Ok, fine :-)

François.




Re: [Cooker] wine and GL?

2002-07-01 Thread Gregoire Favre

On Mon, Jul 01, 2002 at 10:18:11AM +0200, François Pons wrote:
> Gregoire Favre <[EMAIL PROTECTED]> writes:
> 
> > Couldn't open required GL library /usr/X11R6/lib/libGL.so.1.2.350!
> > wine: Unhandled exception, starting debugger...
> > err:seh:EXC_DefaultHandling Unhandled exception code c005 flags 0
> > addr 0x400f4846
> > Exit 1

> Mesa is wrong :-( Sorry...
> 
> I made an error of packaging, this is fixed in 2mdk.

Wouah, very speedy fix: thank you very much, it works perfactly now!

;-))

Grégoire

http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]




Re: [Cooker] wine and GL?

2002-07-01 Thread François Pons

Gregoire Favre <[EMAIL PROTECTED]> writes:

> Couldn't open required GL library /usr/X11R6/lib/libGL.so.1.2.350!
> wine: Unhandled exception, starting debugger...
> err:seh:EXC_DefaultHandling Unhandled exception code c005 flags 0
> addr 0x400f4846
> Exit 1
> 
> I have up to date (well I have maybe one date late packages) rpm...
> 
> What is to be done?

Mesa is wrong :-( Sorry...

I made an error of packaging, this is fixed in 2mdk.

François.




Re: [Cooker] wine and GL?

2002-07-01 Thread François Pons

Gregoire Favre <[EMAIL PROTECTED]> writes:

> Hello,

Hello,

> I just wanted to run wine and I got:
> 
> Couldn't open required GL library /usr/X11R6/lib/libGL.so.1.2.350!
> wine: Unhandled exception, starting debugger...
> err:seh:EXC_DefaultHandling Unhandled exception code c005 flags 0
> addr 0x400f4846
> Exit 1
> 
> I have up to date (well I have maybe one date late packages) rpm...

Wine may need to be rebuild against newer Mesa ? Normally it should try to open
libGL.so.1.3.403.

François.




Re: [Cooker] wine config tool for Mdk

2002-06-20 Thread Brendon Oliver

On Fri, 21 Jun 2002 13:21, Ben Reser wrote:
> On Fri, Jun 21, 2002 at 07:16:07AM +1000, Brendon Oliver wrote:
> > In a single-quoted string:  '\\'  or q{\\}
> > In a double-quoted string ""  or qq{}
>
> Actually only the second set will work.  single quotes don't have
> variable interpolation but they still do have escaped characters like
> \n.  So  is still required for single quotes.
>
> [breser@titanium breser]$ perl
> print q{\\},$/
> __END__
> \
> [breser@titanium breser]$ perl
> print q{},$/
> __END__
> \\

D'oh! That's what i get for replying before checking (note to self - put brain 
in gear first!)





Re: [Cooker] wine config tool for Mdk

2002-06-20 Thread Ben Reser

On Fri, Jun 21, 2002 at 07:16:07AM +1000, Brendon Oliver wrote:
> In a single-quoted string:'\\'  or q{\\}
> In a double-quoted string ""  or qq{}

Actually only the second set will work.  single quotes don't have
variable interpolation but they still do have escaped characters like
\n.  So  is still required for single quotes.

[breser@titanium breser]$ perl
print q{\\},$/
__END__
\
[breser@titanium breser]$ perl
print q{},$/
__END__
\\

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

We tend to see all wars through the lens of the current conflict, and we
mine history for lessons convenient to the present purpose.
- Brian Hayes




Re: [Cooker] wine config tool for Mdk

2002-06-20 Thread Brendon Oliver

On Fri, 21 Jun 2002 04:10, Florent BERANGER wrote:
>   Hi,
>
> I'm writing a wine config tool for Mdk.
> I've just a problem : how to print "\\" in perl ?

In a single-quoted string:  '\\'  or q{\\}
In a double-quoted string ""  or qq{}

Regards,

- Brendon.






Re: [Cooker] Wine doesn't work, compile with -O2

2002-03-27 Thread Leon Brooks

On Thursday 28 March 2002 07:26, andre wrote:
> On Tuesday 26 March 2002 18:02, Danny Tholen wrote:
> > On Monday 25 March 2002 21:37, you wrote:
> > > Wine as packaged by Mandrake doesn't work for me. wine notepad.exe even
> > > doesn't run. I get this with the version in 8.2 or when i compile it
> > > myself. But if i add optflags: i586 -O2 -pipe -mcpu=i586 -march=i586 to
> > > my .rpmrc file and compile it than wine does work. So could you change
> > > the spec file to force a -O2 build

> > Maybe, you can also try gcc 3.0.4, it solved a couple of problems for me
> > (now using wineX i686 -O3 )

> Tried that too. Does not work either. Only O2 seems to work

Maybe a CPU-specific compiler bug?

Cheers; Leon




Re: [Cooker] Wine doesn't work, compile with -O2

2002-03-27 Thread andre

On Tuesday 26 March 2002 18:02, Danny Tholen wrote:
> Maybe, you can also try gcc 3.0.4, it solved a couple of problems for me
> (now using wineX i686 -O3 )
>
> Danny
>
> On Monday 25 March 2002 21:37, you wrote:
> > Wine as packaged by Mandrake doesn't work for me. wine notepad.exe even
> > doesn't run. I get this with the version in 8.2 or when i compile it
> > myself. But if i add optflags: i586 -O2 -pipe -mcpu=i586 -march=i586 to
> > my .rpmrc file and compile it than wine does work. So could you change
> > the spec file to force a -O2 build
>

Tried that too. Does not work either. Only O2 seems to work




Re: [Cooker] Wine doesn't work, compile with -O2

2002-03-27 Thread Danny Tholen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Maybe, you can also try gcc 3.0.4, it solved a couple of problems for me (now using 
wineX i686 -O3 )

Danny


On Monday 25 March 2002 21:37, you wrote:
> Wine as packaged by Mandrake doesn't work for me. wine notepad.exe even
> doesn't run. I get this with the version in 8.2 or when i compile it
> myself. But if i add optflags: i586 -O2 -pipe -mcpu=i586 -march=i586 to my
> .rpmrc file and compile it than wine does work. So could you change the
> spec file to force a -O2 build

- - -- 
"Arthur yawed wildly as his skin tried to jump one way and 
his skeleton the other, whilst his brain tried to work out 
which of his ears it most wanted to crawl out of.
`Bet you weren't expecting to see me again,' said the 
monster, which Arthur couldn't help thinking was a strange 
remark for it to make, seeing as he had never met the 
creature before. He could tell that he hadn't met the 
creature before from the simple fact that he was able to 
sleep at nights." 


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8oKmnaeiN+EU2vEIRAhnsAJ9GAh1j9tX6y/9jrR1Q+O1RENHeswCeLB5y
9dgHkeHgiJxRHKGoAHdjM1g=
=Na2B
-END PGP SIGNATURE-




Re: [Cooker] Wine out of the box problems...

2002-03-20 Thread avblokland

Op woensdag 20 maart 2002 22:39, schreef u:
> When I try to use wine (from the mandrake 8.2 rpm) to start a Windows
> program I am receiving the following error: err:module:map_image Could not
> map section .text, file probably truncated err:module:PE_fixup_imports
> Module (file) shlwapi.dll (which is needed by shell32.dll) not found
> err:module:load_library can't load shell32.dll
> wine: Unhandled exception, starting debugger...
> err:seh:EXC_DefaultHandling Unhandled exception code c005 flags 0 addr
> 0x402b0d77
>
> According to  http://www.winehq.com/hypermail/wine-devel/2001/06/0203.html
> this could be because wine was compiled with -O3 optimistations...
>
> Can anyone shed any light on this?
>
>
>
> 2,000,000,000 Web Pages--you only need 1. Save time with My Lycos.
> http://my.lycos.com

MDK's wine doesn't work since atleast 8.0 I doubt it ever will




Re: [Cooker] wine .....??

2002-02-28 Thread Buchan Milne

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David BAUDENS wrote:
| On Wednesday 27 February 2002 18:23, you wrote:
|
|>Op wo 27-02-2002, om 17:27 schreef Michel Clasquin:
|>
|>>I run Free Agent on it. Sometimes it takes a couple of minutes (!)
|>>to start up though, while it churns through the fonts directory
|>>
|>>If you have problems, then get rid of Mandrake's wine and use
|>>Codeweavers' instead.
|>>
|>>
|>>>It works on some stuff for me.  It crashes on the
|>>>_beginthread() function if anything uses that.
|>>>
|>>>
|Have anybody seen WINE work on the 8.2 ?
|
|I could not even have the notepad.exe working. Wine
|always crashes.
|
|>The version of wine mandrake ships has been bad for atleast a year
|>now. Can we have a version that works for ones. If notepad can't even
|>run than why include it
|>
|
| Patches are welcome. I have unfortunaly not time to fix it at present
| time.
|
| Maybe can you ask Chmouel, he packaged latest releases.
|
|

One of the requests on MF was to have wine compiled with GL support, so
that people can play Counter-strike without having to use a different
Wine ...

I've never had enough time to investigate wine, but being able to play
counter-strike with the win32 boys under Mandrake with minimal setup
would be cool.

Buchan

- --
|Registered Linux User #182071-|
Buchan MilneMechanical Engineer, Network Manager
Cellphone * Work+27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key   http://ranger.dnsalias.com/gpg.key
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8fk+1rJK6UGDSBKcRAsceAJ97TQ2za1DAAkWtekoXOBjwJ/PSEQCeN9nb
/IYiE79peUUcqusXc8yq8uY=
=0Z0T
-END PGP SIGNATURE-





Re: [Cooker] wine .....??

2002-02-27 Thread Michel Clasquin

On Thursday 28 February 2002 00:17, Tim McKenzie wrote:

> Why use Free Agent? PAN is a much better newsgroup program if you ask
> me. Give it a shot if you haven't already.

Been there, done that, got the crash damage to prove it. 

Nothing serious, actually, just don't like the "feel" of the app.

-- 
Michel Clasquin, D Litt et Phil (Unisa)
[EMAIL PROTECTED]/unisa.ac.za   http://www.geocities.com/clasqm
This message was posted from a Microsoft-free PC

... Linux users and the women who chase them - next Oprah!






Re: [Cooker] wine .....??

2002-02-27 Thread Tim McKenzie


> > Op wo 27-02-2002, om 17:27 schreef Michel Clasquin:
> > > I run Free Agent on it. Sometimes it takes a couple of minutes (!)
> > > to start up though, while it churns through the fonts directory
> > >

Why use Free Agent? PAN is a much better newsgroup program if you ask me.
Give it a shot if you haven't already.






Re: [Cooker] wine .....??

2002-02-27 Thread David BAUDENS

On Wednesday 27 February 2002 18:23, you wrote:
> Op wo 27-02-2002, om 17:27 schreef Michel Clasquin:
> > I run Free Agent on it. Sometimes it takes a couple of minutes (!)
> > to start up though, while it churns through the fonts directory
> >
> > If you have problems, then get rid of Mandrake's wine and use
> > Codeweavers' instead.
> >
> > > It works on some stuff for me.  It crashes on the
> > > _beginthread() function if anything uses that.
> > >
> > > > Have anybody seen WINE work on the 8.2 ?
> > > >
> > > > I could not even have the notepad.exe working. Wine
> > > > always crashes.
>
> The version of wine mandrake ships has been bad for atleast a year
> now. Can we have a version that works for ones. If notepad can't even
> run than why include it

Patches are welcome. I have unfortunaly not time to fix it at present 
time.

Maybe can you ask Chmouel, he packaged latest releases.

-- 
David BAUDENS
MandrakeSoft - http://www.mandrakesoft.com




Re: [Cooker] wine .....??

2002-02-27 Thread andre

Op wo 27-02-2002, om 17:27 schreef Michel Clasquin:
> I run Free Agent on it. Sometimes it takes a couple of minutes (!) to 
> start up though, while it churns through the fonts directory
> 
> If you have problems, then get rid of Mandrake's wine and use Codeweavers' 
> instead.
> 
> > It works on some stuff for me.  It crashes on the
> > _beginthread() function if anything uses that.
> >
> > > Have anybody seen WINE work on the 8.2 ?
> > >
> > > I could not even have the notepad.exe working. Wine
> > > always crashes.
>
The version of wine mandrake ships has been bad for atleast a year now.
Can we have a version that works for ones. If notepad can't even run
than why include it





Re: [Cooker] wine .....??

2002-02-27 Thread Michel Clasquin

I run Free Agent on it. Sometimes it takes a couple of minutes (!) to 
start up though, while it churns through the fonts directory

If you have problems, then get rid of Mandrake's wine and use Codeweavers' 
instead.

> It works on some stuff for me.  It crashes on the
> _beginthread() function if anything uses that.
>
> > Have anybody seen WINE work on the 8.2 ?
> >
> > I could not even have the notepad.exe working. Wine
> > always crashes.

-- 
Michel Clasquin, D Litt et Phil (Unisa)
[EMAIL PROTECTED]/unisa.ac.za   http://www.geocities.com/clasqm
This message was posted from a Microsoft-free PC

... Linux users and the women who chase them - next Oprah!






Re: [Cooker] wine .....??

2002-02-27 Thread David Walser

It works on some stuff for me.  It crashes on the
_beginthread() function if anything uses that.

--- Christophe Combelles
<[EMAIL PROTECTED]> wrote:
> Have anybody seen WINE work on the 8.2 ?
> 
> I could not even have the notepad.exe working. Wine
> always crashes.
> 
> 

__
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com




  1   2   >