Hi,
has someone tested the new Acrobat Reader X in conjunction with his Thinapp app? I get an error message when I try to open a PDF of my bubble with a locally installed Adobe X.
Error is from the Adobe "can not run in the Adobe protectet mode".
When I Switch off the Protected Mode in the local Adobe it open the PDF.
What about swithing protected mode in thinapped Adobe Reader X?
We don´t have the Acrobat Reader Thinapped, The Reader is local only an Application who generates PDF´s is thianpped.
Maybe you are in one of the unsupported scenario http://kb2.adobe.com/cps/860/cpsid_86063.html#main_Unsupported_configurations.
No wen i run the Thinapp Program local installed the reader works.
I think a Thinapp bubble is also a unsupported scenario .
As I understand Acrobad makes also a little Virtualisation maybe that crashes in the Thinapped bubble.
Yes, protected mode for Adobe is also sometype of bubble and sandbox.
I have searched the RegKey who turne´s the Protect mode off,
i will set it in my Virtual App and look if this work´s.
Let us know afterwards.
I have set follwing Key in the current_user Registry:
isolation_full HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\Privileged
Value=bProtectedMode
REG_DWORD=#00#00#00#00
Now it work and the Adobe X deaktivate the Protect Mode when you start a PDF from the bubble.
Change Registry to deaktivate the Protect Mode
What does "when you start a PDF from the bubble" mean?
It means: When a Thinapped program starts a pdf maybe a Help Text ore something from in the VM-WARE Programm with the lokal installed Acrobat Reader.
"It means: When a Thinapped program starts a pdf maybe a Help Text ore something from in the VM-WARE Programm with the lokal installed Acrobat Reader."
huh?
anyone else having a problem using the search feature and using the embedded links within the pdf. It works fine when i install it locally without thinapping it.
this only happens on a windows 7 64bit machine.. XP is fine.
I ran in to the protected mode issue in native Acrobat Reader X while launching attachments from a virtual app. I decided to add a couple of lines to Package.ini :
ChildProcessEnvironmentExceptions=acrobat.exe;acrord32.exe
ChildProcessEnvironmentDefault=Virtual
In addition to these lines, if your application's file system isolation modes are Full and WriteCopy, then you may need to make one more tweak. Our application was outputting files to its own temporary directory in the sandbox instead of using the Windows TEMP or TMP settings. We had to find that folder and set it to merged. We can now open PDF attachments from our ThinApp application and Acrobat X is able to see the files when the application extracts them to its temporary directory. We did not need to disable Acrobat Reader X protected mode within the ThinApp registry.
Both Acrobat executable names are in the list because some users have Acrobat and some have Reader.
This was tested on Windows 7 Pro 64-bit.