On Sun, 16 Dec 2007, James McKenzie wrote:
> David Griffith wrote:
> > I'm trying to run Myst (masterpiece edition). By upgrading Wine to .51,
> > I've gotten the install to finish without complaint. When I attempt to
> > run Myst, the following is written to the terminal:
> >
> > $ wine Myst.ex
> > Dmitry Timoshkov wrote:
> > >
> > > Users are not supposed to set a category the bug belongs to, this requires
> > > an investigation and knowledge of a developer. Personally I'd prefer to
> > > have
> > > "default" in the list instead of "wine-misc".
> > >
> > >
> > Better choice: Unknown or
James, check your reply settings. You have done this several times - do not
bring wine-user discussions to wine-devel mailing list.
Vitaliy.
James McKenzie wrote:
> David Griffith wrote:
>> I'm trying to run Myst (masterpiece edition). By upgrading Wine to .51,
>> I've gotten the install to fin
On Dec 16, 2007 7:53 PM, James McKenzie <[EMAIL PROTECTED]> wrote:
>
>
> Original Message
> Subject:Re: New bugzilla components.
> Date: Sun, 16 Dec 2007 18:52:40 -0700
> From: James McKenzie <[EMAIL PROTECTED]>
> To: Dmitry Timoshkov <[EMAIL PROTECTED]>
> Referenc
Original Message
Subject:Re: New bugzilla components.
Date: Sun, 16 Dec 2007 18:52:40 -0700
From: James McKenzie <[EMAIL PROTECTED]>
To: Dmitry Timoshkov <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTE
David Griffith wrote:
> I'm trying to run Myst (masterpiece edition). By upgrading Wine to .51,
> I've gotten the install to finish without complaint. When I attempt to
> run Myst, the following is written to the terminal:
>
> $ wine Myst.exe
> fixme:mixer:ALSA_MixerInit No master control found o
Reijo T Sund wrote:
> Dear Wine-experts,
>
> I've tested the functionality of simple CUI-applications with
> wineconsole (Wine-0.9.50, Ubuntu 7.10). Somewhat surprisingly,
> there seems to be numerous major flaws in the current
> implementation.
>
> The best (worst?) example is the widely distribut
On Dec 16, 2007 4:08 PM, Kai Blin <[EMAIL PROTECTED]> wrote:
> On Sunday 16 December 2007 22:47:23 James Hawkins wrote:
>
> > ws2_32 or wsock32, or both, depending on the existing bugs.
>
> Given that wsock32 forwards over 90% of the calls to ws2_32, let's go for that
> one then.
>
> > > Coming to
On Sunday 16 December 2007 22:47:23 James Hawkins wrote:
> ws2_32 or wsock32, or both, depending on the existing bugs.
Given that wsock32 forwards over 90% of the calls to ws2_32, let's go for that
one then.
> > Coming to think about that, if we're fine to add more categories for
> > things lik
On Dec 16, 2007 3:37 PM, Kai Blin <[EMAIL PROTECTED]> wrote:
> On Sunday 16 December 2007 21:14:16 James Hawkins wrote:
>
> > Ok, I'll start off the list. This is a first draft, open to changes
> > and discussion. Entries with a (?) means I'm not sure.
> >
> > Components:
> [...]
> > wine-net ->
Hi.
Stefan Dösinger wrote:
> Am Samstag, 15. Dezember 2007 12:19:36 schrieb Alexander Dorofeyev:
>> This seems to be specific to front buffer. Maybe
>> glFlush really should be called in BltOverride (or clearing subroutine) if
>> the target is front buffer?
> Yes, glFlush() has to be called when w
On Sunday 16 December 2007 21:14:16 James Hawkins wrote:
> Ok, I'll start off the list. This is a first draft, open to changes
> and discussion. Entries with a (?) means I'm not sure.
>
> Components:
[...]
> wine-net ->
If you delete that one, we definitely need a "winsock" component. Or ws2_32.
On Dec 16, 2007 6:20 AM, Jan Zerebecki <[EMAIL PROTECTED]> wrote:
>
> For me with this renaming is important that at least from the
> description it should then be absolutely clear what goes into a
> component and what not (for a developer).
>
>
> On Sat, Dec 15, 2007 at 09:27:52PM -0700, Vitaliy M
> "Roderick Colenbrander" <[EMAIL PROTECTED]> wrote:
>
> > This patch creates an X11 window for the client area. The code is
> inspired
> > by old x11drv of which even a few pieces got copied over. Further Chris
> > Robinson assisted with positioning issues.
> >
> > After this patch most remnants
Am Montag, 17. Dezember 2007 04:56:09 schrieb Alexander Dorofeyev:
> ---
>dlls/wined3d/device.c |2 +-
>1 files changed, 1 insertions(+), 1 deletions(-)
I actually removed a bunch of links like that some time ago, I think we can
just remove that as well. The source isn't a link collecti
On 17/12/2007, Alexander Dorofeyev <[EMAIL PROTECTED]> wrote:
> ---
>dlls/wined3d/device.c |2 +-
>1 files changed, 1 insertions(+), 1 deletions(-)
>
MSDN URLs should generally just be removed. They change too often to
be of any use anyway.
Robert Shearman wrote:
> (For example, consult Jacek before creating separate mshtml, shdocvw and
> urlmon components.)
>
We currently have wine-shdocvw and wine-urlmon. That's fine for me and I
don't think we want to split shdocvw to mshtml and shdocvw. Although the
current name may be confus
"Roderick Colenbrander" <[EMAIL PROTECTED]> wrote:
> This patch creates an X11 window for the client area. The code is inspired
> by old x11drv of which even a few pieces got copied over. Further Chris
> Robinson assisted with positioning issues.
>
> After this patch most remnants of bug 2398 sho
Dmitry Timoshkov wrote:
> "Robert Shearman" <[EMAIL PROTECTED]> wrote:
>
>>> Is it possible to make it 64-bit and Wine/Windows compatible by using
>>> ULONG_PTR instead of long?
>>
>> At the moment, widl doesn't support generating 64-bit compatible
>> client, server and proxy code so doing so woul
On So, 2007-12-16 at 13:46 +0800, Dmitry Timoshkov wrote:
> "Vitaliy Margolen" <[EMAIL PROTECTED]> wrote:
> > Unless we want to list most of the
> > subsystems in keywords, that span small parts of multiple dlls.
>
> In the vast majority of cases a bug belongs to a particular DLL, not
> a group
"Robert Shearman" <[EMAIL PROTECTED]> wrote:
>> Is it possible to make it 64-bit and Wine/Windows compatible by using
>> ULONG_PTR instead of long?
>
> At the moment, widl doesn't support generating 64-bit compatible client,
> server and proxy code so doing so would be useless. FWIW, MIDL output
For me with this renaming is important that at least from the
description it should then be absolutely clear what goes into a
component and what not (for a developer).
On Sat, Dec 15, 2007 at 09:27:52PM -0700, Vitaliy Margolen wrote:
> > What's happened to the proposal to remove the wine- prefix
Dmitry Timoshkov wrote:
> "Robert Shearman" <[EMAIL PROTECTED]> wrote:
>
>> This isn't done in MIDL, but I think it's desirable both for
>> silencing Valgrind warnings and for security purposes (fixes
>> potential for leaking information to remote computers or other
>> processes).
>
>> +prin
Dmitry Timoshkov wrote:
> Rename wine-ole -> ole32
>
> Add oleaut32, rpcrt4
>
Currently, all of the above are filed in wine-ole and I don't have a
problem with that. Since a common question by our bugzilla advocates is
"does installing DCOM fix the bug?" then this makes sense.
Care needs to
On Sunday 16 December 2007 11:18:11 Dmitry Timoshkov wrote:
> "Kai Blin" <[EMAIL PROTECTED]> wrote:
> > There's a category for secur32, called wine-sspi for now. As Microsoft
> > calls the whole GSSAPI clone implemented in secur32 and possibly
> > additional dlls SSPI, it makes sense to call the bu
"Kai Blin" <[EMAIL PROTECTED]> wrote:
> There's a category for secur32, called wine-sspi for now. As Microsoft calls
> the whole GSSAPI clone implemented in secur32 and possibly additional dlls
> SSPI, it makes sense to call the bugzilla component that way.
sspi consists of at least a host and
"Kai Blin" <[EMAIL PROTECTED]> wrote:
> Is there an inherent advantage of splitting wine-net into wininet and winsock?
> (Apart from probably getting less .NET bugs filed in the category? ;) )
wininet and winsock are two absolutely different layers of very different
functionality.
> I'm not sure
- Original Message -
*From:* Adelle Hartley <[EMAIL PROTECTED]>
*To:* wine-devel@winehq.org
*Sent:* Mon, Dec 10 2007 at 19:06 +0200
*Subject:* COM
> Hi all,
>
> I have some COM DLLs which work fine with VB6 applications on wine.
>
> Is it possible to instantiate a windowsy COM object from
On Sunday 16 December 2007 07:08:57 James Hawkins wrote:
> As Dmitry already said: ntdl, oleaut32, rpcrt4. Searching through
> bugzilla: wininet, wintrust, secur32, advpack, hhctrl, imagehlp,
> mshtml, shlwapi, urlmon. There are probably more, but that's a good
> starter list.
There's a category
On Sunday 16 December 2007 05:34:18 James Hawkins wrote:
> * Remove the following components:
> - wine-rebar
> - wine-gui
> - wine-multimedia
> - wine-net
> - wine-patches
> - test
>
> Any bug report listed under the components that are removed would have
> to be set to wine-misc and e
30 matches
Mail list logo
