"James McKenzie" <[EMAIL PROTECTED]> wrote:
> Dan Kegel wrote:
>> On Wed, Mar 12, 2008 at 5:11 PM, jingo811 <[EMAIL PROTECTED]> wrote:
>>
>>> So I was wondering can you give me an ordered to-do-list in becoming a
>>> Code Monkey for WineHQ?
>>>
>>> Like do I have to know both C and C+
Dan Kegel wrote:
> On Wed, Mar 12, 2008 at 5:11 PM, jingo811 <[EMAIL PROTECTED]> wrote:
>
>> So I was wondering can you give me an ordered to-do-list in becoming a Code
>> Monkey for WineHQ?
>>
>> Like do I have to know both C and C++ to code for Wine.
>>
>
> Nope, just C. Go thr
Yup, ignore.
On Thu, Mar 13, 2008 at 04:00:32PM -0700, Dan Hipschman wrote:
>
> NOTE: I thought I sent this with the other five patches, but I don't see
> it. Sorry if it ends up being a resend.
>
> This feature of MoveFileEx is technically needed by
> IBackgroundCopyJob_Complete
> to return
Christopher Harvey wrote:
> I've had a few ideas that I thought of on my own, but now I'm starting
> to see they perhaps aren't as useful as the ideas thought of by current
> developers, but I'll float it out there one last time. I thought it
> would be cool to create a wine GUI overlay for game
Thanks Alexandre,
(BTW This createwindow / movewindow / draw to window is all occurring in
LBUTTONDOWN processing)
>> 1. MoveWindow doesn't update the DCEx clip_region region, and hence when
the
>> visible region changes, it is merged with the clip region and since there
is
>> no overlap the visi
The 1.0 release of Wine is tenatively scheduled for
the 15th anniversary of the project (roughly 1 June 2008,
if you take Dan Dulitz' message as the start of the project,
http://groups.google.com/group/comp.os.linux/msg/7f92abdf494ab8b3 )
Over the last six or so months, the wine developers have
id
On Thu, Mar 13, 2008 at 12:49 PM, L. Rahyen <[EMAIL PROTECTED]> wrote:
> Separate user is enough if you don't have world writable files in your
> system. And of course user for such purpose shouldn't be in group(s) that
> have write access to your personal or system files.
> If yo
Hi,
even with "--with-alsa" there is no report on a missing asoundlib.h.
This is a bit inconvenient since other missing libs are reported.
Valid for wine-0.9.57
Sebastian
signature.asc
Description: This is a digitally signed message part.
On 3/13/08, L. Rahyen <[EMAIL PROTECTED]> wrote:
> Separate user is enough if you don't have world writable files in your
> system.
No, because the malware could root your Linux system
using a local priv escalation exploit. You really want a
totally isolated sandbox.
- Dan
Huw Davies <[EMAIL PROTECTED]> writes:
> ---
> fonts/Makefile.in |1 +
> fonts/symbol.sfd | 83
> +
> 2 files changed, 84 insertions(+), 0 deletions(-)
> create mode 100644 fonts/symbol.sfd
It fails make test for me:
../../../tools/ru
Jacek Caban <[EMAIL PROTECTED]> writes:
> ---
> dlls/mshtml/protocol.c | 31 +--
> dlls/mshtml/tests/protocol.c | 41
> -
> 2 files changed, 61 insertions(+), 11 deletions(-)
This breaks the tests:
../../../tools/runt
On Thursday March 13 2008 19:31:49 Edward Savage wrote:
> This sounds like some thing I'd be able to do though I'm not sure of
> the best way to sand box wine away from the system. What is the best
> way to go about this, would simply creating a new user be enough to
> protect a system, or does a
> I like that idea. are there any linux tools to watch files for changes?
> Or maybe have linux watch the wine processes for their file changing
> activities.
I've used tripwire for a long time.
fschange looks promising, builds upon inotify, but I've never used it yet:
http://stefan.buettcher.
Dan Kegel wrote:
> On 3/13/08, Edward Savage <[EMAIL PROTECTED]> wrote:
>
>> Just as a silly outside thought; would it be worth keeping track of
>> some of the bigger windows virus so we can see how good wine
>> compatibiliy with all of the nitty gritty bugs of windows really is?
>> Also thi
On 3/13/08, Edward Savage <[EMAIL PROTECTED]> wrote:
> This sounds like some thing I'd be able to do though I'm not sure of
> the best way to sand box wine away from the system. What is the best
> way to go about this, would simply creating a new user be enough to
> protect a system, or does a
This sounds like some thing I'd be able to do though I'm not sure of
the best way to sand box wine away from the system. What is the best
way to go about this, would simply creating a new user be enough to
protect a system, or does a vm have to be used?
I have a bit of free time tomorrow so I'll
On 3/13/08, Edward Savage <[EMAIL PROTECTED]> wrote:
> Just as a silly outside thought; would it be worth keeping track of
> some of the bigger windows virus so we can see how good wine
> compatibiliy with all of the nitty gritty bugs of windows really is?
> Also this would allow us to identify
I remember my last attempt to run a virus under wine caused a total
loss of my .wine structure but didn't manage to cause any damage to my
sandbox (including a juicy fake address list). I was really let down
as I expected carnage.
Just as a silly outside thought; would it be worth keeping track o
Can someone please take a look at this bug for me?
http://bugs.winehq.org/show_bug.cgi?id=11953
Proposing another thing if implementing d3dx9_36.dll is too much I
propose to implement:
1 D3DXAssembleShader
2 D3DXAssembleShaderFromFileA
3 D3DXCompileShader
4 D3DXCompileShaderFromFileA
5 D3DXCreateCubeTextureFromFileExA
6 D3DXCreateCubeTextureFromFileI
Is ther eany problem with this patch?
---
dlls/d3dx8/d3dx8_main.c | 59
+-
1 files changed, 57 insertions(+), 2 deletions(-)
diff --git a/dlls/d3dx8/d3dx8_main.c b/dlls/d3dx8/d3dx8_main.c
index ee897a8..a1d37b8 100644
--- a/dlls/d3dx8/d3dx8_main.c
MammothTruk wrote:
> I read the WineHQ newsletters when they come out to try and keep up on
> the goings on of Wine and what will run on it. I noticed that the
> Wsock32.dll was suggested as a SoC project. I wanted to point out
> that Vista X64 has issues with this dll and some of the newer pr
I read the WineHQ newsletters when they come out to try and keep up on the
goings on of Wine and what will run on it. I noticed that the
Wsock32.dllwas suggested as a SoC project. I wanted to point out that
Vista X64 has
issues with this dll and some of the newer programs arent accessing it
right
Artur Szymiec wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Stefan Dösinger pisze:
>> Am Donnerstag, 13. März 2008 10:19:36 schrieb Artur Szymiec:
>>> This is a corrected patch. The uuid is common to dx8 and dx9
>>> since the UUID is generated inside wined3d.
>> Yes, that looks reas
On Thu, Mar 13, 2008 at 08:32:23AM -0700, Dan Kegel wrote:
> http://wearenixed.blogspot.com/2008/03/you-only-know-good-when-youve-seen-bad.html
>
> "I had set her up with a perfect Wine install. She had a bit
> of software that needed to run under wine and I had shown her
> how to install within t
Quoting Dan Kegel <[EMAIL PROTECTED]>:
> http://wearenixed.blogspot.com/2008/03/you-only-know-good-when-youve-seen-bad.html
>
> "I had set her up with a perfect Wine install. She had a bit
> of software that needed to run under wine and I had shown her
> how to install within that environment. App
http://wearenixed.blogspot.com/2008/03/you-only-know-good-when-youve-seen-bad.html
"I had set her up with a perfect Wine install. She had a bit
of software that needed to run under wine and I had shown her
how to install within that environment. Apparently, I wasn't
specific enough. It never occur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Dösinger pisze:
> Am Donnerstag, 13. März 2008 14:40:07 schrieb Artur Szymiec:
>> Stefan Dösinger pisze:
>>> Am Donnerstag, 13. März 2008 10:19:36 schrieb Artur Szymiec:
This is a corrected patch.
The uuid is common to dx8 and dx9 sinc
Am Donnerstag, 13. März 2008 14:40:07 schrieb Artur Szymiec:
> Stefan Dösinger pisze:
> > Am Donnerstag, 13. März 2008 10:19:36 schrieb Artur Szymiec:
> >> This is a corrected patch.
> >> The uuid is common to dx8 and dx9 since the UUID is generated
> >> inside wined3d.
> >
> > Yes, that looks reas
Am Donnerstag, 13. März 2008 13:04:28 schrieb Artur Szymiec:
> Thank you very much for help Stefan !
You're welcome. Thanks for your help to make Wine better.
Just send the patch to wine-patches, if they're on wine-devel they won't be
applied. Also I recommend not to sign mails to wine-patches be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Dösinger pisze:
> Am Donnerstag, 13. März 2008 10:19:36 schrieb Artur Szymiec:
>> This is a corrected patch. The uuid is common to dx8 and dx9
>> since the UUID is generated inside wined3d.
> Yes, that looks reasonable. Only two small issues:
>
"Ann & Jason Edmeades" <[EMAIL PROTECTED]> writes:
> 1. MoveWindow doesn't update the DCEx clip_region region, and hence when the
> visible region changes, it is merged with the clip region and since there is
> no overlap the visible region is empty so all subsequent processing ends.
>
> Q: Whats
Dan Hipschman <[EMAIL PROTECTED]> writes:
> @@ -129,6 +131,21 @@ ServiceMain(DWORD dwArgc, LPWSTR *lpszArgv)
> return;
> }
>
> +globalMgr.jobEvent = CreateEventW(NULL, TRUE, FALSE, NULL);
> +if (!globalMgr.jobEvent) {
> +ERR("Couldn't create event: error %d\n", GetL
Am Donnerstag, 13. März 2008 10:19:36 schrieb Artur Szymiec:
> This is a corrected patch.
> The uuid is common to dx8 and dx9 since the UUID is generated
> inside wined3d.
Yes, that looks reasonable. Only two small issues:
> +/* Fixes BUG 11897 */
That's not really needed, specifying a GUID is cor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Dösinger pisze:
> Am Donnerstag, 13. März 2008 01:02:47 schrieb Artur Szymiec:
>> Stefan Dösinger pisze:
>>> Hi, Note that we do not accept workaround patches into Wine,
>>> because
>> otherwise the
>>
>>> whole software would become a huge work
>
> What do you mean by hyperlinks don't work?
>
I have such code which create html page:
htmlDoc2->lpVtbl->open(htmlDoc2, L"html/txt", vnull, vnull, vnull, &pdisp);
bstr =SysAllocString(L"Simple text");
if ((pVar->bstrVal = bstr)) {
htmlDoc2->lpVtbl->write(htmlDoc2, sfArray);
}
SysFreeString
James Hawkins wrote:
> Hi,
>
> Fixes bug 11891. http://bugs.winehq.org/show_bug.cgi?id=11891
>
> Changelog:
> * Ignore the custom action type 51 if the source field is empty.
>
> dlls/msi/custom.c|3 ++
> dlls/msi/tests/install.c | 65
> ++
37 matches
Mail list logo
