Eckart Begemann <[EMAIL PROTECTED]> wrote:
>First I admit I am still using PMX1.52 (or 1.53?, anyway the last
PMX-version
>before the "unification" pmxa+pmxb=pmx200).
>That's simply due to quite a large batch file package which I developed
>during the last 2 or 3 years, offering me a more or less
>comfortable menu-guided work with PMX and M-Tx.
>I was too lazy to incorporate PMX200 so far.
>
Here is a crazy (lazy :-)) idea...
Why not create a null program (one that exists but does nothing!! no input,
no output), and replace your pmxb.exe with the null program? Then install
the new pmxab.exe but RENAME it to pmxa.exe.
This way you could run PMX200 without changing any batch files.
Just a thought.
Joel Hunsberger
