Well, seems like that's what everyone would want to do.
Command line parameters should OVERRIDE what you put in the source file.

Let's look at a workaround. IF I put a new DEFINE in the .bas file, it seems to get
get passed through. If I edit the default .inc and .bas file to include a different
processor's .inc and .bas files, and don't specify the processor on the command
line, it seems to work.

I should be able to edit the pbproc.bas and pbproc.inc files to include files conditioned
by the new DEFINE. If I call all that without specifying a processor on the
command line, I get a bunch of redefinition errors. My lack of understanding how preprocessor directives and ifdef's work seems the problem. Or maybe the
DEFINES haven't been defined by the time I get to the .inc and .bas files.

Ideas?

Only other thing I think I know how to do is to parse the source file to pull out the
processor type in my new DEFINE and use that to fill in the proc type in the
pbpw command line.
Shouldn't be hard, just ugly.

I have more fun playing with the tools than the actual program.