> This is related to the problem, but there needs to be at least one
> other bugzilla super-admin. The only active bugzilla admin I know of
> is Jan Zerebecki, and he is not online enough to keep up with the pace
> of wine development, especially this close to the 1.0 release. Who is
> in ch
On Thu, Mar 20, 2008 at 9:40 PM, <[EMAIL PROTECTED]> wrote:
> http://bugs.winehq.org/show_bug.cgi?id=12131
>
>Summary: Need a 1.2.0 milestone
>Product: WineHQ Bugzilla
>Version: unspecified
> Platform: Other
> OS/Version: other
> St
On Thu, Mar 20, 2008 at 8:31 PM, James McKenzie
<[EMAIL PROTECTED]> wrote:
>
> Dan Kegel wrote:
> > What would break if we made XP the default windows version in Wine?
> >
> > I've run into several apps that fail to install unless I change that
> > setting lately...
> >
> >
> >
> +1 to maki
Austin English wrote:
> On Thu, Mar 20, 2008 at 6:40 PM, Lei Zhang <[EMAIL PROTECTED]> wrote:
>> On Ubuntu, you cannot even login as root, they'd have to run "sudo
>> wine". On many other distros, if you login as root, you'll get a
>> dialog warning you about it, and the desktop background will
Dan Kegel wrote:
> What would break if we made XP the default windows version in Wine?
>
> I've run into several apps that fail to install unless I change that
> setting lately...
>
>
>
+1 to making XP the default. Windows98 and Windows2000 are no longer
supported by Microsoft, leaving XP as t
> Henri once suggested making the shader_backend_t structure a COM object, that
> is created and destroyed by the device. That would make the state of the data
> it manages clearer(belongs to the shader object), though it would add some
> stuff we don't need, like the IUnknown parts, refcountin
On Thu, Mar 20, 2008 at 6:40 PM, Lei Zhang <[EMAIL PROTECTED]> wrote:
> On Ubuntu, you cannot even login as root, they'd have to run "sudo
> wine". On many other distros, if you login as root, you'll get a
> dialog warning you about it, and the desktop background will be bright
> red. Are peopl
On Thu, Mar 20, 2008 at 4:28 PM, Marcus Meissner <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 20, 2008 at 03:41:00PM -0700, Dan Kegel wrote:
> > On Thu, Mar 20, 2008 at 3:28 PM, Alexandre Julliard <[EMAIL PROTECTED]>
> wrote:
> > > I hope you are not seriously suggesting that we do this...
> >
>
On Thu, Mar 20, 2008 at 4:28 PM, Marcus Meissner <[EMAIL PROTECTED]> wrote:
> > Many, many newbies are running wine as root without
> > really needing to.
>
> QUestion is ... Why do they do this?
They don't know any better...
On Thu, Mar 20, 2008 at 03:41:00PM -0700, Dan Kegel wrote:
> On Thu, Mar 20, 2008 at 3:28 PM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> > I hope you are not seriously suggesting that we do this...
>
> Seriously.
>
> > I'm not at all convinced that we need even a warning, there doesn't see
On Thu, Mar 20, 2008 at 4:11 PM, Christopher Buck <[EMAIL PROTECTED]> wrote:
> Strictly speaking, running as root is a OS level issue, not a wine
> issue.
Wine is a newbie magnet, though; it's what pulls a lot of
Windows users onto this OS. So it's kind of our fault,
it's best if we clean up the
Strictly speaking, running as root is a OS level issue, not a wine
issue. That being said, wine is being friendly if it notes the
possible issues with running as root. That being said, letting the
user know the bypass switch or when wine doesn't start up right away
is also friendly.
Perhaps we
On Thu, Mar 20, 2008 at 3:55 PM, Michael Stefaniuc <[EMAIL PROTECTED]> wrote:
> >> If we really need to have something then it should be at most a one-time
> >> warning (in a message box so people have a chance to see it) at
> >> wineprefixcreate time, with an easy way to disable it.
> >
>
Dan Kegel wrote:
> On Thu, Mar 20, 2008 at 3:28 PM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
>> I hope you are not seriously suggesting that we do this...
>
> Seriously.
>
>> I'm not at all convinced that we need even a warning, there doesn't seem
>> to be much concrete evidence that runn
On Thu, Mar 20, 2008 at 3:28 PM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> I hope you are not seriously suggesting that we do this...
Seriously.
> I'm not at all convinced that we need even a warning, there doesn't seem
> to be much concrete evidence that running as root is actually harm
"Dan Kegel" <[EMAIL PROTECTED]> writes:
> +if (!strcmp( argv[1], "--nosanitycheck" ))
> +{
> +perform_sanity_check = 0;
> +
> +/* Delete --nosanitycheck from argv */
> +
> +/* Size of argv before is argc +1 for argv[0], +1 for argv[argc]=0 */
> +/* Size of a
> [Somebody is already working on reg.exe.]
> Does that mean the project is no longer free for grabs?
It depends. The SoC staff frown on joint projects, but
it's possible. I would suggest looking at other useful
commandline utilities (see e.g. the list at
http://commandwindows.com ) and check wi
Hi Michael,
2008/3/20, Michael Stefaniuc <[EMAIL PROTECTED]>:
> This looks like an cut'n'paste error to me.
>
> -EnterCriticalSection(This->crst);
> +LeaveCriticalSection(This->crst);
Many thanks for catching that!
Cheers,
Maarten.
Any reason this patch wasn't applied?
http://www.winehq.org/pipermail/wine-patches/2008-March/051747.html
Greetings,
I've noticed Wine is participating in GSoC and one of the ideas is an OSS
implementation of reg.exe. I'm very interested in working on this project,
but looking around the list it seems the stub was posted only a few days
ago, and the author is willing to work on it in the future (I be
I think he's a windows developer, comfortable mostly
with IDEs like Visual C++. He'd like to build winecfg
as a .exe on Wine, test it there, and also try running
it on Windows (at least part of it should kinda work there).
Here's what I told him:
On Ubuntu, 'sudo apt-get install mingw' should in
Am Donnerstag, 20. März 2008 16:05:51 schrieb [EMAIL PROTECTED]:
> Question 1: I need to mess about with winecfg. I want to compile only
> winecfg.exe so I can immediately see when I made a mistake /rather than
> trying to build the entire source of wine/. What's the console command(s) I
> need to
On Thu, Mar 20, 2008 at 9:13 AM, Marcel Partap <[EMAIL PROTECTED]> wrote:
> > but it seems I didn't quite understand the rules of
> > the dev on wine/ or on linux for that matter :(
> > I need someone to show me the ropes...
> > Basically, The Toolbox.
> Last year THAT was my biggest initial p
> but it seems I didn't quite understand the rules of
> the dev on wine/ or on linux for that matter :(
> I need someone to show me the ropes...
> Basically, The Toolbox.
Last year THAT was my biggest initial problem as well. There are really a few
caveats you will most
probably hit (seems to m
Folks, I'm working with Dan Kegel on the idea of a winecfg/control panel
merger; I did a .cpl or two a few days ago, but it seems I didn't quite
understand the rules of the dev on wine/ or on linux for that matter :(
I need someone to show me the ropes...
Basically, The Toolbox.
Question 1: I ne
Am Donnerstag, 20. März 2008 15:26:07 schrieb H. Verbeet:
> On 20/03/2008, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> > On IRC I think you once mentioned making the shader backend an object,
> > and since we don't have a C++ compiler anyway I concluded COM. (That was
> > a
>
> In essence an objec
> Hi,
>
> I have read many valuable information from Detlef, Roderick and Stefan
> about this topic. Thank you very much for this so far!
>
> e.g.
> http://wiki.winehq.org/DirectDraw
> http://wiki.winehq.org/UsefulRegistryKeys
>
> and some comments in bugzilla.
>
> But it is still very har
Hi,
I'm looking into bug 12030 (http://bugs.winehq.org/show_bug.cgi?id=12030). The
driver service is not installed by our InstallHinfSection function.
I'm first trying to come up with a test before even trying to do the
implementation. The question I'm having is whether I should be doing the te
On 20/03/2008, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> On IRC I think you once mentioned making the shader backend an object, and
> since we don't have a C++ compiler anyway I concluded COM. (That was a
In essence an object is just a call table with some data, you don't
really need a C++ comp
Am Donnerstag, 20. März 2008 14:17:56 schrieb H. Verbeet:
> On 20/03/2008, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> > Henri once suggested making the shader_backend_t structure a COM object,
> > that is created and destroyed by the device. That would make the state of
> > the data
>
> I never m
Hi,
I have read many valuable information from Detlef, Roderick and Stefan
about this topic. Thank you very much for this so far!
e.g.
http://wiki.winehq.org/DirectDraw
http://wiki.winehq.org/UsefulRegistryKeys
and some comments in bugzilla.
But it is still very hard for me to tell what I
On 20/03/2008, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> Henri once suggested making the shader_backend_t structure a COM object, that
> is created and destroyed by the device. That would make the state of the data
I never mentioned COM there.
Am Donnerstag, 20. März 2008 05:51:23 schrieb Ivan Gyurdiev:
> It looks to me as if shader_backend is being overloaded for many
> different purposes that are not really related to each other. Typical
> object structure is to group related data an functions in one place, but
> what's happening in sh
Ove Kaaven <[EMAIL PROTECTED]> writes:
> Alexandre Julliard skrev:
>> All other Windows compilers have to respect the ABI as defined by MSVC,
>> if only because all the system dlls are built with MSVC.
>
> Well, we don't really know how the system dlls are built, they could
> have different compil
Alexandre Julliard skrev:
> Ove Kaaven <[EMAIL PROTECTED]> writes:
>
>> Alexandre Julliard skrev:
>>> It depends if MSVC respects that ABI constraint or not.
>> Only if you want to make Wine depend on the compiler used to compile
>> Windows applications. Not all of them are called "MSVC". I know
>
Martin Hinner wrote:
> I am solving problem how to get one Win32 app (for which I have
> source code) running under Wine. The biggest issue is drivers and
> ioctls. Linux has driver support for what we need and provides similar
> ioctls for some stuff, but it differs from Windows.
What drivers an
Ove Kaaven <[EMAIL PROTECTED]> writes:
> Alexandre Julliard skrev:
>> It depends if MSVC respects that ABI constraint or not.
>
> Only if you want to make Wine depend on the compiler used to compile
> Windows applications. Not all of them are called "MSVC". I know
> Borland Delphi is used by some
Alexandre Julliard skrev:
> Ove Kaaven <[EMAIL PROTECTED]> writes:
>
>> But that's a bit of a different issue, unrelated to the kernel flaw. I
>> was only talking about that flaw. I kind of tried to clarify that in
>> my next followup... oh well.
>
> Sure, it has nothing to do with the kernel bug
Ove Kaaven <[EMAIL PROTECTED]> writes:
> When it comes to ABI issues with MSVC code, the question isn't so much
> whether it uses cld, but what Windows does when throwing
> exceptions. Does Windows clear the DF when it calls exception
> handlers? If not, then there's hardly any Wine bug here (that
Ove Kaaven <[EMAIL PROTECTED]> writes:
> But that's a bit of a different issue, unrelated to the kernel flaw. I
> was only talking about that flaw. I kind of tried to clarify that in
> my next followup... oh well.
Sure, it has nothing to do with the kernel bug, except that it points to
a similar
On Wed, 19 Mar 2008, Austin English wrote:
[...]
> Using a program like AutoHotkey to install a program and test its
> features would be a better route IMHO.
I agree but I'm not sure AutoHotKey is quite ready yet. But I think that
getting a robust graphical testing environment would be hugely
be
On 19/03/2008, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Sounds good to me!
> I'm cc'ing wine-devel; if nobody objects by Friday, go ahead and do it.
The thing to keep in mind is: with the new forum gateway, wine-users
is getting a flood of regular non-geek users - the sort of people who
are not
Dimi Paun wrote:
> On Wed, 2008-03-19 at 23:57 +0100, Michael Stefaniuc wrote:
>> +LTEXT "O îeșire sau oprire simulată este în curs dar
>> acest proces nu răspunde.",
>
> This should be "O ieșire" not "O îeșire", no?
Thanks man, I've resent it!
bye
michael
Alexandre Julliard skrev:
> Ove Kaaven <[EMAIL PROTECTED]> writes:
>
>> Francois Gouget skrev:
>>> Does anyone know if MSVC does a cld in the right places?
>> Maybe. But it hardly matters. Only GCC-generated code is affected. The
>> problem might then show up in Wine signal/exception handling. Th
On 3/20/08, Marcus Meissner <[EMAIL PROTECTED]> wrote:
> Best bet is to just check for the registry key HKLM\Software\Wine
I know also other methods, this is not a problem, I just wanted to ask
if it's possible to get some "official wine api" for all this stuff.
> > - load native Linux library a
On Thu, Mar 20, 2008 at 10:26:20AM +0100, Martin Hinner wrote:
> Hi,
>
>I am solving problem how to get one Win32 app (for which I have
> source code) running under Wine. The biggest issue is drivers and
> ioctls. Linux has driver support for what we need and provides similar
> ioctls for some
Ove Kaaven <[EMAIL PROTECTED]> writes:
> Francois Gouget skrev:
>> Does anyone know if MSVC does a cld in the right places?
>
> Maybe. But it hardly matters. Only GCC-generated code is affected. The
> problem might then show up in Wine signal/exception handling. Things
> like, say, copying the C
Hi,
I am solving problem how to get one Win32 app (for which I have
source code) running under Wine. The biggest issue is drivers and
ioctls. Linux has driver support for what we need and provides similar
ioctls for some stuff, but it differs from Windows.
The difference is *so big* that I w
"Andrew Riedi" <[EMAIL PROTECTED]> wrote:
> +int reg_lstrncmpiW(const WCHAR *s1, const WCHAR *s2, size_t n)
CompareString is better.
> +const WCHAR hkcrW[] = {'h','k','c','r',0};
> +const WCHAR hkcuW[] = {'h','k','c','u',0};
> +const WCHAR hklmW[] = {'h','k','l','m',0};
> +const
Ove Kaaven skrev:
>> Does anyone know if MSVC does a cld in the right places?
>
> Maybe. But it hardly matters. Only GCC-generated code is affected.
In order to avoid confusion about my answer, I should probably clarify.
I was answering this question only:
"Could this kernel bug affect MSVC cod
50 matches
Mail list logo
