SBIE v3.00.13 prob AdobeReader with SeaMonkey v1.1.4
Moderator: Barb@Invincea
SBIE v3.00.13 prob AdobeReader with SeaMonkey v1.1.4
SeaMonkey-browser v1.1.4 runs sandboxed under SBIE v3.00.13
No pdf-files are shown in the browserwindows. The browser is blocked for 2 min. Then message appears: Acrobat plug-in could not launch acrobat
No probs with SeaMonkey not sandboxed and AcroRd32.
Also no probs with AcroRd32 on SeaMonkey v1.1.4 and sandboxed under SBIE v3.00.12
Current Im running SBIE v3.00.12 again.
pepibua
No pdf-files are shown in the browserwindows. The browser is blocked for 2 min. Then message appears: Acrobat plug-in could not launch acrobat
No probs with SeaMonkey not sandboxed and AcroRd32.
Also no probs with AcroRd32 on SeaMonkey v1.1.4 and sandboxed under SBIE v3.00.12
Current Im running SBIE v3.00.12 again.
pepibua
-
- Posts: 0
- Joined: Wed Dec 31, 1969 7:00 pm
Hi Longboard,
thanks for your reply.
If we think of using another reader, I can say that AcroRd32 and SeaMonkey are running under SBIE v2.86, also under SBIE 3.00.12 without probs.
So, there was not any reason for me to try another pdf-reader.
And, if AcroRd32 and SeaMonkey is running under SBIE v.3.00.12 without any difficulties and then appears a prob with SBIE v3.00.13, so the reason is to be sought in SBIE not in AcroRd32. A SBIE-fix is the solution.
pepibua
thanks for your reply.
If we think of using another reader, I can say that AcroRd32 and SeaMonkey are running under SBIE v2.86, also under SBIE 3.00.12 without probs.
So, there was not any reason for me to try another pdf-reader.
And, if AcroRd32 and SeaMonkey is running under SBIE v.3.00.12 without any difficulties and then appears a prob with SBIE v3.00.13, so the reason is to be sought in SBIE not in AcroRd32. A SBIE-fix is the solution.
pepibua
Who is online
Users browsing this forum: No registered users and 1 guest