Just a question, since as an XP user I'm not familiar with what the option does on a Vista machine:
In Sandboxie's window, is File > Run as Administrator checked or unchecked?
(I'm assuming that the option is still there. As an XP user, I don't have that option)

And, are you running in an administrator account or just a user account?

I already reported a problem with foxit pdf reader and sandboxie in Vista. It seems that the preferences for foxit are written to .ini file in the program directory.
In vista changes to this .ini file are kept in a virtualstore directory and not in the foxit program directory. When you use foxit outside the sandbox, Vista automatically reads the .ini from this virtualstore directory. When sandboxed only the .ini from the foxit directory is used, this could cause a problem.
I have fixed a problem by copying the foxit .ini from the vista virtualstore to the foxit program directory.

Maybe this will help you,

Greets,
Bertus

For safety reasons I tend to use a normal account especially when linked to the internet. I now tried to run the sandbox as administrator and when running firefox from this sandbox the plugin works! I am not sure whether it is advisable to act in this way. Using a sandbox itself is probably enough security isn't it?

Should be secure. You might want to try Sandbox Settings > Restrictions > Drop Rights for additional protection.

But basically you're saying the combination of Windows Vista, standard user account, Firefox and Foxit Reader is not working well, correct?

I will look into it when I have more time.

Yes, that's correct. Both plugins, the one for the Foxit Reader as well as the one for the PDF-XChange PDF Viewer don't work from within a sandboxed firefox started from a normal user account. When starting the sandbox as administrator both work.


I really appreciate all suggestions. This is really a very active forum, I love it!

[quote="bernd_meyer56"][quote="Guest10"]No problem here.
Choosing to install the "Firefox Plugin" from within Foxit Reader v3 resulted in 3 files in my %Temp% folder:
1. InstallPDFReaderPlugin.exe
2. FoxitReaderOCX.ocx
3. npFoxitReaderPlugin.dll

Items 2 and 3 are copied to
C:\Program Files\Foxit Software\Foxit Reader\Plugins

Item 3 gets copied to
C:\Program Files\Mozilla Firefox\plugins
and that is the copy of the plugin file that Firefox uses.

I'm not sure if there are any Registry entries made - beyond the ones that Foxit Reader saves, as to the location of files 2 and 3 on the hard drive.

When Firefox is running, either unsandboxed or sandboxed, if you type in Firefox's address bar
[b]about:plugins[/b]
you should see the Foxit Reader Plugin listed, and Enabled = yes

Having the Adobe Reader plugin already in my list of Firefox's plugins didn't present any problem.
The Foxit Reader plugin was the one that got used, though. I'm not sure why, except that it was listed at the top of the list of plugins when I used "about:plugins".[/quote]

I have done exactly the same. After the installation from within Foxit Reader I had the files you mentioned in the same directories and within Firefox (unsandboxed or sandboxed) I see the plugin with [b]about:plugins[/b] but in the sandboxed Firefox it doesn't work. I always get the following message box:

[img]http://www.ewetel.net/~bernd.meyer21/fotos/screenshot.png[/img]

The Sandboxie support told me that this happens when there is no access either to the OCX or the corresponding registry entries. I have tried from within the Sandbox configuration to grant firefox access to the OCX, the DLL and the registry entries without any success. I am lost :-([/quote]

So, are you also using the combination that tzuk mentioned, above:If you are using Vista, did you try turning on the "Run as Administrator" option as mentioned above?
Also, what version of Sandboxie are you using, just in case this might have been fixed in a later version?

I could not reproduce any problem with the combination of Windows Vista, standard user account, Firefox and Foxit Reader, and Sandboxie 3.35.21.

Then I switched back to version 3.34 and I did get an error pop up box "FoxitReaderOCX" and no PDF.

So I can't say what was the cause of the problem, but it should already be resolved in the most recent beta version.