[Coco] VCC hdbdw3bc3.rom files
davidwladd at gmail.com
Thu Jul 7 10:13:01 EDT 2016
Technically the ROMs can not be included in the source and must be
externally loaded for copyright issues.
This is why MAME and other emulators require this as well.
On Wednesday, July 6, 2016, Nick Marentes <nickma at optusnet.com.au> wrote:
> A suggestion...
> Why not have VCC packaged and designed to run as a standard disk based
> system with just the standard ROMS included? This will make it easier for
> novices and newcomers to get up to speed.
> The additional ROMS and multitude VHD configurations can be on the
> official VCC website (with official VCC release version) for experts to
> download. These can then be categorized and documented clearly on the
> website without the need to understand cryptic filenames or have to read
> additional document files. (Who reads manuals right?)
> It's all about user friendliness. Let's not "OS9'ify" a great emulator and
> keep an easy to use system...easy.
> This I feel satisfies both novices and experts alike.
> On 7/07/2016 3:44 AM, Salvador Garcia via Coco wrote:
>> Hi all,
>> Motivated by CoCoFEST and Steve's emulator videos I went ahead and
>> installed VCC 2.01 with Drivewire 4 (using DECB). All went well and I am
>> documenting what I have done; however, I have a question. When setting up
>> the Becker port I need to select an external ROM within the FD-502 floppy
>> controller configuration.
>> When looking at the files included with VCC I see four similar ROM files
>> for HDBDW:
>> hdbdw3bck w-offset 5A000.rom
>> hdbdw3bc3 w-offset 5A000.rom
>> From the documentation that I found, it seems that those with the 5A000
>> offset are for use with NitrOS9 and those without it are for DECB. Further,
>> those ending with bck are for the COCO 1 and 2 while those ending with b3
>> are for the CoCo 3. Is this correct? Thanks all! Salvador
> Coco mailing list
> Coco at maltedmedia.com
Sent from Gmail Mobile on iOS.
More information about the Coco