Lines Matching refs:prg

326 #		http://mark0.net/download/triddefs_xml.7z/defs/p/prg-c64.trid.xml
334 # but sELF-ExTRACTING-zIP executable unzp6420.prg contains SYS token at end of second BASIC line (a…
338 >>>0		use		c64-prg
347 # the above combination appartly also occur for other Commodore programs like: gunzip111.c64.prg
351 !:ext	prg/pck
354 !:ext	prg/
362 # valid 2nd BASIC fragment found only in sELF-ExTRACTING-zIP executable unzp6420.prg
372 0	name	c64-prg
376 … like in saveroms; When transferring to other platforms, they are often saved with .prg extensions.
378 !:ext	prg/bas/
394 # Reference:	http://mark0.net/download/triddefs_xml.7z/defs/p/prg-c128.trid.xml
406 >>>>0			use	c128-prg
414 #>0			use	c128-prg
419 #>0			use	c128-prg
421 0	name	c128-prg
424 !:ext	prg
442 !:ext	prg/
458 # Reference:	http://mark0.net/download/triddefs_xml.7z/defs/p/prg-vic20.trid.xml
459 #		defs/p/prg-plus4.trid.xml
469 # skip foo with "invalid high" second line offset but not for 0x123b (Minefield.prg)
475 >>>>0			use	c16-prg
476 # invalid second end of line separator !=0 implies binary executable like: Minefield.prg
486 !:ext	prg/
501 0	name	c16-prg
504 !:ext	prg
520 # Reference:	http://mark0.net/download/triddefs_xml.7z/defs/p/prg-vic20-8k.trid.xml
527 >>0		use		vic-prg
532 0	name	vic-prg
535 !:ext	prg
553 !:ext	prg/
569 # Reference:	http://mark0.net/download/triddefs_xml.7z/defs/p/prg-pet.trid.xml
584 >>>0		use		pet-prg
589 0	name	pet-prg
592 !:ext	prg
609 !:ext	prg/
667 …followed by spaces, "control-characters" or colon (:) followed by next commnds or in victracker.prg