Okay,
So I'm trying to clean up dsound before I make it run properly
in different scheduling conditions, and I'm having a heck of
a time with it; hoping for some advice/thoughts.
First, I encountered two glitches in dsound/mixer.c that appear
to be bugs, but I do not understand the code well enough
"Jonathan Ernst" <[EMAIL PROTECTED]> wrote:
> This time I didn't translate the WINE_ERR messages and translated another
> messagebox.
It would be better to not touch WINE_ERR lines at all then.
> Changelog:
> - localization of uninstaller
> +/* We load the strings */
> +LoadString( hIn
On Fri, 25 Feb 2005 09:22, Alex Woods wrote:
> Over the course of 13 (unlucky for me ;)) crashes, these are the only 3
> addresses it has given. My question is what can I do to debug [target
> application SEGVs].
I can't find any good explanation of this either. Googling for "gdb objdump
site:
On Fri, 25 Feb 2005 07:25, Troy Rollo wrote:
> On Friday 25 February 2005 03:26, Mike McCormack wrote:
> > Thanks for finding this problem. I think the root cause of the problem
> > is that three structures that need to be the same require 3 seperate
> > tweaks.
> >
> > Can you confirm that this p
Hi,
World of Warcraft is working beautifully now apart from a crash that
occurs seemingly randomly. The application is catching the crash, and
giving a message like this:
This application has encountered a critical error:
ERROR #132 (0x85100084)
Program:C:\Program Files\World of Warcraf
On Thu, Feb 24, 2005 at 09:19:15PM +0100, Hans Leidekker wrote:
> Among other possibilities, if you have an RPM based distro
> you could use my MinGW cross compiler RPM packages, prebuilt
> for Fedora Core and SUSE but also available as source RPMS
> to rebuild yourself:
It may be a good idea to h
On Thursday 24 February 2005 17:53, Michael Jung wrote:
> I would like to test a wine dll I'm working on on windows. Could you please
> tell me how the wine dlls are build for windows ? (Or beat me to the the
> place where it is documented.)
Among other possibilities, if you have an RPM based dis
On Thursday 24 February 2005 20:39, Paul Vriens wrote:
> Could you send the patch to wine-patches :-).
Damn, another typo on my part (I meant it to go there in the first place)
On Friday 25 February 2005 03:26, Mike McCormack wrote:
> Thanks for finding this problem. I think the root cause of th
--- James Hawkins <[EMAIL PROTECTED]> wrote:
> What is your opinion on whether we should implement and use either the
> user-mode or kernel-mode (or both) string safe functions? Using these
> functions instead of the standard c string functions would promote
> consistency and security in the wine
Hi,
--- Michael Jung <[EMAIL PROTECTED]> wrote:
> I would like to test a wine dll I'm working on on windows. Could you please
> tell me how the wine dlls are build for windows ? (Or beat me to the the
> place where it is documented.)
Ivan has a script he uses and there are a few patches I keep
On Thu, Feb 24, 2005 at 08:12:10PM +0300, Vitaly Lipatov wrote:
> jade:/home/lav/RPM/BUILD/wine-20050224/documentation/faq.sgml:1716:66:Q:
> length of name token must not exceed NAMELEN (44)
Thanks, sorry for the problem.
ChangeLog
Shorten the id of the question to avoid jade error
Patch
http://cvs.winehq.org/patch.py?id=16300
breaks faq.sgml in line
during compiling:
jade:/home/lav/RPM/BUILD/wine-20050224/documentation/faq.sgml:1716:66:Q:
length of name token must not exceed NAMELEN (44)
--
Vitaly Lipatov, ALT Linux Team
Russia, Saint-Petersburg, www.etersoft.ru
On Thu, 2005-02-24 at 17:26, Mike McCormack wrote:
> Troy Rollo wrote:
> > After changing StorageBaseImpl, StorageInternalImpl was not updated to
> > reflect
> > the change.
>
> Thanks for finding this problem. I think the root cause of the problem
> is that three structures that need to be th
Hello,
I would like to test a wine dll I'm working on on windows. Could you please
tell me how the wine dlls are build for windows ? (Or beat me to the the
place where it is documented.)
Thanks,
--
Michael Jung
[EMAIL PROTECTED]
"Dmitry Timoshkov" <[EMAIL PROTECTED]> wrote:
> in the msg.c,test_DestroyWindow() test case adding WS_VISIBLE to all
> windows except a parent shows that behaviour doesn't change for child
> windows but a popup window starts to receive WM_WINDOWPOSCHANGING and
> friends indicating that child windo
Oops, I inadvertently deleted this from the queue, sorry.
Robert Schuster wrote:
Dear Wine developers,
I wrote some guidelines that should help FOSS projects getting more
lively and lowering the barrier for new developers to join. You can find
them in form of a small manual here
http://projects.
"Jonathan Ernst" <[EMAIL PROTECTED]> wrote:
> Changelog:
> - localization of uninstaller
You should not localize WINE_ERR messages, encoding of strings
might be incompatible in Wine and underlying system.
Also, is it possible to use normal dialog for uninstaller's main
window? We could use conve
On Thursday 24 February 2005 14:50, Mike Hearn wrote:
> Paul van Schayck wrote:
> > Changelog:
> > As last option for drive type detection we try the device node name.
>
> Looks good but please try and use the same code style as in the rest of
> the program. In particular note that winecfg doesn't
Paul van Schayck wrote:
Changelog:
As last option for drive type detection we try the device node name.
Looks good but please try and use the same code style as in the rest of
the program. In particular note that winecfg doesn't use Hungarian
notation anywhere, eg "szNode" would just be "node" or
We found a simple solution (workaround?) to make this application
perform well under WINE. Typical running time of the linking process is
down from 30min to 15sec (!).
A short explanation: The TI linker allocates and frees a lot of small
buffers, typical size 24-32 bytes - but we have not seen
Mike McCormack <[EMAIL PROTECTED]> writes:
> ChangeLog:
> * fix SHSimpleIDListFromPath to do the correct thing for non-existing pathes
This is causing some test failures (and also some extra successes, I
guess we are on the right track...)
shelllink.c:177: Test succeeded inside todo block: path_
21 matches
Mail list logo
