Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17589
Your paranoid android.
=== WNT4WSSP6 (32 bit) ===
No test summary line found
=== W2KPROSP4 (32 bit) ===
No test summary line found
=== WXPPROSP3 (32 bit) ===
No test summary line found
=== W2K3R2SESP2 (32 bit) ===
No …
[View More]test summary line found
=== WVISTAADM (32 bit) ===
No test summary line found
=== W2K8SE (32 bit) ===
No test summary line found
=== W7PRO (32 bit) ===
No test summary line found
=== W7PROX64 (32 bit) ===
No test summary line found
=== TEST64_W7SP1 (32 bit) ===
No test summary line found
=== W7PROX64 (64 bit) ===
No test summary line found
=== TEST64_W7SP1 (64 bit) ===
No test summary line found
[View Less]
Hi,
Andrew Eikum asked Christian Costa:
>Just to be clear, which "native" do you mean? Does this match Windows
>7's dmusic behavior, or something else? I've been trying to target
>Windows 7's behavior in the new audio design.
A w7 target makes a lot of sense for mmdevapi/WASAPI.
However, isn't DMusic a thing of the past? In that case, I argue that DSound and DMusic
should target the "best in class" native OS of the time where apps were written
using these APIs, because the app …
[View More]writers "optimized" their apps to the behaviour
they could observe. Wouldn't "best in class" mean XP for DSound/DMusic?
For similar reasons, the MCI should mimic w9x(/wxp) behaviour, because that's what
was available when apps using the MCI were developed.
I prefer to hear "thank you guys, app X works like a charm in Wine like it worked on
my rusty w98 and later xp box, whereas it refuses to run on w7" rather than
"you guys do a great job of making my app X worked as badly in Wine as in w7 :-(
whereas it used to work fine on my w98/xp machine".
Actually, there are quite a few AppDB comments like the first one. One reason might be
that the dlls those app use were added to Wine at a time where the target OS was w9x or xp,
whereas if they were written now, targeting w7, the old app would not work in Wine either.
A related topic is: we have no idea what the "set compatibility for wXY" checkbox in w7 does.
Recently, I discovered that "Age of Empires II - Conquerors" only plays videos on a w7 machine
when you set w7 to xp compatibility. Why? The rest of the app seems to work (except for the
purple grass issue, which requires a particular DirectDraw compatibility registry entry in w7).
Did AoE target w7 when it was written? Obviously not.
Regards,
Jörg Höhle
[View Less]
Hi Alistair,
On 03/30/12 12:29, Alistair Leslie-Hughes wrote:
> Hi,
>
>
> Changelog:
> jscript: Add VT_I2 support
>
hres = IDispatchEx_InvokeEx(dispex, id, ctx->lcid, flags, dp, retv, &ei->ei, &ctx->jscaller->IServiceProvider_iface);
+ if(SUCCEEDED(hres) && retv)
+ {
+ if(V_VT(retv) == VT_I2)
+ VariantChangeType(retv, retv, 0, VT_I4);
+ }
Since the conversion here is trivial, why not do it directly?
--- a/…
[View More]dlls/jscript/jsutils.c
+++ b/dlls/jscript/jsutils.c
@@ -191,6 +191,10 @@ HRESULT to_primitive(script_ctx_t *ctx, VARIANT *v, jsexcept_t *ei, VARIANT *ret
case VT_R8:
*ret = *v;
break;
+ case VT_I2:
+ V_VT(ret) = VT_I4;
+ V_I4(ret) = V_I2(v);
+ break;
I thought the findings we've discussed off-list was that internal values
should never be of VT_I2 types, so this should never happen. If it's not
the case, I'd like to see a test case.
+function TestVT_I2()
+{
+ varI2 = GetShort();
+ num3 = 3
+
+ ok(getVT(varI2) === "VT_I4", "getVT(varI2) = " + getVT(varI2));
Please include getVT(GetShort()) test I've showed you. This eliminates a
lot of flow of value.
+ if(!strcmp_wa(bstrName, "GetShort")) {
+ *pid = DISPID_GLOBAL_SHORT;
+ return S_OK;
+ }
Please follow JavaScript names convention (this should be getShort).
Cheers,
Jacek
[View Less]
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17581
Your paranoid android.
=== WINEBUILD (build) ===
Make failed
Huw Davies <huw(a)codeweavers.com> wrote:
> + if (size.u.LowPart < sizeof( *dos )) goto fail;
Testing LowPart only could not work for large sizes.
--
Dmitry.
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17568
Your paranoid android.
=== WNT4WSSP6 (32 bit dmsynth) ===
dmsynth.c:39: Test failed: CoCreateInstance returned: 80040154
dmsynth.c:42: Test failed: CoCreateInstance returned: 80040154
=== W2KPROSP4 (32 bit dmsynth) ===
…
[View More]dmsynth.c:39: Test failed: CoCreateInstance returned: 80004002
dmsynth.c:42: Test failed: CoCreateInstance returned: 80004002
=== W2K3R2SESP2 (32 bit dmsynth) ===
dmsynth.c:39: Test failed: CoCreateInstance returned: 80040154
dmsynth.c:42: Test failed: CoCreateInstance returned: 80040154
=== W2K8SE (32 bit dmsynth) ===
dmsynth.c:39: Test failed: CoCreateInstance returned: 80040154
dmsynth.c:42: Test failed: CoCreateInstance returned: 80040154
[View Less]
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17567
Your paranoid android.
=== WNT4WSSP6 (32 bit dmsynth) ===
dmsynth.c:39: Test failed: CoCreateInstance returned: 80040154
dmsynth.c:42: Test failed: CoCreateInstance returned: 80040154
=== W2KPROSP4 (32 bit dmsynth) ===
…
[View More]dmsynth.c:39: Test failed: CoCreateInstance returned: 80004002
dmsynth.c:42: Test failed: CoCreateInstance returned: 80004002
=== W2K3R2SESP2 (32 bit dmsynth) ===
dmsynth.c:39: Test failed: CoCreateInstance returned: 80040154
dmsynth.c:42: Test failed: CoCreateInstance returned: 80040154
=== W2K8SE (32 bit dmsynth) ===
dmsynth.c:39: Test failed: CoCreateInstance returned: 80040154
dmsynth.c:42: Test failed: CoCreateInstance returned: 80040154
[View Less]
Hi everyone,
My name is Marek Chmiel, I am a student a NEIU. I am studying computer
science and network security related topics. This semester I had spent
a fair amount of time writing crypt related functions with java, and
became very interested in Cryptography. After looking over the
suggested ideas on SOC official wine wiki I was pleasantly surprised
to see that there was already a crypt related idea suggested. I have a
great understanding of c++ and java, and though I know c I have not
…
[View More]worked with it as much as the other languages.
Implementing a DSS provider sounds like an awesome task to tackle, if
someone has never written code for Linux, can they take on such a
task? Are there any significant issues implementing a DSS that you
guys know about? Any crypt GSOC ideas would you suggest for someone
who has wrote limited amount of code for Linux?
What I would also like to do, besides implementing a DSS provider, is
to fix most if not all of the crypt related bugs that remain in Wine.
This might seem like more than most people can chew, but viewing the
Bug Tracking database it appears that there aren't that many crypt
related bugs and might even be caused by a lack of a DSS provider
(Hopefully this wouldn't create a entire new series of bugs).
Thanks for any input I might receive, and look forward to speaking
with you all. I can also be found on the irc for development with the
nick "MarcoVonChmiel".
Marek K Chmiel.
[View Less]