I have Filemaker Pro 5.5 installed on a Windows NT 4.0. With Netscape and IE, everything works fine (and fast). But as soon as an Opera 5.x Client gets on my machine, the system comes to an almost complete halt. Filemaker uses 100% of the machine's CPU and it's almost impossible to close Filemaker, using Task Manager. Has anybody got a clue?

vermeul

What OS/Version are you running?

The same thing is happening to me. I have FMP 5.5 on MacOS X (10.0.4) and Opera 5.0 PPC(OS X vers) on the same computer.

I use the IP address of the same computer with the port in the URL; e.g. 'http://10.1.1.2:1155/index.html'.

I love a challenge on the 'Bleeding Edge'. ;-)

Garry

As I wrote, I am running Windows NT 4.0 (Service Pack 6) and FileMaker Pro 5.5 (English Version) with its WebCompanion. I still have no clue why an Opera Client is able to bring the whole system to an almost complete stop. I know that with FileMaker Pro 5.0 (and its WebCompanion) this problem doesn't occur. I think there must be a bug in the new Version of the WebCompanion