[Coco] VCC Update

[James Ross]

Just a suggestion --> Discussions at this level should probably be taken off the list and put in the GitHub messaging system on the commits where they are being modified... (We need to learn how to use GitHub for this kind of communication back-and-forth OR we will bore the others on this list to death!) 

Comment left ... 

https://github.com/jross9/VCC/commit/7d83e2ed7112920d4bfab62728c7f20e9c3d4187

or (same commit from Luis fork)

https://github.com/Luis46coco/VCC/commit/7d83e2ed7112920d4bfab62728c7f20e9c3d4187

Anyone can chime in and the list of commits has a little flag showing which ones have comments.

James

________________________________________
From: Coco <coco-bounces at maltedmedia.com> on behalf of Luis Fernández <luis46coco at hotmail.com>

Ok for me, but keep this in mind
Start playing cartridges, every time you open one, you have to make a change in the selection of hardware to cartridge, and in the end, the hardware is used little, once loaded and not touching loads

Also if the directory is full of * .ccc, * .pak or * .rom, the interesting thing is to see the ccc at first glance, I propose something like bill,

Also the roms and the ccc are loaded in $C000, whether they are rom basic or rom cartridges and ccc also, just have to make a touch to accept .pac

Program pak (*.rom, *.ccc, *.pak)
Virtual Hardware (*.dll)
All (*.*)

By the way is written in English Program pak or Program pack?