View Single Post
  #15  
Old September 27th 13, 04:39 AM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default "animator.hta" has stopped working!

Peter Jason wrote:

On Thu, 26 Sep 2013 14:08:10 -0500, VanguardLH
wrote:

Peter Jason wrote:

VanguardLH wrote:

Just how are you starting this HTA?

All I know is that it had an exe extension, and when I copied it into
a folder with GIF files and clicked on it then all the gifs were
animated all at once.


HTA programs are HTML code to be submitted to and ran by the mshta.exe
interpreter. You should be using the htafile handler, not the one for
exefile.

You'll need to fix your filetype associations. Or just try renaming
from animator.exe to animator.hta and then see what happens when you
double-click in Windows Explorer in an .hta filetype.


I tried to get back the *.exe extension by fixing
the "file association" to "Windows Command
Processor" and now I can't change this back again,
even from the Set Associations window. The HTA
alwys opens with the CMD black screen in the
centre! How do I reverse this?


Why were you trying to "get back the .exe" association when you
should've been renaming the .exe file to .hta and then double-click on
the .hta file to use the htafile handler for that filetype? Even if
there was a problem with the htafile definition in the registry, why
were you putzing around with the exefile definition?

I'm not sure what you used. By "Set Associations" do you mean you went
to Control Panel - Programs - Default Programs (enter "default
programs" in the Start menu searchbox) and then clicked on "Associate a
file type or protocol with a program"? Or were you in a command shell
and ran the assoc.exe program?

In the former Control Panel method, you won't even see .exe listed as a
filetype so how were you able to change it? Did you mean you used this
applet to change the *.hta* association? Since you were told to
associate .hta files with the mshta.exe program, why did you instead
choose to associate it with cmd.exe (which I'm assuming is what you
meant by "Windows Command Processor" instead of command shell aka
command prompt)? If you picked the wrong handler for the .hta filetype
association then why not use the same procedure you used before to
instead associate the mshta.exe program as the .hta handler?
Ads