Re: direct access to IO space [Was: kernel level drivers - next try]

2006-10-16 Thread Marcus Meissner
On Mon, Oct 16, 2006 at 11:45:01PM +0300, Saulius Krasuckas wrote: > * On Sat, 14 Oct 2006, James Courtier-Dutton wrote: > > * Rolf Kalbermatter wrote: > > >* Saulius Krasuckas [EMAIL PROTECTED] wrote: > > >> Today I have tried to compile ntoskrnl.exe, then checked out master > > >> branch, compil

Re: msi [3/3]: Set the USERNAME and COMPANYNAME properties when initializing a package

2006-10-16 Thread James Hawkins
On 10/16/06, Mike McCormack <[EMAIL PROTECTED]> wrote: James Hawkins wrote: > +WCHAR user[MAX_PATH]; > + > +size = MAX_PATH; > +type = REG_SZ; > +user[0] = '\0'; > +res = RegQueryValueExW( hkey, szRegisteredUser, NULL, &type, (LPBYTE)user, &size ); > +

Re: msi [3/3]: Set the USERNAME and COMPANYNAME properties when initializing a package

2006-10-16 Thread Mike McCormack
James Hawkins wrote: +WCHAR user[MAX_PATH]; + +size = MAX_PATH; +type = REG_SZ; +user[0] = '\0'; +res = RegQueryValueExW( hkey, szRegisteredUser, NULL, &type, (LPBYTE)user, &size ); +MSI_SetPropertyW( package, szUSERNAME, user ); How about: L

Re: comctl32: rebar: don't return rectangles with negative width or height in NCCalcSize (fixes bug #3797)

2006-10-16 Thread Vitaliy Margolen
Mikołaj Zalewski wrote: > CreateWindow doesn't like them > > if (infoPtr->dwStyle & WS_BORDER) { > - InflateRect((LPRECT)lParam, -GetSystemMetrics(SM_CXEDGE), > - -GetSystemMetrics(SM_CYEDGE)); > +rect->left = min(rect->left + GetSystemMetrics(SM_CXEDGE), > rect-

Re: msi [2/3]: Run SetProperty events before all other events no matter what the order is

2006-10-16 Thread Mike McCormack
Yey! More msi fixes! :) James Hawkins wrote: +copy = MSI_CopyRecord( rec ); Why not just do a msiobj_addref( &ref->hdr ) rather than copying the record? +/* move SetProperty events to the front of the list */ +reprioritize_set_prop_events( &events ); How about just running

Re: direct access to IO space [Was: kernel level drivers - next try]

2006-10-16 Thread Saulius Krasuckas
* On Sat, 14 Oct 2006, Rolf Kalbermatter wrote: > The IO sys driver I have worked with and made myself in the past > did use a number of specific kernel functions such as > > NTKERNELAPI void Ke386SetIoAccessMap(int, IOPM *); > NTKERNELAPI void Ke386QueryIoAccessMap(int, IOPM *); > NTKERNELAPI vo

Re: [wined3d] GetFrontBufferData

2006-10-16 Thread Stefan Dösinger
Am Montag 16 Oktober 2006 18:02 schrieb Karsten Elfenbein: > Hi, > > this is the patch that allows EVE online to capture ingame screenshots. > (fixes the start coordinates for glReadPixels and turns the output > upside down again) > It works with the login screen (running as managed window) and in

Re: direct access to IO space [Was: kernel level drivers - next try]

2006-10-16 Thread Saulius Krasuckas
* On Sat, 14 Oct 2006, James Courtier-Dutton wrote: > * Rolf Kalbermatter wrote: > >* Saulius Krasuckas [EMAIL PROTECTED] wrote: > >> Today I have tried to compile ntoskrnl.exe, then checked out master > >> branch, compiled stock Wine, then tried to run win32 app which do > >> simple port I/O aft

Re: user: add GetRawInputDeviceList stub

2006-10-16 Thread L. Rahyen
> Thank you for sending patch. Here are few problems with it you need to fix: Thanks for your tips. I'm sorry for doing some mistakes, but this is first time when I send patch and also I havn't experience in Wine development before. I hope I will contribute more complex and useful patch

Re: winedbg: remove duplicated bare address in backtrace

2006-10-16 Thread Eric Pouech
Peter Oberndorfer wrote: the bare address is printed at the beginning of the line and at the end in ( ) like "2 0xb7eccf3b wine_switch_to_stack+0x17 in libwine.so.1 (0xb7eccf3b)" actually, it's the frame address that's supposed to be printed so it should read print_bare_address(&dbg_curr_th

[wined3d] GetFrontBufferData

2006-10-16 Thread Karsten Elfenbein
Hi, this is the patch that allows EVE online to capture ingame screenshots. (fixes the start coordinates for glReadPixels and turns the output upside down again) It works with the login screen (running as managed window) and in fullscreen. (when desktop is 32bit) Is there much more stuff needed or

Re: user32[2/3]: send a WM_MOUSELEAVE even if another window calls TrackMouseEvent before the timer proc is called

2006-10-16 Thread Mikołaj Zalewski
Alexandre Julliard wrote: Mikołaj Zalewski <[EMAIL PROTECTED]> writes: @@ -949,6 +954,12 @@ TrackMouseEvent (TRACKMOUSEEVENT *ptme) } } } else { +/* In our implementation it's possible that another window will receive a + * WM_MOUSEMOVE and call Trac

Re: user32[2/3]: send a WM_MOUSELEAVE even if another window calls TrackMouseEvent before the timer proc is called

2006-10-16 Thread Alexandre Julliard
Mikołaj Zalewski <[EMAIL PROTECTED]> writes: > @@ -949,6 +954,12 @@ TrackMouseEvent (TRACKMOUSEEVENT *ptme) > } > } > } else { > +/* In our implementation it's possible that another window will > receive a > + * WM_MOUSEMOVE and call TrackMouseEvent befo

Re: Fix compilation with gcc 2.95.

2006-10-16 Thread Alexandre Julliard
Francois Gouget <[EMAIL PROTECTED]> writes: > @@ -786,10 +787,10 @@ static inline void print_matrix( > const char* name, const D3DMATRIX* matrix) { > > trace("%s Matrix = {\n", name); > -trace("%f %f %f %f\n", matrix->m[0][0], matrix->m[1][0], > matrix->m[2][0], matrix->m[3][0

Re: Delorme AAA Map N Go 6 install fail - maybe COM related?

2006-10-16 Thread Vitaliy Margolen
David D. Hagood wrote: > Vitaliy Margolen wrote: >> Please open proper bug report in bugzilla and attach (don't paste) this >> terminal output. > > What I was hoping to do was to gather a bit more information about what > is wrong first - for example, while I suspect COM, I cannot > unequivicably

Re: Delorme AAA Map N Go 6 install fail - maybe COM related?

2006-10-16 Thread Stefan Dösinger
Hi, > =>1 0x610d6468 in oleaut32 (+0x36468) (0x610d6468) >2 0x610d7b01 in oleaut32 (+0x37b01) (0x610d7b01) >3 0x610df741 in oleaut32 (+0x3f741) (0x610df741) >4 0x610e006f in oleaut32 (+0x4006f) (0x610e006f) Are you using native oleaut32, ole32 and rpcrt4 maybe? If you're using builtin

Re: Delorme AAA Map N Go 6 install fail - maybe COM related?

2006-10-16 Thread David D. Hagood
Vitaliy Margolen wrote: Please open proper bug report in bugzilla and attach (don't paste) this terminal output. What I was hoping to do was to gather a bit more information about what is wrong first - for example, while I suspect COM, I cannot unequivicably say it IS COM, so I don't want to

Re: Delorme AAA Map N Go 6 install fail - maybe COM related?

2006-10-16 Thread Vitaliy Margolen
David D. Hagood wrote: > I am getting a crash when I try to install Delorme AAA MapNGo 6 under a > fresh build of Wine (CVS as of 15 Oct 2006). The crash leads me to > believe there is a problem with Wine's COM system (Delorme is about the > most COM-happy company I have seen - I think they would m

Delorme AAA Map N Go 6 install fail - maybe COM related?

2006-10-16 Thread David D. Hagood
I am getting a crash when I try to install Delorme AAA MapNGo 6 under a fresh build of Wine (CVS as of 15 Oct 2006). The crash leads me to believe there is a problem with Wine's COM system (Delorme is about the most COM-happy company I have seen - I think they would make every pixel a COM objec

Re: Appdb as application regression finder

2006-10-16 Thread Francois Gouget
On Wed, 27 Sep 2006, Tom Spear wrote: [...] > > I haven't run into too many of those. I'm afraid it might be too much > > information... > > > > Mind if I ask how so? Many games bugs cant be properly diagnosed because > the bug occurs somewhere that the trial version doesnt include. If the bug

Re: u_int32_t

2006-10-16 Thread Alexandre Julliard
n0dalus <[EMAIL PROTECTED]> writes: > I didn't think we were allowed to use C99 code in wine, for > compatibility reasons (C++ style comments, etc)? Though I guess using > C99 headers would still work with pre-C99 compilers whereas C99 code > features wouldn't. > > Any official word on this? In g

Re: [winex11.drv] client-side DIB copy

2006-10-16 Thread Alexandre Julliard
"Damjan Jovanovic" <[EMAIL PROTECTED]> writes: > +switch (dstDib.dsBm.bmBitsPixel) > +{ > + case 1: > +widthBytes = (width + 7) / 8; > +srcOffsetBytes = (xSrc + 7) / 8; > +dstOffsetBytes = (xDst + 7) / 8; > +break; > + case 4: > +widthBytes

Re: ntdll: Win64 printf format warning fixes.

2006-10-16 Thread Alexandre Julliard
Hans Leidekker <[EMAIL PROTECTED]> writes: > I needed two casts to silence warnings arising from the fact > that ULONG/DWORD and SIZE_T are no longer compatible: > > dlls/ntdll/loader.c:1290 > dlls/ntdll/relay.c:651 You can't simply cast them since the types will have different sizes on Win64. -