From: Maciej Witkowiak (ytm_at_elysium.pl)
Date: 2003-02-05 23:47:16
Todd Elliott dnia 06 lut 2003 o 08:44 +1030 napisał: > * GRC seems to pad one byte (a zero?) to the end of each GEOS VLIR module. > For example, a GEOS VLIR application would have five VLIR records with the > following byte sizes: V0# 8004 bytes, V1# 4254 bytes, etc. With GRC, the > resulting module sizes are: V0# 8005 bytes, V1# 4255 bytes, etc. While It is possible that padding code is still wrong. > * How do I add blank records? For example, a VLIR application would have > its first ten VLIR links filled with modules, followed by a blank link > (00,ff), followed by additional five VLIR links, then with three more > blank links (00,ff) and finishing off with 00's for the rest of the VLIR > chain. Is there a NULL directive for GRC to insert blank VLIR links? Keyword "blank" will put (0,0), keyword "noexist" - (0,ff) use them as names of records. The record table is initially filled with 0s. For you example the command would be: grc out.cvt header vlir0 (...) vlir9 noexist vlir11 vlir12 vlir13 noexist \ noexist noexit Of course you have to fill in (...) with names :). Please correct me if the names should be swapped (or different) according to GEOS naming scheme. ytm -- We resolve to energetically integrate our bilateral action items, cross-media sub-technologies, and strategic alliances in order to multiply our net worth. Dr. Gregg Carse ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2003-02-05 23:49:54 CET