We use the .cmd solution here to get around the problem both with ns404/461 and mozilla 1.1..
-Eirik
Michael Kaply wrote:
The problem is that Adobe starts it themselves... Eirik Oeverby wrote:call a .cmd instead of the acrobat .exe, a .cmd that issues a 'start'.. that way acrobat is an entirely separate session, and mozilla will not have a problem with it.
-Eirik
David Rocks wrote:
This has been a long time problem but not consistent. Most of the time Adobe stays in the system after leaving the window where it displayed the document that called it in the first place. But not always. I've never seen a pattern. Is there any way to define how Adobe is called by the browser so that it will terminate when it is no longer the active window? Or to force it to always display in a 'new' window that could be terminated?
Michael Kaply wrote:
eric w wrote:On Wed, 16 Oct 2002 21:46:22 UTC, Brendan McCullough <[EMAIL PROTECTED]> wrote:
Every once in awhile I get the message "You cannot connect to www.ebank.hsbc.ca because SSL is disabled." It also happens with other bank sites. There is no cure, if I surf a few other places and then go back it will work again. In the Preferences there is a tick in every box. Any suggestions?
i intermittently see the following error screen when trying to logon to my
bank. a reboot always fixes it. (1.2a)
500: server error [20-0002]
We actually found this one, but there is no way to fix it. It happens if you start Adobe Acrobat. Adobe stays started after Mozilla closes and keeps files locked.
Closing Acrobat should actually fix the problem.
Mike
