The device is not ready; Access violation at address in modu

[BAHO87]

I hope somebody came across this problem in the past.

I installed WUFI 5.2 ORNL as recommended. My computer is Dell, 64bit, Windows 7. I installed the program and the database in the same folder WUFI on drive D:/.. (OS is on C:/ for the reference). The installation process went smoothly -- both the program and database.

However, when I am trying to open the program 'The device is not ready' message pop up (Fig.1). Once I click Ok, 'Access violation at address xyz in module 'WUFI.exe. Read of address xyz.'' (Fig.2), click Ok again. Then, the window -- that is the same as ABOUT WUFY in HELP -- does not disappear (Fig.3). Anything I do lead to 'Access violation..' again (Fig.4).

How do I resolve this issue?

Thank you very much in advance

tags: ORNL, The device is not ready, Access violation at address in module 'WUFI'. Read of address ...

[veitner]

I guess you have 64-bit Office installed. Please try to replace it with 32-bit version of MS-Office. Otherwise the database drivers could not be loaded (WUFI comes with a MS-ACCESS Database which will be replaced by a future version).

Regards,
Veit

[BAHO87]

Thank you very much for the reply. Indeed, you are right -- I have 64 bit version of MS Office. Can I remove just MS Access without removing the rest of 64xbit MS Office? Are there any work around? or must I replace 64bit Office Suite for 32bit one?

Respectfully,

IK

[veitner]

I don't think so. You will need to replace the whole office suite (http://answers.microsoft.com/en-us/offi ... 36da957dd5)

Veit

[BAHO87]

I uninstalled Office and installed 32-bit version. The program still does not want to run -- has the same issue. I re-install WUFI... The same thing. Then, I uninstalled Office again to find out if it was the issue in the first place... the same thing.

I would like to mention another piece of info that is maybe helpful. When I try to close WUFI, the same issue occurs. I have to force it through Task Manager. I am not sure if that helps though.

Could it be the leftovers of old Office in the Registry? Are there any other suggestions for the resolving this problem?

Thank you