[Coco] VCC Color Computer 3 Emulator v2.0.1 - Public Release (finally!)
Nick Marentes
nickma at optusnet.com.au
Fri Oct 2 04:47:07 EDT 2015
On 2/10/2015 11:39 AM, Bill Pierce via Coco wrote:
>
> After using the new VCC v2.0.1 for a little over a month now, I feel it is stable enough for a binary release.
>
> There have been only a couple of changes from VCC 1.4.2 & VCC 1.4.3b.
>
> 1. The sources were moved from the antiquated "MS Visual C++ 6" (Win95 era) to "MS Visual Studio 2015 Community". VCC should now perform a little better on more "modern" versions of Windows. It also gives us a more modern developement platform.
>
> 2. The "Becker Port" has been moved from the main VCC code to a "becker.dll" module much like the other modules for VCC ("fd502.dll", orch90.dll", mpi.dll", etc). This should keep the Becker Port from interfering with VC mainline code.
>
> Please download a copy and give it a go (sorry, MS Windows only... for now) and let me know if there's any problems or of any suggestions you might have... and no starting the "Coco 4" stuff like: 10,000,000 colors, 10,000 x 10,000 resolution, accessing SATA drives.... Let's get the Coco 3 right FIRST!
> We'll worry about enhancements later.
Should the emulator be configured to run as a standard 512K CoCo3 with
standard ECB (plus DECB?) rather than HBDDOS, Becker ports, drivewires,
hardrives, Orchestra 90 packs , multipacks?
Let the pro user configure the addons. Make it easier for a new user to
enter the world of CoCo3 and less confusing for those unfamiliar with
all the enhancements and "non-standard" add-ons.
And maybe don't distribute an incomplete
still-being-fixed-with-untested-issues out in the wild. Do we want a
myriad of different versions out there to confuse people?
I find it better to assign a handful of people as beta testers to do all
the testing, report their findings to the main developer and release a
near "perfect" version when it's a bit more matured.
Just my 2 cents worth. :)
Nick
More information about the Coco
mailing list