Digital Workshop

I've got a pub made on XP with Opus v6.

On one screen it plays a flash file (from the local pc) within a browser object.

On all test pcs this works fine, except for Vista, where I get a white screen where the flash should be.

It's no doubt a security setting, but I've gone through what I thought were the obvious ones - can anyone advise how to get the browser objects working again?

Thanks, Linda

Ok, here's a test pub: it's a browser object which plays a flash.

On XP, it plays beautifully.

On Vista, where the flash should be, I get an error message "The internet browser is not available".

I've gone through all the security settings I can understand... does anyone know what else in Vista I should change to see the browser?

I don't know if it's related, Linda, but I've recently been having problems with Flash usage with some installations of IE7 (which I believe is what Vista uses by default).

My online courses use FlashPaper and some users with IE7 only seem to be able to view this if they add my domain to 'trusted sites' in Internet Explorer. Otherwise they just get a blank frame. This has never previously been a problem, using the same files, until this last couple of months.... and it isn't a problem on my local XP installation with IE7. I did some googling, though, and others have had similar experiences.

Linda wrote:


Just to add to the discussion. I get exactly the same error, not even involving Flash file/capability.

New Vista Home Premium laptop... where I
Created a new Opus v6 pub, one page that has a DocView object and a Browser object. Tried different subject files and paths/locations. (Word 2003 doc in DocView, and in Browser tried local .html file, a .pdf file, and a regular web URL.)

I also tried various IE7 settings and turned off TrendMicro AV protection... no luck.

My results were same (failure) for both Opus Preview mode and for published as Webpage.

I think this is a something broken (since Vista) that is very fundamental... as Stephen points out: viewtopic.php?t=3099

The Question is "is there any chance of a DW-built Opus solution around the corner?". Change and broken I understand. The silence... is unfortunate.

Seems to be working for me.
Browser object pointing to Google.com, and docview pointing to a local swf calendar.
OK both in preview and published.

Vista Home Premium with SP1 RC installed; that might make a difference.
Opus v6 Pro (build Jun 18 2007).
No Quicktime installed, Flash Player 9 installed.

Paul

Hi Lar_123

Having some similar experiences with Vista, Office 2007 (even when opening older DOC, XLS from Office 2003 in Office 2007) and IE7, I researched the issue at length and found that MS, as a security feature, has changed the browser flags in the registry that used to permit these files to display in the docview (or in a browser window). Please see:

http://support.microsoft.com/kb/927009

There is a free registry editor, filetypesman, that the user could employ to change these browser flags, thereby allowing view of these type files in docview. However, this (1) is an awkward process for users and (2) a utility like this, if it were to be bundled in the pub's set-up, would have to be checked as to redistribution permissions with its developer.

Another approach I considered was to create a REG script based on the above MS article/fix. After eliciting the input of colleagues, thinking this over in terms of potential pitfalls, I decided it's not a viable choice.

In fairness to Opus, these are MS security changes, and I'm not sure what DW or any other software developer can do to remedy them. One hope would be that MS provides a hotfix to re-establish the needed browser flags. The only other potential remedy would be to create a certifiably safe REG script that will work with different OS's, install permissions, etc.

In sum, Vista, Office 2007 and IE 7 will selectively make it more difficult to make use of docview, though this wonderful feature will still work with many files. For example, I can still use docview in Vista to view PDF's.

I hope this adds some clarity to the issue.

Kind Regards,

Paul, thanks. It's somewhat comforting to know that the DocView/Browser features 'may work' -- at least in some configurations. One could only hope that a SP1 of Vista 'cures' this/these ails, and DW doesn't have to gyrate thru hoops or change product architecture. (btw, my PC got hosed by MS Vista updates a couple weeks ago... MS shut down auto updates but allowed the corrupting-update process if one initiated a visit to the site and downloaded. So, I am gunshy of updates right now.)

Stephen,
I did read your earlier posts and did get a sense that was the 'break'. Regarding choices to be made from here, I think a registry-edit would only be 'palatable' if I had a few, captive accounts as customers. (previously discussed).

At this point, I'm just trying to determine what to build into a pub (use docview or not). Paul's experience seems to lend some confidence to the future outlook.

Thanks all. (again, I didn't want to sidetrack Linda's question/post... hope this adds productively).

Hi Lar,

The browser / doc view does work...with a glitch...IE's protected mode prevents access without the right elevation levels. Although the IMP / EXE from Opus will run as a standard user, access to IE from within Opus requires a higher level of access.

If you run the Opus.exe or the published exe as admin, you can use the browser / docview as normal. Of course this is not helpful for those running PCs without admin access under Vista.

I can understand the idea of linking IE protected mode and UAC as this would stop users have full internet access - by which I mean that plugins / activeX controls / malware / virus / etc cannot being installed by a standard user.

From what I've read, it should be possilbe to get the host program to raise the elevation level to solve this issue for non-admins and thus provide the same level of access that you would get if you ran IE as a standard user - but who can trust posts on the internet

If you haven't already got this, download tweakUAC as this allows you to turn UAC to silent and solve the problem. If you're more technical, you can do the same thing via the security policy under admin tools in the CP.

I haven't tried this, but assume it would work - if you select 'run as admin' on the published exe file, it should run your application as admin everytime it's clicked - it won't stop UAC - but will help if you're likely to forget to use the run as admin manually.

There are some user friendly explanations of these 'wonderful' new Vista features that are causing us problems here including UAC & shadowcopy:

http://www.microsoft.com/windows/produc ... ntrol.mspx


Mack

Good info. Good explanation. Thx Mac.

Main thing is that your assessment is 'encouraging'. Being able to expect light at the end of the tunnel... I'm more likely to press ahead and expect to use the features.

BTW, earlier I tried setting ilmplay.exe and IOPlay.exe to compatibility mode and 'run as admin'. That did no good. I'll have to 'study' your info on UAC and 'levels'.

A Pantheist at this point would just worship a tree I suppose. And sacrifice something... in hopes nature will just behave generously eventually.


[ Edit added -L ] Related info on Apps compatibility and UAC. "All UAC compliant applications should have a requested execution level added to the application manifest. If the application requires administrative access to the system, then marking the application with a requested execution level of “require administrator” will ensure...". http://technet2.microsoft.com/WindowsVi ... x?mfr=true

Lar,

If you're trying to run docview / browser object as a plexus publication you need to launch IE as admin for it to work. See screen shot.

Mack

P.S Sorry but had to zip image as forum won't allow images over 800x600

Mack,

Brilliant.... that solved the problem - flash in a doc view now runs on Vista.

Many thanks, Linda