Switches

Folks:

I have an EXE file from a Visual Basic application & I would like to
identify the available switches.

Generally, with Microsoft windows EXE files, we can gain access to the
SWITCHES associated with these file.
By typing "Filename.EXE /?" or "Filename.EXE /Help" I can get a list of
all the available switches.

This approach does NOT work with my VisualBasicFile.EXE file.

* Is there another way to identify the switches associates with my EXE
file ?
* Can Microsoft deliberately hide these switches so that "/Help " or "/?"
do NOT show any results ?
* Appreciate any references to study this issue a bit more


Thanks
JoJo

mayayana
Sat Mar 15 10:02:41 CDT 2008

What has that got to do with scripting? Did you
really need to post such a simple question to 4 different
groups?

There's no built in /? switch. It's just traditionally
added when switches are available. An EXE does not
necessarily have switches. They have to be deliberately
added.

If you don't have the VB code and the author didn't
provide any information, there's no way to find switches...
and there may not be any. The only chance you might
have would be to sift through the binary for hard-coded
strings like -e or /e, but even if you find them that doesn't
tell you what they do.


>
> I have an EXE file from a Visual Basic application & I would like to
> identify the available switches.
>
> Generally, with Microsoft windows EXE files, we can gain access to the
> SWITCHES associated with these file.
> By typing "Filename.EXE /?" or "Filename.EXE /Help" I can get a list
of
> all the available switches.
>
> This approach does NOT work with my VisualBasicFile.EXE file.
>
> * Is there another way to identify the switches associates with my EXE
> file ?
> * Can Microsoft deliberately hide these switches so that "/Help " or
"/?"
> do NOT show any results ?
> * Appreciate any references to study this issue a bit more
>
>
> Thanks
> JoJo
>
>

Paul
Sat Mar 15 11:46:46 CDT 2008


<JoJo> wrote in message news:e5kHWjqhIHA.4140@TK2MSFTNGP04.phx.gbl...
> Folks:
>
> I have an EXE file from a Visual Basic application & I would like to
> identify the available switches.
>
> Generally, with Microsoft windows EXE files, we can gain access to
> the
> SWITCHES associated with these file.
> By typing "Filename.EXE /?" or "Filename.EXE /Help" I can get a
> list of
> all the available switches.
>
> This approach does NOT work with my VisualBasicFile.EXE file.
>
> * Is there another way to identify the switches associates with my
> EXE
> file ?
> * Can Microsoft deliberately hide these switches so that "/Help "
> or "/?"
> do NOT show any results ?
> * Appreciate any references to study this issue a bit more

Hi, JoJo

As mayayana said, the EXE may have no help information.
One thing you might try is to read the entire file into a string,
change all non-text characters (Chr0 to Chr31 and Chr 128 to Chr255)
to Chr32 (space), then write the string to a .txt file. Then view the
text file with notepad or some other plain text viewer. Sometimes you
will find useful info and sometimes you don't. Maybe someone will
post a script or regular expression to blank out the non-text
characters.

-Paul Randall

foxidrive
Sat Mar 15 13:02:06 CDT 2008

On Sat, 15 Mar 2008 10:46:46 -0600, "Paul Randall" <paulr901@cableone.net>
wrote:

>As mayayana said, the EXE may have no help information.
>One thing you might try is to read the entire file into a string,
>change all non-text characters (Chr0 to Chr31 and Chr 128 to Chr255)
>to Chr32 (space), then write the string to a .txt file. Then view the
>text file with notepad or some other plain text viewer. Sometimes you
>will find useful info and sometimes you don't. Maybe someone will
>post a script or regular expression to blank out the non-text
>characters.
>
>-Paul Randall
>


Peek.com is 960 bytes and useful for this Paul.



PEEK

reads the text parts of any file, even with extensions like
EXE, COM, OVR, OBJ, HLP, BAS, BIN, DEF, FMT, DBF, SYS etc.
It will also read text files: TXT, DOC, DAT, LST etc.
It ignores graphic characters and omits empty lines.

Correct syntax is PEEK [/p] filename.ext [>newfile.ext]

Optional switches: /p displays one screen at a time
(may be anywhere /w forces WordStar interpretation
on command line) (normally automatic)

The output may be redirected into a disk file ( newfile.ext
above ) and edited and/or printed out.
If you have forgotten what a program does, or its syntax, you
will generally find in the PEEK output:
1) The origin and author of the program
2) Any Help messages
3) Clues to syntax, special switches, etc.

Jan Machacek Autelco Ltd., 103 London Road,
March 1989 Staines, Middx. TW18 4HN


--
Posted via a free Usenet account from http://www.teranews.com

noone
Mon Mar 17 17:30:17 CDT 2008

Il giorno Sun, 16 Mar 2008 05:02:06 +1100, foxidrive <gotcha@woohoo.invalid> ha scritto:

>On Sat, 15 Mar 2008 10:46:46 -0600, "Paul Randall" <paulr901@cableone.net>
>wrote:
>
>>As mayayana said, the EXE may have no help information.
>>One thing you might try is to read the entire file into a string,
>>change all non-text characters (Chr0 to Chr31 and Chr 128 to Chr255)
>>to Chr32 (space), then write the string to a .txt file.

>Peek.com is 960 bytes and useful for this Paul.

A script for this could be shorter. With the output in an IE window.

Giovanni.
--
Giovanni Cenati (Bergamo, Italy)
Write to user "Reventlov" and domain at katamail com
http://digilander.libero.it/Cenati (Esempi e programmi in VbScript)
--