-=> Quoting David Roper to Tim Hutzler <=-
 DR> Sorry I misunderstood.  This is what I use to compile a
 DR> 200k (??) file to EXE using an editor for the source code.
 DR> My source code is in SRC.  Looking at this, I don't know
 DR> whether the little "e" in "Compile to eXE" (/Ce) is
 DR> necessary, but that's how it is.
 DR>
 DR> I change to C:
 DR> then cd\pb32
 DR> then
 DR> pbc /Ce /LB- /LS- /DLc:\pb32\src c:\pb32\src\DRMENU.BAS
 DR> and it works!! (amazement ensues here, folks... this is magic!)
DR> I hope this helps you.  I use TSE for my editor.  I wish Dave N and
DR> Sammy   would get together and use each others products so I
DR> wouldn't have to do this.
Right now, I am using an editor that I modified from another
development editor which I use as my IDE. Both are written in PB.
I'm doing this, because QEdit just doesn't have the programmability I
need, and TSE costs - and I still don't know if it will meet my
needs.
I am doing this, because I need the practice, and I want a *core*
editor that I can write extentions for to make them applications of
their own. This is the case with my PB-editor.
I have the /Ce arg, but not the /LB- and /LS-. Those last two leave
off some of the run-time code, and I don't see why they are
necessary. Optional, but not necessary.
 DR> David
--- Maximus/2 3.01
---------------