Filemaker 3.0v5 CRASHING/ tell me how to stop it

[Kelly Fisher]

Using Windows XP, I am trying to run Filemaker 3.0v5. (This has happened on two computers that have been set up for me to use, same problem). The problem is:

As I try open a database that I created last week, occasionally it brings up this message:

"The instruction at '0x77f58267' referenced memory at '0xfffffff8'. The memory could not be read. Click on OK to terminate the program."

Then the program dies.

And when Filemaker doesn't bring up that error, it won't even open up the the database I want to open up. It was just crash/close automatically.

(This happens on any database I am trying to open up. The specific databse that I want open, I have sent over the network and have successfully opened it up on an older mac (OS8.1). But I can't use it on that machine, I need it on my own machine.)

Any ideas. We have none.

[BobWeaver]

Version 3 may not be supported in Windows XP. Even at its best, version 3 was not particularly stable (in my opinion). Try re-installing Filemaker, and also make sure that you have the latest update for it. Getting the latest update could be difficult now, because FMI took the version 3 updaters off their website a few months ago, but you might be able to find a copy around somewhere.

[Vaughan]

<sigh> Don't run it in Windows XP.

FMP 3.0 is, oh, maybe six years old by now. It's not certified for WXP. FMP 3.0v5 isn't even Y2K compliant either. (Yes, it's *that* old.)

At least update it to FMP 3.0v6 using the free patch from the FileMaker web site. FMP 3.0v6 is the oldest version that is Y2K compliant.

[BobWeaver]

Vaughan, they've taken the FM 3 updaters off the website. The oldest they have there now is for version 4.

[Vaughan]

Bob -- you're right. Even gone off their ftp site. The rotten swine!

However, a quick search on Google (less than 10 seconds, the first link returned) got me the 3.0v6 updater for Windows.

[Kelly Fisher]

Thanks for the replies. I figured that is the problem, but supposedly (I just started working with this company), everyone runs on XP and I am the only one enountering problems, although it happened on 2 machines. Hmm?

But yesterday, I found we had a 4.1 version and therefore, I uninstalled 3 and installed 4.1. Previously I did encounter some problems with 4.1 when it was on my old machine, but have yet to use 4.1 on this new machine, so hopefully it works out. Should I locate updates for 4.1?

[Vaughan]

I seriously doubt that FMP 4.x is certified for WinXP either. FMP 5.x might be but I don't know, the FMI web site might have some info on it.

Why not upgrade to FMP 6.0?