On 01.12.2007 16:20, Vitaly Lipatov wrote:
> UuidToStringW from legacy (DCOM95) rpcrt4.dll returns RPC_S_CANNOT_SUPPORT,
> works only ANSI version.
>
> Changelog:
> Add return codes checking for UuidCreate and UuidToStringW
Do users still commonly install that legacy DCOM? If so, it may be
bette
On Dec 2, 2007 9:31 PM, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote:
>
> On Dec 3, 2007 5:02 AM, James Hawkins <[EMAIL PROTECTED]> wrote:
> >
> > On Dec 2, 2007 5:22 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> > > Hey Louis,
> > > Focht is using a pseudonym, and I believe it's Wine policy to
> > >
On Dec 3, 2007 5:02 AM, James Hawkins <[EMAIL PROTECTED]> wrote:
>
> On Dec 2, 2007 5:22 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> > Hey Louis,
> > Focht is using a pseudonym, and I believe it's Wine policy to
> > not accept patches without real names.
> > His patches should be used as guides only
On Dec 2, 2007 9:07 PM, Aric Stewart <[EMAIL PROTECTED]> wrote:
> ---
> programs/uninstaller/main.c | 34 +++---
> 1 files changed, 23 insertions(+), 11 deletions(-)
>
I'm not saying that this patch shouldn't be accepted, but I want to
remark that at some point, al
On Sun, 2 Dec 2007, Alexandre Julliard wrote:
> I'm aware of that, but the purpose of having these warnings is to spot
> bugs, and when you find a bug you have to fix it. Yes, the checks
> currently don't work, so they should be made to work, not removed. As
> the comment says, you have to check th
On Dec 2, 2007 5:22 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Hey Louis,
> Focht is using a pseudonym, and I believe it's Wine policy to
> not accept patches without real names.
> His patches should be used as guides only,
> and should not be reposted to wine-patches,
> until such time as he declo
Hey Louis,
Focht is using a pseudonym, and I believe it's Wine policy to
not accept patches without real names.
His patches should be used as guides only,
and should not be reposted to wine-patches,
until such time as he decloaks. If he doesn't
want to decloak, I think we can't use his patches.
I
Gabriel Sailer <[EMAIL PROTECTED]> writes:
> I used the same WinXX Application with wine for a few people (not
> parallel but serialized) in the same group and gave the WINEPREFIX dir
> (and all subdirectories and files) to this group.
>
> Is it really nesseccary to use this protection? Did i get
Gerald Pfeifer <[EMAIL PROTECTED]> writes:
> If we want to add some input checking, I assume you would like to
> check that these values are not too large? (They cannot be negative,
> so the only range checking we can do is on the upper end.) How should
> this look like? Any specific upper bou
On Mon, 19 Nov 2007, Alexandre Julliard wrote:
>> I had expected this comment for a different patch of mine. In
>> dlls/gdi32/enhmetafile.c we are just reading existing records,
>> so I'm not sure what you have in mind here?
> The records usually come from an external file, so they have to be
> v
Hello,
after an update of wine on my Debian etch i got the error:
libwine: Refuse to use a WINEPREFIX dir owned by a different user.
I found that there is a patch in Wine release 0.9.49 but i did not found
why this patch is needed. Are the linux access rights not secure enough?
I have the full a
On Dec 2, 2007 9:16 AM, Francois Gouget <[EMAIL PROTECTED]> wrote:
> How does Gnome/KDE know which WINEPREFIX to use for foo.lnk? Why should
> it be '~/.wine' rather than '~/.wine-steam', '~/.wine-office' or
> something else?
Maybe rather than storying the information in memory and creating it
at
On Sat, 1 Dec 2007, Steven Edwards wrote:
[...]
> What this means is that on logon or logoff the WM would call our
> function and generate these fake Shortcuts for the *.lnk files by
> running a copy of winepath after calling the Wine shelllink processor.
> The results of winepath would translate '
On Thu, 29 Nov 2007, Alexandre Julliard wrote:
>> I checked again and if we don't address this we'll get two new warnings
>> issues in a default build with GCC 4.3. How does the patch below
>> look?
> Not good, it adds noise to the code for no good reason. Why would gcc
> complain about that one?
On Sun, Dec 02, 2007 at 01:01:04PM +0100, Pavel Troller wrote:
> > James McKenzie wrote:
> > > Please also be aware that Wine will NOT build properly with any version
> > > of gcc 4.0
> > >
> >
> > Can you elaborate? I have been building wine with gcc-4.* since forever
> > and never had any probl
> James McKenzie wrote:
> > Please also be aware that Wine will NOT build properly with any version
> > of gcc 4.0
> >
>
> Can you elaborate? I have been building wine with gcc-4.* since forever
> and never had any problems with that. Currently I'm using gcc 4.2.2
> (Gentoo 4.2.2 p1.0).
>
> tom
James McKenzie wrote:
> Please also be aware that Wine will NOT build properly with any version
> of gcc 4.0
>
Can you elaborate? I have been building wine with gcc-4.* since forever
and never had any problems with that. Currently I'm using gcc 4.2.2
(Gentoo 4.2.2 p1.0).
tom
17 matches
Mail list logo