NtMapView of Section is returning bad values from the wineserver calls
trace:virtual:MapViewOfFileEx Mapping Section View handle=58, pid=,
addr=0 zbits=0 commit=0, offs_l=0 offs_h=0 count=0
trace:virtual:NtMapViewOfSection handle=58 process= addr=0
off=0 size=0 access=4
Vi
On Thu, Apr 14, 2005 at 03:05:36PM +0200, Alexandre Julliard wrote:
> Actually it should be possible to handle the fault using a vectored
> handler, without requiring internal functions at all.
Completely untested (what do people use to test DIB handling?),
but it compiles. Is something like this
Le sam 16/04/2005 à 23:35, Benjamin Cutler a écrit :
> Ok, one more try at this.
[snip]
> --- tools/wine.inf11 Apr 2005 18:49:28 - 1.31
> +++ tools/wine.inf17 Apr 2005 03:28:19 -
> @@ -41,6 +41,7 @@
> MCI,\
> Misc,\
> Nls,\
> +PowrProf,\
> OLE,\
> T
OK, I think I haven't explained the patches (sorry).
--- William Poetra Yoga H <[EMAIL PROTECTED]> wrote:
> Hi guys (and gals), sorry for the long absence but my time got taken up in
> something else (a problem with my isp, see
> http://sourceforge.net/projects/drcom-client) and I couldn't spend
Hi,
--- Jakob Eriksson <[EMAIL PROTECTED]> wrote:
> Has anybody else thought of using DLLs (like ReactOS' dlls) as a
> compatibility
> layer to different Windows versions?
I think it would be good in testing Wine/ReactOS vs Windows for Winelib
applications developers.
You can make a dummy file
--- Jakob Eriksson <[EMAIL PROTECTED]> wrote:
> Wasn't there talk about making DLLs for use in Windows, to
> export a native Windows desktop to an X11 server?
There was someone who did this by compiling parts of Wine under Cygwin with
Detours from
research.microsoft.com Look around the mailing l
Wasn't there talk about making DLLs for use in Windows, to
export a native Windows desktop to an X11 server?
//Jakob
Has anybody else thought of using DLLs (like ReactOS' dlls) as a
compatibility
layer to different Windows versions?
I.e. when you distribute your Windows app, you also throw in a bunch of DLLs
that implement lots of functionality you aren't sure exists on your
target otherwise.
(Windows 2003 f
I am trying to Implement get_default_drive_device for Solaris but its unclear
to me what this is supposed to do. It get passed the links in
~/.wine/dosdevices then tries to determine a mount point for them. Reading
the Linux code the function only seems to return a mount point if the
dosdevices
Robert Reif wrote:
Add keyboard data format.
With Dmitry's const changes.
Index: dlls/dinput/data_formats.c
===
RCS file: /home/wine/wine/dlls/dinput/data_formats.c,v
retrieving revision 1.2
diff -p -u -r1.2 data_formats.c
--- dlls/di
> Are you sure that by disabling MOUSE_HACK, it fixes your problem ? If yes,
> it's more a side effect of what exactly MOUSE_HACK is than a real fix.
Yes, it "fixes" the problem. The mouse wasn't moved once during my 2 minute
test, but it looks like this is because the mouse warp is broken with
M
"Robert Reif" <[EMAIL PROTECTED]> wrote:
> +DIOBJECTDATAFORMAT dfDIKeyboard[] = {
> + { &GUID_Key,0,DIDFT_OPTIONAL|DIDFT_BUTTON|DIDFT_MAKEINSTANCE(0),0},
Is it possible to make it 'static const'?
--
Dmitry.
Le sam 16/04/2005 à 07:00, Benjamin Cutler a écrit :
> Oops, last one was missing commas, wasn't it?
I guess you also need to add powrprof to the list of sections in
[DefaultInstall] at the start of wine.inf.
Vincent
> "Lars" == Lars Segerlund <[EMAIL PROTECTED]> writes:
Lars> What is the status of wines USB support ?
Lars> I have an IDE for a developement board and I really would like to
Lars> flash it from Linux, ( I don't have windows), and this uses USB to
Lars> talk to the board. I
I was having this issue with one of my games too, but this patch seems
to have fixed it. However, now I'm hitting an error in kernel32. (System
Shock 2, for the curious.)
What traces should I turn on to help track this down?
wine: Unhandled exception (thread 0009), starting debugger...
WineDbg sta
Juan Lang <[EMAIL PROTECTED]> writes:
> ChangeLog: generate header when proxy/stub is generated to prevent
> "#include(null)" from appearing in generated file
Surely there's a better way to fix this than by forcing generation of
the header even when it's not requested.
--
Alexandre Julliard
[EM
Vitaliy Margolen <[EMAIL PROTECTED]> writes:
> + if (((tvItem->mask & TVIF_CHILDREN ) && (originalItem.cChildren
> != wineItem->cChildren ) ) ||
> + ((tvItem->mask & TVIF_IMAGE) && (originalItem.iImage
> != wineItem->iImage)&&
> + wineI
Eric Pouech <[EMAIL PROTECTED]> writes:
> If you suppose no app would ever set its own vectored handler at the
> beginnnig of the vector...
> One could argue that no well behaved application should do it, but well...
That would only be a problem if the app tries to handle the
exception. I think t
Alexandre Julliard a écrit :
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
I guess this has no chance of going away until we have a DIB engine,
which is not even on the horizon.
Actually it should be possible to handle the fault using a vectored
handler, without requiring internal functions at a
Paul Vriens a écrit :
Hi,
this is a first go at some unit tests and related fixes for
NtQuerySystemInformation.
The ultimate goal is to get SysInternal's Process Explorer running.
you may need (to get P.E. running) more than just a better support for some
Nt*Info* functions. For examples, NT expos
* On Thu, 14 Apr 2005, Jacek Caban wrote:
> *Saulius Krasuckas wrote:
> >And the second question is: should it go to the "include/wine/test.h"
> >or some separate header like a "include/wine/strings.h".
>
> wine/test.h doesn't seems to me to be a good place for it. Also, as it's
> used only in tes
21 matches
Mail list logo
