I've been trying to learn how to encode .vbs files for about a week now....but i still havent found anything or anyone that knows how to do it.......if anyone knows how to encode .vbs files (without using MS Script Encoder) please show me.......thanx in advance

Why don't you want to use the MS Script Encoder?

Well one reason is because theres a MS Script Decoder...and I feel better when I know that I encoded it....do you know how to ?

Why would you want to encode a script anyway? the only people i know of that encode scripts are virus writers.

There are many people on the net that want their scripts encoded so that people who cant write their own dont steal the theirs, and if the only people you know that encode their scripts are virus writers...I feel sorry for you. :)

If you encode your scripts with something other than the MS Script Decoder, will a users browser know how to decode and run them?

I guess so...because there's a key or something that the browser uses to read and process the script....or did you already know the answer to that ?

As long as a users browser has the 'view source' opion of a webpage they will always be able to see your script, unless it is run server side such as PHP or ASP.

They might be able to see the script but if it is encoded then all they'll see is the encoded script....

Yeah, and this will work on any browser I'm assuming? Your script will be robust and easy to execute without the aid of a plugin?

Or he may just be targetting the majority of users.. The ones using IE. (Something I'm totally against, mind you)

"They might be able to see the script but if it is encoded then all they'll see is the encoded script.... "

but then they could just use MS script decoder ;)

Thats what my first post was againt (MS Script Encoder)
"if anyone knows how to encode .vbs files (without using MS Script Encoder) please show me.......thanx in advance"

Well it seems that it either:
a) Can't be done
b) No one here knows how to do it.
c) All of the above

Yea thats what I thought but i'll go with B)...thanx for to everyone that tried to help :)

Well, I suppose my concern is, if you encode your script with something other than the MS Script Encoder, a user's browser will not be able to unencode it because it will be trying to use the MS Sciprt Decoder, which I assume is built into IE. If you encode your script with something else, you'll need need to provide a way to unencode it. However, if the encoder was able to attach header code to the script that would unencode it on the fly, then I suppose it would work ... kind of like executable compressors.

But then a sufficiently clever person could use the attached decoding stuff to get a cleartext version of the script.

Exactly, and thus the need to encode with anything other than the Ms Script Encoder is nullified.