I'm sorry but I don't use system restore and due to this problem occuring weeks ago, the damage is already done and too far back to do a system restore. Can anyone else please offer some advice?
Main Topics
Browse All TopicsHello,
This same problem has already come up once already on the forums but I believe my situation is different. I run AOL instant messenger version 5.5.3595 alongside the DEAD AIM plugin. I use this version of AOL instant messenger due to it being the only compatible version with DEAD AIM and the functionality DEAD AIM offers is not avaliable in newer versions.
AIM has worked flawlessly for years and I have never had any problems up until a few weeks ago. I came back to my screen to see dozens of window panes, stating:
"Microsoft Visual C++ Runtime Library Program C:\Program Files\AIM\aim.exe A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated" (see attatched image - Aim error).
I proceeded to uninstall AIM and attempt to reinstall the same version and while installing the installer would halt at the point it attempts to install imagehlp.dll, it freezes showing another buffer overrun error in the temporary file GLJ596.tmp (see attatched image - aim install error). After I click okay on the buffer overrun error, the installation proceeds and then I am confronted with a bad image pane stating that GLJ596.tmp is a bad windows image file. Please check against your windows installation disklette (see attatched image - aim bad image).
I am not sure why this is occuring. I can only think of a few possibilities. Windows has updated the imghlp.dll file or something to do with the .Net redistributable package being updated automatically by windows.
I also recently updated my version of NOD 32 3.0 Antivirus to 4.0.
I am running WIndows XP SP3.
Thankyou for your help.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes I'm running Windows XP Service Pack 3. I checked my update history in windows update and found nothing installed on the 23rd of June.
With regards to sfc /scanow.. because I am running XP SP3, is it going to be a problem that my XP OEM CD is SP1? I assume the DLL files have been updated, so would it be attempting to overwrite new DLLs with old ones?
i think u may have a prob. regardless of how this turns out u need to make urself a "slipstream" xp sp3 cd later so if u have to use sfc, or do a reapair or reinstall u dont have to go thru all the business of reinstalling each service pack
there may be a way to run sfc using the sp3 installs instead of cd, but i will have to check
I'm unable to point it to the C:\i386 folder, it only prompts me to insert the Windows CD. Also, the i386 folder does not exist on my pc. I've also read that you can change a registry key so that it will install from the servicepack directory:
HKEY_LOCAL_MACHINE\SOFTWAR
CDInstall (1) - set by default
SourcePath: this is supposed to be set to C:\i386 but on my pc it has the E:\ partition set for some reason.
ServicePackSourePath: C:\windows\servicepackfile
i think this is the way i did it
http://apcmag.com/how_to_c
shame u dont have vista, i recently used a prog named vista update integrator and it was a breeze
i just skimmed thru the whole nlite tutorial and it didnt look all that bad, but ive done slipstreams in the past that used antique methods, hehe
http://apcmag.com/how_to_c
Thankyou to evining for all your help.
I inevitably threw in the towel and upgraded to the latest release of AIM.
I tried to install AIM 5.5.3595 on other XP SP3 installed PCs and received exactly the same error. I assume It's a redundant dll that the old installer was trying to reference that is unfortunatey no longer supported.
Business Accounts
Answer for Membership
by: eviningPosted on 2009-08-07 at 19:38:39ID: 25048105
only thing i can think of to do is a system restore to prior to the problem, then any possible update conflicts would vanish until u reinstall the updates. btw switch updates to manual instead of automatic after u do a restore to isolate the offending update