* On Fri, 16 Jun 2006, Mike McCormack wrote:
> * Saulius Krasuckas wrote:
> >
> > Well, next example hasn't forced us to wait long for it. It's
> > Direct3DShaderValidatorCreate9!d3d9 :
(I'm sorry for swapping both parts of a function name each with other;)
> Do you really need to look at asse
Saulius Krasuckas wrote:
Well, next example hasn't forced us to wait long for it.
It's Direct3DShaderValidatorCreate9!d3d9 :
Do you really need to look at assembly to figure out that you can just
return FALSE/0/NULL and make the program or dll that's calling this
function happy?
If that
"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
Well, next example hasn't forced us to wait long for it.
It's Direct3DShaderValidatorCreate9!d3d9 :
[3] http://www.winehq.org/pipermail/wine-patches/2006-June/027601.html
Just replied to that e-mail. So that one doesn't count either.
My guess i
* On Tue, 13 Jun 2006, Dmitry Timoshkov wrote:
> * "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> > * On Mon, 12 Jun 2006, Mike McCormack wrote:
> > > * Saulius Krasuckas wrote:
> > > >
> > > > And what if interface is blackboxed?
> > >
> > > I don't know what a "blackboxed interface" is. If y
Dmitry Timoshkov wrote:
> "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> > What would you suggest me to do?
>
> Make yourself an expert in the area you are trying to improve.
I try to do that for almost a year now for winspool / Printing.
> Read MSDN,
Done for many Functions. MSDN is not
* On Tue, 13 Jun 2006, Dmitry Timoshkov wrote:
> * "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> > >
> > > Make yourself an expert in the area you are trying to improve. Read
> > > MSDN, books, find code samples on the net, write the tests on your
> > > own.
>
> Perhaps you would even become
"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
* "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
>
> What would you suggest me to do? To annoy everyone on the list during
> 2 years by asking for a tutorial on how to debug dx game which draws
> black menu? ;-)
Make yourself an expert in the
* On Tue, 13 Jun 2006, Dmitry Timoshkov wrote:
> * "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> >
> > What would you suggest me to do? To annoy everyone on the list during
> > 2 years by asking for a tutorial on how to debug dx game which draws
> > black menu? ;-)
>
> Make yourself an expe
Damjan Jovanovic <[EMAIL PROTECTED]> writes:
> So what's the story, are you accepting any
> ReactOS-derived patches for dlls/setupapi/devinst.c,
> or do I need to start writing my own?
No ReactOS-derived code will be accepted in Wine at this point.
--
Alexandre Julliard
[EMAIL PROTECTED]
"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
What would you suggest me to do? To annoy everyone on the list during 2
years by asking for a tutorial on how to debug dx game which draws black
menu? ;-)
Make yourself an expert in the area you are trying to improve. Read MSDN,
books, find code
"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
* On Mon, 12 Jun 2006, Mike McCormack wrote:
* Saulius Krasuckas wrote:
>
> And what if interface is blackboxed?
I don't know what a "blackboxed interface" is. If you could name the
interface you're talking about it would be easier to understa
--- Peter Beutner <[EMAIL PROTECTED]> wrote:
> Mike McCormack wrote:
> > Christian Gmeiner wrote:
> >> Partially implement SetupDiGetClassDevsExA. This
> patch bases on
> >> reactos setupapi.dll.
> >
> > Don't be suprised if your patch isn't accepted.
> ReactOS is considered a
> > dirty reve
* On Mon, 12 Jun 2006, Mike McCormack wrote:
> * Saulius Krasuckas wrote:
> >
> > And what if interface is blackboxed?
>
> I don't know what a "blackboxed interface" is. If you could name the
> interface you're talking about it would be easier to understand what you
> mean.
I remember that la
* On Mon, 12 Jun 2006, Dmitry Timoshkov wrote:
> * "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> >
> > > > Yes, but how would you write a test for a badly implemented
> > > > function, when you don't know its name or even name of a DLL it
> > > > resides in?
> > >
> > > Then by what means do
Saulius Krasuckas wrote:
And what if interface is blackboxed?
I don't know what a "blackboxed interface" is. If you could name the
interface you're talking about it would be easier to understand what you
mean.
Mike
* On Mon, 12 Jun 2006, Mike McCormack wrote:
> * Saulius Krasuckas wrote:
> >
> > Mike, and how would you describe API monitoring method of
> > understanding how the stuff works?
>
> You mean using +relay? IMO, that's a legitimate way of understanding how
> things work.
Not exactly. What abou
"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> Yes, but how would you write a test for a badly implemented function,
> when you don't know its name or even name of a DLL it resides in?
Then by what means do you know that the API is misbehaving?
By the fact of my special app [*] not working
* On Mon, 12 Jun 2006, Dmitry Timoshkov wrote:
> * "Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
> >
> > Yes, but how would you write a test for a badly implemented function,
> > when you don't know its name or even name of a DLL it resides in?
>
> Then by what means do you know that the API is
"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:
Using test cases to determine the behaviour of Windows provides a way to
verify both the code that's written today, and code that will be written
a year later. It's not just legally better, it's easier to do, easier
for others to understand, and
Saulius Krasuckas wrote:
Mike, and how would you describe API monitoring method of understanding
how the stuff works?
You mean using +relay? IMO, that's a legitimate way of understanding
how things work.
Does its use for finding misbehaved functions make
Wine look like it pushes the edg
* On Sat, 10 Jun 2006, Mike McCormack wrote:
> * Peter Beutner wrote:
> >
> > I think the problem is that the way you describe is totally legal in
> > most countries.
> > In fact, afaik it is only in the USA where you have this explicit
> > distinction between clean("chinese wall") and "dirty" r
Peter Beutner wrote:
For me, the main problem is that there are ReactOS developers who
think that examining Windows assembly to write ReactOS code is a
proper way to do things.
I think the problem is that the way you describe is totally legal in
most countries.
In fact, afaik it is only in th
Mike McCormack wrote:
Peter Beutner wrote:
I thought they started auditing their code and removing any "dirty"
parts?
And according to their website this process is nearly done.
Unfortunately, the fallout of their audit process has been that many
trusted developers left the project.
For
Peter Beutner wrote:
I thought they started auditing their code and removing any "dirty" parts?
And according to their website this process is nearly done.
Unfortunately, the fallout of their audit process has been that many
trusted developers left the project.
For me, the main problem is
"Peter Beutner" <[EMAIL PROTECTED]> wrote:
Don't be suprised if your patch isn't accepted. ReactOS is considered a
dirty reverse engineering project by many, and Alexandre has rejected
patches using their code before.
I thought they started auditing their code and removing any "dirty" parts?
Mike McCormack wrote:
Christian Gmeiner wrote:
Partially implement SetupDiGetClassDevsExA. This patch bases on
reactos setupapi.dll.
Don't be suprised if your patch isn't accepted. ReactOS is considered a
dirty reverse engineering project by many, and Alexandre has rejected
patches using th
Christian Gmeiner wrote:
Partially implement SetupDiGetClassDevsExA. This patch bases on reactos
setupapi.dll.
Don't be suprised if your patch isn't accepted. ReactOS is considered a
dirty reverse engineering project by many, and Alexandre has rejected
patches using their code before.
The
27 matches
Mail list logo
