Re: xcopy support try 1...
Can somebody update the latest version number in AppDB to 0.9.31 Thanks Nick
Re: xcopy support try 1...
On Do, 2007-02-22 at 21:52 +, Ann & Jason Edmeades wrote:
> Firstly, I am not sure I have included everything correctly to define a new
> directory in the build tree,
With git, you only need to add all the new files to the Index
("git-update-index --add programs/xcopy/Makefile.in" as Example)
and only that changes should be send.
tools/make_makefiles does the rest, so you compile and test
your new app.
> I have only implemented the basics,
Converting to unicode later is much harder.
I suggest to use UNICODE from the begining.
An example UNICODE console app is "programs/msiexec/*"
When you really want to have also an ansi-version
(for DOS or win9x as example), you can use TCHAR and test
your app with and without "#define UNICODE".
UNICODE is prefered and you avoid converting a lot of data,
when the app is running.
> which is file and subdirectory
> copying plus the simple reporting information.
The Patch would be even smaller, when you do no copy at all or just
do a Filecopy without recursion / Parameter-Parsing (wildcards )
> + * According to
> http://www.microsoft.com/technet/archive/msdos/comm8.mspx?mfr=true
Please remove that ref.
Many URLs are a dead link really fast.
--
By by ... Detlef
Re: ntdll: implement NtAllocateLocallyUniqueId with server call
Juan Lang wrote: This introduces a warning in trace.c about dump_luid being undeclared. trace.c seems to be at least partially generated, so I wasn't sure about sending a patch for it. Let me know how I should handle that and I'll fix it up. Hi Juan, dump_luid needs to be in trace.c. As you say, it is partially generated: /* Everything below this line is generated automatically by tools/make_requests */ /* ### make_requests begin ### */ So just put dump_luid above that line and it'll be fine. -- Rob Shearman
Re: 0.9.31 not suitable for gaming
On Mi, 2007-02-21 at 20:31 +0100, Pavel Troller wrote: > Where is SetWindowPos located ? You can find a function with "findfunc" [EMAIL PROTECTED]:~/wine.cvs/src$ tools/findfunc SetWindowPos dlls/user32/winpos.c:BOOL WINAPI SetWindowPos( and also dlls/winex11.drv/winpos.c:BOOL X11DRV_SetWindowPos -- By by ... Detlef
Re: wine.inf: Update the timezone information.
Uwe Bonnes wrote: [...] How do internaltional version of Windows get the localized names of the pletora of timezones? Apparently the registry keys and values themselves are translated, at least in NT4. That does not seem scalable at all so I don't know if that's still the approach they use. -- Francois Gouget [EMAIL PROTECTED]
Re: How complete will Wine ever be for older apps?
> I'm just trying to build up a picture in my head of whether there > will come a day when Wine users can pick an app designed for a > previous generation of Windows and expect it to work flawlessly > (ignoring things that try to manipulate the hardware directly, I > suppose)? Or will there always be incompatibilities? There will (likely) always be incompatibilities. Wine development has always been driven by app compatibility - someone picks an app and tries to run it, and tries to fix problems they come across. We don't aim for feature completeness - Windows is far, far too big to replicate with the resources we have. So, some apps (the ones developers have worked on, and likely others) will work quite well, while others (those that haven't been worked on) may not work as well. --Juan TV dinner still cooling? Check out "Tonight's Picks" on Yahoo! TV. http://tv.yahoo.com/
Re: WineConf 2007 Fundraiser proposal
On 2/21/07, Tom Wickline <[EMAIL PROTECTED]> wrote: Comments and suggestions are at this time highly suggested! We could have a small WPF "Guidelines" and spell out what we intend to spend any raised funds on/for.. Trying to answer the tough questions at hand! Here is a rough suggestion, please feel free to comment on it! (Q) What will the funds that I donate be spent on? (A) All WPF funds will go toward the goal of the Wine project being a self sufficient entity, from time to time we will need to purchase new servers and have maintenance done on our existing servers. We can also help subsidize the purchase of documentation and programming tools for core developers. But the bulk of the funds will be spent on a yearly conference for developers. (Q) What will the funds that are generated through adsence be spent on? (A) The above answer! (Q) Who is in charge of the WPF funds and distribution? (A) Jeremy White CEO and potentate of CodeWeavers (Q) What role will the WPF play in the conference? (A) The WPF will rent conference facilities, pay for one group meal, and one group outing for social conversation and comradery, sponsor travel expenses for core Wine developers. (Q) Who is eligible for conference sponsorship? (A) The top twenty core developers by lines of code committed to the git tree (Q) How often is eligibility reviewed? (A) On a yearly basis (Q) Who is in charge of the guidelines and how are changes made to it. (A) Changes can only be made by a consciences of the core developers and Jeremy White the overseer of the WPF. - The above suggestions and comments are my personal thoughts and suggestions, they should in no way be meant as a consciences or goals set by or of the Wine project. Tom
Re: [DSOUND] Implement a locking mechanism
Robert Reif wrote: You shouldn't need to make any changes to direct sound. You just need to remove the flag DSDDESC_DONTNEEDPRIMARYLOCK from alsa and make the necessary changes in alsa. The direct sound hardware primary buffer locking support is already in primary.c. You are right, partially, primary.c already has support for it, but that is only used when the application chooses to write to the primary buffer directly, in most cases the primary buffer is only used directly by the directsound mixer, and that's the case this patch is trying to handle. However the problem I have right now is that I miss some magic values so sound is a bit cumbersome, maybe someone with knowledge of dsound knows what I should put in there and be able to help me out a little. Maarten PS: CC to people you address in your emails, not everyone receives messages from wine-devel mailing lists.
Re: kernel32: Set object security on process object in CreateProcess.
Vitaliy Margolen wrote:
+
+/* set process security */
+if (ret && psa && psa->lpSecurityDescriptor)
+{
+NTSTATUS status;
+
+status = NtSetSecurityObject( info->hProcess,
DACL_SECURITY_INFORMATION,
+ psa->lpSecurityDescriptor );
+ret = status == STATUS_SUCCESS;
+if (!ret) SetLastError( RtlNtStatusToDosError( status ) );
+}
+
It would be better to pass the security descriptor (or just the DACL if
you would prefer) in the new_process call. You should be able to change
the security structure validation functions to return the number of
bytes used. Therefore, you should be able to put the security data
before the other variable data in the new_process call.
Also, I think several tests in advapi32 should succeed after this patch
is applied so you will need to patch that too.
--
Rob Shearman
Re: 0.9.31 not suitable for gaming
Am Donnerstag 22 Februar 2007 16:15 schrieb H. Verbeet: > On 22/02/07, Pavel Troller <[EMAIL PROTECTED]> wrote: > > OK, never mind. I can continue debugging tonight, just now the machine is > > occupied by my son and his friend :-). I will look at SetWindowPos(). > > Could you tell me in which file its source is ? > > That's in dlls/user32/winpos.c, but I'm not sure how likely it is for > the problem to be in there. I do not think that the problem is in SetWindowPos. I think the problem is in wined3d, either some bad parameter to SetWindowPos or maybe SetWindowPos causes signals to be sent that native d3d does not send. That said, this is a Direct3D7 application, where the window setup is done BEFORE creating the Direct3D device(which calls Init3D in wined3d). So I gather that SetupFullscreenWindow should not be called during Init3D in the d3d7 case because the window and fullscreen setting are not changed. Setting window parameters there may cause signals to be sent to the application that cause crashes in the app. So I think the question is why SetupFullscreenWindow is called at all. pgpryMz8F06HN.pgp Description: PGP signature
How complete will Wine ever be for older apps?
Sort of an open-ended question to developers :) It's obvious that Wine functionality will always lag behind Windows releases somewhat. But how accurate / complete do people think it will eventually be against older Windows releases? Is much development work even still being done on things that don't quite work as expected within apps that were current at the time of say NT4? I'm just trying to build up a picture in my head of whether there will come a day when Wine users can pick an app designed for a previous generation of Windows and expect it to work flawlessly (ignoring things that try to manipulate the hardware directly, I suppose)? Or will there always be incompatibilities? cheers Jules
Re: 0.9.31 not suitable for gaming
On 22/02/07, Pavel Troller <[EMAIL PROTECTED]> wrote: OK, never mind. I can continue debugging tonight, just now the machine is occupied by my son and his friend :-). I will look at SetWindowPos(). Could you tell me in which file its source is ? That's in dlls/user32/winpos.c, but I'm not sure how likely it is for the problem to be in there.
Re: 0.9.31 not suitable for gaming
Hi!
> Am Donnerstag 22 Februar 2007 15:04 schrieb Pavel Troller:
> > So I commented out the SetWindowPos() call in ..._SetupFullscreenWindow
> > (on lines 1251&2 of the today's source) and... voilla, the game starts and
> > runs perfectly. My son has verified it and didn't find any problems.
> Yeah, the SetWindowPos isn't required for all games. One game that needs it
> is
> Gothic 2.
>
> It is strange that SetWindowPos crashed. Can you check that window is
> valid(i.e. not NULL)?
And would it be possible that the immediately following ShowWindow(window, TRUE)
wouldn't fail too ?
>
> TRACE("window is %p\n", window);
>
> > Because I didn't read anything from Stefan for a while, I'll wait a bit
> > more and then I'll create a bugzilla record for it.
> > Is it ok ?
> I was away the last day on a small LAN party with friends, thats why I didn't
> reply.
OK, never mind. I can continue debugging tonight, just now the machine is
occupied by my son and his friend :-). I will look at SetWindowPos(). Could you
tell me in which file its source is ?
With regards, Pavel Troller
Re: 0.9.31 not suitable for gaming
Am Donnerstag 22 Februar 2007 15:04 schrieb Pavel Troller:
> So I commented out the SetWindowPos() call in ..._SetupFullscreenWindow
> (on lines 1251&2 of the today's source) and... voilla, the game starts and
> runs perfectly. My son has verified it and didn't find any problems.
Yeah, the SetWindowPos isn't required for all games. One game that needs it is
Gothic 2.
It is strange that SetWindowPos crashed. Can you check that window is
valid(i.e. not NULL)?
TRACE("window is %p\n", window);
> Because I didn't read anything from Stefan for a while, I'll wait a bit
> more and then I'll create a bugzilla record for it.
> Is it ok ?
I was away the last day on a small LAN party with friends, thats why I didn't
reply.
pgpybnZVMqxtI.pgp
Description: PGP signature
Re: 0.9.31 not suitable for gaming
> > On 21/02/07, Pavel Troller <[EMAIL PROTECTED]> wrote:
> > > The last trace which appeared in the log is 2683, so
> > >IWineD3DDevice_CreateAdditionalSwapChain() didn't return. I'm going bananas
> > >from those names; where the hell this one grows :-) ? grep, as obvious,
> > >shows
> > >its calls only.
> > IWineD3DDeviceImpl_CreateAdditionalSwapChain() in dlls/wined3d/device.c.
> > IWineD3DDevice_CreateAdditionalSwapChain is actually a macro defined
> > in include/wine/wined3d_interface.h.
> >
> Thanks,
> traced a few calls deeper. Now I'm standing at
>
> static void WINAPI IWineD3DDeviceImpl_SetupFullscreenWindow(IWineD3DDevice
> *iface, HWND window) {
> IWineD3DDeviceImpl *This = (IWineD3DDeviceImpl *)iface;
>
> LONG style, exStyle;
> /* Don't do anything if an original style is stored.
> * That shouldn't happen
> */
> TRACE("(%p): Setting up window %p for exclusive mode\n", This, window);
> if (This->style || This->exStyle) {
> ERR("(%p): Want to change the window parameters of HWND %p, but "
> "another style is stored for restoration afterwards\n", This,
> window);
> }
>
> /* Get the parameters and save them */
> style = GetWindowLongW(window, GWL_STYLE);
> exStyle = GetWindowLongW(window, GWL_EXSTYLE);
> This->style = style;
> This->exStyle = exStyle;
>
> /* Filter out window decorations */
> style &= ~WS_CAPTION;
> style &= ~WS_THICKFRAME;
> exStyle &= ~WS_EX_WINDOWEDGE;
> exStyle &= ~WS_EX_CLIENTEDGE;
>
> /* Make sure the window is managed, otherwise we won't get keyboard input
> */
> style |= WS_POPUP | WS_SYSMENU;
>
> TRACE("Old style was %08x,%08x, setting to %08x,%08x\n",
> This->style, This->exStyle, style, exStyle);
> TRACE("1184\n");
> SetWindowLongW(window, GWL_STYLE, style);
> SetWindowLongW(window, GWL_EXSTYLE, exStyle);
> TRACE("1187\n");
> /* Inform the window about the update. */
> SetWindowPos(window, HWND_TOP, 0, 0,
> This->ddraw_width, This->ddraw_height, SWP_FRAMECHANGED);
> TRACE("1191\n");
> ShowWindow(window, TRUE);
> TRACE("1193\n");
> }
>
> The last trace executed is 1187, which looks that SetWindowPos doesn't return.
> Should I trace even more deep, or is anybody getting an idea, what can be
> wrong
> here ?
> Where is SetWindowPos located ?
>
> With regards, Pavel Troller
>
Hi!
Because I had to restore working wine, I did the following:
1) Restored original files
2) Pulled today's version
3) Compiled and verified
... Fallout tactics still didn't start with the obvious symptoms.
So I commented out the SetWindowPos() call in ..._SetupFullscreenWindow (on
lines 1251&2 of the today's source) and... voilla, the game starts and runs
perfectly. My son has verified it and didn't find any problems.
Then he tried HL2 and it seems also fully functional.
So... The bug is still there, but my workaround fixes it for me and I didn't
find any drawbacks (trying a lot of programs I'm using like IDA and some
special telco programs).
Because I didn't read anything from Stefan for a while, I'll wait a bit more
and then I'll create a bugzilla record for it.
Is it ok ?
With regards, Pavel Troller
