Help needed with OLE2.DLL
Thread Starter
Join Date: Jul 2006
Location: Germany
Posts: 44
Likes: 0
Received 0 Likes
on
0 Posts
Help needed with OLE2.DLL
When trying to install a program, I received the message "C
Windows\system32\OLE2.DLL is not a valid image..." I asked my friend Google and found 1.9 million entries, waded through the first 25 and was even more confused after that.
Any help for fixing this would be greatly appreciated.
Brakes
Dell Dimension 4300, Intel Pentium 1.6 Ghz
512 MB RAM
XP home, SP3
Windows\system32\OLE2.DLL is not a valid image..." I asked my friend Google and found 1.9 million entries, waded through the first 25 and was even more confused after that.Any help for fixing this would be greatly appreciated.
Brakes
Dell Dimension 4300, Intel Pentium 1.6 Ghz
512 MB RAM
XP home, SP3
Join Date: Feb 2007
Location: Dublin, Ireland. (No, I just live here.)
Posts: 733
Likes: 0
Received 5 Likes
on
4 Posts
OLE? I'm guessing that program is old. If so, try running the installer in one of the backwards compatibility modes: under Properties, try e.g. Windows 98 on the Compatibility tab.
Join Date: Nov 2007
Location: UK
Age: 38
Posts: 75
Likes: 0
Received 0 Likes
on
0 Posts
Might be worth knowing what the program is..?
Are you running an exe from the source folder or from the desktop? Could be that your exe is on the desktop and not in the folder where it belongs(fix, make it a shortcut)
Are you running an exe from the source folder or from the desktop? Could be that your exe is on the desktop and not in the folder where it belongs(fix, make it a shortcut)
Thread Starter
Join Date: Jul 2006
Location: Germany
Posts: 44
Likes: 0
Received 0 Likes
on
0 Posts
bnt,DaveD,
Thank you for your answer.
OLE2.DLL sits in windows\system32 and came with XP. As far as I can make out it is used by some programs which allow to include objects, like pictures etc. An example would be an e-mail with attached photos.I have downloaded the file, but can find no difference (in version number and size) from the one installed.
That's as far as I got. Not being too computer savvy, I don't know if I can just delete the one in system32 and then copy the downloaded file or if it needs installing..
Thank you for your answer.
OLE2.DLL sits in windows\system32 and came with XP. As far as I can make out it is used by some programs which allow to include objects, like pictures etc. An example would be an e-mail with attached photos.I have downloaded the file, but can find no difference (in version number and size) from the one installed.
That's as far as I got. Not being too computer savvy, I don't know if I can just delete the one in system32 and then copy the downloaded file or if it needs installing..
Last edited by Brakes on; 17th Feb 2009 at 00:13. Reason: spelling
Join Date: Jan 2008
Location: LONDON
Age: 51
Posts: 525
Likes: 0
Received 0 Likes
on
0 Posts
Ole2.dll
OLE2.DLL is just one of the many librarys that provide interfacing compatiblilty for Object Linking and Embeding (OLE). This being an old technology that as been superceded by the .net framework that is now in itteration 3.5.
Enough of the jargon, there are many reasons you may get the "Is not a valid image" message but the most common is when you are trying to install a legacy 16bit application in a 32 bit environment.
To put this is laymens terms... older processors such as the 286/386sx which ran the old windows 3.1 operating system are 16 bits (16 registers made up 1 address of memory) to allow more memory to be addressed this was doubled to 32bits (and more recently again to 64 bits). For compatibility modern processors can work in each of the individual modes - however you cannot mix those modes.
So in essence what appears to be happening is your trying to install an application in one mode that is trying to utilise the OLE2.DLL written for another mode.
e.g. If a 16bit (very old legacy windows) application trys to access a 32 bit DLL such as OLE2.DLL it will encounter it is not a valid windows image - this i because it is trying to access a 32bit dll in 16bit mode.
The same will apply if you are trying to access OLE2.DLL from a 64bit application as it will try to address the DLL in a mode twice the size than it is capable of.
Although this may have not answered your question, it will at least give an indication of the problem - what to do next is to find out what application it is your trying to install, which version it is and its addressing capability.
When downloading applications from the net, if you are using normal windows xp you want a 32bit image which will be referred to normally as an x86 image (compatible with intel 8086 processors and above) if you are running windows 64bit then you want to download if possible x64 images. Theoretically the x86 images should work on all the processors, but the x64 wont work on anything less than the latest 64bit chips and operating systems.
If you can provide more infomation as to what operating system e.g. xp x86 or x64 and what application we should be able to move forward from there.
Cheers
Enough of the jargon, there are many reasons you may get the "Is not a valid image" message but the most common is when you are trying to install a legacy 16bit application in a 32 bit environment.
To put this is laymens terms... older processors such as the 286/386sx which ran the old windows 3.1 operating system are 16 bits (16 registers made up 1 address of memory) to allow more memory to be addressed this was doubled to 32bits (and more recently again to 64 bits). For compatibility modern processors can work in each of the individual modes - however you cannot mix those modes.
So in essence what appears to be happening is your trying to install an application in one mode that is trying to utilise the OLE2.DLL written for another mode.
e.g. If a 16bit (very old legacy windows) application trys to access a 32 bit DLL such as OLE2.DLL it will encounter it is not a valid windows image - this i because it is trying to access a 32bit dll in 16bit mode.
The same will apply if you are trying to access OLE2.DLL from a 64bit application as it will try to address the DLL in a mode twice the size than it is capable of.
Although this may have not answered your question, it will at least give an indication of the problem - what to do next is to find out what application it is your trying to install, which version it is and its addressing capability.
When downloading applications from the net, if you are using normal windows xp you want a 32bit image which will be referred to normally as an x86 image (compatible with intel 8086 processors and above) if you are running windows 64bit then you want to download if possible x64 images. Theoretically the x86 images should work on all the processors, but the x64 wont work on anything less than the latest 64bit chips and operating systems.
If you can provide more infomation as to what operating system e.g. xp x86 or x64 and what application we should be able to move forward from there.
Cheers
Thread Starter
Join Date: Jul 2006
Location: Germany
Posts: 44
Likes: 0
Received 0 Likes
on
0 Posts
Jofm5,
Thanks for having taken time to answer my question.
It now appears that the problem is not with the OLE, but I haven't been able to find out much more.
It's not time critical, so I'll take it slowly.
Thank you all again for your inputs.
Brakes
Thanks for having taken time to answer my question.
It now appears that the problem is not with the OLE, but I haven't been able to find out much more.
It's not time critical, so I'll take it slowly.
Thank you all again for your inputs.
Brakes
