no script engine for ".ws"

[John Menke]

I am getting this error with Windows 2000 when I try to run this line
wscript c:\scripting\first_draft.ws

john

[Andrew Clinick (MS)]

You must have had an early version of WSH 2.0 Beta on your machine. WSH 2.0
doesn't support .ws files in the release version they have to be .wsf. We
had to change the extension to avoid conflict with other programs

"John Menke" <jara...@flash.net> wrote in message
news:#BR21xEt$GA.268@cppssbbsa05...

[Shawn P Cicoria]

That's not true. This was the default behavior. You must associate it in
the regsitry.
I've never installed a beta WSH on my machine and that's exactly what
happens.

This is also documented in the book WSH 2.0

[John Menke]

I don't have access to this book. How do you do the registry hack?

"Shawn P Cicoria" <sh...@cicoria.com> wrote in message
news:#X2V2UGt$GA.213@cppssbbsa03...

[Mike Whalen (MS)]

Which OS did you install the product on? We only supported .ws for the beta,
and all methods of installing the release version will install the correct
registry settings for .wsf files, and nothing for .ws files. We have
completely eliminated the .ws extension from the release version, so if you
are still seeing .ws settings somewhere, you must have installed the beta in
some way.

Also - while the book may have .ws documented, that is not the official
documentation for WSH. All of the official documentation is at
http://msdn.microsoft.com/scripting - we try to support other sources, but
if the book comes out too soon in the development cycle (like I suspect the
book you are referring to did), then it may have errors related to the
author using the beta inplace of released files.

Please be assured that .wsf is the file extension to use. If you have
installed WSH correctly, then you will not have to do any registry hacks to
get it to work (there's a debugging registry hack, but that doesn't affect
actually running WSH files).

Mike Whalen
Windows Script Dev

[Michael Harris]

Just rename the file to .wsf

--
Michael Harris
MVP Scripting

[John Menke]

It must be just the extension... I have Windows 2000 Professional. I named
a file with .ws and tried to run it. I will rename with .wsf and try again.
It should work.

john

"Mike Whalen (MS)" <mwh...@microsoft.com> wrote in message
news:eQVjaaHt$GA.187@cppssbbsa04...

[David Stevenson]

I think the one possible reason the .ws file extension is still prevalent is
that
Dino Esposito in his book, Windows Script Host Programmers Reference
uses the .ws file extension, and the downloadable code examples from wrox
still use the .ws file extension. Apparently, Dino Esposito used the Beta
version of WSH for his book, and the change to .wsf came after he
completed the book.

[George S. Ellis]

Use the slash, slash E:VBScript (// - with E on my machine tries to
associate it to file... Love autocompletion...)

Or
ASSOC .WS=WSHFiles
or VBSFiles...

[Michael Harris]

The .wsf extension recognition is hardcoded in the wscript/cscript executables. Using the _//E
switch won't help-- it only works for "pure" script files (i.e., not xml format)... It's impossible
to get WSH 2.0 to execute .ws files as .wsf without changing the extension.

--
Michael Harris
MVP Scripting

"George S. Ellis" <george...@delta-air.com> wrote in message news:OA24$vnt$GA.266@cppssbbsa03...