Hi

 

I have checked my Win 7 64bit system and have found that ole2.dll, plus 
ole2nls.dll and ole2disp.dll, live in C:\Windows\SysWOW64. The SysWOW64 
subsystem is a thin interface to enable 32bit Windows applications to be able 
to access the equivalent interfaces in the 64bit systems, and has been around 
since WinXP 64bit. These files are all dated as 10 Jun 2009 with, for the 
ole2.dll, a description of OLE 2.1 16/32 Interoperability Library, version 
2.10.35.35, size 41.5KB. If they are corrupted then sfc should find and fix 
them.

 

It also looks that on a Win 32bit system it normally lives in 
c:\windows\system32, and possibly c:\windows\system32\dllcache, but was moved 
to SysWOW64 for the 64bit system. The file should also be registered and the 
error can occur if an installation is trying to reinstall it. That used to be a 
major issue in older versions of Windows, especially with Microsoft files being 
installed outside of the c:\windows tree. 

 

C:\Program Files (x86) is the version of C:\Program Files used for 32bit 
applications and is now a protected folder, since WinXP or Win2000, so that 
applications cannot easily write to it That is why Legacy 7.5 and earlier 
versions used the C:\Legacy folder.

 

I have Legacy 8, full version, running happily on both my 64bit Win7 desktop 
and my 32bit Win10 laptop.

 

Regards

 

Chris

 

From: LegacyUserGroup [mailto:[email protected]] On 
Behalf Of Cathy Pinner
Sent: 24 February 2017 00:45
To: Legacy User Group <[email protected]>
Subject: Re: [LegacyUG] Unable to install Legacy7 or 8 free editions - Any tips?

 

Tony,

Legacy 7 installs by default to C:\Legacy. It can be installed to any folder 
but NOT within the Program Folders. That's because Legacy 7.5 and earlier 
constantly write to the Legacy program folder.

Legacy 8 installs by default to Program Files (x86)\Legacy8\

Doing a system file check may help recover the ole2.dll
Here's a Wikipedia article on it:
https://en.wikipedia.org/wiki/System_File_Checker
and Microsoft support article:
<https://support.microsoft.com/en-au/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files>

If you can't work it out, contact Support. Support isn't currently restricted 
to deluxe customers as far as I know.

Cathy

Tony wrote:




Trying to find out if anyone has had the 'ole2.dll bad image’ error on 
installation o f Legacy 7.5 or 8 Free Editions onto a 64bit system and 
how they overcome the problem?

Any advice on how to get Legacy running would be much appreciated e.g.

(1) How did you cure the ole2.dll error?

(2) What folder you installed Legacy to - C:Legacy or C:Program Files 
(86) or somewhere else?

(3) Any other tips or tweaks employed to get Legacy working.I really 
don't want to lose the last few years work on my family files.

History: - I've had Legacy 7.5 'Free Edition' working fine, firstly on 
Windows XP and then Windows 7, both 32bit systems.When Windows 7 
computer died, I got another Windows 7, but this one is a 64bit system.

I cannot ask the Legacy Help Website for advice because I am using the 
'Free Edition' but the error is mentioned online there.The response on 
the Help Website is to contact Microsoft for help as the 'ole2.dll' is 
part of the Windows operating system.I've spent mo st of the last 2 
weeks reading the advice from Microsoft (and others) and trying to 
install both 7 & 8 with no success.All that happens is the Legacy 
window opens, but I cannot get any of my own family files or even the 
sample file to open, even though I can see them.Can import gedcoms but 
cannot open them either.

Many thanks in advance.Tony.

P.S. I'm off to bed now after trying to install Legacy all evening. 
Will respond to any replies tomorrow (Friday 24 Feb).

-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

Reply via email to