WIN500 and WINE under Linux -- No Love

Status
Not open for further replies.

MOGA

Member
Joined
Sep 18, 2009
Messages
132
Location
Roswell, GA
I have spent the last few hours learning everything that I can about MFC42.DLL problems as it relates to WINE/WIN500 installs. I've followed the instructions at the excellent RR reference on the subject, found HERE to get WIN500 working with WINE. Following the step by step process referenced above, I'm unable to get dotnet1.1 installed using winetricks. The command line error reads:

Note: command 'wine /home/my_user_name/.cache/winetricks/dotnet11/dotnetfx.exe' returned status 5. Aborting.


Calling WIN500_COM.exe subsequently returns this output:

Cannot find import; DLL may be missing, corrupt, or wrong version File “MFC42.DLL,” error 126


This is the error that WINE initially generated which led to my study of WINE/WIN500 issues.

I assume that the failed MS NET 1.1 install and the inability of my machine to initialize WIN500 are related? OR are they two distinct challenges that require a solution?

BTW, the last line that's visible in console before the MS NET install breaks is as follows:

wine: Unhandled page fault on read access to 0x2d987940 at address 0x2d987940 (thread 0039), starting debugger...

The wine message box reads: the program install.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience.


I am way out of my league here. Can anyone give me insight into what is happening? I have the impression that those are memory addresses from the CLI output but I'm not really sure. Does it matter that I apparently have dotnet1.0, 2.0, and 4.0 also installed?

My machine uses Fedora 13, Wine 1.3.7, and the latest version of WIN500. Athlon II quad-core box and 4 GB 1600 DDR3. Any help is greatly appreciated.
 

MOGA

Member
Joined
Sep 18, 2009
Messages
132
Location
Roswell, GA
Also picked this out from the CLI output:

<snip>

Executing wine /home/Moussa/.cache/winetricks/dotnet11/dotnetfx.exe

fixme:storage:create_storagefile Storage share mode not implemented.

fixme:advapi:LookupAccountNameW (null) L"Moussa" (nil) 0x33e824 (nil) 0x33e828 0x33e81c - stub

fixme:advapi:LookupAccountNameW (null) L"Moussa" 0x171fe8 0x33e824 0x176dc0 0x33e828 0x33e81c - stub

fixme:msi:ACTION_CustomAction Deferring rollback only action... rollbacks not supported yet

fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 66 ignored L"MsiAssembly" table values

wine: Unhandled page fault on read access to 0x4801f940 at address 0x4801f940 (thread 0039), starting debugger...

Unhandled exception: page fault on read access to 0x4801f940 in 32-bit code (0x4801f940).

Register dump:

<snip>


Could the info in bold be a hint of what's causing the failure?
 

MOGA

Member
Joined
Sep 18, 2009
Messages
132
Location
Roswell, GA
Downloaded the offending file, dotnetfx.exe, from Microsoft and executed it instead of the version that's distributed by winetricks. Net1.1 Install completed. Also updated WINE to ver1.3.8. Running WIN500_COM.exe with WINE program loader now results in the following error:

Cannot find import; DLL may be missing, corrupt, or wrong version File “MFC42.DLL,” ordinal 6785 (error 0)

There isn't a match anywhere on Google for that message :|
 

MOGA

Member
Joined
Sep 18, 2009
Messages
132
Location
Roswell, GA
Replaced the offending link library file native to WINE with one from dlldump.com -- seems that I have the problem with MFC42 sorted. Now I have a new error message with another file as the culprit: MSVCP60.dll
 

MOGA

Member
Joined
Sep 18, 2009
Messages
132
Location
Roswell, GA
After manually placing MSVCP60.dll in the system32 file of WINE, I was left with a memory error. A little tweaking of my system's BIOS, specifically as it relates to how the two memory controllers on my MB interact, cleared that up. Finally I have a working install of WIN500 to evaluate!

EDIT: Oops, spoke too soon. Experiencing a communications problem between the radio and workstation now. At least the software is up and working :)
 
Last edited:

MOGA

Member
Joined
Sep 18, 2009
Messages
132
Location
Roswell, GA
Last step: make sure your user has privileges to read/write to the device that's controlling the USB link. Until I added my user to the appropriate group, my workstation couldn't detect the connection between the radio and the PC.
 
Status
Not open for further replies.
Top