> 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
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_CUR
> 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 bu
--- On Thu, 7/8/08, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> From: Werner LEMBERG <[EMAIL PROTECTED]>
> Subject: Re: Networking problems with IDU Verwaltung software
> To: [EMAIL PROTECTED]
> Cc: wine-devel@winehq.org
> Date: Thursday, 7 August, 2008, 11:33 PM
&g
> 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
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 0x7e6a 0x1 0x1
> trace:winsock:WSAStartup
This discussion really would be better taken up in bugzilla.
--Juan
> 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 --
> 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 unrela
> 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 0x7e6a 0x1 0x1
trace:winsock:WSAStartup verReq=202
trace:winsock:WSAStar
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 <[EMAIL PROTECTED]>
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 i
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.
Ho
[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 informatio
14 matches
Mail list logo
