Here are some kludgy patches (against the current WineHQ CVS) that's
supposed to make InstallShield 6 with its stupid interprocess COM sort of
work, but it doesn't for some reason, probably because of something else
in Wine that's broken... and because of a lack of time, I think I really
need some debugging assistance.
Most of these patches are too ugly to be submitted to the official wine
as-is, I'll clean these parts up later, but probably not before
InstallShield has been debugged and actually works with these hacks.
To make this run, you need to copy stdole32.tlb from a real windows and
put into c:\windows\system. Then run your favorite InstallShield 6
setup.exe and wait for it to crash. --debugmsg +ole is recommended. It
crashes for me after about 25 remote method calls. If you find out why,
let me know. Please.
Dear Wine Developers,
Due to resource constraints (75 MHz processor, 1.2 GB hard drive, 16 MB
RAM), we recently replaced Windows98 on our daughter's PC with Linux
Mandrake, using the IceWM window manager. It isn't quite as flashy as
Windows, but it boots beyond the startup screen, which is more than can be
said for Win98.
Well, to make a long story short, I've installed and configured Wine
following the instructions in the Wine User's Guide. Everything seems to
be working properly, but when I attempted to run the setup.exe for 'Jim
Henson Muppets Letters: Capital & Small', I received the following errors:
err:ddeml:DdeConnect .. but no Server window available
err:ddeml:DdeClientTransaction Invalid conversation handle
err:ddeml:DdeClientTransaction Invalid conversation handle
err:ddeml:DdeClientTransaction Invalid conversation handle
fixme:ddeml:DdeUninitialize16 stub calling DdeUninitialize
Following the recomendations in the Wine User's Guide, section 3.2
(Installing Wine Without Windows), I re-ran wine with --debug msg
+module,+file. I didn't see anything in the trace that jumped out at me,
but I've attached it here, just in case it means something to someone else.
One last thing. The setup.exe appears to be a 16-bit app, originally
designed for Windows 3.1. Not sure if that makes any difference or not.
Any help in resolving this would be greatly appreciated.
Regards,
Ian D. Stewart
--
"God may have mercy. We will not."
--Senator John S. McCain (R-AZ)
I'm trying to get Civ2 to run under wine (checked out via CVS today),
and I've run into a particular problem. The installation is totally
stand-alone -- all DLLs are built-in.
I get an invalid page fault in X11DRV_GetDC [winpos.c:441], at the line
which says:
drawable = data->client_window
Some debugger work shows that data is NULL. Now, the backtrace shows
that we get *here* from a call to WIN_GetMinMaxInfo from CreateWindowEx
[win.c:885]. The problem, as I see it, is that
USER_Driver.pCreateWindow doesn't get called until [win.c:922] -- in
other words, when the callback inside Civ2 receives the
WM_GETMINMAXINFO, it tries acquiring a DC for some reason, and this
causes the crash.
Now, I don't know enough about how wine works internall to fix this.
Can anyone provide any suggestions?
--
Luke Stras <stras(a)utias.toronto.edu>
"The meek can have the Earth; the rest of us have other plans"
--Henry Spencer
At 03:11 AM 29/09/2001 -0700, you wrote:
>> Probably only that there's a problem with your setup. For example, perhaps
>> you forgot to copy stdole32.tlb from real windows, as instructed?
>
>
> No , I did that..
Well, did you import all the registry entries in winedefault.reg then ?
Gerard
> 51145 096d4e18:Call x11drv.MsgWaitForMultipleObjectsEx(00000001,403faec4,ffffffff,00000000,00000000) ret=406c7efd
can you check that at this point (DWORD*)0x403faec4 points to the handle of the event created above ? (0x7C IIRC)
if it's the case, it means that the started program rely on some messages order to do some stuff
the expected behavior would be for the second program to set the event (7c) under certain circumstances, which shall be triggered from a given message...
A+
---------------
Eric Pouech
(http://perso.wanadoo.fr/eric.pouech/)
The future will be better tomorrow,
Vice President Dan Quayle
__________________________________________________
Voila vous propose une boite aux lettres gratuite sur Voila Mail:
http://mail.voila.fr
"Ilya Konstantinov" <wine-patches(a)future.shiny.co.il> wrote:
> This patch adds a _NET_WM_NAME(UTF8_STRING) property to every window,
> storing it's title in non-ambigous UTF8 encoding. This is a part of the
> NET_WM standard. The UTF8 title feature is currently implemented only
> by KWin (KDE's window manager), but is adopted by both GNOME and KDE
> camps.
@@ -746,12 +748,32 @@ BOOL X11DRV_SetWindowText( HWND hwnd, LP
return FALSE;
}
WideCharToMultiByte(text_cp, 0, text, -1, buffer, count, NULL, NULL);
+
+ count = utf8_wcstombs(text, strlenW(text), utf8_buffer, 0);
Why didn't you use win32 call instead of a purely internal one?
count = WideCharToMultiByte( CP_UTF8, 0, text, -1, NULL, 0, NULL, NULL );
utf8_buffer = HeapAlloc( GetProcessHeap(), 0, count );
count = WideCharToMultiByte( CP_UTF8, 0, text, -1, utf8_buffer, count, NULL, NULL );
--
Dmitry.
I am trying to install Wine on UltraSPARC Solaris 8.0
using tools/wineinstall. The installation script fails
at following point......
gcc -c -I. -I. -I../../include -I../../include -g -O2
-Wall -D__WINE__ -D_REENTRANT -I/usr/openwin/include
-o lex.ppl.o lex.ppl.c
In file included from ./ppl.l:141:
../../include/config.h:486: warning:
`_FILE_OFFSET_BITS' redefined
/usr/include/sys/feature_tests.h:96: warning: this is
the location of the previous definition
./ppl.l: In function `pplex':
./ppl.l:336: `pplval' undeclared (first use in this
function)
./ppl.l:336: (Each undeclared identifier is reported
only once
./ppl.l:336: for each function it appears in.)
make: *** [lex.ppl.o] Error 1
Can anybody suggest how to fix this??
Thanks
Mrugan
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com
Can someone tell me what we should have here? (It might be interesting to
know how it's supposed to work too but that's beside the point).
I had a case where pthread_atfork was being called with two null pointers,
so it all blew up when PTHREAD_FORK tried to execute the code they pointed
to.
Is it legal for pthread_atfork to be called with null parameters (in which
case I will correct PTHREAD_FORK, otherwise I'll assert the pointers).
Bill
