When i get to a site and i install the required macromedia flash player 8 all
the things that uses flash are visible. But the problem is when i click on
flash thing(or even move over it) a get a small message beside my mousepointer
that says "Click to activate and use this control" and a grey border comes
around the flash thing. Then when i click on the flashthing it all gets normal
and i can use the flashlink or whatever it is that is made in flash. But you
can understand that it's quiet annoying when you always have to click twice to
click on the flashlink.

Hopefully someone can help me.

Hi, we've encountered the same problem... We got the problem when we
reinstalled our computers. So this is a fresh copy of WinXP SP2 with all the
updates installed. And Flash 8 player of course.

I think this is a VERY new issue. Because this is the only place on the
internet i found the topic and this message is only 2 days old.

I'm digging into this problem and report back when i find something. In the
meantime, if anyone else knows this problem and/or has a cure for it. Please
post it here. Als if you encounter this problem yourself post it here also...

Dennis Teusink
dennis@alientrick.com

www.alientrick.com

Hi there,

To answer your questions, the problem you are experiencing is in the new IE6
update. Due to a recent court ruling with MS and Eolas Technologies Inc.
"Plug-ins" include objects like Flash movies and Java Applets, as well as any
other components that use the EMBED, APPLET, or OBJECT HTML tags. If your web
site has a Flash or Swish animation.

To read about this change click below


http://www.pixelmill.com/(ft5uowijyqp3j9gysidi9mb0)/support/support_article.aspx
?ParentListID=al1017&articleid=kb101593

There are many fixes but you will need to add some JS tags to pages.

Hope this helps.



Stevo33

:D

omg

I know how u feel i updated my computer and next thing i know this is happening

[quoted text, click to view]

You should have read the details about what the update did regarding control
activation before you updated :)

One will assume that web sites will soon start to be updated so as to avoid
the 'problem' .
--
Jeckyl

Hello,

I do agree with Jeckyl : "One will assume that web sites will soon start to
be updated so as to avoid the 'problem'."

It is a real BIG PROBLEM this upgrade, and many people surf using IEXPLORER
worldwide !!!!!!!!!!!! It really kills FLASH (for instance without any easy
solution). And for most simple cases too. I told myself "let's start to stop
using FLASH buttons, only build ANIMATIONS", but I have noticed that when you
have a FLASH file on the page and you scroll up and down (especially when the
Flash disapear up or down) it makes some TERRIFICS ARTIFACTS, dubs, trail... it
kills !

Let's hope that next, soon in the short future, when one does install FLASH
PLUG IN using Windows, it will ask for an autorization, one time and "forever".
Else, all the FLASH strategy is obsolete. Anyway, Microsoft did a BIG STUPID
mistake while making this update uninstallable, it is stupid, non sense except
perhaps to tell something to Macromedia or ?

We have to react, one day many people will do this update and imagine all the
web pages that has to be changed... I guess there is a commercial deal
somewhere between adobe, microsoft... sure... else I do not understand.
Text

Until you next update IE .. it is permanent part of IE6 and all future IE's
... so you are might as well get used to it !!! Especially if you are
developing site, as you need to be able to see how others will see your
sites.
--
Jeckyl

[quoted text, click to view]

That would then mean the IE was breaking the EOLAS patent again .. so that
won't happen. There is nothing Flash plugin can do about it.

[quoted text, click to view]

That probably is not a sensible things for MS, if indeed it is
uninstallable. But htne, maybe it is something they need to do to get the
EOLAS-patent-contravening earlier IE's out of circulations asap.

[quoted text, click to view]

has NOTHING to do with any Macromedia/Adobe vs Microsoft .. the change
affects ALL activex controls including MS's own controls. It has nothing to
do with MS targetting MM .. its everything to do with EOLAS targetting MS.

[quoted text, click to view]

That's just a silly conspiracy theory.

It is quite simple to build web pages that will work with the changes to IE
imposed by the EOLAS nonsense. Existing webpages will be gradually 'fixed'
to work properly and new ones designed so they work with ie to start with,
and the problem will all but go away (except for some old sites who's
authors can't be bothered fixing them
--
Jeckyl

:P any way back to solving the problem

if u get this anoying little update that makes u double click flash this what
u do:

got to uninstall program under control panel

look for the windows update: Update for Windows XP (KB912945)

click it to remove...let it restart ur computer then...bam!! all done ur
problem is solved

a..........NO

I've uninstalled it and my flash works great now

no more double clicking

ur just try to push the update...ur a part of the system

i'm saying as a viewer of flash and not a programmer, i don't need this certain
update.

Its annoying and delays the progress of my web surfing.

Until the websites the I frequent have this update pluged into their pages it
has no benifits what so ever

I'm saying for those who don't check what windows is actually updateing on
their computer, there is away to fix the problem with out crying that their
computer is broken

For u to tell people its envitable and to " just go with the flow", is just
wrong.

As an American i have a choice to have things working in my comfort zone.

Its called options, if i choose not to have the update cause the problems and
the fustration don't out do the benfits of having this program on my computer,
then its gone.

and since u can't tell, i waz disagreeing with the fact that u said the update
is a perment part of IE6 and that I should deal with it when it actually isn't
and i don't have to lay down and deal with it. Thats like me telling u got a
virus and u have a few hours till ur whole computer crashes down to just being
a paper weight, Just deal with it till ur antivirus updates. Wrong!! u have
options and choices to make as soon as u feel u have a problem.

[quoted text, click to view]

I never said it wouldn't .. what is this 'a ... NO' about? What is it you
are disagreeing with?

[quoted text, click to view]

We are ALL a part of the system .. if you weren't, then you wouldn't have
had this problem. And it will most likely come back to haunt you when you
install some future updates to IE. In order for you to hide from the
problem, you will need to remain behind in terms of updates and IE version.

[quoted text, click to view]

You cannot really suggest that it is a sensible suggestion to simply never
update IE ever again, nor ever get a new computer with the new IE installed
(with this new activation permanently added), nor ever update to the next MS
operating system. This change is part of IE now (and of the next IE 7) and
you'll have to deal with it sooner or later, you're just postponing the
inevitable (and keeping your browser out of date).

I'm not sure what brain-washing you are talking about here (or who the 'poor
people' are) .. but it seems to me you're just burying your head in the sand
and not really dealing with the issue. If that works for you .. fine .. but
it doesn't really help in the longer term. I'm not trying to push the
update, I'm not suggesting everyone go out and update it right now. I don't
NEED (or want) to push it .. it is out there .. and people will update it,
and eventually you will need to update IE yourself (because there will be
some update there that fixes a security or other problem that you really
need) and then you'll have it as well.

Of course, if you are a web site developer .. then it is in your own
interest to get your sites fixed up ASAP so that the activation change does
not affect your site's visitors. And as such, it IS worth getting the
update yourself so that you can see whether or not your site(s) work
'correctly' for people with the latest IE browser (which will start to
increase very soon).
--
Jeckyl

ok

i see where ur coming from now.....kinda....ur a bit eccentric when it comes
to explaining things

ur saying this will be a function that will be included in any advance IE and
that ur hoping sooner then later it will be regulated into being useful when
people start updating their sites.

But what i'm saying is that since i don't have this IE7 and still have 6 where
i can uninstall the plugins and all the updates i want. I don't have to use it
until future notice like when one of the updates for windows or IE require that
certain update. So far, i've just recently updated my computer with out it
saying it requires that plugin to function. So my IE is not out of date. Plus
it wazn't a critical update meaning that it waz just somethin Microsoft wanted
u to have but not necessarily needed.(its under optional software when going to
the update page)

so i'll deal with it when and then if its needed, but right now it has no
purpose for those of us who don't want to deal with the headache of double
clicking on a flash program

and being an American has everything to do with it. There are rules to the
web, and rights to haveing things not done to us, where other countries
citizens would be left in the dark. One of the things programers got in
trouble for is for having all these softwares and updates with out an
uninstallation. So Microsoft being the big bombers that they are have to stay
in the guide lines of our American rights to choose. Its not like Bill Gates
likes having fees thrown at him for all these transgressions time after time,
but hey it happens to people who like monopolizing.

so i'm good, IE is up to date minus one function and surfing is great :-)

[quoted text, click to view]

Yeup .. I agree 100% .. it has no benefit other than stopping IE from
impinging on EOLAS patent. I never said or implied that I thought it was in
any way a good idea. Nor did I suggest that it had any benefit. It
doesn't.

However, it is a non-optional part of IE now (there is no setting in IE to
turn it off). Eventually you'll have to update your IE from the old
no-activate-feature version and you'll get this new 'feature' as a result.

[quoted text, click to view]

Yes .. you don't have to install the update right now .. and if you do
install it, you can uninstall it. I never said you couldn't. Just that
unless you want to stay permantently out-of-date and not install future
updates, eventually you'll end up with it.

[quoted text, click to view]

It IS inevitable though .. and eventually (unless you never update your pc)
you'll end up with the same issue.

I said that web developers are better off getting it sooner rather than
later .. but that more and more people will end up with it as IE
updates/upgrade get applied. Its not an optional thing that you'll be able
to turn off once you update IE. You can, of course, chose to run with an
old version of IE .. as long as you're happy with not having security
updates etc

[quoted text, click to view]

That has nothing to do with being American, and being American has nothing
to do with the problem.

[quoted text, click to view]

Yes .. I never said you didn't have the option to not update .. only that
eventually you'll find you have to. That's what inevitable means.
Hopefully most web developers will have updated their sites by then, so it
will be less of a problem for you an any others who chose to not update
their browser.

[quoted text, click to view]

In that case you are wrong ... It is now. IE6 from now on has that
'feature' as part of it .. as does IE7 when it is released. You can really
just decide whether or not you want to update to have the latest IE or not.

[quoted text, click to view]

You can choose to ignore it for now by not updating your copy of IE.

[quoted text, click to view]

I don't quite see your analogy here so I'll just say .. yeah .. ok.

Anyway .. obviously not updating your IE (so that it doesn't include this
new 'feature') is a short-term alternative for many people, but not a
mid/long term solution to the problem. Unfortunately the only solution (so
far) is for web site developers to 'fix' their sites so they work as desired
for people using latest IE. It is really a race now between how many people
update their browsers and get this new feature against how fast web sites
can make their sites work again.
--
Jeckyl

Hello again,

Thanks, we can uninstall this fix when using ie6 :
C:\WINDOWS\$NtUninstallKB912945$\spuninst\spuninst.exe
But one thing is sure beside eulas and so on law fights that should not affect
the way we simply use internet for 10 years, this fix totally affect a certain
way to build web pages using Flash, practically without solution FLASH would
turn to be the wrong solution in many cases (I had made some interactive pages
that suddenly looked really ridiculous and impractical).
So THANKS to that forum, I have applied the .JS solution that is clearly
suggest to avoid this message and the fact the Flash zone (exemple 640*360) was
no more refresh while scrolling and made terrific artifacts until you have not
activate the activex by clicking).

So question, is this .JS solution the only solution, the future solution ? Is
it a long term solution ? Or whatever we do, one day it will no more be
possible to use Flash (general activex...) with IExplorer without clicking
first to ativate the frame ? Some people would think about Firefox and so on,
but many people still use IE. And I must admit -dummy boy- I still have not
understand why legally there is a change between the old way to include a Flash
file and the javascript solution, does it mean javascript is not caring about
the eulas yet ? Will it turn as a ping-pong game ?

Anyway, thanks to this forum and all the guys and girls sharing, a self-taught
doesn't come out of a magic bottle, personally I am first a dummy.

[quoted text, click to view]

Eccentric ... hardly .. although I do find your replies a little cryptic.

[quoted text, click to view]

Not sure what you mean by 'any advance IE'. The activation is a part of the
current IE6 now and also part of IE7 and (unless something major changes)
part of IE from here to eternity.

I am not sure what you mean by 'regulated' ,, and the update is never going
to be 'useful'. But it will be rendered fairly harmless when web sites are
changed so that this new activation feature will have no effect on how they
operate.

[quoted text, click to view]

Its not a plug in. And yes .. you can choose not to update (or to uninstall
the update). Just like you can choose to use IE4 if you want.

[quoted text, click to view]

Its a part of IE now .. so if there are further updates to IE via Windows
Update etc, it is quite likely that they will also include the activation
feature. You may not be able to know unless you install it and see .. and
if it also changes the activation feature, then you'd have to uninstall that
update.

[quoted text, click to view]

What plugin? And I never stated that the update is required for your
computer (or your browser) to operate. You seem to be reading things into
my fairly clear replies that are not there.

[quoted text, click to view]

Yes it is .. as you've not applied the latest update via windows update. By
definition, that means its not up to date :) Of course, just because it is
out of date doesn't mean it no longer functions.

[quoted text, click to view]

Its probably optional to apply it at this stage, but that may change.
You'll note that many updates include all previous updates as well (you see
text like: "This update contains all previously released security
updates."). So it is quite likely that future updates will also include
this update .. just as this one includes updates before it. In that case
you may no longer be able to install or uninstall it independantly of these
future updates.

[quoted text, click to view]

Yeup .. no useful purpose at all.

[quoted text, click to view]

No . sorry .. it doesn't. The rest of the world is no less civilised and
concerned about consumer and personal rights and liberties than Americans.
You don't have a monopoly on those things. America does, however, tend to
impose its ideas on everyone else, regardless of what others want or how
silly the ideas are.

Actually .. I take it back .. the whole of this problem is due to America ..
because of the stupid way patents are granted in your country, the rest of
the world has to suffer when a company like EOLAS can hold Microsoft to
ransom and as a result everyone in the world ends up having to have this
stupid update to IE to avoid the problems. And don't get me started on the
ridiculour DRM that the good old US is trying to impose on us. Thanks
America.. We all owe you.

Anyway, regardless of whether you are an American or not, you can choose to
NOT install the update .. just like you can choose not to use a computer.
Noone is forcing you to install it. However .. it will be come increasingly
the case that things you DO want to install (re IE updartes in particular)
will also turn this feature on. For now though, you can happily ignore it.
--
Jeckyl

[quoted text, click to view]

It's funny to me (personally) how everyone blames Flash for this, though
it effects every ActiveX control in existence.

We are working on a solution that will help Flash developers resolve
this issue for their end users more easily. Watch technotes on
http://www.macromedia.com/support/flash/.

Bentley Wolfe
Senior Support Engineer, Flash/Flash Player

[quoted text, click to view]

Likewise .. even funnier are the assertions this is some sort of deliberate
attempt by Microsoft to undermine Flash .. yet the change affects Microsoft
activeX controls just like it does Flash.

Basically the whole thing is driven by EOLAS making (and being given) a
ridiculously broad patent for something they never used themselves but that
applied to technology MS etc also developed. Then EOLAS suing Microsoft for
a ridiculous amount and so Microsoft having to either pay equally ridiculous
licensing fees or change how IE works so it doesn't infringe the patent. If
EOLAS gets greedy enough (which on their current record seems quite likely)
they may just as likely go after Firefox and Safari, and Opera and any other
browser that all equally infringe the patent (the companies invovled just
don't have enough moeny for EOLAS to milk them dry) .. if any browser
company does become successful enough, and still supports applets and
controls, then EOLAS will sue them too. Its a very sad and crazy world.

[quoted text, click to view]

The post elsewhere in these forums where a single line added to HTML (no
other changes) plus a reusable .js file seems to be a very good solution.
But it does seem to fly against the 'spirit' of the MS change . .so it may
be a loophole MS will close when they find out about it. If not .. I can't
think of anyhting much simpler than that.
--
Jeckyl

Here is how you fix it. Uninstall the Update for Windows XP (KB912945) from Add
or Remove Programs, restart your computer, run Windows Update (or Microsoft
Update), select Custom, under ?Update for Windows XP (KB912945)? check the box
that says ?Don?t show this update again?. Problem fixed.

As a web designer I was looking for a fix to this...I found one that works!
Unfortuately for now it's up to the designers to fix their sites and not much
users can do (except revert back to an older version of IE, which isn't
practical...I'm fixing mine *sigh...Here's the link:


http://www.pixelmill.com/(6fm7plcl9n0uq9kjmr7qwi90)/support/support_article.aspx
?sid=vfup0mywyuemo9ktqq1x60ln&ArticleID=kb101593

It's a pain in the butt, but it works and it prevents your site from looking
like crap. Hopefully this helps some designers out there...it helped me.
BTW...I'm uploading new pages to a site I'm currently working on check it out
and see the difference. http://www/warninglabel.info

[quoted text, click to view]

If it wasn't for the stupid patent system they wouldn't have rights. They
shouldn't have a right to these 'rights' .. its not right :) And yes .. I
do blame EOLAS ... they did not HAVE to sue MS .. MS was not hurting them in
any way at all, as Eolas have no technology, no products .. nothing but a
piece of paper saying they have a patent on a very broad idea.

They did not develop the activex techology .. MS developers did that
themselve as a natural development of dlls, ole and com technology. EOLAS
didn't really develop any working technology, MS didn't steal anything ..
its just yet another stupid patent of an abstract idea and as a result some
useless little company that only exists to grab patents (not do anything
useful) ends up extorting money.

[quoted text, click to view]

Yes .. good idea. . I think I'll patent that :)
--
Jeckyl

Note: I've seen a simpler method .. add on line of <script> tag to your
existing html (no change to you object and embed tags) and have a common .js
file that all you html pages can use.

see here:

http://www.archivatna.com/t53647-easy-fix-for-ieupdate-activex-problems.html
--
jeckyl

[quoted text, click to view]

Not long to wait then...

MS has announced that the change will be non-optional as of April 11

The recent optional update was mostly so web developers could test their
sites etc.

After April 11, if you update IE at all after that, you'll get the new
click-to-activate.

see
http://www.computerworld.com/developmenttopics/websitemgmt/story/0,10801,109866,00.html
--
Jeckyl

i have a simple answer to this problem

[quoted text, click to view]

Yeup .. and then get other problems .. no browser is perfect (and certainly
not when it comes to Flash). However, you will generally have less problems
with IE, as it is the most popular browser by a huge majority, and as such
most web developers build sites that will definitely work under IE .. IE is
the defacto web standard. If a web developer has a choice of being
officially-standard-conforming or working in IE .. they choose working in
IE.

It won't take long for web sites to update to use external .js files so that
their Flash (and other activex) content will activate automatically. And
there is no guarantee that EOLAS won't go after Firefox, Netscape and Opera
(if they thing the companies who make them have enough money to be worth
suing).

Of course, if you're happier with Firefox et al (which really are no better
or worse than IE .. just less popular) then that's fine .. good luck to you.
--
Jeckyl

And in a couple of weeks time you'll get the problem again as it is then a
permanent part of IE .. so either get used to it, or stay forever out of
date.
--
Jeckyl

I have the same problem. But it had been fixed after I uninstall something. I
just go to control panel - Add/remove program, check the 'show updates' check
box, find the Windows XP - kb912945, then uninstall it. Then, the problem had
been fixed.

I just encountered this issue and was quite surprised by the fact that this was
a federal court ruling against Microsoft IE back in August of 2003. Well, as a
business owner that has three nationally used web sites, I can see this issue
wont just go away by uninstalling the IE update patch I have on my brower.
That is, I cant instruct all my users and prospective customers to unistall an
IE update in order to get the propper browsing experience. So I have to think
of surfers out there that hit my site and not just how I fix it for myself. I
can't stop using IE and start using Netscape and FireFox. I do have all three
loaded for testing my sites but, according to my traffic statistics, 98% of
surfers hitting my sites use IE. I can't ignore them. So I am off to implement
the javascript based solution and will be looking to Adobe'a Active Content
Developer Center for other new solutions specific to their plug-ins.
http://www.macromedia.com/devnet/activecontent/#captivate_before

There's a very simple solution by adding three lines to your <head> tag and
a common .js file

No need to change anything else (like your object and embed tags)
--
Jeckyl

Hi yer,

I use the minimum code to embed my swf files eg:

<object width="550" height="400">
<param name="movie" value="somefilename.swf">
<embed src="somefilename.swf" width="550" height="400">
</embed>
</object>

Would someone amend this script for me please, to allow for Eolas changes?

Jecky says there's a very simple solution by adding three lines to the <head>
tag and a common .js file.

Would someone explain this in ladybird language as I do not understand what
this means. What three lines do I add to the head tag and what is a common .js
file?

Thank you so much for your patience

Oh yeah!

See my post earlier where I give link to the thread where it is discussed

http://www.archivatna.com/t53647-easy-fix-for-ieupdate-activex-problems.html

--
Jeckyl

Jeckyl,
Thanks for the information and link. I'm encountering this issue as
well, but in a different capacity. I'm the webmaster for a department
that uses a proprietary application to maintain its website. The
program contains a DTHML editor within it, which is blocked by this new
update. Trying to edit any pages for the site causes the editor to
crash, so I'm trying to find a workaround, and unfortunately, the
javascript tags and other code workarounds are not an option since we
can not access the program's source code here. So, I have to rely on
an update to this security patch that allows me to have the option to
permanently allow a particular control (or controls on a certain site),
or, I'll have to see if I can switch over to a Windows 2000 machine
just to avoid this issue.

Thanks,
Brian

:frown;

Are there any plans to include this JS solution native in Dreamweaver? I have
an awful lot of low to mid-level Dreamweaver users at my organization who
contribute to our web sites (with templates and other "locking" measures
employed, of course ;) . Some of them like to include flash items I've either
created or purchased on their own pages. It's going to be a real pain to either
teach them how to translate the tags into the appropriate function call
variables (not to mention get them to understand what a function is...) or to
touch every page they make that just might include some flash/shockwave
component I've made. This is especially going to be true as I was in the early
stages of developing many new flash games/tutorials and Captivate content. It
would be really, really great if the "insert shockwave"/"insert flash"
buttons/commands would just insert the .js files into a root level directory
when used (if they aren't already there), and insert both the <script> and
<noscript> content into the page (instead of the current insertion of just the
object and embed tags). Please?

I have managed to find the fix for the issue which resolves all the problems
associated with IE and Flash.

GET THE FIX HERE


http://capitalhead.com/articles/click-to-activate-and-use-this-control---kb91281
2.aspx


http://capitalhead.com/articles/click-to-activate-and-use-this-control---kb91281
2.aspx

This has got to be the craziest thing I've ever heard - some people - do not
uninstall kb912945. There is a fix for it that Microsoft has developed.

GET IT HERE

:D

Originally posted by: Practice365
Here is how you fix it. Go to Add or Remove Programs, put a check in the box
that says Show Updates, uninstall Update for Windows XP (KB912945), restart
your computer, run Windows Update (or Microsoft Update), select Custom, under
?Update for Windows XP (KB912945)? check the box that says ?Don?t show this
update again?. Problem solved.

It is NOT a fix at all .. Its a temporary compatibility patch only. In any
case, there is no 'fix' because it does not need to BE fixed .. its not a
bug !!!

It is also of no use for site developers .. they still have to 'fix' their
sites if they do not want visitors to have to click on the Flash content to
activate it.

This compatibility patch is not really of much help to anybody (except maybe
a few special cases). Clicking to activate is a minor annoyance, and
something that will become less of a problem as developers update their web
pages.
--
Jeckyl

I would also like to add that if you go onto Macromedia/Adobe website, you will
notice that their Flash objects do not show a 'tag' or border when the cursor
is moved over them.

Also, how little Flash do they use. Not a great selling point!!

:disgust;

[quoted text, click to view]

Yes .. they have obviously taken their own advice and have a site that works
without the need to click. its not really that hard to do. Anyone can do
it.

[quoted text, click to view]

On the contrary .. it shows how well flash can be utilised as a part of an
effective web site. One doesn't need grauitous full flash web sites that
have obscure navigation that are hard to use etc etc, where the content is
obscured by how clever the designer thinks he is. I think the simple
integrated use of Flash is a great selling point.

[quoted text, click to view]

Disgusted by what?
--
Jeckyl

You may think that this is a little long-winded, but it is certainly a clean
and organised way of embedding your future Flash objects if you have semi-good
knowledge of the use of JavaScript. This solution, like the others, avoids
placing any embedding code directly in the HTML (or similar) page.

1. Create a function called 'fnLoadFlash', with parameters of those used by
Macromedia/Adobe (include file name and dimensions etc.).

2. Place this function in your common JS file that you use within your
website.

3. Whenever you need to embed a Flash object, simply call the fnLoadFlash
function with the appropriate parameters.

Good luck! :cool;

[quoted text, click to view]
effective web site. One doesn't need grauitous full flash web sites that
have obscure navigation that are hard to use etc etc, where the content is
obscured by how clever the designer thinks he is. I think the simple
integrated use of Flash is a great selling point.

Very good point; after all, Flash is merely a component of what MM/Adobe have
to offer in the way of web designing solutions.

After looking at some of the coding on the Macromedia/Adobe website, I have
noticed that they too embed their Flash object from an external script - BUT -
a very interesting point - they load it using an HTML file for the script, not
a JS file. See their code below:

<script type="text/javascript" language="JavaScript"
src="/jsdw/homepage/en_us/fma/flash.html"></script>

Do you think that they are possibly antisipating Eolas'/Microsoft's next move:
to disallow the embedding of Flash by way of a js file?

Yes, that's what I'm saying: not the amazement at the fact they are loading code from an HTML file, but the reasoning for it on this occasion.

Originally posted by: Newsgroup User
It is NOT a fix at all .. Its a temporary compatibility patch only. In any
case, there is no 'fix' because it does not need to BE fixed .. its not a
bug !!!

It is also of no use for site developers .. they still have to 'fix' their
sites if they do not want visitors to have to click on the Flash content to
activate it.

This compatibility patch is not really of much help to anybody (except maybe
a few special cases). Clicking to activate is a minor annoyance, and
something that will become less of a problem as developers update their web
pages.
--
Jeckyl




This is true ... the individual sites will make the necessary changes in due
time

I was having this problem with my road runner homepage starting on Apr 11th,
when the new microsoft updates were downloaded, and suddenly it disappeared ...
I called road runner to ask if they made any changes to fix that problem with
flash, and they did

Were is a good site to assist/examples in fixing the problem for the developed
web page?
I see that there is a patch from microsoft, but some users will not have the
patch and still need to active the flash/quicktime.

[quoted text, click to view]

The .html there is just a change of file extension .. JavaScript does NOT
have to be in a file with .js extension. That's just a convention.
Regardless of the file extension, the content is still JavaScript .. maybe
its there to make it less obvious that its a JavaScript file (like the
technique of naming your .SWF files as .gif so people looking in their
internet cache won't find your .SWF file) ??
--
Jeckyl

[quoted text, click to view]

You need only add three lines of script to each page that uses flash.
--
Jeckyl

I finally got it to work, but it was a real pain to fix all of the pages. I
cannot view the flash outline while working on that page (the format). But can
be viewed on the web or it can be viewed from the html program, GoLive. All
though from GoLive, the preview did not reveal a problem about the "Click to
activate and use this control" issue.

Will Adobe be updating there programs in the future so this will work more
smoothly and seamless?

Adding the Javascript worked well for me at home (using XP Home Edition). But,
when I got to work to test the same page, it didn't work (using XP
Professional). Is anyone aware of a different update for the two versions of XP?

Hi,
Can you tell me what script you used to fix this problem.
Cheers,

[quoted text, click to view]

What JavaScript did you add?

Can you provide a URL link to your web page?
--
Jeckyl

Everyone -

If you're interested the official Microsoft KB Article on this problem is here:
http://support.microsoft.com/default.aspx/kb/917425

Instructions for Web Developers

You can download instructions on how to
http://capitalhead.com/articles/activating-activex-controls.aspx] using Java
Script techniques which automatically activate the controls.

http://capitalhead.com/articles/activating-activex-controls.aspx

Originally posted by: Newsgroup User
Note: I've seen a simpler method .. add on line of <script> tag to your
existing html (no change to you object and embed tags) and have a common .js
file that all you html pages can use.

see here:

http://www.archivatna.com/t53647-easy-fix-for-ieupdate-activex-problems.html
--
jeckyl




I tried this fix and it worked for me - but with a caveat. It caused an
awkward 1sec pause when the page refreshed...so part of the page content went
up, then a pause, then the rest of the content went up.

Instead, I tried this fix which still has a pause but significantly smaller in
duration: http://www.frontpagetalk.com/forums/m.asp?m=74610&p=1&tmode=1&smode=1

Let me start by saying Jeckyl you are a rude pompus know-it-all and you need a
serious ass kicking! You should really get a life and not set around all day
wating for people to post a message just so you can post some smart ass
response. Go ahead and respond to this messsage and prove my point.

Anyway... If any of you have tried to uninstall the update KB912945 and it was
not in your list to remove you will need to remove KB912182 instead. Then
restart your computer, run Windows Update , select Custom, under ?Update for
Windows XP (KB912182)? check the box that says ?Don?t show this update again?.
Problem Solved!

BTW,
The ultimate solution to fix all of this ignorance is not a javascript... its
called a Macintosh!

I've read Jeckyl's posts and found them to be accurate and timely.

Apparently you haven't.

Had you read them you would understand that removing the Windows Update will
not help a webdeveloper who has to anticipate visitors who have the update.

It'r ironic and somewhat humorous that YOU would call Jeckly "rude" and
"pompous"...lol

[quoted text, click to view]

Oooooh .. I'm too scared to post something now in case your 'point'
(whatever it is) might be proved. Please .. take some time to grow up
before you post next time. There's a good phucker.

[quoted text, click to view]

You really have no idea, do you. At least my posts are factual and helpful.

If you have bothered reading here, you'd know that the changes for ActiveX
activation are (unfortunately) a permanent part of IE now. Even if you
uninstall one of the updates that include it, the next security update you
get will have it again. If you keep uninstalling everything that turns on
this new 'feature', you'll end up being forever out of date and miss all the
security patches and updates.

NOTE: There is a temporary patch from Microsoft that will restore the old
way (and nicer) behaviour where ActiveX controls do not require activation
or external JavaScript. However, that patch is temporary only, mostly for
corporate users who have large and complex applications based on ActiveX
that may take some time to be updated.

If you are REALLY bothered by having an extra click for ActiveX content, you
can install this temporary patch and the problem will go away ... for a
while. By the time it expires, and you end up with the ActiveX activation
again, you'll hopefully find the most web sites have updated their HTML to
avoid the problem. So that may indeed be a good solution if you are a web
surfer (avoid the problem until it goes away of its own accord). Its
certainly seems a better solution than just not installing any updates at
all. Or, as you suggest, you can try an alternative browser .. or even go
out and buy a Mac (but that seems a bit extreme just to avoid an extra click
on ActiveX content).

However, if you are a web developer, you really have to deal with the issue
now (or at least fairly soon). In that case you can't just say "well,
everyone should use Firefox, or Mac's, so I won't bother fixing my site so
that the vast majority of web surfers can use it without the extra click".
That sort of attitude is not likely to encourage people to your web site :).

[quoted text, click to view]

Ignorance? Now there's a pot calling the kettle black :)

If you think a using a Mac means no problems with Flash and browsers, you're
deluding yourself. You're swapping one set of problems for another. Just
like those who say one should use Firefox instead of IE and then you'll get
no problems. Unfortunately, there is no perfect platform and no perfect
browser. If there was, then everyone would be using it by now. As a
general rule, if you use the most popular platform and browser, then things
are more likely to work, and if they don't ,then you're more likely to get a
timely solution to the problem.
--
Jeckyl

[quoted text, click to view]

Thank you Saratoga :)

At least he got one thing right .. I know it all :):):) And maybe I am just
a _little_ pompous ... nobody's perfect.

I'm just trying to provide sensible, non-reactionary, practical, and sane
solutions for this 'problem'.
--
Jeckyl

[quoted text, click to view]

Oh no .. he's turned on the caps lock !!! Quick .. everyone run and hide.
There are capital letters on the lose.

You're such a funny kid, phucker; so witty and yet so charming. We're all
having a good laugh at your expense. I can hardly wait for your next
exciting and stimulating post.
--
Jeckyl

[quoted text, click to view]

Well .. that says a lot more about the oh-so-cleverly-named 'PhuckMicrosoft'
than it does about me. What a charming little child he must be; his mummy
must be so proud.
--
Jeckyl

BTW....

[quoted text, click to view]

Hey, at least Jeckyl responds with intelligence and doesnt run home to his mom
and say he called me a name..... :)
Now you are the DORK!

Jeckyl,
This is fantastic....works a treat!!!!!
Many thanks,

Can someone be kind enough to explain how to create a .js file on dreamweaver mx...

can someone please be as kind as to explain how to create a .js file on dreamweaver mx....

Hi LifeBeat,
I have posted the .js file and instructions on my website which was built
using Dreamweaver mx, it has cured the 'Click to activate and use this control
problem'. Please follow the link below.

http://myweb.tiscali.co.uk/alanjshaw/Fix.htm

Regards,
Alan.

thank you for your help. we are a production company and a few of us at
lifebeat tried downloading your java file and we cannot open it and the error
report says : "document undefined"!
please specify what needs to be done.

Originally posted by: LifeBeat
can someone please be as kind as to explain how to create a .js file on dreamweaver mx....
thanks

In Dreamweaver 8: File > New > General > Basic Page > JavaScript

Hi LifeBeat,
Click on the Java file link and select save then upload the file to your root
directory. If you wish to view it's content you should be able to right click
and select the 'edit' mode, or 'open with' notepad.
If I can help further you can contact me direct via the website.
Regards,
Alan.

alanjshaw
We would like to thank you for the assistance and it worked very well.
However,
on some of our larger flash files we use a service such as Blogupload.com
which allows us to link the flashes back to our sites.
The "solution" you gave us works well with our embedded flashes..with the
exeption of our link flashes. Can you please suggest a solution for that?
once again we do appreciate your knowledge and kind correspondance!

there's your .js file

//
-----------------------------------------------------------------------------
/**
* FlashObject v1.2.3: Flash detection and embed -
http://blog.deconcept.com/flashobject/
*
* FlashObject is (c) 2005 Geoff Stearns and is released under the MIT License:
* http://www.opensource.org/licenses/mit-license.php
*
*/
if(typeof com == "undefined") var com = new Object();
if(typeof com.deconcept == "undefined") com.deconcept = new Object();
if(typeof com.deconcept.util == "undefined") com.deconcept.util = new Object();
if(typeof com.deconcept.FlashObjectUtil == "undefined")
com.deconcept.FlashObjectUtil = new Object();
com.deconcept.FlashObject = function(swf, id, w, h, ver, c, useExpressInstall,
quality, redirectUrl, detectKey){
this.DETECT_KEY = detectKey ? detectKey : 'detectflash';
this.skipDetect = com.deconcept.util.getRequestParameter(this.DETECT_KEY);
this.params = new Object();
this.variables = new Object();
this.attributes = new Array();

if(swf) this.setAttribute('swf', swf);
if(id) this.setAttribute('id', id);
if(w) this.setAttribute('width', w);
if(h) this.setAttribute('height', h);
if(ver) this.setAttribute('version', new
com.deconcept.PlayerVersion(ver.toString().split(".")));
if(c) this.addParam('bgcolor', c);
var q = quality ? quality : 'high';
this.addParam('quality', q);
this.setAttribute('redirectUrl', '');
if(redirectUrl) this.setAttribute('redirectUrl', redirectUrl);
if(useExpressInstall) {
// check to see if we need to do an express install
var expressInstallReqVer = new com.deconcept.PlayerVersion([6,0,65]);
var installedVer = com.deconcept.FlashObjectUtil.getPlayerVersion();
if (installedVer.versionIsValid(expressInstallReqVer) &&
!installedVer.versionIsValid(this.getAttribute('version'))) {
this.setAttribute('doExpressInstall', true);
}
} else {
this.setAttribute('doExpressInstall', false);
}
}
com.deconcept.FlashObject.prototype.setAttribute = function(name, value){
this.attributes[name] = value;
}
com.deconcept.FlashObject.prototype.getAttribute = function(name){
return this.attributes[name];
}
com.deconcept.FlashObject.prototype.getAttributes = function(){
return this.attributes;
}
com.deconcept.FlashObject.prototype.addParam = function(name, value){
this.params[name] = value;
}
com.deconcept.FlashObject.prototype.getParams = function(){
return this.params;
}
com.deconcept.FlashObject.prototype.getParam = function(name){
return this.params[name];
}
com.deconcept.FlashObject.prototype.addVariable = function(name, value){
this.variables[name] = value;
}
com.deconcept.FlashObject.prototype.getVariable = function(name){
return this.variables[name];
}
com.deconcept.FlashObject.prototype.getVariables = function(){
return this.variables;
}
com.deconcept.FlashObject.prototype.getParamTags = function(){
var paramTags = ""; var key; var params = this.getParams();
for(key in params) {
paramTags += '<param name="' + key + '" value="' + params[key] + '"
/>';
}
return paramTags;
}
com.deconcept.FlashObject.prototype.getVariablePairs = function(){
var variablePairs = new Array();
var key;
var variables = this.getVariables();
for(key in variables){
variablePairs.push(key +"="+ variables[key]);
}
return variablePairs;
}
com.deconcept.FlashObject.prototype.getHTML = function() {
var flashHTML = "";
if (navigator.plugins && navigator.mimeTypes &&
navigator.mimeTypes.length) { // netscape plugin architecture
if (this.getAttribute("doExpressInstall")) {
this.addVariable("MMplayerType", "PlugIn"); }
flashHTML += '<embed type="application/x-shockwave-flash" src="'+
this.getAttribute('swf') +'" width="'+ this.getAttribute('width') +'"
height="'+ this.getAttribute('height') +'" id="'+ this.getAttribute('id') + '"
name="'+ this.getAttribute('id') +'"';
var params = this.getParams();
for(var key in params){ flashHTML += ' '+ key +'="'+ params[key] +'"';
}
pairs = this.getVariablePairs().join("&");
if (pairs.length > 0){ flashHTML += ' flashvars="'+ pairs +'"'; }
flashHTML += '></embed>';
} else { // PC IE
if (this.getAttribute("doExpressInstall")) {
this.addVariable("MMplayerType", "ActiveX"); }
flashHTML += '<object
classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="'+
this.getAttribute('width') +'" height="'+ this.getAttribute('height') +'"
id="'+ this.getAttribute('id') +'">';
flashHTML += '<param name="movie" value="' + this.getAttribute('swf')
+ '" />';
var tags = this.getParamTags();
if(tags.length > 0){ flashHTML += tags; }
var pairs = this.getVariablePairs().join("&");
if(pairs.length > 0){ flashHTML += '<param name="flashvars" value="'+
pairs +'" />'; }
flashHTML += '</object>';
}
return flashHTML;
}
com.deconcept.FlashObject.prototype.write = function(elementId){
if(this.skipDetect || this.getAttribute('doExpressInstall') ||
com.deconcept.FlashObjectUtil.getPlayerVersion().versionIsValid(this.getAttribut
e('version'))){
if(document.getElementById){
if (this.getAttribute('doExpressInstall')) {
this.addVariable("MMredirectURL", escape(window.location));
document.title = document.title.slice(0, 47) + " - Flash Player
Installation";
this.addVariable("MMdoctitle", document.title);
}
document.getElementById(elementId).innerHTML = this.getHTML();
}
}else{
if(this.getAttribute('redirectUrl') != "") {
document.location.replace(this.getAttribute('redirectUrl'));
}
}
}
/* ---- detection functions ---- */
com.deconcept.FlashObjectUtil.getPlayerVersion = function(){
var PlayerVersion = new com.deconcept.PlayerVersion(0,0,0);
if(navigator.plugins && navigator.mimeTypes.length){
var x = navigator.plugins["Shockwave Flash"];
if(x && x.description) {
PlayerVersion = new
com.deconcept.PlayerVersion(x.description.replace(/([a-z]|[A-Z]|\s)+/,
"").replace(/(\s+r|\s+b[0-9]+)/, ".").split("."));
}
}else if (window.ActiveXObject){
try {
var axo = new ActiveXObject("ShockwaveFlash.ShockwaveFlash");
PlayerVersion = new
com.deconcept.PlayerVersion(axo.GetVariable("$version").split("
")[1].split(","));
} catch (e) {}
}
return PlayerVersion;
}
com.deconcept.PlayerVersion = function(arrVersion){
this.major = parseInt(arrVersion[0]) || 0;
this.minor = parseInt(arrVersion[1]) || 0;
this.rev = parseInt(arrVersion[2]) || 0;
}
com.deconcept.PlayerVersion.prototype.versionIsValid = function(fv){
if(this.major < fv.major) return false;
if(this.major > fv.major) return true;

there's your HTML file;

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><!-- TDB VitoEl
-->

<html>
<head>
<title>Untitled</title>
<script type="text/javascript" src="flashScript.js"></script>
<LINK REL=stylesheet HREF="PROJECTNAME.css" TYPE="text/css">
</head>
<body leftmargin="0" topmargin="0" rightmargin="0" bottommargin="0"
marginwidth="0" marginheight="0" bgcolor="#ffffff">
<script language="VBScript" type="text/vbscript">
<!-- // Visual basic helper required to detect Flash Player ActiveX control
version information
Function VBGetSwfVer(i)
on error resume next
Dim swControl, swVersion
swVersion = 0

set swControl = CreateObject("ShockwaveFlash.ShockwaveFlash." + CStr(i))
if (IsObject(swControl)) then
swVersion = swControl.GetVariable("$version")
end if
VBGetSwfVer = swVersion
End Function
// -->
</script>
<div id="flashcontent">
<script language="JavaScript" type="text/javascript">
<!--
// Version check based upon the values entered above in "Globals"
var hasReqestedVersion = DetectFlashVer(requiredMajorVersion,
requiredMinorVersion, requiredRevision);

// Check to see if the version meets the requirements for playback
if (hasReqestedVersion) { // if we've detected an acceptable version
var fo = new FlashObject("MOVIENAME.swf", "movie", "380", "440", "7",
"#ffffff");
fo.addParam("allowScriptAccess", "sameDomain");
fo.addParam("quality", "high");
fo.write("flashcontent");
} else { // flash is too old or we can't detect the plugin
var alternateContent = '<img src="images/index_flashPlaceholder.jpg"
width="380" height="440" alt="">';
document.write(alternateContent); // insert non-flash content
}
// -->
</script>

</div>
</body>
</html>

you need the VBScript in there as well. but this is the only solution i've been
able to find. if you have more than one flash movie on a page, use a different
id for the div and change that in the inline script.
this is just another reason, in my opinion, that flash blows.

[quoted text, click to view]

Much easier is the solutions at http://activecontent.blogspot.com

You keep your existing object/embed tags that way and only have minimal
changes to your html.
-
Jecykl