Opened 12 years ago
Last modified 12 years ago
#88 new defect
Lotus Notes 8 no longer works
Reported by: | abwillis | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | general enhancement |
Component: | odin | Version: | 0.8.5 |
Severity: | medium | Keywords: | |
Cc: |
Description
Lotus Notes 8 had been working but I have not been able to determine exactly when it stopped working as I had not used it in some time and going back to 0.7.1 did not fix it either.
Change History (7)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Works last with 20110710 build. I tried backing out the changes except for:
- wgss: Add a hack to fix changing the current directory in CreateProcess
when starting the process of the same type.
I do know that Lotus Notes is creating processes at the point that it now dies... I am not sure how to back out the wgss changes to check that.
comment:3 by , 12 years ago
can you just take the previous wgss version from the Odin distro and try with it?
Regarding the call stack, try this under the debugger again, to get the proper call stack. It may reveal something.
comment:4 by , 12 years ago
When I put the old wgss50.dll in place I get a sys2070 due to something in odincrt.dll. 09-18-2012 13:57:51 SYS2070 PID 00d3 TID 0001 Slot 00b2 E:\ODIN\SYSTEM32\PE.EXE WGSS50->ODINCRT.839 182
This was even after placing the old wgss50.dll into bin, running kmk clean and then a fresh build (though best I can tell the wgss50.lib is created from the def file and not the dll file).
comment:5 by , 12 years ago
I haven't gleaned much from the debugger... it seems to crash in doscall1: XCPT_Access_Violation(unhandled) it starts at 23950202 and if the exception is run it goes through numerous 239xxxxx addresses until it comes to the invalid address of 00000000 in doscall1.
comment:6 by , 12 years ago
Changes in 0.8.6 did not help (not that there was an expectation, just an update).
comment:7 by , 12 years ago
I found that the old wgss50.dll fails due to missing exports in odincrt since 0.8. I put 0.7.1 in place to replace the wgss50.dll and this time 0.7.1 did work so it is not the wgss50.dll but a change related to 0.8 after all.
exception information from debug build: