On Tue, Jul 25, 2000 at 10:56:25PM +0400, Stas Sergeev wrote:
Alexandre Julliard ?:
Thanks for the trace, I see what the problem is now. Could you please
try this patch?
Index: loader/task.c
Yes, this patch works perfectly (only together with the first one!).
The problem is solved,
Stas Sergeev [EMAIL PROTECTED] writes:
No; there can be several 16-bit tasks running inside the same process,
so we cannot simply use the first task name as the process name. The
OK, thanks for the explanation. But anyway, why argv[0]?
When Wine runs 16Bit programs, its own module name is
Alexandre Julliard ÐÉÛÅÔ:
Thanks for the trace, I see what the problem is now. Could you please
try this patch?
Index: loader/task.c
Yes, this patch works perfectly (only together with the first one!).
The problem is solved, thanks.
Alexandre Julliard ÐÉÛÅÔ:
And when creating 32-bit process, it does
if (main_module) PROCESS_Start( main_module, main_exe_name );
_^^^No problems here.
My fix was to replace this NULL with main_exe_name for 16-bit processes
too. It works for
WINE deals incorrectly with process's names. This prevents some
programs from working. I think that the bug is here:
scheduler/process.c:
static void PROCESS_Start( HMODULE main_module, LPSTR filename )
{
if (!filename)
{
/* if no explicit filename, use argv[0] */
if
