gnupic: Thread: Re: SOLUTION: How to use MPASM generated "cod" files with GPSIM

On Thu, Sep 14, 2000 at 11:57:27AM +0200, Wojtek Zabolotny wrote:
> Up to now I did it just with Midnight Commander (F3 to view -> F2 to edit -> 
> repeatedly F2 to switch hex/text edit -> F6 to save), but I'm
> considering to write a simple C program or Perl script to make it
> automatically (making chnages "by hand" after each compilation is rather
> boring & tiring).

Well, so this is the C program for automatic modification of DOS-MPASM
generated COD file, so that it can be used by the GPSIM.
I attached the gzipped (to spare the bandwidth) C sources to this message.

There are however some conditions, which must be met:
1. All sources and include files must be in the same directory (and the
   gpsim must be later called from that directory)
2. All sources and include files must be in lower case.

This solution allows for assembling of files with the DOS-MPASM (ran under
DOSEMU) and simulating of programs with GPSIM.

The source requires the "cod.h" included in GPSIM sources.
The program should be compiled with
gcc -o codmpasm codmpasm.c
And run with
codmpasm filename.cod

WARNING! The program modifies the cod file with name given as it's argument.
The original contents gets destroyed.
-- 
			HTH & Greetings
			Wojciech Zabolotny
			http://www.ise.pw.edu.pl/~wzab

When buying any hardware, ask the dealer if it is Open Source friendly!!!
http://www.openhardware.org

On Thu, Sep 14, 2000 at 10:00:31PM -0300, Garst R. Reese wrote:
> Wojtek Zabolotny wrote:
> 
> > Well, so this is the C program for automatic modification of DOS-MPASM
> > generated COD file, so that it can be used by the GPSIM.
> > I attached the gzipped (to spare the bandwidth) C sources to this message.
> Where? ?;>)

The "gnupic" mailserver removes non-text attachments as viruses =:-(.
My full message with attachment can be found in
http://www.infosite.com/~jkeyzer/piclist/2000/Sep/0906.html
The username is "piclist" & the password is "piclist".
Sorry for confusion.

-- 
				   Greetings
	                      Wojciech M. Zabolotny
	http://www.ise.pw.edu.pl/~wzab  <--> ####@####.####

http://www.freedos.org  Free DOS for free people!

On Fri, 15 Sep 2000, Wojtek Zabolotny wrote:
> The "gnupic" mailserver removes non-text attachments as viruses =:-(.

Not quite true- it's mainly meant to get rid of annoying attachments such
as messages with both text and HTML bodies, or vcards (nothing to do with
viruses). tar.gz files normally get through (as long as they fit within
the maximum message size limit), as the usual mime type for them is
application/x-gunzip (your mailer used application/octet-stream which can
apply to pretty much anything).

Would people prefer me to remove the rule and get HTML messages and such
through unfiltered, trim it down somewhat (remove application/octet-stream
and other common types but leave things like text/html, text/v-card,
application/excel, application/msword, etc.), or leave it as it is?

-- 
--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

On Thu, 14 Sep 2000, Wojtek Zabolotny wrote:

> On Thu, Sep 14, 2000 at 11:57:27AM +0200, Wojtek Zabolotny wrote:
> > Up to now I did it just with Midnight Commander (F3 to view -> F2 to edit -> 
> > repeatedly F2 to switch hex/text edit -> F6 to save), but I'm
> > considering to write a simple C program or Perl script to make it
> > automatically (making chnages "by hand" after each compilation is rather
> > boring & tiring).
> 
> Well, so this is the C program for automatic modification of DOS-MPASM
> generated COD file, so that it can be used by the GPSIM.
> I attached the gzipped (to spare the bandwidth) C sources to this message.

I'll try to package this with gpsim in the next major release. Perhaps I'll
create a `utils' subdirectory and place it there.

BTW, I've place the latest copy of gpsim on the web:

http://www.dattalo.com/gnupic/gpsim-0.20.4.tar.gz

This includes Daniel Christian's patch for reading MPLAB formatted .cod files.
So you may wish to play with it to see how it compares to the utility you've
created.


In addition, this version of gpsim has the ability to log the trace buffer to a
file. As I said on the gnupic list (this is cc'd to the PICLIST), this creates
enormous files (e.g. 70Megs in a few seconds!). Needless to say, the feature is
currently inhibited. 

Scott

On Fri, Sep 15, 2000 at 01:27:39PM +0100, Alex Holden wrote:
> On Fri, 15 Sep 2000, Wojtek Zabolotny wrote:
> > The "gnupic" mailserver removes non-text attachments as viruses =:-(.
> 
> Not quite true- it's mainly meant to get rid of annoying attachments such
> as messages with both text and HTML bodies, or vcards (nothing to do with
> viruses). tar.gz files normally get through (as long as they fit within
> the maximum message size limit), as the usual mime type for them is
> application/x-gunzip (your mailer used application/octet-stream which can
> apply to pretty much anything).

I've checked my /etc/mime.types and there was no entry for ".gz" files.
However I found the following remark at the begining of this file:

#  Note: Compression schemes like "gzip", "bzip", and "compress" are not
#  actually "mime-types".  They are "encodings" and hence must _not_ have
#  entries in this file to map their extensions.  The "mime-type" of an
#  encoded file refers to the type of data that has been encoded, not the
#  type of the encoding.          

So what should I set to get the "application/x-gunzip" type for ".gz" files?

-- 
			TIA & Greetings
			Wojciech Zabolotny
			http://www.ise.pw.edu.pl/~wzab

http://www.gnupg.org  Gnu Privacy Guard - protect your mail & data
                      with the FREE cryptographic system

On Fri, 15 Sep 2000, Wojtek Zabolotny wrote:
> #  Note: Compression schemes like "gzip", "bzip", and "compress" are not
> #  actually "mime-types".  They are "encodings" and hence must _not_ have
> #  entries in this file to map their extensions.  The "mime-type" of an
> #  encoded file refers to the type of data that has been encoded, not the
> #  type of the encoding.
 
That's not how the mime types are conventionally used though. Consider
what would happen, for example, if a web server sent the mime type
text/plain for gzip encoded text files (according to the above comment,
the data that has been encoded is text, so that's what the mime type
should be). The browser would display the binary file as if it was a text
file instead of asking for a location to save it as you would expect...

> So what should I set to get the "application/x-gunzip" type for ".gz" files?

I wouldn't bother. application/octet-stream is just as valid for gzip
files as application/x-gzip or application/x-gunzip (it's basically a
generic "any binary data" type). I've trimmed down the mimeremove rules a
lot so a lot of things that previously would have got stripped (including
application/octet-stream) will now get through.

-- 
--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------