Windows Messenger Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Windows Messenger 5.0 - Rambling Install Thoughts

Well I've dabbled with this product for some time now. Some of what follows are my recollections from previous stabs, some is from my current run. I will attempt to add comments here as I try new things in a timely manner.

The install of this product is completely broken. If you don't declare a winver=winxp or win2k, the install program will pop up a warning that you are not running on the correct OS. That was the only visual window I have ever seen. Once the Windows version is set to winxp it goes down hill. I believe the major issue is the msi.dll. On my system running:

/home/cxoffice/cxoffice/bin/wine '--debugmsg=+loaddll' '--winver=winxp' '/home/cxoffice/cxoffice/support/templates/dotwine/fake_windows/Temp/install.exe'

ends up complaining about msi.dll as follows:

trace:loaddll:load_dll Loaded module L"Z:\\mnt\\nt\\WINDOWS\\system32\\imm32.dll" : builtin
trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\RPCRT4.dll" : native
trace:loaddll:load_dll Loaded module L"Z:\\mnt\\nt\\WINDOWS\\system32\\msi.dll" : native
fixme:advapi:SetThreadToken ((nil), (nil)): stub (NT impl. only)
fixme:advapi:SetThreadToken ((nil), 0x40): stub (NT impl. only)
trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\COMCTL32.dll" : builtin
trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\OLE32.DLL" : builtin
fixme:ntdll:NtAdjustPrivilegesToken (0x6c,0x00000000,0x410af004,0x00000000,(nil),(nil)),stub!
fixme:ntdll:NtAdjustPrivilegesToken (0x6c,0x00000000,0x410af004,0x00000000,(nil),(nil)),stub!
fixme:powermgnt:SetThreadExecutionState (0x80000001): stub, harmless.
fixme:powermgnt:SetThreadExecutionState (0x80000000): stub, harmless.
fixme:advapi:RegisterEventSourceW ((null),L"MsiInstaller"): stub
err:eventlog:ReportEventW L"C:\\Windows\\Temp\\IXP001.TMP\\Messenger.Msi"
err:eventlog:ReportEventW L"(NULL)"
err:eventlog:ReportEventW L"(NULL)"
err:eventlog:ReportEventW L"(NULL)"
err:eventlog:ReportEventW L"(NULL)"
err:eventlog:ReportEventW L"(NULL)"
err:eventlog:ReportEventW L"(NULL)"
fixme:advapi:DeregisterEventSource (0x1): stub
trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\comctl32.dll" : builtin
trace:loaddll:MODULE_FlushModrefs Unloaded module L"Z:\\mnt\\nt\\WINDOWS\\system32\\msi.dll" : native

I haven't posted any config file but I believe that I was heavily using native dll's. If anyone is curious about this output I'll see if I can answer questions about how I got this far. I was never able to get further than the data above. I believe I read something somewhere that indicated that msi.dll was a problem in Crossover currently so I didn't dig much more.

More on next message,
P. David Schaub

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzM4NzIzMjIwLCJjc3JmX3Rva2VuIjoiS1ByVXhhWEJROVZ0THV4SCIsImdkcHIiOjB9