You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(from old issues page)
Luis46coco commented on Apr 14, 2017
The .pak cartridges have a header and a foot with information, which can easily be recognized and accepted, they are no longer used much, but it is easy to make them not block and run well, less problems for the new coco initiates.
.pak only serve for emulators in ms-dos, but it's easy to accept them.
Some time ago I made a converter
PRINT "Program for convert Color Computer Cartridge V.1.00 01/2011"
PRINT "By Luis Fernandez [email protected]"
PRINT "MS-DOS convert filenames to 8.3 and uppercase"
PRINT
PRINT "Use COCOPAK *.PAK *.CCC"
PRINT " or COCOPAK *.CCC *.PAK"
PRINT
PRINT "CCC to PAK"
PRINT " Add at first, 2 Bytes int len(arch) and 2 Bytes int &hC000"
PRINT " and at end, 33 bytes 0 (cero) and 2 Bytes int &hC000"
PRINT
PRINT "PAK to CCC"
PRINT " delete 4 bytes at first and 35 bytes at end"
END
The text was updated successfully, but these errors were encountered:
(from old issues page)
Luis46coco commented on Apr 14, 2017
The .pak cartridges have a header and a foot with information, which can easily be recognized and accepted, they are no longer used much, but it is easy to make them not block and run well, less problems for the new coco initiates.
.pak only serve for emulators in ms-dos, but it's easy to accept them.
Some time ago I made a converter
PRINT "Program for convert Color Computer Cartridge V.1.00 01/2011"
PRINT "By Luis Fernandez [email protected]"
PRINT "MS-DOS convert filenames to 8.3 and uppercase"
PRINT
PRINT "Use COCOPAK *.PAK *.CCC"
PRINT " or COCOPAK *.CCC *.PAK"
PRINT
PRINT "CCC to PAK"
PRINT " Add at first, 2 Bytes int len(arch) and 2 Bytes int &hC000"
PRINT " and at end, 33 bytes 0 (cero) and 2 Bytes int &hC000"
PRINT
PRINT "PAK to CCC"
PRINT " delete 4 bytes at first and 35 bytes at end"
END
The text was updated successfully, but these errors were encountered: