http://bugs.winehq.org/show_bug.cgi?id=7649
------- Additional Comments From focht(a)gmx.net 2007-08-05 04:00 -------
Hello,
see my comments in http://bugs.winehq.org/show_bug.cgi?id=8306
1. implement partial context (or use my short-circuit patch, restoring full context)
2. kernel32.dll/.so export directory module name must be uppercase ("KERNEL32.dll")
With that changes, the software protection is happy now.
Application starts fine with above fixes.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8306
------- Additional Comments From focht(a)gmx.net 2007-08-05 03:50 -------
Hello,
yeah my PE editor picked up the placeholder not the kernel32.dll.so :|
I verified with windows kernel32.dll exports directory entry finally found the
cause.
Windows kernel32.dll export directory module name is UPPERCASE:
--- snip ---
KERNEL32.dll ActivateActCtx AddAtomA AddAtomW AddConsoleAliasA AddConsoleAliasW
AddLocalAlternateComputerNameA AddLocalAlternateComputer
...
--- snip ---
Where wine is lowercase.
The protector compares with the uppercase version.
I patched my kernel32.dll.so entry to uppercase.
Voila the application starts now with splash screen (though it crashes later due
to other wine issues, not related to protections)
You have to modify the build scripts to generate uppercase module name entry, or
this kind of protections wont work.
This currently only applies to kernel32.dll module.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8306
------- Additional Comments From julliard(a)winehq.com 2007-08-05 02:59 -------
> This never happens on windows, because kernel32.dll has a valid export directory
> and module name entry there.
Wine certainly has a valid export directory and module name too. There must be
something else it doesn't like.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7342
------- Additional Comments From damjan.jov(a)gmail.com 2007-08-05 02:13 -------
Bryan, that commit was just the stub for MAPIAdminProfiles that you already tried.
>From what I can see, MAPI32.DLL is the component that does those nasty
undocumented encrypted RPCs to the Exchange server. It's a lot of work and I
don't think it will be working in wine any time soon.
The OpenChange project is working on a library that will do what MAPI32 does,
but it's licensed under the GPL, which is incompatible with wine's LGPL, so
that's useless to us.
For now, your best shot is to get Windows's MAPI32.DLL working on wine. Please
copy MAPI32.DLL from your Windows installation and try putting a native override
for it in winecfg (like before), but this time also type "regsvr32 MAPI32.DLL"
once from the directory that it's in, and then try running Outlook.
And can I finally ask why you're running Outlook (and version 97, of all
things!) instead of something like Evolution?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8314
------- Additional Comments From dmitry(a)codeweavers.com 2007-08-05 01:28 -------
Following you comments I already have a test case that confirms your findings.
Many thanks for your helpful comments.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8314
------- Additional Comments From emwine(a)earthlink.net 2007-08-05 01:22 -------
Um, I'm new to wine bug reports, but I anticipate doing more. I already see
things I could have done to make things easier for you.
Would it help if I attached the winboard.c file containing the code fragment
along with my log? What about attaching the EXE so you can see the log output
differences between Windows and wine?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8314
------- Additional Comments From emwine(a)earthlink.net 2007-08-05 00:54 -------
I built the .EXE from source and added a log in ConsoleWndProc() from the same
file as the in the bugreport. I added it right underneath "case WM_INITDIALOG".
In windows, only one entry is generated. In wine, two are generated. If I
comment out the SendMessage(), then in windows, no entry is generated (with no
window created either, but no crash), and in wine it works properly.
I don't have a test case because, frankly, I don't get how calling
CreateDialog() should work at all with those arguments. heh.
Probably irrelevant, but I used MSVC 6.0. "nmake /f msvc.mak" in the winboard
source directory.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3743
ead1234(a)hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #3355 is|0 |1
obsolete| |
------- Additional Comments From ead1234(a)hotmail.com 2007-07-05 23:54 -------
Created an attachment (id=6172)
--> (http://bugs.winehq.org/attachment.cgi?id=6172&action=view)
+all, showing same infinite loop
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.