how to encode VBS files

[Randy Franklin Smith]

Propably a dumb question. I'm trying to encode some vbs files I run from
wsh(cscript). When I type:

E:\pwreset>c:screnc server.vbs junk

I get:

Bad format for file 'E:\pwreset\junk'

Scripting encoder object ("Scripting.Encoder") failed on
E:\pwreset\SERVER.VBS

Is anyone using the encoder with vbs files? If so what's the secret? Your
help is appreciated.

[Andrew Clinick (MS)]

you need to change the command line to:

c:screnc server.vbs junk.vbe

"Randy Franklin Smith" <randy...@ibm.net> wrote in message
news:OXrN7u$7#GA.55@cppssbbsa04...

[Randy Franklin Smith]

Thanks for your help, unfortunately here is what I get:

E:\pwreset>c:screnc server.vbs junk.vbe

Bad format for file 'E:\pwreset\junk.vbe'

Scripting encoder object ("Scripting.Encoder") failed on
E:\pwreset\SERVER.VBS

Do I need to do something with the script source code?
Andrew Clinick (MS) wrote in message ...

[Chris Lowde]

Randy,

You need to have the following line in your script.

'**Start Encode**

You can also include a coresponding

'*Stop Encode**

making it possible to only encode parts of a script.

Chris Lowde
mailto:low...@texaco.com

"Randy Franklin Smith" <randy...@ibm.net> wrote in message

news:OaYwuRV9#GA.197@cppssbbsa04...

[Randy Franklin Smith]

Chris,

Thank you very much for your response - however I already have '**Start
Encode** present in my source. Any other ideas?

RFS

Chris Lowde wrote in message ...

[Mike Whalen (MS)]

The errror message you are receiving can occur in one of two situations on
an output file:

1) Screnc is unable to write the file - usually because it's read-only for
some reason.
2) A Unicode error occured - something in the file may not be translatable
to an appropriate Unicode format.

What is the Unicode format of the original file? Screnc tries to match that,
and perhaps a character is getting output that can't get encoded. I thought
we kept them all at 7 bit characters, but I didn't write it, so I don't know
for sure.

Also - does the output file already exist? If so, do you have it open
somewhere, perhaps?

Note - the **Start Encode**/**Stop Encode** block is not required. Those
tags allow you to selectively encode a portion of the script. If you don't
have them, the entire script will be encoded.

Otherwise, I don't see why you would receive that message. Is the disk full
maybe?

Mike Whalen,
Windows Script Dev

Randy Franklin Smith <randy...@ibm.net> wrote in message

news:OZwLuMY9#GA.240@cppssbbsa04...

[Randy Franklin Smith]

Mike,

Please don't forward that last file to anyone else and I really appreciate
your help. I have an upcoming article in Information Security Mag about MS
and Win2k. I'm commending MS on how they are beefing up there support and
committment to quality, support and security. It's good to see you and
other MS folks out here answering questions.

Mike Whalen (MS) wrote in message ...