[wine 1.1.2] [openSuSE 10.2, kernel 2.6.21-rc6]
Folks,
I try to make run a German software bundle called `IDU Verwaltung'. It seems to work, however, I can't make it to connect to a PostgreSQL database. I have enabled PostgreSQL access in my firewall.
Interestingly, I couldn't find information how to debug networking problems with wine. Any links?
Whatever, here my problem report. I tried on wine-users first, but the responses weren't really encouraging.
I've executed
WINEDEBUG=warn+all wine Idu_Verwaltung.exe 2> ~/winelog.warnall
[within a fresh .wine, not installing any vcredist_x86.exe bundle -- doing this doesn't solve the `actctx' problem which is listed below, BTW]
Doing
cat winelog.warnall \ | grep -v 'c000003[45]' \ | grep -v 'not found' \ | grep -v 'case-insensitive' \ | grep -i -v 'failed to load' \ | grep -v 'cannot open' \ | grep -v 'no-exec' \ | grep -v 'Invalid handle' \ | grep -v 'font' \ | grep -v 'vkey' \ | grep -v 'keysyms' \ | grep -v 'Heap' \ | grep -v 'Bitmap' \ | grep -v 'GetDC'
gives
warn:sync:SetNamedPipeHandleState stub: 0x24 0x7edca5a8/2 (nil) (nil) warn:msvcrt:msvcrt_init_console :Console handle Initialisation FAILED! warn:class:CLASS_RegisterClass Win extra bytes 44 is > 40 warn:class:CLASS_RegisterClass Win extra bytes 44 is > 40 warn:winspool:WINSPOOL_GetDWORDFromReg Got ret = 2 on name dnsTimeout warn:winspool:WINSPOOL_GetDWORDFromReg Got ret = 2 on name txTimeout warn:winspool:WINSPOOL_GetDWORDFromReg Got ret = 2 on name dnsTimeout warn:winspool:WINSPOOL_GetDWORDFromReg Got ret = 2 on name txTimeout warn:mixer:getcomponenttype Unknown mixer name Capture Mux, probably harmless warn:mixer:getcomponenttype Unknown mixer name Capture Mux, probably harmless warn:class:CLASS_RegisterClass Win extra bytes 44 is > 40 warn:actctx:lookup_manifest_file no matching file for L"x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.*.*_*.manife fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" warn:module:process_attach Initialization of L"MSVCR80.dll" failed warn:combo:ComboWndProc_common unknown msg WM_USER+ba10 wp=460001 lp=00030046 warn:file:CreateFileW Unable to create file L"\\.\Z:" (status c0000022) warn:combo:ComboWndProc_common unknown msg WM_USER+ba10 wp=420001 lp=00060042 warn:combo:ComboWndProc_common unknown msg WM_USER+ba10 wp=4c0001 lp=0009004c warn:driver:CloseDriver Failed to close driver warn:driver:CloseDriver Failed to close driver warn:driver:CloseDriver Failed to close driver warn:driver:CloseDriver Failed to close driver warn:driver:CloseDriver Failed to close driver warn:profile:PROFILE_FlushFile No current profile!
The only messages related to networking are those winspool things which doesn't say anything to me. Any idea how to proceed?
Werner
PS: In case you still have any FreeType issues in Wine, ask me :-)
Werner LEMBERG wrote:
[wine 1.1.2] [openSuSE 10.2, kernel 2.6.21-rc6]
Folks,
I try to make run a German software bundle called `IDU Verwaltung'. It seems to work, however, I can't make it to connect to a PostgreSQL database. I have enabled PostgreSQL access in my firewall.
How are you connecting to the PostgreSQL DB, ADO, ODBC? From pass experience, wine needs to be in win98 mode for odbc.
Interestingly, I couldn't find information how to debug networking problems with wine. Any links?
Whatever, here my problem report. I tried on wine-users first, but the responses weren't really encouraging.
I would log a bug report, and attached a log.
Best Regards Alistair Leslie-Hughes
Hi Werner, fancy seeing you in a different list... I was wondering why you do warn+all (not very useful). I would be doing +relay or +odbc or one of the others. Here is a useful link:
http://wiki.jswindle.com/index.php/Wine_Debug_Channels
--- On Thu, 7/8/08, Werner LEMBERG wl@gnu.org wrote:
[wine 1.1.2] [openSuSE 10.2, kernel 2.6.21-rc6]
Folks,
I try to make run a German software bundle called `IDU Verwaltung'. It seems to work, however, I can't make it to connect to a PostgreSQL database. I have enabled PostgreSQL access in my firewall.
Interestingly, I couldn't find information how to debug networking problems with wine. Any links?
<snipped>
WINEDEBUG=warn+all wine Idu_Verwaltung.exe 2> ~/winelog.warnall
<snipped>
__________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
Hi Werner, fancy seeing you in a different list...
:-)
I was wondering why you do warn+all (not very useful). I would be doing +relay or +odbc or one of the others.
Hrmpf. Using WINEDEBUG=+relay gives me a 237MByte log file, using WINEDEBUG=+warn:relay produces nothing (except the unrelated actctx message). Is there anything between these two extremes?
WINEDEBUG=+odcb gives the following:
trace:odbc:DllMain Initializing or Finalizing proxy ODBC: 0x7e570000,1,0x1 trace:odbc:DllMain Loading ODBC... trace:odbc:ODBC_LoadDriverManager trace:odbc:SQLAllocEnv trace:odbc:SQLAllocEnv Returns ret=0, Env=7c0c5fd8 trace:odbc:ODBC_ReplicateODBCInstToRegistry Driver settings are not currently replicated to the registry trace:odbc:SQLDrivers trace:odbc:SQLDataSources EnvironmentHandle = 0x7c0c5fd8 trace:odbc:SQLDataSources returns: 100 DataSource = ~Ø_ |, Description = trace:odbc:SQLDataSources EnvironmentHandle = 0x7c0c5fd8 trace:odbc:SQLDataSources returns: 100 DataSource = ~Ø_ |, Description = trace:odbc:SQLFreeEnv (Env=7c0c5fd8) trace:odbc:SQLFreeEnv Returns 0 fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" trace:odbc:DllMain Initializing or Finalizing proxy ODBC: 0x7e570000,0,0x1 trace:odbc:DllMain Unloading ODBC...
Werner
On Thursday 07 August 2008 10:33:28 Werner LEMBERG wrote:
I try to make run a German software bundle called `IDU Verwaltung'. It seems to work, however, I can't make it to connect to a PostgreSQL database. I have enabled PostgreSQL access in my firewall.
Interestingly, I couldn't find information how to debug networking problems with wine. Any links?
If your software really is trying to use winsock to access the database, try running it with "WINEDEBUG=+winsock wine app.exe" to log the winsock calls that are being made.
Cheers, Kai
If your software really is trying to use winsock to access the database, try running it with "WINEDEBUG=+winsock wine app.exe" to log the winsock calls that are being made.
This gives
trace:winsock:DllMain 0x7e6a0000 0x1 0x1 trace:winsock:WSAStartup verReq=202 trace:winsock:WSAStartup succeeded trace:winsock:DllMain 0x7e6a0000 0x2 (nil) fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" trace:winsock:DllMain 0x7e6a0000 0x3 (nil) trace:winsock:WSAStartup verReq=2 trace:winsock:WSAStartup succeeded trace:winsock:DllMain 0x7e6a0000 0x2 (nil) trace:winsock:DllMain 0x7e6a0000 0x2 (nil) trace:winsock:DllMain 0x7e6a0000 0x0 0x1
Looks rather innocent to me.
Werner
Werner LEMBERG wrote:
If your software really is trying to use winsock to access the database, try running it with "WINEDEBUG=+winsock wine app.exe" to log the winsock calls that are being made.
This gives
trace:winsock:DllMain 0x7e6a0000 0x1 0x1 trace:winsock:WSAStartup verReq=202 trace:winsock:WSAStartup succeeded trace:winsock:DllMain 0x7e6a0000 0x2 (nil) fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" trace:winsock:DllMain 0x7e6a0000 0x3 (nil) trace:winsock:WSAStartup verReq=2 trace:winsock:WSAStartup succeeded trace:winsock:DllMain 0x7e6a0000 0x2 (nil) trace:winsock:DllMain 0x7e6a0000 0x2 (nil) trace:winsock:DllMain 0x7e6a0000 0x0 0x1
Looks rather innocent to me.
It is probably irrelevant, but something is looking for the visual C 8 runtime and not finding it. You can install VC80 runtime with winetricks.
Hin-Tak
It is probably irrelevant, but something is looking for the visual C 8 runtime and not finding it. You can install VC80 runtime with winetricks.
Well, the program comes with a setup for VC80 files (which I intentionally haven't installed to make Wine debugging easier due to non-tainting -- at least I hope this; please correct me if I'm wrong). However, the message doesn't disappear.
Werner
This discussion really would be better taken up in bugzilla. --Juan
This discussion really would be better taken up in bugzilla.
Fortunately, it isn't necessary. Running an updated version of IDU, I can continue, so maybe the version I tried first was buggy.
Werner
--- On Thu, 7/8/08, Werner LEMBERG wl@gnu.org wrote:
From: Werner LEMBERG wl@gnu.org Subject: Re: Networking problems with IDU Verwaltung software To: hintak_leung@yahoo.co.uk Cc: wine-devel@winehq.org Date: Thursday, 7 August, 2008, 11:33 PM
It is probably irrelevant, but something is looking for
the visual C
8 runtime and not finding it. You can install VC80
runtime with
winetricks.
Well, the program comes with a setup for VC80 files (which I intentionally haven't installed to make Wine debugging easier due to non-tainting -- at least I hope this; please correct me if I'm wrong). However, the message doesn't disappear.
Glad to hear that you have sorted out the problem with a new version of the application. I think the general rule is that if wine doesn't provide some component (such as mfc and vc++ 80), using winetricks to install the additional components is preferred over installing application's bundled additional installers.
As for debugging problems with applications, the most useful and concise advice I have read is actual this - I looked for it earlier but couldn't find it because the web page has a strange name :-): http://www.winehq.org/site/developer-cheatsheet
it explains +relay and +snoop quite well, which are the first two things one normally do, I think.
__________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
Glad to hear that you have sorted out the problem with a new version of the application. I think the general rule is that if wine doesn't provide some component (such as mfc and vc++ 80), using winetricks to install the additional components is preferred over installing application's bundled additional installers.
OK. As mentioned before, I explicitly looked into Winetricks, and for that particular VC++ runtime library version it does an ordinary install and nothing else.
As for debugging problems with applications, the most useful and concise advice I have read is actual this - I looked for it earlier but couldn't find it because the web page has a strange name :-): http://www.winehq.org/site/developer-cheatsheet
Aah. Indeed, this helps. A minor things: I can read
Investigate the RelayInclude and RelayExclude string values in [HKCU\Software\Wine\Debug] if you're being overwhelmed by certain functions. [...]
I suppose this is a registry entry, right? (I normally don't use Windows, so I'm not too acquainted with that.) Perhaps one or two sentences can be added to mention this, together with an explanation which program should be used to change those settings.
Werner
On Fr, 2008-08-08 at 16:51 +0200, Werner LEMBERG wrote:
Investigate the RelayInclude and RelayExclude string values in [HKCU\Software\Wine\Debug] if you're being overwhelmed by certain functions. [...]
I suppose this is a registry entry, right?
Yes. HKCU (or HCU) is: HKEY_CURRENT_USER
Perhaps one or two sentences can be added to mention this, together with an explanation which program should be used to change those settings.
You change the registry with: regedit (wine provide an own implementation)
Patches are welcome. The source of the website is managed with git: http://source.winehq.org/git/website.git (templates/en/*)
Thanks for helping Wine
You change the registry with: regedit (wine provide an own implementation)
Patches are welcome.
The source of the website is managed with git: http://source.winehq.org/git/website.git (templates/en/*)
No time for doing that. However, here's a patch which improves the wording a bit I hope.
Werner
======================================================================
--- developer-cheatsheet.htm~ 2008-08-09 15:51:58.000000000 +0200 +++ developer-cheatsheet.htm 2008-08-09 15:53:16.000000000 +0200 @@ -684,8 +684,10 @@ calls between Wine DLLs: for instance, from GDI32 to KERNEL32. Investigate the RelayInclude and RelayExclude string values in [HKCU\Software\Wine\Debug] if you're being - overwhelmed by certain functions. A good initial value for - RelayExclude is:<p> + overwhelmed by certain functions. (‘HKCU’ stands + for the ‘HKEY_CURRENT_USER’ tree in the Windows + registry; you can edit it with the command ‘wine + regedit’.) A good initial value for RelayExclude is:<p>
<code> RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel;_LeaveSysLevel; _CheckNotSysLevel;RtlAllocateHeap;RtlFreeHeap;LOCAL_Lock;LOCAL_Unlock
-
Alistair Leslie-Hughes -
Detlef Riekenberg -
Hin-Tak Leung -
Hin-Tak Leung -
Juan Lang -
Kai Blin -
Werner LEMBERG