[Bug 21790] 3D Rad demo "BeltBall" can't use its bundled mfc80u.dll (enhance assembly search sequence to include private assemblies in application subfolders)

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Sep 23 11:02:18 CDT 2013


http://bugs.winehq.org/show_bug.cgi?id=21790

--- Comment #7 from Nikolay Sivov <bunglehead at gmail.com> 2013-09-23 11:02:18 CDT ---
It seems to me that a problem with current code is that module file name is not
resolved correctly:

---
0025:trace:actctx:RtlCreateActivationContext 0x32f780 0000008a
0025:trace:actctx:RtlCreateActivationContext module=0x10000000
0025:trace:actctx:RtlCreateActivationContext appdir
init=L"C:\\USERS\\NSIVOV\\LOCAL SETTINGS\\APPLICATION DATA\\.#\\"
0025:trace:actctx:get_manifest_in_module looking for res #0002 in module
0x10000000 L"C:\\USERS\\NSIVOV\\LOCAL SETTINGS\\APPLICATION
DATA\\.#\\MBX at 24@48E1E8.###"
0025:trace:actctx:parse_manifest parsing manifest loaded from (null) base dir
(null)
...
0025:trace:actctx:lookup_assembly looking for name=L"Microsoft.VC80.MFC"
version=8.0.50727.762 arch=L"x86"
0025:warn:actctx:lookup_manifest_file no matching file for
L"x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.*.*_*_*.manifest"
0025:trace:actctx:lookup_assembly appdir=L"C:\\USERS\\NSIVOV\\LOCAL
SETTINGS\\APPLICATION DATA\\.#\\"
0025:trace:actctx:lookup_assembly try 0 - L"C:\\USERS\\NSIVOV\\LOCAL
SETTINGS\\APPLICATION DATA\\.#\\\\Microsoft.VC80.MFC.dll"
0025:trace:actctx:lookup_assembly try 0 - L"C:\\USERS\\NSIVOV\\LOCAL
SETTINGS\\APPLICATION DATA\\.#\\\\Microsoft.VC80.MFC.manifest"
0025:trace:actctx:lookup_assembly try 1 - L"C:\\USERS\\NSIVOV\\LOCAL
SETTINGS\\APPLICATION DATA\\.#\\\\Microsoft.VC80.MFC\\Microsoft.VC80.MFC.dll"
0025:trace:actctx:lookup_assembly try 1 - L"C:\\USERS\\NSIVOV\\LOCAL
SETTINGS\\APPLICATION
DATA\\.#\\\\Microsoft.VC80.MFC\\Microsoft.VC80.MFC.manifest"
0025:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.MFC" (8.0.50727.762)
---

This is a log with some additional TRACEs I added.

(In reply to comment #3)
> 
> The dll in question that has the MFC binding is not directly visible in
> filesystem but mapped in memory.
> 
> MBX at 28@48E1E8_### (2 KiB in AppData folder) -> "C:\3D RAD GAMES\BELTBALL
> V102\dll3impact.dll" (not present on disk)
> 

Hi, Anastasius.

Where does this module name come from? So far incorrect path is the only
problem that breaks dependency lookup.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list