http://bugs.winehq.org/show_bug.cgi?id=22763
cindy sweettarts82@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1
--- Comment #2 from cindy sweettarts82@yahoo.com 2010-05-19 13:59:42 --- first of I want to thank you, I called the NBME test software distributors and they were not even able to provide me with any assistance.
I have done all the things you have said, and it worked to the extend that i can actually see what's on the screen the display (no more white screen), but i still can not use the program. When I use the cursor (to click on) any answers or any of the buttons, it disappears. It is visible on the periphery of the screen but not in the area where it is actually necessary.
if you can provide me with any further assistance it will be greatly appreciated.
Thank you once again
(In reply to comment #1)
There are a couple of problems that I can see after installing the step 3 practice exam within a clean Wine prefix on wine-1.1.44-290-g7d3cb53:
- Assuming that wine-gecko is already installed, starting a practice exam
yields a white screen and the output:
err:ole:CoGetClassObject class {48123bc4-99d9-11d1-a6b3-00c04fd91555} not registered err:ole:CoGetClassObject class {48123bc4-99d9-11d1-a6b3-00c04fd91555} not registered err:ole:CoGetClassObject no class object {48123bc4-99d9-11d1-a6b3-00c04fd91555} could be created for context 0x3
Using winetricks to install msxml3 works around this problem.
- The msxml3 redist doesn't suppress all of the missing interface errors, as I
see:
err:ole:create_server class {88d969c0-f192-11d4-a65f-0040963251e5} not registered err:ole:CoGetClassObject no class object {88d969c0-f192-11d4-a65f-0040963251e5} could be created for context 0x5
Installing the msxml4 redist makes this go away.
- More importantly, after installing the msxml redists, launching the exam
gives me the message:
"A Fatal error has occurred accessing content: js/yui/close12_1.gif: 'js/yui/close12_1.gif' is not a valid integer value"
To work around this, I installed IE6 using the winetricks script, eschewing the wine-gecko renderer.
In summary, the quickest workaround to get the application immediately working is, starting with a clean Wine prefix, to use the winetricks script (http://wiki.winehq.org/winetricks) to do winetricks msxml3 msxml4 ie6. That seems to get the test interface more or less operable.