instruction at "0x73dd11c7" referenced memory

[deb]

After installing visual studio & sql 2005 I was getting a visual studio debug
error in my scanner program (paperport) so I uninstalled sql & visual studio
and now when I run my scanner program I get this
instruction at "0x73dd11c7 referenced memory at 0x00000004. The memory could
not be read. I am running xp pro sp3 - my scanner worked fine until this

 

[RJK]

After installing visual studio & sql 2005 I was getting a visual studio
debug
error in my scanner program (paperport) so I uninstalled sql & visual
studio
and now when I run my scanner program I get this
instruction at "0x73dd11c7 referenced memory at 0x00000004. The memory
could
not be read. I am running xp pro sp3 - my scanner worked fine until this

This is an easy one ! You simply restore your boot-drive / Windows platform
to the state it was in before you made, potentially disastrous, major
software changes to it, such as installing application software that's
destined to cause problems.
So, because you were about to make changes that could damage your Windows
platform, and before making such changes you obviosuly made a full
boot-drive backup using software such as Norton Ghost, or Acronis TrueImage
etc. ..and THEN you attempt to install that program that could cause massive
problems - and if it does - ...you simply restore the drive to how it was
before that rogue application software went on to b****r up your Windows
platform !

regards, Richard

 

[User]

This is an easy one ! You simply restore your boot-drive / Windows platform
to the state it was in before you made, potentially disastrous, major
software changes to it, such as installing application software that's
destined to cause problems.
So, because you were about to make changes that could damage your Windows
platform, and before making such changes you obviosuly made a full
boot-drive backup using software such as Norton Ghost, or Acronis TrueImage
etc. ..and THEN you attempt to install that program that could cause massive
problems - and if it does - ...you simply restore the drive to how it was
before that rogue application software went on to b****r up your Windows
platform !

I had the same problem using Visual C++ 6.0. The error appears when I try to
open files (except when trying to open Workspaces).