On Mon, Dec 29, 2008 at 11:13 AM, William Chops Westfield
<westfw@mac.com> wrote:

> The MPASM manual (chapter 2) implies that mpasm.exe is supposed to
> behave either as a mplab sub-program, a full windows app (pops up a
> full graphics window), a command line app (draws a character graphics
> screen in your "commmand line" window), or a plain command line app
> (accepts all arguments from the command line.)  How it tells the
> difference, or whether it can be forced into one mode or another, is
> not explained.

Actually I believe you are talking about mpasmwin.exe, not mpasm.exe.
mpasmwin.exe which comes from MPLAB IDE installation
(C:\Program Files\Microchip\MPASM Suite\MPASMWIN.exe)
or C18 installation is a GUI program.

There is another mpasm.exe which is a real mode 16bit DOS
program which is still distributed with C18 installation. You can
not use wine with that program. The program is that
program is a real DOS program and do not recognize
long file name.

> When I start it via wine ("wine mpasm.exe foo.asm") it seems to get
> the arguments ok, but it pops up the graphics-style window with the
> results instead of sending them to stdout as I'd expect (generates
> a .err file instead of reporting the errors to stdout too, but perhaps
> that's just the way it works...)

Since it is a GUI program, what you see is normal. It can be invoked
from the console, but it will pop up the GUI program. If you use
Olin's programming environment, you will see the same behavior.

> Is there a "standard" cmd.exe replacement for using with wine?  I
> assume there are license issues with using the one from windows?
>

This is not relevant as explained above.


Xiaofan
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist