I've been running FM Pro 5 with no trouble until recently. we lost power while I was in one of my databases and now I get the following error when I do ANYTHING in FM.

Instruction at 0x77805a10 reference memory at 0x00212000. Memory could not be "read". Click OK to terminate.

I have reinstalled the program under several user configurations and the only one that runs is when I log into the computer as Administrator. Strange since I have administrator rights under all my id's. Other computers open the files just fine, so the problem isn't the database, it is specific to my computer.

Any ideas? I'm normally a Mac user and I'm being forced to use this PC at work.

Purchase System Mechanic and do a thorough check of your equipment. Reinstall Windows 2000. Get the latest patches and updates.

Hmmm... reinstalling Win2K might be a little drastic.

I've seen this type of memory conflict before when certain storage devices are attached. Some of them will grab onto a certain range in memory that FM would like to use, and when FM tries to access it, you get a problem.

Is it possible that there is some piece of hardware available to all users but the administrator?

Jerry

You might try deleting your (Windows) user profile on the offending machine but be sure to copy all of the stuff that you don't want to lose before wacking the profile.

Before reinstalling Win2K you might want to go into Task Manager and end all noncritical processes. Then try FM. If it then works without the error, then you know that you have an application conflict.

There are no extra pieces of hardware attached to this computer. This is a basic laptop that spends most of its time tooling along by its lonesome. I attach to the server only when I need to print.

Just tried that and still get the same error. Deleting the user profile is beginning to sound promising (and relatively painless since I have 4 profiles on this computer).

A very similar problem was posted here:

http://www.fmforums.com/threads/showflat.php/Cat/0/Number/103599/Main/103379

Deleting the user profile worked. Thanks Ted!

Edie Jeffas